Bug 141461

Summary:	partitioner changes for PegasosPPC
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	peter czanik <peter>
Component:	Installation	Assignee:	Edith Parzefall <eparzefall>
Status:	RESOLVED FIXED	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Normal
Priority:	P5 - None
Version:	RC 1
Target Milestone:	---
Hardware:	PowerPC
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Bug Depends on:	192949, 192957
Bug Blocks:
Attachments:	yast2-storage.amiga.patch yast2-storage.amiga.cyl1.patch yast2-storage.amiga.isPPCPegasos.patch yast2-storage.amiga.pegasos.default.patch yast2-storage.amiga.pegasos.default.patch yast2-storage.amiga.max_primary.patch

Description peter czanik 2006-01-04 21:40:32 UTC

On a PegasosPPC machine, the partitioner should suggest to have at least one ext2/ext3 partition, as it's needed for booting (the prepared kernel must be on an ext2 or ext3 partition, other way OpenFirmare of PegasosPPC can not load it). This is always there on an ODW (Open Desktop Workstation, a computer prebuilt around the Pegasos2 PPC mother board), as it comes with several Linux-es preinstalled, but is missing, if a user builds a machine herself.
The partitioner should not suggest to create the CHRP boot partartition, as the Pegasos can not do anything with it.

Comment 1 Stefan Hundhammer 2006-01-05 10:45:46 UTC

I don't think we can or even want to make different partitioning proposals for different brands of hardware of the same architecture.

If you have a large numer of those machines to install, consider using AutoYaST with a partitioning scheme that fits your purposes. Please refer to the AutoYaST documentation for more details.

Comment 2 peter czanik 2006-01-05 11:34:46 UTC

If a large number of these machines are to be installed, the sysadmin will already know about it, and won't be confused. But I got a large number of forum posts and e-mails, like:
"do I really need this CHRP boot partition thing?" or "Why can't I list my boot partition from OpenFirmware"

Pegasos uses probably the same processor, but booting is handled differently on different Power based machines. Both of these problems are simple to check at exit from the partitioner:

if (machine=CHRP) and (not machine=Pegasos) then
begin
  if no CHRP boot partition exist then showmessage('missing CHRP boot partition');
end;

if machine=Pegasos then
begin
  if no ext2/ext3 partition on harddrives then showmessage('You need an ext2 or ext3 partition to boot your Pegasos');
end;

Comment 3 Thomas Fehr 2006-01-09 12:19:13 UTC

Since these Hardware is not officially supported I will not make any changes
regarding this hardware. I could not do this anyway since hardware detection
currently does not detect this machine type.

Comment 4 Olaf Hering 2006-01-10 13:18:34 UTC

we will add that support.

Comment 5 Thomas Fehr 2006-01-10 13:24:36 UTC

So this is something for SLES11...

Comment 6 Bodo Bauer 2006-04-24 11:40:29 UTC

I'm closing this bug. please follow up with a FATE request for Code11...

Comment 7 Olaf Hering 2006-04-24 11:42:23 UTC

thats for 10.2

Comment 8 peter czanik 2006-07-11 07:30:01 UTC

As talked in private e-mails with Olaf:

if Pegasos is detected
   - do not create / suggest a CHRP boot partition
   - if the HDD is empty, create an ext2 partition for /boot on /dev/hda1 and do the rest as on other platforms.
   - check for an OF bootable partition, and complain if no ext2/ext3/AFS/FAT/VFAT partition is found on the attached HDDs, as the default partition type on SUSE is ReiserFS, which is not supported by Genesi OpenFirmware

Comment 9 Olaf Hering 2006-08-01 09:50:23 UTC

Created attachment 94888 [details]
yast2-storage.amiga.patch

Comment 10 Olaf Hering 2006-08-01 09:50:40 UTC

Created attachment 94889 [details]
yast2-storage.amiga.cyl1.patch

Comment 11 Olaf Hering 2006-09-26 12:52:06 UTC

Created attachment 99624 [details]
yast2-storage.amiga.isPPCPegasos.patch

add a function to detect Pegasos

Comment 12 Olaf Hering 2006-09-26 12:54:13 UTC

Created attachment 99625 [details]
yast2-storage.amiga.pegasos.default.patch

Comment 13 Olaf Hering 2006-09-26 12:54:13 UTC

Created attachment 99626 [details]
yast2-storage.amiga.pegasos.default.patch

Comment 14 Olaf Hering 2006-09-27 09:25:08 UTC

Created attachment 99718 [details]
yast2-storage.amiga.max_primary.patch

seems to work without this change

Comment 15 Olaf Hering 2006-09-29 12:57:06 UTC

I have commited these patches to yast2-storage, .r33189:33194

Comment 16 peter czanik 2006-10-15 13:29:18 UTC

Finally, there was a factory build, which could actually be installed, so I tested it in two situations:

- modification of existing Amiga partition table workes fine
- empty HDD is initialised with Amiga partition table and works fine

I could not yet test one thing: what happens, if a HDD already has a DOS partition table with some partitions containing data and the one modifies the partitions? Will it be kept as DOS? Other way all data is lost (as it was the other way around in 10.0).

Comment 17 Olaf Hering 2006-11-10 16:01:05 UTC

yes, it should work now.