© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Unfortunately, the solutions suggested previously on message #4 and #6 don’t work. I’ve tried to do an hex2hcd of the .hex file used by my windows, then put it in /lib/firmware with the good name and it didn‘t work at all, bluetooth is still unusable.
For the solution proposed in #6, I don’t really understand how to rename the .hcd, if the name matters, I might have done an error, but if not, it simply doesn’t seem to work.
The solution that looked the most promising was to use ndiswrapper on the windows driver, device seems to be recognized, but still not working unfortunately.