Jump to content

Master Chief's P5K PRO ACPI Warfare


VegasKarma
 Share

908 posts in this topic

Recommended Posts

This is an interesting approach. Just so people know. If you're looking for the PCI address of ANY of your devices not just your GFX card. All you have to do is use the command
./gfxutil -f pci8086,3a34

it should spit out something like:

DevicePath = PciRoot(0x1)/Pci(0x1d,0x0)

Or simply use something like:

 

gfxutil -f ethernet

gfxutil -f lan0

gfxutil -f display

gfxutil -f EHCI

gfxutil -f UHCI

gfxutil -f UHCn

gfxutil -f hdef

 

In either lower or uppercase.

Link to comment
Share on other sites

Sleep is more important. This can wait. Don't forget to sleep in time!

 

 

You got it. Great!

 

 

Like I said: I am not trying to get the smallest possible DSDT ever, but the next update will however include a number of patches from the "insane DSDT". Of course, but all of it.

 

BTW: My first goal was to satisfy my own curiosity about ACPI coding. And because of this I was able to lower the barrier for other people. For non-developers, people like yourself. Or at least that's what I hear from people PM'ing me.

 

I'm also trying to change the way (some) people think about (code) sharing. Which I think is the biggest asset of my work. Sharing. I mean without sharing we would have been... nowhere. Right?

 

And I don't know everything. Of course not. Sometimes I have to search and think hard to get something done. And this next to other work (hello Mozilla). Not being afraid to make mistakes is a plus. Probably because mistakes are just that. Mistakes. No wrong doing whatsoever. I mean; Aren't we all learning something new here?

 

Sorry. Had to get something off my chest. Done!

 

With every mistake something is learned.

Link to comment
Share on other sites

Ok so it's a couple of day that i'm thinking about the usb patch

for what i see there are 6 portion of code that are identical

 

Device (UHC0)
           {
               [color="#FF0000"]Name (_ADR, 0x001D0000)[/color]
               Name (_PRW, Package (0x02)
               {
                   0x03, 
                   0x04
               })
               Name (_S3D, 0x02)
               OperationRegion (BAR0, PCI_Config, 0xC4, One)
               Field (BAR0, ByteAcc, NoLock, Preserve)
               {
                   USBW,   2,
                   		Offset (0x01)
               }

               Method (_PSW, 1, NotSerialized)
               {
                   Multiply (0x03, Arg0, USBW)
               }
           }

 

the red part change for every USB but the black not. So i think that is possible to put a method similar to:

 

Method (MCID, 2, NotSerialized)

or something like the alias for the CPU

where can i start to find info about implementing this by myself?

Link to comment
Share on other sites

Ok so it's a couple of day that i'm thinking about the usb patch

for what i see there are 6 portion of code that are identical

 

Device (UHC0)
           {
               [color="#FF0000"]Name (_ADR, 0x001D0000)[/color]
               Name (_PRW, Package (0x02)
               {
                   0x03, 
                   0x04
               })
               Name (_S3D, 0x02)
               OperationRegion (BAR0, PCI_Config, 0xC4, One)
               Field (BAR0, ByteAcc, NoLock, Preserve)
               {
                   USBW,   2,
                   		Offset (0x01)
               }

               Method (_PSW, 1, NotSerialized)
               {
                   Multiply (0x03, Arg0, USBW)
               }
           }

 

the red part change for every USB but the black not. So i think that is possible to put a method similar to:

 

Method (MCID, 2, NotSerialized)

or something like the alias for the CPU

where can i start to find info about implementing this by myself?

 

Have a look at the "Insane dsdt" you'll see you end up with this for UHC's

 

Device (UHC1)
           {
               [color="#FF0000"]Name (_ADR, 0x001D0000)[/color]
               Name (_PRW, Package (0x02)
               {
                   [color="#FF0000"]0x03, 
                   0x04[/color]
               })
           }

           Device (UHC2)
           {
               Name (_ADR, 0x001D0001)
               Name (_PRW, Package (0x02)
               {
                   [color="#FF0000"]0x04, 
                   0x04[/color]
               })
           }

           Device (UHC3)
           {
               Name (_ADR, 0x001D0002)
               Name (_PRW, Package (0x02)
               {
                  [color="#FF0000"] 0x0C, 
                   0x04[/color]
               })
           }

           Device (UHC4)
           {
               Name (_ADR, 0x001A0000)
               Name (_PRW, Package (0x02)
               {
                   [color="#FF0000"]0x0E, 
                   0x04[/color]
               })
           }

           Device (UHC5)
           {
               Name (_ADR, 0x001A0001)
               Name (_PRW, Package (0x02)
               {
                   [color="#FF0000"]0x05, 
                   0x04[/color]
               })
           }

           Device (UHC6)
           {
               Name (_ADR, 0x001A0002)
               Name (_PRW, Package (0x02)
               {
                   [color="#FF0000"]0x20, 
                   0x04[/color]
               })
           }
       }

 

It's not just the address that changes and this code is short enough anyways.

 

To all: I am about to attach an insanely small – only 2024 bytes – but still fully functional DSDT as an example / a study object only, because I know that people are going to fall over it, jump right in and get back hundreds of times with all sort of complaints, and questions, simply because they don't know what to do with it. Not exactly something I am waiting for, but here we go; compiling...

 

No complaints here it works for me on VM. Excellent work Chief - thanks for your hard work.

 

Anyone else notice if you use GraphicsEnabler in Boot.plist with Chameleon boot then insert a device-property string the graphics fail.i.e seems they wont work in combination (at least for me in Cham4 or with PCEFI 5). Had to combine graphics string with the device id's to get things working. Oh and I left HDEF in the dsdt rather than hack about in the kexts.

Link to comment
Share on other sites

Have a look at the "Insane dsdt" you'll see you end up with this for UHC's

 see post # 580

It's not just the address that changes and this code is short enough anyways.

Spot on.

 

Note to scrax: The first value in the _PRW package is sort of link to the _GPE (representing a bit number see the ICHn datasheet) and the second value is the lowest power state (Sn) supported for the wake functionality.

 

No complaints here it works for me on VM. Excellent work Chief - thanks for your hard work.

Thank you for the confirmation.

 

BTW: Did you also 'fix' AppleHDA.kext also? Both of these reduced my boot time up to five seconds. You can verify this by looking at kernel.log Oh and removing kexts was a good idea after all – booting from a modified USB installation made that perfectly clear to me.

 

Anyone else notice if you use GraphicsEnabler in Boot.plist with Chameleon boot then insert a device-property string the graphics fail.i.e seems they wont work in combination (at least for me in Cham4 or with PCEFI 5). Had to combine graphics string with the device id's to get things working. Oh and I left HDEF in the dsdt rather than hack about in the kexts.

I ran into this when I started to add GFX data into my DSDT – I still had device properties in com.apple.Boot.plist which apparently wasn't a good idea.

 

I wish I had a 885 chip like you. Much easier to fix it seems.

Link to comment
Share on other sites

Man thats one BIG plist :D better CHECK mine.

Yeah. I couldn't believe it at first. LOL I even started to count the digits. Thinking to be delusional (and I was as I should have said MB instead of GB).

 

Note: This I presume will get fixed in a next upgrade – like they did with ACPI_SMC_PlatformPlugin.kext (have a look in Resources and find 30 new plists).

 

To all: Anyone here having lines with: com.apple.launchd.peruser in system.log? I had/have:

 

com.apple.ReportCrash (fixed by removing file)

com.apple.Kerberos.renew.plist (fixed by removing file).

com.apple.CSConfigDotMacCert-... (part of core service)

 

Pointing to files in: /System/Library/LaunchAgents (enter: launchctl list in a terminal window). See also post #516

Link to comment
Share on other sites

Hey Jefe

 

Why the hell is your AppleHDAPlatformDriver so BIG. Mine use 2.5 mb. As difference to you i am using all 3 kext in extra and not just 2.

 

/Volumes/BootThink/Darwin/System/LibrarySL/Extensions/LegacyAppleHDAHardwareConfigDriver.kext

/Volumes/BootThink/Darwin/System/LibrarySL/Extensions/LegacyHDAController.kext

/Volumes/BootThink/Darwin/System/LibrarySL/Extensions/LegacyHDAPlatformDriver.kext

 

And as i posted in the beginning of these threat i don't get the sound assertions error using bootthink on 64bit.

 

salu2

Link to comment
Share on other sites

Hey Jefe

 

Why the hell is your AppleHDAPlatformDriver so BIG. Mine use 2.5 mb.

So I was delusional after all. I mean I should have said MB instead of GB – was in the usual rush to get work done. Anyway. I need my sleep now. Before I start making hideous errors :P

 

As difference to you i am using all 3 kext in extra and not just 2.

 

/Volumes/BootThink/Darwin/System/LibrarySL/Extensions/LegacyAppleHDAHardwareConfigDriver.kext

/Volumes/BootThink/Darwin/System/LibrarySL/Extensions/LegacyHDAController.kext

/Volumes/BootThink/Darwin/System/LibrarySL/Extensions/LegacyHDAPlatformDriver.kext

 

And as i posted in the beginning of these threat i don't get the sound assertions error using bootthink on 64bit.

 

salu2

I don't have any Legacy kexts left. I copied my Info.plist data (from legacy kext) into a new copy of AppleHDA.kext which I load after boot time now. Same for Yukon2. Much faster this way.

Link to comment
Share on other sites

hello chief, i´ve got audio mic working in 10.6.2/64 bit with these kext.

 

it works but not as it should. behind wakeup the sound is quitly. posible you could insert it into your kext or dsdt.

 

i have a please, could you please insert into your dsdt 2.4 my cpu (Package (0x06) { 2997, 80535, 10, 10, 0x921, 0x921 }) ?

i does it wrong, because every second boot i get panic and without it is to slow. i use all your kext, without CPUi.kext and CPU injektor.kext.

 

also iám not able to change my imac 8.1 into a mac pro or p5k-pro. could you please post your ioplatformfamily.kext ?

it would be great if you could help me, thx in advance :P

Carstimann_kext.zip

Link to comment
Share on other sites

I ran into this when I started to add GFX data into my DSDT – I still had device properties in com.apple.Boot.plist which apparently wasn't a good idea.

 

I wish I had a 885 chip like you. Much easier to fix it seems.

 

For everyone having trouble injecting their devices via EFI strings maybe this will help. Way before DSDT this is the way it was done.

 

Assemble your device plist like so. This one contains two graphics cards, ethernet and HDEF. You coulds easily add your USB and anything else you wish but structure it 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>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>@2,#adress-cells</key>
	<string>0x01000000</string>
	<key>@2,#size-cells</key>
	<string>0x00000000</string>
	<key>@2,compatible</key>
	<string>NVDA,sensor-parent</string>
	<key>@2,device_type</key>
	<string>NVDA,gpu-diode</string>
	<key>@2,hwctrl-params-version</key>
	<string>0x02000000</string>
	<key>@2,hwsensor-params-version</key>
	<string>0x02000000</string>
	<key>@2,name</key>
	<string>sensor-parent</string>
	<key>@2,reg</key>
	<string>0x02000000</string>
	<key>NVCAP</key>
	<data>
	BAAAAAAAAwAMAAAAAAAABwAAAAA=
	</data>
	<key>NVPM</key>
	<data>
	AQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==
	</data>
	<key>VRAM,totalsize</key>
	<data>
	AAAAIA==
	</data>
	<key>device_type</key>
	<string>NVDA,GeForce</string>
	<key>model</key>
	<string>NVIDIA GeForce 8800 GT 512</string>
	<key>name</key>
	<string>NVDA,Parent</string>
	<key>rom-revision</key>
	<string>3172a</string>
</dict>
<key>PciRoot(0x1)/Pci(0x1c,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>@2,#adress-cells</key>
	<string>0x01000000</string>
	<key>@2,#size-cells</key>
	<string>0x00000000</string>
	<key>@2,compatible</key>
	<string>NVDA,sensor-parent</string>
	<key>@2,device_type</key>
	<string>NVDA,gpu-diode</string>
	<key>@2,hwctrl-params-version</key>
	<string>0x02000000</string>
	<key>@2,hwsensor-params-version</key>
	<string>0x02000000</string>
	<key>@2,name</key>
	<string>sensor-parent</string>
	<key>@2,reg</key>
	<string>0x02000000</string>
	<key>NVCAP</key>
	<data>
	BAAAAAAAAwAMAAAAAAAABwAAAAA=
	</data>
	<key>NVPM</key>
	<data>
	AQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==
	</data>
	<key>VRAM,totalsize</key>
	<data>
	AAAAEA==
	</data>
	<key>device_type</key>
	<string>NVDA,GeForce</string>
	<key>model</key>
	<string>NVIDIA GeForce 8500 GT 256</string>
	<key>name</key>
	<string>NVDA,Parent</string>
	<key>rom-revision</key>
	<string>3172a</string>
</dict>
<key>PciRoot(0x1)/Pci(0x1c,0x5)/Pci(0x0,0x0)</key>
<dict>
	<key>built-in</key>
	<string>0x01</string>
</dict>
<key>PciRoot(0x1)/Pci(0x1b,0x0)</key>
 	<dict>
   	<key>PinConfigurations</key>
   	<string></string>
   	<key>built-in</key>
   	<string>0x00</string>
   	<key>layout-id</key>
   	<string>0x0000000c</string>
   	<key>revision-id</key>
   	<string>0x00000001</string>
   	<key>subsystem-id</key>
   	<string>0x0000a002</string>
   	<key>subsystem-vendor-id</key>
   	<string>0x00001458</string>
   	<key>vendor-id</key>
   	<string>0x00008086</string>
</dict>
</dict>
</plist>

 

Then use gfxutility to turn it into your giant hex string:

d507000001000000030000003f0000000100000002010c00d041030a010000000101060
0051c0101060000007fff0400160000006200750069006c0074002d0069006e0000000500000001c
5
0300001500000002010c00d041030a010000000101060000010101060000007fff04001400000040
0
032002c006e0061006d00650000001100000073656e736f722d706172656e7422000000560052004
1
004d002c0074006f00740061006c00730069007a0065000000080000000000002036000000400032
0
02c00680077006300740072006c002d0070006100720061006d0073002d007600650072007300690
0
6f006e00000008000000000000021c0000006400650076006900630065005f007400790070006500
0
000100000004e5644412c4765466f7263650e0000006e0061006d00650000000f0000004e5644412
c
506172656e7422000000400030002c006400650076006900630065005f0074007900700065000000
0
b000000646973706c6179100000006d006f00640065006c0000001e0000004e56494449412047654
6
6f72636520383830302047542035313222000000400031002c006400650076006900630065005f00
7
40079007000650000000b000000646973706c617912000000400032002c007200650067000000080
0
00000000000222000000400032002c006400650076006900630065005f0074007900700065000000
1
20000004e5644412c6770752d64696f646520000000400032002c0063006f006d007000610074006
9
0062006c0065000000160000004e5644412c73656e736f722d706172656e7422000000400032002c
0
02300730069007a0065002d00630065006c006c00730000000800000000000000200000004000310
0
2c0063006f006d00700061007400690062006c00650000000e0000004e5644412c4e564d61631400
0
000400030002c006e0061006d0065000000120000004e5644412c446973706c61792d413a0000004
0
0032002c0068007700730065006e0073006f0072002d0070006100720061006d0073002d00760065
0
07200730069006f006e000000080000000000000226000000400032002c002300610064007200650
0
730073002d00630065006c006c0073000000080000000000000114000000400031002c006e006100
6
d0065000000120000004e5644412c446973706c61792d4220000000400030002c0063006f006d007
0
0061007400690062006c00650000000e0000004e5644412c4e564d61631e00000072006f006d002d
0
07200650076006900730069006f006e000000090000003331373261100000004e005600430041005
0
0000001800000004000000000003000c00000000000007000000000e0000004e00560050004d0000
0
02000000001000000000000000000000000000000000000000000000000000000c50300001500000
0
02010c00d041030a0100000001010600001c0101060000007fff040014000000400032002c006e00
6
1006d00650000001100000073656e736f722d706172656e74220000005600520041004d002c00740
0
6f00740061006c00730069007a0065000000080000000000001036000000400032002c0068007700
6
300740072006c002d0070006100720061006d0073002d00760065007200730069006f006e0000000
8
000000000000021c0000006400650076006900630065005f0074007900700065000000100000004e
5
644412c4765466f7263650e0000006e0061006d00650000000f0000004e5644412c506172656e742
2
000000400030002c006400650076006900630065005f00740079007000650000000b000000646973
7
06c6179100000006d006f00640065006c0000001e0000004e5649444941204765466f72636520383
5
30302047542032353622000000400031002c006400650076006900630065005f0074007900700065
0
000000b000000646973706c617912000000400032002c00720065006700000008000000000000022
2
000000400032002c006400650076006900630065005f0074007900700065000000120000004e5644
4
12c6770752d64696f646520000000400032002c0063006f006d00700061007400690062006c00650
0
0000160000004e5644412c73656e736f722d706172656e7422000000400032002c00230073006900
7
a0065002d00630065006c006c0073000000080000000000000020000000400031002c0063006f006
d
00700061007400690062006c00650000000e0000004e5644412c4e564d616314000000400030002c
0
06e0061006d0065000000120000004e5644412c446973706c61792d413a000000400032002c00680
0
7700730065006e0073006f0072002d0070006100720061006d0073002d0076006500720073006900
6
f006e000000080000000000000226000000400032002c0023006100640072006500730073002d006
3
0065006c006c0073000000080000000000000114000000400031002c006e0061006d006500000012
0
000004e5644412c446973706c61792d4220000000400030002c0063006f006d00700061007400690
0
62006c00650000000e0000004e5644412c4e564d61631e00000072006f006d002d00720065007600
6
900730069006f006e000000090000003331373261100000004e00560043004100500000001800000
0
04000000000003000c00000000000007000000000e0000004e00560050004d000000200000000100
0
000000000000000000000000000000000000000000000000000

 

Then combine them into your com.apple.boot.plist under device-properties:

<?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>Graphics Mode</key>
<string>1280x1024x32@60Hz</string>
<key>Kernel</key>
<string>mach_kernel</string>
<key>Kernel Flags</key>
<string>MemSpeed=1066 -v</string>
<key>Timeout</key>
<string>3</string>
<key>device-properties</key>
<string>d507000001000000030000003f0000000100000002010c00d041030a0100000001010600051c0
101060000007fff0400160000006200750069006c0074002d0069006e0000000500000001c503000
0
1500000002010c00d041030a010000000101060000010101060000007fff04001400000040003200
2
c006e0061006d00650000001100000073656e736f722d706172656e74220000005600520041004d0
0
2c0074006f00740061006c00730069007a0065000000080000000000002036000000400032002c00
6
80077006300740072006c002d0070006100720061006d0073002d00760065007200730069006f006
e
00000008000000000000021c0000006400650076006900630065005f007400790070006500000010
0
000004e5644412c4765466f7263650e0000006e0061006d00650000000f0000004e5644412c50617
2
656e7422000000400030002c006400650076006900630065005f00740079007000650000000b0000
0
0646973706c6179100000006d006f00640065006c0000001e0000004e5649444941204765466f726
3
6520383830302047542035313222000000400031002c006400650076006900630065005f00740079
0
07000650000000b000000646973706c617912000000400032002c007200650067000000080000000
0
00000222000000400032002c006400650076006900630065005f0074007900700065000000120000
0
04e5644412c6770752d64696f646520000000400032002c0063006f006d007000610074006900620
0
6c0065000000160000004e5644412c73656e736f722d706172656e7422000000400032002c002300
7
30069007a0065002d00630065006c006c0073000000080000000000000020000000400031002c006
3
006f006d00700061007400690062006c00650000000e0000004e5644412c4e564d61631400000040
0
030002c006e0061006d0065000000120000004e5644412c446973706c61792d413a0000004000320
0
2c0068007700730065006e0073006f0072002d0070006100720061006d0073002d00760065007200
7
30069006f006e000000080000000000000226000000400032002c002300610064007200650073007
3
002d00630065006c006c0073000000080000000000000114000000400031002c006e0061006d0065
0
00000120000004e5644412c446973706c61792d4220000000400030002c0063006f006d007000610
0
7400690062006c00650000000e0000004e5644412c4e564d61631e00000072006f006d002d007200
6
50076006900730069006f006e000000090000003331373261100000004e005600430041005000000
0
1800000004000000000003000c00000000000007000000000e0000004e00560050004d0000002000
0
00001000000000000000000000000000000000000000000000000000000c50300001500000002010
c
00d041030a0100000001010600001c0101060000007fff040014000000400032002c006e0061006d
0
0650000001100000073656e736f722d706172656e74220000005600520041004d002c0074006f007
4
0061006c00730069007a0065000000080000000000001036000000400032002c0068007700630074
0
072006c002d0070006100720061006d0073002d00760065007200730069006f006e0000000800000
0
000000021c0000006400650076006900630065005f0074007900700065000000100000004e564441
2
c4765466f7263650e0000006e0061006d00650000000f0000004e5644412c506172656e742200000
0
400030002c006400650076006900630065005f00740079007000650000000b000000646973706c61
7
9100000006d006f00640065006c0000001e0000004e5649444941204765466f72636520383530302
0
47542032353622000000400031002c006400650076006900630065005f0074007900700065000000
0
b000000646973706c617912000000400032002c00720065006700000008000000000000022200000
0
400032002c006400650076006900630065005f0074007900700065000000120000004e5644412c67
7
0752d64696f646520000000400032002c0063006f006d00700061007400690062006c00650000001
6
0000004e5644412c73656e736f722d706172656e7422000000400032002c002300730069007a0065
0
02d00630065006c006c0073000000080000000000000020000000400031002c0063006f006d00700
0
61007400690062006c00650000000e0000004e5644412c4e564d616314000000400030002c006e00
6
1006d0065000000120000004e5644412c446973706c61792d413a000000400032002c00680077007
3
0065006e0073006f0072002d0070006100720061006d0073002d00760065007200730069006f006e
0
00000080000000000000226000000400032002c0023006100640072006500730073002d006300650
0
6c006c0073000000080000000000000114000000400031002c006e0061006d006500000012000000
4
e5644412c446973706c61792d4220000000400030002c0063006f006d00700061007400690062006
c
00650000000e0000004e5644412c4e564d61631e00000072006f006d002d00720065007600690073
0
069006f006e000000090000003331373261100000004e00560043004100500000001800000004000
0
00000003000c00000000000007000000000e0000004e00560050004d000000200000000100000000
0
000000000000000000000000000000000000000000000</string>
</dict>
</plist>

 

Here are the files attached. You can also use other utilities like OSX86tools or EFIStudio to convert your device info into hex. The attached files were used for my old GA-EP35-DS4.

EFI_strings.zip

Link to comment
Share on other sites

Yeah. I couldn't believe it at first. LOL I even started to count the digits. Thinking to be delusional (and I was as I should have said MB instead of GB).

 

Note: This I presume will get fixed in a next upgrade – like they did with ACPI_SMC_PlatformPlugin.kext (have a look in Resources and find 30 new plists).

 

To all: Anyone here having lines with: com.apple.launchd.peruser in system.log? I had/have:

 

com.apple.ReportCrash (fixed by removing file)

com.apple.Kerberos.renew.plist (fixed by removing file).

com.apple.CSConfigDotMacCert-... (part of core service)

 

Pointing to files in: /System/Library/LaunchAgents (enter: launchctl list in a terminal window). See also post #516

 

 

Hi, here I am again.

 

My string about launchctl are this in system.log (at boot, at logout)

I've removed this in every line: Dec 12 04:13:18 Mac-Pro-di-scrax com.apple.launchd.peruser.501

[color="#2E8B57"]04:13:18 peruser.501[100] (com.apple.ReportCrash): Falling back to default Mach exception handler. 
Could not find: com.apple.ReportCrash.Self
04:13:19 peruser.501[100] (com.apple.Kerberos.renew.plist[123]): Exited with exit code: 1[/color]
[color="#0000FF"]05:22:34 peruser.501[100] ([0x0-0x1e01e].com.apple.TextEdit[336]): Exited: Killed
05:22:34 peruser.501[100] ([0x0-0x11011].com.apple.systemevents[137]): Exited: Killed
05:22:34 peruser.501[100] ([0x0-0xf00f].com.wacom.Consumer_TouchDriver[134]): Exited with exit code: 1
05:22:34 peruser.501[100] (com.wacom.pentablet[126]): Exited with exit code: 1[/color]
[color="#2E8B57"]14:18:31 peruser.501[100] (com.apple.ReportCrash): Falling back to default Mach exception handler. 
Could not find: com.apple.ReportCrash.Self
14:18:33 peruser.501[100] (com.apple.Kerberos.renew.plist[122]): Exited with exit code: 1[/color]

 

Last boot:

bootlog[63]: BOOT_TIME: 1260623886 0

 

My kernel.log in 64bit is this now:

Dec 12 14:18:12 localhost kernel[0]: npvhash=4095
Dec 12 14:18:12 localhost kernel[0]: Darwin Kernel Version 10.2.0: 
Tue Nov  3 10:35:19 PST 2009; root:xnu-1486.2.11~1/RELEASE_X86_64
Dec 12 14:18:12 localhost kernel[0]: vm_page_bootstrap: 1982162 free pages and 114990 wired pages
[color="#FF0000"]Dec 12 14:18:12 localhost kernel[0]: kext submap [0xffffff7f80600000 - 0xffffff8000000000], 
kernel text [0xffffff8000200000 - 0xffffff8000600000][/color]
Dec 12 14:18:12 localhost kernel[0]: standard timeslicing quantum is 10000 us
Dec 12 14:18:12 localhost kernel[0]: mig_table_max_displ = 73
Dec 12 14:18:12 localhost kernel[0]: AppleACPICPU: ProcessorId=1 LocalApicId=0 Enabled
Dec 12 14:18:12 localhost kernel[0]: AppleACPICPU: ProcessorId=2 LocalApicId=1 Enabled
Dec 12 14:18:12 localhost kernel[0]: AppleACPICPU: ProcessorId=3 LocalApicId=130 Disabled
Dec 12 14:18:12 localhost kernel[0]: AppleACPICPU: ProcessorId=4 LocalApicId=131 Disabled
Dec 12 14:18:12 localhost kernel[0]: calling mpo_policy_init for Quarantine
Dec 12 14:18:12 localhost kernel[0]: Security policy loaded: Quarantine policy (Quarantine)
Dec 12 14:18:12 localhost kernel[0]: calling mpo_policy_init for Sandbox
Dec 12 14:18:12 localhost kernel[0]: Security policy loaded: Seatbelt sandbox policy (Sandbox)
Dec 12 14:18:12 localhost kernel[0]: calling mpo_policy_init for TMSafetyNet
Dec 12 14:18:12 localhost kernel[0]: Security policy loaded: Safety net for Time Machine (TMSafetyNet)
Dec 12 14:18:12 localhost kernel[0]: Copyright © 1982, 1986, 1989, 1991, 1993
Dec 12 14:18:12 localhost kernel[0]: The Regents of the University of California. All rights reserved.
Dec 12 14:18:12 localhost kernel[0]: MAC Framework successfully initialized
Dec 12 14:18:12 localhost kernel[0]: using 16384 buffer headers and 4096 cluster IO buffer headers
Dec 12 14:18:12 localhost kernel[0]: IOAPIC: Version 0x20 Vectors 64:87
Dec 12 14:18:12 localhost kernel[0]: ACPI: System State [s0 S3 S4 S5] (S3)
Dec 12 14:18:12 localhost kernel[0]: netkas presents fakesmc, a kext which emulates smc device
Dec 12 14:18:12 localhost kernel[0]: RTC: Only single RAM bank (128 bytes)
Dec 12 14:18:12 localhost kernel[0]: mbinit: done (96 MB memory set for mbuf pool)
Dec 12 14:18:12 localhost kernel[0]: From path: "uuid", 
Dec 12 14:18:12 localhost kernel[0]: Waiting for boot volume with UUID 697C30BD-EE6E-32A4-B71C-789D54A2FD7A
Dec 12 14:18:12 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key><string 
ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
Dec 12 14:18:12 localhost kernel[0]: com.apple.AppleFSCompressionTypeZlib load succeeded
Dec 12 14:18:12 localhost kernel[0]: AppleIntelCPUPowerManagementClient: ready
Dec 12 14:18:12 localhost kernel[0]: JMicronATA: JMB363 (CMD 0xdc00, CTR 0xd880, IRQ 17, BM 0xd400)
Dec 12 14:18:12 localhost kernel[0]: JMicronATA: JMB363 (CMD 0xd800, CTR 0xd480, IRQ 17, BM 0xd408)
Dec 12 14:18:12 localhost kernel[0]: FireWire (OHCI) VendorID 1106 ID 3044 built-in now active, 
GUID 0011d800018fcabf; max speed s400.
Dec 12 14:18:12 localhost kernel[0]: Got boot device = IOService:/AppleACPIPlatformExpert/
PCI0@0/AppleACPIPCI/SATA@1F,2/AppleAHCI/PRT3@5/IOAHCIDevice@0/
AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageDriver/Maxtor
6Y120M0 Media/IOGUIDPartitionScheme/Snow Leo@2
Dec 12 14:18:12 localhost kernel[0]: BSD root: disk1s2, major 14, minor 6
Dec 12 14:18:12 localhost kernel[0]: Kernel is LP64
Dec 12 14:18:12 localhost kernel[0]: AppleIntelCPUPowerManagement: initialization complete
Dec 12 14:18:13 localhost kernel[0]: systemShutdown false
Dec 12 14:18:14 Mac-Pro-di-scrax kernel[0]: AttansicL1Ethernet(p5k) from markswell
Dec 12 14:18:15 Mac-Pro-di-scrax kernel[0]: Previous Shutdown Cause: 0
Dec 12 14:18:15 Mac-Pro-di-scrax kernel[0]: NVDANV50HAL loaded and registered.
Dec 12 14:18:15 Mac-Pro-di-scrax kernel[0]: [AttansicL1Ethernet] Error: Mac address through SPI is invalid
Dec 12 14:18:21 Mac-Pro-di-scrax kernel[0]: DSMOS has arrived
Dec 12 14:18:21 Mac-Pro-di-scrax kernel[0]: AttansicL1Ethernet: Ethernet address 00:1d:60:35:cd:78
Dec 12 14:18:38 

 

Note that i've no more error for audio, but i didn't make any change to audio. I've changed chameleon with RC4, removed PlatformUUID and added jmicron an VIAATA kext to see my IDE device that wasn't working without.

 

I ran into this when I started to add GFX data into my DSDT – I still had device properties in com.apple.Boot.plist which apparently wasn't a good idea.

Me too.

 

For the usb thing, thnaks for the explanations. Are the ICH9R ancd ICH9 datasheet the same? Probably not...

If somebody could help me to find the ICH9 datasheet that would be great...

Link to comment
Share on other sites

hello chief, i´ve got audio mic working in 10.6.2/64 bit with these kext.

 

it works but not as it should. behind wakeup the sound is quitly. posible you could insert it into your kext or dsdt.

Thanks, but I don't use a microphone and I have no plan to add anything anytime soon – other than FAN speed / MB temp maybe.

 

i have a please, could you please insert into your dsdt 2.4 my cpu (Package (0x06) { 2997, 80535, 10, 10, 0x921, 0x921 }) ? i does it wrong, because every second boot i get panic and without it is to slow. i use all your kext, without CPUi.kext and CPU injektor.kext.

I guess you meant DSDT V3.4 but more importantly; adding a _PSS object with valid values (invalid even) won't make your hack faster or slower. That's a false assumption.

 

And here's a tip: Start reading this thread because that might help you.

 

also iám not able to change my imac 8.1 into a mac pro or p5k-pro. could you please post your ioplatformfamily.kext ? it would be great if you could help me, thx in advance :thumbsup_anim:

My model identifier is still the default one being "P5K PRO", but you can easily change that with help of Chameleon. And I use the vanilla IOPlatformFamily.kext (10.6.2) with two legacy kexts available from one of the posts here.

 

...

Are the ICH9R ancd ICH9 datasheet the same? Probably not... If somebody could help me to find the ICH9 datasheet that would be great...

LOL What about checking the links in post #3? Get that ICH9 datasheet and read this:

 

"For the Intel® 82801IB ICH9, 82801IR ICH9R, 82801IH ICH9DH, 82801IO ICH9DO, 82801IBM ICH9M and 82801IEM ICH9M-E, and ICH9M-SFF ICH9-I/O Controller Hubs".

Link to comment
Share on other sites

Think about this: Why work this hard, to reduce the code size of one file – being our DSDT.aml – while other people keep adding bloat to your boot loader?

 

I've just find this: http://prasys.co.cc/2009/10/chameleon-rc3-...fi-10-3-extras/

It's a modder RC3 with some patch included in the last RC4 but without the GUI

(So for now i don't need to learn how to develop a boot loader anymore ;) )

Link to comment
Share on other sites

I've just find this: http://prasys.co.cc/2009/10/chameleon-rc3-...fi-10-3-extras/

It's a modder RC3 with some patch included in the last RC4 but without the GUI

(So for now i don't need to learn how to develop a boot loader anymore :unsure: )

If you don't want to bother with the Chameleon GUI, why not simply set GUI=No in /Extra/com.apple.Boot.plist?

<key>GUI</key>

<string>No</string>

 

Other options which I find useful are

 

Do not use quiet boot mode (displays progress messages for the curious among us).

"Quiet Boot"=No

<key>Quiet Boot</key>

<string>No</string>

 

Prompt for a key press before starting the kernel. (Allows you plenty of time to see those messages from "Quiet Boot"=No)

Wait=Yes

<key>Wait</key>

<string>Yes</string>

 

Force displaying the partition selection menu. (Hmmm. Wonder if I really need this if Wait=Yes is set?)

"Instant Menu"=Yes

<key>Instant Menu</key>

<string>Yes</string>

 

Use an alternate value for PciRoot. (default value: 0). (Only works in just released V2 RC4-r684)

PciRoot=1

<key>PciRoot</key>

<string>1</string>

 

-irrational john

Link to comment
Share on other sites

-irrational john

 

Thank's for the info.

I already use the "GUI NO" options but the size of the bootloader isn't affected and so the time to load it is the same. For this reason i'll try the one without GUI and hope it is faster ( the GUI one is 320.320 byte vs 140.440 byte of the other). Check post #551 for more info on that

Link to comment
Share on other sites

I can't figure out how to make ALC883 works using DSDT! Could anyone tell me how to modify DSDT? What do I have to do else?

with DSDT you just let your MacOS to "know" your hardware, as codec-id, pin-default, etc., but to let it sound you should feel up your AppleHDA.kext plug-ins with proper info.

like this (see attach) (based on kext from 10.6.0 but work in 10.6.2 also)

and in DSDT should be something like this:

Device (HDEF)
           {
               Name (_ADR, 0x001B0000)
               Name (_PRW, Package (0x02)
               {
                   0x0D, 
                   0x06
               })
               OperationRegion (HDCS, PCI_Config, 0x54, 0x04)
               Field (HDCS, DWordAcc, NoLock, Preserve)
               {
                       ,   15, 
                   PMES,   1
               }

               [color="#ff0000"]Method (_DSM, 4, NotSerialized)
               {
                   Store (Package (0x0C)
                       {
                           "codec-id", 
                           Buffer (0x04)
                           {
                               0x83, 0x08, 0xEC, 0x10
                           }, 

                           "built-in", 
                           Buffer (One)
                           {
                               0x00
                           }, 

                           "model", 
                           Buffer (0x0F)
                           {
                               "Realtek ALC883"
                           }, 

                           "device_type", 
                           Buffer (0x07)
                           {
                               "alc883"
                           }, 

                           "layout-id", 
                           Buffer (0x04)
                           {
                               0x0C, 0x00, 0x00, 0x00
                           }, 

                           "PinConfigurations", 
                           Buffer (One)
                           {
                               0x00
                           }[/color]
                       }, Local0)
                   MCDP (Arg2, RefOf (Local0))
                   Return (Local0)
               }
           }

AppleHDA.kext.zip

Link to comment
Share on other sites

I can't figure out how to make ALC883 works using DSDT! Could anyone tell me how to modify DSDT? What do I have to do else?

Who said that this is even possible?

 

Note: Getting the on-board ALC883 to work without a legacy / modified kext requires a modified BIOS ROM.

 

p.s. I am going to experiment with eeupdate.exe (Intel firmware dump/update program for LAN) and start by using /DUMP to get the data I want to change (hello new device-id).

Link to comment
Share on other sites

I still have a problem with my hack.

 

When the computer has shut down the USB ports get turned on so there's light in my Apple keyboard and MIDI keyboard. That results in problems when booting if I don't power off manually before boot.

 

I have applied Q6600 info from P-states calculator to DSDT v3.3.

 

Are there any solution to this and are there others experiencing the same?

Link to comment
Share on other sites

I still have a problem with my hack.

 

When the computer has shut down the USB ports get turned on so there's light in my Apple keyboard and MIDI keyboard. That results in problems when booting if I don't power off manually before boot.

 

I have applied Q6600 info from P-states calculator to DSDT v3.3.

 

Are there any solution to this and are there others experiencing the same?

Let's start by naming things: What Apple keyboard specifically (model number) and please do me a favor, and make a picture of the lights you are talking about. Thanks.

 

What DSDT are you using? I mean is that DSDT V3.3.1 or any of its predecessors, or your own? In case of the latter; please attach it. Thanks.

Link to comment
Share on other sites

 Share

×
×
  • Create New...