358 replies to this topic

[waveman777]

ricola, on Aug 29 2009, 03:42 PM, said:

Upload your DSDT.aml, i'll patch it for you

Thanks for trying to help me but unfortunately I don't know how to create my own DSDT.aml file... I know its a shame but... never done that before. Is there any soft to do this? I know that DSDTPatcherGUI_1.0 is for applying the file, but I don't know how to create one from scratch...

[ricola]

waveman777, on Aug 29 2009, 04:23 PM, said:

Thanks for trying to help me but unfortunately I don't know how to create my own DSDT.aml file... I know its a shame but... never done that before. Is there any soft to do this? I know that DSDTPatcherGUI_1.0 is for applying the file, but I don't know how to create one from scratch...

- copy DSDT Patcher1 folder from Downloads to Desktop - open a DSDT Patcher1 folder
- open Terminal (/Applications/Utilities/Terminal.app) - drag & drop DSDT Patcher into Terminal
- type -newHPET

/Users/user name/Desktop/DSDT_Patcher/DSDT\ Patcher -newHPET

and press Enter until you need to select Which OS to emulate? [0=Darwin,1=WinXP,2=WinVista], type 0 and press Enter

- in debug folder you'll find dsdt_fixed.txt, just send me that file

[waveman777]

ricola, on Aug 29 2009, 05:50 PM, said:

- copy a DSDT Patcher1 folder from Downloads to Desktop - open a DSDT Patcher1 folder
- open Terminal (/Applications/Utilities/Terminal.app) - drag & drop DSDT Patcher into Terminal
- type -newHPET

/Users/user name/Desktop/DSDT_Patcher/DSDT\ Patcher �€“newHPET

and press Enter until you need to select Which OS to emulate? [0=Darwin,1=WinXP,2=WinVista], type 0 and press Enter

- in debug folder you'll find dsdt_fixed.txt, just send me that file

Got it

[`Black]

ricola, on Aug 29 2009, 04:54 PM, said:

@'Black : how u get QE/CI for ur graphic card in Leopard?

EFI String. Tried to add it to dsdt.aml but that didn't work.

[ricola]

@Waveman777 : I attached ur DSDT.aml

and place your DSDT.aml to /Volumes/Snow/Extra

Type this in terminal :
sudo -s
chown 0:0 /Volumes/Snow
kextcache -v 1 -t -l -m /Volumes/Snow/Extra/Extensions.mkext /Volumes/Snow/Extra/Extensions /Volumes/Snow/System/Library/Extensions

@'Black : EFI String working fine in SL

[waveman777]

ricola, on Aug 29 2009, 06:58 PM, said:

@Waveman777 : I attached ur DSDT.aml

After you put DSDT.aml to /Volumes/Snow/Extra

Type this in terminal :

sudo chown -R 0:0 /Volumes/Snow/Extra/Extensions
 sudo chmod -R 755 /Volumes/Snow/Extra/Extensions
 sudo  kextcache -v 1 -t -l -m /Volumes/Snow/Extra/Extensions.mkext  /Volumes/Snow/Extra/Extensions /Volumes/Snow/System/Library/Extensions

Thanks a lot man, great job
Now, if you can tell me how did you make it... ? It would be very helpful in the future, I'm not gonna bother you next time Did you just add Audio and Network options to this file? How did you compile it? with iaslMe.v1.2?

[ricola]

waveman777, on Aug 29 2009, 06:11 PM, said:

Thanks a lot man, great job
Now, if you can tell me how did you make it... ? It would be very helpful in the future, I'm not gonna bother you next time Did you just add Audio and Network options to this file? How did you compile it? with iaslMe.v1.2?

Just add 'CMOS reset fix' and add HDEF(Audio), your network should work OOB . Compiled it with DSDT Patcher by fassl

[waveman777]

ricola, on Aug 29 2009, 07:26 PM, said:

Just add 'CMOS reset fix' and add HDEF(Audio), your network should work OOB . Compiled it with DSDT Patcher by fassl

When I was making dsdt_fixed.txt for you I got 1 error and a few warnings, is it normal? So the only way to compile DSDT.aml file is to use -f option to force it, is that correct?

[vividvew]

My specs
Abit IP35-Pro
Q6600 quad
BFG 7900GS 256MB

Quote

7. You have to modify GFX string in com.apple.boot.plist and information in smbios.plist to match yours.

Was not able to do this as my current install (iATKOS) does not seem to have these files. At least not in that same location.

Quote

10. open /Volumes/Mac\ OS\ X\ Install\ DVD/System/Installation/Packages/OSInstall.mpkg

Install failed first time. Start over, repeated same procedure, remove all printer drivers options. Success!

Quote

11. kextcache -v 1 -t -m /Volumes/Snow/Extra/Extensions.mkext /Volumes/Snow/Extra/Extensions /Volumes/Snow/System/Library/Extensions

Gives tons of errors. Mostly of the type

kextcache: kext /Volumes/Snow/Extra/Extensions/fakesmc.kext is not valid
   kernel extension /Volumes/Snow/Extra/Extensions/fakesmc.kext is not valid; skipping it and any plugins
   kext diagnostics:
   Validation failures:
   {
	   "Executable file doesn't contain kernel extension code" = true
   }
   Missing dependencies:
   {
	   "com.apple.iokit.IOACPIFamily" = 
		   "No valid version of this dependency can be found"
   }

Reboot and try anyway and I am getting same KP as mustiCas

Panic (cpu 0 caller 0x.....) Unable to find driver for this platform :\ACPI\".\n"@/SourceCache/xnu/xnu-1456.1.25/iokit /Kernel/IOPlatformExpert.cpp:1389

Having Problems with DSDT Patcher GUI same as boundone

...
   ./dsdt_fixed.txt  5819:						 Store (GAHS (0x00), Local6)
   Error	4060 -			Called method returns no value ^
   ...

Force compile and still get same KP.
Tried DSDT.aml that you posted for waveman777 but no joy. Assume my hardware does not match his.
Having trouble working through issue as I have no idea what DSDT.aml is for so can't troubleshoot in any logical manner.

Thanx for any help.
-vividvew

[vividvew]

made a little progress.

got 7900GS-256MB EFI string from OSX86Tools and inserted in com.apple.Boot.plist.
Still no idea what to do with plist that OSX86tools generated.

<?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
 <plist version="1.0">
 <dict>
	 <key>PciRoot(0x1)/Pci(0x1,0x0)/Pci(0x0,0x0)</key>
	 <dict>
		 <key>@0,compatible</key>
		 <string>NVDA,NVMac</string>
		 <key>@0,device_type</key>
		 <string>display</string>
		 <key>@0,name</key>
		 <string>NVDA,Display-A</string>
		 <key>@1,compatible</key>
		 <string>NVDA,NVMac</string>
		 <key>@1,device_type</key>
		 <string>display</string>
		 <key>@1,name</key>
		 <string>NVDA,Display-B</string>
		 <key>NVCAP</key>
		 <data>
		 BAAAAAAAAwAMAAAAAAAABwAAAAA=
		 </data>
		 <key>NVPM</key>
		 <data>
		 AQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==
		 </data>
		 <key>VRAM,totalsize</key>
		 <string>0x10000000</string>
		 <key>device_type</key>
		 <string>NVDA,Parent</string>
		 <key>model</key>
		 <string>nVidia GeForce 7900 GS</string>
		 <key>name</key>
		 <string>display</string>
		 <key>rom-revision</key>
		 <string>nVidia GeForce 7900 GS OpenGL Engine [EFI]</string>
	 </dict>
 </dict>
 </plist>

got new Extensions.mkext generated by using Kext Utility instead of CLI.


still can't get past KP. Googled around and found out what DSDT.aml is for.
compile with force option but still get same KP
tried just removing DSDT.aml but then get KP about HPET
tried using iasl to compile in gentoo but get 3 compile errors instead of 1.

attaching contents of my DSDT session dir in case at all useful.

Attached Files

•  dsdt.zip   107.71K   21 downloads

[ricola]

Hi Vividview,

Your com.apple.boot.plist will look something like this

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>Kernel</key>
	<string>mach_kernel</string>
	<key>Kernel Flags</key>
	<string>boot-uuid=PASTE_YOUR_UUID_HERE</string>
	<key>Timeout</key>
	<string>5</string>
	<key>device-properties</key>
	<string>PASTE_YOUR_GFX_STRING_HERE</string>
</dict>
</plist>

Here's DSDT.aml and com.apple.boot.plist (with 7900GS GFX String)

Attached Files

•  vvv.zip   24.14K   52 downloads

[boundone]

boundone, on Aug 29 2009, 06:20 PM, said:

Hey, I used your DSDT.aml in the guide and do not use my own.  I tried to make my own,
but got errors in the use of "DSDT Patcher":

...
 ./dsdt_fixed.txt  5819:						 Store (GAHS (0x00), Local6)
 Error	4060 -			Called method returns no value ^ 
 ...

Shall I ignore it and force to compile one?

Thanks for your help!

Boundone

Ah, I got it up and running! It is really an improvement with many changes underneath.

I think, everybody should compile their own DSDT file. Even on the same motherboard
there are differences.

Thanks again, Ricola, for your great guide and personal support!

Boundone

waveman777, on Aug 29 2009, 08:38 PM, said:

When I was making dsdt_fixed.txt for you I got 1 error and a few warnings, is it normal? So the only way to compile DSDT.aml file is to use -f option to force it, is that correct?

This is the same, that I got when compiling it: 4 warnings and 1 error.

Nevertheless, it could be patched and runs oob.

Boundone

[vividvew]

ricola,

Thank you very much for the help.

Still no joy. Now I am starting to think it is not because of DSDT.aml

At boot none of the kext in Extra are loading. All are giving errors.

I still cannot get step 11 to work without errors. I thought I got around this by using Kext Utility but maybe not. As KP is from AppleIntelCPUPowerManagement is assume that this means NullCPUPowerManagement is not doing it's job because it is not loading.

attaching output from kextcache and pic of KP.

Attached Files

•  kextcache_KP.zip   336.8K   13 downloads

[vividvew]

SUCCESS!!!

At least with -x32 but this is what I wanted anyway as vmware does not support 64bit SL kernel.

I just taking a guess here that you did your install from an earlier build of SL. I am doing this from Leopard. I don't think that kextcache can work correctly on 64bit SL kext when done from 32bit Leopard. Used alternate method.

touch /Volumes/Snow/Extra/Extensions
touch /Volumes/Snow/System/Library/Extensions/

Off to go check out all the little details like CI,QE,audio,Network, etc

Thank you very much for the help.

[mattswell]

Still not working

I recompiled my DSDT a third time, no difference. Deleted my Extensions.mkext, replaced it, no difference.


I've attached my DSDT files from DSDT_Patcher1

Hopefully someone can give me a hand? I can't seem to make a working version.

Attached Files

•  dsdt_mattswell.zip   221.81K   11 downloads

[vividvew]

mattswell, on Aug 30 2009, 04:57 PM, said:

Still not working

I recompiled my DSDT a third time, no difference. Deleted my Extensions.mkext, replaced it, no difference.


I've attached my DSDT files from DSDT_Patcher1

Hopefully someone can give me a hand? I can't seem to make a working version.

Are you still getting errors when doing

kextcache -v 1 -t -m /Volumes/Snow/Extra/Extensions.mkext /Volumes/Snow/Extra/Extensions /Volumes/Snow/System/Library/Extensions

If so the DSDT.aml may not be your problem. Take a look at my last post to get around this problem if you are doing install from Leopard or Tiger.

If you could post a screen shot of the KP screen that might help. For me the KP message was not he key. The key was the kext load failures a dozen or so lines above the KP message.

[mattswell]

vividvew, on Aug 30 2009, 11:11 AM, said:

Are you still getting errors when doing

kextcache -v 1 -t -m /Volumes/Snow/Extra/Extensions.mkext /Volumes/Snow/Extra/Extensions /Volumes/Snow/System/Library/Extensions

If so the DSDT.aml may not be your problem. Take a look at my last post to get around this problem if you are doing install from Leopard or Tiger.

If you could post a screen shot of the KP screen that might help. For me the KP message was not he key. The key was the kext load failures a dozen or so lines above the KP message.

I do get a million errors when running that command. I tried your alternate method of just touching those two directories, but I still had the same error when booting. Would running the kextcache command corrupt anything from Leopard?

[vividvew]

mattswell, on Aug 30 2009, 05:15 PM, said:

I do get a million errors when running that command. I tried your alternate method of just touching those two directories, but I still had the same error when booting. Would running the kextcache command corrupt anything from Leopard?

Well if you deleted it and then used Leopard to make a new one that got errors, maybe. Not that much of a guru to say for sure.

The key to find out if that is your problem is whether you see load errors for the kext in Extra during SL boot. For me pretty much every kext in Extra was not loading correctly during boot and this caused KP for AppleIntelCPUPowerManagement. Once the kext errors went away so did KP.

[mattswell]

vividvew, on Aug 30 2009, 11:20 AM, said:

Well if you deleted it and then used Leopard to make a new one that got errors, maybe. Not that much of a guru to say for sure.

The key to find out if that is your problem is whether you see load errors for the kext in Extra during SL boot. For me pretty much every kext in Extra was not loading correctly during boot and this caused KP for AppleIntelCPUPowerManagement. Once the kext errors went away so did KP.

Not sure how to even see the log. Once the KP happens, it clears the screen before displaying (using -v). I can't scroll to see what it failed on. The KP itself doesn't give any hints to what the error was involving...

During the load prior however I wasn't seeing errors about kexts not loading, so I really can't be sure.

mattswell, on Aug 30 2009, 11:24 AM, said:

Not sure how to even see the log. Once the KP happens, it clears the screen before displaying (using -v). I can't scroll to see what it failed on. The KP itself doesn't give any hints to what the error was involving...

During the load prior however I wasn't seeing errors about kexts not loading, so I really can't be sure.

You know I'm typing this on my macbook which is running snow leopard currently... I'm going to run that kext cache command from here and see if it makes a difference.

[vividvew]

mattswell, on Aug 30 2009, 05:26 PM, said:

Not sure how to even see the log. Once the KP happens, it clears the screen before displaying (using -v). I can't scroll to see what it failed on. The KP itself doesn't give any hints to what the error was involving...

During the load prior however I wasn't seeing errors about kexts not loading, so I really can't be sure.




You know I'm typing this on my macbook which is running snow leopard currently... I'm going to run that kext cache command from here and see if it makes a difference.

That would be worth a shot. If you can get a screen shot of the KP that would help a lot. There really should be more than just a hex mem address. The calling process should be listed as well.

Also try -x32 just to see if it works or if you get a different KP message. For me the two KP messages were about the same just that the 64bit one has longer hex mem addresses in KP message.