Package: acpi-support
Version: 0.109-1
Followup-For: Bug #482349

Hello there,

a follow up on my problems on the ASUS V2S. Today I have bit more time to
try to chase the problem, so I reinstall acpi-support (isn't debian
great? :)) and playied with it.

At boot time, after the gdm comes up, the wireless goes off, and I find
this in the log

May 22 14:15:39 obi NetworkManager: <info>  Wireless now enabled by radio 
killswitch 
May 22 14:15:42 obi acpid: client connected from 3645[0:0] 
May 22 14:15:45 obi NetworkManager: <info>  Wireless now disabled by radio 
kills witch 
May 22 14:15:45 obi NetworkManager: <info>  Deactivating device wlan0. 

so it's an interaction with NetworkManager (notice I don't have any
problem without acpi-support, that's why I submitted the bug here). Note
#2 the kill switch (a mechanical switch that turns off both bluetooth and
wireless) is never touched, and it's not the problem here. At this time
the wlan led is off, but bluetooth is on.

After that, if I do

echo 1 > /sys/devices/platform/asus-laptop/wlan

the led for wireless comes on, *and* the wireless become functional:

May 22 14:17:40 obi NetworkManager: <info>  Wireless now enabled by radio 
killswitch 

and more log till it connects.

Pressing Fn+F2 (which should cycle to turn off wlan, bluetooth in all
posible combination) turn off both wlan and bluetooth and pressing it
multiple time have no consequences (the led and the services are
effectively off).

Doing 

echo 1 > /sys/devices/platform/asus-laptop/bluetooth

brings bluetooth back up, but doing 

echo 1 > /sys/devices/platform/asus-laptop/wlan

brings the wlan led up, but not the wireless itself. And from now on
wireless is off (I haven't found yet a way to re-enable it without
rebooting). Doing 

cat /sys/module/iwl4965/drivers/pci\:iwl4965/0000\:05\:00.0/rf_kill

brings back 2 and I cannot make it 0 anylonger (that is the wireless
believes to have the HW switch on, which is not true).

This is the extent of my experiments: the old version of acpi-support
worked (or at least I didn't notice any problem with it) but this one
brings the dead on boot problem (which it looks like I can overcome) and
the everything dead after Fn+F2 which is not fixable.

thanks
graziano





-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.25 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages acpi-support depends on:
ii  acpi-support-base             0.109-1    scripts for handling base ACPI eve
ii  acpid                         1.0.6-8    Utilities for using ACPI power man
ii  dmidecode                     2.9-1      Dump Desktop Management Interface 
ii  finger                        0.17-12    user information lookup program
ii  hdparm                        8.6-1      tune hard disk parameters for high
ii  laptop-detect                 0.13.6     attempt to detect a laptop
ii  libc6                         2.7-11     GNU C Library: Shared libraries
ii  lsb-base                      3.2-12     Linux Standard Base 3.2 init scrip
hi  nvclock                       0.8b2-1    Allows you to overclock your nVidi
ii  powermgmt-base                1.30       Common utils and configs for power
ii  vbetool                       1.0-3      run real-mode video BIOS code to a
ii  x11-xserver-utils             7.3+2      X server utilities

Versions of packages acpi-support recommends:
ii  radeontool                    1.5-5      utility to control ATI Radeon back

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to