Bug#604134: ppc: after debian installation MacOS 9.2 won't recognize disk anymore
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 tag 604134 - squeeze-ignore Justification: workaround doesn't work, alternative workaround (described below) is horribly, horribly convoluted I am multi-booting on an iBook G3 (April 2003), 900mHz. The hardware does, amazingly for a G3, appear to be capable of handling disks greater than 128 GB, although OS 9.2.2 is not. This is one of the last models capable of booting directly into Mac OS 9.2.2, as opposed to only running it in Classic Mode. However, apparently Mac OS 9.2.2 can only be installed from within Classic Mode on OS X, not directly off the CD. After Debian broke Mac OS 9.2.2 so it couldn't boot anymore, but instead displayed a floppy image with a flashing question mark, the Update Drivers function on the Classic install CD did not work. When booting off the CD, the option was greyed out, and when opening the CD in Classic mode, it did not appear capable of seeing the disk. Re-blessing the System Folder didn't help either. Neither did re-initializing the Apple Partition Map with OS X's pdisk and manually inputting the partition map that was there before, although admittedly there were some asterisks in the original that I could not duplicate. I have successfully installed OpenBSD and NetBSD on this iBook without them breaking Mac OS 9.2.2. OpenBSD worked normally, while NetBSD required following some very well-written instructions about bypassing certain parts of their installation procedure manually. The NetBSD makes mention of the default installation procedure faking the Apple Partition Map in such a way that it works for most purposes but not for Mac OS; however, it is possible to work around this by bypassing that portion of the installation and only modifying (not re-initializing) the partition map with NetBSD's pdisk. (Which, for the record, they have graciously ported to Linux.) Based on the NetBSD documentation, I devised a plan to wipe the disk and start over, this time bypassing the portions of the Debian installer than might be causing issues. But first, I copied yaboot, yaboot.conf, and ofboot.b to a small external drive. For reference, here are the NetBSD/macppc installation instructions. ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-5.1/macppc/INSTALL.html The NetBSD documentation goes into great detail on how to correctly partition a disk on macppc that is intended to be multi-booted. http://www.netbsd.org/ports/macppc/partitioning.html I re-initialized the disk with Mac OS X's Disk Utility, being careful of course to install the Classic disk drivers. Classic's Disk Setup would also have worked; however, Disk Setup cannot see more than 128GB of the disk, thus I chose Disk Utility. Mac OS 9.2.2 is perfectly capable of reading this larger-than-128GB partition map, although of course I expect it wouldn't be able to boot from or mount any partitions over the limit, at least not without third party software. Then, after making sure any HFS/HFS+ partitions were unmounted, I ran pdisk /dev/disk0 from a terminal. NetBSD has excellent instructions on the use of pdisk, and creating filesystems afterward. (As an alternative to newfs_hfs /dev/whatever, you may also create the HFS(+) partitions using Disk Utility's Erase Partition functionality.) http://www.netbsd.org/ports/macppc/partitioning.html#pdisk Using pdisk, I was able to get rid of the free spaces Disk Utility puts between partitions. I was, of course, careful not to touch the first 8 partitions (partition map and drivers). I was also able to create partitions with type Apple_UNIX_SVR2, which is what Debian and NetBSD use, and also one of type OpenBSD. I then installed Mac OS X Tiger. After booting into Tiger, I had to change the permissions on the disk I intended to install Classic on so that it was actually writable. They were probably broken as the result of my nonstandard way of creating the filesystems. Ctrl- clicking the disk, this could be done graphically. After this, I was able to restore a Classic System Folder from a small backup media (the disk that originally came with the laptop and is now in a USB enclosure), and use that to install Mac OS 9.2.2 onto another partition. At this point, both OS X and Classic were quite able to boot. I then booted into the Debian cd and selected expert mode. However, since expert wasn't expert enough for me, I promptly pressed Esc and changed the debconf priority to low. I then went to the beginning and continued normally, until it came time to partition the disks. At this point, instead of entering partman, I escaped to a shell. I had already partitioned all of Debian's partition's from Tiger's pdisk, since I did not know if any of Debian's partitioning utilities were safe to use, not having found pdisk among them, and did not want to re-install everything another half-dozen times to find out. So, I used mac-fdisk only to view pdisk to remind myself where everything was, but did not change anything with it. I should also add that I
Bug#604134: ppc: after debian installation MacOS 9.2 won't recognize disk anymore
Hi Mathias, thanks for the report you've written after you have had so many troubles with your PowerMac G4. Of course, it is crucial to either use hard disk drives supported by your early G4 Power Mac's internal PATA controller (i.e. devices featuring a capacity of up to 128GB in early Power Mac G4 machines, I think) or to connect HDDs with a higher capacity with it and restrict their disk space usable to a maximum of 128GB. It is interesting that connecting HDDs with a higher capacity and restricting their disk space usable to a maximum of 128GB seems only to work if operating systems like Mac OS 9 and Mac OS X are used (and no longer as soon as Debian GNU/Linux gets involved). Using an operating system like Debian GNU/Linux does, of course, not automatically mean that this is a way of easily exceeding the limits of your HDD controller. I also do not expect that disk errors similar to the ones you reported will occur if Power Mac users use special PCI addon cards to operate bigger PATA/IDE or SATA disk drives - at least if those PCI addon cards are suitable to be used in Power PC Macs (see the product specifications and system requirements of e.g. ACARD addon cards). (Personally, however, I've never tried to use a HDD controller extension card in a Power Mac with Debian GNU/Linux; I only know that such an extension card works perfectly in my OldWorld Power Mac 7300 running Mac OS 7 and 9. But currently I'm not running Linux on this particular machine, only on my Power Mac 7500.) -) trying to fix the problem when using bigger disks at the original built in controllers (but beware, as recent Terrabyte disks are no problems throught PCI cards, and seem to be used often at G4s) I'm not sure if I understand correctly what you're stating here. To be honest, I think it is rather unlikely that a software solution within the Debian GNU/Linux installation tool allowing you to reliably use bigger disks ( 128 GB) connected with the original built-in PATA/IDE controller of early Power Mac G4 computers will ever be released. Yet, it seems that there was a way of doing this, using a special workaround tool, but this product is commercial software and therefore AFAIK it is not subject to GPL licence conditions: http://www.apfeltalk.de/forum/neue-festplatte-powermac-t84599-2.html#post2678601 http://www.macupdate.com/app/mac/14544/speedtools-ata-hi-cap-support-driver Currently I am not aware of any reports stating that this tool works together with Debian GNU/Linux installations or of reports that it does not work, thus it seems that using this tool _might_ allow you to use bigger HDDs with your system while you would not have to buy new hardware products. Probably you would have to check this yourself... The use of hardware extension cards for the PCI slots might be an option allowing you to use larger hard disks - if those extension cards are suitable for Power Mac G4 computers, of course. Personally I'd prefer this option, for using hardware extension cards might even speed up your system's data transfer rates. The subject of this bug report might imply that there was an installation problem if you try to use Debian GNU/Linux together with Mac OS 9 on one (big) hard disk, on various partitions of an early Power Mac G4 system. In fact, I think that if you try to use any other operating system (like Mac OS X or even MorphOS) in a similar way together with Debian GNU/Linux, i.e. by creating several disk partitions on a huge hard disk drive 128GB connected with one of the internal PATA/IDE ports of early Power Mac G4 computers, it is likely that similar problems will occur, either during the installation process, or - even worse - during the operation of those operating systems at a later point in time, and, of course, this would mean that there is a high danger of data loss. -) downgrade the bug if needed, as it only affects early G4 Macs with upgraded HDs bigger than 128 GB which do not use the availaible space over 128 GB. I remember that a couple of years ago reports were printed in various Macintosh computer magazines recommending users of early G4 Macs to use HDDs bigger than 128 GB only in such a way with their machines. I think we could really say that it is a matter of tough luck, for it seems that running Debian GNU/Linux using such a hardware environment was not tested back in those days, but, on the other hand, one could not really expect this of journalists. There are still a few references on internet forums available about which G4 Macs were affected by this 128 GB problem, whilst others weren't: http://discussions.apple.com/thread.jspa?threadID=1823678 http://forums.xlr8yourmac.com/action.lasso?-database=faq.fp3layout=FaqList-response=answer.faq.lasso-recordID=34188-search Kind regards, Sebastian Schroeer -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe.
Bug#604134: ppc: after debian installation MacOS 9.2 won't recognize disk anymore
Hi Sebastian, thanks for the report you've written after you have had so many troubles with your PowerMac G4. No problem, I am interrested in a well working Debian ;) It is interesting that connecting HDDs with a higher capacity and restricting their disk space usable to a maximum of 128GB seems only to work if operating systems like Mac OS 9 and Mac OS X are used (and no longer as soon as Debian GNU/Linux gets involved). It is! And in special the fact that it even doesn´t work if someone is partitioning the entire (restricted to 128 GB) space with MacOS, and let Debian just change the filesystems at the existing partitions, as I reported above, ... -) trying to fix the problem when using bigger disks at the original built in controllers (but beware, as recent Terrabyte disks are no problems throught PCI cards, and seem to be used often at G4s) I'm not sure if I understand correctly what you're stating here. I just wanted to point at the fact, that MacOS 9 (and 8) limits are at 42 terrabyte, and the 128 GB is just a limit of the onboard controller of the early G4s. So a solution that will scan for the controller in use (!) would be needed, as the problem doesn´t occure at the same machine, with several addon cards for SATA, LVD-SCSI, or ATA100/133. http://support.apple.com/kb/TA21924?viewlocale=en_US Also the general HFS+ limits, 8 exbibyte (EiB), seem to be valid, even if MacOS just can use the 42 terrabyte. regards Mathias -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#604134: ppc: after debian installation MacOS 9.2 won't recognize, disk anymore
Dear Sebastian Schroeer! Your workaround is usable - at least partially. In general it is still possible to have a bootable Debian beside a bootable MacOS 9 at the same disk, as long as the Hard Disk is smaller than 128 GB. The last 3 days I did 8 or 9 complete installations of MacOS 9 AND Debian, so let me report what happened. the Linux partition was first on the disk, that's what the d-i manual recommends Which manual do you actually refer to? Do you refer to the Debian manual for PowerPC installations? I was referring to the Debian GNU/Linux Installationsanleitung http://debian.org/releases/stable/powerpc/ch03s05.html.de#id2726490 As I already knew the tip with restarting, after Debian installation, with the MacOS CD and using update the driver (Treiber aktualisieren) from within drive setup (Laufwerke konfigurieren) from earlier debian list postings (see above: http://lists.debian.org/debian-powerpc/2008/05/msg00047.html ), I began by repartitioning the entire HD, and putting the Linux partitons at the end of the HD like you suggested. Who knows maybe the partitions at the end would have worked, ... but they didn't. I tried manualy partitioning from within the Debian installer, and also automatically partitioning of the biggest free space. When I did the automatically partitioning at the end of the HD I recognised that Debian installer reports the entire HD as valid - a 250GB Seagate disk - while some G4 computers, like mine, have only controllers for 128GB onboard, what is always reported correctly by MacOSs drive setup. But I could use, and even start to install at entire 250 GB with Debian installer. So I tried to repartition the drive with drive setup by doing 3 partitions. A small one at the end (of the 128 GB), and having 80GB for Debian before that last small one, as I thought maybe debian will only use that 80GB inside the part of the HD which is usable by the controller. After every repartitioning - installing MacOS 9 - installing Debian - I used a MacOS 9.2.2 CD, and as it didn't work, the original MacOS 9.1 CD that belongs to the machine, for trying if I can update the drivers. But it never worked. I followed the idea that the problem is the too big HD, and tried repartitioning the HD from within MacOS, with all partitions that Debian will need. A small one for yaboot, a big one for / and a Swap partition. Doing this, the debian installer should have only changed the filesystems but not changed the partitioning itselve. But also with the disc partitioned by MacOS and not by the Debian installer, I was not able to use or boot my MacOS 9! I was also not able to use the drive setup for updating the driver. That is really strange, as the partition table was not touched by Debian, only the filesystems at some partitions, ... So I finally switched to another 80GB HardDisk, used drive setup for creating 2 partitions. One 30 GB HFS+ and one 50 GB undefined. Rebooted into Debian installer from CD (the one I used at my first try - see the first report here at #604134) and used atomatically partitioning of the greatest free space, as I did several times before with the other HD. After installing Debian, I changed the yaboot.conf and added macos (like also done many times before), used ybin and rebooted with the MacOS 9.2.2 CD. It was immediatly possible to use drive setup, and update the driver. Now I have a working MacOS 9/ Debian dualboot system. Later I tried to veryfy everything, but my old Maxtor 20GB HD seems to be broken. I could not install Debian at all, and I have no further empty HD. So I am not absolutely sure, but belive the following (also because many other people reported to use MacOS 9 successfully beside Debian): -) The bug I reported only occures if the physical size of the disc is bigger than the maximum possible size that the controller, built in to the Mac, can handle. Only early G4s are limited to 128 GB. Later G4s even supported 48-Bit-LBA at the onboard IDE controller. -) There is no dataloss under circumstances that the disk fits to the maxiumum possible size, usable by the built in controller (128GB at early G4s). -) If the disk is bigger than the size the controller can handle, there is recently no way to correctly use it. You would need to do a manually partitioning to the maximum of 128 GB (at early G4s) and you will not be able to use MacOS 9 and Debian at the same disk - means you will loose your MacOS 9 installation and never be possible to restart it again, even when access to the data in general is possible through Debian. -) You need to update the driver in every case from the MacOS CD after Debian installation, to be able to reboot into MacOS 9 (or 8.6) again, but this workaround only works if the disc is smaller than 128 GB (if you use the onboard controller of the early G4s). I would suggest the following: -) write a huge warning into the installation manuals -) trying to fix the problem when using bigger disks at the original built
Bug#604134: ppc: after debian installation MacOS 9.2 won't recognize, disk anymore
user release.debian@packages.debian.org tag 604134 + squeeze-ignore usertag 604134 + squeeze-can-defer thanks Hi, On Tue, 2011-01-04 at 01:43 +, Sebastian Schroeer wrote: Dear Mr Wittau! To make sure that nothing unexpected will cause you troubles, please read through my complete text first before doing anything: I successfully run Debian Lenny, Mac OS 9, Mac OS X 10.4, and 10.5 on my PowerMac G4/800MHz Quicksilver using just one hard disk drive with various partitions. It sounds like there's a workaround for the problems mentioned in this bug report, so I don't think this should be a blocker for squeeze; tagging appropriately. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#604134: ppc: after debian installation MacOS 9.2 won't recognize, disk anymore
Processing commands for cont...@bugs.debian.org: user release.debian@packages.debian.org Setting user to release.debian@packages.debian.org (was a...@adam-barratt.org.uk). tag 604134 + squeeze-ignore Bug #604134 [parted] partman-base: Makes MacOS 9 incompatible partition table Added tag(s) squeeze-ignore. usertag 604134 + squeeze-can-defer Bug#604134: partman-base: Makes MacOS 9 incompatible partition table There were no usertags set. Usertags are now: squeeze-can-defer. thanks Stopping processing here. Please contact me if you need assistance. -- 604134: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604134 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#604134: ppc: after debian installation MacOS 9.2 won't recognize, disk anymore
Adam D. Barratt wrote: It sounds like there's a workaround for the problems mentioned in this bug report, so I don't think this should be a blocker for squeeze; tagging appropriately. Hi! I also think that this problem should not serve as a reason for a delay of Squeeze. Yet, ideally an experienced PowerPC Debian developer should have a close look at the Debian installer and related programs to find out why after a Debian installation it is crucial to reboot with a Mac OS 9 installation CD and use it to update the HDD's driver another time, just to still be able to use a Mac OS 9 already installed on a different disk partition. I even fear unexperienced users might be unable to rescue their Mac OS data, be it by simply updating the HDD's driver or (as Debian supports HFS file systems) by using Debian GNU/Linux. If I write a few lines about this issue, is there a chance of getting this into the PPC manual for installations of Debian on Power Macintosh computers? Last week Mr Wittau contacted me; he stated that he wanted to try the installations again and that he intended to report back. Kind regards, Sebastian Schroeer -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#604134: ppc: after debian installation MacOS 9.2 won't recognize, disk anymore
Dear Mr Wittau! To make sure that nothing unexpected will cause you troubles, please read through my complete text first before doing anything: I successfully run Debian Lenny, Mac OS 9, Mac OS X 10.4, and 10.5 on my PowerMac G4/800MHz Quicksilver using just one hard disk drive with various partitions. I can confirm that after an installation of Debian - Debian 5.0.7 Lenny, but such problems also occured with a testing version of Squeeze I tested in August 2010 or so - on a NewWorld PowerPC Macintosh you might run into trouble booting a separate Mac OS 9 OS from a different partition which you had installed before. Please make sure that the program Drive Setup, respectively Laufwerke konfigurieren (German system version of Mac OS 9) recognises the hard disk drive you use, for, actually, there are IDE HDDs which are not supported by this program, and then you cannot use it. As you intend to use yaboot I assume that the HDD is connected with an internal IDE port, i. e. the same hard disk drive(!) might cause troubles if you try to connect it via FireWire in an external case, for in many cases Drive Setup / Laufwerke konfigurieren will not recognize it anymore if connected externally via FireWire. (Problems regarding FireWire support of external hard disk drives and file systems were, however, fixed by Apple in later releases of Mac OS X operating systems, AFAIR.) Quoting wit...@lnxnt.org (wit...@lnxnt.org): the Linux partition was first on the disk, that's what the d-i manual recommends Which manual do you actually refer to? Do you refer to the Debian manual for PowerPC installations? I think that the sequence of partitions used for operating systems should not matter too much, and personally I set up my Linux partitions in the final section of my hard disk drive (at the end of the disk space available). After initializing my HDD with Mac OS 9's Drive Setup / Laufwerke konfigurieren eight partitions were created, and they were named Apple, seven times Macintosh, and 1 x Patch Partition. I did not touch them with the Debian installer, and their sizes only come up to an amount of 25kb to about 300kb, each. It seems that Mac OS 9 needs these partitions to mount HFS(+) formatted volumes; well, actually I am sure of that. The first partition I use for the data of my operating systems is hda9. Preferably, Mac OS Extended (HFS+) should be used as a file system for Mac OS 9 (and Mac OS X) operating systems. I added several other partitions (hda10...hda16) for my daily work purposes. Yet, I created the final Debian partitions on my HDD with the Debian installation tool from the netboot.iso disc, I think, i.e. during the process of the installation of Debian GNU/Linux. In my case I allowed the Debian installer to create a partition hda17 of 1.0MB (could be even less, I think, but I used 1MB; nevermind) as a sort of boot partition on NewWorld PowerPC computers for the yaboot boot loader. It is followed by a /root partition for Debian GNU/Linux hda18 sized about 12.5GB. On my HDD hda19 equals a /home partition of 35GB. Finally, I opted to use about 1.9GB of disc space on my Swap partition hda20, and that's it, for I own 1.5GB of physical memory in this machine. Actually, if you're still trying to fix your problem, I think, however, that you probably do not have to reorganize your set of partitions; at least if you did not destroy any of those small partitions required by Mac OS 9. If your Debian GNU/Linux testing system is up and running and if you did not destroy the partitions Mac OS 9 created during the hard disc initialisation process (including the HFS partition you used to install Mac OS 9 on, of course), please just restart your Macintosh with your Mac OS 9 installation CD. If you then run Drive Setup, respectively Laufwerke konfigurieren (German system version of Mac OS 9), this program will report an IDE disc which was not initialized. Of course, you _must_not_ use this tool to initialize your HDD again, for we actually KNOW that it has already been initialized by Mac OS 9, whilst Debian just added a couple of additional partitions. (If you wanted to reinitialize you would have to start over again to install Debian from the start.) So just use this tool Drive Setup / Laufwerke konfigurieren to update the driver (Treiber aktualisieren) of your hard disk drive. You should find this function in a pull-down menu (and you might have to select this device _once_ with your mouse button before, until its background is shaded with a sort of purple color). If Mac OS 9 can successfully update your HDD's driver the HFS(+) partition(s) of the Mac OS 9 OS you had created before might appear on your screen. Yet, you might also have to reboot your Macintosh one more time from the Mac OS 9 installation CD to (hopefully) see it/them mounted. Updating the HDD driver using Drive Setup does, AFAIK, not have any effect on partitions primarily
Bug#604134: ppc: after debian installation MacOS 9.2 won't recognize disk anymore
It looks like installer creates MacOS 9 incompatible partition table, but which works fine with MacOS X and Linux. After partitioning a disk using default settings with MacOS X installer CD I installed MacOS X on its third partition and MacOS 9 on its second partition. Then: - booted the machine using squeeze testing installer cd and backed up partition table to a memory stick. - installed squeeze testing by manually removing the first HFS+ partition and then letting Guided partitioning to use the largest continuous free space. - rebooted into squeeze and observed that it works fine, it can mount and use all partitions - rebooted into MacOS X and observed that it also works fine, able to mount and use the partition containing MacOS 9 installation - rebooted into MacOS 9: - firmware finds the partition - loads MacOS 9 - MacOS 9 displays a small disk with a blinking question mark, not being able to find any partition - reboot into squeeze again - restore partition table from the memory stick - reboot into MacOS 9, it works fine - reboot into MacOS X, it works fine Hope this helps. signature.asc Description: OpenPGP digital signature
Bug#604134: ppc: after debian installation MacOS 9.2 won't recognize disk anymore
Package: installation-reports Severity: critical Tags: d-i Justification: breaks unrelated software (other OS on same computer) We did a clean new installation of MacOS 9.2.2, and subsequent the next step for setting up a dualboot system. We created 3 partitions with MacOS 9 (1 Linux with 71GB, two hfs+ 30GB) - the Linux partition was first on the disk, that's what the d-i manual recommends. Then we used the Debian netinstaller (default mode) to remove the Linux partition, because yaboot needs it's own extra partition. Then we let the installer do the automatic Linux partitioning for beginners, on the now empty space. The Debian installation worked flawlessly and all data are recognized from within debian (even the Mac OS data). However after rebooting the system, yaboot only found the debian installation but didn't know anything about the Mac OS 9 system present on the same hard drive. We manually added the Mac OS installation to yaboot.conf, which kind of worked (yaboot indeed switches to open firmware) but the Mac OS installation appears destroyed (the disk symbol with the blinking question mark). Next step was to reboot from MacOS 9 CD and see what the partitioning tool from MacOS can tell. Nothing. Laufwerke Konfigurieren (a German system - can't remember the English name for the partitioning tool) reports a not formatted IDE disc. As said above all MacOS 9 data are accessable from Debian, but it seems to us Debian partitioning tool is killing the non afflicted MacOS 9 partitions for MacOS 9. We don't know how to get our MacOS 9 system back. People who try to install Debian not at a seperat hard disk will get serious problems, as they not only have no dualboot system - they even would have no MacOS anymore and a kind of complete dataloss, ... Please let us know if we can help with further information. Also any hints how to get our MacOS installation back working without reinstalling (and thus killing Debian) would be appreciated. -- Package-specific info: Boot method: CD Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/powerpc/iso-cd/debian-testing-powerpc-netinst.iso Date: Fre Nov 19 16:43:35 CET 2010 Machine: Macintosh PPC G4 @1.4 GHz Partitions: df -Tl will do; the raw partition table is preferred dr...@g414:~$ df -Tl Dateisystem Typ1K#8208;Blöcke Benutzt Verfügbar Ben% Eingehängt auf /dev/hda12ext370154660 3691936 62899056 6% / tmpfstmpfs 256508 0256508 0% /lib/init/rw udev tmpfs 251548 220251328 1% /dev tmpfstmpfs 256508 0256508 0% /dev/shm dr...@g414:~$ The MacOS Volumes were hda10 and hda11. We guess the yaboot-partition is hda9 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [E] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[E] Overall install:[E] Comments/Problems: On the Partition hard drives error: After partitioning the hard drive in d-i, the open firmware and the MacOS installation CDROM both did not recognize any volumes anymore. Thus rendering the system unuseable. On the Install boot loader: d-i failed to setup the bootloader in way that the other OS can be loaded. This works for other platforms/OS, so we see no obvious reason why that shouldn't work on ppc/MacOS 9 too. See above for a detailed description of how we used the installer. -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=6.0 (squeeze) - installer build 20101119-00:04 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux G414 2.6.32-5-powerpc #1 Sat Oct 30 23:26:42 UTC 2010 ppc GNU/Linux lspci -knn: :00:0b.0 Host bridge [0600]: Apple Computer Inc. UniNorth AGP [106b:0020] lspci -knn: Kernel driver in use: agpgart-uninorth lspci -knn: :00:10.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon R200 QL [Radeon 8500 LE] [1002:514c] lspci -knn: Subsystem: ATI Technologies Inc Radeon R200 QL [Radeon 8500 LE] [1002:514c] lspci -knn: Kernel driver in use: radeonfb lspci -knn: 0001:10:0b.0 Host bridge [0600]: Apple Computer Inc. UniNorth PCI [106b:001f] lspci -knn: 0001:10:0d.0 PCI
Processed: Re: Bug#604134: ppc: after debian installation MacOS 9.2 won't recognize disk anymore
Processing commands for cont...@bugs.debian.org: reassign 604134 yaboot-installer Bug #604134 [installation-reports] ppc: after debian installation MacOS 9.2 won't recognize disk anymore Bug reassigned from package 'installation-reports' to 'yaboot-installer'. thanks Stopping processing here. Please contact me if you need assistance. -- 604134: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604134 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#604134: ppc: after debian installation MacOS 9.2 won't recognize disk anymore
reassign 604134 yaboot-installer thanks Quoting wit...@lnxnt.org (wit...@lnxnt.org): As said above all MacOS 9 data are accessable from Debian, but it seems to us Debian partitioning tool is killing the non afflicted MacOS 9 partitions for MacOS 9. We don't know how to get our MacOS 9 system back. People who try to install Debian not at a seperat hard disk will get serious problems, as they not only have no dualboot system - they even would have no MacOS anymore and a kind of complete dataloss, ... Please let us know if we can help with further information. Also any hints how to get our MacOS installation back working without reinstalling (and thus killing Debian) would be appreciated. If there's a surviving powerpc porter, hopefully signature.asc Description: Digital signature
Bug#604134: ppc: after debian installation MacOS 9.2 won't recognize disk anymore
I did further investigations if other people had similar problems, and indeed the problem occured several times. For example in 2008 here: http://lists.debian.org/debian-powerpc/2008/05/msg00047.html So it seems to be a common issue. But the solution which worked for José, and Samy back than, do not work in my case/with the latest test image. It's not that the different volumes are not activated/unmounted, it is that the entire hard disk, with all partitions, appears as not initialized! Maybe it is the same complex of problems - just a little bit more complicated now, as the Debian partitioning tool advanced? If so, it is maybe not too much work to fix this, and prevent users from beeing unable to have a dualboot system and loosing in unexpected ways the MacOS 9 installation? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#604134: ppc: after debian installation MacOS 9.2 won't recognize disk anymore
Processing commands for cont...@bugs.debian.org: clone 604134 -1 Bug#604134: ppc: after debian installation MacOS 9.2 won't recognize disk anymore Bug 604134 cloned as bug 604192. reassign -1 os-prober Bug #604192 [yaboot-installer] ppc: after debian installation MacOS 9.2 won't recognize disk anymore Bug reassigned from package 'yaboot-installer' to 'os-prober'. retitle -1 os-prober: Won't detect MacOS 9 Bug #604192 [os-prober] ppc: after debian installation MacOS 9.2 won't recognize disk anymore Changed Bug title to 'os-prober: Won't detect MacOS 9' from 'ppc: after debian installation MacOS 9.2 won't recognize disk anymore' severity -1 important Bug #604192 [os-prober] os-prober: Won't detect MacOS 9 Severity set to 'important' from 'critical' affects -1 yaboot-installer Bug #604192 [os-prober] os-prober: Won't detect MacOS 9 Added indication that 604192 affects yaboot-installer thanks Stopping processing here. Please contact me if you need assistance. -- 604192: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604192 -1: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=-1 604134: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604134 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#604134: ppc: after debian installation MacOS 9.2 won't recognize disk anymore
clone 604134 -1 reassign -1 os-prober retitle -1 os-prober: Won't detect MacOS 9 severity -1 important affects -1 yaboot-installer thanks I can confirm that os-prober takes a look at hfsplus partition containing MacOS 9, but won't report installed MacOS 9. Cloning to os-prober. signature.asc Description: OpenPGP digital signature
