From here it looks like faulty hardware but you said it worked in E-OS (My own abbreviation), so I doubt it is that.But the fact that it complains about no device being present again makes me think of some kind of hardware thing.
That is interesting… so just a simple explanation:
UEFI initialize bluetooth normally.
If fastboot, partial initialization or sort of is enabled at the UEFI settings then it skips some devices for boot speed up.
If so, then linux does not recognize the device, therefore: it is not there.
Also, when booted with with fastboot and you run mkinitcpio (usually on kernel upgrade), it will not include the bluethooth module on startup, meaning:
default kernel includes only current loaded modules
fallback kernel includes everything even if not necessary
Hope it helps to understand the problem for further testing
There was a problem with this adapter on each of the distributions I tested with this adapter. I tested LINUX MINT, Zorin OS. With the help of forum users from this distribution, we were able to get this adapter up and running. I thought that if I switch to Manjaro, this will not be a problem
so if I understand you correctly, in the bios settings I should turn off the boot speed so that the bluetooth adapter module can be seen when the computer is started and not only after restarting the computer
Sir, when it comes to starting the bluetooth module when starting the computer, you were right. I changed the boot settings and it’s ok. In my bios, the fastboot sweep has a different name.
When it comes to searching for devices, I also managed to fix the problem. The quetia was the driver of the bleethooth module. In the next post I will write how I managed to solve the problem.
~ lsusb ✔
Bus 002 Device 002: ID 8087:8000 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 003 Device 004: ID 105b:e065 Foxconn International, Inc. BCM43142A0 Bluetooth module
Bus 003 Device 003: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth
Bus 003 Device 002: ID 174f:148d Syntek Lenovo EasyCamera
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
check the manufacturer and model of the bluetooth module.
In my case:
Bus 003 Device 006: ID 105b: e065 Foxconn International, Inc. BCM43142A0 Bluetooth module
Just remember, if it’s not a dkms kernel module, it won’t survive kernel updates and will have to be reinstalled after every kernel change. (So basically after every update. That is, if your kernel version gets an update.)