Bug#641749: ath3k_load_firmware: Can't change to loading configuration err
Hi Jonathan,
> I'd like to narrow down the difference even more. So, here are some
> ideas:
>
> 1. Can you reproduce this with a squeeze kernel? (I'm guessing it
> lacks support since it doesn't include commit
> v2.6.33-rc7~20^2~3^2~1, "Bluetooth: Add DFU driver for Atheros
> Bluetooth chipset AR3011", but it can't hurt to try.) If you can,
> please test with the same kernel package on squeeze and testing.
Squeeze's kernel (on squeeze) does not work. I tried that sometime
ago. I haven't tried it on top of wheezy, but I'm pretty sure it won't
work either.
> 2. Please test with v3.2-rc1 or later once it is available from
> experimental (or sooner, if you have time to build it from source).
> If you can reproduce it with that, everything else is moot, and we
> should try to get help from upstream by contacting
> linux-bluetooth@vger.kernel.org, cc-ing
> linux-kernel@vger.kernel.org (please cc me or this bug log when
> doing so so we can track it).
I can tell you that kernel 3.0.x and 3.1.x have no trouble with the
atheros firmware loading process (on top of Squeeze). I haven't tried
3.2.
> 3. Can you reproduce this on wheezy using a pristine upstream kernel?
> See [1] for instructions on building one.
At the moment I can't try this, because I don't have wheezy installed.
I used to, but it gave me so much trouble with this laptop that I had
go to Squeeze and use an upstream recent kernel.
All my tests ever since have been based on a debian live usb-key with
wheezy (I don't know how to tell live-build to boot the upstream
package, instead of the main). What I can do is get a wheezy image
with the 3.2 kernel from experimental.
> 4. Another thing to try would be downgrading just udev and libudev0
> to the versions in squeeze from wheezy.
I haven't tried downgrading. This could work. I will give this a shot
for my next debian-live image. As it turns out, the new udev 175
breaks live-boot, so it's not working right now (I was hoping
upgrading to 175 would solve the problem...). Hopefully downgrading
will solve both issues!
I will report back as soon as I get a chance
Andres
Reply to: