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

[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

[Maldorhan]

@substring Same thing with the whole folder :

[ 2.709191] Bluetooth: hci0: Bootloader revision 0.0 build 26 week 38 2015
[ 2.709866] intel_rapl: Found RAPL domain package
[ 2.709868] intel_rapl: Found RAPL domain core
[ 2.709870] intel_rapl: Found RAPL domain uncore
[ 2.709872] intel_rapl: Found RAPL domain dram
[ 2.710387] Bluetooth: hci0: Device revision is 16
[ 2.710389] Bluetooth: hci0: Secure boot is enabled
[ 2.710390] Bluetooth: hci0: OTP lock is enabled
[ 2.710390] Bluetooth: hci0: API lock is enabled
[ 2.710391] Bluetooth: hci0: Debug lock is disabled
[ 2.710392] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 2.712136] Bluetooth: hci0: Found device firmware: intel/ibt-12-16.sfi
[ 2.713745] Bluetooth: hci0: Failed to send firmware signature (-38)

[Maldorhan]

@substring I THINK I SUCCEEDED !!!

Using these files, exact same name but different size : https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/intel/

[Maldorhan]

@substring CONTROLLER PAIRED !

UP RUNNING 
RX bytes:15151 acl:0 sco:0 events:2449 errors:0
TX bytes:603629 acl:0 sco:0 commands:2447 errors:0

[Maldorhan]

@substring Wiimote paired first shot, PS3 sixaxis didnt but this might not be related at all, well at least now if you wanna include the driver in a further update, you know that the ones on the second link work, no idea why the previous ones didnt

EDIT : PS3 Sixaxis works fine too !

[Substring]

@maldorhan You may not have downloaded correctly But your perseverance has paid, here you are with your NUC working like a charm

Now it's my turn to ask you something : can you

• fill https://github.com/recalbox/recalbox-os/wiki/PC-compatibility-(EN) with what you can ? At least your NUC reference, your CPU and the intel HDxxxx in GPU
• make hash of all files in the /lib/firmware rep ? Just md5sum /lib/firmware/*and give me the result 'enclose everything between 3 back ticks please, like
  ```
  output
  ```

thank you

[Maldorhan]

@substring Well the thing is, the previous files did not have the same hash / size (far from it) compared to the ones I've found on the second link, they only have the same name. The second ones dont trigger the signature failing issue.

And of course I would be glad to help too if I can, I'll try to do everything you asked tomorrow Thanks again for your help and work !

[Substring]

@maldorhan you're welcome ! Stay around, and spread the word

[Maldorhan]

@substring I just updated the github with my hardware and a few important details (bios versions since there's a glitch with the recalbox manager temperature probe with the last bios). Also I hashed the folder and gonna send it to you on the chat (?).

Topic is closed now