Simply superb video. From start to finish. Also learnt a lot about the lore of the void project.

I Tried Void Linux For The First Time, It Was INSANE

Hello all -- I was just wondering, I can see kernel 7.3 is available in the repos, but linux-mainline is still using 7.2_1 (at least on my machine when I update/query).

Obviously not a request or anything, just pure curiosity as to how linux-mainline is linked to kernel updates.

I will also take this opportunity to wholeheartedly thank the Void team for their incredible dedication to this amazing project. This distribution is a true rare gem and for what it is worth, your work is immensely appreciated!

If you are running mangowc be advised that voidlinux just upgraded to version 18, and you will need to upgrade your config file for some breaking changes. There's a script you can run at https://github.com/mangowm/mango/releases/tag/0.18.0 to do the work.

Edit: it seems like Realtek just sucks ans i'll have to spend money ona new adapter as some of yoy suggested. But thanks for the help :(

Good afternoon guys, hope you're doing well

The reason i am posting is because i am so pissed already with my Bluetooth which in this case is a Realtek Semiconductor Corp. Bluetooth Radio (from lsusb | grep Bluetooth), specifically, the rtw88_8821ce (version 24.11.0, H2C version 12 from sudo dmesg | grep rtw88_8821ce).

So basically, i've been having this issue on Windows 10 (when i was using it before), on Parrot OS 6-7, on Debian Trixie, on Mint (live USB) and right now on Void Linux. So, the service is up and running, but when i enter into bluetoothctl, when i do this:

bluetoothctl

[NEW] Media /org/bluez/hci0

`SupportedUUIDs: 0000110a-0000-1000-8000-00805f9b34fb`

`SupportedUUIDs: 0000110b-0000-1000-8000-00805f9b34fb`

Agent registered

[bluetoothctl]> power on

Changing power on succeeded

[bluetoothctl]> agent on

Agent is already registered

[bluetoothctl]> default-agent

Default agent request successful

[bluetoothctl]> scan on

SetDiscoveryFilter success

Discovery started

[CHG] Controller 38:D5:7A:D0:65:C8 Discovering: yes

It just hangs there and doesn't scan a damn device at all.. It just hangs on this, and my Bluetooth is not blocked at all if i rfkill list as here:

rfkill list

0: hci0: Bluetooth

`Soft blocked: no`

`Hard blocked: no`

1: phy0: Wireless LAN

`Soft blocked: no`

`Hard blocked: no`

And yes, the service is running in case you wonder:

sudo sv status bluetoothd

run: bluetoothd: (pid 790) 24897s; run: log: (pid 786) 24897s

Yes, i admit i've used AI to investigate further and discard other causes, so the AI suggested i create this file because it had to do something about the poor way it handled autosuspend and power management for this device:

cat /etc/modprobe.d/btusb.conf

options btusb enable_autosuspend=0

options btusb reset=1

This is what i get after i boot up, log in, start my dbus session with mango and check the dmesg:

sudo dmesg | grep rtw88_8821ce

[ 8.653401] rtw88_8821ce 0000:01:00.0: enabling device (0000 -> 0003)

[ 8.654153] rtw88_8821ce 0000:01:00.0: Firmware version 24.11.0, H2C version 12

[ 8.934673] rtw88_8821ce 0000:01:00.0 wlo1: renamed from wlan0

[ 9.822714] rtw88_8821ce 0000:01:00.0 wlo1: renamed from wlan0 (while UP)

lsmod | grep bluetooth

bluetooth 1228800 35 btrtl,btmtk,btintel,btbcm,bnep,btusb,hci_vhci,rfcomm

rfkill 45056 5 hp_wmi,bluetooth,cfg80211

crc16 12288 2 bluetooth,ext4

ecdh_generic 16384 3 bluetooth,tpm

I use pipewire with wireplumber as followed in the Void manual, and these are the packages that i installed:

xbps-query -s bluetooth

[*] bluez-5.86_2 Bluetooth tools and daemons

[*] ldacBT-2.0.2.3_1 LDAC Bluetooth encoder library

[*] libbluetooth-5.86_2 Library to use the Bluez Linux Bluetooth Stack

[*] libspa-bluetooth-1.6.10_1 Server and user space API to deal with multimedia pipelines - bluetooth plugins

[*] sbc-2.2_1 Bluetooth Subband Codec (SBC) library

Has anyone been in this situation before? Is this possible to fix (yes i checked the device myself while upgrading the ram and it seems fine, no physical damage that can be seen on the spot), because i do not know what to do at this point. This is Linux, everything has to be fixable somehow...

Thank you for any help or advice and for rejecting systemd

So I use network manager alongside kde plasma and for some reason my network would sometimes randomly disconnect for no reason, I dont have a laptop so that isnt the problem. Idk how to explain it properly but it js some days it will work fine and some days it will keep randomly disconnect, usually when im on calls on discord or sometimes on a roblox game. I know those are two bad examples but its the only time they occured.