Jump to content
19 posts in this topic

Recommended Posts

Recently I installed iATKOS v1.0ir2 on a partition on my slave drive. I'm wanting to dual boot it.

It's fully installed, I can browse the files and such on Ubuntu, but the problem is booting into it.

My OSes are as follows

Microsoft Windows XP - hd0,0

Ubuntu 7.10 - hd1,4

Mac OS X Leopard - hd1,6

 

My GRUB setup for Mac

 

rootnoverify (hd1,6)
makeactive
chainloader (hd1,4)/boot/OSX/chain0

 

I extracted chain0 from standalone/i386/ (I believe that's right directory) and moved it over to the Ubuntu partition as I was told to do.

Problem is it obviously doesn't work. GRUB Error 12.

 

I hope that's clear enough.

Thanks :)

 

-Pew

Link to comment
https://www.insanelymac.com/forum/topic/89292-dual-booting-grub-error/
Share on other sites

Get boot_v8 (The pc_efi bootloader)

(Google "pc_efi v8.0 download")

 

Copy it to /boot inside linux

 

Then edit /boot/grub/menu.lst

 

title Mac OSX Leopard

root (hd1,6) (use the values grub uses for Linux partition, not ones for OSX partition)

kernel /boot/boot_v8

boot

In my tri/quad boot systems using GRUB, OS X boots fine with the same menu.lst entry as WinXP. All I have to do is change the partition.

 

I don't have to specify any other file to boot.

 

title Mac OS X: Leopard

root (hd0,0)

makeactive

savedefault

chainloader +1

 

title Windows XP Professional

root (hd1,0)

makeactive

savedefault

chainloader +1

 

YMMV

Yes, but this configuration still works (I have to edit grub entries on the fly vs editing grub permanently) in other drive positions.

 

Mac OS still boots even as (hd2,0). I have Leopard and Tiger on the same drive and I can boot between both through GRUB. (hd2,1) or (hd0,1) or whatever. No matter the boot order, it stills works for me.

Hmm, well it doesn't seem to for me :)

 

Here's a list of my drives if that'll help

 

Disk /dev/sda: 81.9 GB, 81964302336 bytes

255 heads, 63 sectors/track, 9964 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Disk identifier: 0x912d912d

 

Device Boot Start End Blocks Id System

/dev/sda1 * 1 9963 80027766 7 HPFS/NTFS

 

Disk /dev/sdb: 200.0 GB, 200049647616 bytes

255 heads, 63 sectors/track, 24321 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Disk identifier: 0x18f37da6

 

Device Boot Start End Blocks Id System

/dev/sdb1 1 7194 57785773+ 7 HPFS/NTFS

/dev/sdb2 7195 23488 130881555 5 Extended

/dev/sdb5 7195 9744 20482843+ 83 Linux

/dev/sdb6 * 9745 14209 35865081 af Unknown

/dev/sdb7 14210 23456 74276496 7 HPFS/NTFS

/dev/sdb8 23457 23488 257008+ 82 Linux swap / Solaris

 

-Pew

Get boot_v8 (The pc_efi bootloader)

(Google "pc_efi v8.0 download")

 

Copy it to /boot inside linux

 

Then edit /boot/grub/menu.lst

 

title Mac OSX Leopard

root (hd1,6) (use the values grub uses for Linux partition, not ones for OSX partition)

kernel /boot/boot_v8

boot

Just saw your post.

I'm using SSE2 SSE3 Kernel and I was told EFI won't work, but I'll give it a shot.

 

-Pew

instead of grub use acronis its much easier thne grub from what i know

I don't know acronis at all, but grub is very easy to use, you just have to edit (with gedit, nano or kwrite) your /boot/grub/menu.lst

 

Boot from your favorite distro and add this lines at the end of the file : (open the file with Alt+F2, type gksudo gedit /boot/grub/menu.lst, then enter)

 

# Mac OS X Leopard

title Mac OS X Leopard

root (hd0,1)

makeactive

chainloader +1

 

You have to replace (hd0,1) with what you have, ie (hdn,p) with n number (less one) of your disk and p the number (less one) of your partition (in my case it's the 1st disk and the 2nd partition)

You save it, reboot and it should be OK

Hmm, well it doesn't seem to for me :P

 

Here's a list of my drives if that'll help

...

-Pew

I think I recall reading somewhere that it's better if OS X is installed on a primary partition in order to avoid booting problems, yet on yours it's on a logical partition (if i'm not mistaken). If none of the suggestions so far help, I'd try reinstalling it on a primary partition (on either your first or second drive - shouldn't matter).

 

I've also never needed any chain0 methods when using Grub, which I find terribly useful/convenient. Simply adding a Grub entry has worked for me so far, tho the entries have differed, not booting when I omitted a certain line, etc...

 

My GRUB entries, one with all OSes on one drive are:

title Mac OS X

root (hd0,2) <-- note: 3rd partition [on the only drive]

savedefault <-- note: not needed on my old rig.

makeactive

chainloader +1

 

The entry in my old rig, which has 2 disks: ubuntu + grub on one, OS X on the other:

title Mac OS X

root (hd1,1) <-- note: 2nd partition on the second drive

makeactive

chainloader --force +1

 

I hope one of these, or a variation thereof works for you...

All the best,

3phemeral

No no, Logical vs Primary are types of partitions, not their position on the drive. Logical partitions reside within extended partitions and often give boot troubles. If you want to boot an OS, it typically needs to be a primary partition for this reason.

 

Keep in mind that you are limited to a certain amount (five, I think) of primary partitions on an MBR drive.

 

Device Boot Start End Blocks Id System
/dev/sdb1 1 7194 57785773+ 7 HPFS/NTFS

/dev/sdb2 7195 23488 130881555 5 Extended

 

All of your partitions between 7195 and 23488 are within the sdb2 extended partition. This makes them logical partitions, if I'm not mistaken.

Not sure what tool you used to initially partition your drives, but in Linux Gparted or Partition Editor will show you logical or extended partitions vs primary partitions in the device overview. When you create a partition, you have the option of creating any of the three (and more).

 

The tricky part here is that you will more than likely lose your data on the drive during the modification. Backup before making any changes!

The tricky part here is that you will more than likely lose your data on the drive during the modification.
Not necessarily so; I've done lots of partition moves, resizings, etc... without losing any data. But:

Backup before making any changes!
Is NEVER a bad idea :) Be sure to back up the essentials ;) Things can always go wrong, not just messing around with partitions.

 

Boot_v8 just restarts my computer after it attempts to boot it.

 

-Pew

This also leads me to the question - is your hardware OSX compatible? Have you ever had it boot? If it's a no go, there's not much point in spending more time and effort trying to get it to work..

I, for instance, have been unable to load Leopard on my old rig, where Tiger ran near flawless.

 

 

I'd recommend you try to find a piece of software for Windows, called PowerQuest PartitionMagic, Version 8.0. This is a very easy program which allows moving/deleting/resizing of partitions, and suchlike. Once you have this, I can help you further to move/delete/resize partitions in order to be able to install OSX on a primary partition (on say, the drive which you have Ubuntu installed on). Send me a pm if you want/need further help, but i don't check this site every day and i'm very busy these days.

All the best,

3phemeral

Yeah it is, or least the guys at UpHuck's forums said it would with the SSE2/SSE3 kernel, darwin boot and remove all the power management and thermal kext stuff. EFI isn't supposed to work with my computer, and boot_v8 is for PC EFI.

I'll give it a few more goes. Thanks,

 

-Pew

×
×
  • Create New...