Yaboot on Powermac G3 B&W

["Juan Casero (FL FLC)" <Juan.Casero@wholefoods.com>]

Greetings Everyone -

I have a rather messy problem with an old Powermac G3 (blue and white)
that I want to install Fedora Core 4 PPC on.  The installation seems to
go through fine and it even appears that the system installs the
bootloader at the end but after a reboot the mac cannot run the boot
loader.  Right now the system has an internal AHA 2940U2B scsi card that
is supposedly bootable.  The layout of the disk partitions is as follows

/dev/sda1 -> 800k Apple Boot Strap Partition
/dev/sda2 -> 100 Mb boot partition mounted under /boot
/dev/sda3 -> 8.0 Gb logical volume partition which is later mounted
under /


The following is the /boot/etc/yaboot.conf file

	# yaboot.conf generated by anaconda

	boot=/dev/sda1
	init-message=Welcome to Fedora Core\!

	Hit <TAB> for boot options

	partition=2
	timeout=80
	install=/usr/lib/yaboot/yaboot
	delay=5
	enablecdboot
	enableofboot
	enablenetboot
	magicboot=/usr/lib/yaboot/ofboot

	image=/vmlinuz-2.6.11-1.1369_FC4
		label=linux
		read-only
		initrd=/initrd-2.6.11-1.1369_FC4.img
		root=/dev/VolGroup00/LogVol00

I had to indent each line so stupid ms outlook wouldn't capitalize the
first letter but in the original file there are no spaces at the
beginning of each line.

I am able to use the FC4 install cd 1 to boot linux in rescue mode,
mount the disk partitions mentioned above and then chroot /mnt/sysimage.
Using the ofpath on the disks I have determined that the openfirmware
path for /dev/sda is /pci@80000000/pci-bridge@d/scsi@4/@0:1, so I reboot
the mac and then go into the openfirmware (ver 3.1.1) and set the
boot-device environment variable to
/pci@80000000/pci-bridge@d/scsi@4/@0:1,\yaboot but when I reboot the
yaboot loader never runs.  I have tried many variations of this
including setting the boot-file openfirmware environment variable to
yaboot, \\yaboot, \\:yaboot and none of them have worked.  I even tried
performing an install of FC4 PPC Linux on an ide drive attached to the
primary ide controller of the mother board (while disconnecting the scsi
system) and I experience the same problem. So I don't think it is the
scsi controller or its firmware code that is the problem.  Any one have
any ideas what I am doing wrong here?  I could really use some help with
this.


Thanks,
Juan Casero
Juan.casero@wholefoods.com