Thanks for your replay. It is a very strange problem, because does not occur always. Now, for example, all goes well.
Here is the output of second command: eeepc:~# sh -x /etc/acpi/actions/hotkey.sh . . 00000039 .; echo 'ret:' $? + PKG=eeepc-acpi-scripts + FUNC_LIB=/usr/share/eeepc-acpi-scripts/functions.sh + DEFAULT=/etc/default/eeepc-acpi-scripts + [ -e /usr/share/eeepc-acpi-scripts/functions.sh ] + runlevel + BACKLIGHT=/sys/class/backlight/eeepc/brightness + [ -e /etc/default/eeepc-acpi-scripts ] + . /etc/default/eeepc-acpi-scripts + ENABLE_OSD=no + OSD_FONT=DejaVuSans 36 + ENABLE_OSD_BRIGHTNESS=no + SOUND_LABEL= + SOUND_SWITCH= + SOUND_SWITCH_EXCLUSIVE= + SOUND_PREFER_MASTER=yes + SOUND_VOLUME_STEP=1.5 + DETAILED_SOUND_INFO=no + VGA_ON=--auto + LVDS_OFF=--off + SUSPEND_METHOD=pm-suspend + SUSPEND_OPTIONS=--quirk-s3-bios + LOCK_SCREEN_ON_SUSPEND=yes + LID_CLOSE_ACTION= + BLUETOOTH_FALLBACK_TO_HCITOOL=yes + SOFTBTN1_ACTION=handle_blank_screen + SOFTBTN2_ACTION=NONE + SOFTBTN3_ACTION=handle_camera_toggle + SOFTBTN4_ACTION=handle_bluetooth_toggle + SOFTBTNSHE_ACTION=handle_shengine + FnF_TOUCHPAD=handle_touchpad_toggle + FnF_RESCHANGE=NONE + FnF_BACKLIGHTOFF=handle_blank_screen + FnF_VGATOGGLE=handle_vga_toggle + FnF_TASKMGR=NONE + FnF_MUTE=handle_mute_toggle + FnF_VOLUMEDOWN=handle_volume_down + FnF_VOLUMEUP=handle_volume_up + PWR_CLOCK_AC= + PWR_CLOCK_BATTERY= + . /usr/share/eeepc-acpi-scripts/functions.sh + have_dev_rfkill + [ -c /dev/rfkill ] + . /etc/acpi/lib/notify.sh + code=00000039 + test x. = x- + echo 0x00000039 + value=0x00000039 + acpi= + acpiwrite= + ACPITEST=/lib/init/rw/eeepc-acpi-scripts.acpi-ignore + test -f /lib/init/rw/eeepc-acpi-scripts.acpi-ignore + read acpi + test . = - + cat /sys/class/dmi/id/product_name + [ != NONE ] + handle_shengine + . /etc/acpi/lib/shengine.sh + SHENGINE_CTL=/sys/devices/platform/eeepc/cpufv + cat /sys/devices/platform/eeepc/cpufv + SHENGINE_LIMIT=0x302 + SHENGINE_LIMIT=3 + SHENGINE_CONFIG=/var/lib/eeepc-acpi-scripts/cpufv + cat /var/lib/eeepc-acpi-scripts/cpufv + SHENGINE_SETTING=manual + SHENGINE_SETTING=manual + handle_shengine + [ -e /sys/devices/platform/eeepc/cpufv ] + [ = ] + cycle_shengine + [ -e /sys/devices/platform/eeepc/cpufv ] + get_shengine + [ manual = auto -a = ] + [ -e /sys/devices/platform/eeepc/cpufv ] + cat /sys/devices/platform/eeepc/cpufv + echo 2 + SHENGINE_CLOCKING=2 + [ manual = auto ] + SHENGINE_CLOCKING=0 + [ 0 = 0 ] + cat /sys/class/power_supply/AC0/online + [ 1 != 0 ] + SHENGINE_CLOCKING= + SHENGINE_DEFAULT=0 + [ :+1 ] + SHENGINE_SETTING=auto + echo auto + echo 0 + [ != ] + get_shengine + [ auto = auto -a = ] + echo 255 + notify super_hybrid_engine S. H. Engine: Automatic + CATEGORY=super_hybrid_engine + MSG=S. H. Engine: Automatic + [ -n -o ( -n -a != fast ) ] + echo S. H. Engine: Automatic S. H. Engine: Automatic + [ ! -S /tmp/.X11-unix/X0 ] + [ xno = xno ] + return + test = ret: 0 acpi-listen gives the correct value. I'll keep an eye on that and I'll post the required data when and if the problem will occur again! Ciao and thanks. 2010/1/25 Darren Salt <[email protected]> > I demand that Domenico Cufalo may or may not have written... > > > As in subject, when I start the PC with Bluetooth turned off, it seems > > impossible manage she-engine. > > That's... strange. Some debugging will be needed: > > * Run "acpi_listen", press the S.H.E. button and report what events are > reported for it. It would be worth knowing whether/how toggling Bluetooth > affects this. > > * Run (as root) > sh -x /etc/acpi/actions/hotkey.sh . . 00000039 .; echo 'ret:' $? > > -- > | Darren Salt | linux at youmustbejoking | nr. Ashington, | Doon > | using Debian GNU/Linux | or ds ,demon,co,uk | Northumberland | Army > | + Vermin Media = Internet Surveillance Partner of HM Govt. ENCRYPT! > > You do not have mail. > -- Prof. Domenico Cufalo Via Contessa Matilde 14 56123 Pisa (PI) Tel.: 3475207746
_______________________________________________ Debian-eeepc-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/debian-eeepc-devel
