Jump to content

jumping back in :)


neilK
 Share

23 posts in this topic

Recommended Posts

hi folks :whistle:

 

awesome site helped me get a vanilla 10.5 install up and running, with win 7 on the partition, little over a year ago. and it ran mostly perfect, some sleep issue as i recall. was a "by hand" install using chameleon rc2 (or older one maybe?)

 

new house, finally got this machine set back up! win 7 was trial and has expired obviously, so i went out and bought one to put on.

 

in the meantime, snow leopard tools have appeared so i'm thinking of doing that too and going with dsdt as i don't think i bothered last time.

 

board is a GA-EP35-DS3L Rev 1, video is 9800gtx.

 

still catching up on threads, but seems there are many options to do this install. one being "LEAVE IT ALONE!" hahaha

 

what is the best method to do vanilla?

has anyone got this old board running using the [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url]/[url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] tools? seems so easy.

any issue-free 10.6.5 installs out there?

 

thanks

 

neilK :)

Link to comment
Share on other sites

so, i've been doing my homework and (mostly) have a plan. it will be a win7 and SL dual boot on a single drive.

 

i'm going to go with the [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url]/[url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] method as a first try.

 

couple questions:

 

1. i used 'dsdt auto patcher' to create the dsdt.aml file, am i supposed to do any further edits to this file or just point [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] to it when the time comes?

 

2. not sure if i should do the windows 7 or snow leopard install first. i have read many threads saying one or the other. leaning towards doing windows first but thought maybe i would use my SL DVD to setup the partition, then do win7, then do SL, update, and [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url].

 

3. kexts. more homework for me before i ask :D

 

probably going to be getting this started in about 3 or 4 hours, if anybody sees a "red flag" i would appreciate comments.

 

thanks

 

neilK

Link to comment
Share on other sites

quick update:

 

things went smooth. SL 10.6.5 is live, as is win 7 on its own partition. amazing really, everything installed, booted, updated, first try.

 

all is well except... the usual suspects: sleep and no audio.

 

it goes to sleep, keyboard tries to wake it but fails, and machine reboots.

 

left idle it goes into light sleep (no screen) and wakes no problem.

 

no issues with restart/shut down.

 

no KPs so far.

 

attempted to edit the dsdt file for the audio fix i saw here. however new dsdt would not compile (using app 'DSDTSE' to do this).

 

decided to test my dsdt.aml file unmodified and it wouldn't compile that either. it was created by 'dsdt auto-patcher' app, which let me choose my mobo from the dropdowns. not sure if there is a better way to get a working dsdt that i can edit for audio... DSDTSE will extract one - but from what i am reading there are a lot of 'fixes' to do.

 

a bit lost here, could use some help. i know it's an old mobo, but she's all i've got at the moment :D

 

thanks,

 

neilK

Link to comment
Share on other sites

quick update:

 

things went smooth. SL 10.6.5 is live, as is win 7 on its own partition. amazing really, everything installed, booted, updated, first try.

 

all is well except... the usual suspects: sleep and no audio.

 

it goes to sleep, keyboard tries to wake it but fails, and machine reboots.

 

left idle it goes into light sleep (no screen) and wakes no problem.

 

no issues with restart/shut down.

 

no KPs so far.

 

attempted to edit the dsdt file for the audio fix i saw here. however new dsdt would not compile (using app 'DSDTSE' to do this).

 

 

Try using the voodoohda.kext for audio, install it using kextutility. It'll work for almost all sound cards, as far as sleep, I'm stumped.

 

decided to test my dsdt.aml file unmodified and it wouldn't compile that either. it was created by 'dsdt auto-patcher' app, which let me choose my mobo from the dropdowns. not sure if there is a better way to get a working dsdt that i can edit for audio... DSDTSE will extract one - but from what i am reading there are a lot of 'fixes' to do.

 

a bit lost here, could use some help. i know it's an old mobo, but she's all i've got at the moment ;)

 

thanks,

 

neilK

Link to comment
Share on other sites

sound working!

 

not sure what was up with the dsdt file, must have broken it somewhere along the way. went back to the original and it compiled fine in DSDTSE.

 

so i typed in the HDEF hack by hand, from the thread linked above. compiled fine. [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] did the deed and we have sound.

 

sleep is next.

 

noticed on -v that the last thing seen before desktop is a comment about "c states not being set" or something like that. does that mean more DSDT edits for me?

 

help appreciated.

 

tldr: sleep left only. e/e: fakesmc.kext, IOAHCIBlockStorageInjector.kext, Legacy888HDA.kext

 

off to bed. ;)

 

neilK

Link to comment
Share on other sites

well, not a very productive day (vacation is a good time to hackintosh -_- )

 

no luck on sleep. messing around with some things i've seen here, and looks like some have had success with editing DSDT and then adding lines to boot.plist for p states and c states, but i am now officially in over my head. had lots of fun and weird things happen though!

 

i've tried a few sleepenabler kexts but none have brought sleep. at this point on my own, i'm stuck with an insomniac hack.

Link to comment
Share on other sites

still working on sleep.

 

last logged lines in -v before desktop:

 

ACPI_SMC_PlatformPlugin::pushCPU_CSTData - _CST evaluation failed

ACPI_SMC_PlatformPlugin::registerLPCDriver - WARNING - LPC device initialization failed: C-state power management not initialized

 

i do not have have generatePstates, generateCstates, or dropSSDT in my c.a.B.plist.

 

if i add them, it fails to boot, if dropSSDT is yes or no. last thing -v shows is 'found: ACPI CPU 0', then CPU 1 2 and 3, then 'SSDT with cpu c states generated successfully', and then it just sits there.

 

earlier in the log it says 'ACPI table not found: SSDT.aml '

 

i think i'm missing something maybe in my DSDT.aml and i have not been able to figure out how to create SSDT.aml files. i have started to read the long 'fixes for gigabyte boards' thread but it gets over my head pretty quick. i have dl'd one of the dsdt files but i can't boot with it, i did add some SSDT info to my DSDT.aml but the result was the same.

 

anybody have any ideas?

Link to comment
Share on other sites

You need to do some more work to get native power management going.

Get AppleLPC.kext to load and some other stuff too - follow this checklist:

http://www.projectosx.com/forum/index.php?...amp;#entry10065

Read this topic for more information:

http://www.insanelymac.com/forum/index.php?showtopic=225766

You can dump all your ACPI tables (including SSDT) using Everest Corporate or Ultimate Edition on Windows.

Look at the screenshots in this post to see how to do that:

http://www.insanelymac.com/forum/index.php...p;#entry1468558

Enable ACPI 2.0 and ACPI APIC before dumping your APCI tables.

Don't overclock while you're experimenting with this and make sure all CPU features (except CPUID limit) are enabled in the BIOS.

Link to comment
Share on other sites

i've read your first link just now, more info:

 

i installed using [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] disc and [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] which at 2.6 is using chameleon 2.0 rc5 r651.

 

unmodified processor scope: how do i make sure this is correct? my DSDT.aml file was generated, the first time, by DSDT auto-patcher for my board (http://www.insanelymac.com/forum/index.php...howtopic=235523)

 

all 3 kexts showing are loaded according to system profiler.

 

vanilla kernel, intel cpu and intel chipset = true

 

model identifier is macpro 3,1. my e/e folder has it in smbios.plist. got a bit lucky on this one, i chose the first mac pro model in the [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] options.

 

i will work through the 58 page thread as best i can. i had started it earlier but didn't get too far, i will resume.

 

the third link i will try as well. my proc is quite overclocked (e2200 - it's slow at default) but easily returned to default while i try things.

 

in my com.apple.Boot.plist, will i add 'generate c states' and 'generate p states' and 'dropSSDT yes' once i have SSDT.aml files?

 

thank you for these links, i will update when i have news!

 

neilK

Link to comment
Share on other sites

unmodified processor scope: how do i make sure this is correct? my DSDT.aml file was generated, the first time, by DSDT auto-patcher

 

It probably has the CPU aliases removed then? I don't know - I have never used the DSDT auto-patcher and I can no longer remember if having the CPU aliases in there makes any difference. You can compare the DSDT you're using now to the one you'll be extracting under Windows using Everest.

 

You can use DSDTSE or the DSDT Editor by el coniglio and oldnapalm to view and edit your ACPI tables. Use google or the forum search to find them.

Link to comment
Share on other sites

to you i say: um milhão de agradecimentos!!!

 

processor scope was not modified in any substantial way. the everest one might give a 0x00 where mine said 'zero', etc but otherwise completely the same.

 

so, i dropped the ssdt.aml files (there were 3 of them) into my 'extra' folder, added lines com.apple.boot.plist to generate-p states and c-states.

 

reboot and... it boots! first time to get this far.

 

i hold my breath for a second and then... "sleep". wait a few seconds, then hit space bar. it wakes up! amazing and thank you for this last bit of the puzzle (getting ssdt.aml files) as now all is well. i am very grateful.

 

neilK :D

Link to comment
Share on other sites

i ran it for a while at native (2.2GHz), then clocked it back up to 3.0GHz, the limit of where it runs stable on each OS. at some point i really need to get something faster than an e2200 hahaha

 

i'm going to d/l CPU-X and see how things are going. i know on the win 7 OS there has never been any problems with stepping. fingers crossed :)

Link to comment
Share on other sites

well i spoke too soon :D . my previous post was on win 7 and i had not booted back to SL with the overclock.

 

it failed, it says during boot that i am missing SDST-3.aml and hangs.

 

back to windows to create new SDST files, and yes they are different. but a problem - there is no 4th SDST in the dropdown to create SDST-3.aml

 

reboot to SL from [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] CD, removed all SDST.aml files, and c-state/p-state tags from com.apple.Boot.plist, and rebooted (still overclocked).

 

went to ioRegistryExplorer -> AppleACPIPlatformExpert -> ACPI tables and there is only one SSDT table showing. copied the hex, pasted to hex editor. is there a way to turn this into a readable file for DSDTSE so that i can see what is in there?

Link to comment
Share on other sites

Well..I did suggest that you don't overclock while you're experimenting with this. This is why.

On most motherboads, overclocking will disable ACPI power management - Look in your BIOS, you'll probably see some CPU settings missing or grayed out. This also explain why you don't see as many SSDT tables with Everest, they are not used when overclocking because you are setting frequencies manually.

 

You're complicating things - don't use ioreg to get your SSDTs (and pay attention ;) it's SSDT, not SDST!):

1.png2.png

But but but..extracting those tables in OS X is pointless - unless you want to see what Chameleon is doing to them - the SSDT tables you see in ioreg (and can extract with DSDTSE) are the ones generated by Chameleon + the ones you put in /Extra yourself! lol

 

What happens if you keep the overclock and place the new SSDT tables in /Extra (Extract them with Everest)?

Make sure you remove all the old ones first.

Link to comment
Share on other sites

your suggestion is a good one. with your help, i can live long and prosper without the overclock. but this is a new experiment :wacko:

 

i made an important omission in my earlier post. (well, two as the first is that i did attempt to use the new SSDT files generated in everest with the overclock, and that was the failed boot that asked for SSDT-3.aml.)

 

but more interesting:

 

the new (overclock) SSDT.aml (i will be watching for typos hahaha) has this:

 

Name (SPSS, Package (0x02)

 

with only two sets of values (return values for stepping?)

 

the native (no overclock) SSDT.aml has this:

 

Name (SPSS, Package (0x03)

 

and three sets of values. on the native speed, the first hex value in the first set is:

 

0x00000898

 

which in decimal is... 2200. the max speed of the CPU in Hz with no overclock. interestingly the max speed of the overclocked should show

 

0x00000BB8

 

for 3000Hz but instead shows 2667 as the first value (maximum cpu speed? i am guessing) which at my cpu multiplier corresponds to a 333MHz bus, but i am not sure if that is important.

 

this variation is also true for the values under NPSS as well.

 

the only other difference in the files is in SSDT-2.aml, which has one hex value different and it corresponds to the byte length of SSDT.aml in both native and overclocked versions of that file.

 

i am going to try setting the overclock to match the 2667 value and see what the SSDT files look like.

 

(thank you for confirming that extracting tables in OS X only returns what i give it. i thought possibly hahaha)

Link to comment
Share on other sites

...

But but but..extracting those tables in OS X is pointless - unless you want to see what Chameleon is doing to them - the SSDT tables you see in ioreg (and can extract with DSDTSE) are the ones generated by Chameleon + the ones you put in /Extra yourself! lol

You are right, but the original data is still accessible. Just not from the ioreg dumps (we should have a tool for this a.s.a.p).

Link to comment
Share on other sites

You are right, but the original data is still accessible. Just not from the ioreg dumps (we should have a tool for this a.s.a.p).

Should the bootloader store original tables somewhere before replacing them, or is there an easy way to access it directly?

Link to comment
Share on other sites

 Share

×
×
  • Create New...