You are not logged in.
Hi all,
I'm just new to the Arch world after running Debian and Gentoo for 3 years and I think I found the distro I was looking for. Anyway, I'd like to speed up a little this boot as I did for gentoo with initng for example. I read some interesting informations on hwdetect which can replace hotplug so I did it Anyway it works (seems to by the way ) but as Arch boots, I still get these lines about my hardware you know, just before Arch Linux "logo" appears and then all the scripts indicating done when they did their task. I thought these lines were providing by hotplug but since I "replace" it with hwdetect, I don't understand from where they come Which script/program ?
Offline
Well, the init process will still say "Loading Modules" when it loads the modules found in your MODULES=() array and executes hwdetect. (just check out rc.sysinit, around line 252)
As for any other such messages, the daemons 'hotplug' and 'hwd' both autoload hardware; make sure they're not in your DAEMONS array.
Offline
These lines are after the lines I talk about. Those are just after choosing Arch in Grub. It can be informations from kernel but it sounds strange to me (it takes 5-6s on my P4 3.2) I always thouht they were from hotplug or coldplug.
Offline
If I understood correctly what lines you are referring to, they come from the kernel which is booting up.
Offline
I think you're right. I didn't think it was taking so much time to boot up kernel
Offline
I think you're right. I didn't think it was taking so much time to boot up kernel
It also takes a few seconds on my Pentium M 1.7GHz. You could try the initrd kernel in testing with a custom initrd26.img. It's smaller than the one in [current] repo so it should boot faster. To do so, enable the testing repo in /etc/pacman.conf. Also it would be better to move it at the end of the other repo if you don't want to use the other packages in testing. Then:
# pacman -Sy testing/kernel26
# pacman -Sy testing/mkinitrd
Don't forget to read the instructions in the wiki.
Offline
you can pass "quiet" as a kernel parameter to get rid of all that info.
Offline
thank you snowman but I use ck sources so I don't know if I can make an initrd easily with your tool. I didn't try but it sounds good anyway
Offline
thank you snowman but I use ck sources so I don't know if I can make an initrd easily with your tool. I didn't try but it sounds good anyway
If you compile your own kernel, then initrd won't be much of use as you probably already compile the kernel with only the HD controllers/ filesystems you need. As I use the stock kernels, the new initrd kernel in testing let me get a relatively custom kernel without the hassle of compiling my own.
Offline
@snowman
I compile my own kernel, can I completely remove initrd?
The ultimate Archlinux release name: "I am your father"
Offline
You shouldn't need initrd if you have a properly compiled custom kernel.
oz
Offline
@snowman
I compile my own kernel, can I completely remove initrd?
Like snowman said, if you compile your HD controllers and filesystem module into the kernel, you don't need initrd.
Offline