One of them was an AR, not sure what the other was. Or you just want to try and use the latest driver. In its unmodified form, it doesn’t help. Recovering is logistically problematic. It is not a hardware problem. So these devices will just work out of the box.
|Date Added:||16 July 2013|
|File Size:||65.6 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
I can also confirm what others have reported. I see at least one of the two patches already in 4.
Qualcomm Atheros – WikiDevi
In my experience which might be totaly wrong A newer version of the restricted kernel package will be installed over those modules. Remove the following package if installed: If not, I will.
Browse Requests Reports Product Dashboard. Comment 2 Ldap Tester Attached scsi generic sg1 type 5 Dec 18 Hauppauge modelrev C, serial Dec 18 Comment 53 Jarod Wilson Until this is fixed, I’ll stick to linux-image Other bug subscribers Subscribe someone else. I agree about priority. But anyway your method probably is the safest one.
Needs Expansion This article is incomplete, and needs to be expanded. More data on my system and the actual Oops message are attached there.
Attached scsi disk sda Dec 18 Getting cpuindex for acpiid 0x1 Dec 18 Maybe one of the other posters can do the bisect. Atheroz got a laptop with a nic driven by alx, but it has no problems to speak of, so I can really only regression-test, if I can ever get a custom built kernel to actually boot — currently tripping over a grub2 double-free whenever I try to boot a kernel I built with patches added which are based on the ones in the upstream bug with some modifications.
After it, the boot process freezes, I have to hit Ctrl-Alt-Del to reboot. It’s most probably caused by setup of Jumbo frames.
I’ll check to see if thats the case by reinstalling my restricted kernel package and see if wireless still works, if it does I am wrong if it ain’t I am right. Damien Raude-Morvan drazzib on This was considered to atheeos more stable than the new madwifi-ng at the time of release.
So these devices will just work out of the box. Symbols match kernel version 2.
Alan Pater alan-pater wrote on If I boot back into the 4. I just found mention of a madwifi-tools package.
1. Driver Information
On my system, it takes about minutes before the oops. Ubuntu Release Specific Info 3.
Fedora 22 has now been rebased to 4. Add an attachment proposed patch, testcase, etc. Feel also free to contact me in PM if you think that’s more appropriate than discussing stuff here.