DualG5 PowerMac 2.0

codadilupo · Advocate Joined: 05 Aug 2003 Posts: 3135

Hello gentooers ;-)

I've always installed gentoo on x86 macchines. Now I'm trying to install it on a friend's new PPC64. We've had some problems booting the liveCD, so I would like to know if there's some trick that automagically bring us to our goal.

We've used both gentoo 2004.3 (update 3) and gentoo 2005.0. Sure, we typed "G5 video=ofonly" at the promt.

Uh, by the way, here's some infos on the HW:

adaptr · Posted: Thu Jun 16, 2005 7:29 pm Post subject:

What problems, exactly ?
_________________
>>> emerge (3 of 7) mcse/70-293 to /
Essential tools: gentoolkit eix profuse screen

codadilupo · Advocate Joined: 05 Aug 2003 Posts: 3135

nigoro · Retired Dev Joined: 27 Dec 2004 Posts: 12 Location: Japan

When you type nothing but ENTER, how does it operate ?
And, would you try a new LiveCD in Bug #94263 ?

https://bugs.gentoo.org/show_bug.cgi?id=94263

nigoro · Retired Dev Joined: 27 Dec 2004 Posts: 12 Location: Japan

I thought from your information that it was the model in which MacOSX 10.4 (Tiger) was pre-installed.
Is it right ?

Please let me know a model number, if you don't have a problem about it.
Example: M9747LL/A

Thanks!

wolf3d · Posted: Sun Jun 19, 2005 12:14 pm Post subject:

ciao coda

I also installed gentoo on two ppc at work but with one machine I had a problem similar to yours

I had to burn a livecd on a different brand of CD (In my case I had to burn it on a rewritable disc because I had no other brand).

Try that

edit: seems I overlooked your post, the problem you described happened latter with a kernel compilation, random hangups during the boot sequence with gentoo installed... I had to put a debian because we were in a hurry

_________________
The Brave Do Not Fear The Grave

codadilupo · Advocate Joined: 05 Aug 2003 Posts: 3135

Hey guys, We've booted with the suggested nw ISO, and installed almost all system ;-)

First of all, thanks to all for that.
Now We have problems with yaboot, but I'm sure it's my own mistake, so I'll explain to you what I did, and hope someone can help me to find my error ;-)

Well, We begin installing MacOsX (we know that we have to install it before GNU/Linux, right ?). During the installation we parted the HD. One partition on the sda for MacOsX, one for the /boot and one for the swap. Then we parted the sdb with one partition for / and one for /home.
Well, we completed the installation of MacOsX, and boot with the Gentoo LiveCD.
With mac-fdisk we saw that the MacOsX Installation Wizard had created the partition_map and the bootstrap_partition, so I did not created them as explained in the HandBook.
We completed the installation of gentoo, and then we arrived at the yaboot installation. We installed the yaboot-static, as suggested. Then we tried to launch

pindar · Apprentice Joined: 30 Apr 2004 Posts: 220

I'm not sure if I have understood what you're trying to achieve, but I had a problem that might be related: I could never get yaboot to boot from my second hard drive (sdb). Try switching the order of the drives, putting the bootloader (which is != /boot) and / on sda.

codadilupo · Advocate Joined: 05 Aug 2003 Posts: 3135

Uh, it could be !
Actually, I was wondering why yabootconfig tried to search the apple_boot partition on sdb instead of sda: so, you're suggesting that it identifies the "booting device" following the /... uhmm... we'll try this solution.
Thanks, for now.

Coda

patxurrin · n00b Joined: 28 Oct 2004 Posts: 15

I have a similar machine, a dual power mac G5 with gentoo installed on secon serial ATA disk . Mi yaboot.conf is:

## 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/sdb4
## bootstrap partition for serial ATA on second disk
## 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=sd1:
## "sd0" is the firts disk "sd1" is the secon disk.

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

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

ofboot=sd1:4

image=/boot/vmlinux
sysmap=/boot/System.map
label=Linux
root=/dev/sdb6
read-only
enableofboot
enablecdboot
macosx=sd0:3

codadilupo · Advocate Joined: 05 Aug 2003 Posts: 3135

uff !
We're welcome to announce that installation has gone (almost) well !
We had some break 'cause of holidays, you can understand ;-)

Now we rebooted, and we have only some little problems. After boot, system says that it couldn't mount some local filesystems. It also says that /proc/openroms does not exists. I'm using udev, and I think this could be an explanation. Have you suggestions about this ? Is udev yet unstable for ppc ? In the HowTo I couldn't find anything about this issue.

Coda

P.S.: Thanks to all, again: now I'm able to manage system via ssh, and it's really better to adjust it, and faster than go to the pc-owner home ;-)

silian87 · Posted: Tue Aug 23, 2005 2:50 pm Post subject:

Udev is stable on ppc, can you tell me exactly the filesystems can't be mount at boot, thanks.
_________________
Musica che ascolto: http://www.last.fm/user/silian87/

Silian87 FAQs: http://marentax.homelinux.org/~silian87/silian87-faq.txt

GTalk: silian87@gmail.com

codadilupo · Advocate Joined: 05 Aug 2003 Posts: 3135