Re: Sarge testing 2.6 boot problems
Hello John. My english is not very good so. I have used for two years debian woody, in this time I have not problems booting 2.4 customized kernels. Some months ago, I have changed to Sarge, and since then, I have not been able to boot 2.6 kernels, with problems very similars to those you speak about. I have thought to take care with IDE options during configuration, but it has not been usefull, I cannot boot.Have you solved your problem in some way? Thanks! Jordi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge testing 2.6 boot problems
On Tue, May 18, 2004 at 07:52:02PM -0400, John Kerr Anderson wrote: I've tried installing a custom modularised kernel version 2.6.5 on Debian Sarge testing. I'm using ext3 filesystem and compiled it directly into the kernel along with ReiserFS sypport (I read you need it in order to avoid an initrd image). Everytime it tries to boot the new kernel I get the following error: VFS: Cannot open root device 301 on unknown-block(3,1) Please append a correct root boot option Kernel panic: VFS unable to mount root fs on unknown-block(3,1) This sounds like you forgot to compile in IDE support, or whatever's needed for your disk. -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Sarge testing 2.6 boot problems
Hello, I've tried installing a custom modularised kernel version 2.6.5 on Debian Sarge testing. I'm using ext3 filesystem and compiled it directly into the kernel along with ReiserFS sypport (I read you need it in order to avoid an initrd image). Everytime it tries to boot the new kernel I get the following error: VFS: Cannot open root device 301 on unknown-block(3,1) Please append a correct root boot option Kernel panic: VFS unable to mount root fs on unknown-block(3,1) The hard disk partition used for booting is /dev/hda1 which is specified in Lilo. I originally used Grub and experienced the same exact problem. I've compiled my own kernels before but never 2.6 series and never with this many problems... I seems to be that its some sort of file system error message, but I don't know what. I've tried everything. The motherboard is an Intel 845WN. If anyone can shed some light on this situation I would be very happy! :-) Cheers, John Kerr Anderson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
