Recalbox 4.1 x64 stable on PC : is there a way to see if the onboard bluetooth is supported ?

[Substring]

the file is available at https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/intel

No idea yet where to drop it ... /lib/firmware/intel ? or /etc/firmware/intel ? No recalbox at hand for now.

But i think we can make it available by default in a later release

[Maldorhan]

@substring Oh wow thanks ! I answered before I saw your second answer, i'm gonna check if I can add it manually (I have no clue about that yet), and else wait for an update, thanks A LOT for considering it and again for your help !

[Substring]

@maldorhan Once I get back home i'll have a quick look where the file is suppoed to be. I don't know if you're familiar with linux, but it may not be a funny moment for you to drop the file where it is expected. I'll give you the step-by-step if necessary

[Maldorhan]

I have honestly no idea where to put it yet even if I know a bit of Linux but I'll make sure to look hard for it and if needed follow your (very much appreciated) advices when you get home

[Maldorhan]

Seems to be /lib/firmware/intel doesn't work for now though

[Maldorhan]

@Substring

I get that after adding the files

Bluetooth: hci0: Found device firmware: intel/ibt-12-16.sfi
[ 1.858988] Bluetooth: hci0: Failed to send firmware signature (-38)

Edit : this the the new message I get in dmesg, no idea how to bypass? the signature check or add one

[Substring]

@maldorhan I'm still looking for, but anyway, keep checking with hciconfig because the firmware upload happens wuite early in the boot process, might need bluez to be started too

[Maldorhan]

@Substring hciconfig still the same for now, dmesg fails because of this "fail to send firmware signature" error now so it finds the firmware but doesnt load it up for some reason, I have no idea what's this signature sending error is about, still googling it with no results yet, I'll try to reboot and wait a bit more

[Maldorhan]

/lib/firmware/intel$ dmesg | grep Bluetooth
[ 1.476560] Bluetooth: Core ver 2.21
[ 1.476569] Bluetooth: HCI device and connection manager initialized
[ 1.476572] Bluetooth: HCI socket layer initialized
[ 1.476574] Bluetooth: L2CAP socket layer initialized
[ 1.476585] Bluetooth: SCO socket layer initialized
[ 1.493970] Bluetooth: HCI UART driver ver 2.3
[ 1.493972] Bluetooth: HCI UART protocol H4 registered
[ 1.493972] Bluetooth: HCI UART protocol BCSP registered
[ 1.493973] Bluetooth: HCI UART protocol LL registered
[ 1.493974] Bluetooth: HCI UART protocol ATH3K registered
[ 1.493975] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 1.493999] Bluetooth: HCI UART protocol Intel registered
[ 1.494011] Bluetooth: HCI UART protocol BCM registered
[ 1.494012] Bluetooth: HCI UART protocol QCA registered
[ 1.846754] Bluetooth: hci0: Bootloader revision 0.0 build 26 week 38 2015
[ 1.847769] Bluetooth: hci0: Device revision is 16
[ 1.847770] Bluetooth: hci0: Secure boot is enabled
[ 1.847770] Bluetooth: hci0: OTP lock is enabled
[ 1.847771] Bluetooth: hci0: API lock is enabled
[ 1.847771] Bluetooth: hci0: Debug lock is disabled
[ 1.847772] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 1.857202] Bluetooth: hci0: Found device firmware: intel/ibt-12-16.sfi
[ 1.858988] Bluetooth: hci0: Failed to send firmware signature (-38)
[ 3.877037] Bluetooth: hci0: Reading Intel version information failed (-110)
[ 3.877039] Bluetooth: hci0 command 0xfc05 tx timeout
[ 17.272526] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 17.272528] Bluetooth: BNEP filters: protocol multicast
[ 17.272531] Bluetooth: BNEP socket layer initialized

[Substring]

@maldorhan try running modprobe -r btusb ; modprobe btusb and report back. If the first command fails, try rmmod btusb ; modprobe btusb

[Maldorhan]

@substring rebooting gave me another error, that is really weird : (without to change anything since last signature error)

/sbin$ dmesg | grep Bluetooth
[ 1.449567] Bluetooth: Core ver 2.21
[ 1.449577] Bluetooth: HCI device and connection manager initialized
[ 1.449580] Bluetooth: HCI socket layer initialized
[ 1.449583] Bluetooth: L2CAP socket layer initialized
[ 1.449591] Bluetooth: SCO socket layer initialized
[ 1.463656] Bluetooth: HCI UART driver ver 2.3
[ 1.463658] Bluetooth: HCI UART protocol H4 registered
[ 1.463659] Bluetooth: HCI UART protocol BCSP registered
[ 1.463659] Bluetooth: HCI UART protocol LL registered
[ 1.463660] Bluetooth: HCI UART protocol ATH3K registered
[ 1.463661] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 1.463685] Bluetooth: HCI UART protocol Intel registered
[ 1.463696] Bluetooth: HCI UART protocol BCM registered
[ 1.463696] Bluetooth: HCI UART protocol QCA registered
[ 3.941418] Bluetooth: hci0 command 0xfc05 tx timeout
[ 3.941450] Bluetooth: hci0: Reading Intel version information failed (-110)
[ 5.957541] Bluetooth: hci0 command 0xfc05 tx timeout
[ 5.957547] Bluetooth: hci0: Reading Intel version information failed (-110)
[ 23.468044] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 23.468046] Bluetooth: BNEP filters: protocol multicast
[ 23.468050] Bluetooth: BNEP socket layer initialized

[Maldorhan]

@substring said in Recalbox 4.1 x64 stable on PC : is there a way to see if the onboard bluetooth is supported ?:

modprobe -r btusb

I can't seem to be able to run the modprobe command (command not found) (that's where my small Linux knowledge stops I guess)

[Substring]

@maldorhan run rmmod instead of modprobe -r

[Maldorhan]

@substring both say "command not found" through SCP and nothing seem to happen through SSH :

SSH :

modprobe -r btusb ; modprobe btusb
modprobe -r btusb
modprobe btusb
rmmod btusb ; modprobe btusb
hciconfig
hci0: Type: BR/EDR Bus: USB
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
DOWN
RX bytes:81 acl:0 sco:0 events:8 errors:0
TX bytes:661 acl:0 sco:0 commands:7 errors:0

SCP :

/sbin$ modprobe -r btusb
-sh: line 94: modprobe: command not found
/sbin$ modprobe -r btusb ; modprobe btusb
-sh: line 96: modprobe: command not found
-sh: line 96: modprobe: command not found
/sbin$ rmmod btusb ; modprobe btusb
-sh: line 98: rmmod: command not found
-sh: line 98: modprobe: command not found

Sorry if I mess up something... long time I didnt use all of this I might do something stupid

[Maldorhan]

@substring and then dmesg keep saying :

[ 19.302778] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 19.302780] Bluetooth: BNEP filters: protocol multicast
[ 19.302783] Bluetooth: BNEP socket layer initialized
[ 26.976994] random: crng init done
[ 87.565311] usbcore: deregistering interface driver btusb
[ 87.618464] usbcore: registered new interface driver btusb
[ 89.641342] Bluetooth: hci0 command 0xfc05 tx timeout
[ 89.641373] Bluetooth: hci0: Reading Intel version information failed (-110)
[ 91.657512] Bluetooth: hci0 command 0xfc05 tx timeout
[ 91.881416] Bluetooth: hci0: Reading Intel version information failed (-110)
[ 129.843346] usbcore: deregistering interface driver btusb
[ 129.899740] usbcore: registered new interface driver btusb
[ 131.913463] Bluetooth: hci0 command 0xfc05 tx timeout
[ 131.913524] Bluetooth: hci0: Reading Intel version information failed (-110)
[ 133.929610] Bluetooth: hci0 command 0xfc05 tx timeout
[ 133.929738] Bluetooth: hci0: Reading Intel version information failed (-110)

[Substring]

@maldorhan This is all really weird
modprobe and rmmod do exist otherwise we can't dynamically load some kernel modules

[Maldorhan]

@substring Well maybe it worked through SSH ? I mean, is it supposed to answer something if it worked ? Waiting for your help about that, I've decided to update the BIOS from the NUC, gotta try something right ^^

[Maldorhan]

@substring Same thing with the new NUC Bios, dmesg reports that it can find the firmware, but else signature error else reading intel version information failed (errors -38 and -110), I've added both files to the drivers folder, ibt-12-16.sfi and .ddc

[Substring]

@maldorhan linux command hardly ever report anything if they worked. Printing nothing is the normal behaviour.

I thought that maybe you need the whole intel folder + make sure it is in fact "synced" with the kernel version

[Maldorhan]

@substring I just put the whole Intel folder in, what do you mean by "make sure it is in fact "synced" with the kernel version" ? Thanks