Bug#453861: #453861: acpi-support: Fn+F2 (wireless on/off) stopped working with upgrade to 0.103-4 on ASUS A6J

2008-03-18 Thread Arnout Boelens 
On Monday 17 March 2008, Bart Samwel wrote:
 Arnout Boelens wrote:
  On Sunday 16 March 2008, Bart Samwel wrote:
  Hi Carl, Arnout,
 
  I've fixed the double quotes in asus-wireless.sh, like Carl suggested
  earlier (there were two cases) and I'll leave it at that for the next
  upload. There were more changes in this area in the mean time, and I'd
  like to analyse this problem again after you guys upgrade to 0.105-1. I
  can't guarantee that any changes I make now based on your suggestions will
  fix anything.
 
  Just for now, I would like to make the following things absolutely sure:
  both of you, if you uninstall *and purge* the acpi-support package, does
  the wireless hotkey still work? In that case the kernel handles it, and
  acpi-support shouldn't handle it. I would also love it if you could try
  the same thing with a 2.6.24 kernel -- lots of things are happening in
  this area.
  
  I just purged acpi-support and the wireless hotkey stopped working. However
  bluetooth is still switched on and off. This is for kernel 2.6.24.
 
 Interesting: you report that it doesn't work, while Carl reports that it 
 does. Could both of you report on your exact hardware, i.e., laptop type 
 and wireless hardware? I'm also interested in the contents of the files 
 /var/lib/acpi-support/system-*. And perhaps the output of lsmod, to 
 see if there is anything that can explain the difference.

Here you go:

Laptop: Asus A6J
Wireless: Intel WM3945ABG

$ cat /var/lib/acpi-support/system-*
ASUSTeK Computer Inc.
A6J
1.0

# lsmod
Module  Size  Used by
fglrx1481388  18
rfcomm 36784  4
l2cap  22880  9 rfcomm
ppdev   8804  0
parport_pc 33668  0
lp 11076  0
parport34280  3 ppdev,parport_pc,lp
ipv6  240772  26
acpi_cpufreq9260  0
cpufreq_userspace   4260  0
cpufreq_stats   5184  0
cpufreq_powersave   1856  0
cpufreq_ondemand8492  0
freq_table  4512  3 acpi_cpufreq,cpufreq_stats,cpufreq_ondemand
cpufreq_conservative 7560  0
xt_tcpudp   3136  101
ipt_TOS 2240  51
xt_TCPMSS   4384  4
ipt_LOG 5952  39
ipt_REJECT  4480  0
iptable_nat 6916  0
nf_nat 18316  1 iptable_nat
iptable_mangle  2784  1
xt_multiport3040  0
xt_state2464  16
xt_limit2656  42
xt_conntrack2784  0
nf_conntrack_ftp8896  0
nf_conntrack_ipv4  17352  18 iptable_nat
nf_conntrack   62240  6
iptable_nat,nf_nat,xt_state,xt_conntrack,nf_conntrack_ftp,nf_conntrack_ipv4
sha256_generic 11040  0
aes_i586   33376  4
aes_generic27776  0
geode_aes   6024  0
cbc 4416  1
dm_crypt   13220  1
dm_snapshot16964  0
dm_mirror  21600  0
dm_mod 55812  5 dm_crypt,dm_snapshot,dm_mirror
coretemp7168  0
uvcvideo   52104  0
compat_ioctl32  1408  1 uvcvideo
videodev   26304  1 uvcvideo
v4l1_compat12580  2 uvcvideo,videodev
v4l2_common16608  2 uvcvideo,videodev
fuse   45204  0
iptable_filter  2976  1
ip_tables  13188  3 iptable_nat,iptable_mangle,iptable_filter
x_tables   14244  11
xt_tcpudp,ipt_TOS,xt_TCPMSS,ipt_LOG,ipt_REJECT,iptable_nat,xt_multiport,xt_state,xt_limit,xt_conntrack,ip_tables
mmc_block  13316  0
sr_mod 16708  0
firewire_sbp2  14252  0
ide_generic 1280  0 [permanent]
hci_usb14780  2
bluetooth  53220  7 rfcomm,l2cap,hci_usb
arc42016  2
ecb 3552  2
blkcipher   6724  3 geode_aes,cbc,ecb
snd_hda_intel 275264  4
snd_pcm_oss38272  0
snd_mixer_oss  15296  1 snd_pcm_oss
joydev 11360  0
snd_pcm71780  3 snd_hda_intel,snd_pcm_oss
snd_seq_dummy   3780  0
snd_seq_oss29472  0
snd_seq_midi8160  0
snd_rawmidi22624  1 snd_seq_midi
snd_seq_midi_event  6976  2 snd_seq_oss,snd_seq_midi
iwl394584712  0
snd_seq46544  6
snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
pcmcia 37036  0
firmware_class  9312  2 iwl3945,pcmcia
sdhci  16836  0
snd_timer  21092  3 snd_pcm,snd_seq
snd_seq_device  7820  5
snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
mac80211  114380  1 iwl3945
video  18672  0
firewire_ohci  17760  0
firewire_core  39232  2 firewire_sbp2,firewire_ohci
battery13572  0
asus_laptop17432  0
ehci_hcd   32524  0
uhci_hcd   23376  0
snd

Bug#453861: #453861: acpi-support: Fn+F2 (wireless on/off) stopped working with upgrade to 0.103-4 on ASUS A6J

2008-03-18 Thread Bart Samwel 

Arnout Boelens wrote:

On Sunday 16 March 2008, Bart Samwel wrote:

Hi Carl, Arnout,

I've fixed the double quotes in asus-wireless.sh, like Carl suggested
earlier (there were two cases) and I'll leave it at that for the next
upload. There were more changes in this area in the mean time, and I'd
like to analyse this problem again after you guys upgrade to 0.105-1. I
can't guarantee that any changes I make now based on your suggestions will
fix anything.

Just for now, I would like to make the following things absolutely sure:
both of you, if you uninstall *and purge* the acpi-support package, does
the wireless hotkey still work? In that case the kernel handles it, and
acpi-support shouldn't handle it. I would also love it if you could try
the same thing with a 2.6.24 kernel -- lots of things are happening in
this area.


I just purged acpi-support and the wireless hotkey stopped working. However
bluetooth is still switched on and off. This is for kernel 2.6.24.


Interesting: you report that it doesn't work, while Carl reports that it 
does. Could both of you report on your exact hardware, i.e., laptop type 
and wireless hardware? I'm also interested in the contents of the files 
/var/lib/acpi-support/system-*. And perhaps the output of lsmod, to 
see if there is anything that can explain the difference.


Cheers,
Bart


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

Bug#453861: #453861: acpi-support: Fn+F2 (wireless on/off) stopped working with upgrade to 0.103-4 on ASUS A6J

2008-03-18 Thread Bart Samwel 

Hi Carl,

Castanier Carl wrote:

Hi, sorry is long to answer.


No problem, I'm in no particular hurry. :-)


A6JC


Difference between the systems: A6J versus A6JC.

[kernel 2.6.24]

dmesg give me

iwl3945: Detected Intel PRO/Wireless 3945ABG Network Connection
ACPI: Battery Slot [BAT0] (battery present)
input: Video Bus as /class/input/input6
ACPI: Video Device [VGA] (multi-head: yes  rom: no  post: no)
iwl3945: iwlwifi-3945-1.ucode firmware file req failed: Reason -2
iwl3945: Could not read microcode: -2
ACPI: PCI interrupt for device :03:00.0 disabled
iwl3945: probe of :03:00.0 failed with error -2

at boot time. ifconfig don't show my wifi interface.
ls -ld /sys/class/net/*/wireless/ respond nothing in that case...
apt-get install firmware-iwlwifi

and wifi interface is reconize. hurray!


That's how it's supposed to work, yeah. :-)


I have also this error when apcid start.
modprobe -v asus_acpi
FATAL: Error inserting asus_acpi 
(/lib/modules/2.6.24-1-686/kernel/drivers/acpi/asus_acpi.ko): No such device

My acpi is not reconize as an asus one. Onto 2.6.22 I had this message :
Asus Laptop ACPI Extras version 0.30
  unsupported model A6JC, trying default values
  send /proc/acpi/dsdt to the developers
I have send /proc/acpi/dsdt to the developers 2 years ago But 
default values works fine.


In fact, your acpi is recognized as asus. Your 2.6.24 kernel lsmod shows 
module asus_laptop, which apparently is the new asus ACPI support in 
the kernel.


What the hell !!! I don't have nay more /proc/acpi/asus/mled. More over 
I found only /sys/class/leds/asus\:mail. Only led for email is avaliable 
(very usefull feature).


Do you have:

/sys/devices/platform/asus-laptop/wlan

? That's the wireless LED. I think they've done some things to break 
this and/or fix this up in the upstream acpi-support package (version 
0.106), I will try to keep an eye on this.


Other thing is, wlan0_rename interface appears in ifconfig -a when 
iwl3945 is loaded but udev set it to eth2 by reading mac address. But, 
eth2 is now an unkown interface (with wrong mac address ie to many 
digits) and wlan0_rename is ethernet interface. Very strange...
Changing wireless configuration from eth2 to wlan0_rename does nothing. 
No way to have working network!
adding a file in modprobe.d with line alias eth2 iwl3945 does nothing. 
Wireless interface still remain wlan0_rename.


This is very strange. I have no clue how to fix that. :-/

Conclusion : I have to learn how use iwl3945 first. Probably there are a 
way to set power on this interface ; rf_kill file don't exist anymore 
and I can't find power switch and/or how to use ower/wakeup.


Do you have /sys/class/net/wlan0/operstate? If you do, that's the power 
control!


Cheers,
Bart


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

Bug#453861: #453861: acpi-support: Fn+F2 (wireless on/off) stopped working with upgrade to 0.103-4 on ASUS A6J

2008-03-18 Thread Bart Samwel 


For the record, here's the complete info from Carl.

--Bart

Castanier Carl wrote:



2008/3/17, Bart Samwel [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]:

Arnout Boelens wrote:
  On Sunday 16 March 2008, Bart Samwel wrote:
  Hi Carl, Arnout,
 
  I've fixed the double quotes in asus-wireless.sh, like Carl
suggested
  earlier (there were two cases) and I'll leave it at that for the
next
  upload. There were more changes in this area in the mean time,
and I'd
  like to analyse this problem again after you guys upgrade to
0.105-1. I
  can't guarantee that any changes I make now based on your
suggestions will
  fix anything.
 
  Just for now, I would like to make the following things
absolutely sure:
  both of you, if you uninstall *and purge* the acpi-support
package, does
  the wireless hotkey still work? In that case the kernel handles
it, and
  acpi-support shouldn't handle it. I would also love it if you
could try
  the same thing with a 2.6.24 kernel -- lots of things are
happening in
  this area.
 
  I just purged acpi-support and the wireless hotkey stopped
working. However
  bluetooth is still switched on and off. This is for kernel 2.6.24.

Interesting: you report that it doesn't work, while Carl reports that it
does. Could both of you report on your exact hardware, i.e., laptop type
and wireless hardware? I'm also interested in the contents of the files
/var/lib/acpi-support/system-*. And perhaps the output of lsmod, to
see if there is anything that can explain the difference.

Cheers,

Bart


Hi, sorry is long to answer.

ASUS A6000 series : A6J
Network controller: Intel Corporation PRO/Wireless 3945ABG Network 
Connection (rev 02)


WITH KERNEL 2.6.22

cat /var/lib/acpi-support/system-*
ASUSTeK Computer Inc.
A6JC
1.0

lsmod
Module  Size  Used by
appletalk  33696  2
ax25   5  2
ipx26084  2
p8023   2080  1 ipx
nvidia   7816224  26
snd_rtctimer3520  1
ppdev   8676  0
parport_pc 33828  0
lp 10980  0
parport33928  3 ppdev,parport_pc,lp
video  16456  0
asus_acpi  16348  0
sbs18568  0
dock9632  0
button  7920  0
battery 9988  0
container   4512  0
ac  5188  0
arc42016  2
ecb 3520  2
blkcipher   6116  1 ecb
ieee80211_crypt_wep 5056  1
ipv6  236964  35
dm_snapshot16900  0
dm_mirror  20928  0
dm_mod 52160  2 dm_snapshot,dm_mirror
coretemp7136  0
eeprom  7024  0
i2c_core   23552  2 nvidia,eeprom
videodev   26656  0
v4l2_common16672  1 videodev
v4l1_compat12580  1 videodev
fuse   41908  3
snd_virmidi 5120  0
snd_seq_virmidi 6848  1 snd_virmidi
snd_seq_dummy   3748  0
snd_seq_oss29408  0
snd_seq_midi8160  0
snd_rawmidi22624  2 snd_seq_virmidi,snd_seq_midi
snd_seq_midi_event  6880  3 snd_seq_virmidi,snd_seq_oss,snd_seq_midi
snd_seq46320  8 
snd_seq_virmidi,snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_seq_device  7692  5 
snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq

sr_mod 16516  0
firewire_sbp2  12100  0
ide_generic 1216  0 [permanent]
joydev  9568  0
snd_hda_intel 239160  2
snd_pcm_oss39200  1
snd_mixer_oss  15424  1 snd_pcm_oss
pcmcia 37100  0
ipw3945   192740  1
snd_pcm72324  2 snd_hda_intel,snd_pcm_oss
snd_timer  21028  3 snd_rtctimer,snd_seq,snd_pcm
sdhci  16524  0
pcspkr  3104  0
ieee80211  31656  1 ipw3945
ieee80211_crypt 5792  2 ieee80211_crypt_wep,ieee80211
psmouse36016  0
snd48324  18 
snd_virmidi,snd_seq_virmidi,snd_seq_oss,snd_rawmidi,snd_seq,snd_seq_device,snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer

soundcore   7520  2 snd
mmc_core   26116  1 sdhci
iTCO_wdt9924  0
rtc12856  1 snd_rtctimer
serio_raw   6692  0
intel_agp  23188  0
firmware_class  9504  2 pcmcia,ipw3945
snd_page_alloc 10056  2 snd_hda_intel,snd_pcm
yenta_socket   24844  1
rsrc_nonstatic 11968  1 yenta_socket
pcmcia_core37108  3 pcmcia,yenta_socket,rsrc_nonstatic
agpgart31880  2 nvidia,intel_agp
tsdev   7968  0
evdev   9312  6
ext3  121288

Bug#453861: #453861: acpi-support: Fn+F2 (wireless on/off) stopped working with upgrade to 0.103-4 on ASUS A6J

2008-03-17 Thread Arnout Boelens 
On Sunday 16 March 2008, Bart Samwel wrote:
 Hi Carl, Arnout,
 
 I've fixed the double quotes in asus-wireless.sh, like Carl suggested
 earlier (there were two cases) and I'll leave it at that for the next
 upload. There were more changes in this area in the mean time, and I'd
 like to analyse this problem again after you guys upgrade to 0.105-1. I
 can't guarantee that any changes I make now based on your suggestions will
 fix anything.
 
 Just for now, I would like to make the following things absolutely sure:
 both of you, if you uninstall *and purge* the acpi-support package, does
 the wireless hotkey still work? In that case the kernel handles it, and
 acpi-support shouldn't handle it. I would also love it if you could try
 the same thing with a 2.6.24 kernel -- lots of things are happening in
 this area.

I just purged acpi-support and the wireless hotkey stopped working. However
bluetooth is still switched on and off. This is for kernel 2.6.24.

Cheers,

Arnout

 Cheers,
 Bart



smime.p7s
Description: S/MIME cryptographic signature

Bug#453861: #453861: acpi-support: Fn+F2 (wireless on/off) stopped working with upgrade to 0.103-4 on ASUS A6J

2008-03-16 Thread Bart Samwel 
Hi Carl, Arnout,

I've fixed the double quotes in asus-wireless.sh, like Carl suggested
earlier (there were two cases) and I'll leave it at that for the next
upload. There were more changes in this area in the mean time, and I'd
like to analyse this problem again after you guys upgrade to 0.105-1. I
can't guarantee that any changes I make now based on your suggestions will
fix anything.

Just for now, I would like to make the following things absolutely sure:
both of you, if you uninstall *and purge* the acpi-support package, does
the wireless hotkey still work? In that case the kernel handles it, and
acpi-support shouldn't handle it. I would also love it if you could try
the same thing with a 2.6.24 kernel -- lots of things are happening in
this area.

Cheers,
Bart

Bug#453861: #453861: acpi-support: Fn+F2 (wireless on/off) stopped working with upgrade to 0.103-4 on ASUS A6J

2008-03-10 Thread Arnout Boelens 
On Sunday 09 March 2008, Bart Samwel wrote:
 Hi Arnout,
 
 In addition to the information I requested below, could you also send me
 the contents of the files in /var/lib/acpi-support/*? Those help me
 identify your specific system in case I need to make an exception.
 
 Dank,
 Bart

Hi Bart,

I made a couple of changes to my system (upgrade to acpi-support 0.103-5, using
kernel module asus_laptop instead of asus-acpi, and wireless driver iwl3945
instead of ip33945) and switching the wireless on and off is almost working
again. That is, the wireless is switched on and off according to
/var/log/daemon.log, but the wireless LED does not work at all. Is this an acpi
bug?

Thanks,

Arnout

 On Sun, March 2, 2008 21:23, Bart Samwel wrote:
  Hi Arnout,
 
  I believe your problems with wireless and acpi-support 0.103-4 are due to
  the fixes done for debian bug #410952. Could you confirm that if you
  remove
 
  /etc/acpi/events/asus-wireless-on
  /etc/acpi/events/asus-wireless-off
 
  that things then work again?
 
  I would appreciate it if you could send me some extra info by following
  the following two procedures:
 
  1. Run the command acpi_listen when wireless is ON.
  2. Press your wireless key.
  3. Stop acpi_listen and send me the output.
 
  and
 
  1. Run the command acpi_listen when wireless is OFF.
  2. Press your wireless key.
  3. Stop acpi_listen and send me the output.
 
  This will tell me exactly how your laptop buttons behave, and I can make
  sure that we support that.
 
  Cheers,
  Bart
 
 
 
 
 
 





smime.p7s
Description: S/MIME cryptographic signature

Bug#453861: #453861: acpi-support: Fn+F2 (wireless on/off) stopped working with upgrade to 0.103-4 on ASUS A6J

2008-03-10 Thread Bart Samwel 

Arnout Boelens wrote:

On Sunday 09 March 2008, Bart Samwel wrote:

Hi Arnout,

In addition to the information I requested below, could you also send me
the contents of the files in /var/lib/acpi-support/*? Those help me
identify your specific system in case I need to make an exception.

Dank,
Bart


Hi Bart,

I made a couple of changes to my system (upgrade to acpi-support 0.103-5, using
kernel module asus_laptop instead of asus-acpi, and wireless driver iwl3945
instead of ip33945) and switching the wireless on and off is almost working
again. That is, the wireless is switched on and off according to
/var/log/daemon.log, but the wireless LED does not work at all. Is this an acpi
bug?


Hi Arnout,

I actually have the same problem since I switched from ipw3945 to 
iwl3945. No clue what causes it (although I think it's a problem in the 
driver), and no clue if I can control it. I don't see any obvious way of 
doing it. For instance, there's no obvious /sys/class/* or /proc/acpi 
entries for the LED. :-( Not a very serious bug (I mean, at least it 
*works*), but it's worth looking at. I'll see if I can take this up with 
the iwl3945 guys.


Cheers,
Bart



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

Bug#453861: #453861: acpi-support: Fn+F2 (wireless on/off) stopped working with upgrade to 0.103-4 on ASUS A6J

2008-03-09 Thread Bart Samwel 
Hi Arnout,

In addition to the information I requested below, could you also send me
the contents of the files in /var/lib/acpi-support/*? Those help me
identify your specific system in case I need to make an exception.

Dank,
Bart

On Sun, March 2, 2008 21:23, Bart Samwel wrote:
 Hi Arnout,

 I believe your problems with wireless and acpi-support 0.103-4 are due to
 the fixes done for debian bug #410952. Could you confirm that if you
 remove

 /etc/acpi/events/asus-wireless-on
 /etc/acpi/events/asus-wireless-off

 that things then work again?

 I would appreciate it if you could send me some extra info by following
 the following two procedures:

 1. Run the command acpi_listen when wireless is ON.
 2. Press your wireless key.
 3. Stop acpi_listen and send me the output.

 and

 1. Run the command acpi_listen when wireless is OFF.
 2. Press your wireless key.
 3. Stop acpi_listen and send me the output.

 This will tell me exactly how your laptop buttons behave, and I can make
 sure that we support that.

 Cheers,
 Bart

Bug#453861: #453861: acpi-support: Fn+F2 (wireless on/off) stopped working with upgrade to 0.103-4 on ASUS A6J

2008-03-02 Thread Bart Samwel 
Hi Arnout,

I believe your problems with wireless and acpi-support 0.103-4 are due to
the fixes done for debian bug #410952. Could you confirm that if you
remove

/etc/acpi/events/asus-wireless-on
/etc/acpi/events/asus-wireless-off

that things then work again?

I would appreciate it if you could send me some extra info by following
the following two procedures:

1. Run the command acpi_listen when wireless is ON.
2. Press your wireless key.
3. Stop acpi_listen and send me the output.

and

1. Run the command acpi_listen when wireless is OFF.
2. Press your wireless key.
3. Stop acpi_listen and send me the output.

This will tell me exactly how your laptop buttons behave, and I can make
sure that we support that.

Cheers,
Bart