Tried exactly the version requested (v3.7-rc2-raring). It resulted unity failing to load properly (expected, because i was using fglrx driver which perhpas compile against my previous kernel).
Nevertheless, new kernel doesn't work. Without unity, I can still do 'hcitool scan' as root. No device is found by it. In order to try if 'hcitool scan' in general work with the new kernel, I put on a secondary external USB bluetooth adaptor, indending to try scan again with that adaptor. But it resulted bluetoothd segment fault right after USB device plugged in. I rebooted to the old kernel and did 'hcitool -i hci1 scan', whcih uses the external bluetooth adaptor, and I do find device, meaning the device in test is not to be suspected. Would you be so kind to provide a workaround? I mentioned in previous post a commandline workaround which force use of external USB adaptor, but in reality it works very unstable. I guess a stable workaround would require preventing the kernel discovering the first internal bluetooth adaptor. P. S. If you have kernel source, have you poke in to see if the DEVICE id in question was referred to there? ** Tags removed: needs-upstream-testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1071341 Title: bluetooth usb 0489:e048 Foxconn / Hon Hai fail to scan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1071341/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
