Timeline for Driver is sometimes loaded, sometimes not
Current License: CC BY-SA 3.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 25, 2014 at 21:07 | history | edited | Braiam |
edited tags
|
|
| Feb 6, 2013 at 14:09 | answer | added | Pedro | timeline score: 1 | |
| Jul 28, 2012 at 8:12 | comment | added | klapaucius | I doubt this is a software issue. Is there a difference if you cold or warm boot? | |
| Mar 12, 2012 at 20:05 | comment | added | J. M. Becker | @apoorv020: If you already found an answer, you should post it as an answer and then accept. Its best to accept out questions, rather than leave them perpetually open. | |
| Dec 15, 2011 at 20:24 | history | edited | Kevin | CC BY-SA 3.0 |
added 11 characters in body
|
| Aug 20, 2011 at 21:40 | history | tweeted | twitter.com/#!/StackUnix/status/105031461731696640 | ||
| Apr 19, 2011 at 16:32 | comment | added | apoorv020 | One related problem was that on Ubuntu 9.04, you have to 'activate' proprietary drivers (madwifi uses some proprietary binaries). But this is not made obvious. | |
| Apr 19, 2011 at 16:29 | comment | added | apoorv020 | I tested the driver on some similar hardware, and it seems that the problem is that the card is somewhat loose. | |
| Apr 19, 2011 at 10:55 | comment | added | Gilles 'SO- stop being evil' |
@apoorv020: So the driver is loaded anyway but sometimes doesn't like the hardware. Can we have the logs from a successful boots for comparison? On an unsuccessful boot, if you rmmod ath_pci; rmmod ath_hal; modprobe ath_pci, does it sometimes work?
|
|
| Apr 19, 2011 at 8:13 | history | edited | apoorv020 | CC BY-SA 3.0 |
added 1275 characters in body
|
| Apr 19, 2011 at 7:11 | comment | added | Gilles 'SO- stop being evil' |
@apoorv020: Next time you boot and see the card as unclaimed, post all the lines concerning the card or the driver from /var/log/kern.log. Also try modprobe ath_pci and report any error message or line appearing in the kernel logs. One possible explanation is that there's a conflicting driver that claims the card but then doesn't work; if that's the issue and you find this name, you can blacklist it.
|
|
| Apr 19, 2011 at 6:14 | comment | added | apoorv020 | I mean the former, it changes after each boot. | |
| Apr 18, 2011 at 18:43 | comment | added | Gilles 'SO- stop being evil' |
Do you mean sometimes you boot and it's unclaimed and sometimes you boot and it's claimed, or do you mean it oscillates between claimed and unclaimed just like that? Do you see anything in the kernel logs (/var/log/kern.log) (post anything that you aren't sure is irrelevant)?
|
|
| Apr 18, 2011 at 16:47 | history | asked | apoorv020 | CC BY-SA 3.0 |