[Yaird-devel] Bug#336993: [sto@debian.org: Re: Unable to boot with debian kernel 2.6.15]

Sven Luther sven.luther at wanadoo.fr
Sun Feb 12 21:42:58 UTC 2006


----- Forwarded message from Sergio Talens-Oliag <sto at debian.org> -----

Date: Sun, 12 Feb 2006 16:24:28 +0100
From: Sergio Talens-Oliag <sto at debian.org>
To: debian-powerpc at lists.debian.org
Subject: Re: Unable to boot with debian kernel 2.6.15
Message-ID: <20060212152428.GA18402 at uv.es>
Mail-Followup-To: debian-powerpc at lists.debian.org

El Sun, Feb 12, 2006 at 10:45:06AM +0100, Wouter Lueks va escriure:
> It's been some time since I updated my kernel.  I'm currently using a
> self-compiled 2.6.12 kernel.  It thought it was time to check out the
> stock debian kernels since the seemed to be working very good for a lot
> of people.
> 
> So I went ahead and installed the debian kernel and hoped it would boot. 
> However, no matter what I try I keep getting the following error:
> 
> "VFS: unable to mount root fs on unknown-block(0,0)"
> 
> The root-fs is XFS, and the xfs module is included in the initrd module. 
> I couldn't find any major differences with other yaboot.conf files, so
> I'm a bit at a loss on how to solve this.

This is caused by a known bug on yaboot and XFS that afects initrd images
build using initramfs and yaird (the old mkinitrd images DO work, though).

The bug is not assigned to yaboot, but I've found a that includes an
explanation:

  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=336993

I solved the issue making a small ext3 /boot partition to put my initrd there
and now standard kernels work (I'm using initramfs right now); luckily I made
a 1Gb swap partition when I first installed the machine and was able to split
that one in two instead of reinstalling.

Greetings,

  Sergio.

-- 
Sergio Talens-Oliag <sto at debian.org>   <http://people.debian.org/~sto/>
Key fingerprint = 29DF 544F  1BD9 548C  8F15 86EF  6770 052B  B8C1 FA69



----- End forwarded message -----





More information about the Yaird-devel mailing list