I'm suffering from this, running 10.10:
[1484047.788648] bcm203x_complete: URB failed with status -84
[1484047.793058] usb 8-2: USB disconnect, address 9
[1484051.928027] usb 8-2: new full speed USB device using uhci_hcd and address
10
--
You received this bug notification because you are a
Wait, wait... so the fix is to take a 2.6.18 driver which the maintainer
has deliberately changed and slam it into 2.6.20/22? Seriously? Was this
problem reported upstream? (Google suggests 'no'.)
--
bcm203x firmware will not load
https://bugs.launchpad.net/bugs/85247
You received this bug
For the record, someone else did report it upstream, and the author
confirms that this fix is the wrong fix, but did not apparently propose
a different one or even really acknowledge the bug:
http://fixunix.com/kernel/336629-2-6-24-bcm203x-bluetooth-dongle-does-
not-work.html
--
bcm203x
And Debian has the same bug report as well, but also didn't report it to
bugzilla.kernel.org:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=458719
--
bcm203x firmware will not load
https://bugs.launchpad.net/bugs/85247
You received this bug notification because you are a member of Ubuntu
Just hit this on a feitsy machine. Is the bcm203x fix too intrusive
stick the update in the next driver/security-fix round up?
--
bcm203x firmware will not load
https://bugs.launchpad.net/bugs/85247
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
** Changed in: linux-source-2.6.20 (Ubuntu)
Assignee: Kyle McMartin (kyle) = (unassigned)
Status: Incomplete = Won't Fix
--
bcm203x firmware will not load
https://bugs.launchpad.net/bugs/85247
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
linux-source-2.6.22 (2.6.22-11.32) gutsy; urgency=low
[Amit Kucheria]
* Build system: Allow custom builds to comprise multiple patches
* Move UME to a Custom build and add first setup of thermal framework
[Ben Collins]
* ubuntu: Enable CONFIG_BLK_DEV_IO_TRACE
* bcm203x: Fix
Gutsy commit e553585d897d2b63c362f2ccb261bbdeb6ff2f47
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: Ubuntu Kernel Team = Ben Collins
Status: Triaged = Fix Committed
--
bcm203x firmware will not load
https://bugs.launchpad.net/bugs/85247
You received this bug notification
** Changed in: linux-source-2.6.22 (Ubuntu)
Importance: Undecided = Medium
Assignee: (unassigned) = Ubuntu Kernel Team
Status: New = Triaged
--
bcm203x firmware will not load
https://bugs.launchpad.net/bugs/85247
You received this bug notification because you are a member of
The problem was originally discovered in Feisty (2.6.20), but Gutsy
(2.6.22) is also affected.
** Also affects: linux-source-2.6.22 (Ubuntu)
Importance: Undecided
Status: New
--
bcm203x firmware will not load
https://bugs.launchpad.net/bugs/85247
You received this bug notification
I just upgraded to gutsy (tribe4) running 2.6.22 and found that the
problem still exists. The only thing different that I noticed is the
dmesg failure error code
[19681.456000] bcm203x_complete: URB failed with status -108
I assume that my original patch still works (about to try the patch
now),
I followed the instructions in the bug report and the instructions at
http://www.howtoforge.com/kernel_compilation_ubuntu . I haven't tried
the older module with the latest kernel from 7.04.
On Wed, 2007-06-13 at 18:34 +, kjsteuer wrote:
How do I backport the driver? I am having the same
How do I backport the driver? I am having the same issue.
--
bcm203x firmware will not load
https://bugs.launchpad.net/bugs/85247
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Success! .. I backported drivers/bluetooth/bcm203x.c from 2.6.20 to
2.6.18 and recompiled the module within the 2.6.20 source. My BT-120
device is back online in fiesty!
I'll attach a diff here of what I did, it's very straight forward.
I still need to test to see if 2.6.21-rc2 or later already
I've had this same problem for a couple weeks now. After a little
digging I believe that the likely culprit was introduced in 2.6.19. From
that kernel's changelog:
commit 3f5306927d800306ebba542438cfdf1a1c418376
Author: Marcel Holtmann
Date: Sun Oct 15 17:31:19 2006 +0200
[Bluetooth]
I'm experiencing the same problem with this dongle. It worked fine with
Edgy but I can't get it to work with Feisty.
If the firmware wouldn't have been found the message would be:
bcm203x_probe: Mini driver request failed
bcm203x: probe of 1-1:1.0 failed with error -5
But instead it is
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Confirmed = Needs Info
--
bcm203x firmware will not load
https://launchpad.net/bugs/85247
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Hi!
Can you please try copying them to /lib/firmware/`uname -r`/ and let me
know if that fixes the problem? We should probably be supplying a
seperately looked at directly for user firmware... Sigh.
Cheers,
Kyle
** Changed in: linux-source-2.6.20 (Ubuntu)
Assignee: (unassigned) = Kyle
Thanks for taking the time to report this bug. Unfortunately we can't
fix it, because your description didn't include enough information.
Please include the following additional information, if you have not already
done so (please pay attention to lspci's additional options), as required by
the
Umm... thanks for the cut n' paste response but I attached dmesg output.
The kernel is the latest update for feisty on amd64: 2.6.20-8
This is a USB device having problems so lspci is not going to be very
useful for debugging but if you want it you got it:
00:00.0 Host bridge: ATI Technologies
** Attachment added: dmesg output
http://librarian.launchpad.net/6439657/dmesg.out
--
bcm203x firmware will not load
https://launchpad.net/bugs/85247
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
->
[Bug 85247] Re: bcm203x firmware will not load
ubuntu-bugs
-- Thread --
-- Date --
<!--
google_ad_client = "pub-7266757337600734";
google_alternate_ad_url = "http://www.mail-
22 matches
Mail list logo
