RE: [SLE] Problem compiling vanilla SuSe 8.0 kernel on Vaio - hangson reboot - with cloneconfig!
![](https://seccdn.libravatar.org/avatar/934606839d54342f98a04a348bcb7e03.jpg?s=120&d=mm&r=g)
On Tue, 2002-11-19 at 17:33, Richard.Foley@ubsw.com wrote:
IMHO cloneconfig doesn't do what it says it does.
So - just for clarification, my typical process is to go into a vanilla SuSE linux dir and type the following:
cd /usr/src/linux-2.4.18.SuSE make mrproper make cloneconfig make menuconfig # <- _change_ to crusoe processor _only_! make dep clean bzImage modules modules_install cp arch/i386/boot/bzImage /boot/vmlinuz.rjsf mk_initrd -k vmlinuz.rjsf -i initrd.suse /
Which modules do you need in the initrd. I don't seem to see any at all here, so AFAICS this would create an initrd consisting only of the splash screen graphics
I'm perfectly happy to concede I have done this wrong somewhere, _but_, when I recompiled my kernel 2 weeks ago (5 times), I never came across mk_initrd at all, and this is a bit of a surprise to me - so far. Anyway - um, /etc/sysconfig/kernel has 'reiserfs' as the only module listed under INITRD_MODULES, which I thought was where mk_initrd gets it's info from? Am I supposed to do something else, at this point? Richard Foley Ciao - shorter than Aufwiedersehen -- ps. sorry about the ubs sig. (below) - can't get rid of it, for the moment :-\ Visit our website at http://www.ubswarburg.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments.
![](https://seccdn.libravatar.org/avatar/72ee3b9e0735cf98a1e936a90fc087ed.jpg?s=120&d=mm&r=g)
On Tue, 2002-11-19 at 18:10, Richard.Foley@ubsw.com wrote:
I'm perfectly happy to concede I have done this wrong somewhere, _but_, when I recompiled my kernel 2 weeks ago (5 times), I never came across mk_initrd at all, and this is a bit of a surprise to me - so far.
Anyway - um, /etc/sysconfig/kernel has 'reiserfs' as the only module listed under INITRD_MODULES, which I thought was where mk_initrd gets it's info from?
Yes, you're right, I'm sorry. I read the message too fast.
Am I supposed to do something else, at this point?
I think you're right in your second mail that the problem is that your root file system is encrypted. You will need to have the modules for the encryption either compiled into the kernel or in the initrd, plus you'll need some sort of kernel parameters to tell the system how to decrypt it, but I don't know the details. I've never had the root file system encrypted, to be honest I didn't even think it was possible
participants (2)
-
Anders Johansson
-
Richard.Foley@ubsw.com