Jump to content
8 posts in this topic

Recommended Posts

Hi everyone. I am very curious to use PC_EFI on my hackintosh.

However, there is some very annoying problem. I followed the instructions to install PC_EFI on my Leopard partition: boot into the single user mode and execute the program to create a efi partition.

When I use the original kernel to boot, my machine reboot again and again. Very odd, I don't come across any kernel panic, just the unlimited reboot.

If anyone here knows what is source to cause this problem , would you please tell me? Thank you in advanced.

 

PS: I am using Intel Core 2 Duo E4300 on a Intel 945P + ICH7 motherboard.

I am running:

Tiger on /dev/rdisk0s1

Leopard on /dev/rdisk0s2

Windows on /dev/rdisk1s1(It seems that this one has no relation to the two above).

 

I use the hacked kext follows:

Titan.kext(to support my Geforce 7300GT).

AppleACPIplatform (from BrazilMac patch package ).

dsmos.kext

 

and with the EFIRuntime kext deleted.

 

With the hacked kernel, everything runs perfect. With the original kernel , I got the unlimited reboot.

The darwin loader loads the kernel. After the kernel loads the kexts, it reboots...

 

Very eager to receive any reply. Thank you again.

Link to comment
https://www.insanelymac.com/forum/topic/73635-unlimited-reboot-by-pc_efi/
Share on other sites

Hi everyone. I am very curious to use PC_EFI on my hackintosh.

However, there is some very annoying problem. I followed the instructions to install PC_EFI on my Leopard partition: boot into the single user mode and execute the program to create a efi partition.

When I use the original kernel to boot, my machine reboot again and again. Very odd, I don't come across any kernel panic, just the unlimited reboot.

If anyone here knows what is source to cause this problem , would you please tell me? Thank you in advanced.

 

PS: I am using Intel Core 2 Duo E4300 on a Intel 945P + ICH7 motherboard.

I am running:

Tiger on /dev/rdisk0s1

Leopard on /dev/rdisk0s2

Windows on /dev/rdisk1s1(It seems that this one has no relation to the two above).

 

I use the hacked kext follows:

Titan.kext(to support my Geforce 7300GT).

AppleACPIplatform (from BrazilMac patch package ).

dsmos.kext

 

and with the EFIRuntime kext deleted.

 

With the hacked kernel, everything runs perfect. With the original kernel , I got the unlimited reboot.

The darwin loader loads the kernel. After the kernel loads the kexts, it reboots...

 

Very eager to receive any reply. Thank you again.

 

I think I encountered your problem in one of my install tries, altho mine reboots after just a few lines into the Darwin boot.

 

Looking at your list, you have the Tiger partition as active right? So I think this is where it picks up its boot loader which doesnt have PC_EFI. So when you select the Leopard partition PC_EFI will not be loaded, hence the orig kernel doesnt like what it sees and reboots. So either make the Leopard partition active or load PC_EFI on the Tiger install.

Thank you very much for your guidance. Royco.

The problem is that I have also installed the PC_EFI and Darwin loader on my Tiger partition. So according to your theory, I use the Darwin loader on the active Tiger partition to boot Leopard, it must pick the darwin loader with PC_EFI. Very odd issue.

 

Your help is useful to me. I will try later.

Greetings.

Well, im not so sure about the theory but When I had my Tiger on the first partition and Leopard on the second, it boots fine with Modified kernel. If I have the original kernel it goes on a boot cycle. So what I did was make the Leopard partition active, booted aok with orig kernel. Installed EFI on tiger and made it active partition, leopard now boots aok with orig kernel.

 

Give it a try and see if it works for you.

Yes,Royco. I got your meaning. You must repair the Leopard boot by active the partition it resides first. When the Leopard can boot normally with the vanilla kernel, you transform the tiger patition to an EFI one and active it, then the tiger partition can boot normally with the vanilla kernel for tiger. Am I right?

Yes,Royco. I got your meaning. You must repair the Leopard boot by active the partition it resides first. When the Leopard can boot normally with the vanilla kernel, you transform the tiger patition to an EFI one and active it, then the tiger partition can boot normally with the vanilla kernel for tiger. Am I right?

 

 

Yes, but if you want to keep the Leopard as active then no need to install EFI on Tiger, but it would hurt to do so.

×
×
  • Create New...