Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
PPC 64 boot: Cannot open root device [SOLVED]
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Gentoo on PPC
View previous topic :: View next topic  
Author Message
CondorDes
n00b
n00b


Joined: 28 Apr 2003
Posts: 7
Location: San Luis Obispo, CA, USA

PostPosted: Thu Jun 15, 2006 12:57 am    Post subject: PPC 64 boot: Cannot open root device [SOLVED] Reply with quote

Hi all --

This is my first time doing a ppc64 installation (onto an Apple G5 workstation), and I'm having one issue I can't seem to figure out. I've searched through the Gentoo forums, and on Google, but haven't had any luck.

When I boot the machine from its hard disk, it gives me the following error message:

Code:
VFS: Cannot open root device "sda4" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
 <0>Rebooting in 180 seconds..


Some notes:

  • sda is the first (and only) Serial ATA drive in the machine. I know the machine finds the (physical) disk, because it lists it earlier in the dmesg output.
  • sda4 is an ext3 filesystem.
  • The kernel is configured with the following (all of these are compiled in, not modules):

    • The K2 SATA driver
    • Mac partition tables
    • The Ext3 filesystem

  • I checked, and all the device files are in the right place in /dev on the root filesystem (without udev or devfs or anything like that running).


Here is my yaboot.conf, which I adapted from /etc/yaboot.conf.example and the ppc64 installation instructions:

Code:
## Example yaboot.conf for ybin and yaboot >= 0.6
## see man yaboot.conf for more details.

## Change `unconfigured' to your bootstrap partition eg: /dev/hda2
boot=/dev/sda2

## device is the OpenFirmware device path to the disk containing
## kernel images.  if your disk is /dev/hda you can find the
## OpenFirmware path by running the command: ofpath /dev/hda DO NOT
## specify a partition number for this!  On IBM hardware you can
## generally comment this out.

device=hd:

## partition is the partition number where the kernel images are
## located.  The kernel images should be on your root filesystem, so
## this is usually the same partition number as your root filesystem.
## so if root = /dev/hda3 (the 3rd partition) then you should have
## partition=3  This *MUST* be set correct or yaboot won't boot!  This
## option can be either set globally as shown here, or per image in
## the image= sections

partition=4

## delay is the amount of time in seconds the dual boot menu (if one
## is configured, by the presense of macos, macosx, etc options here)
## will wait before choosing the default OS (GNU/Linux or the value of
## defaultos=).  If you omit this then the value of timeout=
## (converted to seconds) will be used.

delay=10

## timeout is the amount of time in tenths of a second that yaboot
## will wait before booting the default kernel image (the first image=
## section in this config file or the value of default=). 

timeout=40
install=/usr/lib/yaboot/yaboot
magicboot=/usr/lib/yaboot/ofboot

## Change the default colors, fgcolor is the text color, bgcolor is
## the screen background color. (default: fgcolor=white, bgcolor=black)
#fgcolor=black
#bgcolor=green

## Password supplied in plaintext, required for yaboot to boot, unless
## restricted is also present (see below). Be sure to
## chmod 600 /etc/yaboot.conf if you set this!

#password=secret

## Password supplied as an md5 hash, see above

#password=$1$saltstrg$HnJ/gcM3oKhNbnzUPgXTD/

## A password is only required to boot an image specified here if
## parameters are specified on the command line or if the user enters
## an image is not specified in the configuration file at all (ie.
## arbitrary file load).  restricted can also be placed in an image
## section in that case any image not including the restricted keyword
## will be fully password protected.

#restricted

## image is the kernel itself, commonly kept in / but also commonly
## found in /boot.  Note that /boot should generally not be its own
## partition on powerpcs, its not necessary and complicates things.
## Make sure /boot is on the partition specified by partition= see
## above.  /boot should never be an HFS filesystem.  You may point
## image= to a symbolic link so long as the symlink does not cross
## partition boundries.

image=/vmlinux
   label=Linux
   root=/dev/sda4
   read-only


I'm totally out of ideas at this point. If you have any suggestions as to how I can get this thing booting, I would appreciate it.

-- Des


Last edited by CondorDes on Thu Jun 15, 2006 5:44 pm; edited 2 times in total
Back to top
View user's profile Send private message
corsair
Retired Dev
Retired Dev


Joined: 06 Oct 2003
Posts: 451
Location: Aachen, Germany

PostPosted: Thu Jun 15, 2006 7:20 am    Post subject: Reply with quote

well... normaly that error means that the root file system is not compiled into the kernel.

could you please check that and report back?

regards,

markus
Back to top
View user's profile Send private message
CondorDes
n00b
n00b


Joined: 28 Apr 2003
Posts: 7
Location: San Luis Obispo, CA, USA

PostPosted: Thu Jun 15, 2006 4:03 pm    Post subject: Reply with quote

corsair wrote:
well... normaly that error means that the root file system is not compiled into the kernel.

could you please check that and report back?


The root filesystem (ext3) is compiled in (that is, it's not a module). I just now went back and checked.

(Also edited my initial post to clarify this.)
Back to top
View user's profile Send private message
CondorDes
n00b
n00b


Joined: 28 Apr 2003
Posts: 7
Location: San Luis Obispo, CA, USA

PostPosted: Thu Jun 15, 2006 5:44 pm    Post subject: Reply with quote

Well, that was silly.

Apparently "SCSI disk support" includes SATA disk support, as well. ::headpalm::

It's booting now, sort of. On to the next problem (which probably deserves a separate thread, if I can't figure it out on my own)...
Back to top
View user's profile Send private message
rangerpb
Retired Dev
Retired Dev


Joined: 19 Jan 2005
Posts: 147

PostPosted: Thu Jun 15, 2006 7:30 pm    Post subject: next problem Reply with quote

If you cant figure it out, drop into #gentoo-ppc64 and we'll help!
_________________
-->
rangerpb
<--
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Gentoo on PPC All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum