Hi, Kevin Thanks for the reply :) > What type of filesystem is your "root" partition? fd --> Linux Raid Autodetect > Is all of the necessary support for this fs compiled into your kernel? Well, the old kernel boots. I haven't changed the .config I used make oldconfig The command #diff .config .config.old --> returns nothing > If not, did you remake the proper initrd.img file for your new kernel so > that it contains the proper modules for your root partition? initrd.img is something I'm not familiar with. Byt the kernels are the same > The chronology is the following: > > System BIOS determines the active partition and loads and executes the > boot loader. Yes. > The system boot loader knows where to find the Linux kernel image, how > to load it, and to de-compress it if necessary. The problem is that the two kernels are exactly the same. And the old boots, the new don't !!! >This kernel image needs > to contain the necessary file systems builtin to it in order to find and > mount the root partition so that it can load any necessary modules > needed to complete your system boot up. This is OK > If (like RedHat) your boot loader boots an initial RamDisk image, this > image can contain copies of various modules needed for the kernel image > to load so that it has all the necessary modules it needs to find/load > the root file system. When it mounts the root partition, it unmounts > the initial ramdisk and your system boot then continues "normally". I'm not sure about this. I use Slackware. > Is this clear enough? Yes :), thanks a lot! Something I found is: 09:00 is NOT the SCSI disk. It's SCSI Tape! The other kernel reads from 08:00 (or something). Why this kernel tries 09:00? How can I change this? Thanks again for replay help is appriciated Greetings Ralica Kirilova - : send the line "unsubscribe linux-admin" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
