DSDT fixes for Gigabyte boards

Aargh-a-Knot · January 3, 2010

Ask you guys, is it possible to use DSDT.aml file on OS X 10.5.8?

Yes, I can boot into leo with mine.

xjasx · January 3, 2010

Checked my log aswell, all of my NOOPs revolve around networking/airport (I don't even use wireless, or have a wireless card)

* Domain: applicationresponse.slowresponse
- Message: PMConnection AirPort configd plug-in com.apple.powermanagement.applicationresponse.slowresponse 3907 ms
- Time: 12/26/09 9:17:15 AM PST 
- Signature: AirPort configd plug-in
- UUID: C40AA677-A579-42B6-8560-A7D5C847001B
- Result: Noop
- Response time (ms): 3907

* Domain: applicationresponse.slowresponse
- Message: PMConnection IPConfiguration com.apple.powermanagement.applicationresponse.slowresponse 3908 ms
- Time: 12/26/09 9:17:15 AM PST 
- Signature: IPConfiguration
- UUID: C40AA677-A579-42B6-8560-A7D5C847001B
- Result: Noop
- Response time (ms): 3908

Johnny V · January 3, 2010

My last DSDT had a problem, in red, but temps were running 49-50C:

  Scope (_PR.CPU0)
   {
       Method (_PSS, 0, NotSerialized)
       {
           Return (Package (0x05)
           {
               Package (0x06)
               {
                   Zero, 
                   Zero, 
                   0x10, 
                   0x10, 
                   0x0A24, 
                   Zero
               }, 

               Package (0x06)
               {
                   Zero, 
                   Zero, 
                   0x10, 
                   0x10, 
                   0x0922, 
                   One
               }, 

               Package (0x06)
               {
                   Zero, 
                   Zero, 
                   0x10, 
                   0x10, 
                   0x0820, 
                   0x02
                }, 

               Package (0x06)
               {
                   Zero, 
                   Zero, 
                   0x10, 
                   0x10, 
                   0x071E, 
                   [color="#FF0000"]One[/color]
               }, 

               Package (0x06)
               {
                   Zero, 
                   Zero, 
                   0x10, 
                   0x10, 
                   0x061B, 
                   [color="#FF0000"]0x02[/color]    
               }

I fixed the above in RED and my temps jumped 8 degrees hotter. Not sure what's my next step. I could take out 3 and 4 but I don't think that's the way to go.

I have these in my Extra folder:

fakesmc.kext
LegacyHDA.kext
OrangeIconFix.kext
OSXRestart.kext

Other than the higher temps everything else seems to be working.

snackole · January 3, 2010

Try making look a little more like this.

Scope (_PR)

{

Name (PSS, Package (0x02)

{

Package (0x06)

{

Zero,

0x0A,

0x072A,

Zero

},

Package (0x06)

{

Zero,

0x0A,

0x061D,

One

}

})

Make sure to change 72A and 61D to your own values and add any others you might have. You need to define the amount of pstates here Name (PSS, Package (0x02)

mm67 · January 3, 2010

These are my results. C2:C4 is about 50:50.

Only C1E enabled

    PowerTOP version 1.11      © 2007 Intel Corporation

Cn                Avg residency       P-states (frequencies)
C0 (cpu running)        ( 0.8%)         2.67 Ghz   100.0%
polling           0.0ms ( 0.0%)         2.00 Ghz     0.0%
C1               14.3ms (99.2%)



Wakeups-from-idle per second : 69.2     interval: 5.0s
no ACPI power usage estimate available

Top causes for wakeups:
 29.1% ( 60.0)       <interrupt> : fglrx[0]@PCI:1:0:0 
 27.1% ( 55.8)     <kernel core> : hrtimer_start_range_ns (tick_sched_timer) 
 12.3% ( 25.4)      <kernel IPI> : Rescheduling interrupts 
  8.3% ( 17.2)     <kernel core> : hrtimer_start (tick_sched_timer) 
  5.3% ( 11.0)     <kernel core> : timer_action (ehci_watchdog) 
  4.1% (  8.4)      <kernel IPI> : TLB shootdowns

Suggestion: Enable SATA ALPM link power management via:
 echo min_power > /sys/class/scsi_host/host0/link_power_management_policy
or press the S key.
Q - Quit   R - Refresh   S - SATA Link Power Management 

C1E & C2E enabled

    PowerTOP version 1.11      © 2007 Intel Corporation

Cn                Avg residency       P-states (frequencies)
C0 (cpu running)        ( 0.6%)         2.67 Ghz     0.0%
polling           0.0ms ( 0.0%)         2.00 Ghz   100.0%
C1 halt           0.0ms ( 0.0%)
C2                5.7ms (99.4%)


Wakeups-from-idle per second : 175.5    interval: 4.1s
no ACPI power usage estimate available

Top causes for wakeups:
 18.9% ( 69.8)   USB device 1-5.3 : Apple Optical USB Mouse (Fujitsu Takamisawa
 17.2% ( 63.5)      <kernel IPI> : Rescheduling interrupts 
 16.5% ( 61.0)       <interrupt> : fglrx[0]@PCI:1:0:0 
 16.3% ( 60.2)       <interrupt> : extra timer interrupt 
  8.1% ( 30.0)     <kernel core> : hrtimer_start_range_ns (tick_sched_timer) 
  5.5% ( 20.5)       <interrupt> : ehci_hcd:usb1, uhci_hcd:usb5, uhci_hcd:usb8,
ohci1394 



Q - Quit   R - Refresh  

C1E, C2E & C4E enabled.

    PowerTOP version 1.11      © 2007 Intel Corporation

Cn                Avg residency       P-states (frequencies)
C0 (cpu running)        ( 0.3%)         2.67 Ghz     0.0%
polling           0.0ms ( 0.0%)         2.00 Ghz   100.0%
C1 halt           0.0ms ( 0.0%)
C2                4.9ms (46.7%)
C3                7.8ms (53.0%)

Wakeups-from-idle per second : 163.4    interval: 1.1s
no ACPI power usage estimate available

Top causes for wakeups:
 31.2% (140.0)   USB device 1-5.3 : Apple Optical USB Mouse (Fujitsu Takamisawa
 15.4% ( 69.0)       <interrupt> : fglrx[0]@PCI:1:0:0 
 14.1% ( 63.0)       <interrupt> : extra timer interrupt 
  9.2% ( 41.0)      <kernel IPI> : Rescheduling interrupts 
  8.5% ( 38.0)     <kernel core> : hrtimer_start_range_ns (tick_sched_timer) 
  6.0% ( 27.0)     <kernel core> : hrtimer_start (tick_sched_timer) 




Q - Quit   R - Refresh

Did you also monitor temperatures while doing those tests. I couldn't see any changes in temps if I was using 1,2 or 3 C-states. Or did you see any changes in power usage ?

rayap · January 3, 2010

Did you also monitor temperatures while doing those tests. I couldn't see any changes in temps if I was using 1,2 or 3 C-states. Or did you see any changes in power usage ?

Four minutes run for each C-State, temps and power usage all practically consistent (±1 ºC or Watt) tilting marginally lower for higher C-States.

mm67 · January 3, 2010

Four minutes run for each C-State, temps and power usage all practically consistent (±1 ºC or Watt) tilting marginally lower for higher C-States.

I just repeated similar tests on Windows and results are the same, no notable changes in temperatures using any of the C-state options. I still wonder what breaks C4 for me, C2:C4 usage was almost the same on Windows.

Common Sense · January 3, 2010

Great find!

I have the following in my log:

* Domain: applicationresponse.slowresponse

- Message: PMConnection AirPort configd plug-in com.apple.powermanagement.applicationresponse.slowresponse 5877 ms

- Time: 2009-12-22 04.16.18 GMT+08.00

- Signature: AirPort configd plug-in

- UUID: 42706A3A-27C9-4404-9901-E8BE5AF89DD8

- Result: Noop

- Response time (ms): 5877

* Domain: applicationresponse.slowresponse

- Message: PMConnection IPConfiguration com.apple.powermanagement.applicationresponse.slowresponse 5877 ms

- Time: 2009-12-22 04.16.18 GMT+08.00

- Signature: IPConfiguration

- UUID: 42706A3A-27C9-4404-9901-E8BE5AF89DD8

- Result: Noop

- Response time (ms): 587

any idea what the first one could be? The last one can be the remains of iStats?

Did you previously have iStats installed? If so try reinstalling it then using the uninstall script again. There were remnants that the uninstaller script didn't get the firt time around for me.

Use
pmset -g log
to view pmset entries.

Entries like this are problems. They may not tell you exactly what the problem is but it might help you track them down.
 * Domain: applicationresponse.slowresponse
 - Message: PMConnection IPConfiguration com.apple.powermanagement.applicationresponse.slowresponse 2990 ms
 - Time: 1/3/10 10:15:17 AM EST 
 - Signature: IPConfiguration
 - UUID: FBD38D98-62A3-4B17-84D7-0F63A1991621
 - Result: Noop
 - Response time (ms): 2990

Johnny V · January 3, 2010

Try making look a little more like this.

Scope (_PR)

{

Name (PSS, Package (0x02)

{

Package (0x06)

{

Zero,

Zero,

0x0A,

0x0A,

0x072A,

Zero

},

Package (0x06)

{

Zero,

Zero,

0x0A,

0x0A,

0x061D,

One

}

})

Make sure to change 72A and 61D to your own values and add any others you might have. You need to define the amount of pstates here Name (PSS, Package (0x02)

Thanks snackole!

Followed your example above and changed pstates to 5 (PSS, Package (0x05) But when I try to compile I get this iASLme error:

Intel ACPI Component Architecture
ASL Optimizing Compiler version 20091214 [Dec 16 2009]
Copyright © 2000 - 2009 Intel Corporation
Supports ACPI Specification Revision 4.0

/Users/jv/Desktop/dsdt.dsl   122:     Scope            Notify (\_SB.PWRB, 0x02)
Error    4096 -                                 ^ syntax error, unexpected PARSEOP_SCOPE, expecting $end


Elapsed time for major events


Miscellaneous compile statistics

       121 : Parse nodes
         9 : Namespace searches
        10 : Named objects
         2 : Control methods
        10 : Memory Allocations
    188742 : Total allocated memory
         0 : Constant subtrees folded

ASL Input:  /Users/jv/Desktop/dsdt.dsl - 1596 lines, 51520 bytes, 12 keywords
Compilation complete. 1 Errors, 0 Warnings, 0 Remarks, 0 Optimizations

Thanks again.

snackole · January 3, 2010

Upload what your working with and I'll take a look.

keeza · January 3, 2010

I just did some testing on Ubuntu using different C - state settings.
If I understand those results correctly using C4 is totally pointless since cpu spends 98.2 % of it's time in C2 anyway even if C4 is enabled. What do you think ?

Depends on how that result was calculated.

Does that result of 98.2% relate to overall CPU usage or is it a result of the CPU usage at the time of your testing?

Would it make a difference to my result if I boot off a live CD instead of having it installed? (i.e. my FF result in Ubuntu).

We've come a long way in getting cstates to work - we need some sort of benchmark of acceptable cstate performance, just having cstinfo in ioreg and cooler temps I think just tells us we have C1 (or is it C2) working. We need to be able to check the status of those deeper cstates (for those who have processor support for them of course).

Johnny V · January 3, 2010

Upload what your working with and I'll take a look.

Thanks I appreciate it!

dsdt.dsl.zip

snackole · January 3, 2010

Try with this. If anything is missing you'll have to add it back.

dsdt.aml.zip

Johnny V · January 4, 2010

Try with this. If anything is missing you'll have to add it back.

Thanks snackole!

Temps are lowered to around 50-52C... that's about where I started. PStateChanger is reporting all states values, mV and VID are 1275 and 24 respectively.

Not sure why the values are pegged all the same? Is it just my setup or is there a conflict somewhere?

Thanks!

SunKi · January 4, 2010

Meaning that you now have working C-states, congratulations.

After I made _CST method FFixedHW setpci-s 0:1 f.0 0xa6.b now returns 80. The temperature dropped by 2-3 degrees.

But the trouble began. If you care to sleep the computer you want to double-click button. The first time he goes into a state where the fans are working. In the second he goes into full sleep.

It comes back from sleep normally.

Do you have such problems?

leslieking · January 4, 2010

I read almost the whole thread...

There is no information about:

Name (FLAG, Zero)
Name (STAT, Zero)

Can I remove FLAG, and STAT?

Also, I have this code:

OperationRegion (SMOD, SystemMemory, 0x000FF840, One)
   Field (SMOD, ByteAcc, NoLock, Preserve)
   {
           ,   7, 
       SUSF,   1
   }

   OperationRegion (DEBG, SystemIO, 0x80, One)
   Field (DEBG, ByteAcc, NoLock, Preserve)
   {
       DBG1,   8
   }

   OperationRegion (RCRB, SystemMemory, 0xFED1C000, 0x4000)
   Field (RCRB, DWordAcc, Lock, Preserve)
   {
               Offset (0x3404), 
           ,   7, 
       HPTF,   1
   }

   OperationRegion (ELKM, SystemMemory, 0x000FFFEA, One)
   Field (ELKM, ByteAcc, NoLock, Preserve)
   {
           ,   1, 
           ,   1, 
       ELSO,   1, 
           ,   1, 
           ,   1, 
           ,   1, 
           ,   1
   }

   OperationRegion (EXTM, SystemMemory, 0x000FF830, 0x10)
   Field (EXTM, WordAcc, NoLock, Preserve)
   {
       ROM1,   16, 
       RMS1,   16, 
       ROM2,   16, 
       RMS2,   16, 
       ROM3,   16, 
       RMS3,   16, 
       AMEM,   32
   }

   OperationRegion (SMIC, SystemIO, 0xB2, One)
   Field (SMIC, ByteAcc, NoLock, Preserve)
   {
       SCP,    8
   }

   OperationRegion (GP2C, SystemIO, 0x042C, 0x02)
   Field (GP2C, ByteAcc, NoLock, Preserve)
   {
       G2C1,   8, 
       G2C2,   8
   }

   OperationRegion (GBLE, SystemIO, 0x0421, One)
   Field (GBLE, ByteAcc, NoLock, Preserve)
   {
       ESMI,   8
   }

   OperationRegion (APMP, SystemIO, 0xB2, 0x02)
   Field (APMP, ByteAcc, NoLock, Preserve)
   {
       APMC,   8, 
       APMD,   8
   }

   OperationRegion (AGPS, SystemIO, 0x0438, 0x04)
   Field (AGPS, ByteAcc, NoLock, Preserve)
   {
       GPSE,   16, 
       GPSS,   16
   }

   OperationRegion (GPCN, SystemIO, 0x0442, One)
   Field (GPCN, ByteAcc, NoLock, Preserve)
   {
           ,   1, 
       SWGC,   1, 
               Offset (0x01)
   }

   OperationRegion (INFO, SystemMemory, 0x000FF840, 0x02)
   Field (INFO, ByteAcc, NoLock, Preserve)
   {
       KBDI,   1, 
       RTCW,   1, 
       PS2F,   1, 
       IRFL,   2, 
       DISE,   1, 
       SSHU,   1
   }

Can I remove SMOD, RCRV, ELKM, SMIC, GP2C, GBLE, APMP, APGS, GPCN, and INFO ?

@masterchief noticed SMIC and APMP on page #5 but nothing more..

I would be grateful for any help! Thank you!

mm67 · January 4, 2010

After I made _CST method FFixedHW setpci-s 0:1 f.0 0xa6.b now returns 80. The temperature dropped by 2-3 degrees.
But the trouble began. If you care to sleep the computer you want to double-click button. The first time he goes into a state where the fans are working. In the second he goes into full sleep.

It comes back from sleep normally.

Do you have such problems?

I did have something similar with one version of scope PR, care to post what yours looks like ?

Depends on how that result was calculated.
Does that result of 98.2% relate to overall CPU usage or is it a result of the CPU usage at the time of your testing?

Would it make a difference to my result if I boot off a live CD instead of having it installed? (i.e. my FF result in Ubuntu).

We've come a long way in getting cstates to work - we need some sort of benchmark of acceptable cstate performance, just having cstinfo in ioreg and cooler temps I think just tells us we have C1 (or is it C2) working. We need to be able to check the status of those deeper cstates (for those who have processor support for them of course).

I believe that Powertop calculates the results only from the time it is running, and my system was idle the whole time during the test run. I don't think it matters if you boot from hard disk or cd, results should still be the same. The interesting thing is that my MSI board had just about opposite result on C2:C4 levels, 98 % of time was spent in C4. Clearly something is breaking C4 on my Gigabyte board.

Tool like Powertop would really be handy for OS X, now we are mostly just guessing what is happening.

SunKi · January 4, 2010

I did have something similar with one version of scope PR, care to post what yours looks like ?

It looks like my processor scope:

	Scope (_PR)
{
	Processor (CPU0, 0x00, 0x00000410, 0x06)
	{ 
/*			Name (_CST, Package (0x04) 
		{
			 0x03,
			 Package (0x04) {ResourceTemplate () {Register (FFixedHW, 1, 2, 0x0000, 2,)},0x01,0x01,0x03E8},
			 Package (0x04) {ResourceTemplate () {Register (SystemIO, 8, 0, 0x0414,,)},0x02,0x01,0x01F4},
			 Package (0x04) {ResourceTemplate () {Register (SystemIO, 8, 0, 0x0416,,)},0x04,0x55,0xFA}
		}) */
		Name (_CST, Package (0x04) 
		{
			0x3,
			Package (0x4){ResourceTemplate (){Register (FFixedHW,0x01,0x02,0x000,0x0,)},One,One,0x3E8},
			Package (0x4){ResourceTemplate (){Register (FFixedHW,0x01,0x02,0x010,0x1,)},0x2,One,0x1F4}
			Package (0x4){ResourceTemplate (){Register (FFixedHW,0x01,0x02,0x030,0x3,)},0x4,0x39,0x064}
		})
		Name (_PSD, Package (0x05) {0x05, Zero, Zero, 0xFC, 0x02})
		Name (_PCT, Package (0x02)
		{
			 ResourceTemplate () { Register (FFixedHW, 0x10, 0x00, 0x0000000000000199, ,) }, 
			 ResourceTemplate () { Register (FFixedHW, 0x10, 0x00, 0x0000000000000198, ,) }
		})
		Name (_PSS, Package ()
		{
			Package (0x06) { 3600, 64688, 10, 10, 0x921, 0x921 },
			Package (0x06) { 3200, 56021, 10, 10, 0x81E, 0x81E },
			Package (0x06) { 2800, 46430, 10, 10, 0x71A, 0x71A },
			Package (0x06) { 2400, 37578, 10, 10, 0x613, 0x613 }
		})
		Name (_PPC, Zero)
	}
	Processor (CPU1, 0x01, 0x00000410, 0x06) 
	{
/*			Name (_CST, Package (0x04) 
		{
			0x3,
			Package (0x4){ResourceTemplate (){Register (FFixedHW,0x01,0x02,0x000,0x0,)},One,One,0x3E8},
			Package (0x4){ResourceTemplate (){Register (FFixedHW,0x01,0x02,0x010,0x1,)},0x2,One,0x1F4},
			Package (0x4){ResourceTemplate (){Register (FFixedHW,0x01,0x02,0x030,0x3,)},0x4,0x55,0x0FA}
		}) */
		Alias (\_PR.CPU0._CST, _CST)
		Alias (\_PR.CPU0._PSD, _PSD)
		Alias (\_PR.CPU0._PCT, _PCT)
		Alias (\_PR.CPU0._PPC, _PPC)
	}
	Processor (CPU2, 0x02, 0x00000410, 0x06)
	{
		Alias (\_PR.CPU0._CST, _CST)
		Alias (\_PR.CPU0._PSD, _PSD)
		Alias (\_PR.CPU0._PCT, _PCT)
		Alias (\_PR.CPU0._PPC, _PPC)
	}
	Processor (CPU3, 0x03, 0x00000410, 0x06)
	{
		Alias (\_PR.CPU0._CST, _CST)
		Alias (\_PR.CPU0._PSD, _PSD)
		Alias (\_PR.CPU0._PCT, _PCT)
		Alias (\_PR.CPU0._PPC, _PPC)
	}
}

mm67 · January 4, 2010

It looks like my processor scope:

	Scope (_PR)
{
	Processor (CPU0, 0x00, 0x00000410, 0x06)
	{ 
/*			Name (_CST, Package (0x04) 
		{
			 0x03,
			 Package (0x04) {ResourceTemplate () {Register (FFixedHW, 1, 2, 0x0000, 2,)},0x01,0x01,0x03E8},
			 Package (0x04) {ResourceTemplate () {Register (SystemIO, 8, 0, 0x0414,,)},0x02,0x01,0x01F4},
			 Package (0x04) {ResourceTemplate () {Register (SystemIO, 8, 0, 0x0416,,)},0x04,0x55,0xFA}
		}) */
		Name (_CST, Package (0x04) 
		{
			0x3,
			Package (0x4){ResourceTemplate (){Register (FFixedHW,0x01,0x02,0x000,0x0,)},One,One,0x3E8},
			Package (0x4){ResourceTemplate (){Register (FFixedHW,0x01,0x02,0x010,0x1,)},0x2,One,0x1F4}
			Package (0x4){ResourceTemplate (){Register (FFixedHW,0x01,0x02,0x030,0x3,)},0x4,0x39,0x064}
		})
		Name (_PSD, Package (0x05) {0x05, Zero, Zero, 0xFC, 0x02})
		Name (_PCT, Package (0x02)
		{
			 ResourceTemplate () { Register (FFixedHW, 0x10, 0x00, 0x0000000000000199, ,) }, 
			 ResourceTemplate () { Register (FFixedHW, 0x10, 0x00, 0x0000000000000198, ,) }
		})
		Name (_PSS, Package ()
		{
			Package (0x06) { 3600, 64688, 10, 10, 0x921, 0x921 },
			Package (0x06) { 3200, 56021, 10, 10, 0x81E, 0x81E },
			Package (0x06) { 2800, 46430, 10, 10, 0x71A, 0x71A },
			Package (0x06) { 2400, 37578, 10, 10, 0x613, 0x613 }
		})
		Name (_PPC, Zero)
	}
	Processor (CPU1, 0x01, 0x00000410, 0x06) 
	{
/*			Name (_CST, Package (0x04) 
		{
			0x3,
			Package (0x4){ResourceTemplate (){Register (FFixedHW,0x01,0x02,0x000,0x0,)},One,One,0x3E8},
			Package (0x4){ResourceTemplate (){Register (FFixedHW,0x01,0x02,0x010,0x1,)},0x2,One,0x1F4},
			Package (0x4){ResourceTemplate (){Register (FFixedHW,0x01,0x02,0x030,0x3,)},0x4,0x55,0x0FA}
		}) */
		Alias (\_PR.CPU0._CST, _CST)
		Alias (\_PR.CPU0._PSD, _PSD)
		Alias (\_PR.CPU0._PCT, _PCT)
		Alias (\_PR.CPU0._PPC, _PPC)
	}
	Processor (CPU2, 0x02, 0x00000410, 0x06)
	{
		Alias (\_PR.CPU0._CST, _CST)
		Alias (\_PR.CPU0._PSD, _PSD)
		Alias (\_PR.CPU0._PCT, _PCT)
		Alias (\_PR.CPU0._PPC, _PPC)
	}
	Processor (CPU3, 0x03, 0x00000410, 0x06)
	{
		Alias (\_PR.CPU0._CST, _CST)
		Alias (\_PR.CPU0._PSD, _PSD)
		Alias (\_PR.CPU0._PCT, _PCT)
		Alias (\_PR.CPU0._PPC, _PPC)
	}
}

Try commenting out PPC and PCT, I'm not 100% sure but I think I was also experimenting with those when I had problems.

leslieking · January 4, 2010

Someone is able to help me with the code cleanup? Thanks!

greythorne · January 4, 2010

Try making look a little more like this.

Scope (_PR)

{

Name (PSS, Package (0x02)

{

Package (0x06)

{

Zero,

Zero,

0x0A,

0x0A,

0x072A,

Zero

},

Package (0x06)

{

Zero,

Zero,

0x0A,

0x0A,

0x061D,

One

}

})

Make sure to change 72A and 61D to your own values and add any others you might have. You need to define the amount of pstates here Name (PSS, Package (0x02)

Hi,

Saw in your signature that you are using 9600GT 512mb DDR3. I am basically using the same gfx card. Do you use graphics enabler fix in your com.boot.plist or you have the fix in your DSDT.aml file? Secondly what about audio, are you using an USB audio since you only have fakeSMC in your /E/E?

Thanks.

mm67 · January 4, 2010

Hi,

Saw in your signature that you are using 9600GT 512mb DDR3. I am basically using the same gfx card. Do you use graphics enabler fix in your com.boot.plist or you have the fix in your DSDT.aml file? Secondly what about audio, are you using an USB audio since you only have fakeSMC in your /E/E?

Thanks.

Yes, I use GraphicsEnabler option and I use USB audio

Someone is able to help me with the code cleanup? Thanks!

Yes, you can remove most of that stuff. You have to figure out what those do from ICH9 datasheet or just use someone else's dsdt as model

leslieking · January 4, 2010

@mm67 thanks, mate!

I have the EP35-DS4 dsdt as an example (kdawg dsdt).

There is no information about SMOD, DEBG in ICH9 datasheet.

SunKi · January 4, 2010

Try commenting out PPC and PCT, I'm not 100% sure but I think I was also experimenting with those when I had problems.

I tried to do it, but the problem remains: (

greythorne · January 4, 2010

zoliky,

Here you go.

Let me know if something is wrong.

DSDT fixes for Gigabyte boards

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites