Re: Kernel panic when using linux-image-2.6.16-1-686 with a PATA drive
On Sun, 2006-04-09 at 14:30 +0200, Florian Kulzer wrote:
> Ron Johnson wrote:
> > The root device is PATA drive hda, but there is also a SATA drive
> > in the system.
> >
> > I've Googled this, but no joy. Must be searching for the wrong
> > strings.
> >
> > Currently running linux-image-2.6.14-1-686, which seems to be working
> > fine. Sound, mouse, boot speed, etc all normal.
> >
> > $ uname -a
> > Linux haggis 2.6.14-1-686 #1 Tue Nov 1 15:51:43 JST 2005 i686 GNU/Linux
> >
> > $ cd /boot
> > $ dir *2.6.16*686
> > -rw-r--r-- 1 root root 652659 Apr 3 09:31 System.map-2.6.16-1-686
> > -rw-r--r-- 1 root root 67112 Apr 3 07:40 config-2.6.16-1-686
> > -rw------- 1 root root 1128474 Apr 8 13:07 initrd.img-2.6.16-1-686
> > -rw-r--r-- 1 root root 1145551 Apr 3 09:31 vmlinuz-2.6.16-1-686
> >
> > $ grep hda /etc/lilo.conf
> > boot=/dev/hda
> > root=/dev/hda2
> >
> > The error:
> > RAMDISK: Couldn't open root device "302" or unknown-block(3,2).
> > Please append a correct "root=" boot option
> > Kernel panic - not syncing: VFS: Unable to mount root fs or unknown-
> > block(3,2)
> >
> > Has something radical changed between 2.6.14 & .16?
>
> That might be a problem with your initrd image for 2.6.16. There are (at
> least) two different packages for initrd creation, initrd-tools and
> yaird. Sometimes it is enough to just switch to the one that you did not
> use before.
The issue is moot for me now, because I built my own kernel that
has the vital chipset/ide/etc routines compiled into the kernel.
And it's still smaller than the stock images.
--
-----------------------------------------------------------------
Ron Johnson, Jr.
Jefferson, LA USA
"Politics [is] the art of achieving the maximum amount of freedom
for individuals that is consistent with the maintenance of social
order."
Senator Barry Goldwater (R-AZ)
Reply to: