Tiny Core Linux

Tiny Core Base => TCB Q&A Forum => Topic started by: tcl_user5 on April 16, 2022, 11:36:18 AM

Title: Bluetooth not working
Post by: tcl_user5 on April 16, 2022, 11:36:18 AM

I am facing an issue of being unable to activate Bluetooth on Tiny Core Linux v 13.0, 64 bit. I have a Realtek 8723 B bluetooth device on a laptop.

I have installed Blueman from TC repo. On clicking Blueman,  I am getting the error message:-

Code: [Select]

" Bluez daemon is not running, blueman-manager cannot continue. This probably means that there were no Bluetooth adapters detected or Bluetooth daemon was not started."
a)

Code: [Select]

dmesg | grep blue gives the following output

Code: [Select]

bluetooth hci0: Direct firmware load for rtl_bt/rtl8723b_fw.bin failed with error -2
bluetooth hci0: Falling back to sysfs fallback for: rtl_bt/rtl8723b_fw.bin
bluetooth hci0: Direct firmware load for rtl_bt/rtl8723b_config.bin failed with error -2
bluetooth hci0: Falling back to sysfs fallback for: rtl_bt/rtl8723b_config.bin

b) I checked the directory

Code: [Select]

/usr/local/lib/firmware/rtl_bt. The file rtl8723b_fw.bin was there but rtl8723b_config.bin was missing. I downloaded both the files from github and saved it in the directory and backed it up. However, the above error messages continue.

c) During booting, the error message "

Code: [Select]

Bluetooth: hci0: command 0*fc20 tx timeout"  is also received.

I am attaching dmesg output also for reference.

Kindly advise.

Title: Re: Bluetooth not working
Post by: Rich on April 16, 2022, 02:53:05 PM

Hi tcl_user5

Quote from: tcl_user5 on April 16, 2022, 11:36:18 AM

... I have installed Blueman from TC repo. On clicking Blueman,  I am getting the error message:-

Code: [Select]

" Bluez daemon is not running, blueman-manager cannot continue. This probably means that there were no Bluetooth adapters detected or Bluetooth daemon was not started." ...

Did you read the  .info  file:
http://www.tinycorelinux.net/13.x/x86_64/tcz/blueman.tcz.info

Specifically the  Howto  part that says:

Quote

                sudo /usr/local/etc/init.d/bluez start
                startx

That ensures the  bluez daemon  gets started before  X (GUI)  starts.

You can make sure bluez starts at the correct time by adding:

Code: [Select]

/usr/local/etc/init.d/bluez startto your  /opt/bootsync.sh  file before the line that calls  bootlocal.sh.