Page: Previous  1, 2, 3

xav
Status: Interested
Joined: 17 May 2021
Posts: 17
Location: Grenoble, France
Reply Quote
I have the correct firmware installed, it used to work with a previous liquorix kernel, just it doesn't work anymore.
Back to top
damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 906
Reply Quote
Can you post the output of sudo journalctl -k | grep -Pi 'ath11k|firmware'? Most likely something else is failing and you'll find it in your kernel boot logs.

Also, it looks like overall there was (still is?) a huge regression with ath11k, you can see by searching kernel.org's bugzilla: bugzilla.kernel.org/buglist.cgi?quicksearch=ath11k

Your bug was supposed to be fixed in 5.12.6, but something about your specific system is still having issues.
Back to top
xav
Status: Interested
Joined: 17 May 2021
Posts: 17
Location: Grenoble, France
Reply Quote
Here it is, it doesn't look like it event tries to load it.
:: Code ::
❯ sudo journalctl -k | grep -Pi 'ath11k|firmware'
[sudo] Mot de passe de xav :
juin 04 09:42:33 dev5 kernel: i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
juin 04 09:42:33 dev5 kernel: nouveau 0000:01:00.0: pmu: firmware unavailable
juin 04 09:42:33 dev5 kernel: psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x0f5002)
juin 04 09:42:33 dev5 kernel: ath11k_pci 0000:6d:00.0: BAR 0: assigned [mem 0xb4200000-0xb42fffff 64bit]
juin 04 09:42:33 dev5 kernel: ath11k_pci 0000:6d:00.0: enabling device (0000 -> 0002)
juin 04 09:42:33 dev5 kernel: ath11k_pci 0000:6d:00.0: chip_id 0x0 chip_family 0xb board_id 0xff soc_id 0xffffffff
juin 04 09:42:33 dev5 kernel: ath11k_pci 0000:6d:00.0: fw_version 0x101c06cc fw_build_timestamp 2020-06-24 19:50 fw_build_id
juin 04 09:42:33 dev5 kernel: ath11k_pci 0000:6d:00.0 wlp109s0: renamed from wlan0
juin 04 13:40:10 dev5 kernel: ath11k_pci 0000:6d:00.0: dropping mgmt frame for vdev 0, is_started 0
juin 04 13:46:29 dev5 kernel: psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x0f5002)

Back to top
damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 906
Reply Quote
How about sudo journalctl -k | grep -i bluetooth?
Back to top
xav
Status: Interested
Joined: 17 May 2021
Posts: 17
Location: Grenoble, France
Reply Quote
Only generic stuff is started:
:: Code ::
juin 04 09:42:33 dev5 kernel: Bluetooth: Core ver 2.22
juin 04 09:42:33 dev5 kernel: Bluetooth: HCI device and connection manager initialized
juin 04 09:42:33 dev5 kernel: Bluetooth: HCI socket layer initialized
juin 04 09:42:33 dev5 kernel: Bluetooth: L2CAP socket layer initialized
juin 04 09:42:33 dev5 kernel: Bluetooth: SCO socket layer initialized
juin 04 09:42:33 dev5 kernel: Bluetooth: HCI UART driver ver 2.3
juin 04 09:42:33 dev5 kernel: Bluetooth: HCI UART protocol H4 registered
juin 04 09:42:33 dev5 kernel: Bluetooth: HCI UART protocol BCSP registered
juin 04 09:42:33 dev5 kernel: Bluetooth: HCI UART protocol LL registered
juin 04 09:42:33 dev5 kernel: Bluetooth: HCI UART protocol ATH3K registered
juin 04 09:42:33 dev5 kernel: Bluetooth: HCI UART protocol Three-wire (H5) registered
juin 04 09:42:33 dev5 kernel: Bluetooth: HCI UART protocol Intel registered
juin 04 09:42:33 dev5 kernel: Bluetooth: HCI UART protocol QCA registered
juin 04 09:42:33 dev5 kernel: Bluetooth: HCI UART protocol AG6XX registered
juin 04 09:42:33 dev5 kernel: Bluetooth: HCI UART protocol Marvell registered
juin 04 09:42:34 dev5 kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
juin 04 09:42:34 dev5 kernel: Bluetooth: BNEP filters: protocol multicast
juin 04 09:42:34 dev5 kernel: Bluetooth: BNEP socket layer initialized

Back to top
damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 906
Reply Quote
Yup, it looks like the device itself is never initialized. Is there any difference in modules loaded between Liquorix and a stock kernel?

For example:
:: Code ::
$ lsmod | grep -Pi 'bt|bluetooth'
btusb                  61440  0
btrtl                  16384  1 btusb
btbcm                  16384  1 btusb
btintel                32768  1 btusb
bluetooth             520192  47 btrtl,btintel,btbcm,bnep,btusb,rfcomm
ecdh_generic           16384  2 bluetooth
rfkill                 32768  9 hp_wmi,bluetooth,cfg80211
crc16                  16384  2 bluetooth,ext4


Another thing to check, what's your output of sudo journalctl -xu bluetooth -b0 when booting with Liquorix?
Back to top
xav
Status: Interested
Joined: 17 May 2021
Posts: 17
Location: Grenoble, France
Reply Quote
Oh sorry I didn't see your last post ...

Here are the bt modules:
:: Code ::
❯ grep -Pi 'bt|bluetooth'  <mods.debian
btqca                  20480  1 hci_uart
btrtl                  24576  1 hci_uart
btbcm                  20480  1 hci_uart
btintel                32768  1 hci_uart
bluetooth             737280  34 btrtl,btqca,btintel,hci_uart,btbcm,bnep,rfcomm
ecdh_generic           16384  2 bluetooth
rfkill                 28672  8 bluetooth,dell_laptop,cfg80211
crc16                  16384  2 bluetooth,ext4
libaes                 16384  2 bluetooth,aesni_intel

❯ grep -Pi 'bt|bluetooth'  <mods.liquorix
btqca                  16384  1 hci_uart
btrtl                  16384  1 hci_uart
btintel                28672  1 hci_uart
bluetooth             491520  11 btrtl,btqca,btintel,hci_uart,bnep
ecdh_generic           16384  1 bluetooth
rfkill                 28672  8 bluetooth,dell_laptop,cfg80211
crc16                  16384  2 bluetooth,ext4

and here's the journal under liquorix:
:: Code ::
-- Journal begins at Sun 2021-04-25 09:58:36 CEST, ends at Fri 2021-07-23 08:46:43 CEST. --
Jul 23 08:41:13 dev5 systemd[1]: Starting Bluetooth service...
-- Subject: A start job for unit bluetooth.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit bluetooth.service has begun execution.
--
-- The job identifier is 1624.
Jul 23 08:41:13 dev5 bluetoothd[1155]: Bluetooth daemon 5.55
Jul 23 08:41:13 dev5 systemd[1]: Started Bluetooth service.
-- Subject: A start job for unit bluetooth.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit bluetooth.service has finished successfully.
--
-- The job identifier is 1624.
Jul 23 08:41:13 dev5 bluetoothd[1155]: Starting SDP server
Jul 23 08:41:13 dev5 bluetoothd[1155]: Bluetooth management interface 1.19 initialized

Back to top
damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 906
Reply Quote
xav, can you try the latest kernel available? Per this github issue, bluetooth suddenly started working again for a user on Debian Sid: github.com/damentz/liquorix-package/issues/63
Back to top
xav
Status: Interested
Joined: 17 May 2021
Posts: 17
Location: Grenoble, France
Reply Quote
Here it still doesn't work:
:: Code ::
root@dev5:~# uname -a
Linux dev5 5.13.0-13.1-liquorix-amd64 #1 ZEN SMP PREEMPT liquorix 5.13-11.1~sid (2021-08-26) x86_64 GNU/Linux

:: Code ::
root@dev5:~# ~xav/inxi/inxi -ENxx
Network:   Device-1: Intel I210 Gigabit Network vendor: CalDigit driver: igb v: kernel port: <unassigned> bus-ID: 0b:00.0
           chip-ID: 8086:1533
           Device-2: Qualcomm QCA6390 Wireless Network Adapter [AX500-DBS ] vendor: Rivet Networks driver: ath11k_pci
           v: kernel port: <unassigned> bus-ID: 6d:00.0 chip-ID: 17cb:1101
Bluetooth: Message: No bluetooth data found.

Back to top
Display posts from previous:   
Page: Previous  1, 2, 3
All times are GMT - 8 Hours