LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
gebra has quit [Remote host closed the connection]
GNUmoon has quit [Ping timeout: 260 seconds]
schmengie has quit [Ping timeout: 256 seconds]
e1z0 has quit [Changing host]
e1z0 has joined #libreelec
mrpelotazo has joined #libreelec
GNUmoon has joined #libreelec
ChriChri_ has quit [Ping timeout: 245 seconds]
ChriChri_ has joined #libreelec
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
gebra has joined #libreelec
k-man has quit [Ping timeout: 246 seconds]
k-man has joined #libreelec
electro575 has joined #libreelec
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
TomTom has joined #libreelec
<sopparus>
yeah, I tried to explain that I have added my own firmware :)
<sopparus>
its that bluetooth firmware file that kills everything
<sopparus>
tried libreelecs, volumios and the newest one from linux firmware page
<sopparus>
only volumios work at all, but problems. Like it only worked after replug
<sopparus>
so I guess bug report upstream is the way to go
<sopparus>
but in the meanwhile, I cant blacklist that firmware file from being loaded? so i dont have to custom build
<LEBot>
[slack] <chewitt> sopparus: You can blacklist drivers (that load firmware) assuming they are =m not built-in with =y
<LEBot>
[slack] <chewitt> and you can override the firmware files (as described)
<sopparus>
Yes, but no Bluetooth firmware file works at all
<sopparus>
And I need the driver for wifi, same driver loads blietooth
<LEBot>
[slack] <chewitt> but no method to exclude the default firmware unless you drop it from the kernel-firmware package
<sopparus>
Yeah that's what I had to do
<LEBot>
[slack] <chewitt> I did find some discussion about this adapter and it’s issues upstream which was saying something about BT .. need to re-find the link tho
<sopparus>
I pasted a link in the forum
<sopparus>
That's the link that got me to "solve" this
<LEBot>
[slack] <chewitt> “Bug: (2023-12-22) Many Linux distros are detecting Bluetooth capability in mt7921au based adapters but none of the adapters on the market have Bluetooth turned on so it won’t work. Linux should not be detecting Bluetooth capability when it is actually not available.”
<LEBot>
[slack] <chewitt> “Status: Open and ongoing”
<LEBot>
[slack] <chewitt> I’d guess that detection results in attempts to load firmware which may then result in bad things happening?
<sopparus>
Ah yea
<LEBot>
[slack] <chewitt> I didn’t read the whole thread though .. so guessing
<sopparus>
Nice
<sopparus>
So kernel should stop detecting Bluetooth?
<sopparus>
Or mt7921 driver rather
<LEBot>
[slack] <chewitt> IIRC you reported that removing the BT firmware results in everything (else) working as expected?
<LEBot>
[slack] <chewitt> “That is caused by RasPiOS detecting the bt support in the cf-951ax, even though Comfast turned the support off. I can get rid of this by deleting the bt firmware. I’ll do that when I upgrade the firmware for the wifi.”
<LEBot>
[slack] <chewitt> message from the issues thread, and log entry from your dmesg
<LEBot>
[slack] <chewitt> Q: do you need BT for anything?
<LEBot>
[slack] <chewitt> If no, I’m wondering what happens with “systemctl disable bluetooth && systemctl mask bluetooth && reboot” ?
<LEBot>
[slack] <chewitt> also, what USB port is the dongle attached to? .. USB 2.0 or USB 3.0?
<LEBot>
[slack] <chewitt> but there’s no response that I can see
<LEBot>
[slack] <chewitt> it does tell you which version of firmware last worked, which would allow an LE overlay workaround
<LEBot>
[slack] <chewitt> from the ‘lore’ article you can download an mbox version of the original message - and then load that into a mail client to send a ‘reply’ to the original message saying ’“me too, was this replied to anywhere, I don’t see one on the mailing list” or such
<LEBot>
[slack] <chewitt> echo “blacklist btmk > /storage/.config/modprobe.d/blacklist.conf” might work as a workaround?
agentcasey has quit [Remote host closed the connection]
psydroid has joined #libreelec
agentcasey has joined #libreelec
LEBot has quit [Remote host closed the connection]
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
<sopparus>
nope its reakl
<sopparus>
real
<oblikoamorale>
..you can always bind mount an empty file over firmware blobs you don't like in /lib/firmware/...
<sopparus>
empty file on /storage/.config/mediatek/
<sopparus>
and le still loads 5.236874] bluetooth hci1: loading /lib/firmware/mediatek/BT_RAM_CODE_MT7961_1_2_hdr.bin failed with error -22
<sopparus>
hm
<sopparus>
oblikoamorale: will it be persistant?
<oblikoamorale>
if you make it a systemd unit, yes
<oblikoamorale>
oh, fw is loading before that. nevermind
<oblikoamorale>
is bluetooth a loadable module? there is a way to blacklist specific modules via kernel boot param via initcall_blacklist
<sopparus>
CONFIG_MT7921U=m
<sopparus>
That's the only thing I added in the original pr to le
<sopparus>
Two years ago
<sopparus>
And I need that for wifi
<sopparus>
So I guess it.loads the BT too
minimal has joined #libreelec
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
<LEBot>
[slack] <chewitt> the modules that I can see that might be involved are “btmtk” and “btmtkuart”
<LEBot>
[slack] <chewitt> both are built with =m
<LEBot>
[slack] <chewitt> there’s also CONFIG_BT_HCIBTUSB_MTK but that’s =y
<oblikoamorale>
wondering if blocking the related modules will also stop MT7921U module from loading completely
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
rsalvaterra has quit [Quit: No Ping reply in 180 seconds.]
rsalvaterra has joined #libreelec
psydroid has joined #libreelec
rsalvaterra has quit [Ping timeout: 255 seconds]
rsalvaterra has joined #libreelec
<rain0r>
Hey there, I'm trying to build libreelec with "PROJECT=Generic ARCH=x86_64 make image" but I'm getting "undefined reference to 'cdio_charset_to_utf8'" even though I got libcdio-dev=2.1.0-4 installed (Debian Bookworm) - what's missing?
<oblikoamorale>
rain0r: ubuntu 22.04 is used by the team to build current LE's, never had a problem with it personally. unclear if it matters, but libcdio-dev is 2.1.0-3ubuntu0.2 version there
LEBot has quit [Remote host closed the connection]
<rain0r>
oblikoamorale: Thanks, I will give it a try. Meanwhile: can I disable cd completely? I dont even have a cd/dvd drive