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] [day] [month] [year] [list]

Message-ID: <CAH=dYrFs+Ty2XxWvv6y-OMi6stT-tYR7nL20+2fyQLV3RgseKQ@mail.gmail.com>
Date:	Sun, 12 Feb 2012 12:44:50 -0500
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 ?)

I believe I have finally narrowed down the problem. It lies in the
'libmtp-runtime' package with the command 'mtp-probe' (only present in
wheezy or newer).

I'm not sure what this is doing to my system, but when the package
mentioned is installed, it "messes" up my atheros bluetooth device so
that the kernel/udev cannot load the firmware into it.

As soon as I uninstalled this package and thus caused the boot process
to throw some errors about missing mtp-probe command, my bluetooth
module was correctly loaded and the led turned on.

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

I guess this snapshot that I tested earlier didn't have that package installed

I found out about this completely by chance. For whatever reason, on
my second upgrade to wheezy 'apt-get dist-upgrade' didn't pull
'libmtp-runtime' and my bluetooth module just worked.

I tried to get the bootlog messages so I can send this info, but even
with bootlogd enabled these messages happen too early on the boot
process to be logged in /var/log/boot.

I feel this is not necessarily a kernel bug anymore (all kernels
tested work fine 3.0.x, 3.1.x, 3.2.x and even 3.3.0-rc3). But the
experts will know better.

This is definitely progress!

Cheers

Andres

PS: please forward the info to other bug reports I don't have access
to, like Red Hat / Fedora and Ubuntu. Additional testing is needed.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/