Just a question out of curiosity.
I bought a combo of bluetooth keyboard and mouse yesterday, but I forgot I have used dm-crypt to encrypt most of my partition (/usr, /var, /home), so the system will prompt for password to decrypt in the middle of rc.S If the bluetooth keyboard didn't get recognized before that, I will not able to boot smoothly.
When I plugged in the two devices today, I am amazed all runs well and the bluetooth keyboard is well detected in the middle of rc.S (which let me input the dm-crypt password) and I able to boot into X without any problem, and the bluetooth mouse detected perfectly as well.
I found out I actually
- didn't enable /etc/rc.d/rc.bluetooth to be executable
- /sbin/modprobe bluetooth is not turned on in /etc/rc.d/rc.modules
- result of 'lsmod|grep bluetooth' gives me
bluetooth 47805 0
rfkill 13278 1 bluetooth
- content of /etc/modprobe.d/bluetooth.conf gives me:
options btusb reset=1
- the following is found in my /boot/config:
My question is: which part of the system is responsible to make the bluetooth keyboard working perfectly well during rc.S ? The bluetooth modules didn't enabled in /etc/rc.d/rc.modules but why it's still able to be loaded ? Is it something to do with udev ?
Any sharing will be much appreciated or any hints on which direction I should look into in order to understand it. Thanks
[I am using slackware 13.37 ]