Re: USB.Bluetooth not recognized at boot-time
From: Martin Gerken (m_gerken_at_yahoo.com)
Date: 10/30/05
- Next message: Enrique Perez-Terron: "Re: USB.Bluetooth not recognized at boot-time"
- Previous message: stu: "Is reiserfs slower to mount / on bootup?"
- In reply to: Enrique Perez-Terron: "Re: USB.Bluetooth not recognized at boot-time"
- Next in thread: Enrique Perez-Terron: "Re: USB.Bluetooth not recognized at boot-time"
- Reply: Enrique Perez-Terron: "Re: USB.Bluetooth not recognized at boot-time"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sun, 30 Oct 2005 17:35:12 +0100
On Sun, 30 Oct 2005 16:01:35 +0100, "Enrique Perez-Terron"
<enrio@online.no> wrote:
>>>>>> my new super-budged-made-in-china Bluetooth-Stick works fine - but it is
>>>>>> only recognized when I plug it into USB when the system is running. It
>>>>>> is not recognized when it is plugged in at boot-time.
>>>>>> (Debian Sarge & Bluez used)
>> I found some hint here:
>> http://sourceforge.net/mailarchive/message.php?msg_id=9106268
>> Frankly, I don't know how to apply the mentioned fix - and as the hint
>> is pretty old and I have used apt-get to get the latest bluez-utils I'm
>> not even shure if it helps.
>
>What kernel are you running? The patch in the link is already in my
>kernel sources, both 2.6.12 and 2.6.13 have it.
Debian 2.6.8-2-386
(I'm about to compile the latest 2.6.14 but I'm quite afraid to break
somethink)
>But I don't know yet if this is what makes it work once you plug the
>thing out and back in, versus not work at all. The context of the
>patch is to add those three lines (with pluses in the margin) to a list
>called "blacklist_ids". This list is treated especially in the probe
>routine, but I have not yet digged into the details.
Okay, I understand. I've just installed the latest bluez-libs and
bluez-utils from bluez.org but still no progress.
>Something that looks confusing here is that you have the bluetooth
>module loaded even when it does not work. Do you have any idea about
>what ntriggers the loading of that module? Can you find something related
>in dmesg? If you do, it would be nice to see some of what happens before
>and after, to get an idea of the context that triggers the loading.
my dmesg (relevant parts):
usbcore: registered new driver usbfs
usbcore: registered new driver hub
USB Universal Host Controller Interface driver v2.2
ACPI: PCI interrupt 0000:00:11.2[D] -> GSI 3 (level, low) -> IRQ 3
uhci_hcd 0000:00:11.2: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller
uhci_hcd 0000:00:11.2: irq 3, io base 0000d400
uhci_hcd 0000:00:11.2: new USB bus registered, assigned bus number 1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
ACPI: PCI interrupt 0000:00:11.3[D] -> GSI 3 (level, low) -> IRQ 3
uhci_hcd 0000:00:11.3: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (#2)
uhci_hcd 0000:00:11.3: irq 3, io base 0000d800
uhci_hcd 0000:00:11.3: new USB bus registered, assigned bus number 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
usb 1-2: new full speed USB device using address 2
usb 1-2: device not accepting address 2, error -71
usb 1-2: new full speed USB device using address 3
usb 1-2: device not accepting address 3, error -71
[...]
Bluetooth: Core ver 2.6
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP ver 2.3
Bluetooth: L2CAP socket layer initialized
Bluetooth: RFCOMM ver 1.3
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
ra0: no IPv6 routers present
uhci_hcd 0000:00:11.2: remove, state 1
usb usb1: USB disconnect, address 1
uhci_hcd 0000:00:11.2: USB bus 1 deregistered
uhci_hcd 0000:00:11.3: remove, state 1
usb usb2: USB disconnect, address 1
uhci_hcd 0000:00:11.3: USB bus 2 deregistered
usbcore: deregistering driver usbfs
usbcore: deregistering driver hub
pciehp: acpi_pciehprm:\_SB_.PCI0 evaluate _BBN fail=0x5
pciehp: acpi_pciehprm:get_device PCI ROOT HID fail=0x5
shpchp: acpi_shpchprm:\_SB_.PCI0 evaluate _BBN fail=0x5
shpchp: acpi_shpchprm:get_device PCI ROOT HID fail=0x5
usbcore: registered new driver usbfs
usbcore: registered new driver hub
USB Universal Host Controller Interface driver v2.2
ACPI: PCI interrupt 0000:00:11.2[D] -> GSI 3 (level, low) -> IRQ 3
uhci_hcd 0000:00:11.2: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller
uhci_hcd 0000:00:11.2: irq 3, io base 0000d400
uhci_hcd 0000:00:11.2: new USB bus registered, assigned bus number 1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
ACPI: PCI interrupt 0000:00:11.3[D] -> GSI 3 (level, low) -> IRQ 3
uhci_hcd 0000:00:11.3: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (#2)
uhci_hcd 0000:00:11.3: irq 3, io base 0000d800
uhci_hcd 0000:00:11.3: new USB bus registered, assigned bus number 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
usb 1-2: new full speed USB device using address 2
usb 1-2: device not accepting address 2, error -71
usb 1-2: new full speed USB device using address 3
usb 1-2: device not accepting address 3, error -71
There is some error message, strange!
>What happens if you do "modprobe hci_usb" after booting with the stick
>installed, without taking it out & back in?
Does not help.
Neither does /etc/init.d/hotplug restart
cu, Martin
-- Ubi bene ibi Colonia! ROT13 for email: znegva.trexra@jro.qr
- Next message: Enrique Perez-Terron: "Re: USB.Bluetooth not recognized at boot-time"
- Previous message: stu: "Is reiserfs slower to mount / on bootup?"
- In reply to: Enrique Perez-Terron: "Re: USB.Bluetooth not recognized at boot-time"
- Next in thread: Enrique Perez-Terron: "Re: USB.Bluetooth not recognized at boot-time"
- Reply: Enrique Perez-Terron: "Re: USB.Bluetooth not recognized at boot-time"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
