You are not logged in.
I've got a netbook with bluetooth supported by the omnibook driver. In rc.conf, I left the modules autoloading on, and added 'omnibook' to the modules array, because it wasn't automatically loaded. Then I added the following line to /etc/modules.d/modprobe.conf:
options omnibook ectype=12 wifi=1 bluetooth=1But I still don't get a Bluetooth device after the boot. I only get it if I run:
sudo rmmod omnibook ; sudo modprobe omnibook ectype=12 wifi=1 bluetooth=1How should I set these options at boot time? I couldn't find any other orientation in the wiki. Thanks!
Last edited by leonardof (2010-04-29 01:58:24)
Offline
The omnibook module isn't something I've ever used but there is no need to include "sudo" in the options line. How about trying:
options omnibook ectype=12 wifi=1 bluetooth=1Offline
Actually the sudo is not in the .conf file, sorry for pasting it here,
Offline
Linux 2.6.33 is out, and the issue continues. Any ideas?
Offline
The module could be getting loaded by the initcpio. Try adding /etc/modprobe.d/modprobe.conf to FILES in /etc/mkinitcpio.conf.
Offline
Already did it, no luck. Should I add the driver to the modules list in the mkinitcpio conf file?
Offline
By the way, tried adding the omnibook driver to the modules list in /etc/mkinitcpio.conf but I still don't get bluetooth on startup.
Offline
With the latest kernel update the problem was solved. I just set the options in /etc/modprobe.d/ and the kernel autoloads the driver.
Offline