On Thu, 2009-10-08 at 03:55 +0100, Philip Ashmore wrote: > Ben Hutchings wrote: > > [...] > > > > You're using the Atheros proprietary driver (aka madwifi), which we do > > not have source for and so cannot debug. I suspect that this may be > > responsible for at least some of the crashes. Please can you remove > > this and try using the ath5k driver instead? > > > > Ben. > > > I tried switching to ath5k but had no luck. > I followed > http://wiki.debian.org/ath5k > and also > http://wiki.debian.org/WiFi/HowToUse > but unfortunately as far as KDE 3.5.10 is concerned the "HowToUse" > documentation is incomplete. > TODo: Complete knetworkmanager procedure. > > I tried "iwlist wlan0 scan" but it failed to list any networks. > > I tried "ifconfig wlan0 up" - X > > I tried "iwconfig wlan0 up" - X > > I could tell it failed by the entry in /var/log/messages - > "ADDRCONF(NETDEV_UP): wlan0: link is not ready". > I didn't and don't have an entry in /etc/network/interfaces for wlan0 or ath0. > > I tried "/etc/init.d/network-manager restart" - X > > I tried "/etc/init.d/network-manager-dispatcher restart" - X > > I switched back to madwifi (ath0) and it works fine. [...]
Except for this bug, presumably. I've reassigned this to madwifi and opened a separate bug (#550649) for the lack of support for your hardware in ath5k. Ben. -- Ben Hutchings DNRC Motto: I can please only one person per day. Today is not your day. Tomorrow isn't looking good either.
signature.asc
Description: This is a digitally signed message part
