Export to GitHub

aceracpi - issue #4

0.3 worked with 2.6.15-1, 0.6 does not work with 2.6.20-16


Posted on Jul 8, 2007 by Quick Rabbit

What steps will reproduce the problem? 1. I had the 0.3 version working for months with several kernels. The last one working on my computer is vmlinuz-2.6.15-27-amd64-k8. 2. I have updated the kernel (upgraded to Ubuntu Feisty). Now it uses vmlinuz-2.6.20-16-generic. 3. Network hardware is not found, despite the same script used: modprobe acer_acpi modprobe ndiswrapper echo "enabled: 1" >/proc/acpi/acer/wireless [... iwconfig *] 4. $ dmesg says: acer_acpi: Acer Laptop ACPI Extras version 0.6 acer_acpi: Detected ACER AMW0 interface ndiswrapper version 1.38 loaded (preempt=no,smp=yes

It used to say: acer_acpi: Acer Laptop ACPI Extras version 0.3 ndiswrapper version 1.8 loaded (preempt=yes,smp=yes) ndiswrapper (load_pe_images:571): fixing KI_USER_SHARED_DATA address in the driver ndiswrapper: driver bcmwl5 (Broadcom,02/11/2005, 3.100.64.0) loaded ACPI: PCI Interrupt 0000:06:05.0[A] -> GSI 21 (level, low) -> IRQ 177 ndiswrapper: using irq 177 wlan0: vendor: '' wlan0: ndiswrapper ethernet device 00:0e:9b:c4:b6:94 using driver bcmwl5, 14E4:4318.5.conf wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK acer_acpi: Wireless value 1 acer_acpi: Wireless value 1

I am using version 0.6, with:

uname -a

Linux aspirant 2.6.20-16-generic #2 SMP Thu Jun 7 19:00:28 UTC 2007 x86_64 GNU/Linux

I'll try to use the 0.4 version.

Comment #1

Posted on Jul 8, 2007 by Grumpy Bird

Try: echo 1 >/proc/acpi/acer/wireless

Comment #2

Posted on Jul 8, 2007 by Grumpy Bird

(No comment was entered for this change.)

Comment #3

Posted on Jul 8, 2007 by Quick Wombat

Hi (I am the same as person as 061007),

It does not help. It says:

echo 1 >/proc/acpi/acer/wireless

-su: echo: bład zapisu: Invalid argument

(where "błąd zapisu" means "write error")

It used to work with "enabled: 1" and 'sending' in the 'enabled: 1' causes a reaction by the module (dmesg says 'acer_acpi: Wireless value 1'). So I think the problem is somewhere else.

Comment #4

Posted on Jul 8, 2007 by Grumpy Bird

Not printing "acer_acpi: Wireless value 1" anymore to dmesg is not a bug - but in re-reading your bug, I don't understand - what do you mean by "Network hardware is not found, despite the same script used:"? acer_acpi has nothing to do with finding or not finding hardware, it just switches the wireless on. I presume you updated/ reinstalled ndiswrapper as well after updating your kernel/ distribution?

Comment #5

Posted on Jul 11, 2007 by Happy Bear

I'm running acer_acpi 0.6 on the 64bit version of Feisty (and have run older versions on the 32bit and 64bit versions of Feisty). I've noticed that you need to copy acer_acpi.o manually to /lib/modules//kernel/drivers/char/ IN ADDITION TO the normal make install command in order for it to work properly.

-David C. Uhrig

Comment #6

Posted on Jul 16, 2007 by Grumpy Bird

The install problem is a Bash "bug" (I've tested with an Ubuntu live CD) - the bug being that *buntu has upgraded to bash 3.2, whereas Slackware (and Slamd64, an unofficial AMD64 port, which I use) reverted to 3.1 because of the new Bash breaking lots of scripts.

Attached is a patch to the Makefile which should fix the install problem (I've added back in the old 2.4 kernel test - if this patch works, then Make shouldn't error out on the "No support for 2.4 kernels" - if it does, then I need to go back to the drawing board).

Attachments

Comment #7

Posted on Jul 16, 2007 by Grumpy Bird

And if I attached the patch this time, that would also help. :-)

Attachments

Comment #8

Posted on Jul 16, 2007 by Grumpy Bird

My first Makefile patch was broken - please try this one (against either 0.6.1 or 0.6.2)

Attachments

Comment #9

Posted on Jul 27, 2007 by Grumpy Bird

Marking as invalid - the original bug is not due to acer_acpi (no wireless drivers installed on new kernel - either ndiswrapper or bcm43xx need to be installed and set up properly). If you can confirm this is not the case, please re-open this bug.

Second part of this bug (installer) has moved to bug #6, so any comments along those lines should be directed there.

Status: Invalid

Labels:
Type-Defect Priority-Medium