This time, no initial timeout occurs with hciconfig:īD Address: 00:1F:81:00:01:1C ACL MTU: 1021:4 SCO MTU: 180:1 I have just tested this again with experimental kernel version 2.6.38-rc6: That was last week, using a 2.6.35.6-desktop-1mnb (Mandriva) kernel.Īs far as I am concerned, my problem is fixed, but the kernel could probably address this situation and handle the rejection more nicely. We fixed the remote firmware and now that it returns 0, I am able to disconnect and reconnect at will. The only way to reconnect was to reset the remote device. I do not know _why_, but with this condition, I could establish an rfcomm link once and disconnect, but could never connect again. It turns out that the remote device I was trying to connect to was not fully compliant with v1.2, and rejected as 'not understood' the request about extended features instead of returning 0 (meaning not supporting any extended feature).
Cambridge silicon radio bluetooth software Patch#
I have asked Quel Qun to send the hcidump &dmesg infoĬould you apply the below debug patch and send the broken dmesg?Īfter giving up on bluetooth for 2 years, I decided last week to try once more to fix my problem. > hm, I don't think that much changed between 2.6.23 and 2.6.24 in > seems to work fine otherwise (I have a custom app linked with libusb > Summary: Cambridge Silicon Radio USB bt dongle support I have asked Quel Qun to send the hcidump &dmesg info > And afaik most or all of the recent bluetooth fixes were in 2.6.25-rc3.
> hm, I don't think that much changed between 2.6.23 and 2.6.24 in bluetooh, > I selected bluetooth for component, but that might be a usb issue. > dongle is still unusable, usually giving a 'connection reset by peer' > A new patch ( ) now prevents the crash, > HCI Ver: 1.1 (0x1) HCI Rev: 0xbc LMP Ver: 1.1 (0x1) LMP Subver: Hm, I don't think that much changed between 2.6.23 and 2.6.24 in bluetooh,Īnd afaik most or all of the recent bluetooth fixes were in 2.6.25-rc3. > seems to work fine otherwise (I have a custom app linked with libusb that > dongle is still unusable, usually giving a 'connection reset by peer' error > A new patch ( ) now prevents the crash, but > Since 2.6.24, the kernel locked the machine when I tried to use this > Manufacturer: Cambridge Silicon Radio (10) > HCI Ver: 1.1 (0x1) HCI Rev: 0xbc LMP Ver: 1.1 (0x1) LMP Subver: 0xbc > Hardware Environment: Dell Dimension, 1 P4 w/ HT. > AssignedTo: ReportedBy: Latest working kernel version: > Summary: Cambridge Silicon Radio USB bt dongle support broken USB itself seems to work fine otherwise (I have a custom app linked with libusb that uses bulk I/O). I selected bluetooth for component, but that might be a usb issue. Since 2.6.24, the kernel locked the machine when I tried to use this bluetooth USB dongle.Ī new patch ( ) now prevents the crash, but the dongle is still unusable, usually giving a 'connection reset by peer' error Manufacturer: Cambridge Silicon Radio (10) HCI Ver: 1.1 (0x1) HCI Rev: 0xbc LMP Ver: 1.1 (0x1) LMP Subver: 0xbc Hardware Environment: Dell Dimension, 1 P4 w/ HT.
0 kommentar(er)
