Jump to content

[Guide] Boot from EFI partition, zero modification installs on Intel SSE2 or better...


munky
 Share

1,404 posts in this topic

Recommended Posts

bladerunner - thanks. here goes:

Can you show me what your /Volumes/EFI directory looks like? Including /Volumes/EFI/System/Booter.

 

bash-3.2# ls -l /volumes/efi

total 152

drwx------ 5 root admin 170 Oct 9 10:40 .fseventsd

drwxr-xr-x 3 root admin 102 Oct 9 10:39 System

-rw-r--r--@ 1 root admin 63744 Oct 19 14:46 boot

drw-r--r--@ 20 root wheel 680 Oct 19 21:51 extensions

-rw-r--r-- 1 root admin 6522 Oct 19 16:57 update.log

-rwxr-xr-x 1 root admin 727 Oct 19 17:47 update.sh

bash-3.2# ls -l /volumes/efi/extensions

total 32

-rw-r--r--@ 1 root wheel 12292 Oct 19 21:51 .DS_Store

drw-r--r-- 3 root wheel 102 Oct 19 21:51 ACPIPS2Nub.kext

drw-r--r--@ 3 root wheel 102 Oct 19 21:51 AppleACPIPlatform.kext

drw-r--r--@ 3 root wheel 102 Oct 19 21:51 AppleAHCIPort.kext

drw-r--r-- 3 root wheel 102 Oct 19 21:51 AppleAzaliaAudio.kext

drw-r--r-- 3 root wheel 102 Oct 19 21:51 AppleBCM440XEthernet.kext

drw-r--r-- 3 root wheel 102 Oct 19 21:51 AppleBCM5751Ethernet.kext

drw-r--r--@ 3 root wheel 102 Oct 19 21:51 AppleDecrypt.kext

drw-r--r-- 3 root wheel 102 Oct 19 21:51 AppleSMBIOS.kext

drw-r--r-- 3 root wheel 102 Oct 19 21:51 AppleSMBIOSEFI.kext

drw-r--r--@ 3 root wheel 102 Oct 19 21:51 Disabler.kext

drw-r--r-- 4 root wheel 136 Oct 19 21:51 Dont Steal Mac OS X.kext

drw-r--r--@ 3 root wheel 102 Oct 19 21:51 IOAHCIFamily.kext

drw-r--r--@ 3 root wheel 102 Oct 19 21:51 IOATAFamily.kext

drw-r--r--@ 3 root wheel 102 Oct 19 21:51 JMicronATA.kext

drw-r--r--@ 3 root wheel 102 Oct 19 21:51 OpenHaltRestart.kext

drw-r--r--@ 3 root wheel 102 Oct 19 21:51 dsmos.kext

drw-r--r-- 21 root wheel 714 Oct 19 21:51 lspcidrv.kext

bash-3.2# ls -l /volumes/efi/system/booter

total 0

drwxr-xr-x 2 root admin 68 Sep 30 01:06 Extensions

bash-3.2#

 

Are you using Munkys' update.sh script to build the Extensions.mkext?

i have used it and not used it. for debugging i have not used it so i can watch the kexts loading fly by during boot.

 

Which kernel is being used?

i have 10.5.4

 

Oh, and what about your system specs. CPU type etc. It's not in your signature. It may help to know that as well. thanks for the hint. see below.

thank you!

ghoffman

--------------------

hp nc6320 with cpus=1 to avoid hpet error; leopard 10.5.4 via iatkos4i on guid partition install; munky's bootloader v5.1 for efi; mac smbios 28+ smbiosefi; gma900 working; dell 1490 wifi card drop-in working; ad1981 sound onboard speakers working; sleep and wake working (except for lid open).

Link to comment
Share on other sites

I am sure they are all aimed at the same basic problem. However they do use different methods of reaching their goal. I tried all three. The only one that did not give me a kernel panic was the SMBIOSresolver by SuperHi. Also, it allowed me to modify some settings by changing the Info.plist. I think that at least one of the others requires a re-compile and I thought that was a bit cumbersome.

 

I guess the idea is to try each and pick the one that works best for you. That's what I did. :mellow:

 

May I know which kexts have you used for your machine? I'm still unable to figure out which proper kexts I should use to add proper boot device -- although I added supposed AppleIntelPIIXATA.kext for my ICH5, I still get "waiting for boot device" message.

 

Right now, my /Volumes/EFI/Extensions folder is pretty much minimalist: AppleDecrypt,kext, Disabler.kext and IOATAFamily.kext. I got others for my sound and video cards but will not add them until I am able to boot.

 

Thanks.

Link to comment
Share on other sites

bladerunner - thanks. here goes:

Can you show me what your /Volumes/EFI directory looks like? Including /Volumes/EFI/System/Booter.

 

bash-3.2# ls -l /volumes/efi

total 152

drwx------ 5 root admin 170 Oct 9 10:40 .fseventsd

drwxr-xr-x 3 root admin 102 Oct 9 10:39 System

-rw-r--r--@ 1 root admin 63744 Oct 19 14:46 boot

drw-r--r--@ 20 root wheel 680 Oct 19 21:51 extensions

-rw-r--r-- 1 root admin 6522 Oct 19 16:57 update.log

-rwxr-xr-x 1 root admin 727 Oct 19 17:47 update.sh

bash-3.2# ls -l /volumes/efi/extensions

total 32

-rw-r--r--@ 1 root wheel 12292 Oct 19 21:51 .DS_Store

drw-r--r-- 3 root wheel 102 Oct 19 21:51 ACPIPS2Nub.kext

drw-r--r--@ 3 root wheel 102 Oct 19 21:51 AppleACPIPlatform.kext

drw-r--r--@ 3 root wheel 102 Oct 19 21:51 AppleAHCIPort.kext

drw-r--r-- 3 root wheel 102 Oct 19 21:51 AppleAzaliaAudio.kext

drw-r--r-- 3 root wheel 102 Oct 19 21:51 AppleBCM440XEthernet.kext

drw-r--r-- 3 root wheel 102 Oct 19 21:51 AppleBCM5751Ethernet.kext

drw-r--r--@ 3 root wheel 102 Oct 19 21:51 AppleDecrypt.kext

drw-r--r-- 3 root wheel 102 Oct 19 21:51 AppleSMBIOS.kext

drw-r--r-- 3 root wheel 102 Oct 19 21:51 AppleSMBIOSEFI.kext

drw-r--r--@ 3 root wheel 102 Oct 19 21:51 Disabler.kext

drw-r--r-- 4 root wheel 136 Oct 19 21:51 Dont Steal Mac OS X.kext

drw-r--r--@ 3 root wheel 102 Oct 19 21:51 IOAHCIFamily.kext

drw-r--r--@ 3 root wheel 102 Oct 19 21:51 IOATAFamily.kext

drw-r--r--@ 3 root wheel 102 Oct 19 21:51 JMicronATA.kext

drw-r--r--@ 3 root wheel 102 Oct 19 21:51 OpenHaltRestart.kext

drw-r--r--@ 3 root wheel 102 Oct 19 21:51 dsmos.kext

drw-r--r-- 21 root wheel 714 Oct 19 21:51 lspcidrv.kext

bash-3.2# ls -l /volumes/efi/system/booter

total 0

drwxr-xr-x 2 root admin 68 Sep 30 01:06 Extensions

bash-3.2#

 

Are you using Munkys' update.sh script to build the Extensions.mkext?

i have used it and not used it. for debugging i have not used it so i can watch the kexts loading fly by during boot.

 

Which kernel is being used?

i have 10.5.4

 

Oh, and what about your system specs. CPU type etc. It's not in your signature. It may help to know that as well. thanks for the hint. see below.

thank you!

ghoffman

--------------------

hp nc6320 with cpus=1 to avoid hpet error; leopard 10.5.4 via iatkos4i on guid partition install; munky's bootloader v5.1 for efi; mac smbios 28+ smbiosefi; gma900 working; dell 1490 wifi card drop-in working; ad1981 sound onboard speakers working; sleep and wake working (except for lid open).

 

 

OK! Well, there are some things that don't make sense to me. Some may, or may not, be part of your problem.

 

When I asked about CPU type I wanted to know if you had a core2duo or some other processor that would allow you to run the vanilla kernel. I don't think I saw that in your answer. You did say you had a 9.4 kernel. I am assuming that is a patched - non-vanilla kernel. If I am wrong, please clarify.

 

The list of kext you are using is a bit confusing. You list:

drw-r--r--@ 3 root wheel 102 Oct 19 21:51 AppleDecrypt.kext
drw-r--r-- 3 root wheel 102 Oct 19 21:51 AppleSMBIOS.kext
drw-r--r-- 3 root wheel 102 Oct 19 21:51 AppleSMBIOSEFI.kext
drw-r--r--@ 3 root wheel 102 Oct 19 21:51 Disabler.kext
drw-r--r-- 4 root wheel 136 Oct 19 21:51 Dont Steal Mac OS X.kext
drw-r--r--@ 3 root wheel 102 Oct 19 21:51 IOAHCIFamily.kext
drw-r--r--@ 3 root wheel 102 Oct 19 21:51 IOATAFamily.kext
drw-r--r--@ 3 root wheel 102 Oct 19 21:51 JMicronATA.kext
drw-r--r--@ 3 root wheel 102 Oct 19 21:51 OpenHaltRestart.kext
drw-r--r--@ 3 root wheel 102 Oct 19 21:51 dsmos.kext

 

I don't understand using AppleSMBIOS and AppleSMBIOSEFI togather. AppleSMBIOSEFI should allow you to use the vanilla AppleSMBIOS. i.e., I would use one or the other, but not both.

 

I don't understand having "Dont Steal Mac OS X.kext" your decrypt kext are there to override it. I would remove it.

 

You don't need "AppleDecrypt.kext" and "dsmos.kext" they are both doing the same thing. Pick one and remove the other.

 

Back to the kernel for a moment. If you are not running the vanilla (Apple supplied) kernel, then the kernel you are using should reside in "/Volumes/EFI" e.g., "/Volumes/EFI/mach_kernel.voodoo"

 

 

 

May I know which kexts have you used for your machine? I'm still unable to figure out which proper kexts I should use to add proper boot device -- although I added supposed AppleIntelPIIXATA.kext for my ICH5, I still get "waiting for boot device" message.

 

Right now, my /Volumes/EFI/Extensions folder is pretty much minimalist: AppleDecrypt,kext, Disabler.kext and IOATAFamily.kext. I got others for my sound and video cards but will not add them until I am able to boot.

 

Thanks.

 

sure, not a problem. I have a vanilla retail install of 10.5.1 updated to 10.5.5 via Apple software update. The ONLY change in the OS X partition is com.apple.Boot.plist. That is to add the pointer to the patched kernel I need and boot-uuid= to point to the partition being booted.

 

The /Volumes/EFI/Extensions used to build the Extensions.mkext cache has the following:

bash-3.2# ls -l /Volumes/EFI/Extensions
total 0
drw-r--r--  3 root  wheel  102 Oct  8 09:28 AppleACPIPlatform.kext
drw-r--r--  3 root  wheel  102 Oct  8 09:28 AppleDecrypt.kext
drw-r--r--@ 3 root  wheel  102 Oct  8 09:28 ApplePS2Controller.kext
drw-r--r--@ 3 root  wheel  102 Oct  8 09:28 Disabler.kext
drw-r--r--  3 root  wheel  102 Oct  8 22:26 IOATAFamily.kext
drw-r--r--@ 3 root  wheel  102 Oct 16 13:03 SMBIOSResolver.kext

 

and the Boot.plist has:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>Graphics Mode</key>
	<string>"1280x1024x24"</string>
	<key>Kernel</key>
	<string>bt(0,0)/mach_kernel.voodoo-b1</string>
	<key>Kernel Flags</key>
	<string>-v boot-uuid=0802587B-4CBE-3E24-9A92-09AD0D296CE2</string>
	<key>Timeout</key>
	<string>7</string>
	<key>device-properties</key>

 

Hope that helps.

Link to comment
Share on other sites

bladerunner said -

When I asked about CPU type I wanted to know if you had a core2duo or some other processor that would allow you to run the vanilla kernel. I don't think I saw that in your answer. You did say you had a 9.4 kernel. I am assuming that is a patched - non-vanilla kernel. If I am wrong, please clarify.

------

 

thanks for your help, bladerunner.

it is a core2duo t5600. kernel is vanilla.

 

i clearly don't understand enough about what smbios.kext does to make a good choice; alittle trial and error got me to where i am.

i also don;t understand dsmos vs dontstealmacos.

 

i'll follow your suggestions and see.

 

thanks,

Link to comment
Share on other sites

Fixed this. The culprit was in fact a previous install of Chameleon that was not completely removed.

 

I followed through Phase 5 and on the test boot I get the following error:

 

boot0: GPT

boot0: HFS+

boot0: booting

boot0: done

HFS+ partition error

 

Now, if I use my previous Boot132 ISO I can boot through to the point where I choose my hard disk and load OSX and all is fine.

 

Suggestions?

Link to comment
Share on other sites

Just wanted to say thanks for the excellent writeup Munky. I was able to install a retail OSX and boot from the EFI partition. I'm currently using the voodoo kernel and it seems to be working fine with my Core Duo machine. I might try the vanilla w/TSC patch later just to see.

 

Is there a writeup on the various kernels and what they do differently? I know non-SSE3 machines need a patched kernel, but I haven't seen much about the differences between the various kernels.

 

I did confirm that formatting does change the UUID of the boot drive (I did a re-install). Boot once with the CD and cut-paste the UUID from Disk Manager into the boot.plist and all is well again.

 

I was able to use software update to update to 10.5.5 and everything else it shoves down. All seems well. Just need to get some drivers installed and I should be good to go. Thanks!

Link to comment
Share on other sites

my system, using munky's boot v5.1, is still crashing (at 31%) during 10.5.5 update from 10.5.4. i have to reboot and i don't know if the whole update finished.

appleintelcpupowermanagement.kext is still loading from the update, and needs to be deleted with -s flag on boot..

there is also a gma900 issue requiring use of 'gma900 by nick14' - thanks nick.

my /volumes/efi/extensions folder has these kexts:

 

sh-3.2# ls -l /volumes/efi/extensions

total 32

-rw-r--r--@ 1 root wheel 12292 Oct 21 16:13 .DS_Store

drw-r--r-- 3 root wheel 102 Oct 21 16:13 ACPIPS2Nub.kext

drw-r--r--@ 3 root wheel 102 Oct 21 16:13 AppleACPIPlatform.kext

drw-r--r--@ 3 root wheel 102 Oct 21 16:13 AppleAHCIPort.kext

drw-r--r-- 3 root wheel 102 Oct 21 16:13 AppleAzaliaAudio.kext

drw-r--r-- 3 root wheel 102 Oct 21 16:13 AppleBCM440XEthernet.kext

drw-r--r-- 3 root wheel 102 Oct 21 16:13 AppleBCM5751Ethernet.kext

drw-r--r-- 3 root wheel 102 Oct 21 16:13 ApplePS2Controller.kext

drw-r--r--@ 3 root wheel 102 Oct 21 16:13 Disabler.kext

drw-r--r--@ 3 root wheel 102 Oct 21 16:13 IOAHCIFamily.kext

drw-r--r--@ 3 root wheel 102 Oct 21 16:13 IOATAFamily.kext

drw-r--r-- 3 root wheel 102 Oct 21 16:13 IntelCPUPMDisabler.kext

drw-r--r--@ 3 root wheel 102 Oct 21 16:13 OpenHaltRestart.kext

drw-r--r-- 3 root wheel 102 Oct 21 16:13 SMBIOSEnabler.kext

drw-r--r--@ 3 root wheel 102 Oct 21 16:13 dsmos.kext

sh

 

anyone see the problem here?

disabler.kext plist looks like this

 

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

<key>CFBundleDevelopmentRegion</key>

<string>English</string>

<key>CFBundleExecutable</key>

<string>Disabler</string>

<key>CFBundleGetInfoString</key>

<string>Kernel Extension Disabler 1.0.1, Copyright © 2008 by Kabyl</string>

<key>CFBundleIdentifier</key>

<string>net.osrom.kext.Disabler</string>

<key>CFBundleInfoDictionaryVersion</key>

<string>6.0</string>

<key>CFBundleName</key>

<string>Kernel Extension Disabler</string>

<key>CFBundlePackageType</key>

<string>KEXT</string>

<key>CFBundleVersion</key>

<string>1.0.1</string>

<key>IOKitPersonalities</key>

<dict>

<key>EFIRuntimeDisabler</key>

<dict>

<key>CFBundleIdentifier</key>

<string>net.osrom.kext.Disabler</string>

<key>IOClass</key>

<string>Disabler</string>

<key>IOMatchCategory</key>

<string>AppleEFIRuntime</string>

<key>IOProbeScore</key>

<integer>1000</integer>

<key>IOProviderClass</key>

<string>AppleACPIPlatformExpert</string>

<key>IOResourceMatch</key>

<string>ACPI</string>

</dict>

<key>IntelCPUPMDisabler</key>

<dict>

<key>CFBundleIdentifier</key>

<string>net.osrom.kext.Disabler</string>

<key>IOClass</key>

<string>Disabler</string>

<key>IOMatchCategory</key>

<string>AppleIntelCPUPowerManagement</string>

<key>IOProbeScore</key>

<integer>1000</integer>

<key>IOProviderClass</key>

<string>IOResources</string>

<key>IOResourceMatch</key>

<string>IOKit</string>

</dict>

<key>SMCPlatformPluginDisabler</key>

<dict>

<key>CFBundleIdentifier</key>

<string>net.osrom.kext.Disabler</string>

<key>IOClass</key>

<string>Disabler</string>

<key>IOMatchCategory</key>

<string>ACPI_SMC_PlatformPlugin</string>

<key>IOProbeScore</key>

<integer>2000</integer>

<key>IOProviderClass</key>

<string>AppleACPICPU</string>

<key>IOResourceMatch</key>

<string>ACPI</string>

</dict>

</dict>

<key>OSBundleLibraries</key>

<dict>

<key>com.apple.kernel.iokit</key>

<string>1.1</string>

</dict>

<key>OSBundleRequired</key>

<string>Root</string>

</dict>

</plist>

 

the .kexts load visibly on boot -

any help would be apprecited.

thanks,

Link to comment
Share on other sites

Fixed this. The culprit was in fact a previous install of Chameleon that was not completely removed.

 

Good to hear, really important to clear out previously installed Chameleon!

 

Wanted to confirm, when you have KEXT's that are put in the EFI Partition (or a Boot-132 CD), which contain embedded KEXT's in their "PlugIns" folder, do you have to modify each sub-KEXTs' Info.plist to add

<key>OSBundleRequired</key>
<string>Root</string>

at the end?

 

I'm having some difficulty getting a Retail Leopard install to use all (not just some) of the KEXT's on my EFI partition, yet all have the OSBundleRequired lines. KEXT for my LAN aren't loading (see sig for specs). I have not employed any EFI Strings. Is it possible to use EFI Strings for for a NIC?

 

Thanks for any help.

Link to comment
Share on other sites

ok, more probing, more reading, less clarity, and more questions.

 

1st basic question: does munky's bootloader require an .mkext file, or will it load kexts? does it load kexts from

/EFI/Extensions, or from /EFI/System/Booter/Extensions, or both?

 

2nd: is there a way to verify extensions loaded? i see them fly by, but not all appear to be loaded when i use system profiler/extensions

 

3rd: if the kexts require /root at the end, do they not get loaded with safe boot ? (at least one of the kexts in my /efi/extensions folder had /safe boot at the end, not /root) ?

 

thanks

Link to comment
Share on other sites

ok, more probing, more reading, less clarity, and more questions.

 

1st basic question: does munky's bootloader require an .mkext file, or will it load kexts? does it load kexts from

/EFI/Extensions, or from /EFI/System/Booter/Extensions, or both?

 

2nd: is there a way to verify extensions loaded? i see them fly by, but not all appear to be loaded when i use system profiler/extensions

 

3rd: if the kexts require /root at the end, do they not get loaded with safe boot ? (at least one of the kexts in my /efi/extensions folder had /safe boot at the end, not /root) ?

 

thanks

 

1A - no, the Extensions.mkext is not required - it is preferred, but not required.

 

1B - it is my understanding, based on observation that the kext load only from /Volumes/EFI/System/Booter/Extensions

 

I can't really help with the other two items. I always went with the idea that if the kext had made things work when it was in S/L/E and they were now not working, the kext had not loaded. Still, that is a brute force trial and error method :)

Link to comment
Share on other sites

bladerunner -

thanks.

i also reached the conclusion that only kexts in /efi/system/booter/extensions would load. there does seem to be some difference in whether they are in an mkext or not - i think something with dependencies... but i don;t know.

my system now survives a 10.5.5 upgrade, save for power management.

Link to comment
Share on other sites

Hi I have just installed 10.5 retail with a cd built from ~Galaxy's script then used this EFI Partition booting method. Booting 10.5 with nvkush in my efi partition I had QE and CI, after the update nvkush is loaded but no more QE and CI, seems the GeForce.kext is still loading after the update. anyone have any ideas ?

 

nvkush works fine on another 10.5.5 install I have .. tho thats with using chameleon to boot the partition and putting extensions in s/l/e.

Link to comment
Share on other sites

Followed every step as the tutorial says and all goes fine.

 

But still not able to boot.

 

 

dev/disk2

	 #:					   TYPE NAME					SIZE	   IDENTIFIER

	 0:	  GUID_partition_scheme						*149.1 Gi   disk2

	 1:						EFI						 200.0 Mi   disk2s1

	 2:				  Apple_HFS Macintosh			   45.0 Gi	disk2s2

	 3:				  Apple_HFS Data					103.6 Gi   disk2s3



  bash-3.2# diskutil info disk2s1

	 Device Identifier:		disk2s1

	 Device Node:			  /dev/disk2s1

	 Part Of Whole:			disk2

	 Device / Media Name:	  EFI System Partition



	 Volume Name:			  

	 Mount Point:			  



	 Partition Type:		   EFI

	 Bootable:				 Not bootable

	 Media Type:			   Generic

	 Protocol:				 ATA

	 SMART Status:			 Verified



	 Total Size:			   200.0 Mi (209715200 B) (409600 512-byte blocks)

	 Free Space:			   0.0 B (0 B) (0 512-byte blocks)



	 Read Only:				No

	 Ejectable:				No

	 Whole:					No

	 Internal:				 Yes

 

Booting without a boot.plist file, but with rd(0,1)/mach_kernel -v boot-uuid=<uuid of boot device> gives me the still waiting for root device:

 

If I puth the boot.plist file on the EFI partition I get

 

boot0: GPT

boot0: HFS+

boot0: booting

boot0: done

(Forgot this line ... ;))

 

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Kernel</key>
<string>rd(0,1)/mach_kernel</string>
<key>Kernel Flags</key>
<string>boot-uuid=907054E0-AC2A-3D53-8F5E-F90BB2EB6EA3 -v</string>
<key>Timeout</key>
<string>5</string>
</dict>
</plist>

 

If you mount the EFI partition, should you be able to see it in the desktop? Cause I can't.

Did a repartition and a fresh install before I started doing this.

 

Booting with the 132-cd goes fine.

Link to comment
Share on other sites

I moved nvkush into s/l/e and out of the efi partition and QE and CI are back ;)

 

So I have a 100% Hackintosh that can survive system updates with full hardware support. for as long as that lasts.

 

System specs

 

P4 HTT Prescott 1mb L2

ICH5 SATA (dvd drive on PATA)

1 GIG DDR 400 Dual Channel

320 Total GIGS Over 2 HDD

GeForce 6200A

USB Wifi

32 Inch HD T.V Display

 

Install Methods

~Galaxy's Slimboot (dfe) cd building script to Retail 10.5

Munky's EFI Partition Method w/dfe booter to Software Updated 10.5.5

 

Thanks everyone this is just too Sweet !!!!

 

 

 

 

If you mount the EFI partition, should you be able to see it in the desktop? Cause I can't.

Did a repartition and a fresh install before I started doing this.

 

You can't see the efi partition in the desktop, use terminal to work in it.

When booting I use bt(0,0)... to boot as booting from the hdd seems to use a different switch then the cd. I just put all the uuid info in the boot plist in the root of the /efi partition then when I boot i can just use thebt(0,0)mach_kernel.1 hope this helps

Link to comment
Share on other sites

well i need an advice here... ;)

 

i have a 7600gs fully working with efi strings in my "com.apple.Boot.plist" on efi partition...now with drivers for 9600gt available for mac, i just replace 7600 with my 9600gt and bam! kernel panic screen.

my question is: i need to put my 7600gs again and delete the "com.apple.Boot.plist" and after that replace with my 9600gt and install the drivers???

can i put this new kexts in my efi partition and generate new efi strings?

 

thanks for the help :P

Link to comment
Share on other sites

well i need an advice here... ;)

 

i have a 7600gs fully working with efi strings in my "com.apple.Boot.plist" on efi partition...now with drivers for 9600gt available for mac, i just replace 7600 with my 9600gt and bam! kernel panic screen.

my question is: i need to put my 7600gs again and delete the "com.apple.Boot.plist" and after that replace with my 9600gt and install the drivers???

can i put this new kexts in my efi partition and generate new efi strings?

 

thanks for the help :P

 

I believe you need to have the old card in then boot into the os, remove the efi string from the boot.plist on the efi partition .... reboot with the new card and generate a new efi string.

Link to comment
Share on other sites

extra question:

 

in tutorial, you say:

 

7) rm -rf /Volumes/EFI

 

So this means it will delete all of the enclosed files and sub-folders, am I right?

 

What's the point of doing this?

 

Read more carefully. The context is:

 

6) umount /Volumes/EFI (If this fails, do umount -f /Volumes/EFI).

7) rm -rf /Volumes/EFI

 

as you can see, with the EFI partition unmounted, all that is being removed is the sub-directory EFI.

 

You should also be able to use the command

rmdir /Volumes/EFI

to do the same thing.

Link to comment
Share on other sites

Anyone used this method on a Lenovo S10 yet? I'm thinking about picking one up.

 

I know OS X installs and runs fine after some tweaking on the S10 so with a USB dvd drive the dfe Boot-132 cd + retail install should work, then its the same as setting up the EFI Partition booting like any other system.

Link to comment
Share on other sites

Hi All,

I have finally gained success in following Munky's great Tutorial and can boot into a Virgin OS X with all the extra's on the EFI partition.

 

I observed tho, that I can no longer boot a CD/DVD with this bootloader. WHen I press Escape at the Darwin/x86 screen, I am returned to the choose boot device prompt (80, 81, etc). At this prompt, on the boot-132 CD, you would normally enter "ef" (on my PC at least, noticed "9f" on another) to boot the optical drive. However, when I enter "ef" at this prompt it does not recognize the "Mac OS X Install DVD" volume on the DVD. Is this failure normal? Do we still have to rely on a boot-132 CD to boot a DVD?

 

Thanks

Link to comment
Share on other sites

 Share

×
×
  • Create New...