You are not logged in.
I having a problem, or a question...
Having a rather fast computer, and a little bit tweaked system.
Linux boots on under 20 sec, and X starts very quickly, when it start.
But i have some kind of delay before X starts to load. I see the login prompt for about 5-10 seconds before it starts to load.
I start X with "x:5:once:/bin/su USER -l -c "/bin/bash --login -c startx -nolisten tcp >/dev/null 2>&1"" in inittab and "exec awesome" in.xinitrc. The delay is about the same time if i start X with kdm as an deamon.
I am using the nvidia driver, if it matter.
Both "init 5" and startx starts X very fast, so it seems like it takes time to switch to runlevel 5...
Where shall i start looking for the delay?
Last edited by JaQoB (2008-03-16 22:27:09)
Offline
I know you shouldn't bump, but i really want an soulution
My deamons:
DAEMONS=(@syslog-ng !network @net-profiles !netfs @crond @hal @openntpd @laptop-mode @alsa)
Any more information i can give?
Last edited by JaQoB (2008-03-27 11:15:35)
Offline
@ @ @ @ ...
The delay may simply be those backgrounded processes all trying to start at once, and thrashing the hard disk
Also, loading the kernel modules for alsa may require a pause, I think.
So, is the hard drive active during the 5-10 seconds?
Offline
@ @ @ @ ...
The delay may simply be those backgrounded processes all trying to start at once, and thrashing the hard disk
Also, loading the kernel modules for alsa may require a pause, I think.
So, is the hard drive active during the 5-10 seconds?
Very active indeed. And putting alsa in the beginning of the row cut around 2 sec of the delay.
Thanks for the answer! Not much to do i guess? Wait for better disks...
Offline
My deamons:
DAEMONS=(@syslog-ng !network @net-profiles !netfs @crond @hal @openntpd @laptop-mode @alsa)
Can you actually start everything like that in background without experiencing any problems?
Offline
Some of them can be gotten away with. It's all about timings and dependencies, and also how important those dependencies are.
E.g. it's advisable to do a time-sync before starting the logger, so the logger has the right time. But not critical.
hal needs dbus, but luckily /etc/rc.d/hal will itself *start* dbus if required.
Ideally, both the CPU & hard drive will both be kept fully-occupied throughout the boot process.
Offline
JaQoB wrote:My deamons:
DAEMONS=(@syslog-ng !network @net-profiles !netfs @crond @hal @openntpd @laptop-mode @alsa)
Can you actually start everything like that in background without experiencing any problems?
No problems yet, after 3-4 months
Offline
Mine's even worse
DAEMONS=(syslog-ng @alsa @cpufreqd @network @netfs @crond @cups @mpd @laptop-mode !vmware !httpd !mysqld)
Haven't been here in a while. Still rocking Arch.
Offline
My biggest concern was about kdm starting before hal, and the possible problems with that: I think I'll go background though, just because I can!
Mine's even worse
DAEMONS=(syslog-ng @alsa @cpufreqd @network @netfs @crond @cups @mpd @laptop-mode !vmware !httpd !mysqld)
you don't start hal at all?
Offline