Leopard Installer

[Dense]

Yeah, it is slower. I've been trying several things to fix the Extensions.mkext problem. I've tried replacing it with one I extracted out, but it didn't help. Either the system locked up or it ran the mkext builder anyway. It really seems only about 30 seconds to build the extensions.mkext. The remainder of the time is slowly moving trough loading the network .... etc.

 

I've been spending the last day working on Extensions.mkext. There is an unfortunate problem and that is if you try to build a Extensions.mkext for 10.5 using 10.4, you will not succeed. For those of us trying to make distributions of Leopard this is a serious problem because we cant create a valid Extensions.mkext and therefore the installation is much slower. The solution I have been working on is to compile the latest kexttools from Apple's site and get it working on 10.4 (so it can process the 10.5 extensions directory).

 

I have tried a few other tricks (so you don't double up efforts). Using the 10.5 kextcache tool under 10.4 (memory allocation error - tried a variety of DYLD_LIBRARY_PATH and DYLD_FRAMEWORK_PATH no success). Also tried forcing it through rosetta (same memory allocation error).

[swag01]

Well I have a E6750 so it's SSE3. I have a hunch it's my JMicron controller. Can I use Tiger extensions with LEO or should I get the JMicron extension off the DVD and make sure the device ID for my controller is in the file

 

Thanks,

SMF

 

 

What chipset is your motherboard? Different chipsets have different requirements.

 

I'm hoping in the end, someone creates a package for each chipset, then all that needs to happen is to select it in the custom section. Similar to what Jaz did for 10.4.7 - ??

 

Then, there is one Leopard installer which everyone downloads and picks their specific chipset.

 

The problem is to get to this point is for people to try out what the required kexts are needed for a specific chipset is (trial and error).

 

I have it figured out for the 975x/ICH7DX and the package I created should work.

 

I know other people are work P35 and other chipsets too.

[SMF]

swag01,

 

 

I have a Gigabyte P35-DQ6. It has the ICH-9R and the JMicron JMB363 controllers. I'm working away at trying to get it to boot. As I'm learning as I go it might be a long process!

 

Thanks,

SMF

[swag01]

swag01,

I have a Gigabyte P35-DQ6. It has the ICH-9R and the JMicron JMB363 controllers. I'm working away at trying to get it to boot. As I'm learning as I go it might be a long process!

 

Thanks,

SMF

 

 

It seems that you and Herbalb should talk. He is trying to do the same thing with similar hardware.

[herbalb]

Talking right now ;-)

I sent SMF the rapidshare link with the files you made. Unfortunately I wasn't able to test the mpkg and EFI_6 from you yet as I am still missing the power supply for the new PC but maybe SMF can get it to work.

Btw would it be better for us (i.e. better booting) if we used the new pc_efi_v7 with it?

 

It seems that you and Herbalb should talk. He is trying to do the same thing with similar hardware.

[swag01]

Talking right now ;-)

I sent SMF the rapidshare link with the files you made. Unfortunately I wasn't able to test the mpkg and EFI_6 from you yet as I am still missing the power supply for the new PC but maybe SMF can get it to work.

Btw would it be better for us (i.e. better booting) if we used the new pc_efi_v7 with it?

 

 

Great to hear.... Once you all figure it out for the chipset, then I can add it to the package or you can create your own.

 

Good question about v7. I haven't downloaded that one yet, but I don't know if it includes the patches specific for your graphics card. You might have to investigate.

 

Also, so you don't need a new package delivery, I would suggest you rename it to boot_gf8800. The script I created for you is expecting that specific file name.

[BladeRunner]

Great to hear.... Once you all figure it out for the chipset, then I can add it to the package or you can create your own.

 

Good question about v7. I haven't downloaded that one yet, but I don't know if it includes the patches specific for your graphics card. You might have to investigate.

 

Also, so you don't need a new package delivery, I would suggest you rename it to boot_gf8800. The script I created for you is expecting that specific file name.

 

The v7 package appears to be for a very narrow user group - just those using a non mbr partition scheam and grub multi-boot.

 

On a somewhat different topic, I have been working with a sparse image made from the retail dvd and I am having a major problem getting it down to a single layer size. I have a double layer dvd burner but for some reason it won't work. Every time I burn a dl dvd it fails and then appears to the system as a blank.

 

When I try to build the patched dvd I remove the Xcode tools, all but two of the printer drivers, all language packs, asian language support, boot camp, additional fonts, and ATI*.kext since I have nvidia. That gets me down to 4.2Gb as reported by df -h.

 

Still, asr says there is not enough room to do the copy - and I have set the size to 4482M.

 

I could sure use some pointers on what else I can safely remove.

[herbalb]

As soon as one of us gets everything to work we can let you know what files we had used in order to get it to work so you can release this set for other people using the same/a similar board as we do.I already made several DVDs with the files you gave me which combined with the Patch_Folder-files as you instructed me so fingers crossed that one of them will work ;-) About the new Efi. Could I use boot_gf8800GTS320 from the Efi_v7.tar (in the folder called PC_Efi_6_boot_loaders), rename it to boot_gf8800 and replace it with the one that was in the folder of the files you sent me in order to get specific support for my grafic card? No need to replace/add anything else to the Patcher-Folder? What about that Efi_Kernel_v6.pkg? There is no Efi_Kernel_v7 - can I just keep the rest of the files you sent me as they are as it seems according to what BladeRunner explained (thanks) that I do not need the new features of EFI_v7?

Great to hear.... Once you all figure it out for the chipset, then I can add it to the package or you can create your own. Good question about v7. I haven't downloaded that one yet, but I don't know if it includes the patches specific for your graphics card. You might have to investigate.Also, so you don't need a new package delivery, I would suggest you rename it to boot_gf8800. The script I created for you is expecting that specific file name.

For my actual test-DVDs I removed even less than you and it still fits. I removed all printer drivers, XCode and all the languages except Japanese and Chinese and its small enough, no need to delete asian language support or fonts. Just use Swag01's script from here forum.insanelymac.com/index.php?s=&showtopic=72180&view=findpost&p=518084- it worked for me.

The v7 package appears to be for a very narrow user group - just those using a non mbr partition scheam and grub multi-boot.On a somewhat different topic, I have been working with a sparse image made from the retail dvd and I am having a major problem getting it down to a single layer size. I have a double layer dvd burner but for some reason it won't work. Every time I burn a dl dvd it fails and then appears to the system as a blank.When I try to build the patched dvd I remove the Xcode tools, all but two of the printer drivers, all language packs, asian language support, boot camp, additional fonts, and ATI*.kext since I have nvidia. That gets me down to 4.2Gb as reported by df -h.Still, asr says there is not enough room to do the copy - and I have set the size to 4482M.I could sure use some pointers on what else I can safely remove.

[swag01]

The v7 package appears to be for a very narrow user group - just those using a non mbr partition scheam and grub multi-boot.On a somewhat different topic, I have been working with a sparse image made from the retail dvd and I am having a major problem getting it down to a single layer size. I have a double layer dvd burner but for some reason it won't work. Every time I burn a dl dvd it fails and then appears to the system as a blank.When I try to build the patched dvd I remove the Xcode tools, all but two of the printer drivers, all language packs, asian language support, boot camp, additional fonts, and ATI*.kext since I have nvidia. That gets me down to 4.2Gb as reported by df -h.Still, asr says there is not enough room to do the copy - and I have set the size to 4482M.I could sure use some pointers on what else I can safely remove.

What size is your OSInstall folder within the Patch_folder? If that is too large, that will cause problems.Also, I posted a non asr version of the script. It uses ditto instead and people seem to have better success with that.One other thing... if your incoming dvd image is double layer, asr still thinks it is 8 gb dvd even if you remove files. You'll need to follow the steps to get it down to a 4 GB dvd. The reason is asr does a block by block copy and if the two sizes don't match, then it fails.

As soon as one of us gets everything to work we can let you know what files we had used in order to get it to work so you can release this set for other people using the same/a similar board as we do.I already made several DVDs with the files you gave me which combined with the Patch_Folder-files as you instructed me so fingers crossed that one of them will work ;-) About the new Efi. Could I use boot_gf8800GTS320 from the Efi_v7.tar (in the folder called PC_Efi_6_boot_loaders), rename it to boot_gf8800 and replace it with the one that was in the folder of the files you sent me in order to get specific support for my grafic card? No need to replace/add anything else to the Patcher-Folder? What about that Efi_Kernel_v6.pkg? There is no Efi_Kernel_v7 - can I just keep the rest of the files you sent me as they are as it seems according to what BladeRunner explained (thanks) that I do not need the new features of EFI_v7?For my actual test-DVDs I removed even less than you and it still fits. I removed all printer drivers, XCode and all the languages except Japanese and Chinese and its small enough, no need to delete asian language support or fonts. Just use Swag01's script from here forum.insanelymac.com/index.php?s=&showtopic=72180&view=findpost&p=518084- it worked for me.

Sounds good. Yes, just rename the boot_... Just make sure it uses the original name boot_gf8800 otherwise the script will fail.The package doesn't actually contain the boot code, it just runs a script at the end which applies the boot record to the new installed partition.In order for it to install on the new partition, it has to unmount it. If you unmount, the boot_gf8800 isn't available and the script will fail. So, that's why you have to put the boot_* in the i386 folder. The script goes to the dvd and applies it from there. Long description.... I'll look about cleaning that up at some point. Maybe there is some temp folder it could go into. Also, create a package for specific graphics cards and the user selects at the custom button.

[BladeRunner]

As soon as one of us gets everything to work we can let you know what files we had used in order to get it to work so you can release this set for other people using the same/a similar board as we do.I already made several DVDs with the files you gave me which combined with the Patch_Folder-files as you instructed me so fingers crossed that one of them will work ;-) About the new Efi. Could I use boot_gf8800GTS320 from the Efi_v7.tar (in the folder called PC_Efi_6_boot_loaders), rename it to boot_gf8800 and replace it with the one that was in the folder of the files you sent me in order to get specific support for my grafic card? No need to replace/add anything else to the Patcher-Folder? What about that Efi_Kernel_v6.pkg? There is no Efi_Kernel_v7 - can I just keep the rest of the files you sent me as they are as it seems according to what BladeRunner explained (thanks) that I do not need the new features of EFI_v7?For my actual test-DVDs I removed even less than you and it still fits. I removed all printer drivers, XCode and all the languages except Japanese and Chinese and its small enough, no need to delete asian language support or fonts. Just use Swag01's script from here forum.insanelymac.com/index.php?s=&showtopic=72180&view=findpost&p=518084- it worked for me.

 

Well, I am using a modified version of that script to build the system. However, when I first started, it built a patched image of about 2.1Gb and unless I am reading the script wrong, I don't understand how the system could work.

 

What I see there is a complete removal of all install packages, and the $APDIR/OSInstall directoy only contains two kernel packages and a fix for local time.

 

echo "======> replacing OSInstall directory..."
rm -rf "$VOL/System/Installation/Packages"
cp -Rf "$APDIR/OSInstall"/ "$VOL/System/Installation/Packages"/
chown -Rf root:wheel "$VOL/System/Installation/Packages"

 

What am I missing? I don't see another source for install packages.

[SMF]

Bladerunner,

 

See post #68. You have to take all the packages you want of the original Leo DVD and place them in the OSInstall folder inside the patch_folder or they won't be included on the DVD and you'll see the much less than 4.2GByte size.

 

SMF

[swag01]

Well, I am using a modified version of that script to build the system. However, when I first started, it built a patched image of about 2.1Gb and unless I am reading the script wrong, I don't understand how the system could work.

 

What I see there is a complete removal of all install packages, and the $APDIR/OSInstall directoy only contains two kernel packages and a fix for local time.

 

echo "======> replacing OSInstall directory..."
rm -rf "$VOL/System/Installation/Packages"
cp -Rf "$APDIR/OSInstall"/ "$VOL/System/Installation/Packages"/
chown -Rf root:wheel "$VOL/System/Installation/Packages"

 

What am I missing? I don't see another source for install packages.

 

 

I don't know if you saw my post, but are you certain that the source dvd (Leopard4Gig.sparseimage) is a 4 GB image and not an 8 GB one where you just removed the files?

 

The dvd is still 8 GB even when you remove the files. You have to go through the steps to take the 8 GB and create a 4 GB dvd.

[BladeRunner]

I don't know if you saw my post, but are you certain that the source dvd (Leopard4Gig.sparseimage) is a 4 GB image and not an 8 GB one where you just removed the files?

 

The dvd is still 8 GB even when you remove the files. You have to go through the steps to take the 8 GB and create a 4 GB dvd.

 

OK! Now I am more confused than ever! I reread your first post and then went to the link about creating a sparse image. This time, I read it all the way to the end. If I follow that sparse image procedure to create a 4.7Gb sparse image it includes removing the Xcode Tools, printer drivers etc... during that process. Then why is there code in your script to do the same steps?

 

When I read your script and saw code to remove those packages there I assumed ( I know ) that just making an 8GB sparse image was enough.

 

Did you do all the package removal in the sparse image step or am I still missing something?

[swag01]

OK! Now I am more confused than ever! I reread your first post and then went to the link about creating a sparse image. This time, I read it all the way to the end. If I follow that sparse image procedure to create a 4.7Gb sparse image it includes removing the Xcode Tools, printer drivers etc... during that process. Then why is there code in your script to do the same steps?

 

When I read your script and saw code to remove those packages there I assumed ( I know ) that just making an 8GB sparse image was enough.

 

Did you do all the package removal in the sparse image step or am I still missing something?

 

 

Yeah, some of the script does what the other "how to" does. The first tutorial was written by someone who was trying to get the 8Gb version to fit on a 4 GB version. They already removed a bunch of items to clean it up.

 

I chose to make the script easier for people to use. Instead of modifying the script when packages are added/removed, they just need to put what is needed in the OSInstall folder and it all gets copied over. Otherwise, the script would need to be modified as packages change. More of a "drag and drop" solution.

 

If it makes things easier for you, you can change the script so it doesn't copy the OSInstall directory. You can just copy the specific files over.

 

Your choice...

 

 

The important thing is that the sparseimage is a 4 GB image. Not the amount of storage the files are taking. You can't copy an 8GB disk to a 4 GB disk by just removing files unless you do some file copy command. ditto does this, but has limitation in that some file attributes don't get copied over.

[BladeRunner]

Yeah, some of the script does what the other "how to" does. The first tutorial was written by someone who was trying to get the 8Gb version to fit on a 4 GB version. They already removed a bunch of items to clean it up.

 

I chose to make the script easier for people to use. Instead of modifying the script when packages are added/removed, they just need to put what is needed in the OSInstall folder and it all gets copied over. Otherwise, the script would need to be modified as packages change. More of a "drag and drop" solution.

 

If it makes things easier for you, you can change the script so it doesn't copy the OSInstall directory. You can just copy the specific files over.

 

Your choice...

The important thing is that the sparseimage is a 4 GB image. Not the amount of storage the files are taking. You can't copy an 8GB disk to a 4 GB disk by just removing files unless you do some file copy command. ditto does this, but has limitation in that some file attributes don't get copied over.

 

OK! I got it now. The dawn comes later for some of us than others. I have a new sparse image process going on in the background now. I appreciate the explanation - and all the hard prep work you have shared.

[herbalb]

In order to copy the pkg-files from my newly created 4GB-sparse image I did it as described on the first page:

4. Now you need to copy your OSInstall files from your Leopard dvd from here:
/System/Installation/Packages to /Users/XXXX/Desktop/Patch_Folder
Example: cp -R "/Volumes/Mac OS X Install DVD/System/Installation/Packages"/* ~/Desktop/Patch_Folder/OSInstall
(WARNING: Keep in mind that you will have very limited space to store extra things on the 4Gig install so you should remove unused packages)

[Onixs]

swag01:

 

greeting...!

 

made a dvd using your ditto2.sh script. the original script that comes from the package didnt work for me.

 

after i made thw dvd and installed it, im stuck at

 

BSD: MAJOR 14 MINOR 7

 

help pls.

 

 

i only added KEXT that work when i tried the brazilmac.

[swag01]

swag01:

 

greeting...!

 

made a dvd using your ditto2.sh script. the original script that comes from the package didnt work for me.

 

after i made thw dvd and installed it, im stuck at

 

BSD: MAJOR 14 MINOR 7

 

help pls.

i only added KEXT that work when i tried the brazilmac.

 

 

What's your hardware? Also, is it a SSE3 machine? If not, you'll need to replace the kernel with the SSE2 version.

[Onixs]

swag01:

 

Hi...

 

i have a SSE2 machine. i replaced the kernel with the ToH DVD which is capable of SSE2.

 

tried with success the kernel and kext with brazilmac . but having an issue regardin boot thats why i want to try yours.

[swag01]

swag01:

 

Hi...

 

i have a SSE2 machine. i replaced the kernel with the ToH DVD which is capable of SSE2.

 

tried with success the kernel and kext with brazilmac . but having an issue regardin boot thats why i want to try yours.

 

 

Yes, so you need to put the SSE2 kernel in the Patch_Folder and the script will replace the one on the dvd.

 

Also, the package I included as an example is only the SSE3 kernel too. You'll have to create a package specific for your hardware.

 

You are going into uncharted territory as I haven't tested this with SSE2 machines.

[Onixs]

Yes, so you need to put the SSE2 kernel in the Patch_Folder and the script will replace the one on the dvd.

 

Also, the package I included as an example is only the SSE3 kernel too. You'll have to create a package specific for your hardware.

 

You are going into uncharted territory as I haven't tested this with SSE2 machines.

 

 

 

yeah. i guess this will not work on a SSE2 machine.

i think it has something to do with the "i386booter.iso"

 

i'll just find a way to work this things out.

 

thanks!

[herbalb]

OK I finally got my new mainboard, CPU and GPU and I tested the versions I made with the files you sent me but none of them worked When trying to boot the DVD I am always getting

panic (cpu 0 caller 0x004304FF):"Unable to find driver for this platform: "/"ACPI/"./n@\Volumes/disk1s2/leo_xnu-1228/iokit/Kernel/IOPlattformExpert.cpp:1376
Debugger calles panic
Backtrace, format - Frame: Return Address (4 potential args on stack)
0x5504bdd8: 0x12b0e1 
...

 

The strange thing is that the version I used with BrazilMac's patch does at least boot and brings me into the installation screen, the same with the ToH-release (I did not test them any further as I wanted to get your version to boot, because it seems much more comfortable to me and uses the latest Efi-bootloader for my Geforce).

So what do you think is wrong? I did everything exactly as you described and I replaced the files just as you told so maybe there is something wrong with the files?

[swag01]

OK I finally got my new mainboard, CPU and GPU and I tested the versions I made with the files you sent me but none of them worked When trying to boot the DVD I am always getting

panic (cpu 0 caller 0x004304FF):"Unable to find driver for this platform: "/"ACPI/"./n@\Volumes/disk1s2/leo_xnu-1228/iokit/Kernel/IOPlattformExpert.cpp:1376
Debugger calles panic
Backtrace, format - Frame: Return Address (4 potential args on stack)
0x5504bdd8: 0x12b0e1 
...

 

The strange thing is that the version I used with BrazilMac's patch does at least boot and brings me into the installation screen, the same with the ToH-release (I did not test them any further as I wanted to get your version to boot, because it seems much more comfortable to me and uses the latest Efi-bootloader for my Geforce).

So what do you think is wrong? I did everything exactly as you described and I replaced the files just as you told so maybe there is something wrong with the files?

 

My guess is one of the kext's isn't compatible in the Extensions folder. Just to run a test, you might use the brazilmac extensions and see if that gets you booted.

[herbalb]

I already had created one with BrazilMac's Kext-files plus the necessary files for onboard sound and LAN and it does not get much further - it just hangs during the boot process. On the other side I added the same kexts for sound and LAN to the BrazilMac-patcher and it boots. So I guess it is not just the kexts...but what could it be?!

[swag01]

I already had created one with BrazilMac's Kext-files plus the necessary files for onboard sound and LAN and it does not get much further - it just hangs during the boot process. On the other side I added the same kexts for sound and LAN to the BrazilMac-patcher and it boots. So I guess it is not just the kexts...but what could it be?!

 

 

The only other thing which is different is the kernel. So, maybe replace the kernel in the Patch_Folder with BrazilMac's and give that a try.

 

Thanks