Hello fedora-ppc :
I am trying to install Fedora Core 4 for PPC on a Genesi ODW PowerPC workstation and am running into a few problems. Thankfully I have received help from some gifted people and can at least boot up the installer process. I found great info and resources at :
ftp://zeniv.uk.linux.org/pub/people/dwmw2/fc4-pegasos/README.Pegasos
The installer will not read from an expanded tree on a secondary harddisk in the system. I was thinking of speeding up the install process by putting the ISO images onto a secondary harddisk and filesystem ( /dev/hdd1 ) but alas the installer will not read the ISO images from the original PowerPC distro and will not read from an expanded tree either. I am guessing that I have to create a full expanded tree on a DVD and then read from there. I'm not sure. This is a bit of a stumble forward hack and slash approach to installing an OS but I am willing to experiment a bit.
Is there a place to file bug reports for the Fedora Core 4 PowerPC project ?
Dennis Clarke
On Wed, 2005-09-21 at 09:25 -0400, Dennis Clarke wrote:
Hello fedora-ppc :
I am trying to install Fedora Core 4 for PPC on a Genesi ODWPowerPC workstation and am running into a few problems. Thankfully I have received help from some gifted people and can at least boot up the installer process. I found great info and resources at :
ftp://zeniv.uk.linux.org/pub/people/dwmw2/fc4-pegasos/README.Pegasos The installer will not read from an expanded tree on a secondaryharddisk in the system. I was thinking of speeding up the install process by putting the ISO images onto a secondary harddisk and filesystem ( /dev/hdd1 ) but alas the installer will not read the ISO images from the original PowerPC distro and will not read from an expanded tree either.
Hard disk installs are iso only - so having the iso's on the second HDD should work. What sort of messages are you getting on tty3-5.
Is there a place to file bug reports for the Fedora Core 4 PowerPC project ?
Installation bugs go against anaconda.
Paul
On Wed, 2005-09-21 at 09:34 -0400, Paul Nasrat wrote:
Hard disk installs are iso only - so having the iso's on the second HDD should work. What sort of messages are you getting on tty3-5.
I didn't build ISO images for my updated tree -- I'm not entirely sure _how_ to. He can't use the original FC4 images, because they're not the same install tree, and he can't use the expanded tree which he rsync'd from zeniv because anaconda won't do HD installs that way any more.
I think the latter is the bug he wants to report. A workaround is probably to write the contents of the install tree to a DVD and install from that, but it would be better if we could just fix anaconda to install from expanded trees on the hard drive, like it used to.
On 9/21/05, David Woodhouse dwmw2@infradead.org wrote:
On Wed, 2005-09-21 at 09:34 -0400, Paul Nasrat wrote:
Hard disk installs are iso only - so having the iso's on the second HDD should work. What sort of messages are you getting on tty3-5.
I didn't build ISO images for my updated tree -- I'm not entirely sure _how_ to.
Well that _is_ something I can help with.
Perhaps after I get the rsync done I will create a ISO-9660 ISO and then burn it to a DVD and test. If all goes well I can then provide the DVD ISO for you.
He can't use the original FC4 images, because they're not the same install tree, and he can't use the expanded tree which he rsync'd from zeniv because anaconda won't do HD installs that way any more.
That is the problem that I am hitting.
I think the latter is the bug he wants to report. A workaround is probably to write the contents of the install tree to a DVD and install from that, but it would be better if we could just fix anaconda to install from expanded trees on the hard drive, like it used to.
Which reminds me .. perhaps I can dump the ISO image that I will create onto that second hard disk as a simple foo.iso file ? Or am I dreaming there ?
Sorry for these noobish questions .. I am a much better Solaris guy than a Linux guy and I often have to flail about with coffee in order to get these things to work :-)
Dennis Clarke
On Wed, 2005-09-21 at 14:46 +0100, David Woodhouse wrote:
I think the latter is the bug he wants to report. A workaround is probably to write the contents of the install tree to a DVD and install from that, but it would be better if we could just fix anaconda to install from expanded trees on the hard drive, like it used to.
Oh, the workaround for anaconda's regression, btw, is to _start_ an NFS install from elsewhere, but then switch to tty2 as soon as it's started the second stage of the installer, mount the local file system with the install tree and bind-mount it over the top of /mnt/source.
It's not simple or pretty, and you do still have to have network access to a machine with _parts_ of the install tree -- but it does let you fetch all the _packages_ from your local copy of the tree, instead of over the network. The Fedora/RPMS/ directory can actually be empty on the network server you're using.
Actually, it might work if you write a CD containing all but Fedora/RPMS from the install tree, then do the same bind-mount trick to put the RPMS where the installer expects them in /mnt/source/Fedora/RPMS/. At least blank CDs are cheaper than blank DVDs.
On 9/21/05, David Woodhouse dwmw2@infradead.org wrote:
On Wed, 2005-09-21 at 14:46 +0100, David Woodhouse wrote:
I think the latter is the bug he wants to report. A workaround is probably to write the contents of the install tree to a DVD and install from that, but it would be better if we could just fix anaconda to install from expanded trees on the hard drive, like it used to.
Oh, the workaround for anaconda's regression, btw, is to _start_ an NFS install from elsewhere, but then switch to tty2 as soon as it's started the second stage of the installer, mount the local file system with the install tree and bind-mount it over the top of /mnt/source.
It's not simple or pretty, and you do still have to have network access to a machine with _parts_ of the install tree -- but it does let you fetch all the _packages_ from your local copy of the tree, instead of over the network. The Fedora/RPMS/ directory can actually be empty on the network server you're using.
gee .. this looks like the dance of the woo-lee masters to me but I will have a go at it
:-)
Actually, it might work if you write a CD containing all but Fedora/RPMS from the install tree, then do the same bind-mount trick to put the RPMS where the installer expects them in /mnt/source/Fedora/RPMS/. At least blank CDs are cheaper than blank DVDs.
I have lots of both. As well as -RW versions which are slow but very handy for testing.
Dennis
ppc@lists.stg.fedoraproject.org
-
David Woodhouse -
Dennis Clarke -
Paul Nasrat