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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 3 Feb 2012 13:49:49 +0000
From:	Andres Cimmarusti <acimmarusti@...il.com>
To:	"James M. Leddy" <james.leddy@...onical.com>
Cc:	linux-bluetooth@...r.kernel.org, linux-kernel@...r.kernel.org,
	Jonathan Nieder <jrnieder@...il.com>, 641749@...s.debian.org,
	info@...uxcertified.com
Subject: Re: firmware loading failure for AR3011 (0cf3:3000 or 0cf3:3005 ?)

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.

Cheers,

Andres

View attachment "dmesg_2012-02-02_wheezy.txt" of type "text/plain" (50459 bytes)