Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[SOLVED] OF parameters and yabootconfig
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
Gustav IV
n00b
n00b


Joined: 10 Jan 2007
Posts: 69
Location: Copenhagen

PostPosted: Wed Jan 10, 2007 12:41 pm    Post subject: [SOLVED] OF parameters and yabootconfig Reply with quote

Hi everyone

I have tried to install Gentoo on a G5 but ran out of luck at the yabootconfig stage. After issuing a yabootconfig command, I am met with the error that yabootconfig cannot find mac-fdisk. So the process quits. Obviously being mount on the different diectories, and in chroot mode, mac-fdisk became unreachable.

I am also trying to install Gentoo on a second SATA disk, while MacOSX resides on the first: Upper and lower, "a" and "b", and therefore I am using dev/sdb1, for the map partition, dev/sdb2 for the Appleboot strap, dev/sd3 for swap, dev/sdb4 for root and dev/sdb5 for home.

The porblem occurs when tying to manually create a yaboot configuration, where OF writes something like hd:1. But isn't that sda1 to you and me?? Can you write hdb:1 in OF?

looking for your help,

Gustav
_________________
"Hey, hey, hey — don't be mean. No need to be mean. 'Cause, remember: no matter where you go... there you are." - Buckaroo Banzai


Last edited by Gustav IV on Tue Mar 06, 2007 2:15 pm; edited 1 time in total
Back to top
View user's profile Send private message
nixnut
Bodhisattva
Bodhisattva


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

PostPosted: Wed Jan 10, 2007 4:35 pm    Post subject: Reply with quote

Moved from Installing Gentoo to Gentoo on PPC.
you can use ofpath to find out the OF paths (or just peek at the devalias output in OF)
_________________
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
pindar
Apprentice
Apprentice


Joined: 30 Apr 2004
Posts: 220

PostPosted: Thu Jan 11, 2007 11:04 am    Post subject: Re: OF parameters and yabootconfig Reply with quote

Gustav IV wrote:

The porblem occurs when tying to manually create a yaboot configuration, where OF writes something like hd:1. But isn't that sda1 to you and me?? Can you write hdb:1 in OF?


If you're referring to the "device=XXX" line in yaboot.conf: I had trouble with it too; then a helpful soul here told me to just comment it out. This has worked for me.

HTH

Thomas
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 Jan 11, 2007 3:03 pm    Post subject: Reply with quote

Please take a look in the handbook section about manual yaboot configuration

if you cannot provide a valid value for hd: or hd:1 you can use the Open Firmware path instead. If this for example doesn't work for you (example taken from my powerbook, but g5 is the same):

Code:

...
device=hd:
...


then you would do something like this:

Code:

...
device=/pci@f4000000/ata-6@d/disk@0:
...


you can get the open firmware path with the ofpath tool:

Code:

$ ofpath /dev/hda
/pci@f4000000/ata-6@d/disk@0:


same for /dev/hda1:

Code:

$ ofpath /dev/hda1
/pci@f4000000/ata-6@d/disk@0:1


regards,

-corsair
Back to top
View user's profile Send private message
Gustav IV
n00b
n00b


Joined: 10 Jan 2007
Posts: 69
Location: Copenhagen

PostPosted: Fri Jan 12, 2007 7:19 am    Post subject: Reply with quote

Thanks for the great tips everyone. I will be working on this configuration this coming weekend.

But one thing that I am curious about, is the missing mac-fdisk while in chroot mode, and running yabootconfig. Is this a common problem or should the Handbook be updated in some way? Could an emerge mac-fdisk command provide access to the miss piece of the puzzle?

I should point out here that my intention is to boot directly from second hard-disk at the computer start-up while holding down the option key and selecting the Gentoo disk instead of the MacOSX disk. Should there be a default setting point to the MacOSX system in the yaboot config or could I safe side step this?

thanks!
_________________
"Hey, hey, hey — don't be mean. No need to be mean. 'Cause, remember: no matter where you go... there you are." - Buckaroo Banzai
Back to top
View user's profile Send private message
ndansmith
n00b
n00b


Joined: 01 Aug 2005
Posts: 60

PostPosted: Fri Jan 12, 2007 5:43 pm    Post subject: Reply with quote

Gustav IV wrote:
Thanks for the great tips everyone. I will be working on this configuration this coming weekend.

But one thing that I am curious about, is the missing mac-fdisk while in chroot mode, and running yabootconfig. Is this a common problem or should the Handbook be updated in some way? Could an emerge mac-fdisk command provide access to the miss piece of the puzzle?
Those packages are missing in the chroot because they are not part of Gentoo's stage 3, so yes, you will have to emerge them if you would like to use them inside the chroot. :-)
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: Fri Jan 12, 2007 6:10 pm    Post subject: Reply with quote

Gustav IV wrote:
I should point out here that my intention is to boot directly from second hard-disk at the computer start-up while holding down the option key and selecting the Gentoo disk instead of the MacOSX disk. Should there be a default setting point to the MacOSX system in the yaboot config or could I safe side step this?


yes, you can use a yaboot config, which defaults to macosx. for example:

Code:

...
defaultos=macosx
...
macosx=hd:5
...


-corsair
Back to top
View user's profile Send private message
Gustav IV
n00b
n00b


Joined: 10 Jan 2007
Posts: 69
Location: Copenhagen

PostPosted: Mon Jan 15, 2007 3:28 pm    Post subject: Reply with quote

Well after a morning of hacking I still am not able to create a bootable disk for Gentoo Linux.

I followed all of your helpful advice and cut through alot of configurational impurities. I was also able to emerge mac-fdisk while in the chroot mode, but after running yabootconfig, I ended up with even more questions:

yabootconfig wants a path for a the kernal that it can't find. Why can't it and where is it?

yabootconfig is also looking for a path to the initrd file. Is there one?

yabootconfig then aborts, while stating that it can resolve the configuration under the present conditions, and then asks me if I was running yabootconfig whil in chroot mode instead of yabootconfig --chroot. Baffling.

Regardless, I ran the ofpath command and discovered that the correct path to use as boot device is:
/ht@0,f2000000/pci@7/k2-sata-root@c/k2-sata@1disk@0:

A far cry from "hd:" :lol:

I am still a little concerned with how "ofboot=" should be configured. I recall setting it as ofboot=sdb:2

I ran "mkofboot -v" and it resolved successfully. But to my dismay on the reboot I could not boot the linux disk. There were three options: l for Gnu/Linux, c for cdrom, o for open firmware. Whenever I pressed "l" I was sent back to the screen with the two disks you can boot from.

Could anyone offer me some help with these issues?

Sincerely
Gustav IV
_________________
"Hey, hey, hey — don't be mean. No need to be mean. 'Cause, remember: no matter where you go... there you are." - Buckaroo Banzai
Back to top
View user's profile Send private message
ndansmith
n00b
n00b


Joined: 01 Aug 2005
Posts: 60

PostPosted: Mon Jan 15, 2007 5:10 pm    Post subject: Reply with quote

Gustav IV wrote:
Well after a morning of hacking I still am not able to create a bootable disk for Gentoo Linux.

I followed all of your helpful advice and cut through alot of configurational impurities. I was also able to emerge mac-fdisk while in the chroot mode, but after running yabootconfig, I ended up with even more questions:

1. yabootconfig wants a path for a the kernal that it can't find. Why can't it and where is it?

2. yabootconfig is also looking for a path to the initrd file. Is there one?

yabootconfig then aborts, while stating that it can resolve the configuration under the present conditions, and then asks me if I was running yabootconfig whil in chroot mode instead of yabootconfig --chroot. Baffling.

Regardless, I ran the ofpath command and discovered that the correct path to use as boot device is:
/ht@0,f2000000/pci@7/k2-sata-root@c/k2-sata@1disk@0:

A far cry from "hd:" :lol:

3. I am still a little concerned with how "ofboot=" should be configured. I recall setting it as ofboot=sdb:2

I ran "mkofboot -v" and it resolved successfully. But to my dismay on the reboot I could not boot the linux disk. There were three options: l for Gnu/Linux, c for cdrom, o for open firmware. Whenever I pressed "l" I was sent back to the screen with the two disks you can boot from.

Could anyone offer me some help with these issues?

Sincerely
Gustav IV


1. If you run yabootconfig outside the chroot (i.e. by adding --chroot /mnt/gentoo to the command), you have to specify the absolute path to the kernel image. That would most likely be /mnt/gentoo/boot/kernel-whatever .

2. You also do not need the initrd in most cases (just pressing enter will skip this in yabootconfig).

3. Open firmware does not look at block devices the same way the kernel does. That is, even if your bootstrap partition is /dev/sda2, open firmware will still refer to that as hd:2 (IIRC hd: is open firmware for the first hard drive OF encounters).

Anyhow, I hope that helps.
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: Tue Jan 16, 2007 7:57 am    Post subject: Reply with quote

If you still didn't got it working you might want to join #gentoo-ppc64 on freenode irc or post your yaboot.conf here in the forum.

regards,

-corsair
Back to top
View user's profile Send private message
Gustav IV
n00b
n00b


Joined: 10 Jan 2007
Posts: 69
Location: Copenhagen

PostPosted: Thu Jan 18, 2007 8:28 am    Post subject: Reply with quote

Modedit by corsair: Cleaned the [ code ] segment

Hi again!

here is the yaboot.conf file i have as chroot and mounted on the different directories proscribed in the manual:

Code:

#etc/yaboot.conf
#

boot=/dev/sdb2

ofboot=sdb:2

device=/ht@0,f2000000/pci@7/k2-sata-root@c/k2-sata@1/disk@0:

delay=5

defaultos=linux

timeout=60

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

image=/boot/linux-2.6.17-gentoo-r5
      label=Linux
      root=/dev/sdb4
      partition=4
      read-only

enablecdboot
enableofboot


I find no examples within "(chroot) Livecd/#", where etc/yaboot.conf and etc/yaboot.unconfigured were completely blank.

Although I did find some examples while in the non-(chroot) mode, and wrote out the preceeding code in accordence by hand.

I hope this helps and that it will clearify were any errors can be found.

looking forward to an orderly boot,

Gustav IV
_________________
"Hey, hey, hey — don't be mean. No need to be mean. 'Cause, remember: no matter where you go... there you are." - Buckaroo Banzai
Back to top
View user's profile Send private message
Gustav IV
n00b
n00b


Joined: 10 Jan 2007
Posts: 69
Location: Copenhagen

PostPosted: Thu Jan 18, 2007 8:31 am    Post subject: Reply with quote

Wow that post looked like a dogs breakfast!

Of course the last paragraph is not code, but the part that looks like code is. (Sorry that was the first time I tried to post code.)

Gustav IV
_________________
"Hey, hey, hey — don't be mean. No need to be mean. 'Cause, remember: no matter where you go... there you are." - Buckaroo Banzai
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 Jan 18, 2007 8:49 am    Post subject: Reply with quote

I've corrected the [ code ] segment in your post. basicly you didn't open with [ code ] and closed with [ / code ], but the other way around and the java script closed once more.. 8)

your yaboot.conf looks almost correct, but only almost.. please change the following lines, which are marked:

Code:

#etc/yaboot.conf
#

boot=/dev/sdb2

# old: ofboot=sdb:2
ofboot=/ht@0,f2000000/pci@7/k2-sata-root@c/k2-sata@1/disk@0:2     <- this should be correct

device=/ht@0,f2000000/pci@7/k2-sata-root@c/k2-sata@1/disk@0:

delay=5

# old: defaultos=linux
defaultos=macosx       <- this should boot directly to macosx as you said in a few posts before

timeout=60

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

image=/boot/linux-2.6.17-gentoo-r5
      label=Linux
      root=/dev/sdb4
      partition=4
      read-only

macosx=/dev/sda3    <- please change as needed

enablecdboot
enableofboot


then boot the live cd again, mount /proc /dev and /sys, chroot into your install and run: mkofboot -v

regards,

-corsair
Back to top
View user's profile Send private message
Gustav IV
n00b
n00b


Joined: 10 Jan 2007
Posts: 69
Location: Copenhagen

PostPosted: Thu Jan 18, 2007 2:24 pm    Post subject: Reply with quote

Hi Corsair

Thanks for your kind help. Unfortunately none of the re-coding broke through to a bootable image, although I think I am a little closer to a solution. The ofboot parameter you gave me was a relief. But when I rebooted the same thing happened again, and in the Open Firmware dialogue there appeared a new choice: x macosx. I pressed "l" for GNU/Linux and I am immediately sent back to the drive selection screen. Just as before.

You also mentioned something that made me a little uneasy: "mount /sys" I have never mounted /sys before and I don't know how to do so with the correct configurations, -t? -o? -bind?. Should I have been mount on /sys in the first place?

However I now suspect a botched up etc/fstab configuration. The instructions regarding /boot on i386 systems and which is not needed on an Apple PowerPC are confusing because the given examples are only for configuring i386 architectures. The instructions state that Apple computers do not need a /boot partition. So how do you configure dev/sdb2, which in this case is the Apple Bootstrap partition, in etc/fstab. I basically left it out.

Also, is there a way to copy and paste the etc/fstab configuration and post it here? :)

Perhaps the following is a topic for a another post:
How does the yaboot bootloader play against the BootX in the start procedures for the G5? When in OS X I cannot see the second harddisk with its
HFS partition in System Preferences, therefore I cannot select it as the boot disk. I hope these descriptions can help you understand what I am trying to achieve. It should alos be noted here that unless I hold the option key down on the reboot or or start-up, MacOSX is immediately invoked. There is no other operative selection screen.

Thanks again!

Sincerely
Gustav IV
_________________
"Hey, hey, hey — don't be mean. No need to be mean. 'Cause, remember: no matter where you go... there you are." - Buckaroo Banzai
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: Fri Jan 19, 2007 8:01 am    Post subject: Reply with quote

Gustav IV wrote:
You also mentioned something that made me a little uneasy: "mount /sys" I have never mounted /sys before and I don't know how to do so with the correct configurations, -t? -o? -bind?. Should I have been mount on /sys in the first place?


I mount it, because it cannot hurt :wink: . I just did a quick search and there are nvram related files in /dev, /proc and /sys, so mounting /sys seems wise:

Code:

G5 ~ # find /proc/ -name "*nvram*"
/proc/device-tree/aliases/nvram
/proc/device-tree/nvram@0,fff04000
/proc/device-tree/options/nvramrc
/proc/device-tree/options/use-nvramrc?
/proc/device-tree/chosen/nvram
G5 ~ # find /sys/ -name "*nvram*"
/sys/class/misc/nvram
G5 ~ # find /dev/ -name "*nvram*"
/dev/nvram
/dev/.udev/db/class@misc@nvram
G5 ~ #


to mount /sys into your chroot execute the following command:

Code:

mount -o bind /sys /mnt/gentoo/sys


Gustav IV wrote:
However I now suspect a botched up etc/fstab configuration. The instructions regarding /boot on i386 systems and which is not needed on an Apple PowerPC are confusing because the given examples are only for configuring i386 architectures. The instructions state that Apple computers do not need a /boot partition. So how do you configure dev/sdb2, which in this case is the Apple Bootstrap partition, in etc/fstab. I basically left it out.


yes, that's correct. that partition is basicly an hfs formated partition so that open firmware can load the kernel.

Gustav IV wrote:
Also, is there a way to copy and paste the etc/fstab configuration and post it here? :)


no need I think.

I'm out of knowledge. I'll ask ranger (another PowerPC64 developer, who knows everything you can imagine. and if he doesn't, then he knows how to find out 8) ), if he can take a look at this topic.

regards,

-corsair
Back to top
View user's profile Send private message
rangerpb
Retired Dev
Retired Dev


Joined: 19 Jan 2005
Posts: 147

PostPosted: Sat Jan 20, 2007 2:31 pm    Post subject: yaboot Reply with quote

At first glance, the yaboot.conf looks ok. I personally haven't configured a system where the botostrap and such were on the second disk. I think you are on to something there where you say you have to force the yaboot load with the special key combination.

Suppose you temporarily unplug the disk with OSX on it and just work in getting Linux to boot. That would isolate if it's a configuration problem.

I truely think you should join us in on irc as corsair suggested. You have better luck of running across someone with a similar configuration.
_________________
-->
rangerpb
<--
Back to top
View user's profile Send private message
Gustav IV
n00b
n00b


Joined: 10 Jan 2007
Posts: 69
Location: Copenhagen

PostPosted: Mon Jan 22, 2007 7:26 pm    Post subject: Reply with quote

Howdy Ranger and Corsair

I worked on getting a bootable Gentoo this past weekend, and tried to tweek things according to Corsair's advice. Basically it worked...somewhat:

I mounted /sdb4 /sdb5 /dev /proc /sys, then chroot to the new system. I even created a new kernel and copied it to /boot, checked the etc/fstab, it looked right. I then checked etc/yaboot.conf and tweeked the ofpath to macosx, and then I ran mkofboot -v to effect the mount environment that now included /sys.

After a reboot, something different happened and I thought I finally broke through:

Ranger Rick is right hold the "option key/alt key" down while I reboot, this brings up a grey screen with Icons of bootable media from which you can select. This time it was the Linux image that was ready to launch, as opposed to the Mac OS X image.

I got past the the OF screen prompt and on to the yaboot prompt....(Yeah!!!)
I hit return to boot...
and I was met with this:
Code:

Welcome to yaboot v. 1.3.13
boot: Linux
Please wait, loading kernel...
/ht@0,f2000000/pci@7/k2-sata-root@c/k2-sata@1/disk@0:4, /boot/linux-2.6.17-gentoo-r5: No such file or directory


8O Ouch!
The of path and partition is correct; and the when ls is invoked on /boot it returns "boot" and "linux-2.6.17-gentoo-r5".
Something is not being connected somewhere. Please check this out.
I'll be able to get on to irc sometime this week.

Thanks for your fine attention,

Gustav IV
_________________
"Hey, hey, hey — don't be mean. No need to be mean. 'Cause, remember: no matter where you go... there you are." - Buckaroo Banzai
Back to top
View user's profile Send private message
Gustav IV
n00b
n00b


Joined: 10 Jan 2007
Posts: 69
Location: Copenhagen

PostPosted: Wed Jan 24, 2007 6:44 pm    Post subject: Reply with quote

Does anyone have any idea why the bootloader can not find the kernal image in /boot on /dev/sdb4, as mentioned in the previous posting?

Gustav IV
_________________
"Hey, hey, hey — don't be mean. No need to be mean. 'Cause, remember: no matter where you go... there you are." - Buckaroo Banzai
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 Jan 25, 2007 8:57 am    Post subject: Reply with quote

what file system do you have on /boot/ ?

and once again: you are welcome to join us at #gentoo-ppc64 on freenode ;-)

-corsair
Back to top
View user's profile Send private message
Gustav IV
n00b
n00b


Joined: 10 Jan 2007
Posts: 69
Location: Copenhagen

PostPosted: Thu Jan 25, 2007 9:51 am    Post subject: Reply with quote

Hi Corsair

I am using Reiserfs on partitions 4 and 5. /boot/linux-2.6.17-gentoo-r5, as well as a copy of vmlinuz, reside on /dev/sdb4.

I did not set any file systems on /dev/sdb1 nor on /dev/sdb2, the Apple partition map, and the Apple_Bootstrap partitions.

I must note here that last night I tried, very aggressively, to force yabootconfig to work on this system. It did work, but it asked where to find the kernal that should be booted. I gave the address of /boot/linux-2.6.17-gentoo-r5 and it returned that no file was found. I then gave the address of the copy in /boot created from /usr/src/linux where the original kernal resides as vmlinux. yabootconfig accepted this kernal and created a new yaboot.conf file with the values generated by Open Firmware
and set mkofboot in motion.

This file it created was not as detailed as expected and the values of boot= were those that ofpath gave me previously. the ofboot line was not generated in this new file.

I rebooted and the yaboot screen came on, I hit "l" for Linux, at the Open Firmware prompt. But alas, I was again met with

Code:
/ht@0,f2000000/pci@7/k2-sata-root@c/k2-sata@1/disk@0:4,/boot/vmlinuz: No such file or diectory


So I didn't win anything by forcing yabootconfig to create a new configuration file. I edited the file with values for ofboot defaultos delay timeout and I can't remember more than those, to resmble the file we earlier talked about.

:sigh:

Although I don't have a lot of experience with this, my instincts tell me that the problem may lay with the Open Firmware I have on my system. When I tried to boot from the o> prompt with the prescribe value for mac osx, "mac-boot" if I remember correctly, then the screen turns grey and does nothing. The only way out is to shut down the system.

This however, maybe the start of a new thread, and although my computer won't boot the Linux kernel, I must admit that the original request for help with Ofboot parameters and yaboot configurations is solved.

I was on line last night but couldn't find much activity on irc #gentoo-ppc, although i met ndansmith there, which was a quaint surprise.

Have a look at what I wrote and send me a reply, if I gave you any more info that may lead to a bootable linux image.

Thanks again Corsair,

Sincerely

Gustav IV
_________________
"Hey, hey, hey — don't be mean. No need to be mean. 'Cause, remember: no matter where you go... there you are." - Buckaroo Banzai
Back to top
View user's profile Send private message
Gustav IV
n00b
n00b


Joined: 10 Jan 2007
Posts: 69
Location: Copenhagen

PostPosted: Wed Feb 07, 2007 11:29 pm    Post subject: Reply with quote

I've now had some time to work on this Gentoo installation project and have come up with some good answers to the question I originally posted.

After picking around Open Firmware, rather cautiously mind you, I stumbled on some fine short cuts to the paths I needed in configuring the yaboot.conf file. In Open Firmware I ran devalias to find the short formed aliases that have eluded me, and which are not found in any Gentoo liturature. Not until now: The situation i have is that I am installing Gentoo on a second hard disk on a G5. This second hard disk turns up with the alias sd1 in OF speak. The first hard disk is aliased as sd0.

Here is a little extract from the file I pulled:

Code:

sata            /ht/pci@7/k2-sata-root
hd              /ht/pci@7/k2-sata-root/k2-sata@0/disk0
ultra0          /ht/pci@7/k2-sata-root/k2-sata@0/disk0
ultra1          /ht/pci@7/k2-sata-root/k2-sata@1/disk0
sd0             /ht/pci@7/k2-sata-root/k2-sata@0/disk0
sd1             /ht/pci@7/k2-sata-root/k2-sata@1/disk0
sd2             /ht/pci@7/k2-sata-root/k2-sata@2/disk0
sd3             /ht/pci@7/k2-sata-root/k2-sata@3/disk0


So the first disk is known to OF as hd, ultra0, or sd0. Take your pick. But as for the second hard disk it's known as sd1 or ultra1.

So now my yaboot.conf file looks like this:

Code:


boot=/dev/sdb2
device=sd1

ofboot=sd1:2

timeout=100
delay=30
defaultos=macosx
install=/usr/lib/yaboot/yaboot
magicboot=/usr/lib/yaboot/ofboot

image=/boot/linux-2.6.17-gentoo-r5
          label=Gentoo
          root=/dev/sdb4
          partition=4
          read-only


Nice, neat and clean.
And it boots when Gentoo is typed at the prompt. :D

But now the bad news: The booting process is hindered by a framebuffer problem that I am now trying to solve. I get this message on a pure glaring white screen:

Code:

done
found display    :     /pci@0,f0000000/ATY,SimoneParent@10/ATY,Simone_B@1, opening...


The G5's fan starting to spin furiously after a short while, a clear indication that something is frozen.
What irks me a little is the last bit in the path: "Simone_B@1" because the alias called "screen" in OF indicates something that looks different:
Code:

screen          /pci@0,f0000000/ATY,SimoneParent@10/ATY,Simone_A@0


Again I am baffled.

Does anyone have any suggestion as to pass a video variable to the boot process, or should there also be one written into the yaboot.conf file?

Thanks a ton!

Sincerely,
Gustav
_________________
"Hey, hey, hey — don't be mean. No need to be mean. 'Cause, remember: no matter where you go... there you are." - Buckaroo Banzai
Back to top
View user's profile Send private message
Gustav IV
n00b
n00b


Joined: 10 Jan 2007
Posts: 69
Location: Copenhagen

PostPosted: Tue Feb 13, 2007 9:53 pm    Post subject: Reply with quote

Hej everbody!

I finally think I broke through to the solution I've been seeking!

It has been an intriguing journey through the bowels (OpenFirmware) of my G5; sometimes it was horrendous, even. But the answer to the correct boot solution was somewhere else!

On my wifes little Intel based laptop I installed Fedora Core 6 for her. It went off with out a hitch. Nice and clean, and in less than an half-hour. Unbelievable, it was. And gorgeous, too. I was inspired to try installing Debian on my G5 just to see if there were any discrepencies, between Debian and Gentoo. Debian reacted the same as Gentoo. It failed on every attempt with after a boot from yaboot prompt. So was the answer in Open Firmware? No. It was somewhere else, and it wasn't obvious.

I haven't reconfigured my Gentoo kernel yet, it will have to wait until this weekend. BUT I did manage to get Debian to boot after trying to reinstall it. Debian's boot configuration was loaded with with it own yabootconfig program and it wrote out a bunch of nonsense on the yaboot.conf file. Obviously full of bugs. After rewriting the boot codes by hand I managed to get it to the same screen as Gentoo, so now the two failed equally.

After this weekend I will write out the full configuration files for everyone, and hopefully it will help to generate a better understanding of the Linux boot process especially from a non-first drive.

Thanks againto everyone who help out with this thread!

Sincerely,

Gustav
_________________
"Hey, hey, hey — don't be mean. No need to be mean. 'Cause, remember: no matter where you go... there you are." - Buckaroo Banzai
Back to top
View user's profile Send private message
Bones McCracker
Veteran
Veteran


Joined: 14 Mar 2006
Posts: 1609
Location: U.S.A.

PostPosted: Wed Feb 14, 2007 4:03 am    Post subject: Reply with quote

There are many ways to handle this, but I think the easiest is to switch the boot device parameter in the stage 1 bootloader (Open Firmware). Get to the Open Firmware prompt. I only skimmed the thread -- forgive me if you've already done/tried this:
Code:
printenv
setenv boot-device sd1:
reset-all


I'm not certain on the "sd1:" portion. It might have to be "setenv boot-device sd1:,yaboot" or similar. (When I set up dual-boot with OpenBSD I had to specify the bootloader, as in "setenv boot-device ultra1:,ofwboot".

By the way, while you're in there, you might want to password-protect your system if you haven't. Security mode options are "none" "command" (password required to do stuff at OF prompt) and "full" (password required to boot):
Code:
password
set-env security-mode command
reset-all
Back to top
View user's profile Send private message
Gustav IV
n00b
n00b


Joined: 10 Jan 2007
Posts: 69
Location: Copenhagen

PostPosted: Tue Mar 06, 2007 2:23 pm    Post subject: Reply with quote

Hi Everyone,

I finally managed to get Gentoo up and running on my G5. It wasn't easy. But soon I will post the solutions as to what happened and how I made the yaboot configuration to finally work. The main problem was with a misconfigured kernel that the computer just wouldn't boot. But right now I am plagued with a mask problem while trying to load a GPR package from the Packages CD. This will be posted as a new thread, so no need to reply to this post regarding masking problems.


Thanks again to everyone who participated in this post.

Sincerely,

Gustav IV
_________________
"Hey, hey, hey — don't be mean. No need to be mean. 'Cause, remember: no matter where you go... there you are." - Buckaroo Banzai
Back to top
View user's profile Send private message
Gustav IV
n00b
n00b


Joined: 10 Jan 2007
Posts: 69
Location: Copenhagen

PostPosted: Fri Mar 16, 2007 4:33 pm    Post subject: Reply with quote

Hi again!

There answers to the plaguing problem of the following message at boot...
Code:
done
found display    :     /pci@0,f0000000/ATY,SimoneParent@10/ATY,Simone_B@1, opening...

was not that Openfirmware needed to be configured with video parameters, but SIMPLY that the kernel to boot was woefully botched up. I later reconfigured a kernel using a G5 default configuration which I had no idea was even available, because it was never mentioned in the documentation i was using. The suggested kernel configuration methods, were rather difficult to guess what was what in make menuconfig that I had a high chance of winnings Wednesday's lottery, than configuring a bootable kernel.

The real answers to the problems that plagued my yaboot configuration file were found in the /usr/lib/yaboot/yaboot program that was written by ybin or mkofboot. I cannot recreate the files, but the messages were written to the program before a list of the other dialogue prompts used at the preboot stage, and a weird picture of a dog, a male one, even. Here, there was a warning that the Apple boot strap had the wrong name, discrepencies between upper and lower case characters, so there were incongrituities between fstab and what was written with mac-fdisk. These irregularities were adjusted accordingly using the Debian installation interface that allows you to name and set mount points and many other things where mac-fdisk is starkly limited.

Debian boots wonderfully and is a slick distribution.

Here is the yaboot.conf file I use for both Gentoo and Debian, but mind you, the yabootconfig tool in Debian also had a lot of errors in it, wrong device and ofboot names in long form, and so it wasn't bootable until I edited it by using the Gentoo liveCD and a chroot on to the Debian partitions and system:
Code:

## yaboot.conf generated by debian-installer
##
## run: "man yaboot.conf" for details. Do not make changes until you have!!
## see also: /usr/share/doc/yaboot/examples for example configurations.
##
## For a dual-boot menu, add one or more of:
## bsd=/dev/hdaX, macos=/dev/hdaY, macosx=/dev/hdaZ

boot=/dev/sdb6
device=sd1:

ofboot=sd1:6

partition=7
root=/dev/sdb7

timeout=100
delay=50

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

enablecdboot
enableofboot

#macosx=/dev/sda3

image=/boot/vmlinux
    label=Linux
    read-only
    initrd=/boot/initrd.img

image=/boot/vmlinux.old
    label=old
    read-only
    initrd=/boot/initrd.img.old

# This entry automatically added by the Debian installer for an existing
# Linux installation on /dev/sdb4.
image=sd1:4,/boot/gentoo
    label=Gentoo
    root=sd1:4
    append="root=/dev/sdb4 ro append"

# This entry automatically added by the Debian installer for an existing
# Linux installation on /dev/sdb5.
#image=/k2-sata@0/disk@0:5,/boot/gentoo
#    label=sdb5-Linux
#    root=/k2-sata@0/disk@0:5
#    append="root=/dev/sdb4 ro"

# May God have mercy on this computer.


And this is the yaboot.conf I have on the Gentoo system:
Code:

#etc/yaboot.conf written by hand.

#bootstrap partition:
boot=/dev/sdb2
device=sd1:

ofboot=sd1:2

root=/dev/sdb4
partition=4

delay=5
timeout=100

#append
#    video=radeonfb:1152x870@75
#    display=screen

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

enablecdboot
enableofboot


macosx=sd:2
debian=sd1:6

image=/boot/gentoo
    label=Gentoo
    read-only
    root=/dev/sdb4
    partition=4   

image=/boot/vmlinux
    label=Debian
    read-only
    root=/dev/sdb7
    partition=7   
    append="root=/dev/sdb7 ro append"

#May God help this machine.


And that is what is, man.

Thanks and goodluck everyone.
_________________
"Hey, hey, hey — don't be mean. No need to be mean. 'Cause, remember: no matter where you go... there you are." - Buckaroo Banzai
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