Intel Comet Lake PCH-LP CNVi WiFi works but no bluetooth

MAYBL8 · 8 October 2022 21:11

I wish there was some way to reverse engineer the windows driver because it works in Windows.

MAYBL8 · 8 October 2022 21:53

I did this and got this result but kde still says no bluetooth adapter found.

[demo@manjaro ~]$ systemctl start bluetooth.service
[demo@manjaro ~]$ systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
     Active: active (running) since Sat 2022-10-08 17:50:46 EDT; 21s ago
       Docs: man:bluetoothd(8)
   Main PID: 36712 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 18732)
     Memory: 2.0M
        CPU: 29ms
     CGroup: /system.slice/bluetooth.service
             └─36712 /usr/lib/bluetooth/bluetoothd

Oct 08 17:50:46 manjaro systemd[36712]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
Oct 08 17:50:46 manjaro systemd[1]: Starting Bluetooth service...
Oct 08 17:50:46 manjaro bluetoothd[36712]: Bluetooth daemon 5.65
Oct 08 17:50:46 manjaro systemd[1]: Started Bluetooth service.
Oct 08 17:50:46 manjaro bluetoothd[36712]: Starting SDP server
Oct 08 17:50:46 manjaro bluetoothd[36712]: Bluetooth management interface 1.22 initialized

brahma · 9 October 2022 06:38

so if you check with: rfkill list is bluetooth detected?
post output from:
cat /usr/lib/systemd/system/bluetooth.service

MAYBL8 · 9 October 2022 17:19

[demo@manjaro ~]$ rfkill list
0: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
[demo@manjaro ~]$ cat /usr/lib/systemd/system/bluetooth.service
[Unit]
Description=Bluetooth service
Documentation=man:bluetoothd(8)
ConditionPathIsDirectory=/sys/class/bluetooth

[Service]
Type=dbus
BusName=org.bluez
ExecStart=/usr/lib/bluetooth/bluetoothd
NotifyAccess=main
#WatchdogSec=10
#Restart=on-failure
CapabilityBoundingSet=CAP_NET_ADMIN CAP_NET_BIND_SERVICE
LimitNPROC=1

# Filesystem lockdown
ProtectHome=true
ProtectSystem=strict
PrivateTmp=true
ProtectKernelTunables=true
ProtectControlGroups=true
StateDirectory=bluetooth
StateDirectoryMode=0700
ConfigurationDirectory=bluetooth
ConfigurationDirectoryMode=0555

# Execute Mappings
MemoryDenyWriteExecute=true

# Privilege escalation
NoNewPrivileges=true

# Real-time
RestrictRealtime=true

[Install]
WantedBy=bluetooth.target
Alias=dbus-org.bluez.service

brahma · 9 October 2022 17:24

not detected …
open this file:
kate /usr/lib/systemd/system/bluetooth.service
and edit this line:

ConfigurationDirectoryMode=0555

to look like this:

ConfigurationDirectoryMode=0755

save the file… this will fix this message:

then turn off your computer, unplug it, remove the battery, and hold the power button for around 10 seconds, plug battery back, boot and check if it helped: rfkill list

MAYBL8 · 9 October 2022 17:44

I changed that line in the file however taking the battery out is out of the question at this time.
I have to remove the whole bottom of the case to do that and it is quite an ordeal to do.
I will use it unplugged until it dies and then hold the power button down.
I’ll let you know if it makes a difference

MAYBL8 · 9 October 2022 21:54

Well I let the battery go completely dead , held down the power button.
Started it back up.
Still not working.

brahma · 9 October 2022 22:02

so open this file:
kate /etc/default/grub
and in this line: GRUB_CMDLINE_LINUX_DEFAULT= inside the quotes add these parameters:
acpi_osi=! acpi_osi='Windows 2017'
dont remove anything from there, add it to existing parameters, save the file, update grub:
sudo update-grub
reboot and check with: rfkill list

if you cant boot with these parameters, in the grub menu press ‘E’ and locate the paramaters and remove them

MAYBL8 · 9 October 2022 22:19

First I really appreciate you sticking with me through all of this.
I felt we were getting real close with some of the results .
Still not there yet.
My Grub file looks like this now:

GRUB_CMDLINE_LINUX_DEFAULT="quiet pci=nocrs acpi=force acpi_osi=! acpi_osi='Windows 2017'"

The part before what you had me add was there already. I hope it doesn’t interfere with what you had me add.
I can remove it if you think it will help.
The result of rfkill is the same as it was before:

[demo@manjaro ~]$ rfkill list
0: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no

brahma · 9 October 2022 22:29

ok, so now replace the parameters, so that the grub looks like this:

GRUB_CMDLINE_LINUX_DEFAULT="quiet pci=nocrs acpi_osi=Linux"

i removed the acpi=force that you had there, lets try without it… if you however have issues that require this parameter, keep it there, dont remove it
then save the grub, update grub, reboot and test

edit: there was a typo there: apci_osi=Linux, so i corrected it to: acpi_osi=Linux

MAYBL8 · 9 October 2022 22:58

I think I had errors when the system booted is why I had the acpi=force there but it doesn’t seem to have affected anything.

So every time I boot I check the status of bluetooth and this time is is inactive.
and the commands to enable it and start it don’t seem to have an effect anymore.

[demo@manjaro ~]$ systemctl status bluetooth.service
○ bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
     Active: inactive (dead)
       Docs: man:bluetoothd(8)

Oct 09 18:48:07 manjaro systemd[1]: Bluetooth service was skipped because of a failed condition check (ConditionPathIsDirectory=/sys/class/bluetooth).

brahma · 9 October 2022 23:04

did you noticed this :

if not correct it and try again;
if it didnt worked, add this parameter:
acpi_osi=
so that your grub looks like this:

GRUB_CMDLINE_LINUX_DEFAULT="quiet pci=nocrs acpi_osi="

save the grub, update grub, reboot and check
if it doesnt work, add back the parameters you had there before

could be because of those changes in parameters that its status changed…
you check with: rfkill list if bluetooth is detected

MAYBL8 · 9 October 2022 23:58

Well I got something different with rfkill
However I lost my touchpad for some reason.
Putting grub back to what it was

[demo@manjaro ~]$ rfkill list
0: hp-wifi: Wireless LAN
        Soft blocked: no
        Hard blocked: no
1: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no

MAYBL8 · 9 October 2022 23:59

[demo@manjaro ~]$ systemctl status bluetooth.service
× bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
     Active: failed (Result: timeout) since Sun 2022-10-09 19:52:38 EDT; 6min ago
       Docs: man:bluetoothd(8)
    Process: 996 ExecStart=/usr/lib/bluetooth/bluetoothd (code=killed, signal=TERM)
   Main PID: 996 (code=killed, signal=TERM)
        CPU: 1ms

Oct 09 19:51:08 manjaro systemd[1]: Starting Bluetooth service...
Oct 09 19:52:38 manjaro systemd[1]: bluetooth.service: start operation timed out. Terminating.
Oct 09 19:52:38 manjaro systemd[1]: bluetooth.service: Failed with result 'timeout'.
Oct 09 19:52:38 manjaro systemd[1]: Failed to start Bluetooth service.

brahma · 10 October 2022 06:58

it detected the bluetooth as another wireless…
so now your grub looks like this?:

GRUB_CMDLINE_LINUX_DEFAULT="quiet pci=nocrs acpi=force acpi_osi=!"

first edit this:
kate /etc/modprobe.d/iwlwifi.conf
and put a # at the beginning so that it looks like this:
#options iwlwifi bt_coex_active=N
save the file

so lets try some more of these parameters:

GRUB_CMDLINE_LINUX_DEFAULT="quiet pci=nocrs acpi=force acpi_osi=!!"

GRUB_CMDLINE_LINUX_DEFAULT="quiet pci=nocrs acpi=force acpi_osi=!*"

GRUB_CMDLINE_LINUX_DEFAULT="quiet pci=nocrs acpi=force acpi_osi='Windows 2015'"

after adding each parameter, save the grub, update grub, reboot and check with:
rfkill list
if you cant boot with these parameters, in the grub menu press ‘E’ and locate the paramaters and remove them

MAYBL8 · 10 October 2022 12:32

I will reply after I do each change.
With this
acpi_osi=!

I lose my touchpad
and have this for rfkill

[demo@manjaro ~]$ rfkill list
0: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
1: hp-wifi: Wireless LAN
        Soft blocked: no
        Hard blocked: no

Olli · 10 October 2022 12:38

boot into a live-iso. use a live-iso of manjaro and a second one like linux-mint and check if bluetooth is avaiable in a live-session.
also check if bluetooth is still avaiable in your ms-windows. boot to windows and activate bluetooth.

MAYBL8 · 10 October 2022 14:10

quiet pci=nocrs acpi=force acpi_osi=!!

touchpad working

[demo@manjaro ~]$ rfkill list
0: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no

quiet pci=nocrs acpi=force acpi_osi=!*

No Touchpad

[demo@manjaro ~]$ rfkill list
0: hp-wifi: Wireless LAN
        Soft blocked: no
        Hard blocked: no
1: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no

quiet pci=nocrs acpi=force acpi_osi='Windows 2015'

touchpad working

[demo@manjaro ~]$ rfkill list
0: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no

Bluetooth working fine in windows
Linux mint live usb no adapter found
Manjaro live usb no adapter found

Olli · 10 October 2022 14:18

please post the output of

sudo dmesg | grep Bluetooth

MAYBL8 · 10 October 2022 14:42

[demo@manjaro ~]$ sudo dmesg | grep Bluetooth
[sudo] password for demo: 
[demo@manjaro ~]$