You are not logged in.
Pages: 1
I am using my old thinkpad with a pentium M cpu ,it's stuck at udev for almost 10s evey time i boot the system .Is it normal ?
when i use opensuse ,it takes about 1 or 2s at starting udev .Is it because arch is an i686 optimized kernel ? I remember When I was using fedore 8 i686 ,it was the same case . How much time does udev takes on your machines ?
Do not use Linux as desktop.
Offline
Compare the whole boot time, not udev.
In the past it was faster, but a daemon was taking care of some function that later moved to udev, so the delay was in this daemon, not in udev. Simply, the delay moved to a sooner state of the system, making everything more consistent.
Offline
precisely it's the Loading udev uevents step ,not udev . Yeah it not takes a lot time during the whole process .
According to Pajaro's reply ,that's to say everyone is the same as me ?
Last edited by lovat (2008-01-04 18:12:15)
Do not use Linux as desktop.
Offline
that's to say everyone is the same as me ?
no, but you're not alone
I had this problem too when I switched from ipw3945 to iwlwifi. Removing my custom network rule (to avoid device name swapping) solved my problem.
Offline
Maybe recompile my kernel should be work ,anyone has better suggestions ?
Do not use Linux as desktop.
Offline
it's stuck at udev for almost 10s every time i boot the system .Is it normal ?
I sympathize with your agony... udev's uevents loading times make me want to use a static /dev again (well, almost...). After heavy research and some hacking I found out that I could shrink my Satellite M70's boot time from ~1min to <30 sec (grub to login prompt) just by doing these:
- disable module autoloading in rc.conf
- use the output of hwdetect --modules for the MODULES section in /etc/mkinitcpio.conf and disable all other hooks but "base", then rebuild the kernel images
Also (and this is the most interesting part), I found out that including ipw2200 in the image made the computer stall and take forever to boot!! This happens with the install CD as well and udev is also significantly slower if required to load the dreaded module, btw. However, if you modprobe it by hand, it loads instantly. Any clue as to why this happens (bug, maybe)?
Offline
simply add
ipw2200
to
/etc/rc.conf
MODULES=(...)
Offline
simply add
ipw2200
to
/etc/rc.conf
MODULES=(...)
Precisely, although I wasn't asking for the solution, I already had done that. The question was why it takes so much time to load ONLY if included in the kernel image.
And another thing, these lines creeps me out :
/etc/start_udev - line 121:
udev_uevents () {
# configure all devices
trigger_device_events
# until we know how to do better, just wait for _all_ events to finish
wait_for_queue
}
Offline
i remember when i recompiled my kernel, removing everything i didnt need, i got my boot time from 30s+ down to about 15 seconds.
I also noticed after doing this, the time it took for udev to finish seemed much less, i dont know if the above has any effect on it?
Offline
for me boot time difference with or without udev i 1s. I guess if you clean kernel and remove all unused stuff, there is not much for udev to detect
Offline
for me boot time difference with or without udev i 1s. I guess if you clean kernel and remove all unused stuff, there is not much for udev to detect
You are right. I did not recompile my kernel (but will eventualy try to), but just "forbiding" udev to load any module whatsoever cut my boot time in half.
Offline
i put it on background by adding a '&' at the end of line 77 of /etc/rc.sysinit like this-->status "Loading UDev uevents" /etc/start_udev uevents &
Last edited by btgo (2008-01-15 11:10:10)
Offline
Woah woah woah do NOT background udev. Please, for the love of god, don't start editing things if you don't know what they do.
By backgrounding this, you tell the rest of the script to carry on no matter what hardware is loaded at the time. This means that the rest of the script that mounts your drives and things like that may fail because the modules aren't loaded yet.
Offline
I am using my old thinkpad with a pentium M cpu ,it's stuck at udev for almost 10s evey time i boot the system .Is it normal ?
when i use opensuse ,it takes about 1 or 2s at starting udev .Is it because arch is an i686 optimized kernel ? I remember When I was using fedore 8 i686 ,it was the same case . How much time does udev takes on your machines ?
I have this same "issue".
Offline
Woah woah woah do NOT background udev. Please, for the love of god, don't start editing things if you don't know what they do.
By backgrounding this, you tell the rest of the script to carry on no matter what hardware is loaded at the time. This means that the rest of the script that mounts your drives and things like that may fail because the modules aren't loaded yet.
Oh, sorry, i shouldnt tell this.....i know it, but it's ok for me, i will undo the file it if it's fail, then not to do so for the rest of us.
Offline
Woah woah woah do NOT background udev.
Man, was that scary or what?(try reading it and looking at the avatar immediately )
In some other thread, we were also having some udev related discussion (wich wasn't the original topic, btw).
Maybe some people would like to read it.
Offline
Pages: 1