Salix Forums

lmello wrote:Aren't those messages gone when you make an initrd and boot the generic kernel instead?

I am afraid that I do not understand exactly what you mean. Initrd is not for newbies wanting an out-of-the-box working installation and it needs to be rebuilt for every new kernel image cause of the modules included into initrd (although the slack kernel does not change so much often...). So initrd sucks mainly. (I have some experiences with lvm support that needs such an initrd.)
I do not have the test environment for the described behaviour any more, so I've closed the thread to "done". For me, the problem is solved.

damNageHack wrote:Initrd is not for newbies

Yes, I see. Nowadays the very first thing I do after installation is changing to the generic kernel. I always keep the boot entry for the huge kernel on lilo for backup, if anything goes wrong with the initrd. Learned the hard way, AKA the kernel panic path.

lmello wrote:Yes, I see. Nowadays the very first thing I do after installation is changing to the generic kernel.

Why?

lmello wrote:if anything goes wrong with the initrd. Learned the hard way, AKA the kernel panic path.

Look into /usr/share/mkinitrd/ or /usr/share/initrd-tools/ somewhere (depends on the distribution). There should be a script which can suggest you the command line to create a correct initrd.

thenktor wrote:

lmello wrote:Yes, I see. Nowadays the very first thing I do after installation is changing to the generic kernel.

Why?

I need those 5 Mb of RAM!

lmello wrote:I need those 5 Mb of RAM!