Being a Linux user for many years I'm in that increasingly small percentage that likes to roll their own kernel. Only, I'm not any more. Each time I want a new feature (recently, ipchains, LS120 drive, SB sound, and more) I recompile. Enough is enough. I'm going to do what everybody else does: use the SuSE one. My question is, how do I go about using it? Last night I moved my kernel to one side and used Yast to select a SuSE boot kernel. I put the SMP modules package in (after moving mine aside in /lib/modules). All well and good, I ran LILO, rebooted and the SuSE kernel came up - and then paniced. No SCSI support, so it can't find my boot partition. Clearly I've missed a step somewhere. What causes the SuSE kernel to spot devices like SCSI adaptors and pull in support for them? -- 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/
I got a kermnal panick , and added the mem=32m to lilo. Have you tried to add the modules so they autamaticly load ? At 12:36 PM 3/24/2000 +0000, Derek Fountain wrote:
Being a Linux user for many years I'm in that increasingly small percentage that likes to roll their own kernel. Only, I'm not any more. Each time I want a new feature (recently, ipchains, LS120 drive, SB sound, and more) I recompile. Enough is enough. I'm going to do what everybody else does: use the SuSE one.
My question is, how do I go about using it? Last night I moved my kernel to one side and used Yast to select a SuSE boot kernel. I put the SMP modules package in (after moving mine aside in /lib/modules). All well and good, I ran LILO, rebooted and the SuSE kernel came up - and then paniced. No SCSI support, so it can't find my boot partition.
Clearly I've missed a step somewhere. What causes the SuSE kernel to spot devices like SCSI adaptors and pull in support for them?
-- 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/
No, I suppose that's my question. If the root partition is on a SCSI disk, and the kernel doesn't know about SCSI (which it doesn't because SCSI is compiled as a module) how can it even start to load that module? Wasn't there something to do with RAMDisks at boot time?
I got a kermnal panick , and added the mem=32m to lilo. Have you tried to add the modules so they autamaticly load ?
At 12:36 PM 3/24/2000 +0000, Derek Fountain wrote:
Being a Linux user for many years I'm in that increasingly small percentage that likes to roll their own kernel. Only, I'm not any more. Each time I want a new feature (recently, ipchains, LS120 drive, SB sound, and more) I recompile. Enough is enough. I'm going to do what everybody else does: use the SuSE one.
My question is, how do I go about using it? Last night I moved my kernel to one side and used Yast to select a SuSE boot kernel. I put the SMP modules package in (after moving mine aside in /lib/modules). All well and good, I ran LILO, rebooted and the SuSE kernel came up - and then paniced. No SCSI support, so it can't find my boot partition.
Clearly I've missed a step somewhere. What causes the SuSE kernel to spot devices like SCSI adaptors and pull in support for them?
-- 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/
Replying to myself here, but I've solved the problem and it's something that made me say "Coo, that's pretty clever! I never knew that...". It's well summed up in the support database: http://sdb.suse.de/sdb/en/html/initrd.html Derek Fountain wrote:
No, I suppose that's my question. If the root partition is on a SCSI disk, and the kernel doesn't know about SCSI (which it doesn't because SCSI is compiled as a module) how can it even start to load that module?
Wasn't there something to do with RAMDisks at boot time?
I got a kermnal panick , and added the mem=32m to lilo. Have you tried to add the modules so they autamaticly load ?
At 12:36 PM 3/24/2000 +0000, Derek Fountain wrote:
Being a Linux user for many years I'm in that increasingly small percentage that likes to roll their own kernel. Only, I'm not any more. Each time I want a new feature (recently, ipchains, LS120 drive, SB sound, and more) I recompile. Enough is enough. I'm going to do what everybody else does: use the SuSE one.
My question is, how do I go about using it? Last night I moved my kernel to one side and used Yast to select a SuSE boot kernel. I put the SMP modules package in (after moving mine aside in /lib/modules). All well and good, I ran LILO, rebooted and the SuSE kernel came up - and then paniced. No SCSI support, so it can't find my boot partition.
Clearly I've missed a step somewhere. What causes the SuSE kernel to spot devices like SCSI adaptors and pull in support for them?
-- 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/
-- 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/
participants (2)
-
fountai＠hursley.ibm.com -
samelash＠ix.netcom.com