Jump to content

DSDT fixes for Gigabyte boards


iSoprano
 Share

1,908 posts in this topic

Recommended Posts

Anyone here using -pci1 in com.apple.Boot.plist or using rekursors PCI root port patch?

 

If yes; what do you get when you enter: sudo reggie_se -D PhysAddr -r -a 0xe0000000 -B 32

 

Note: This command requires Xcode!

 

p.s. Bonus points for the one adding a dump of his/her MCFG table.

 

Thank you.

Link to comment
Share on other sites

Anyone here using -pci1 in com.apple.Boot.plist or using rekursors PCI root port patch?

 

If yes; what do you get when you enter: sudo reggie_se -D PhysAddr -r -a 0xe0000000 -B 32

 

Note: This command requires Xcode!

 

p.s. Bonus points for the one adding a dump of his/her MCFG table.

 

Thank you.

 

sudo reggie_se -D PhysAddr -r -a 0xe0000000 -B 32

Password:

WARNING: Could not determine processor information.

WARNING: Could not determine memory controller information.

WARNING: Could not determine Operating System information.

. 4.7.2 (263)

Memory Address - 0x00000000e0000000 (local)

ERROR: unable to map address: x3758096384lx "Failure in I/O Kit (Are the kexts loaded?) (-10993)"

 

Oh my, what does this mean?

MCFG.aml.zip

Link to comment
Share on other sites

sudo reggie_se -D PhysAddr -r -a 0xe0000000 -B 32

Password:

WARNING: Could not determine processor information.

WARNING: Could not determine memory controller information.

WARNING: Could not determine Operating System information.

. 4.7.2 (263)

Memory Address - 0x00000000e0000000 (local)

ERROR: unable to map address: x3758096384lx "Failure in I/O Kit (Are the kexts loaded?) (-10993)"

 

Oh my, what does this mean?

 

Probably you are using 64-bit kernel ?

Link to comment
Share on other sites

Yes I kind of guessed that but I just did what the poster asked after checking what reggie_se did

 

ie what is the significance of the question

 

I mean you must boot with 32-bit kernel to use reggie_se, it uses some 32-bit only kext files. For me it doesn't work even with that but using 64-bit kernel you have no chance of running it.

Link to comment
Share on other sites

I mean you must boot with 32-bit kernel to use reggie_se, it uses some 32-bit only kext files. For me it doesn't work even with that but using 64-bit kernel you have no chance of running it.

 

OK this is what I get in 32 mode

 

sudo reggie_se -D PhysAddr -r -a 0xe0000000 -B 32
Password:
. 4.7.2 (263)
Memory Address - 0x00000000e0000000 (local)
Address 0xe0000000       0x55ffffff          |0 1 0 1|0 1 0 1|1 1 1 1|1 1 1 1|1 1 1 1|1 1 1 1|1 1 1 1|1 1 1 1|

 

so what does it mean?

Link to comment
Share on other sites

Anyone here using -pci1 in com.apple.Boot.plist or using rekursors PCI root port patch?

 

If yes; what do you get when you enter: sudo reggie_se -D PhysAddr -r -a 0xe0000000 -B 32

 

Note: This command requires Xcode!

 

p.s. Bonus points for the one adding a dump of his/her MCFG table.

 

Thank you.

 

. 4.7.2 (263)

Memory Address - 0x00000000e0000000 (local)

Address 0xe0000000 0x55ffffff |0 1 0 1|0 1 0 1|1 1 1 1|1 1 1 1|1 1 1 1|1 1 1 1|1 1 1 1|1 1 1 1|

 

MCFG.dsl.zip

Link to comment
Share on other sites

And here's what I get -

 

Last login: Sat Jan 2 09:43:12 on ttys000

Steves-Computer:~ Steve$ sudo reggie_se -D PhysAddr -r -a 0xe0000000 -B 32

Password:

. 4.7.2 (263)

Memory Address - 0x00000000e0000000 (local)

Address 0xe0000000 0x00bfbfbf |0 0 0 0|0 0 0 0|1 0 1 1|1 1 1 1|1 0 1 1|1 1 1 1|1 0 1 1|1 1 1 1|

 

 

/*
* Intel ACPI Component Architecture
* AML Disassembler version 20091112
*
* Disassembly of acpi_mcfg.bin, Sat Jan  2 10:24:02 2010
*
* ACPI Data Table [MCFG]
*
* Format: [HexOffset DecimalOffset ByteLength]  FieldName : FieldValue
*/

[000h 0000  4]                    Signature : "MCFG"    /* Memory Mapped Configuration table */
[004h 0004  4]                 Table Length : 0000003C
[008h 0008  1]                     Revision : 01
[009h 0009  1]                     Checksum : E4
[00Ah 0010  6]                       Oem ID : "GBT   "
[010h 0016  8]                 Oem Table ID : "GBTUACPI"
[018h 0024  4]                 Oem Revision : 42302E31
[01Ch 0028  4]              Asl Compiler ID : "GBTU"
[020h 0032  4]        Asl Compiler Revision : 01010101

[024h 0036  8]                     Reserved : 0000000000000000

[02Ch 0044  8]                 Base Address : 00000000F0000000
[034h 0052  2]         Segment Group Number : 0000
[036h 0054  1]             Start Bus Number : 00
[037h 0055  1]               End Bus Number : 3F
[038h 0056  4]                     Reserved : 00000000

Raw Table Data

 0000: 4D 43 46 47 3C 00 00 00 01 E4 47 42 54 20 20 20  MCFG<.....GBT   
 0010: 47 42 54 55 41 43 50 49 31 2E 30 42 47 42 54 55  GBTUACPI1.0BGBTU
 0020: 01 01 01 01 00 00 00 00 00 00 00 00 00 00 00 F0  ................
 0030: 00 00 00 00 00 00 00 3F 00 00 00 00              .......?....

 

Chief - if you need anything else let me know.

 

 

Regards,

SMF

Link to comment
Share on other sites

Here my EP35-DS3 , OS X 10.5 , 4 GB

GA_EP35:~ ami$ sudo reggie_se -D PhysAddr -r -a 0xe0000000 -B 32

....

Memory Address - 0x00000000e0000000 (local)

Address 0xe0000000 0x5afdfdfd |0 1 0 1|1 0 1 0|1 1 1 1|1 1 0 1|1 1 1 1|1 1 0 1|1 1 1 1|1 1 0 1|

GA_EP35:~ ami$

[000h 0000  4] Signature : "[b]MCFG[/b]"    /* Memory Mapped Configuration table */
[004h 0004  4]                 Table Length : 0000003C
[008h 0008  1]                     Revision : 01
[009h 0009  1]                     Checksum : E4
[00Ah 0010  6]                       Oem ID : "GBT   "
[010h 0016  8]                 Oem Table ID : "GBTUACPI"
[018h 0024  4]                 Oem Revision : 42302E31
[01Ch 0028  4]              Asl Compiler ID : "GBTU"
[020h 0032  4]        Asl Compiler Revision : 01010101

[024h 0036  8]                     Reserved : 0000000000000000

[02Ch 0044  8]                 Base Address : 00000000F0000000
[034h 0052  2]         Segment Group Number : 0000
[036h 0054  1]             Start Bus Number : 00
[037h 0055  1]               End Bus Number : 3F
[038h 0056  4]                     Reserved : 00000000

Link to comment
Share on other sites

It's actually easy to check if C4 works, run this : sudo setpci -s 0:1f.0 0xa6.b

 

If bit 7 of result is set then CPU has gone to a C-state deeper than C2 at least once. My result with working C4 is 80

More information about that register can be found on ICH10 datasheet page 455.

 

I get '00'

Link to comment
Share on other sites

It's like you said I have a processor that doesn't support C2 & C4 so I never saw those options. I used the same processor in both boards. The EP35-DS4 board is retired (anyone want to buy it?).

 

Update: I just flipped through the P35 manual and didn't see the C2 & C4 options. However I do see those options in my P45 manual. So I guess there's no support… that sucks. I wonder if they might have added it in a later BIOS update.

 

The Q9450 only supports C1E @ 12 and 16W ..

 

"12.These parts have Extended HALT State (C1E) enabled

13.These parts have Extended HALT (C1E) power of 16W

14.These parts have Extended HALT (C1E) power of 12W"

 

Maybe these two C1E states should be defined?

 

**EDIT** or is that C1 and C2?

 

D.

Link to comment
Share on other sites

The Q9450 only supports C1E @ 12 and 16W ..

 

"12.These parts have Extended HALT State (C1E) enabled

13.These parts have Extended HALT (C1E) power of 16W

14.These parts have Extended HALT (C1E) power of 12W"

 

Maybe these two C1E states should be defined?

 

D.

 

In that case you should define your CST like this:

		Method (CST, 0, NotSerialized)
	{
		Return (Package (0x02)
		{
			0x1, 
			Package (0x4){ResourceTemplate (){Register (FFixedHW,0x01,0x02,0x00,,)},One,One,0x3E8} 
		})
	}

 

What datasheet are you referring to ?

 

/edit

 

Ok, found the sheet. You should use this CST table, you only have C1E

Link to comment
Share on other sites

Could not using Zero's in the PR Scope PSS method cause system instability? I have

 

Package (0x06) { 2394, 53405, 10, 10, 0x923, Zero },

Package (0x06) { 2128, 46868, 10, 10, 0x822, One },

Package (0x06) { 1862, 39955, 10, 10, 0x720, 0x02 },

Package (0x06) { 1596, 33343, 10, 10, 0x61E, 0x03 }

 

I just now noticed everyone else has Zero's in place of bold numbers, every 2 days or so I get a lockup.. always while I'm gaming (only thing I do that really uses much of cpu), but I never had this while I was using NullCPUPM

Link to comment
Share on other sites

Could not using Zero's in the PR Scope PSS method cause system instability? I have

 

Package (0x06) { 2394, 53405, 10, 10, 0x923, Zero },

Package (0x06) { 2128, 46868, 10, 10, 0x822, One },

Package (0x06) { 1862, 39955, 10, 10, 0x720, 0x02 },

Package (0x06) { 1596, 33343, 10, 10, 0x61E, 0x03 }

 

I just now noticed everyone else has Zero's in place of bold numbers, every 2 days or so I get a lockup.. always while I'm gaming (only thing I do that really uses much of cpu), but I never had this while I was using NullCPUPM

 

I also see that you are running your cpu at 3 GHz, I don't see how it could possibly help you to define P0 state as 2394 when you are really using 3000.

Link to comment
Share on other sites

Yup 266 with x9

 

Have you tried letting CPUTest.app run for some time, maybe you have some cooling issues ? And how about reggie_se, I still haven't seen anyone using P45 successful with it.

Link to comment
Share on other sites

In that case you should define your CST like this:

		Method (CST, 0, NotSerialized)
	{
		Return (Package (0x02)
		{
			0x1, 
			Package (0x4){ResourceTemplate (){Register (FFixedHW,0x01,0x02,0x00,,)},One,One,0x3E8} 
		})
	}

 

What datasheet are you referring to ?

 

/edit

 

Ok, found the sheet. You should use this CST table, you only have C1E

 

As per kdawg ... post 1240 qui !

 

But that only defines C1 .. ?! not C1E at 2 possible power states 12W and 16W

 

 

EDIT**

something like: DONT USE!

 Method (CST, 0, NotSerialized)
{
Return (Package (0x03)
{
0x2,
Package (0x4){ResourceTemplate (){Register (FFixedHW,0x01,0x02,0x00,,)},One,One,0x3E8,1600},
Package (0x4){ResourceTemplate (){Register (FFixedHW,0x01,0x02,0x00,,)},One,One,0x3E8,1200}
})
}

 

D

Link to comment
Share on other sites

My temps are really cool, (tested on both Windows and OSX (CPU-i)) I idle at around 30-32C and on load I'm at around 42-45C. Way below max thermal spec.

 

I'll try reggie_se next time I reboot, I boot into 64-bit by default.

 

Will try CPUTest. So those numbers I posted earlier couldn't be causing my problem?

 

edit: ran cputest for about 10mins, went through 160 tests, 0 failed, and temps never went above 50C, definitely not a cooling problem

Link to comment
Share on other sites

 Share

×
×
  • Create New...