-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Olaf, thanks for your message! On 06/24/2008 10:52 AM, Olaf Hering wrote:

Or if you have already SuSE installed, copy the inst32 to your local harddrive, add it to lilo.conf and boot it via yaboot.

Add something like this to lilo.conf:

image=/mydirectory/inst32 label=i110 append="sysrq=1 quiet " optional

yaboot is also able to load and start the file via tftp.

I also tried starting the installation by copying inst32 from the DVD to the hard disk and adding an entry for inst32 to the OFW menu - I currently don't use LILO on that box. I currently run Debian 4.0 on there. It started booting (again the spinner was active for a while) and then stopped, similar to when I tried booting from the DVD. Are you saying that using LILO and yaboot is a *requirement* for getting inst32 to start on Pegasos? Bye, LenZ - -- - ------------------------------------------------------------------ Lenz Grimmer -o) [ICQ: 160767607 | Jabber: LenZGr@jabber.org] /\\ http://www.lenzg.org/ V_V -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFIYM65SVDhKrJykfIRAoKGAJ9vue2GsZcrug9rXasJ30277fE1HwCfS7i+ +Usr1nlecHIrcRBcuyXF2LI= =DF8j -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-ppc+help@opensuse.org

Olaf Hering írta:

On Tue, Jun 24, Lenz Grimmer wrote:

...

It started booting (again the spinner was active for a while) and then stopped, similar to when I tried booting from the DVD. Are you saying that using LILO and yaboot is a *requirement* for getting inst32 to start on Pegasos?

Only yaboot is the requirement, any recent yaboot binary will do it.

OK, just testing it: I copied yaboot, yaboot.cnf, yaboot.txt and inst32 from the suseboot directory to the root directory of an ext3 partition. Then just 'boot hd:0 yaboot' and yaboot started. Entered 'install', and the openSUSE 11.0 installer started without any problems. Bye, CzP --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-ppc+help@opensuse.org

On Tue, Jun 24, Lenz Grimmer wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Hi,

Peter, thanks a lot for your support and testing!

On 06/24/2008 02:03 PM, Peter Czanik wrote:

...

OK, just testing it: I copied yaboot, yaboot.cnf, yaboot.txt and inst32 from the suseboot directory to the root directory of an ext3 partition. Then just 'boot hd:0 yaboot' and yaboot started. Entered 'install', and the openSUSE 11.0 installer started without any problems.

Ah, that sounds doable :) As these files (incl. yaboot) are included in the "suseboot" directory of the DVD as well, wouldn't it be sufficient to boot from the DVD by entering "boot cd suseboot/yaboot" at the OFW prompt?

yaboot can not read from the cd via the openfirmware filesystem driver. An isofs driver for yaboot would fix this, so far I did not have to time to implement this. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-ppc+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Peter, On 06/24/2008 08:02 AM, Peter Czanik wrote:

That was me :) 'inst32' does not boot on the Pegasos any more :-( What you can do is installing a minimal 10.3 and upgrade it to 11.0 using zypper. Beware, 10.3 is badly broken for ppc32, as there are some packages with direct 64bit dependencies, which mess up the system. So install a minimal 10.3, do not run online upgrade during installation, and once ready, remove any 64bit packages: rpm -e itrace rpm -qa '*-64bit*' | xargs rpm -e --nodeps --noscripts rpm -qa '*ppc64*' | xargs rpm -e --nodeps --noscripts Then replace the 10.3 installation sources with 11.0 and first upgrade rpm (zypper -v in rpm), then upgrade zypper (zypper -v in zypper), and then the rest of the distro (zypper -v dup).

Ugh, I was really hoping that there is a simpler procedure than that... Since I already have a running (Debian) system, I wonder if I could bootstrap the installation from there somehow?

If you run into any problems, please let me know!

Thanks! It seems like PPC does not really have a high priority for openSUSE anymore, if things have been "badly broken" in 10.3 already and it now even doesn't boot anymore. Or is it only that bad on the Pegasos? Bye, LenZ - -- - ------------------------------------------------------------------ Lenz Grimmer -o) [ICQ: 160767607 | Jabber: LenZGr@jabber.org] /\\ http://www.lenzg.org/ V_V -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFIYM99SVDhKrJykfIRApHJAJwLVtzt/mtg4rV5LnUebfkIXwWrAQCfWxRk mp8zJrKZ8tfeglGqSSRtwYE= =6xpU -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-ppc+help@opensuse.org

On Tue, Jun 24, 2008 at 7:05 AM, Peter Czanik wrote:

"badly broken" referred to 32bit PPC support in general, not to Pegasos. As far as I could understand from various bugzilla remarks, only 64bit IBM servers are officially supported by SuSE, the rest is just a hobby project for Olaf & Co. But this part was fixed for 11.0.

I managed to get around that by just tabooing any 64bit packages before installing with 10.3. After that, it was completely stable on all my 32bit Powermacs. However, after I started beta testing v11.0, I dumpled 10.3 completely. The packager in 11.0 is amazingly fast. As for PPC, it is an "official" port, and lists all the PPC procs from the 601 forward. I've bugged for a while to see if they were going to drop support for older PPC chips, but so far they haven't. I'm running v11.0 on my son's Wallstreet G3/266. It's slow, but stable. Otherthan the annoying backlight issue(which I THINK is because I need to replace the PRAM battery. If that doesn't work, then it's just a bug in the machine..... *sigh*), it runs just fine. Been using it as a SaMBa server for the last few weeks with no problems. Even has built-in UPS ;-) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-ppc+help@opensuse.org

On Tue, Jun 24, 2008 at 10:33 AM, Peter Czanik wrote:

That's right, but for anybody not fully aware of this problem before installation, this was a serious problem. Luckily it is fixed now, and openSUSE 11.0 installs properly on any of my 32bit PPC machines!

Yeah, 10.1's kernel broke support for Old World Macs. 10.2 broke the Wallstreet's backlight support. 10.3 had issues with 64/32bit. v11.0 looks to have finally ironed out most of the issues. Oh well, since they didn't add PPC support back in until 10.0, I guess we can't complain too much that there were some problems. 10.0 was pretty solid all the way around tho. Other than wanting CD media, v11.0's been mostly solid. I've had a few minor issues on my Celeron DC E1200 with networking, but haven't had time to figure them out yet. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-ppc+help@opensuse.org

Hello, Also, a crash bug remained in the installer, which can be worked around with a driver update. Just add the following parameter to 'install' in yaboot: dud=http://download.opensuse.org/update/11.0/driverupdate Other way package selection crashes the installer once the 'OK' button pushed. Bye, CzP --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-ppc+help@opensuse.org