You know when you boot into Slack, you always got a lot of messages like:

....................
INIT: Entering run level : 4
Going : multiuser ....

PCI: Enabling device 0000 : 02 : 0a.0 ( 0004 -> 0005 )

starting syklogd daemons : /usr/sbin/syslogd ..........
..................................

Ok, from bold start up statement ( PCI: bla bla bla ) to next start up statement ( starting sysklogd ..... ), it takes 4-5 seconds. That is too long for me. What's wrong ? What is all about ? What is that device that need 4 seconds to be enabled ?

Thank you.

cat /proc/pci
should give you an idea of what's inside your box....
Take a look at the info that gives you and see if you can find the "offending" hardware card there...

4 to 5 sekonds doesn't sem like that much of a bother to me...
How long does it take you from you power on yor pc and the loginscreen is up?
Depending on if it checks the ram or not it takes between 50 seconds and 90 seconds to me..

$ cat /proc/pci
PCI devices found:
Bus 0, device 0, function 0:
Host bridge: Intel Corp. 82850 850 (Tehama) Chipset Host Bridge (MCH) (rev 2).
Prefetchable 32 bit memory at 0xf8000000 [0xfbffffff].
Bus 0, device 1, function 0:
PCI bridge: Intel Corp. 82850 850 (Tehama) Chipset AGP Bridge (rev 2).
Master Capable. No bursts. Min Gnt=8.
Bus 0, device 30, function 0:
PCI bridge: Intel Corp. 82801BA/CA/DB/EB PCI Bridge (rev 4).
Master Capable. No bursts. Min Gnt=6.
Bus 0, device 31, function 0:
ISA bridge: Intel Corp. 82801BA ISA Bridge (LPC) (rev 4).
Bus 0, device 31, function 1:
IDE interface: Intel Corp. 82801BA IDE U100 (rev 4).
I/O at 0xb800 [0xb80f].
Bus 0, device 31, function 2:
USB Controller: Intel Corp. 82801BA/BAM USB (Hub #1) (rev 4).
IRQ 9.
I/O at 0xb400 [0xb41f].
Bus 0, device 31, function 3:
SMBus: Intel Corp. 82801BA/BAM SMBus (rev 4).
IRQ 10.
I/O at 0xe800 [0xe80f].
Bus 0, device 31, function 4:
USB Controller: Intel Corp. 82801BA/BAM USB (Hub #2) (rev 4).
IRQ 9.
I/O at 0xb000 [0xb01f].
Bus 1, device 0, function 0:
VGA compatible controller: nVidia Corporation NV20 [GeForce3 Ti 200] (rev 163).
IRQ 11.
Master Capable. Latency=248. Min Gnt=5.Max Lat=1.
Non-prefetchable 32 bit memory at 0xee000000 [0xeeffffff].
Prefetchable 32 bit memory at 0xf0000000 [0xf7ffffff].
Prefetchable 32 bit memory at 0xef800000 [0xef87ffff].
Bus 2, device 10, function 0:
Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 7).
IRQ 11.
Master Capable. Latency=32. Min Gnt=2.Max Lat=20.
I/O at 0xd800 [0xd81f].
Bus 2, device 10, function 1:
Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 7).
Master Capable. Latency=32.
I/O at 0xd400 [0xd407].
Bus 2, device 12, function 0:
Ethernet controller: D-Link System Inc RTL8139 Ethernet (rev 16).
IRQ 10.
Master Capable. Latency=32. Min Gnt=32.Max Lat=64.
I/O at 0xd000 [0xd0ff].
Non-prefetchable 32 bit memory at 0xed800000 [0xed8000ff].

I cann't read this. So what is that device? Ok, from the moment I choose Slackware in Grub Menu until I reach GDM, I need 31-32 seconds. What makes me sad that My Windows need 21-23 seconds to reach login screen.

What do you think????

the command lspci (as root) would probably help you identify the device.

I understand your wanting a snappy boot up, but I suspect you are going to use up a lot of 4 seconds getting to the bottom of this!

tobyl

As tobyl said..
fixing those 4 sec will take you a lot of time..
And i guess lspci is the best bet too...
Anyway, why are those 4 seconds so important?

On my setup the only way to get it to boot faster wuld be to:
A) Remove 1 gig ram
B) Remove Ip-tables and the rules...
C) remove all other modules etc. from the kernel that has to do with networking...

*isn't doing any of them*

you found 4 seconds a lot? I found this important message about syslogd you should read it, will found out why it takes those eternal for you 4 or 5 seconds to continue. after reading this, it should take 10 or 15 seconds really to continue. here is the link.

http://www.cert.org/security-improve...s/i041.08.html

syslogd is a daemon as far as i saw, only available under BSD systems, solaris and macos x, and of course slack try to be so Unix like that import this option too. The reason i think windows boot up faster than Linux/Unix is cause windows don't check in his boot, for new hardware detection, don't mount partition by partition, don't begin to run daemons before boot to the x-windows, besides that, windows boot up everything when it log in to his x-window and have all automatically, but linux had all separate and had to detect thing by thing. Maybe this is a stupid answer or this it's not the reason why, but that's what i guess out it could be.

It is Multimedia audio controller: Creative Labs SB Live! EMU10k1. I don't understand. Well, actually I can beat Windows boot time by choosing light window manager like xfce.

Thanx guyz!!!

Of course you could use a lower boot up window manager like fluxbox, icewm, xfce4 (which i use) cause KDE and Gnome load a lot of plugins, libs, qt3 objects (which take like double time always to find, like when you configure a apps that's need qt3 saw that take like 30 seconds to find qt3 stuff) a lot of daemons, etc. Even if you use a lower x-windows manager like xfce or flux linux will still take more time to boot than windows for the reason i told you and i think that might be, remember that x-windows system under linux is separate from the rest of the OS not the same way happends under windows which have everything integrated.

If you don't whant more syslogd run when it boot ups your linux, just uncomment it out you could edit rc.local for that or you could do this in /etc/rc.d

chmod -x rc.syslogd

and voila that should stop syslogd daemon at boot up.

I would also think that you shouldn't need to reboot all that often. If you're running Linux on a laptop, then Yes, you may regularly reboot a couple of times a day, but for a desktop system, and assuming you turn off the PC at night, you should only need to reboot once a day when you first power on. (If you leave your PC running continuously then obviously you can go weeks/months without a reboot).

My point is simply that if your system is rebooting so frequently that a 4 second delay becomes an issue, then perhaps you've got other more significant issues to solve than waiting for 4 seconds. Just my 2 cents -- J.W.

I remember that when I was Fedora user, people in fedora irc channel told me that not to disable syslogd startup service because when shit happens, this will help you. Right????

As you read in the link i post before, syslogd save kernel message of all process daemons and hardware detection in some extra files, so yes it's important to know why kernel gives error message and why happends weird boot up hardware. it takes those eternal 4 seconds cause it's saving or searching for all kernel message that it received.