/sbin/lilo fails on SuSE10 install on Mac Mini
I'm trying to install SuSE10 on a Mac Mini, having successfully installed it on an old iMac DV400. I carefully followed all the directions at http://www.opensuse.org/PPC, and the install goes through OK, but nothing I can do will persuade lilo to be happy. When I run it, I get: linux:~ # /sbin/lilo running on pmac_new BOOT_DEVICEPATH = /pci@f4000000/ata-6@d/disk@0:2 OTHER_DEVICEPATH = /pci@f4000000/ata-6@d/disk@0:7 hmount: /dev/hda2: not a Macintosh HFS volume (Invalid argument) It's this last line I'm concerned about. The partition map is: Partition map (with 512 byte blocks) on '/dev/hda' #: type name length base ( size ) 1: Apple_partition_map 'Apple ' 63 @ 1 2: Apple_Bootstrap 'bootstrap ' 20480 @ 64 ( 10.0M) 3: Apple_HFS 'spare_hfs ' 20480 @ 20544 ( 10.0M) 4: Linux 'spare_linux ' 20480 @ 41024 ( 10.0M) 5: Linux 'swap ' 2048000 @ 61504 (1000.0M) 6: Linux 'root ' 106573104 @ 2109504 ( 50.8G) 7: Apple_HFS 'Apple_HFS_Untitled_4' 47618864 @ 108682608 ( 22.7G) 8: Apple_Free ' ' 16 @ 156301472 My reading of the opensuse.org web pages is that I should direct the bootloader to /dev/hda2. hda6 is root. hda7 contains a MacOS install. My lilo.conf is: boot=/dev/hda2 timeout=100 default=linux activate image=/boot/vmlinux initrd=/boot/initrd label=linux append="root=/dev/hda6 sysrq=1" other=/dev/hda7 label=macos What am I doing wrong? J
On Sun, Oct 30, Julian Seward wrote:
hmount: /dev/hda2: not a Macintosh HFS volume (Invalid argument)
Run 'hformat /dev/hda2' to create a HFS filesystem. It is probably hfsplus. -- short story of a lazy sysadmin: alias appserv=wotan
Alle 20:53, domenica 30 ottobre 2005, Julian Seward ha scritto:
I'm trying to install SuSE10 on a Mac Mini, having successfully installed it on an old iMac DV400. I carefully followed all the directions at http://www.opensuse.org/PPC, and the install goes through OK, but nothing I can do will persuade lilo to be happy.
When I run it, I get:
linux:~ # /sbin/lilo running on pmac_new BOOT_DEVICEPATH = /pci@f4000000/ata-6@d/disk@0:2 OTHER_DEVICEPATH = /pci@f4000000/ata-6@d/disk@0:7 hmount: /dev/hda2: not a Macintosh HFS volume (Invalid argument)
It's this last line I'm concerned about. The partition map is:
Partition map (with 512 byte blocks) on '/dev/hda' #: type name length base ( size ) 1: Apple_partition_map 'Apple ' 63 @ 1 2: Apple_Bootstrap 'bootstrap ' 20480 @ 64 ( 10.0M) 3: Apple_HFS 'spare_hfs ' 20480 @ 20544 ( 10.0M) 4: Linux 'spare_linux ' 20480 @ 41024 ( 10.0M) 5: Linux 'swap ' 2048000 @ 61504 (1000.0M) 6: Linux 'root ' 106573104 @ 2109504 ( 50.8G) 7: Apple_HFS 'Apple_HFS_Untitled_4' 47618864 @ 108682608 ( 22.7G) 8: Apple_Free ' ' 16 @ 156301472
My reading of the opensuse.org web pages is that I should direct the bootloader to /dev/hda2. hda6 is root. hda7 contains a MacOS install. My lilo.conf is:
boot=/dev/hda2 timeout=100 default=linux activate
image=/boot/vmlinux initrd=/boot/initrd label=linux append="root=/dev/hda6 sysrq=1"
other=/dev/hda7 label=macos
What am I doing wrong?
J
may be you formatted under suse your bootstrap partition. You can do with disk utility under mac os side hfs not hfsplus and then re run lilo
On Sunday 30 October 2005 20:07, Olaf Hering wrote:
On Sun, Oct 30, Julian Seward wrote:
hmount: /dev/hda2: not a Macintosh HFS volume (Invalid argument)
Run 'hformat /dev/hda2' to create a HFS filesystem. It is probably hfsplus.
I now have a working MacOS + SuSE10 dual-boot setup. All the required info is in the pages at http://www.opensuse.org/PPC_Partitioning, but even as a long-time Linux/SuSE user I found the documentation fragmented and confusing. I have written a 1-page summary of everything I had to do to get a working installation on my Mac Mini. It references the other pages in http://www.opensuse.org/PPC_Partitioning and gives a big- picture overview of what needs to happen. It is attached below. Is it appropriate to add it as a top level link from http://www.opensuse.org/POWER%40SUSE, for example with the name "Overview of installing SuSE 10 on a Mac Mini" ? Having such a summary would have saved me many hours. J ---------------- I managed to install a dual-boot arrangement of SuSE 10 and MacOSX 10.4 on a Mac Mini. The result works nicely. As a long-time user of SuSE on x86/amd64, but mostly unfamiliar with ppc hardware, I found the experience confusing and time consuming. In fact it's pretty easy. Here I offer a big-picture of what to do in the hope that it will save you time and frustration. First off, I should point out, all the relevant details already exist in this Wiki, starting at http://www.opensuse.org/POWER%40SUSE, and you need to read them. Read this first though. 1. Boot with MacOSX 10.3 install CD. Go into the Disk Utility (from the menu bar that you get immediately after the installer starts up). Delete all previous partitions. Select the 2-partition scheme. The first partition will be for SuSE and the second for MacOS. Make the first partition be empty space, and the second partition be the default MacOS type (MacOS Extended Journalled). 2. Install MacOSX 10.3 in the second partition. Reboot with the 10.4 upgrade CD and upgrade accordingly. Run some (online update, reboot) cycles until the online updater is done. Check you can boot into MacOS and quit and it works. That concludes the MacOS part. 3. Boot from the SuSE10 CD 1. When prompted by yaboot type: install start_shell. Use pdisk to partition the free space as described at http://www.opensuse.org/PPC_Partitioning. In short, you need to replace the free space with 3 partitions: a tiny 800k one of type 'Apple_Bootstrap', a swap partition of type 'Linux', and a root partition also of type 'Linux'. The first one is not optional; it is the place where the bootloader will eventually go. 4. Continue as described in http://www.opensuse.org/PPC_Partitioning: exit the initial shell, which lets the main body of the installer run. Be particularly careful to only let YaST format the swap and root partitions, exactly as described in "Bootloader setup" on the page. 5. After chewing through CD 1, YaST will complain that the bootloader installation failed. Ignore that and let it reboot, still on CD 1. Read "Bootloader Installation (lilo or yaboot)" in http://www.opensuse.org/PPC_Installation_Issues. Let the YaST installer start again, but this time, when asked for the installation type (new/upgrade/other), select other and then "boot into installed system". Continue with the package installation, which will use CDs 2-5. When done, log into the resulting system as root, and create an /etc/lilo.conf as described on http://www.opensuse.org/PPC_Installation_Issues. The "boot=" should point to the 'Apple_Bootstrap' partition you made (hopefully /dev/hda2) and root= to your root partition. I skipped the "resume=..." part as this is not a laptop. 6. Run lilo. It barfs: "hmount: /dev/hda2: not a Macintosh HFS volume (Invalid argument)" because /dev/hda2 is an HFS+ partition, not an HFS one. Do "hformat /dev/hda2" to fix it. Re-run lilo and this time it should succeed. You should now have a bootable system. Check you can reboot into SuSE, into MacOS, and back into SuSE with no problems. 7. Back in SuSE land, X may not work -- it didn't for me. The installer decided on 1280x1024x76Hz, which sounds reasonable, but my flat-panel display didn't like the 76Hz bit and refused to display anything. In the end I plugged in a good old-fashioned CRT monitor to see what was going on, then asked YaST to drop the frame rate to 60Hz. Another getting-started kludge is to do "cp /etc/X11/xorg.conf.install /etc/X11/xorg.conf", which gets you the same X setup as the initial installer has. This worked for me, but had insufficient colour depth and no acceleration and so is not a good long-term solution.
On Mon, Oct 31, Julian Seward wrote:
All the required info is in the pages at http://www.opensuse.org/PPC_Partitioning, but even as a long-time Linux/SuSE user I found the documentation fragmented and confusing.
We need a professional docu writer, be we dont have a spare one.
I have written a 1-page summary of everything I had to do to get a working installation on my Mac Mini. It references the other pages in http://www.opensuse.org/PPC_Partitioning and gives a big- picture overview of what needs to happen.
If you can improve the existing docu, that would help.
It is attached below. Is it appropriate to add it as a top level link from http://www.opensuse.org/POWER%40SUSE, for example with the name "Overview of installing SuSE 10 on a Mac Mini" ? Having such a summary would have saved me many hours.
It is not specific to the Mac Mini.
1. Boot with MacOSX 10.3 install CD. Go into the Disk Utility (from the menu bar that you get immediately after the installer starts up). Delete all previous partitions. Select the 2-partition scheme. The first partition will be for SuSE and the second for MacOS. Make the first partition be empty space, and the second partition be the default MacOS type (MacOS Extended Journalled).
Ordering doesnt really matter.
3. Boot from the SuSE10 CD 1. When prompted by yaboot type: install start_shell. Use pdisk to partition the free space as described at http://www.opensuse.org/PPC_Partitioning. In short, you need to replace the free space with 3 partitions: a tiny 800k one of type 'Apple_Bootstrap', a swap partition of type 'Linux', and a root partition also of type 'Linux'. The first one is not optional; it is the place where the bootloader will eventually go.
No Apple_Bootstrap is required. This is only a workaround for a missing valid MacOS 9 System Folder. lilo will create a valid System Folder, with a 'System' and 'Finder' file, with the proper creator/type attributes. Apple_HFS as type is correct. It allows one to tweak the settings from MacOS, if there is a need to do so. A HFS partition must be at least 800k, thats correct.
7. Back in SuSE land, X may not work -- it didn't for me. The installer decided on 1280x1024x76Hz, which sounds reasonable, but my flat-panel display didn't like the 76Hz bit and refused to display anything. In the end I plugged in a good old-fashioned CRT monitor to see what was going on, then asked YaST to drop the frame rate to 60Hz.
This would be a bug in hwinfo or in Sax. Can you check if the monitor can be detected at all? Run 'hwinfo --monitor' and see if it finds anything useful. If you see valid data for your monitor, open a bug. Attach the 'hwinfo' and 'lsprop -R /proc/device-tree' output, and the /var/log/SaX.log and /var/log/Xorg.*.log* files. -- short story of a lazy sysadmin: alias appserv=wotan
participants (3)
-
andrea -
Julian Seward -
Olaf Hering