Hello, on a 5.3 CD there are SCSI kernel images in suse/images. I can't find them in the 6.3 release on the Ftp-server. They aren't either on a FreeX Suse 6.3 demo CD. I have built the kernel by hand. But in case I'm in a hurry I'de appreciate the SCSI images. Won't they be include in future releases? Is it intended to build the kernel by hand on a `profi'-box? Hanspeter -- -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
* Hanspeter Roth Bsag (roth@bsag.ch) [20000106 10:06]:
I can't find them in the 6.3 release on the Ftp-server. They aren't either on a FreeX Suse 6.3 demo CD.
The boot concept has changed with 6.3. Have a look at our online support
database at http://sdb.suse.de/en/html , keyword initrd.
In a nutshell: starting from 6.3, our kernels use the initial ramdisk to
load modules needed for booting. If you build your own kernel and want to
use that feature, you have to compile the support for ramdisk and initial
ramdisk into your kernel.
Add the line
initrd=/boot/initrd
to /etc/lilo.conf in the global section if it's not already there.
Edit /etc/rc.config and look for the line
INITRD_MODULES=
Add any needed module here, like
INITRD_MODULES="aic7xxx"
Save the file and call /sbin/mk_initrd, this will build the initrd. Call
/sbin/lilo and at the next boot the modules will get loaded.
--
Philipp Thomas
What is the advantage whith RAM-disk support compiled into the kernel? Is this something I as an ordinary user can benefit from?
>>>>>>>>>>>> Ursprungligt meddelande <<<<<<<<<<<<<<<<<<
Philipp Thomas
* Hanspeter Roth Bsag (roth@bsag.ch) [20000106 10:06]:
I can't find them in the 6.3 release on the Ftp-server. They aren't either on a FreeX Suse 6.3 demo CD.
The boot concept has changed with 6.3. Have a look at our online support database at http://sdb.suse.de/en/html , keyword initrd.
In a nutshell: starting from 6.3, our kernels use the initial ramdisk to load modules needed for booting. If you build your own kernel and want to use that feature, you have to compile the support for ramdisk and initial ramdisk into your kernel.
Add the line
initrd=/boot/initrd
to /etc/lilo.conf in the global section if it's not already there.
Edit /etc/rc.config and look for the line
INITRD_MODULES=
Add any needed module here, like
INITRD_MODULES="aic7xxx"
Save the file and call /sbin/mk_initrd, this will build the initrd. Call /sbin/lilo and at the next boot the modules will get loaded.
-- Philipp Thomas
If God had meant us to be brave, why did he give us legs ?
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Hi Anders, * Anders Dahlqvist (dahlqvist@sundsvall.mail.telia.com) [20000106 19:08]:
What is the advantage whith RAM-disk support compiled into the kernel? Is this something I as an ordinary user can benefit from?
If you compile your own kernels, it depends. For us it had tremendous effect
in that it allowed us to cut down the number of kernels from about 28 to 5.
Of which one is a Pentium optimised one.
The benefit for a normal user IMO are:
1) no need to recompile the kernel for new hardware (if basic support has
been compiled into).
2) For older machines with no PnP support in BIOS, it would allow you to
run isapnp before loading the module. But this would be a bit more tricky
and not so easily achivable as simply adding modules to the initrd.
--
Philipp Thomas
participants (3)
-
dahlqvist＠sundsvall.mail.telia.com -
pthomas＠suse.de -
roth＠bsag.ch