search for: iniitrd

...module which later calls > "syslinux_run_command" > 2) the begining of "start_kernel" function > 3) end of kernel load > > As far as I understand the duration between 1 to 2 is bootloader time (am I > wrong?). That sounds reasonable. Time to fetch kernel and iniitrd payload(s) plus set it all up. > Using the custom BIOS: > - it takes ~1.1 seconds for bootloader to finish > - it takes ~0.9 seconds for Linux to finish > > Using the general purpose BIOS: > - it takes ~0.45 seconds for bootloader to finish > - it takes ~0.9 seconds for Linux...

Hi Gene Thanks for your reply.I'm trying to breakdown overall system boot time and to understand each component duration. My linux image is a ~10 MB bzImage file with the rootfs cpio'ed inside. I also have 2 BIOS images:- some general purpose BIOS - a custom BIOS which loads real quick I'm using TSC to measure time. I'm not sure it's the best way (I've read about CPU's

Hi all, I've got a Centos 5.1 kickstart that I must continue to use. How can I update the kick start image so that it recognizes Intel gigabit 82576 nic? BTW, I compiled the driver I need and have this igb.ko file. How do I incorporate that into my initrd.img file that I see on the kickstart CD that is probably my kickstart boot OS. Thank you very much in advance. aurf -

...module which later calls > "syslinux_run_command" > 2) the begining of "start_kernel" function > 3) end of kernel load > > As far as I understand the duration between 1 to 2 is bootloader time (am I > wrong?). That sounds reasonable. Time to fetch kernel and iniitrd payload(s) plus set it all up. > Using the custom BIOS: > - it takes ~1.1 seconds for bootloader to finish > - it takes ~0.9 seconds for Linux to finish > > Using the general purpose BIOS: > - it takes ~0.45 seconds for bootloader to finish > - it takes ~0.9 seconds for Linux...

...; "syslinux_run_command" >> 2) the begining of "start_kernel" function >> 3) end of kernel load >> >> As far as I understand the duration between 1 to 2 is bootloader time (am I >> wrong?). > > That sounds reasonable. Time to fetch kernel and iniitrd payload(s) > plus set it all up. > >> Using the custom BIOS: >> - it takes ~1.1 seconds for bootloader to finish >> - it takes ~0.9 seconds for Linux to finish >> >> Using the general purpose BIOS: >> - it takes ~0.45 seconds for bootloader to finish >&g...

...; "syslinux_run_command" >> 2) the begining of "start_kernel" function >> 3) end of kernel load >> >> As far as I understand the duration between 1 to 2 is bootloader time (am I >> wrong?). > > That sounds reasonable. Time to fetch kernel and iniitrd payload(s) > plus set it all up. > >> Using the custom BIOS: >> - it takes ~1.1 seconds for bootloader to finish >> - it takes ~0.9 seconds for Linux to finish >> >> Using the general purpose BIOS: >> - it takes ~0.45 seconds for bootloader to finish >&g...

..." >>> 2) the begining of "start_kernel" function >>> 3) end of kernel load >>> >>> As far as I understand the duration between 1 to 2 is bootloader time (am I >>> wrong?). >> >> That sounds reasonable. Time to fetch kernel and iniitrd payload(s) >> plus set it all up. >> >>> Using the custom BIOS: >>> - it takes ~1.1 seconds for bootloader to finish >>> - it takes ~0.9 seconds for Linux to finish >>> >>> Using the general purpose BIOS: >>> - it takes ~0.45 seconds...

..." >>> 2) the begining of "start_kernel" function >>> 3) end of kernel load >>> >>> As far as I understand the duration between 1 to 2 is bootloader time (am I >>> wrong?). >> >> That sounds reasonable.? Time to fetch kernel and iniitrd payload(s) >> plus set it all up. >> >>> Using the custom BIOS: >>> - it takes ~1.1 seconds for bootloader to finish >>> - it takes ~0.9 seconds for Linux to finish >>> >>> Using the general purpose BIOS: >>> - it takes ~0.45 seconds...