You are not logged in.
Hi !
back to arch, from Ubuntu, because I wanted more speed...
I managed to get pretty much everything working, not without difficulties ...
btw the forum is great !!
still, I am a bit confused about the correct way to load modules at startup
here is my setup :
mkinitcpio with beyond kernel
in rc.conf :
MOD_AUTOLOAD="yes"
MODULES=(ipw3945 !r1000 evdev)
DAEMONS=(syslog-ng !hotplug !hwd !pcmcia ipw3945d network netfs crond alsa)
nothing in modprobe.conf
with that, am I using hwd (think no), hwdetect, udev ?
tried to switch off MOD_AUTOLOAD and putting all modules loaded in MODULES but without any success
once again, everything is working for the moment, it's more because I'm curious and I understand the lack of info about this as mkinitcpio is new (or maybe I didn't find the info :? )
Thanks
Offline
MOD_AUTOLOAD uses udev. You certainly can list all your modules in the MODULES=() array, although how much speed increase you'd get is.. questionable.
By the way, none of this really has anything to do with mkinitcpio
I am a gated community.
Offline
ok thank you for the quick reply
so i'm up and running with arch ! yeepie 8)
Offline
actually I think MOD_AUTOLOAD uses hwdetect (written by a dev) which uses udev events to load hardware. do hwdetect --help to see all available options.
Offline
Perhaps I've gotten this all wrong, but I thought that udev was used with MOD_AUTOLOAD and hwdetect only when building the mkinitcpio image.
Offline
Perhaps I've gotten this all wrong, but I thought that udev was used with MOD_AUTOLOAD and hwdetect only when building the mkinitcpio image.
Woah, you're mixing like 5 technologies here.
a) mkinitcpio - this runs at boot time. It is called "early userspace". mkinitcpio ONLY affects the stuff that happens before you get the colored text on bootup. As soon as you see the colored text, mkinitcpio is done.
b) hwdetect - this is no longer used. Everything is done via simple modalias dereferences.
c) udev - yes this is used in early-userspace, but that is unimportant. The udev you care about runs at boot time (normal userspace). It uses the settings in rc.conf to properly load your modules (i.e. blacklisted modules).
d) MOD_AUTOLOAD - allows udev to load modules. Without this, udev does very little.
e) MODULES array - loaded before udev begins loading modules. Use this to control load order if it is an issue.
Offline
actually I think MOD_AUTOLOAD uses hwdetect (written by a dev) which uses udev events to load hardware. do hwdetect --help to see all available options.
No, MOD_AUTOLOAD is used for the udev module loader - it's /lib/udev/load-modules.sh IIRC
Offline
Wow, I never realized exactly how all of this stuff worked. It's just always 'just worked' here so it's never been an issue.
Offline
once again, everything is working for the moment, it's more because I'm curious and I understand the lack of info about this as mkinitcpio is new (or maybe I didn't find the info :? )
I hope it's not really lacking, this document is HUGE (thanks mostly to brain0):
http://wiki.archlinux.org/index.php/Mkinitcpio
Offline