Need help with post-patch step of Leopard installation!

[Mold Prince]

Hello,

 

So...I installed Leopard on my Toshiba Satellite A105-S4344 (1.6 GHz Core 2 Duo, 2 Gigs of Ram, etc.)

 

I used Brazailmac's guide for the most part, deviating to other posts when necessary. I patched a retail DVD of leopard...that went fine. Installation went fine...now it's the post-patch that's giving me headaches.

 

Post-install, when I try to boot from the hd it gives me the sole blinking " _ "...and nothing else. Next...I tried this section from the guide.

 

Load from the DVD and Open up terminal. This is what you do

 

sudo -s

fdisk -e /dev/rdiskX (replace X and x with the disk/partition you will restore the image to) (press tab after /dev/rdisk to see your options)

fdisk: 1> update

Machine code updated.

fdisk:*1> f 1

Partition 1 marked active.

fdisk:*1> w

Device could not be accessed exclusively.

A reboot will be needed for changes to take effect. OK? [n] y

Writing MBR at offset 0.

fdisk: 1> q

 

Your partition is now active!

 

MAKING IT BOOTABLE

 

In order to follow the next steps you'll need a usb drive with startuptool on it (can be found on this forum or google) Make sure the drive is inserted before booting the dvd

 

- First, Lets Unmount the disk: In terminal type: diskutil umount diskXsx

- Ok, now lets put the file "boot1h" in the beginning of the partition: In terminal, browse to the i386 folder inside the installation dvd

dd if=boot1h of=/dev/rdiskXsx bs=512 count=1

- Now, lets run the startup tool to embed the boot code: (change directory to your pendrive where startup tool is i.e. cd /Volumes/USBdisk/tools)

startupfiletool -v /dev/rdiskXsx boot

- And last, lets give the pope's blessing to the partition:

bless -device /dev/diskXsx -setBoot –verbose

 

Now, mount and bless the mount:

· diskutil mount /diskXsx

· bless -mount /Volumes/YOUR_VOLUME_NAME -setBoot -verbose (Volume name is prob Leopard)

 

reboot, everthing should be fine now

 

Still nothing. Just the blinking cursor...even though it all seemed to work fine. Then I paid more attention to the 9a581PostPatch.sh process. Doesn't seem to be working. Here's what I get...

-bash-3.2# cd /Volumes/PATCHER

-bash-3.2# pwd

/Volumes/PATCHER

-bash-3.2# ls

.DS_Store 9a581-patch.sh leopatch

.Trashes 9a581PostPatch.sh resources

._.Trashes files

-bash-3.2# ./9a581PostPatch.sh

Deleting OSSMGR.plist...

Success !!

Replacing mach_kernel...

Success !!

Deleting necessary kernel extensions...

mv: rename AppleACPIPlatform.kext to AppleACPIPlatform.kext.post/AppleACPIPlatform.kext: Directory not empty

mv: rename AppleIntelIntegratedFramebuffer.kext to AppleIntelIntegratedFramebuffer.kext.post/AppleIntelIntegratedFramebuffer.kext: Directory not empty

mv: rename ApplePS2Controller.kext to ApplePS2Controller.kext.post/ApplePS2Controller.kext: Directory not empty

mv: rename AppleSMBIOS.kext to AppleSMBIOS.kext.post/AppleSMBIOS.kext: Directory not empty

mv: rename dsmos.kext to dsmos.kext.post/dsmos.kext: Directory not empty

mv: rename IOATAFamily.kext to IOATAFamily.kext.post/IOATAFamily.kext: Directory not empty

mv: rename IOAHCIFamily.kext to IOAHCIFamily.kext.post/IOAHCIFamily.kext: Directory not empty

mv: rename AppleAC97Audio.kext to AppleAC97Audio.kext.post/AppleAC97Audio.kext: Directory not empty

mv: rename AppleAHCIPort.kext to AppleAHCIPort.kext.post/AppleAHCIPort.kext: Directory not empty

mv: rename AppleAzaliaAudio.kext to AppleAzaliaAudio.kext.post/AppleAzaliaAudio.kext: Directory not empty

mv: rename AppleVIA.kext to AppleVIA.kext.post/AppleVIA.kext: Directory not empty

mv: rename AppleVIAATA.kext to AppleVIAATA.kext.post/AppleVIAATA.kext: Directory not empty

mv: rename IOHDIXController.kext to IOHDIXController.kext.post/IOHDIXController.kext: Directory not empty

mv: rename AppleHWSensor.kext to AppleHWSensor.kext.post/AppleHWSensor.kext: No such file or directory

Success !!

Adding patched kernel extensions...

Success !!

Remove AppleIntelCPUPowerManagement.kext? [Y/N] Y

All patches applied successfully !!

 

A couple of other times I tried the patch, it gave the "No such file or directory" then it did this time. Now it's a lot of "Directory not empty"

 

This looks like it's a simple problem with pointing the patch in the right direction...but I can't seem to find the problem. I think all of my case-sensitivity matches up.

 

I'm not a total noob, but this problem has been plaguing me for hours. Any suggestions?

 

Thanks in advance.

[3vilution]

First off I already assume you have tiger on another partition. Did you rename the postpatch from /Usr/XXX/Desktop to /Usr/YOUR_USERNAME/Desktop? If not that could be your problem.

Also If you dont have the ToH RC2 dvd, you will need it to run the script.sh to boot into leopard automatically.

[Mold Prince]

No...this is a fresh install. No Tiger...this will be my first time owning a computer with a Mac OS .

 

Heres the "cat" of the script I used, if that helps.

 

-bash-3.2# cat 9a581PostPatch.sh

#!/bin/sh

 

IFS= \n' # important!

PATCH="/Volumes/PATCHER/LEOPATCH/" # path to the patched extensions

LEO="/Volumes/Leopard" # path to Leopard installation

 

echo Deleting OSSMGR.plist...

cd $LEO/System/Library/LaunchDaemons/

rm -rf ossmgr.plist

echo Success !!

 

sleep 1

 

echo Replacing mach_kernel...

cd $LEO

rm -rf mach_kernel

cp -R $PATCH/mach_kernel $LEO/mach_kernel

chmod -R 644 $LEO/mach_kernel

chown -R root:wheel $LEO/mach_kernel

echo Success !!

 

sleep 1

 

echo Deleting necessary kernel extensions...

cd $LEO/System/Library/Extensions/

mv AppleACPIPlatform.kext AppleACPIPlatform.kext.post

mv AppleIntelIntegratedFramebuffer.kext AppleIntelIntegratedFramebuffer.kext.post

mv ApplePS2Controller.kext ApplePS2Controller.kext.post

mv AppleSMBIOS.kext AppleSMBIOS.kext.post

mv dsmos.kext dsmos.kext.post

 

mv IOATAFamily.kext IOATAFamily.kext.post

mv IOAHCIFamily.kext IOAHCIFamily.kext.post

mv AppleAC97Audio.kext AppleAC97Audio.kext.post

mv AppleAHCIPort.kext AppleAHCIPort.kext.post

mv AppleAzaliaAudio.kext AppleAzaliaAudio.kext.post

mv AppleVIA.kext AppleVIA.kext.post

mv AppleVIAATA.kext AppleVIAATA.kext.post

mv IOHDIXController.kext IOHDIXController.kext.post

 

 

# Deleting file to Boot speed-up?...

mv AppleHWSensor.kext AppleHWSensor.kext.post

 

echo Success !!

 

sleep 1

 

echo Adding patched kernel extensions...

cd $PATCH/ext

cp -R * $LEO/System/Library/Extensions

chmod -R 755 $LEO/System/Library/Extensions/* && chown -R root:wheel $LEO/System/Library/Extensions/*

echo Success !!

 

sleep 1

 

read -n 1 -s -p "Remove AppleIntelCPUPowerManagement.kext? [Y/N]" \n'; case $REPLY in y|Y) rm -rf $LEO/System/Library/Extensions/AppleIntelCPUPowerManagement.kext && echo "Deleted" ;; n|N) echo "Leaving be";; esac

 

sleep 1

 

#read -n 1 -s -p "Replace IOATAFamily.kext? [Y/N]" \n'; case $REPLY in y|Y) rm -rf $LEO/System/Library/Extensions/IOATAFamily.kext && cp -R $EXT/IOATAFamily.kext $LEO/System/Library/Extensions && echo "Replaced." ;; n|N) echo "Leaving be";; esac

 

sleep 1

 

echo All patches applied successfully !!

read -n 1 -s -p "Reboot? [Y/N]" \n'; case $REPLY in y|Y) printf "Rebooting in 3..."; sleep 1; printf " 2..."; sleep 1; printf " 1...\n" sleep 1; reboot;; n|N) echo "You must reboot manually";; esac

-bash-3.2#

 

The paths seem to be correct, case-sensitivity and all.

 

So I need the script.sh regardless of how I go about the install? Does that mean I have to download the whole iso...or can I find that file somewhere?

 

Thanks again for the help...

[3vilution]

Well i had to download the whole dvd and boot off of it and run in terminal off the dvd. And I tried forever to get away from the blinking cursor and thats the only way i could get leopard to boot. How did you patch leopard if you wasnt in tiger? And you have to be in tiger to run post patch.

[Mold Prince]

You can run post patch if you boot into the leo dvd, then run terminal. PostPatch is on a usb thumbdrive.

[3vilution]

So you changed in the postpatch the directory to /Volumes/Your_thumbdrive_name/ right?

[Mold Prince]

Correct. The postpatch reads:

IFS= \n' # important!

PATCH="/Volumes/PATCHER/LEOPATCH/" # path to the patched extensions

LEO="/Volumes/Leopard" # path to Leopard installation

 

Those are the correct paths...I think.

[3vilution]

Just making sure.. The Name of your partition is EXACTLY called "Leopard" right? case sensitive. If it is, have you tried booting and holding down f8 while the dvd is still in and see if you can boot into leopard first? If you can then you know you patched it right. If you cant then you didnt. If patched correctly, grab toh dvd and run that script to fix the booting problem.

[Mold Prince]

-bash-3.2# df

Filesystem 512-blocks Used Available Capacity Mounted on

/dev/disk1s3 9176056 9116480 0 100% /

devfs 214 214 0 100% /dev

fdesc 2 2 0 100% /dev

/dev/disk2 934 16 872 2% /Volumes

/dev/disk3 934 124 764 14% /private/var/tmp

/dev/disk4 190 22 160 13% /private/var/run

/dev/disk5 190 4 178 3% /Library/Preferences

/dev/disk0s1 390721904 13274208 377447696 4% /Volumes/Leopard

-bash-3.2# cd /Volumes/PATCHER

-bash-3.2# ls

.DS_Store 9a581PostPatch.sh

.Trashes LEOPATCH

._.Trashes Terminal Saved Output.txt

._Terminal Saved Output.txt cat patch.txt

._cat patch.txt disks.txt

._disks.txt files

9a581-patch.sh resources

-bash-3.2# cd LEOPATCH

-bash-3.2# pwd

/Volumes/PATCHER/LEOPATCH

-bash-3.2# ls

.DS_Store ext mach_kernel

-bash-3.2#

 

There is what everything is currently named. Everything seems to match this

IFS= \n' # important!

PATCH="/Volumes/PATCHER/LEOPATCH/" # path to the patched extensions

LEO="/Volumes/Leopard" # path to Leopard installation

 

I'm a bit confused by your last instructions. I have the Darwin bootloader, and I can press f8 to get into the boot options (I used that to run the leo dvd in "safe mode" i guess, with the parameters -v -x) I don't really know what those parameters do...I just read it in another post.

 

If I run with no parameters, it goes into the installer fine. If I boot from hd...all I have is the blinking cursor. How should I try to boot?

 

and...i think i need to bump this. bump.

[i_am...me]

Its not the post patch that you are doing wrong... its the drive.

You should get kalyways boot disk to make the drive pre bootable, then install leopard then run the post patch. That is your problem.

 

Another option, only is OSX is going to be your sole OS no other ones on there. is to install EFI v7.2 and erase your hard drive and partition it as a GUID partition, and install leopard. that will make it bootable since leopard was meant to be booted off a GUID anyways, and not a MBR.

 

Im going to write a guide soon on how to get EFI v 7.2 on a drive with out another tiger install

[more or less]

When I ran the postpatch I had a folder named "files" which had the postpatch.sh and the resources folder.

 

Check your USB drive and make sure you have kext files in your resources folder.

 

I don't think the postpatch needs the user name mod, just to the patch cd to run the scripts in OSX when patching the disc.

 

I also used the command ./[patcher name].sh to run the script after the cd to 'files' on the flash drive, not 'pwd'?

[Mold Prince]

Awesome. Thanks for the suggestion.

 

I think I'm going to try the Kalyway route first. I see a listing for "Kalyway OSX86 v10.4.10"

 

Will this work, or is there a Leopard-specific (Kalyway v10.5) disk that I need? Any clues as to where I'd find this?

[more or less]

I couldn't make a successful boot disc from patching, so finally I used the 'ToH rc 2' disc.

 

 

google is your friend, use the disc/file names you want, plus the word 'torrent.' Really, you shoudl fix your install tho...

 

 

The blinking cursor is aka the HFS+ boot error, and the scripts above "should" fix it, but you need to run those AFTER you successfully postpatch.

[more or less]

Yeah, I just re-read the thread and

 

"PATCH="/Volumes/PATCHER/LEOPATCH/""

 

and with that you need the postpatch.sh along with the relevent kexts in resources. Maybe you should check for other versions of the patcher...? Maybe mod it to PATCHER/FILES/LEOPATCH ?

 

I know there is a revised BrazilMac one, as the first one may have been borked.

 

My postpatcher specified a file path called "files," and thus I had to move the "files" folder to the root of the thumbdrive after I unzipped the BrazilMac patch. You'd need to name it either 'files' or FILES' accordingly to your postpatcher.sh

 

I used this guide. Lots of links!

 

Good luck!

[3vilution]

For some reason i thought that you could only patch brazil through tiger (post patch), at least thats what the guide said..

[Mold Prince]

More or less...

 

Thanks for the suggestion. Right now I've got three folders in the root of my thumbdrive. "files" "LEOPATCH" and "resources".

 

So...you suggest that I put the "LEOPATCH" folder and the postpatch.sh into the "files" folder, then try running it, correct?

 

Looks like all the .kext files are in the /files/extensions folder right now...so I guess I just have to work on getting everything in the right place...hopefully.

 

Should I move anything else around...or do you think that might work?

[i_am...me]

More or less...

 

Thanks for the suggestion. Right now I've got three folders in the root of my thumbdrive. "files" "LEOPATCH" and "resources".

 

So...you suggest that I put the "LEOPATCH" folder and the postpatch.sh into the "files" folder, then try running it, correct?

 

Looks like all the .kext files are in the /files/extensions folder right now...so I guess I just have to work on getting everything in the right place...hopefully.

 

Should I move anything else around...or do you think that might work?

Post patching wont fix that problem, it will only fix it if your system is rebooting after it says "loading OS X 86"

[Mold Prince]

i am...me

 

forgive my ignorance, but what is EFI v7.2? My Google hunt turned up next to nothing.

[more or less]

More or less...Thanks for the suggestion. Right now I've got three folders in the root of my thumbdrive. "files" "LEOPATCH" and "resources".So...you suggest that I put the "LEOPATCH" folder and the postpatch.sh into the "files" folder, then try running it, correct?Looks like all the .kext files are in the /files/extensions folder right now...so I guess I just have to work on getting everything in the right place...hopefully. Should I move anything else around...or do you think that might work?

I assume when you patched the CD the .iso was in the patcher folder, correct? In this folder, or in the original unzipped patcher you should have a file called, possibly, "files". I did not have a folder called "LEOPATCH" and I believe that line in the .sh is just a placeholder. The patcher is named 9a581postpatch.sh or whatever. In windows, you should see the kexts in the resources folder. If its empty, that's your problem.Some Brazil patchers have the kexts ready to go, some require, as above, for you to be in Tiger to copy those resources/kext from the Tiger library. That's what the patcher does, it uses known Tiger kexts [kernel extensions] with the Tiger mach_kernel, essentially. This is the unix shell that OS X Leopard can run on, as I understand it.I used the one in the guide I linked you to, and you can read it specifies a "123/files" directory. The Brazil patcher I got from that guide had the Tiger kexts ready to go... so I ran it from the patched OS X installer DVD in Terminal.

 

Post patching wont fix that problem, it will only fix it if your system is rebooting after it says "loading OS X 86"

I don't think he's going to be able to boot from a non-patched install. I also have a vested interest in helping him as I have nearly the same laptop.... Again, one has to run the post patch FIRST. Then run the fdisk script to set it to primary, then run the ./dd/startupfiletool/bless routine. Sadly, I've done this routine about 4 times in the last few days... I know it well.

 

And I have never used the Tiger OS in my life, as my iBook cannot really run it.... tho it seems my Dell can run Leopard.

[i_am...me]

i am...me

 

forgive my ignorance, but what is EFI v7.2? My Google hunt turned up next to nothing.

http://netkas.org/

you can get all EFI updates there

 

I don't think he's going to be able to boot from a non-patched install. I also have a vested interest in helping him as I have nearly the same laptop.... Again, one has to run the post patch FIRST. Then run the fdisk script to set it to primary, then run the ./dd/startupfiletool/bless routine. Sadly, I've done this routine about 4 times in the last few days... I know it well.

 

And I have never used the Tiger OS in my life, as my iBook cannot really run it.... tho it seems my Dell can run Leopard.

From the log he posted in the beginning of the thread the post patch was successful. His drive just inst bootable thats why he is getting the blinking _

 

If it was a unpatched install then it would just reboot endlessly

[more or less]

One correction, the "files" had a file called "files" and it has the postpatcher and folders for 'resources' and 'bootfix.' I am 99.9% sure its the files.rar that is linked to several times in the guide above. That is the 'files' I moved to the drive I renamed to '123.'

[i_am...me]

One correction, the "files" had a file called "files" and it has the postpatcher and folders for 'resources' and 'bootfix.' I am 99.9% sure its the files.rar that is linked to several times in the guide above. That is the 'files' I moved to the drive I renamed to '123.'

If it was a problem with the post patching it would go in to an endless reboot. He said that he gets a blinking _ which is caused by the partition not being bootable. im 110% sure of that.

[more or less]

http://netkas.org/

you can get all EFI updates there

 

 

From the log he posted in the beginning of the thread the post patch was successful. His drive just inst bootable thats why he is getting the blinking _

 

If it was a unpatched install then it would just reboot endlessly

 

 

Uh, not so fast my friend... If he has the very first BrazilMac patcher, it does not have the Tiger kexts iirc - and it is known to not have worked. All he has done is successfully replace the unpatched original extensions, with the same unpatched extensions. It would seem he ran fdisk,.dd bless etc, thus why he is stuck with a good boot into an OS that cannot be loaded because the mach_kernel and kexts have still not been patched correctly.

 

If he got Leopard to install, the disc is formatted correctly, that much should be obvious.

[3vilution]

Theres an easy conclusion to this blinking cursor, get the ToH dvd and run that script.sh and I GUARantee It will work! (if its patched correctly )

[i_am...me]

Uh, not so fast my friend... If he has the very first BrazilMac patcher, it does not have the Tiger kexts iirc - and it is known to not have worked. All he has done is successfully replace the unpatched original extensions, with the same unpatched extensions. It would seem he ran fdisk,.dd bless etc, thus why he is stuck with a good boot into an OS that cannot be loaded because the mach_kernel and kexts have still not been patched correctly.

 

If he got Leopard to install, the disc is formatted correctly, that much should be obvious.

 

Hello,

 

So...I installed Leopard on my Toshiba Satellite A105-S4344 (1.6 GHz Core 2 Duo, 2 Gigs of Ram, etc.)

 

I used Brazailmac's guide for the most part, deviating to other posts when necessary. I patched a retail DVD of leopard...that went fine. Installation went fine...now it's the post-patch that's giving me headaches.

 

Post-install, when I try to boot from the hd it gives me the sole blinking " _ "...and nothing else. Next...I tried this section from the guide.

Still nothing. Just the blinking cursor...even though it all seemed to work fine. Then I paid more attention to the 9a581PostPatch.sh process. Doesn't seem to be working. Here's what I get...

A couple of other times I tried the patch, it gave the "No such file or directory" then it did this time. Now it's a lot of "Directory not empty"

 

This looks like it's a simple problem with pointing the patch in the right direction...but I can't seem to find the problem. I think all of my case-sensitivity matches up.

 

I'm not a total noob, but this problem has been plaguing me for hours. Any suggestions?

-bash-3.2# cd /Volumes/PATCHER 
-bash-3.2# pwd
/Volumes/PATCHER
-bash-3.2# ls
.DS_Store 9a581-patch.sh leopatch
.Trashes 9a581PostPatch.sh resources
._.Trashes files
-bash-3.2# ./9a581PostPatch.sh
Deleting OSSMGR.plist...
Success !!
Replacing mach_kernel...
Success !!
Deleting necessary kernel extensions...
mv: rename AppleACPIPlatform.kext to AppleACPIPlatform.kext.post/AppleACPIPlatform.kext: Directory not empty
mv: rename AppleIntelIntegratedFramebuffer.kext to AppleIntelIntegratedFramebuffer.kext.post/AppleIntelIntegratedFramebuffer.kext: Directory not empty
mv: rename ApplePS2Controller.kext to ApplePS2Controller.kext.post/ApplePS2Controller.kext: Directory not empty
mv: rename AppleSMBIOS.kext to AppleSMBIOS.kext.post/AppleSMBIOS.kext: Directory not empty
mv: rename dsmos.kext to dsmos.kext.post/dsmos.kext: Directory not empty
mv: rename IOATAFamily.kext to IOATAFamily.kext.post/IOATAFamily.kext: Directory not empty
mv: rename IOAHCIFamily.kext to IOAHCIFamily.kext.post/IOAHCIFamily.kext: Directory not empty
mv: rename AppleAC97Audio.kext to AppleAC97Audio.kext.post/AppleAC97Audio.kext: Directory not empty
mv: rename AppleAHCIPort.kext to AppleAHCIPort.kext.post/AppleAHCIPort.kext: Directory not empty
mv: rename AppleAzaliaAudio.kext to AppleAzaliaAudio.kext.post/AppleAzaliaAudio.kext: Directory not empty
mv: rename AppleVIA.kext to AppleVIA.kext.post/AppleVIA.kext: Directory not empty
mv: rename AppleVIAATA.kext to AppleVIAATA.kext.post/AppleVIAATA.kext: Directory not empty
mv: rename IOHDIXController.kext to IOHDIXController.kext.post/IOHDIXController.kext: Directory not empty
mv: rename AppleHWSensor.kext to AppleHWSensor.kext.post/AppleHWSensor.kext: No such file or directory
Success !!
Adding patched kernel extensions...
Success !!
Remove AppleIntelCPUPowerManagement.kext? [Y/N] Y
All patches applied successfully !!

 

Thanks in advance.

 

 

Ok so look, his mach_kernel was replaced successfully.

 

like i said many times If it was a kernel problem it would reboot endlessly and he would see "Loading Mac OS X86" for a half a sec then his system would reboot.