Page 17 of 19 FirstFirst ... 71516171819 LastLast
Results 161 to 170 of 188

Thread: Power Management gui

  1. #161
    Join Date
    Jun 2007
    Location
    Columbus, OH
    Beans
    172
    Distro
    Ubuntu 8.10 Intrepid Ibex

    Re: Power Management gui

    Yes they are up, acutally using them both right now.

  2. #162
    Join Date
    Jun 2006
    Beans
    267

    Re: Power Management gui

    is the interfaces section just blank? or is it not detecting all of them?

  3. #163
    Join Date
    Jun 2007
    Location
    Columbus, OH
    Beans
    172
    Distro
    Ubuntu 8.10 Intrepid Ibex

    Re: Power Management gui

    Nope, just have lo.

  4. #164
    Join Date
    Jun 2006
    Beans
    267

    Re: Power Management gui

    that's weird, the autodetection works by taking your ifconfig and parsing the output of that. Thats why the interface needs to be up, but if it's finding lo it should find the others. Do you mind posting your ifconfig?

  5. #165
    Join Date
    Jun 2007
    Location
    Columbus, OH
    Beans
    172
    Distro
    Ubuntu 8.10 Intrepid Ibex

    Re: Power Management gui

    Bluetooth is down right now, but here id the rest.


    Code:
    ifconfig
    eth0      Link encap:Ethernet  HWaddr 00:1c:23:0f:eb:8c  
              UP BROADCAST MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
              Interrupt:18 
    
    lo        Link encap:Local Loopback  
              inet addr:127.0.0.1  Mask:255.0.0.0
              inet6 addr: ::1/128 Scope:Host
              UP LOOPBACK RUNNING  MTU:16436  Metric:1
              RX packets:22 errors:0 dropped:0 overruns:0 frame:0
              TX packets:22 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0 
              RX bytes:1500 (1.5 KB)  TX bytes:1500 (1.5 KB)
    
    wlan0     Link encap:Ethernet  HWaddr 00:13:e8:09:81:73  
              inet addr:192.168.0.101  Bcast:192.168.0.255  Mask:255.255.255.0
              inet6 addr: fe80::213:e8ff:fe09:8173/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:4768 errors:0 dropped:0 overruns:0 frame:0
              TX packets:5254 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:3861893 (3.8 MB)  TX bytes:620254 (620.2 KB)
    
    wmaster0  Link encap:UNSPEC  HWaddr 00-13-E8-09-81-73-31-37-00-00-00-00-00-00-00-00  
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  6. #166
    Join Date
    Jun 2006
    Beans
    267

    Re: Power Management gui

    ok I think I fixed the interface detection part. Give it a try now, also I changed the cdrom drive detection part but I'm not sure if it will fix your issue, if it doesn't could you run
    Code:
    hal-find-by-capability --capability storage.cdrom
    and tell me the output?

  7. #167
    Join Date
    Nov 2005
    Beans
    60
    Distro
    Ubuntu 9.04 Jaunty Jackalope

    Re: Power Management gui

    Quote Originally Posted by iggykoopa View Post
    if you want to try to figure it out yourself, around line 500 is the class firelauncher, you'll need to copy that section and modify it. If you want me to look into it I could try to make the launcher code more modular so it is easier to launch other applications as well.
    Okay, I'll give it a try. Don't bother making easier to launch it to another applications. You can put it on far future to do list. hehe
    Just installed revision 46, fresh install, working fine, cd-rom detects, interfaces detects, also tested.
    Bluetooth is being detected, although I don't even have the service here, isn't something linked with the uhci_hcd, which is also used for usb?
    Last edited by felipefoz; December 24th, 2008 at 08:44 PM.

  8. #168
    Join Date
    Jun 2006
    Beans
    267

    Re: Power Management gui

    some of the bluetooth stuff depends on uhci (which is for usb) so you need to remove uhci before you can remove bluetooth. And it uses hciconfig to detect bluetooth so that may be why it is detecting something for you.

  9. #169
    Join Date
    Nov 2005
    Beans
    60
    Distro
    Ubuntu 9.04 Jaunty Jackalope

    Re: Power Management gui

    Quote Originally Posted by iggykoopa View Post
    some of the bluetooth stuff depends on uhci (which is for usb) so you need to remove uhci before you can remove bluetooth. And it uses hciconfig to detect bluetooth so that may be why it is detecting something for you.
    Hum, so it uses hciconfig, I was just checking that I don't have installed hciconfig, as I uninstalled all bluetooth support as I don't have it. When the program tries to detect bluetooth through hciconfig, it doesn't find because it is uninstalled and somehow it detects it.

  10. #170
    Join Date
    Nov 2005
    Beans
    60
    Distro
    Ubuntu 9.04 Jaunty Jackalope

    Re: Power Management gui

    I was researching about brightness here
    I found out that gnome-power-manager also uses hal (one of the ways) to detect and change the lcd brightness.
    here I typed
    Code:
    $ lshal | grep video
      system.hardware.primary_video.product = 1331  (0x533)  (int)
      system.hardware.primary_video.vendor = 4318  (0x10de)  (int)
      linux.sysfs_path = '/sys/devices/virtual/backlight/acpi_video0'  (string)
      input.keymap.data = {'e025:help', 'e026:setup', 'e027:battery', 'e029:switchvideomode', 'e033:euro', 'e034:dollar', 'e054:bluetooth', 'e055:wlan', 'e056:wlan', 'e057:bluetooth', 'e058:bluetooth', 'e059:brightnessup', 'e06e:brightnessup', 'e06f:brightnessdown', 'e071:f22', 'e072:f22', 'e073:prog2', 'e074:prog1', 'e075:presentation', 'e078:fn', 'e079:f23'} (string list)
      info.linux.driver = 'uvcvideo'  (string)
      info.linux.driver = 'uvcvideo'  (string)
    udi = '/org/freedesktop/Hal/devices/usb_device_64e_a101_CN0314_OV03_VA_R02_00_00_if0_video4linux'
      access_control.file = '/dev/video0'  (string)
      access_control.type = 'video4linux'  (string)
      info.capabilities = {'video4linux', 'video4linux.video_capture', 'access_control'} (string list)
      info.category = 'video4linux'  (string)
      info.subsystem = 'video4linux'  (string)
      info.udi = '/org/freedesktop/Hal/devices/usb_device_64e_a101_CN0314_OV03_VA_R02_00_00_if0_video4linux'  (string)
      linux.device_file = '/dev/video0'  (string)
      linux.subsystem = 'video4linux'  (string)
      linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:04.1/usb2/2-2/2-2:1.0/video4linux/video0'  (string)
      video4linux.device = '/dev/video0'  (string)
      video4linux.version = '1'  (string)
    Then I found another way to change brightness (0 to 9), in the third line, listing the video path.
    Code:
    echo 9 > /sys/devices/virtual/backlight/acpi_video0/brightness
    another way by me, is using the /proc/ but it is far more complicated to get to the folder, as you already know
    I'd suggest to have a look into it.
    cheers
    merry xmas to all

    edit: I didn't figure out yet, but gpm uses dbus to send a message to hal, to change brightness, hal also provides information on how many levels of brightness is supported, etc...
    Last edited by felipefoz; December 25th, 2008 at 12:48 AM.

Page 17 of 19 FirstFirst ... 71516171819 LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •