Fail to setup Bluetooth on Dell Venue 11 Pro
A message that is not in the archive (sent off-list or not yet received): [email protected]/
https://bugzilla.kernel.org/show_bug.cgi?id=73081
Dmitry Khromov <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
--- Comment #1 from Dmitry Khromov <[email protected]> ---
Same here, on Venue 8 Pro.
Actually, the protocol Windows is using is H4, nevertheless, it doesn't work also.
This snippet from DSDT table (BTH0 entry, DLAC3002) specifies the UART settings that Windows (supposedly) uses:
UartSerialBus (0x0001C200, DataBitsEight, StopBitsOne, 0xC0, LittleEndian, ParityTypeNone, FlowControlHardware, 0x0020, 0x0020, "\\_SB.URT1", 0x00, ResourceConsumer, ,)
URT1 is /dev/ttyS4 in my config, the interesting thing is that there's no bytes inbound at all - looks like the BT module is simply unpowered, no matter if I attach an rfkill-gpio (like Jin above), or drive GPIOs manually (via /sys/bus/gpio).
So, it's unlikely a kernel bug (and may be closed as such).
Jin. had you ever succeed in getting this piece working?
Signature · 2 lines
You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=73081
Jianlong Liu <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
--- Comment #2 from Jianlong Liu <[email protected]> ---
Same here, not working on Venue 8 Pro. Adding the ACPI ID doesn't result in anything.
Signature · 2 lines
You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=73081
--- Comment #3 from Jianlong Liu <[email protected]> --- Forgot to mention, this was tested on kernel 4.4.
Signature · 2 lines
You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=73081
Hytham ([email protected]) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
--- Comment #4 from Hytham ([email protected]) ---
Has anyone been able to resolve this issue? I installed Ubuntu 2022 LTR but I yet have the same issue with both WiFi and Bluetooth.
I would be okay with WiFi not working if I could at least get Bluetooth working without using a dongle. That way I could attach my tablet to a Keyboard case and use it for notes etc.
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=73081
Paul Menzel ([email protected]) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pmenzel+bugzilla.kernel.org
| |@molgen.mpg.de--- Comment #5 from Paul Menzel ([email protected]) --- Puh, that is an old issue, and no attachments. Please attach the output of dmesg and all other things asked for if you create a new issue in
https://github.com/bluez/bluez/issues.
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=73081
--- Comment #6 from Hytham ([email protected]) --- Thanks Paul, please find my dmesg.log and new issue here:
https://github.com/bluez/bluez/issues/2222
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=73081
--- Comment #7 from Dmitry Khromov ([email protected]) ---
If memory serves, the MMIO-mapped UART requires CONFIG_SERIAL_DEV_CTRL_TTYPORT=y for a port to be picked up by BlueZ. This, in turn, requires CONFIG_SERIAL_DEV_BUS=y, but most desktop distros ship a kernel with CONFIG_SERIAL_DEV_BUS=m.
Long story short, I was successful in bringing Bluetooth up and running on Venue 8 Pro back in the day, so try compiling a kernel with the configuration flags mentioned. No further action should be required -- BlueZ should automatically pick the port up and attach the HCI.
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=73081
--- Comment #8 from Paul Menzel ([email protected]) --- At least Debian’s Linux kernel (6.1 and 7.1 from suite *experimental*) have it set to CONFIG_SERIAL_DEV_BUS=y. @Hytham, please check your Ubuntu Linux kernel config in /boot/, for example with grep CONFIG_SERIAL_DEV_BUS /boot/config*.
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=73081
--- Comment #9 from Hytham ([email protected]) ---
Hi Paul,
Yes, I confirmed that the kernel I already have in /boot has CONFIG_SERIAL_DEV_BUG=y.
Thanks,
Hytham
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=73081
--- Comment #10 from Dmitry Khromov ([email protected]) --- My apologies for misleading, that was a hunch from back then.
From your dmesg log I notice the kernel fails to find the WiFi/Bluetooth chip firmware. You should grab it from
https://github.com/qca/ath6kl-firmware/tree/master/ath6k/AR6004/hw3.0
which is where I got it the last time and put into /lib/firmware/ath6k/AR6004/hw3.0 if you haven't done so already.
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=73081
--- Comment #11 from Hytham ([email protected]) --- Hi Dmitry,
I followed the instructions in https://github.com/bluez/bluez/issues/2222 to copy the firmware to this directory and rebooted which solved the Wifi issue but Bluetooth is yet not working. I provided additional logs in the bluez ticket.
Thanks,
Hytham
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=73081
--- Comment #12 from Dmitry Khromov ([email protected]) --- @Hytham, noted.
First, please disregard everything I said about CONFIG_SERIAL_DEV_BUG -- got another Baytrail device mixed up with this one, my bad. That said, the actual problem, according to my notes, is the UART's baud_base (2764800), resulting in framing errors with common baud rates (i.e. 3000000 and 3500000). The speed the controller is pre-set to is 3768000. I've dug the tablet up and with semi-recent musl-based Void rootfs and kernel 6.18.35 (CONFIG_SERIAL_DEV_BUS=m, btw) got btattach -B /dev/ttyS1 -P ath3k working by manually setting the speed with a TCSETS2 ioctl. I’ve managed to pair and test some BT peripherals.
@Paul, since, ultimately, this isn’t a kernel bug (though a patch for rfkill-gpio is still required), should this discussion be continued on GitHub?
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=73081
--- Comment #13 from Paul Menzel ([email protected]) --- Yes, as @Hytham is about the Dell Venue 8 Pro 5830/0RK4PK anyway, and this Kernel Bugzilla issue is about the Dell Venue 11 Pro, let’s continue in the GitHub issue.
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.