Summary: | no autoloading of bluetooth modules when daemons are started | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Marcel Wiesweg <marcel.wiesweg> |
Component: | Current packages | Assignee: | Mobile Herd (OBSOLETE) <mobile+disabled> |
Status: | RESOLVED INVALID | ||
Severity: | minor | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Marcel Wiesweg
2005-07-31 09:31:38 UTC
This is strange, as those exact lines are in "modprobe -c" output on my machine - they should be part of the /lib/modules/<kernel-version>/module.aliases file which is read automatically by modprobe & friends. So those entries should not be necessary to place in /etc/modules.d/aliases. Curious. In any case, I placed rfcomm and hci_usb in my /etc/modules.autoload.d/kernel-2.6 and it solved the problem for me. Thanks for the pointer. (In reply to comment #1) > This is strange, as those exact lines are in "modprobe -c" output on my machine > - they should be part of the /lib/modules/<kernel-version>/module.aliases file > which is read automatically by modprobe & friends. So those entries should not > be necessary to place in /etc/modules.d/aliases. Curious. These aliases are already part of the standard aliases for kernels with bluetooth modules as shown by running `modprobe -c`. |