User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.4) Gecko/2008111217 Fedora/3.0.4-1.fc10 Firefox/3.0.4 Today my ath9k wifi chipset on my Asus M50VM laptop is no longer detected by any network components. Instead I get the following in my dmesg: ath9k: 0.1 ath_pci: software IOTLB in use, aborting Since the release of Fedora 10 is so close, this seems to me to be a major bug. Reproducible: Always
Not as major as the disk corruption it is meant to avoid... :-) FWIW, there are now patches upstream for fixing that issue. So maybe F10's anti-ath9k hack can disappear before too long. Unfortunately, I think release procedures are such that it is too late to get those patches into F10's default install kernel. I didn't put that hack in, but I suppose I'll grab this bug and make sure the hack disappears once the appropriate patches are available in Fedora kernels.
(In reply to comment #2) > > Today my ath9k wifi chipset on my Asus M50VM laptop is no longer detected by > any network components. Instead I get the following in my dmesg: > Do you have 4GB of memory or more installed?
Yes, this x86_64-based laptop has 4 GB of memory.
(In reply to comment #3) > Yes, this x86_64-based laptop has 4 GB of memory. You can work around this problem by adding "mem=3G" to the kernel boot options in grub.conf (on the line that starts with "kernel")
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
The test kernels here have patches intended to address this issue: http://koji.fedoraproject.org/koji/buildinfo?buildID=72916 Please give them a try and post the results here...thanks!
I have the same problem and tried to test that kernel-2.6.27.7-135.fc10, however, there was a dependency problem with the kernel-firmware package. I searched for kernel-firmware-2.6.27.7-135.fc10, but couldn't find it anywhere.
You may want to look closer -- that package is available under the "noarch" part of the RPMs... :-)
Works for me, thanks!