On Fri, 2011-09-16 at 09:55 -0400, Andres Cimmarusti wrote: [...] > If I turn it off and boot into Debian, then I have trouble. I think > this may be a bug in a recent kernel: > https://bugzilla.redhat.com/show_bug.cgi?id=702375 > > I guess this should be reassigned to the kernel then? Yes, I already did that. On Fri, 2011-09-16 at 16:52 -0400, Andres Cimmarusti wrote: > Hey, I just found more information > > >> This device is rather peculiar. I currently have a dual boot with > >> Ubuntu 11.04. In Ubuntu, using kernel 2.6.38 the device works > >> correctly as expected. The bluetooth LED turns on and everything. In > >> Debian, however, running either my vanilla kernel 3.0.4 or official > >> Debian kernel 3.0.0-1-amd64 leads to the same error at boot time. The > >> weird thing is that, sometimes when I restart Ubuntu and go into > >> Debian, the firmware loaded into the AR3011 does not get wiped out and > >> I get a clean boot with no errors using Debian. > > The reason why it works in Ubuntu with kernel 2.6.38 is because they > patched their kernel: > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/720949 > https://launchpadlibrarian.net/68723624/0002-UBUNTU-SAUCE-Revert-Bluetooth-Add-new-PID-for-Athero.patch But comment #9 there says that this revert patch didn't fix that bug. > I also saw this patch also in a Gentoo forum: > http://forums.gentoo.org/viewtopic-t-887112-view-previous.html?sid=46739f74e3419eb7efee8b0b1cb98ce0 > > Apparently there is an upstream bug report: > https://bugzilla.kernel.org/show_bug.cgi?id=27402 > But that is down right now, because kernel.org is down. > > Perhaps this patch could be applied to Debian's kernel? I am inclined to think that the Atheros developer making the original change probably knows better how to handle Atheros hardware than the Ubuntu developers do. The revert patch will probably break other devices, even if it makes yours work. Then later you wrote: > Actually this patch is already in 3.0.0 and above. My issue remains. No, this patch has not been applied upstream. > My specific device is: > > Bus 001 Device 003: ID 0cf3:3000 Atheros Communications, Inc. AR3011 But the patch that you're referring to does not appear to change the handling of devices with this device ID! Still, if you want to test it in Debian then use the attached patch for 3.0 and follow the instructions at <http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official>. Ben. -- Ben Hutchings If more than one person is responsible for a bug, no one is at fault.
From 9dc15ff86a8e9ca8e90f9b567210699b0b574e0d Mon Sep 17 00:00:00 2001
From: Ben Hutchings <ben@decadent.org.uk>
Date: Mon, 19 Sep 2011 03:01:26 +0100
Subject: [PATCH] Revert "Bluetooth: Add new PID for Atheros 3011"
This reverts commit be93112accb42c5586a459683d71975cc70673ca.
Conflicts:
drivers/bluetooth/ath3k.c
drivers/bluetooth/btusb.c
---
drivers/bluetooth/ath3k.c | 1 -
drivers/bluetooth/btusb.c | 1 -
2 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/drivers/bluetooth/ath3k.c b/drivers/bluetooth/ath3k.c
index 6bacef3..bfbb3db 100644
--- a/drivers/bluetooth/ath3k.c
+++ b/drivers/bluetooth/ath3k.c
@@ -61,7 +61,6 @@ static struct usb_device_id ath3k_table[] = {
{ USB_DEVICE(0x0CF3, 0x3000) },
/* Atheros AR3011 with sflash firmware*/
- { USB_DEVICE(0x0CF3, 0x3002) },
{ USB_DEVICE(0x13d3, 0x3304) },
/* Atheros AR9285 Malbec with sflash firmware */
diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
index c2de895..513d462 100644
--- a/drivers/bluetooth/btusb.c
+++ b/drivers/bluetooth/btusb.c
@@ -103,7 +103,6 @@ static struct usb_device_id blacklist_table[] = {
{ USB_DEVICE(0x0a5c, 0x2033), .driver_info = BTUSB_IGNORE },
/* Atheros 3011 with sflash firmware */
- { USB_DEVICE(0x0cf3, 0x3002), .driver_info = BTUSB_IGNORE },
{ USB_DEVICE(0x13d3, 0x3304), .driver_info = BTUSB_IGNORE },
/* Atheros AR9285 Malbec with sflash firmware */
--
1.7.5.4
Attachment:
signature.asc
Description: This is a digitally signed message part