[Debian-eeepc-devel] New version of eeepc-acpi-scripts needs testing

[oz]

On Sat, 6 Sep 2008 01:40:41 +0300
Damyan Ivanov <dmn at debian.org> wrote:

> Hi, I was going to upload the current Git version of 
> eeepc-acpi-scripts tonight, but took some time to implement an 
> additional feature or two.
> 
>  * support toggling of internal Bluetooth on models that have it. 
>    Bound to soft-button #4 by default
>  * add support for toggling the built-in camera. Bound to 
>    soft-button #3 by default
>  * support configurable soft-button actions
>  * add support for turning the lid off, bound to soft-button #1 by 
>    default
>  * hotkey.sh, functions.sh: pass notifications to gnome-osd server 
>    if that is detected running. Add gnome-osd to Suggests
> 
> Since the changeset grew large, it would be nice if the package gets 
> some testing before the upload.
> 
> Please fetch[1] the source from the Git repository, build[2], 
> install[3] and test[4] the package.
> 
> Comments, corrections, flames all welcome :)
> 
>  [1] git clone git://git.debian.org/git/debian-eeepc/eeepc-acpi-scripts.git
>  [2] cd eeepc-acpi-scripts
>      debuild -us -uc -i -I
>  [3] dpkg -i ../eeepc-acpi-scripts_1.0.6_all.deb
>  [4] see if all special keys work as they should. try changing some
>      binding (i.e. move screen blanking to another key)
> 
> -- 
> dam            JabberID: dam at jabber.minus273.org
> 

Hi,

I followed your git guide and installed eeepc-acpi-scripts 1.0.6
(previous 1.0.5) on my 901 2.6.26-1 lenny.

* Button #1 works perfectly. Screen goes off.

* Webcam with button #3 excellent!
  I tested it with the viewer luvcview. In detail:

  button #4 --> 'Camera enabled' from aosd -->
$ luvcview
luvcview 0.2.4

SDL information:
  Video driver: x11
  A window manager is available
Device information:
  Device path:  /dev/video0
Stream settings:
  Frame format: YUYV (MJPG is not supported by device)
  Frame size:   640x480
  Frame rate:   30 fps

--> camera-window pops up and camera-LED goes on.

button #4 again --> 'Camera disabled' from aosd -->

$ luvcview
luvcview 0.2.4

SDL information:
  Video driver: x11
  A window manager is available
Device information:
  Device path:  /dev/video0
ERROR opening V4L interface: No such file or directory

* Bluetooth seems to be a little odd. But I don't know how to test it
correctly, because I have no external bluetooth-devices.

I started testing with BT disabled in BIOS. No bluetooth messages
appear in syslog (ok). The wireless-LED is off. Pressing button #4
produces these syslogs:

Sep  6 12:03:53 ebony kernel: [  523.704003] Bluetooth: HCI device and
connection manager initialized Sep  6 12:03:53 ebony kernel:
[  523.704003] Bluetooth: HCI socket layer initialized Sep  6 12:03:53
ebony kernel: [  523.713361] Bluetooth: HCI USB driver ver 2.9 Sep  6
12:03:53 ebony kernel: [  523.713361] usbcore: registered new interface
driver hci_usb Sep  6 12:03:53 ebony NetworkManager: <debug>
[1220695433.230721] nm_hal_device_added(): New device added (hal udi is
'/org/freedesktop/Hal/devices/platform_bluetooth').

... and Bluetooth Off appears on the screen (aosd-cat is installed).

When I press #4 again, Bluetooth Off is shown again. As well with
every new key-press. No further syslog messages are produced.

Then I rebooted and enabled BT in BIOS. While booting the wireless-LED
went on (!). In the bootlog I found now:

Sep  6 11:47:09 ebony kernel: [   10.193372] Bluetooth: Core ver 2.11
Sep  6 11:47:09 ebony kernel: [   10.204950] NET: Registered protocol
family 31 Sep  6 11:47:09 ebony kernel: [   10.204950] Bluetooth: HCI
device and connection manager initialized Sep  6 11:47:09 ebony kernel:
[   10.204950] Bluetooth: HCI socket layer initialized Sep  6 11:47:09
ebony kernel: [   10.303157] Bluetooth: HCI USB driver ver 2.9 Sep  6
11:47:09 ebony kernel: [   10.305420] usbcore: registered new interface
driver hci_usb

Pressing button #4 always shows 'Bluetooth Off' on OSD. No further
events in syslogs. The odd thing is, the wireless-LED stays always on.
Normally I can switch it on and off with Fn+F2 (together with ra0).

So I think it is save, to start the eee with BT disabled in BIOS. -

I saw wireless.sh is unchanged, so I continue to take my modified
version:

 #!/bin/sh

. /usr/share/eeepc-acpi-scripts/functions.sh

wlan_control=/sys/devices/platform/eeepc/wlan
[ -e $wlan_control ] || wlan_control=/proc/acpi/asus/wlan # pre-2.6.26

case $1 in
    on|enable)
        if [ $(cat $wlan_control) = 0 ]; then
            modprobe -r pciehp
            modprobe pciehp pciehp_force=1 pciehp_slot_with_bus=1
            echo 1 > $wlan_control
            #detect_wlan
            #modprobe $WLAN_MOD
            # adding a sleep here, due to some bug the driver loading
is not atomic here # and could cause ifconfig to fail
            #sleep 1
            #if ! ifconfig $WLAN_IF up; then exec $0 off; fi
        fi
        ;;
    off|disable)
        if [ $(cat $wlan_control) = 1 ]; then
            detect_wlan
            ifdown --force $WLAN_IF
            modprobe -r $WLAN_MOD
            echo 0 > $wlan_control
        fi
        ;;
    *)
        echo "Usage: $0 [on|off]"
        exit 1
        ;;
esac

Thanks, Damyan, for making the new button-functions available!

regards,
oz