https://bugzilla.kernel.org/show_bug.cgi?id=198423 Bug ID: 198423 Summary: Bluetooth device Lite-on QCA6174A [04ca:3016] does not work Product: Drivers Version: 2.5 Kernel Version: 4.15.0-rc7 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Bluetooth Assignee: linux-bluetooth@xxxxxxxxxxxxxxx Reporter: oscar@xxxxxxxxxxxx Regression: No Hi, In my acer Switch Alpha 12 the integrated bluetooth device does not work on my opensuse Tumbleweed (using latest kernel, 4.15.0-rc7). If I boot into Android x86 everything works fine. Steps to reproduce: - Execute: hciconfig hc0 up Expected output: - hci0 is turned up Current output: - Bluetooth is not activated and the following 2 errors appear in dmesg: -> kernel: Bluetooth: hci0: urb 00000000fdf311a5 failed to resubmit (113) -> bluetoothd[1326]: Failed to set mode: Failed (0x03) Additional output: - hwinfo: 05: USB 00.1: 11500 Bluetooth Device [Created at usb.122] Unique ID: NwzV.OU+Lh4yxoTF Parent ID: k4bc.2DFUsyrieMD SysFS ID: /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.1 SysFS BusID: 1-5:1.1 Hardware Class: bluetooth Model: "Lite-On Bluetooth Device" Hotplug: USB Vendor: usb 0x04ca "Lite-On Technology Corp." Device: usb 0x3016 Revision: "0.01" Driver: "btusb" Driver Modules: "btusb" Speed: 12 Mbps Module Alias: "usb:v04CAp3016d0001dcE0dsc01dp01icE0isc01ip01in01" Driver Info #0: Driver Status: btusb is active Driver Activation Cmd: "modprobe btusb" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #9 (Hub) - usb-devices: T: Bus=01 Lev=01 Prnt=01 Port=04 Cnt=04 Dev#= 6 Spd=12 MxCh= 0 D: Ver= 2.01 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=04ca ProdID=3016 Rev=00.01 C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb Thanks! -- 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
