| View previous topic :: View next topic |
| Author |
Message |
Cloney
n00b
Joined: 10 Oct 2003
Posts: 65
|
 Posted: Fri Feb 13, 2004 2:30 pm Post subject: 2.6.2 Kernel - modprobe errors on boot |
 |
|
I've just built gentoo-dev-sources-2.6.2, and got it working with the nvidia driver and glx from ~x86.
I built the kernel with ALSA and the Bluez bluetooth sections entirely modularised, but I'm getting these errors on bootup:
| Code: | * Mounting sysfs at /sys... [ ok ]modprobe: FATAL: Module keybdev not found.
Bluetooth: Core ver 2.3
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: HCI USB driver ver 2.4
drivers/usb/core/usb.c: registered new driver hci_usb
modprobe: FATAL: Module hci_usb already in kernel.
modprobe: FATAL: Module hci_usb already in kernel.
* Loading ALSA drivers...
* Loading: snd-mixer-oss
* Loading: snd-pcm-oss
* Loading: snd-seq-oss
* Loading: snd_emu10k1
FATAL: Module snd_emu10k1 already in kernel.
* Loading: snd-emu10k1-synth
FATAL: Module snd_emu10k1_synth already in kernel.
* Loading: snd-seq-midi
FATAL: Module snd_seq_midi already in kernel.
* Loading: snd-seq-oss
FATAL: Module snd_seq_oss already in kernel.
* Running card-dependent scripts
* Restoring Mixer Levels |
Any idea what I need to do to get rid of these? lsmod shows that these modules are running and definitely are modules, so they must be being loaded twice.
Ta in advance.
Cloney |
|
| Back to top |
|
 |
nerdbert
l33t
Joined: 09 Feb 2003
Posts: 981
Location: Berlin
|
| Posted: Fri Feb 13, 2004 5:45 pm Post subject: |
|
|
Make sure you don't have those modules autoloaded twice. Like you have it in /etc/modules.autoload and /etc/modules.autoload.d/kernel-2.6
_________________
I'm really wondering what Lovechild is doing nowadays... |
|
| Back to top |
|
|
Robin79
l33t
Joined: 18 Oct 2003
Posts: 632
Location: /home/valdemarsvik
|
| Posted: Fri Feb 13, 2004 7:29 pm Post subject: |
|
|
i had the same problem before and a eroor on reboot i did a system upodate and then it got away and so with the reboot error but now when i have done system upgrade again the reboot error come back!
_________________
Gentoo 2005.0
ASUS P5AD2 Deluxe MB
Intel P4 3.2GHz
PCI-E Nvidia Geforce PCX 5750
--------------------
Registered Linux User Nr # 319050 http://counter.li.org |
|
| Back to top |
|
|
GentooBox
Veteran
Joined: 22 Jun 2003
Posts: 1168
Location: Denmark
|
| Posted: Sat Feb 14, 2004 1:51 pm Post subject: |
|
|
its just a bug in modules-init-tools, they errors dosent harm your system.
they are harmless.
more information and a temp solution:
https://forums.gentoo.org/viewtopic.php?t=128724
_________________
Encrypt, lock up everything and duct tape the rest |
|
| Back to top |
|
|
dopey
Apprentice
Joined: 10 Feb 2003
Posts: 235
|
| Posted: Sat Feb 14, 2004 4:28 pm Post subject: |
|
|
i'm not so sure this is the same as the bug in module-init-tools 3.whatever. My guess is that most likely CONFIG_KMOD was set to y in the kernel config (modules autoloading). This allows the kernel to detect and automaticaly load modules for most pnp peripherals well before the init process has progess to the boot runlevel.
i was able to solve the problem by disabling CONFIG_KMOD. Neat feature, but when i build modular stuff, I want to tell the kernel what to load, not have it do it automatically. |
|
| Back to top |
|
|
warthog
Tux's lil' helper
Joined: 11 Aug 2003
Posts: 82
Location: Seattle (Eastside)
|
| Posted: Sun Feb 15, 2004 8:13 am Post subject: CONFIG_KMOD |
|
|
| Interestingly enough, I'm having the same problem with my gentoo-dev-sources. Can someone shed some light on the CONFIG_KMOD option? |
|
| Back to top |
|
|
dopey
Apprentice
Joined: 10 Feb 2003
Posts: 235
|
| Posted: Sun Feb 15, 2004 5:31 pm Post subject: Re: CONFIG_KMOD |
|
|
| warthog wrote: | | Interestingly enough, I'm having the same problem with my gentoo-dev-sources. Can someone shed some light on the CONFIG_KMOD option? |
CONFIG_KMOD allows the kernel to auto load modules as necessary. This used to be kerneld in the older kernels. This might make sense for somethings and especially to less technical people and newbies since you don't need to explicitly figure out what modules to load. Apparently, the 2.6 kernel seems to load modules much more easily than the old 2.4 kernel used to. I'm not 100% sure what triggers the alsa driver to be loaded before the alsascript, but i have an idea that it may be due to PNP support.
By setting CONFIG_KMOD you force the kernel to not ever autoload modules. If you want a module loaded, do it yourself via modprobe, or /etc/modules.autoload.d/kernel-2.6 or whatever. However if you don't know what you are doing here, you have to take care because no modules are ever autoloaded from the kernel and ou have to figure the modules out yourself. This can get particularly confusing if you build alot of things as modules. |
|
| Back to top |
|
|
warthog
Tux's lil' helper
Joined: 11 Aug 2003
Posts: 82
Location: Seattle (Eastside)
|
| Posted: Thu Feb 26, 2004 5:07 am Post subject: Re: CONFIG_KMOD |
|
|
| Quote: | | CONFIG_KMOD allows the kernel to auto load modules as necessary. This used to be kerneld in the older kernels. This might make sense for somethings and especially to less technical people and newbies since you don't need to explicitly figure out what modules to load. <...> However if you don't know what you are doing here, you have to take care because no modules are ever autoloaded from the kernel and ou have to figure the modules out yourself. This can get particularly confusing if you build alot of things as modules. |
Thanks for the great information! However, I'm stuck wondering if it's better to leave automounting up to the kernel or to leave it up to the autoload file in /etc? I've already got a working 2.4.22 gentoo-sources system with autoload.d and hotplug. BTW, does this CONFIG_KMOD in the gentoo-dev-sources have any implication in regards to using hotplug?
thanks! |
|
| Back to top |
|
|
dopey
Apprentice
Joined: 10 Feb 2003
Posts: 235
|
| Posted: Sat Feb 28, 2004 4:02 pm Post subject: Re: CONFIG_KMOD |
|
|
| warthog wrote: |
Thanks for the great information! However, I'm stuck wondering if it's better to leave automounting up to the kernel or to leave it up to the autoload file in /etc? I've already got a working 2.4.22 gentoo-sources system with autoload.d and hotplug. BTW, does this CONFIG_KMOD in the gentoo-dev-sources have any implication in regards to using hotplug?
thanks! |
So I still believe that on a locked down, properly administered system, the right way to go (if you use modules) is to only load modules explicitly specified somewhere (or dependencies if required). However, I'm lazy, and on my desktop systems (and laptop, hell even my server) I now use KMOD 
I don't think KMOD has any affect on hotplug. hotplug is still capable of autodetecting and loading the proper modules I believe.
btw, the problem originally reported in this thread should be fixed by the new alsaound script int he alsa-utils package.
PORTAGE_DIR/media-sound/alsa-utils/files/alsasound is the new version. either re-emerge alsa-utils or just copy the new one to /etc/init.d/alsasound. |
|
| Back to top |
|
|
|
Kernel & Hardware
