Re: kernel panic

[developer@wexwarez.com]

>>>I am dual booting xp and linux on a single harddrive.  I got both booting
>>>with xp controlling the mbr and I added my linux grub bootsector to the
>>>xp
>>>boot.ini in order to get linux to boot.  I installed debian off the sarge
>>>net install cd using the 2.6 kernel.  The kernel that came with it runs
>>>fine, but I compiled and installed a new kernel and it will not run. 
>>>When
>>>I boot to it, it complains :
>>>VFS: Cannot open root device "hda3" or unknown-block(0,0)
>>>Please append a correct "root=" boot option
>>>Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0)
>>>
>>>By the way:
>>>/dev/hda3 is /
>>>/dev/hda6 is boot
>>>
>>>The auto generated boot options in grub are as follows(the top two work,
>>>the bootom don't):

>>>title           Debian GNU/Linux, kernel 2.6.5-1-386
>>>root            (hd0,5)
>>>kernel          /vmlinuz-2.6.5-1-386 root=/dev/hda3 ro
>>>initrd          /initrd.img-2.6.5-1-386
>>>savedefault
>>>boot

>>>title           Debian GNU/Linux, kernel 2.6.5-1-386 (recovery mode)
>>>root            (hd0,5)
>>>kernel          /vmlinuz-2.6.5-1-386 root=/dev/hda3 ro single
>>>initrd          /initrd.img-2.6.5-1-386
>>>savedefault
>>>boot
>>>
>>>title           Debian GNU/Linux, kernel 2.6.5
>>>root            (hd0,5)
>>>kernel          /vmlinuz-2.6.5 root=/dev/hda3 ro
>>>savedefault
>>>boot
>>>
>>>title           Debian GNU/Linux, kernel 2.6.5 (recovery mode)
>>>root            (hd0,5)
>>>kernel          /vmlinuz-2.6.5 root=/dev/hda3 ro single
>>>savedefault
>>>boot


>>>Might this have something to do with the no initrd option?
>>>I thought debian boot loaders used the whole vmlinuz vmlinuz.old
>>>scenario,
>>>is there a way to make this work?
> On Mon, May 24, 2004 at 08:59:21AM -0700, developer@wexwarez.com wrote:
>> >
>> You are correct, the 2.6.5 is the new one.
>> I did not use any flags I just did a make-kpkg kernel_image and a dpkg
>> -i
>> I noticed that the new boot loader menu items didn't have the initrd
>> lines, is that required.  I didn't think you really needed to use
>> initrd?
>>
>
>
>   In general, depending on the kernel configuration, you can do without
> an initrd. However since the configuration of the new kernel doesn't
> differ much from the old one, it could be that you must have an initrd
> because essential components are compiled as modules. Another option is
> that for your hardware the difference in the configuration of the old
> and new kernels is important.
>   The new boot loader menu items didn't have the initrd lines because it
> identified the new kernel as not requiring an initrd. Which is correct
> since you didn't make-kpkg --initrd.
>
> --
> "If you have an apple and I have  an apple and we  exchange apples then
> you and I will still each have  one apple. But  if you have an idea and I
> have an idea and we exchange these ideas, then each of us will have two
> ideas." -- George Bernard Shaw     (sent by  shaulk @ actcom . net . il)
>

So what you are saying is that what I did is fine?  So why do I get this
kernel panic error???