Re: Re: faster boots?

Re: Re: faster boots?

[joeja]

Think pre init scripts....

no apache was install on this machine, no iptables scripts, etc.

I'm actually talking about the time from where Linux spits out all this crap about probing irq's, ide drive found with dma etc.  That kind of stuff.  

I'm not sure if there is an issue because I use the Linux framebuffer and all those printk() are taking to much time to print? To much scrolling or  redraw?  Is there any way to turn all that off (without commenting that code out)?

It would be nice to test if that is an issue.  FreeBSD does not seem to spit out all that crap.  It is more like 1 or 2 lines a device not this 30 lines of irq mapping and 4 lines of thank you to so and so and foo for the code of blah....   

If the video card is old and slow, could all this extra stuff that scrolls up the screen be causing the issue?  If so is there a way of turning this off?    


Joe

On Fri, 5 Apr 2002 01:21:17 +0100 (BST) Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:

>     Is there some way of making the linux kernel boot faster?  

#1: Start less crap at boot time. Obvious but thats frequently most of
    the issue.

For Red Hat if your hardware set up is constant then rpm -e kudzu will do
no harm and avoid the grovelling through the box looking for new toys.

Longer term swsuspend means you can bang alt-sysrq-Z and suspend to disk
without BIOS support

Re: Re: faster boots?

[Alan Cox]

> If the video card is old and slow, could all this extra stuff that scrolls up the screen be causing the issue?  If so is there a way of turning this off?    

Boot with the "quiet" option to quieten messages. (I think its quiet anyway)

Re: Re: faster boots?

[dean]

[-- Attachment #1: Type: text/plain, Size: 507 bytes --]

> > If the video card is old and slow, could all this extra stuff that
> > scrolls up the screen be causing the issue?  If so is there a way of
> > turning this off?
>
> Boot with the "quiet" option to quieten messages. (I think its quiet
> anyway)

Yes, just add the line:
append="quiet" to the correct section in your lilo.conf to have the
initial bootup messages turned off.  You can still access these messages
via dmesg of course.

HTH and HAND.

- Dean

ps Alan (sorry for the cc to you - I slipped;)

[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]

Re: faster boots?

[Helge Hafting]

joeja@mindspring.com wrote:
> 
> Think pre init scripts....
> 
> no apache was install on this machine, no iptables scripts, etc.
> 
> I'm actually talking about the time from where Linux spits out all this crap about probing irq's, ide drive found with dma etc.  That kind of stuff.

Compile your own kernel with drivers only for hardware you
actually have and use during boot.  Omit all other drivers.  That gets
rid
of a lot of probing, and the time from "kernel loaded" to "starting
init"
gets quite short.  Also, some drivers lets you specify irq's etc.
on the kernel command line - that may avoid further probing.

Drivers for things not needed in the kernel boot process (cdrom, floppy, 
ethernet, etc.) can be made modular.  That avoids time-consuming cd
spinup
and probing of non-boot devices.

The kernel boot is only a few seconds on my office machine.  The bios
boot is one long delay, the initscripts another.

Helge Hafting

Re: faster boots?

[Thomas 'Dent' Mirlacher]

improving kernel bootup time:

	what about saving the parameters for successfully loaded modules?
	(like the IRQs and other stuff which gets autodetected.)
	- and when those modules are loaded for the second time, the
		saves values will be used, without the need to do
		autoprobing (don't know how much time that will
		save, but it should save quite some time for people
		having all the drivers in the kernel, but no matching
		hardware)
		- this will only work if there are no static inits,
			but everything's modularized (which should
			be in the works?)
	- also you need to have a parameter to reprobe the whole modules


- this would also give a nice template for building a customized kernel
(well again for people who are not really used to do things like that)

	just my $0.02

		tm

-- 
in some way i do, and in some way i don't.

Re: faster boots?

[Luigi Genoni]

What is really noisy is the scsi boot on some server, when you have 4 or
more disks and some other stuff, like on some of my sparc64.
Sometimes It can happen that a reboot asks some minute just for all scsi
and fibbre stuff. If you have MC^2 and some logical volume around on it,
it can be really noisy, especially if you are in a hurry, as always
when it comes to production servers :(.

On desktop PC kernel boot is hardly a problem, the real
slowdown are the init script, but then every distribution
has its own (slower or faster).

On Fri, 5 Apr 2002, Helge Hafting wrote:

> joeja@mindspring.com wrote:
> >
> > Think pre init scripts....
> >
> > no apache was install on this machine, no iptables scripts, etc.
> >
> > I'm actually talking about the time from where Linux spits out all this crap about probing irq's, ide drive found with dma etc.  That kind of stuff.
>
> Compile your own kernel with drivers only for hardware you
> actually have and use during boot.  Omit all other drivers.  That gets
> rid
> of a lot of probing, and the time from "kernel loaded" to "starting
> init"
> gets quite short.  Also, some drivers lets you specify irq's etc.
> on the kernel command line - that may avoid further probing.
>
> Drivers for things not needed in the kernel boot process (cdrom, floppy,
> ethernet, etc.) can be made modular.  That avoids time-consuming cd
> spinup
> and probing of non-boot devices.
>
> The kernel boot is only a few seconds on my office machine.  The bios
> boot is one long delay, the initscripts another.
>
> Helge Hafting
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>