[Debian-eeepc-devel] Problems with Linux 2.6.26 and Madwifi
dmn at debian.org
Thu Aug 21 05:29:00 UTC 2008
-=| Paul Menzel, Tue, Aug 19, 2008 at 11:26:41PM +0200 |=-
> Dear Damyan,
> today I had access to the concerning EeePC 701 4G again.
> Am Montag, den 18.08.2008, 09:52 +0200 schrieb Paul Menzel:
> > Am Montag, den 18.08.2008, 08:32 +0300 schrieb Damyan Ivanov:
> > > -=| Paul Menzel, Sun, Aug 17, 2008 at 10:32:40PM +0200 |=-
> > > > Any ideas. I will appreciate any hints.
> > >
> > > run " sh -x /etc/acpi/actions/wireless.sh on" and see what fails
> > > exactly.
> > I will be able to try that tomorrow.
> I had to run it as root and did
> $ sudo sh -x /etc/acpi/actions/wireless.sh on
> + wlan_control=/sys/devices/platform/eeepc/wlan
> + [ -e /sys/devices/platform/eeepc/wlan ]
> + cat /sys/devices/platform/eeepc/wlan
> + [ 0 = 0 ]
> + modprobe -r pciehp
> + modprobe pciehp pciehp_force=1
> + echo 1
> + modprobe ath_pci
> + sleep 1
> + ifconfig ath0 up
> ath0: ERROR while getting interface flags: Kein passendes Gerät gefunden (translation: No suitable device found.)
> + exec /etc/acpi/actions/wireless.sh off
> In my dmesg output (relevant parts attached at the end) I saw that udev
> was naming the device wifi0. I substituted the respective lines
> $ sudo vim /etc/acpi/actions/wireless.sh
you mean - replacing "ath0" with "wifi0"? This shouldn't be done. In
my understanding there should be both wifi0 and ath0 interfaces, wifi0
being a "control interface" and ath0 being used as an ordinary network
> > > So far it seems that the wlan is enabled, but the 'ifconfig'
> > > call fails for some reason and therefore the wlan is disabled
> > > again.
> > Ok. I do not know if it matters, but I installed and want to use wicd
> > for managing wlan.
> So you were right. It looks like since 2.6.26 the devices are named
> differently. Or does it depend on udev?
Loooking at the dmesg output you gave, it seems to me that the ath5k
module is not blacklisted, causing for ath_pci to fail to properly
create ath0 or something like that. Does ath5k appear in lsmod output?
> > > Also, did you update initrd's? That's mandatory after changing files
> > > under /etc/modprobe.d like blacklisting a module or adding options to
> > > a module.
> > I think I did not. I will do it tomorrow.
> Sorry, I forgot to look into this. But it looks like this did not
It certainly matters if you blacklist ath5k as it will still be loaded
during boot until the initrd is updated.
> $ dmesg # Sorry, somehow not everything was saved (I used screen),
> so just the end.
> [ 1123.853073] ieee80211_unref_node: NULL ieee80211_node *
> [ 1123.853073] Pid: 0, comm: swapper Tainted: P 2.6.26-1-686 #1
> [ 1123.853073] [<e05a1c2d>] ieee80211_input+0x14b9/0x14d1 [wlan]
> [ 1123.853073] [<e05b641d>] ieee80211_input_monitor+0xf9/0x629 [wlan]
> [ 1123.853073] [<e05a1cc0>] ieee80211_input_all+0x7b/0x9d [wlan]
> [ 1123.853073] [<e05e2540>] ath_rx_tasklet+0x631/0x8c9 [ath_pci]
> [ 1123.853073] [<c0129a7b>] __mod_timer+0x99/0xa3
> [ 1123.853073] [<c010f975>] __setup_APIC_LVTT+0x70/0x8d
> [ 1123.853073] [<c0135ff0>] getnstimeofday+0x37/0xbc
> [ 1123.853073] [<c012687f>] tasklet_action+0x68/0xd0
> [ 1123.853073] [<c0126431>] __do_softirq+0x66/0xd3
> [ 1123.853073] [<c01264e3>] do_softirq+0x45/0x53
> [ 1123.853073] [<c012679a>] irq_exit+0x35/0x67
> [ 1123.853073] [<c0105f4f>] do_IRQ+0x52/0x63
> [ 1123.853073] [<c01042b7>] common_interrupt+0x23/0x28
> [ 1123.853073] [<c01300d8>] param_sysfs_setup+0x20/0xc8
> [ 1123.853073] [<e003a29b>] acpi_idle_enter_simple+0x196/0x203 [processor]
> [ 1123.853073] [<e0039eb1>] acpi_idle_enter_bm+0xc3/0x317 [processor]
> [ 1123.853073] [<c0246e89>] cpuidle_idle_call+0x5b/0x86
> [ 1123.853073] [<c0246e2e>] cpuidle_idle_call+0x0/0x86
> [ 1123.853073] [<c01025ce>] cpu_idle+0xab/0xcb
> [ 1123.853073] =======================
Looks like a stacktrace so there is certainly something wrong
dam JabberID: dam at jabber.minus273.org
More information about the Debian-eeepc-devel