https://bugzilla.kernel.org/show_bug.cgi?id=51981 Summary: Bluetooth not working on Linux after power cycling Product: Drivers Version: 2.5 Kernel Version: 3.4.11-2.16-desktop #1 SMP PREEMPT Wed Sep 26 17:05:00 UTC 2012 (259fc87) x86_64 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Bluetooth AssignedTo: linux-bluetooth@xxxxxxxxxxxxxxx ReportedBy: aleph0hpela-bugz@xxxxxxxxxxx Regression: No Machine is a Dell Latitude D820 laptop with Dell 350 Bluetooth card connected via internal USB bus. It has multiple boot partitions. If I boot Linux from cold, there is no Bluetooth. The blue light on the machine is lit, rfkill says it is not blocked, but lsusb can't find it and the KDE System Settings Bluetooth applet says there is no adapter. If I boot Windows Vista from another boot partition, the Bluetooth works on Windows Vista. If I then reboot into Linux without powering down, the Bluetooth works on Linux too. lsusb sees Bus 001 Device 005: ID 413c:8103 Dell Computer Corp. Wireless 350 Bluetooth and the KDE System Settings Bluetooth applet sees it too and I can pair and browse my Bluetooth phone. I don't know if it worked any better with older kernels. Another boot partition with 32-bit openSUSE 12.1 3.1.10-1.16-desktop #1 SMP PREEMPT Wed Jun 27 05:21:40 UTC 2012 (d016078) i686 shows the same behaviour. I don't think that Bluetooth has ever worked with Linux since I bought the machine and installed openSUSE 10.x on it, but I really don't want to clobber one of my boot partitions with an old OS to verify this. It always worked with Windows Vista. I was advised to try downgrading the firmware in the Bluetooth card to the Windows XP version (see http://forums.opensuse.org/showthread.php?t=481385&goto=newpost). This breaks the Bluetooth on Windows Vista because the firmware installer removes the Vista Bluetooth stack and I don't know how to reinstall it without installing the Vista firmware too. However Linux behaves the same with either firmware: Bluetooth only works if Windows has been run since the machine was powered up. As far as I can see the only possible explanation for this behaviour is that the Linux Bluetooth driver for the Dell 350 card isn't initialising the card properly. Presumably there is some register in the card which is destroyed by cycling the power but not by rebooting. Windows is initialising this register correctly but the Linux driver isn't. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
