Jump to content
5 posts in this topic

Recommended Posts

I can install Tiger and it runs fine. I can install Leopard and it runs fine. Yet, when I partition the hard drive into 2 partitions, install Tiger and test that it runs ok, then install Leopard on the other partition, Tiger crashes before getting to the login window. It's there in the boot menu, and it starts to boot, loads a couple of kexts, but then there's a kernel panic with lots of numbers thrown on the screen. There's not enough information to tell what's causing the crash.

 

Why would installing Leopard on another partition mess up the already-working Tiger installation? That's just weird!

 

I know this isn't a lot of info to go on, but if anyone's got a dual-boot Tiger and Leopard setup, were there any gotcha's I should be aware of?

Ok, a little bit more info. I used the Leopard Disk Utility to partition the drive, and set it up to use MBR (I tried GUID but only got a fixed cursor when the boot manager should be displayed -- not sure what the problem was there, but using MBR I get the boot manager back). After partitioning the drive, I installed Tiger on one partition. After installation, I booted into Tiger, did the initial first-boot setup, re-booted again to make sure everything was working ok.

 

Then I installed Leopard on the other partition. Re-booted into Leopard and did the first-boot setup, then re-booted into Leopard again to make sure it was working ok.

 

Then I re-booted once again and selected Tiger from the boot menu. It crashes within about 1 second. I can't even boot into safe mode.

 

I've searched but haven't found anyone mentioning this problem. Does anyone have any ideas?

http://forum.insanelymac.com/index.php?showtopic=115636

 

but instead of NTFS + HFS you coud have HFS + HFS in first drive

 

Another solution is to asign a diferent boot plist file with the UUID included and when you want to boot the orher drive you can write "config=leopard"

 

leopard.plist resides where com.apple.Boot.plist is

Thanks for the tip macgirl, but I just found my problem. I'll describe it here in case someone else comes across this same problem. For some reason, when the Leopard boot loader tries to load Tiger, it's making Tiger load AppleEFIRuntime.kext. I booted into Leopard and deleted that kext from the Tiger partition, and now Tiger boots fine.

 

I just happened to see a post describing PC_EFI which said that the most common kernel panic was when the AppleEFIRuntime.kext hadn't been deleted. Although I wasn't using PC_EFI, I took a chance and deleted that kext from the Tiger partition. I don't know why it would be a problem when Leopard is installed and not a problem when Leopard isn't installed, but deleting it fixed my boot problem.

  • 9 months later...
Thanks for the tip macgirl, but I just found my problem. I'll describe it here in case someone else comes across this same problem. For some reason, when the Leopard boot loader tries to load Tiger, it's making Tiger load AppleEFIRuntime.kext. I booted into Leopard and deleted that kext from the Tiger partition, and now Tiger boots fine.

 

I just happened to see a post describing PC_EFI which said that the most common kernel panic was when the AppleEFIRuntime.kext hadn't been deleted. Although I wasn't using PC_EFI, I took a chance and deleted that kext from the Tiger partition. I don't know why it would be a problem when Leopard is installed and not a problem when Leopard isn't installed, but deleting it fixed my boot problem.

 

 

THANKS FOR THIS POST! i encountered the same problem. i deleted that kext file and i was able to boot into tiger now!

 

is there a way to make tiger boot as 1st choice instead of leopard?

×
×
  • Create New...