![](https://seccdn.libravatar.org/avatar/861b5545c111d2257fa12e533e723110.jpg?s=120&d=mm&r=g)
The 02.11.19 at 17:33, Richard.Foley@ubsw.com wrote:
IMHO cloneconfig doesn't do what it says it does.
It doesn't claim to do anything about modules in the initial ramdisk :-)
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
No real need for that: only if you install new sources. Also, I'd edit the Makeconfig file, and put something in the "EXTRAVESION", for example: EXTRAVERSION = _RJFS This way, your new kernel modules stay differentiated from the original, and they do not overwrite.
make cloneconfig make menuconfig # <- _change_ to crusoe processor _only_! make dep clean bzImage modules modules_install
Already clean :-)
cp arch/i386/boot/bzImage /boot/vmlinuz.rjsf mk_initrd -k vmlinuz.rjsf -i initrd.suse /
Er... I wouldn't touch initrd.suse. You could use initrd.rjfs. And I do that by editing the mk_initrd file itself, so that I don't ever forget.
lilo
lilo entry as follows: image = /boot/vmlinuz.rjsf label = rf root = /dev/hda2 vga = 788 initrd = /boot/initrd
This is not the same initrd.suse you wrote above.
append = "ide=nodma apm=off acpi=off ide2=0x180,0x386 mem=256M"
result: read_super_block: bread failed (dev 03:02, block 8, size 1024) Kernel panic: VFS: Unable to mount root fs on 03:02
This takes 1.5 hours, to find out ...sigh...!
No wonder... after a clean, or worse, a mrproper, it takes that long. The second time is faster if you skip that. -- Cheers, Carlos Robinson