Thread (7 messages) 7 messages, 3 authors, 2012-02-12

Re: firmware loading failure for AR3011 (0cf3:3000 or 0cf3:3005 ?)

From: Andres Cimmarusti <hidden>
Date: 2012-02-10 05:28:26
Also in: lkml

Inexplicably yesterday's (and the day before) Debian testing snapshot
seems to have the problem fixed!

I tested kernel 3.2.x and 3.1.x. udev still is at version 175.

I'm completely ignorant to what change in Debian testing led to the
fixing of this problem. I guess I should have tested everyday, for
every round of updates to testing, but I lacked the time.

I'm attaching a dmesg, though it shows nothing of interest AFAIK.

I hope this issue doesn't come back to haunt me. I'll upgrade to
wheezy on this machine soon so I can monitor everything more closely
instead of relying on live images.
I finally installed wheezy by default on the laptop... it ended up
being rather hard...
Anyways the problem is back. I don't know what change in the Usb
images I tested days ago may have resulted in a fix.

I've tested the most recent Debian kernel -> basically 3.2.5 and also 3.3.0-rc3
Both throw the same error. I'm attaching dmesg from 3.3.0-rc3, but
there's absolutely no new information.
Should I enable the debugging symbols to test if there's more output?
my build had them disabled, otherwise the kernel image was huge.

Andres

Attachments

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help