Hello everybody
I'm facing with a dilemma:
Usually I compile for myself the kernel for my laptop.
with the last kernel 2.6.34 I had the following problem

After the compilation and installation of the image and header and the consequently update of the menu.lst the kernel boot normally.
After some days I removed the old kernel the routine update automatically again the menu.lst file, but this time at the next reboot the kernel remain stuck on the usb as if there weren't the module or the initramfs!!!
Then I checked the file log and the file menu.lst
the weird thing is that this kernel work when in the menu.lst is not present the row initrd inittr-2.6.34......etc...
But why it doesn't work when I spcify the initram file??? and if there is not need of this row why at each modification of the kernel the installation program update and add this row??

Thank you to everyone who can explain me this

piccir

hi

while you are waiting for a better reply ....try running a diff application against your old and new kernel config files you should see in /boot.
(I like xxdiff as it provides nice colours)

I am thinking maybe usb module.

2) I may have misunderstood so when you get a chance do you mean.....for your menu
initrd /boot/initrd inittr-2.6.34.gz......fails
delete initrd line........................succeeds?

Yes, is This what I mean.
In the past the first time that I compiled the kernel I miss that line and clearly the kernel was unable to boot because the module were in initramfs, but now it's weird, it works if don't put that line

piccir

sorry for late reply

well all that is happened....is you compiled enough stuff into kernel NOT to need an initial ram disk image.

Lots of distros have no initrd...so its not a new concept.

Obviously you could go to extremes and have no modules as well....but that leaves you with one big kernel.

The minimum you need not to use an initrd is all drivers needed to access your system....the partition format, network and in your case usb

Altho there is no doc I can find quickly to describe NOT using initrd here is the reason for using it
http://www.faqs.org/docs/Linux-HOWTO...#create_initrd

So on a booted system.....ignoring kernels "inbuilt" run lsmod and see if rebuilding to inbuild those modules helps?

Thank you for your reply
What I'm still confusing is:
I compiled some parts in the kernel (for example to have less trouble like static in the kernel: ext2 ext3) and others like modules (for example iwl3945, rtl..., and other stuff).
IN the ramdisk It should be the modules required at boot time... ok maybe I don't need because all these modules are built in my kernel....
But how to know if I need or not of the initram??
Thank you
piccir

well what you need in your kernel is stuff to access your keyboard, mouse, hard partition if no initrd (basically) and the other stuff can wait for modules to load.

If you look at /etc/init.d/ rcS.....compile anything needed in there such as your network card.

To say it again....boot a kernel with an initrd....then run lsmod....note want modules you need.....compile the kernel to compile "in" = (not module) the hardware support you need.....if it boots you are sweet....if it does not boot you have missed out your partition Kernel bit most likely

Why don't you just try creating versions and make notes of whats changed between each kernel build?