[TOTALLY VANILLA] Retail Leopard Install with EFI-strings support [Powered by Chameleon 2.0]

[OSXtotheZ]

First of all, Thanks everyone for all the information. I usually lurk on here, and have found it to be massively helpful.

 

I am having ACPI kernel panic. Not sure why.

 

running 10.5.6, boots fine with boot-132 disc. Trying to use identical kexts.

Any help would be helpful.

 

shuttle g33g5

c2d 3.0 ghz

4gb ram

 

i was good using MacLoader up to 10.5.4 but when I jumped to 10.5.6 combo update and ran the Macloader updater.sh it now gave me a kernel panic on boot something like "unable to find driver for....ACPI". I booted again from my old boot132 DVD and then ran Macloader.sh again so to restore base kext from Macloader's own kext folder. This seemed to get things working again. So I'm just curious as to what happened with running the updater.sh

[justinxxvii]

Hey guys, my boot 132 is not working. I see a quick error referring to a missing .plist file or something before I get to the boot menu where I insert the Leopard disc. My system hangs at a blue screen before the installer even opens. I tried making my own disc with working kext files from a kalyway install, and I also tried the "noob iso" from a thread mentioned up top.

 

Is there anything in particular I need to have in that kext folder? I only put my audio, video and ethernet kexts in the folder. Should I be including something else?

 

I'm using an OSX 10.5.1 retail disc.

[Sumo89]

9. Put inside the “KEXTs” folder all extra kexts from your Boot-132-Disc (also include any extra audio kexts – HDAEnabler/ALCinject + AppleHDA, which are the only kexts that cannot be pre-loaded from Boot-132-Disc).

 

Hi, I'm new to OSX, Sorry for noob question.

Does the "KEXTs" folder referred to above mean the /System/Library/Extensions folder? Or is there an actual KEXT folder in OSX?

 

It may seem obvious to you guys, but I havn't tried this yet, and other posts on this website talk about putting kexts in the /System/Library/Extensions folder.

 

Thanks for tutorial and all the hard work you guys have done to make OSX work with PC

[JT@T]

sudo nano /etc/fstab

UUID="MacLoader's UUID" none hfs rw,noauto

[CTRL]+o (to save)

[ENTER]

[CTRL]+x (to exit)

 

 

======

I follow this instruction, but it doesn't work for me!

I can see one file(fstab) in /etc/

for example my MacLoader's UUID is 1234

the text in this file is

 

UUID="1234" none hfs rw,noauto

 

who can help me?

 

thanks!

[hoyanf]

sudo nano /etc/fstab

UUID="MacLoader's UUID" none hfs rw,noauto

[CTRL]+o (to save)

[ENTER]

[CTRL]+x (to exit)

======

I follow this instruction, but it doesn't work for me!

I can see one file(fstab) in /etc/

for example my MacLoader's UUID is 1234

the text in this file is

 

UUID="1234" none hfs rw,noauto

 

who can help me?

 

thanks!

 

First of all you're not suppose to edit directly 'sudo nano /etc/fstab'. On Leopard it is supposed to be use with 'vifs', if you want to use 'nano' for editing purposes do this instead =>

 

export EDITOR=/usr/bin/nano
sudo vifs

 

For fstab settings should be like this =>

UUID=1234-5678-101112 /Volumes/"Label" hfs rw,noauto 0 0

[MACinized]

sudo nano /etc/fstab

UUID="MacLoader's UUID" none hfs rw,noauto

[CTRL]+o (to save)

[ENTER]

[CTRL]+x (to exit)

 

 

======

I follow this instruction, but it doesn't work for me!

I can see one file(fstab) in /etc/

for example my MacLoader's UUID is 1234

the text in this file is

 

UUID="1234" none hfs rw,noauto

 

who can help me?

 

thanks!

 

the value for the UUID should not contain quotation marks.

[spanakorizo]

ill try this cause im about to install a new vanilla 10.5.6 for testing purpose

[rh535]

Hey guys, my boot 132 is not working. I see a quick error referring to a missing .plist file or something before I get to the boot menu where I insert the Leopard disc. My system hangs at a blue screen before the installer even opens. I tried making my own disc with working kext files from a kalyway install, and I also tried the "noob iso" from a thread mentioned up top.

 

Is there anything in particular I need to have in that kext folder? I only put my audio, video and ethernet kexts in the folder. Should I be including something else?

 

I'm using an OSX 10.5.1 retail disc.

 

I have the same problem with the .plist error. But im able to continue booting up. Any ideas on what this is?

[MACinized]

I have the same problem with the .plist error. But im able to continue booting up. Any ideas on what this is?

 

you may try EXcluding the video kext.

[zhell]

Thanks for your awesome guide, Macinized.

 

I use a similar script to update the .mkext cache; it mainly differs from update.sh in MacLoader as follows.

[...]

 

A completely revised script and a GUI application are now available over at the Genius Bar.

[cheelam1220]

does this mean i can install Leopard 10.5.6 from an original disc to a PC by doing all this steps?i don't know what is this topic talk about......i was new to mac and sorry for my lack of English

[zhell]

does this mean i can install Leopard 10.5.6 from an original disc to a PC by doing all this steps?i don't know what is this topic talk about......i was new to mac and sorry for my lack of English

It means exactly this.

 

By booting from the Boot-132 CD, your PC is put into a state where it looks almost like a Mac. At this point, you swap the Mac OS X DVD for the Boot-132 CD and it boots up as if it were on a Mac.

 

Then you install Mac OS X to one partition of your disk, , yielding an installation that is exactly the same as on a real Mac. What was on the Boot-132 CD you install onto another partition, and make that partition bootable.

 

From then on, your PC will first boot the bootable partition and the bootloader will then continue to boot the Mac OS X partition.

[cheelam1220]

Ok,i got it....can use the kalyway 10.5.2 to instead of the original wan?and another question is where to put all the kext,and what is mkext

[MACinized]

updated post#1.

 

MacLoader is now powered by Chameleon 2.0 r431!

 

enjoy the gui of the new chameleon bootloader (check it out at their site -chameleon.osx86.hu-).

[Raph4]

Woow, thanks. You rock

[rh535]

I never fully finished the install. ( I still boot from a CD) If i install Chameleon 2.0 will that allow me to boot of the hard drive?

[Sumo89]

Hi, I'm new to OSX, Sorry for noob question.

Does the "KEXTs" folder referred to above mean the /System/Library/Extensions folder? Or is it another folder?

 

It may seem obvious to you guys, but I havn't tried this yet, and other tutorials on this website talk about putting kexts in the /System/Library/Extensions folder. Yet another tutorial talkes about putting kexts in the users/username/ directory.

 

Would Kext Helper b7 work with retail install and take care of it automatically?

 

Thanks for tutorial and all the hard work you guys have done to make OSX work with PC

 

Can someone answer this questions please. It's such a simple question and should be an easy answer to anyone who's tried this before. Just ignoring such a simple question makes me less inclined to EVER donate to or monetarily support this site. And YES I do support sites that are helpful.

[Eddie Turfboer]

Can someone answer this questions please. It's such a simple question and should be an easy answer to anyone who's tried this before. Just ignoring such a simple question makes me less inclined to EVER donate to or monetarily support this site. And YES I do support sites that are helpful.

It refers to a folder you create with your personalized kext in order to be able to boot your hardware. It does not relate to the /System/Library/Extensions folder. The reason is that we like to keep that folder as is, whilst modifying some of the kext would mean that the system breaks when we try to update. Therefore we 'preload' kext from that KEXT folder at boot, so we have the kext and be able to update the system as well.

 

Hope this clarifies it for you, if not feel free to ask again.

[MACinized]

It refers to a folder you create with your personalized kext in order to be able to boot your hardware. It does not relate to the /System/Library/Extensions folder. The reason is that we like to keep that folder as is, whilst modifying some of the kext would mean that the system breaks when we try to update. Therefore we 'preload' kext from that KEXT folder at boot, so we have the kext and be able to update the system as well.

 

Hope this clarifies it for you, if not feel free to ask again.

the MacLoader5 provided has a folder in it named "KEXTs". that's where you have to put any extra kext you need for your computer setup.

 

good luck.

 

I never fully finished the install. ( I still boot from a CD) If i install Chameleon 2.0 will that allow me to boot of the hard drive?

you may want to use a usb-flashdisk (a 256mb capacity would be sufficient, if you still have one ) as your MacLoader (i.e. use it as the bootloader).

 

good luck.

[Sumo89]

It refers to a folder you create with your personalized kext in order to be able to boot your hardware. It does not relate to the /System/Library/Extensions folder. The reason is that we like to keep that folder as is, whilst modifying some of the kext would mean that the system breaks when we try to update. Therefore we 'preload' kext from that KEXT folder at boot, so we have the kext and be able to update the system as well.

 

Hope this clarifies it for you, if not feel free to ask again.

 

Ok, thanks a lot for reply, but just another question.

I might try EFI string for my gfx card 8800GTS instead of kext. So does the EFI string still go into the com.apple.Boot.plist file? Or is there a special file (like KEXTs folder) to put EFI strings into? I do want to keep install as vanilla as possible.

[MACinized]

Ok, thanks a lot for reply, but just another question.

I might try EFI string for my gfx card 8800GTS instead of kext. So does the EFI string still go into the com.apple.Boot.plist file? Or is there a special file (like KEXTs folder) to put EFI strings into? I do want to keep install as vanilla as possible.

the MacLoader has it's own com.apple.Boot.plist so you could put the efi-strings for your vga there.

 

good luck.

[IMHERETOSTAY]

I followed your tutorial on how to use the macloader with my system ( Asus P5B-Plus with q6600)...

But I have a problem... I can boot with a P5B custom Boot-132 CD and install leopard just fine... But when I copy the kext to the macloader folder and execute the command, I can't reboot after, I get a kernel panic and my AppleUSHUHCi seems to have a problem... it won't load or whatever and right after, in verbose mode, it says that it is still waiting for root device... My system is set to Sata as AHCI and there is no problem booting iPC with it... Do you know what can pose this problem???

[MACinized]

updated post#1 for the updated MacLoader.

 

w/ the new MacLoader, com.apple.Boot.plist is automatically generated w/ the required string(s).

 

good luck & enjoy.

[mikedddd]

Video/sound issues with GA-EP45 UD3/8800GTS

I can't seem to get my audio/video working correctly, otherwise the install is working fine. Do I install audio/video kexts into the macloader partition or into the full OS install? Likewise, if I try messing with EFI strings, do I do that in the macloader partition or the full install?

Seems like a great system otherwise, really like the Chameleon v2 you've added.

Mike

[MACinized]

Video/sound issues with GA-EP45 UD3/8800GTS

I can't seem to get my audio/video working correctly, otherwise the install is working fine. Do I install audio/video kexts into the macloader partition or into the full OS install? Likewise, if I try messing with EFI strings, do I do that in the macloader partition or the full install?

Seems like a great system otherwise, really like the Chameleon v2 you've added.

Mike

the intention of this method is to keep the retail install untouched. you should try first putting any extra kexts (including the ones for your audio & video) to the "KEXTs" folder. if you're already done setting-up your "MacLoader", then after putting all necessary kexts for your system, just double-click the "updater.command".

 

the same goes w/ efi-srings, you should put them in the Boot.plist of the MacLoader. you can find it inside the "Extra" folder of the MacLoader (/Volumes/MacLoader/Extra).

 

good luck.