I downgraded to 6.1.10-artix1-1 because after upgrading:
- No more audio, dummy output
- No more hibernation, I tried also "echo disk > /sys/power/state "
- No more touchscreen click, because no more uinput module. It is necessary for ydotool.
Without that since a bug in Hyprland I cannot use the touchscreen - No more internet can't connect
No more bluetooth on the downgraded kernel:
blueman-manager
blueman-manager 20.51.25 ERROR Manager:147 on_dbus_name_appeared: Default adapter not found, trying first available.
blueman-manager 20.51.25 ERROR Manager:151 on_dbus_name_appeared: No adapter(s) found, exiting
Edit: it started to work, although I couldn't connect to my desktop or my PinePhone.
Was uinput module removed by the kernel?
I use ydotool to perform right click etc.
My device: CHUWI UBook.
This 6.x kernel series is a disaster, but hey, at least it comes with a CoC!
Today I upgraded the kernel and I can't see the BT again.
Same blueman-manager errors as before.
I turned it off and then on thrice.
uname -r
6.3.3-artix1-1
https://www.phoronix.com/news/Linux-6.3-XFS-Metadata-Corrupt
> Since last week has been this Red Hat BugZilla report over XFS metadata corruption when upgrading to Linux 6.3.3.
TLDR: read wiki (https://wiki.archlinux.org/title/Bluetooth) and go over installation, configuration and troubleshooting. check if device appear in "rfkill" command
Before Kernel 6, there was 2 or 3 different Interfaces (not the word, I just forgot the word for it) for communicating with A single device. so for me I was able to control brightness with all 3 but none worked properly, so i end up write script to modify the file in " /sys "
after Kernel 6 , I abandoned those scripts and now everything works out of box
the kernel dev end up dropping old method of handling devices that had replacement
as for what you can do, you can check if your device is being recognized to begin with or not.
so for bluetooth go to wiki (https://wiki.archlinux.org/title/Bluetooth) and go over installation, configuration and troubleshooting. look for when your device report is not similar to wiki. then just google the error or what is missing (there's definitely someone in arch or fedora that face same problem)
best case scenario, it will be fixed by time
totally worth it
lsusb
...
Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP)
...
https://linux-hardware.org/?id=usb:8087-0aaa.
A workaround is to unload and load the btusb module:
modprobe -r btusb
modprobe btusb