3675 replies to this topic

[AndreaGalileo]

Great guide. Thank you very much!

[blackosx]

Alex DeWolf, on Aug 25 2009, 09:26 PM, said:

If you have a modded BIOS is DSDT still needed?

If your modded BIOS includes the CMOS reset fix then you don't need a DSDT.

AndreaGalileo, on Aug 25 2009, 10:02 PM, said:

Great guide. Thank you very much!

Your Welcome

[YoYelloW]

right so now i have a working dsdt.aml, had to download windows7 and install that in virtualbox to run the app its not giving me cmos reset anymore.

still got the KP at random time after boot (takes longer now) and my screen is at 1280=something instead of my native resolution, any idea how thats fixable?

[blackosx]

Great, well done with the DSDT.aml
Have you still got your <key>Graphics Mode</key> in com.apple.Boot.plist ?

and have you tried building an extensions.mkext with the instructions I posted to aread22?

[YoYelloW]

blackosx, on Aug 25 2009, 10:28 PM, said:

Great, well done with the DSDT.aml
Have you still got your <key>Graphics Mode</key> in com.apple.Boot.plist ?

and have you tried building an extensions.mkext with the instructions I posted to aread22?

yes i did set boot.plist to 1920x1080 and by building a extensions.mkext u mean booting in -s and do the chown kextcache stuffs? also ran that kextapp right after booting into finder for first time.

i tried to EFI the gfx into the boot.plist but didnt work so far.

[roadcrash1]

Hi it's been a while since i posted on the forums but i've been trying to install snow leopard since yesterday night to no avail i have finally gotten it successfully installed but as soon as chameleon boots up my snowleopard partition a kernal panic comes up the first few lines read
panic cpu 0 caller 0xffffff80002cbf74 kernal trap at 0xffffff80004f65c3 if anyone knows what the problem may be please help it would be greatly appreciated

[blackosx]

I have been testing with using an Extensions.mkext in the /Extra folder and it has helped me get Bonjour working
So maybe it will help others not have KP's?

But rather than build and Extensions.mkext of just the extensions in /Extra, I have built and Extenisons.mkext of the extensions in both /Extra and /S/L/E which gives me a 30.2MB file but it works.. (This was in Laszlo's original guide, I don't know how I missed it   )

To do this, type the following in Terminal on one line...
kextcache -v 1 -t -m /Volumes/Cham/Extra/Extensions.mkext /Volumes/Cham/Extra/Extensions /Volumes/SnowLeopard/System/Library/Extensions


EDIT: Before I did this I selected the Cham volume in Finder, Chose Get Info, then unticked 'Ignore ownership on this volume'. Then in Terminal typed....
sudo chown -R 0:0 /Volumes/Cham
sudo chmod -R 755 /Volumes/Cham/Extra/Extensions

by doing this I now have to honour permissions in the Cham volume, but that's no hardship  

YoYelloW, on Aug 25 2009, 10:41 PM, said:

yes i did set boot.plist to 1920x1080 and by building a extensions.mkext u mean booting in -s and do the chown kextcache stuffs? also ran that kextapp right after booting into finder for first time.

i tried to EFI the gfx into the boot.plist but didnt work so far.

If you use the device (EFI) string in com.apple.Boot.plist, then you'll have to build a DSDT.aml without patched video.

roadcrash1, on Aug 25 2009, 11:07 PM, said:

Hi it's been a while since i posted on the forums but i've been trying to install snow leopard since yesterday night to no avail i have finally gotten it successfully installed but as soon as chameleon boots up my snowleopard partition a kernal panic comes up the first few lines read
panic cpu 0 caller 0xffffff80002cbf74 kernal trap at 0xffffff80004f65c3 if anyone knows what the problem may be please help it would be greatly appreciated

Have you followed this guide and installed all the files?
If so, as you have a different system you might want to try booting with only fakesmc,.kext, NullCPUPowerManagement.kext and PlatformUUID.kext.

[YoYelloW]

hmm im wonderign btw, what does the platformuuid kext do exactly, i didnt see a difference in using it, or not using it.

[brushedtooth]

32bit seems to be pretty stable, been trying out 64bit and seem to get a random system dead lock. Anyone else experiencing this?

[blackosx]

YoYelloW, on Aug 25 2009, 11:36 PM, said:

hmm im wonderign btw, what does the platformuuid kext do exactly, i didnt see a difference in using it, or not using it.

I think it just allows the system to pass a few tests and not flag errors in the system.log but I could be wrong. And my backup Snow Leopard install works fine, and that's on a different volume with a different UUID than what's in PlatformUUID and SMBIOS.

So roadcrash1, ignore the bit about including PlatformUUID.kext when just trying minimal kexts.

Thanks for questioning that YoYelloW

brushedtooth, on Aug 25 2009, 11:38 PM, said:

32bit seems to be pretty stable, been trying out 64bit and seem to get a random system dead lock. Anyone else experiencing this?

I had this only once in 64-bit (and it wasn't really random) and that was when I was trying to test automatic sleep. I left it with the screen saver running and for it to enter sleep in 10 minutes after that, but when I came back to the machine it was frozen. I haven't tried that since in 64-bit.

[roadcrash1]

no luck even after your suggestion blackosx i'm beginning to lose hope lol
i might be in a bit over my hea, as i might better off waiting for a distro to come out

[YoYelloW]

roadcrash1, on Aug 26 2009, 12:15 AM, said:

no luck even after your suggestion blackosx i'm beginning to lose hope lol
i might be in a bit over my hea, as i might better off waiting for a distro to come out

we dont need a whole distro, its all about setting the right base for the system to boot, and some people found that and got it stable, but it seems based on luck now, once we get something like an updated version of chameleon(example) together with maybe a few little files in /E and we actually KNOW whats causing it to work we dont need a whole distro like what we had with 10.5 story.

distros give alot less freedom in the end anyway.

[elitee]

blackosx, on Aug 25 2009, 09:31 PM, said:

@elitee - Well done, Thanks for letting everyone know. For the record, can you remember anything in particular that you did extra to this guide that got it working for you? was it the Extensions.mkext?

My HD with SL just crashed, so I had to grab another and reinstall. It wasn't the Extensions.mkext in E/E (though it might be necessary in SL, I haven't checked yet). The biggest thing was having a proper DSDT and setting the permissions in the Snow Leopard Volume correctly, without it I got all sorts of weird kernel panics.

You could also have a generic DSDT for your board and use EFI strings for audio/video, but having the right DSDT made it easier.

[richtig]

YoYelloW, on Aug 25 2009, 07:36 PM, said:

we dont need a whole distro, its all about setting the right base for the system to boot, and some people found that and got it stable, but it seems based on luck now, once we get something like an updated version of chameleon(example) together with maybe a few little files in /E and we actually KNOW whats causing it to work we dont need a whole distro like what we had with 10.5 story.

distros give alot less freedom in the end anyway.

Maybe it could work this way:
Using a revised generic "boot 132" bootable CD, a blank USB memory stick, and the retail DVD:
Boot from the (new version) generic boot CD, that would write customized files (specific to the user hardware present) to then make a bootable USB drive.
Remove the CD & reboot from the new USB drive.
Insert retail DVD and continue with Snow Leopard customized install onto hard drive.

[blackosx]

YoYelloW, on Aug 26 2009, 12:36 AM, said:

we dont need a whole distro

If your hardware is very compatible like mine with this mobo then I agree retail is the way to go.

YoYelloW, on Aug 26 2009, 12:36 AM, said:

its all about setting the right base for the system to boot, and some people found that and got it stable, but it seems based on luck now

Yes the correct base is important, but also you need to set the permissions and build the Extensions.mkext.

I am still trying to help you guys here, so I wiped my 'BackupSL' partition this morning and did a re-install. I Rebooted in to Chameleon (which was using the -32 kernel flag in com.apple.Boot.plist), selected the BackupSL system and let it run and it KP'd at the grey screen at the start, didn't even show me the welcome video!... so I just went back in to 10.5.8, opened Terminal and typed (something like this)..

cd /Volumes/BackupSL/System/Library
sudo chown -R root:wheel Extensions
sudo kextcache -v 1 -t -m /Volumes/BackupSL/System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext /Volumes/BackupSL/System/Library/Extensions/

then rebooted back in to Chameleon, selected BackupSL and it worked this time ... got to desktop. I only spent about 5 minutes or so in it and did the automatic update of remote desktop client. But it worked fine..

elitee, on Aug 26 2009, 03:03 AM, said:

You could also have a generic DSDT for your board and use EFI strings for audio/video, but having the right DSDT made it easier.

Yes, for example, if you can't manage to get your video working with DSDT, then don't include video in your DSDT and just use a device (EFI) string for video in com.apple.Boot.plist. Just don'e have video in both the DSDT and and EFI string.

richtig, on Aug 26 2009, 03:57 AM, said:

Maybe it could work this way:
Using a revised generic "boot 132" bootable CD, a blank USB memory stick, and the retail DVD:

Yes I have read people talking about this method. Stellarolla says on his blog to avoid OSInstall.mkpg and put the SL disc image on to a 8GB USb stick anD go from there. And he knows what he's talking about! But for me the OSInstall.mkpg route works fine.

[YoYelloW]

blackosx, on Aug 26 2009, 08:19 AM, said:

Yes, for example, if you can't manage to get your video working with DSDT, then don't include video in your DSDT and just use a device (EFI) string for video in com.apple.Boot.plist. Just don'e have video in both the DSDT and and EFI string.

has to be the boot.plist thats in teh /Extra folder right? i dont have to dig up the one thats in the system folders somewhere

ill make a dsdt without gfx and cehck that out. (got the hang of it in w7 now anyway, w7 looks pretty nice tbh )

blackosx, on Aug 26 2009, 08:19 AM, said:

...

Yes I have read people talking about this method. Stellarolla says on his blog to avoid OSInstall.mkpg and put the SL disc image on to a 8GB USb stick anD go from there. And he knows what he's talking about! But for me the OSInstall.mkpg route works fine.

another partition would work as well im guessing? i think the problem with mpkg way is that priveleges go dodgy+ more stuffs?
i got enough disks so im gonna try to put it on a partition and see how that goes for me at elast.

[blackosx]

The com.apple.Boot.plist goes in /Extra. I supplied one to get you going in my support files - Use the 32-bit one (The yellow one, as it has the -x32 kernel flag set) and don't forget to edit the video resolution.

And yes, if you can't get video working properly from DSDT then build one without video.

Good idea, leave the Cham partition setup and make as many different SL partitions as you want to test with

[YoYelloW]

blackosx, on Aug 26 2009, 09:02 AM, said:

The com.apple.Boot.plist goes in /Extra. I supplied one to get you going in my support files - Use the 32-bit one (The yellow one, as it has the -x32 kernel flag set) and don't forget to edit the video resolution.

And yes, if you can't get video working properly from DSDT then build one without video.

Good idea, leave the Cham partition setup and make as many different SL partitions as you want to test with

got 1 spare 250gb disk, partitioned into 10 parts now, keeps me buzy


but why teh 32bit one? efi dont work with 64?

[blackosx]

Lol, Yeah... 10 installs, 10 minutes each from a mounted disc image.
Use the 32-bit kernel to boot your system to start with. Then once it's stable, try the 64-bit kernel. Keep it simple for now.

[YoYelloW]

blackosx, on Aug 26 2009, 10:19 AM, said:

Lol, Yeah... 10 installs, 10 minutes each from a mounted disc image.
Use the 32-bit kernel to boot your system to start with. Then once it's stable, try the 64-bit kernel. Keep it simple for now.

well sees to be holding now, i used a dsdt without gfx settings +efi, nothing changed, installed nvkush and got it working except that it seems my card as 256 and not 512. PLUS systems seems to be holding now (knockknock).

seems as the dsdt doesnt give proper info on audio and gfx for my system.


Btw booting from a restored partition with the dvd onit gave me a KP too in the installer, i jsut booted it nothing in -s or anything.