You are not logged in.
Pages: 1
This message is the attempt to address the udev uevents issue.
With fast computers the udev uevents loads in a few seconds while slower computers such as a p2 could take perhaps up to a minute to load. That issue has been posted at the bugs and such talks about it have been posted at this board going back a few years now.
Some old messages at this board that provide a temporary workaround for this issue, no longer tends to working for Archlinux-i686-2007.08-2.core.iso by leaving the arch boot up process in a critical condition. The alternative is the custom kernel to decrease the lag. However, the custom kernel does not seem to be worth the time and effort as a slow computer can take a very long time (5+ hours) to build (as I have discovered) but this of course depends on the method used and there is also the study factor.
Here is the udev uevents lag bug report.
Reported Version 2007.08-2
http://bugs.archlinux.org/task/8878
Here is what tends to be the best at current workaround for this issue.
Type at root…
hwdetect –modules
write down all these modules
type at root…
nano rc.conf
inside the rc.conf file, change to…
mod_autoload="no"
then put all the modules that you wrote down, into the modules()
save file then exit
type at root…
nano start_udev
find /sbin/udevsettle
and change to…
/sbin/udevsettle –timeout=2
save and exit.Note: "udev uevents" will not lag for as long but the "mounting root read only" will now tend to lag a bit. However, the overall boot process will be faster but by how much faster will depend on your computer. You could change timeout to 1 but that may crash the computer from time to time.
Although udev uevents can discourage you from arch linux, keep in mind that it is a great distro for learning linux from the ground up. It has pacman that can make it easier for you to install packages and it has KDEmod (KDE on steroids for Arch Linux) that you can get here >>> http://www.kdemod.ath.cx/
Last edited by windoze (2008-01-17 01:39:19)
Offline
If the above explanation does not solve your problem, have a look of this one : http://bbs.archlinux.org/viewtopic.php? … 67#p375667
Offline
Pages: 1