Most recent kernel where this bug did not occur: Distribution: Opensuse10.2 Hardware Environment: Dell Precision M90 Notebook Software Environment: Opensuse10.2 & Vista 32Bit both installed Problem Description: please see at: https://bugzilla.novell.com/show_bug.cgi?id=278715 Steps to reproduce: boot notebook to linux, and bluetooth will not work. no bluetooth adapter found (because of wrong usb id). boot notebook to vista, then reboot to linux: bluetooth working! usb id is correct after this.
Reply-To: akpm@linux-foundation.org On Fri, 20 Jul 2007 00:05:56 -0700 (PDT) bugme-daemon@bugzilla.kernel.org wrote: > http://bugzilla.kernel.org/show_bug.cgi?id=8786 > > Summary: Dell 350 Bluetooth device (usb id 413c:8103) not found > Product: Networking > Version: 2.5 > KernelVersion: 2.6.18 > Platform: All > OS/Version: Linux > Tree: Mainline > Status: NEW > Severity: normal > Priority: P1 > Component: Wireless > AssignedTo: networking_wireless@kernel-bugs.osdl.org > ReportedBy: rainer.klier@gmx.at > > > Most recent kernel where this bug did not occur: > Distribution: Opensuse10.2 > Hardware Environment: Dell Precision M90 Notebook > Software Environment: Opensuse10.2 & Vista 32Bit both installed > Problem Description: please see at: > https://bugzilla.novell.com/show_bug.cgi?id=278715 > > Steps to reproduce: > boot notebook to linux, and bluetooth will not work. no bluetooth adapter > found > (because of wrong usb id). > boot notebook to vista, then reboot to linux: bluetooth working! usb id is > correct after this. > err, guys, is this a USB thing or a bluetooth thing or a wireless thing?
Check /proc/bus/usb/devices or lsusb if the Bluetooth dongle is really there. You might need some ACPI hacking to make it visible under Linux. All Bluetooth dongles should use a USB class identifier to assign the driver and so the USB vendor and product ids are not used at all. Get the content of /proc/bus/usb/devices and prove that this specific dongle is broken.
as described in https://bugzilla.novell.com/show_bug.cgi?id=278715. when started windows vista, and then rebooted to linux, lsusb shows the correct usb-id 413c:8103. but whenn computer switched on and booted to linux (WITHOUT booting vista before) the usb-id is wrongly set to 413c:8105. and because of that, the bluetooth adapter is not detected correctly. here ist the relevant part of /proc/bus/usb/devices when the device is detected correctly: T: Bus=05 Lev=02 Prnt=02 Port=03 Cnt=02 Dev#= 5 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=e0(unk. ) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=413c ProdID=8103 Rev=24.22 C:* #Ifs= 3 Cfg#= 1 Atr=e0 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=1ms E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb E: Ad=03(O) Atr=01(Isoc) MxPS= 0 Ivl=1ms E: Ad=83(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms I: If#= 1 Alt= 1 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb E: Ad=03(O) Atr=01(Isoc) MxPS= 9 Ivl=1ms E: Ad=83(I) Atr=01(Isoc) MxPS= 9 Ivl=1ms I: If#= 1 Alt= 2 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb E: Ad=03(O) Atr=01(Isoc) MxPS= 17 Ivl=1ms E: Ad=83(I) Atr=01(Isoc) MxPS= 17 Ivl=1ms I: If#= 1 Alt= 3 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb E: Ad=03(O) Atr=01(Isoc) MxPS= 25 Ivl=1ms E: Ad=83(I) Atr=01(Isoc) MxPS= 25 Ivl=1ms I: If#= 1 Alt= 4 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb E: Ad=03(O) Atr=01(Isoc) MxPS= 33 Ivl=1ms E: Ad=83(I) Atr=01(Isoc) MxPS= 33 Ivl=1ms I: If#= 1 Alt= 5 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb E: Ad=03(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms E: Ad=83(I) Atr=01(Isoc) MxPS= 49 Ivl=1ms I: If#= 2 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=00 Driver=(none)
That is not an argument. There is no wrongly set USB device id. Show me the content of /proc/bus/usb/devices when the device id 413c:8105 (not detected). What does "hciconfig hci0 revision" (as root) say when the adapter was detected.
"hciconfig hci0 revision": hci0: Type: USB BD Address: 00:1A:6B:11:9B:8B ACL MTU: 384:8 SCO MTU: 64:8 Build 2422 Chip version: BlueCore4-External Max key size: 56 bit SCO mapping: HCI
And the content of /proc/bus/usb/devices when it is not detected? I really do need that one to see if it is an HID proxy dongle. Since it is a CSR chip, you can run "bccmd buildname" (also as root) to see if it is special custom made firmware for Dell.
ok, content of /proc/bus/usb/devices when it is not detected is a little bit tricky, coz under vista i deinstalled the software which is responsible for that usb id mismatch (called "vista profile pack"). without this software bluetooth isn't working any more under vista, but it works under linux, coz the id remains 413c:8103, whereas it is 413c:8105 when this software is installed. at http://ubuntuforums.org/showthread.php?p=2308248 you can read this: "The bluetooth Vista driver actually loads a piece of firmware upgrade from CSR (the bluetooth chip manufacturer) that enables the "Vista profile pack" i.e. a set of utilities developed for the Microsoft Bluetooth stack and api. These utilities, among other things, are used to initialize the bluetooth chip in a way that allows a bluetooth mouse or keyboard to be enabled via the bios before the boot phase. Obviously the Microsoft bluetooth stack is aware of this kind of initialization while the bluez stack simply ignore it." and when "Vista profile pack" is not installed, the id is left untouched, and therefor works. here is the output of "bccmd buildname": Build name: cyt_8unified_fl_nofs_bt2.0_21_0508261422_encr56 2005-08-26
What is the problem with getting the /proc/bus/usb/devices content for the case when the device is not detected. That is actually your problem case. So when the adapter is not detected simply get that information. And the firmware in this dongle is nothing special. It is a standard Bluetooth 2.0 firmware from CSR. So it is likely that HID proxy is enabled. Call "bccmd psread" (as root) and see what PS keys are set.
the problem is, that i have to install the "vista profile pack" software first to have the problem situation again. right now i have worked around the problem by deinstalling the "vista profile pack" and downgrading the firmware to a version older than that which comes with "vista profile pack". with that workaround bluetooth is working under linux, but not under vista any more. the steps i did are the same which are described on: http://ubuntuforums.org/showthread.php?p=2308248 http://ubuntuforums.org/showthread.php?p=2464779 http://sourceforge.net/mailarchive/message.php?msg_name=46417C35.8010906%40a1.net i am not surprised that the firmware is nothing special. the firmware installed right now is a version older than the version which comes with "vista profile pack". it is a version which comes with latest windows xp bluetooth driver pack for that notebook. i downgraded to it with a tool called "dfu" which was also part of latest windows xp bluetooth driver pack. i did it like described in above links. and when "vista profile pack" is installed the firmware will be upgraded, and then the effect is, that it is not detected any more, if computer is switched on and booted to linux directly. it is only detected when vista is booted first. here is the output of "bccmd psread": // PSKEY_BDADDR &0001 = 0011 9b8b 006b 001a // PSKEY_MAX_ACLS &000d = 0005 // PSKEY_LC_POWER_TABLE &001e = 0900 ec00 1000 f000 1700 f400 2100 f800 2a00 fc00 3500 0000 3f00 0300 // PSKEY_LC_DEFAULT_TX_POWER &0021 = ffff // PSKEY_LC_COMBO_DISABLE_PIO_MASK &0028 = 0040 0000 0000 // PSKEY_LC_COMBO_PRIORITY_PIO_MASK &0029 = 0010 0000 // PSKEY_LC_COMBO_DOT11_CHANNEL_PIO_BASE &002a = 000d // PSKEY_LC_ENHANCED_POWER_TABLE &0031 = 0700 0000 3f00 4400 e700 0d00 0000 3f00 4600 eb00 1400 0000 3f00 4800 ef00 1c00 0000 3f00 4b00 f300 2400 0000 3f00 4f00 f700 2c00 0000 3f00 5200 fb00 3500 0000 3f00 5800 ff00 3f00 0000 3f00 6000 0300 // 0x00dc &00dc = 0044 0065 006c 006c 0020 0057 0069 0072 0065 006c 0065 0073 0073 0020 // 0x00dd &00dd = 0033 0035 0030 0020 0042 006c 0075 0065 0074 006f 006f 0074 0068 0020 // 0x00de &00de = 0049 006e 0074 0065 0072 006e 0061 006c 0020 0043 0061 0072 0064 // 0x00ee &00ee = 0029 // PSKEY_LOCAL_SUPPORTED_FEATURES &00ef = ffff fe9f f99b 8000 // PSKEY_PRIVATE_LINK_KEY_BD_ADDR0 &00fe = 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 // PSKEY_PRIVATE_LINK_KEY_BD_ADDR1 &00ff = 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 // PSKEY_DEVICE_NAME &0108 = 6544 6c6c 5720 7269 6c65 7365 2073 3533 2030 6c42 6575 6f74 746f 2068 6e49 6574 6e72 6c61 4320 7261 // PSKEY_DFUENC_VMAPP_PK_MODULUS_MSB &015e = fc72 e441 a587 1e70 6646 5617 989e 587f e467 ff8e 40f2 9a16 c383 14dd d4f5 3811 53a5 d670 89d9 dd4e b9c1 4f77 3d8f 9171 6523 9bf9 d97a c904 8881 5422 ed32 6aef // PSKEY_DFUENC_VMAPP_PK_MODULUS_LSB &015f = 303b 4c03 7eeb 945b cc1c 0d1f 2380 d1e0 d4a9 7d02 5cfb e581 d9f8 41e4 9fbb ce7b 1444 2ce7 3a0a 341e 16f4 5a9f c895 b749 e9e0 312c 1a56 6d68 d8ae 1ed5 1b58 6dc3 // PSKEY_DFUENC_VMAPP_PK_M_DASH &0160 = 1515 // PSKEY_DFUENC_VMAPP_PK_R2N_MSB &0161 = 9572 afc6 9011 3af4 2546 c9d4 2125 4c97 05cd 22d8 43c4 a2d3 e738 f0c5 ddb7 67fb b40d 9247 93a4 ea61 de80 26a7 22ef 2ef3 c26f 4b15 0719 9077 5993 015f dbcb c236 // PSKEY_DFUENC_VMAPP_PK_R2N_LSB &0162 = c030 52f8 ddbb 2eb1 7ca8 e299 2a0c 1759 eebd b13f d7d6 946e 3e23 6d8f d66a 8263 f1fb 4252 308a fe14 2d27 85b5 7e39 be81 c399 e4be f53b e464 5d68 c24c bc11 5687 // PSKEY_UART_BAUDRATE &01be = 01d8 // PSKEY_ANA_FTRIM &01f6 = 002b // PSKEY_HOST_INTERFACE &01f9 = 0002 // PSKEY_ANA_FREQ &01fe = 3e80 // PSKEY_RF_RESONANCE_TRIM &0254 = 333c // PSKEY_MODULE_SECURITY_CODE &025c = 0000 0000 0000 0000 0000 0000 0000 0000 // PSKEY_MOD_MANUF5 &0263 = 0001 // PSKEY_MOD_MANUF6 &0264 = 0055 // PSKEY_MOD_MANUF7 &0265 = 0005 // PSKEY_MOD_MANUF8 &0266 = 6332 0704 5035 3120 // PSKEY_MOD_MANUF9 &0267 = 0007 // PSKEY_USR0 &028a = 0002 // PSKEY_USR1 &028b = 0007 // PSKEY_USR2 &028c = 0001 // PSKEY_USR6 &0290 = 0000 // PSKEY_USR7 &0291 = 0008 0000 0001 0000 // PSKEY_USR8 &0292 = 0008 0000 0001 0000 // PSKEY_USR9 &0293 = 0000 // PSKEY_USR10 &0294 = 0000 // PSKEY_USR41 &02b3 = 0000 0000 0000 0000 0000 0000 0000 0000 // PSKEY_USB_VENDOR_ID &02be = 413c // PSKEY_USB_PRODUCT_ID &02bf = 8103 // PSKEY_USB_ATTRIBUTES &02c5 = 00e0 // PSKEY_USB_DFU_PRODUCT_ID &02cb = 8106 // PSKEY_USB_PIO_VBUS &02d1 = 0002 // PSKEY_INITIAL_BOOTMODE &03cd = 0000 // 0x04b1 &04b1 = 02bd 02bf 03cc 02d8 03c0 // 0x04f8 &04f8 = 0000 0000 0000 // 0x04f9 &04f9 = 8105 // 0x04fa &04fa = 0001 // 0x04fb &04fb = 0008 // 0x04fc &04fc = 0001 // 0x6002 &6002 = 0000 0000 0000 00ff
The boot mode is correctly set to HCI. From which firmware version is this output? Is the new one or the old one? You totally confused me now. However there seems to be some magic application running in the VM of the firmware. Maybe Dell put something on top of it. You can always sniff the USB traffic to find the magic sequence they used to switch the adapter into working mode.
ok here are the facts again, to clear things up: 1. there is a vista-driver-package called "vista profile pack". this pack also includes a new firmware. when this pack is installed, it also upgrades the firmware. this software was part of default vista installation on my notebook. it was installed when notbook was shipped. 2. when firmware is upgraded and "vista profile pack" is installed, then you have the problem that bluetooth under linux only works, when you first boot to vista, and then reboot to linux. when notebook is switched on, and booted to linux, bluetooth is not working. the reason for that problem/behaviour can be read in: http://ubuntuforums.org/showthread.php?p=2308248 http://ubuntuforums.org/showthread.php?p=2464779 http://sourceforge.net/mailarchive/message.php?msg_name=46417C35.8010906%40a1.net 3. to have a solution right now (a workaround) i followed the steps described in the links above. i deinstalled the "vista profile pack" and downgraded the firmaware. i did the downgrade with a windows xp package, where an older firmware was included. 4. so right now, i have bluetooth working, but not under vista any more, coz i removed "vista profile pack" and downgraded firmware. 5. all outputs i sent today were made with this working (downgraded) firmware. and because of that, i think, every output seems fine. 6. to give you results with non working firmware, i have to install "vista profile pack" and upgrade firmware again. i will do that asap. is the situatuion now more understandable?
Okay. I really need the output from the non-working version. That are the important things we have to look at.
ok, here is the relevant part of /proc/bus/usb/devices in the case, where it doesn't work and the id is wrong: T: Bus=01 Lev=02 Prnt=02 Port=03 Cnt=03 Dev#= 6 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=413c ProdID=8105 Rev=35.38 C:* #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=01 Driver=usbhid E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=1ms I: If#= 1 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=usbhid E: Ad=82(I) Atr=03(Int.) MxPS= 16 Ivl=1ms and here is the output in case where it is working: T: Bus=01 Lev=02 Prnt=02 Port=03 Cnt=02 Dev#= 5 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=e0(unk. ) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=413c ProdID=8103 Rev=24.22 C:* #Ifs= 3 Cfg#= 1 Atr=e0 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=1ms E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb E: Ad=03(O) Atr=01(Isoc) MxPS= 0 Ivl=1ms E: Ad=83(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms I: If#= 1 Alt= 1 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb E: Ad=03(O) Atr=01(Isoc) MxPS= 9 Ivl=1ms E: Ad=83(I) Atr=01(Isoc) MxPS= 9 Ivl=1ms I: If#= 1 Alt= 2 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb E: Ad=03(O) Atr=01(Isoc) MxPS= 17 Ivl=1ms E: Ad=83(I) Atr=01(Isoc) MxPS= 17 Ivl=1ms I: If#= 1 Alt= 3 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb E: Ad=03(O) Atr=01(Isoc) MxPS= 25 Ivl=1ms E: Ad=83(I) Atr=01(Isoc) MxPS= 25 Ivl=1ms I: If#= 1 Alt= 4 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb E: Ad=03(O) Atr=01(Isoc) MxPS= 33 Ivl=1ms E: Ad=83(I) Atr=01(Isoc) MxPS= 33 Ivl=1ms I: If#= 1 Alt= 5 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb E: Ad=03(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms E: Ad=83(I) Atr=01(Isoc) MxPS= 49 Ivl=1ms I: If#= 2 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=00 Driver=(none) it seems, that in case where it doesn't work, the system thinks it is an bluetooth-mouse/keyboard (Driver=usbhid). this seems understandable for me coz of explanation in http://ubuntuforums.org/showthread.php?p=2464779#7
I think you need to modify the hid2hci tool to include the VID:PID 413c:8105 to make it switch between HID and HCI mode.
but i am only a "customer". shouldn't the maintainer of hid2hci or, at least the distributor make these changes? but i will try to do it myself.
(In reply to comment #14) > I think you need to modify the hid2hci tool to include the VID:PID 413c:8105 > to > make it switch between HID and HCI mode. > i checked the bluez-utils-package in opensuse10.2 (wehere hid2hci belongs to) to find out the authors of the hid2hci tool. and guess who i found? if found Marcel Holtmann <marcel@holtmann.org>.... so marcel, as you are the maintainer of hid2hci. can you make these changes please?
I don't have this laptop for testing and so I can't do it. It is only a wild guess that this might solve your problems. If it does, then I will commit it to the upstream source.
I have this exact problem. My Dell D520 came with Vista and I installed Kubuntu 7.10 over it. Vista's now gone and I'm unable to downgrade the firmware in the lsusb reports: Bus 005 Device 004: ID 413c:8105 Dell Computer Corp. $ dmesg | grep '8105' [ 12.696000] input: HID 413c:8105 as /class/input/input2 [ 12.696000] input: USB HID v1.11 Keyboard [HID 413c:8105] on usb-0000:00:1d.7-2.2 [ 12.716000] input: HID 413c:8105 as /class/input/input4 [ 12.716000] input: USB HID v1.11 Mouse [HID 413c:8105] on usb-0000:00:1d.7-2.2 $ sudo hcitool dev Devices: $ ls /proc/bus/usb gives me nothing at all. I would be more than happy to test out a solution. Tom Johnson tjohnson@prtsoftware.com
Created attachment 14305 [details] output of strace -f hid2hci
hid2hci at #19 was the unpatched version: $ md5sum /usr/sbin/hid2hci 1cfa76dcee9c83e6e410bc7635665c9f /usr/sbin/hid2hci Relevant portions of /proc/bus/usb (non working Dell 350 Wireless): T: Bus=05 Lev=02 Prnt=02 Port=01 Cnt=01 Dev#= 4 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=413c ProdID=8105 Rev=35.38 C:* #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=01 Driver=usbhid E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=1ms I:* If#= 1 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=usbhid E: Ad=82(I) Atr=03(Int.) MxPS= 16 Ivl=1ms
as you can see @dell: http://support.euro.dell.com/support/downloads/download.aspx?c=at&l=de&s=gen&releaseid=R157674&SystemID=LATITUDE%20PRECISION%20M90&servicetag=&os=WW1&osl=ge&deviceid=7388&devlib=0&typecnt=0&vercnt=1&catid=-1&impid=-1&formatcnt=1&libid=5&fileid=210380 they have the same problem with customers who want to use windows xp on the m90 notebook after vista was installed first, because windows xp also doesn't detect the bluetooth chip correctly. they offer a downgrade patch so that bluetooth-firmware is not vista-only any more.