Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Problem in the boot
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
locco
n00b
n00b


Joined: 23 Sep 2005
Posts: 5
Location: Malaga - Spain

PostPosted: Fri Sep 23, 2005 7:06 pm    Post subject: Problem in the boot Reply with quote

I am installing in a system Pegasos with G4 1 Ghz and when I choose the options for boot the system stop with this message:

"Calling quiesce..."
"returning 0x00010000 from prom_init"

I need help for install my system.

Sorry for my enghlish

Best regards :D
Back to top
View user's profile Send private message
nixnut
Bodhisattva
Bodhisattva


Joined: 09 Apr 2004
Posts: 10974
Location: the dutch mountains

PostPosted: Fri Sep 23, 2005 7:29 pm    Post subject: Reply with quote

Moved from Installing Gentoo to Gentoo on PPC.
PPC problem, better off here.
_________________
Please add [solved] to the initial post's subject line if you feel your problem is resolved. Help answer the unanswered

talk is cheap. supply exceeds demand
Back to top
View user's profile Send private message
JoseJX
Retired Dev
Retired Dev


Joined: 28 Apr 2002
Posts: 2774

PostPosted: Fri Sep 23, 2005 9:43 pm    Post subject: Reply with quote

You don't have a framebuffer device. PPC requires a framebuffer. On the Pegasos II, it's usually a Radeon, so add radeonfb support to your kernel.
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml
Back to top
View user's profile Send private message
locco
n00b
n00b


Joined: 23 Sep 2005
Posts: 5
Location: Malaga - Spain

PostPosted: Sat Sep 24, 2005 9:32 am    Post subject: Reply with quote

I have NVidia, but if yu said thas is better I can get a ATI
Back to top
View user's profile Send private message
JoseJX
Retired Dev
Retired Dev


Joined: 28 Apr 2002
Posts: 2774

PostPosted: Sat Sep 24, 2005 9:58 pm    Post subject: Reply with quote

No, I didn't suggest one was better than the other (although there is better driver support for 3D with Radeon on PPC). What you need to do is include some sort of graphical framebuffer support. For nvidia, either use OpenFirmware FB, RivaFB or nVidiaFB depending upon which works best for you.
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml
Back to top
View user's profile Send private message
firekopf
n00b
n00b


Joined: 30 Nov 2004
Posts: 31

PostPosted: Thu Oct 06, 2005 1:39 am    Post subject: Reply with quote

I get the same message when I start up with the 2.6.12 kernel. My lspci output lists my graphics card as:

Code:
0000:00:12.0 VGA compatible controller: ATI Technologies Inc 3D Rage Pro 215GP (rev 5c)


what frame buffer device should I include in the kernel?

Thanks in advance.
Back to top
View user's profile Send private message
JoseJX
Retired Dev
Retired Dev


Joined: 28 Apr 2002
Posts: 2774

PostPosted: Thu Oct 06, 2005 1:45 am    Post subject: Reply with quote

I'm pretty sure that's a Mach64, give that a try. If that doesn't work, try the OpenFirmware FB. Make sure that you have the Framebuffer Console enabled as well.
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml
Back to top
View user's profile Send private message
firekopf
n00b
n00b


Joined: 30 Nov 2004
Posts: 31

PostPosted: Sun Oct 09, 2005 10:23 pm    Post subject: Reply with quote

tried what you said and got past the white quiesce screen (woohoo!) but when it went through the normal boot operations it got stuck here:

Code:
VFS: Cannot open root device "hda8" 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.._


Yaboot.conf:

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/hda6

## 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:
root=/dev/hda8
## 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=8

## 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=150

## 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=200
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.

default=Linux

image=/boot/kernel-2.6.9
   label=Linux
   root=/dev/hda8
   read-only
   sys-map=/boot/System.map-2.6.9

image=/boot/kernel-2.6.12
   label=Test
   root=/dev/hda8
   read-only
   sys-map=System.map-2.6.12

#image=/boot/kernel-2.6.12a
#   label=Test2
#   root=/dev/hda8
#   read-only
#   sys-map=System.map-2.6.12a

enablecdboot
enableofboot
macos=/dev/hda5
defaultos=Linux


My yaboot.conf seems set up right, so why is it not recognizing the root device?
Back to top
View user's profile Send private message
KeyserZero
n00b
n00b


Joined: 21 Mar 2005
Posts: 68

PostPosted: Mon Oct 10, 2005 2:40 pm    Post subject: Reply with quote

Have you installed the right file-system type into the Kernel?
Back to top
View user's profile Send private message
Sleipnir
Guru
Guru


Joined: 20 Sep 2005
Posts: 372
Location: Germany

PostPosted: Mon Oct 10, 2005 2:48 pm    Post subject: Reply with quote

@firekopf:
I don't know if this is the same problem, but have a look here!
_________________
A)bort, R)etry, I)nfluence with large hammer.
Back to top
View user's profile Send private message
firekopf
n00b
n00b


Joined: 30 Nov 2004
Posts: 31

PostPosted: Sat Oct 15, 2005 6:51 pm    Post subject: Reply with quote

I think I fixed it. The kernel was set to think the hard drive was scsi based and not ata based, which it was. The kernel boots now.

Thanks for the help!
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