Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#15218 - ath5k and network manager stopped working after update
Attached to Project:
Arch Linux
Opened by Dan Gray (deggy) - Monday, 22 June 2009, 20:11 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 24 June 2009, 11:05 GMT
Opened by Dan Gray (deggy) - Monday, 22 June 2009, 20:11 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 24 June 2009, 11:05 GMT
|
DetailsI just updated my setup and my atheros wireless card has stopped working.
I can bring wlan0 up and down with ifconfig I can change settings with iwconfig But NetworkManager doesn't want to know. It can see the card, but no networks (and as far as I can see, using iwconfig and ifconfig the card never associates). I had a similar issue a while ago that was a HAL problem, but hal hasn't been updated here. Recent package upgrades are: [2009-06-19 09:38] upgraded cryptsetup (1.0.6-2 -> 1.0.6-3) [2009-06-19 09:38] upgraded filesystem (2009.01-1 -> 2009.01-2) [2009-06-19 09:38] upgraded flex (2.5.35-1 -> 2.5.35-3) [2009-06-19 09:38] upgraded klibc (1.5.15-2 -> 1.5.15-3) [2009-06-19 09:38] upgraded klibc-extras (2.5-3 -> 2.5-4) [2009-06-19 09:38] upgraded klibc-kbd (1.15.20080312-9 -> 1.15.20080312-10) [2009-06-19 09:38] upgraded klibc-module-init-tools (3.5-2 -> 3.8-1) [2009-06-19 09:38] upgraded klibc-udev (141-2 -> 141-3) [2009-06-19 09:38] upgraded udev (141-1 -> 141-3) [2009-06-19 09:38] upgraded mkinitcpio (0.5.24-1 -> 0.5.25-1) [2009-06-19 09:38] upgraded module-init-tools (3.5-1 -> 3.8-1) [2009-06-19 09:38] upgraded moon-lander (1.0-3 -> 1.0-3.1) [2009-06-19 09:38] upgraded pacman-mirrorlist (20090509-1 -> 20090616-1) [2009-06-19 09:38] upgraded tdb (3.3.4-1 -> 3.3.5-1) [2009-06-19 09:38] upgraded smbclient (3.3.4-1 -> 3.3.5-1) [2009-06-19 09:38] upgraded samba (3.3.4-1 -> 3.3.5-2) [2009-06-19 09:38] upgraded speex (1.2rc1-1 -> 1.2rc1-1.1) [2009-06-19 09:39] upgraded xz-utils (4.999.8beta-3 -> 4.999.8beta-3) [2009-06-21 17:22] upgraded findutils (4.4.1-2 -> 4.4.2-1) [2009-06-21 17:22] upgraded man-db (2.5.5-1 -> 2.5.5-2) [2009-06-21 17:22] upgraded sqlite3 (3.6.14.1-1 -> 3.6.15-1) [2009-06-21 17:22] upgraded tzdata (2009g-1 -> 2009j-1) [2009-06-21 17:22] upgraded wine (1.1.23-1 -> 1.1.24-1) [2009-06-22 21:02] upgraded lapack (3.2-2 -> 3.2.1-1) [2009-06-22 21:02] upgraded libdaemon (0.13-1 -> 0.13-2) [2009-06-22 21:02] upgraded libidn (1.14-1 -> 1.15-1) [2009-06-22 21:02] upgraded pidgin (2.5.6-1 -> 2.5.7-1) [2009-06-22 21:02] upgraded unrar (3.9.3-1 -> 3.9.4-1) Any ideas what could be causing my problem? Dan |
This task depends upon
Also downgraded mkinitcpio to 0.5.24-1 because of a dependecy issue.
Problem has gone away.
Believe this is a udev issue as mkinitcpio was not used between system boots.
[2009-06-19 09:38] upgraded module-init-tools (3.5-1 -> 3.8-1)
http://www.archlinux.org/news/450/
Did you read this?
FS#15219as a duplicate. Feel free to switch opened/closed status of these bugs.Read and actioned on upgrade of module-init-tools.
There are no lines within any of the modprobe config files refering to the atheros driver either. So I have a feeling that's not it (plus, I have not downgraded module-init-tools and with the udev downgrade my wireless card now work again).
I had a similar issue with hal a few months ago when we switched to the git tree, but that seems to have resolved itself.
For some reason hal and udev seem particularly fond of throwing up strange hardware issues like this from time to time, and I find them unpenetrable enough to make it hard to come up with an exact reason.
Dan
could they lead to this?
If udev is the source, you could try to load the modules by MODULES= to avoid autoloading.
With the latest udev, is the module actually loaded? Use lsmod to check
I Re-upgraded to udev 141-1 and mkinitcpio 0.5.25 yesterday and my wifi card stopped working again (iwconfig and ifconfig returned no errors, but scanning for AP and associating did not work), do I downgraded again.
I have just tried to re-upgrade to get some good debugging information for this report and this time eveything is fine.
So I am flumoxed, but this seems to have resolved itself. I really can't think where the problem in my configuration would have come from (and where it has gone to, I don't think I changed anytning else in the meantime).
What I did get when I upgraded this time was an initial failure because /etc/modprobe.d/framebuffer_blacklist.conf already existed. I manually removed the file and then the upgrade went through. I don't think that intelfb was ever loaded though, even when I was having issues.
I will monitor the system, but this seems to have resolved itself.
Thanks for all your help.
Can someone please close the bug report?