Jump to content

DSDT fixes for Gigabyte boards

iSoprano

By iSoprano,
in Guides

 Share
1,909 posts in this topic

Recommended Posts

leslieking
leslieking
Posted
Posted

I have the same motherboard as iSoprano "EP35-DS3L", same bios "F6" and the same CPU "Q6600". His DSDT (which I presume is correct, check out the first thread) doesn't allow me to wake up using the aluminum keyboard.

I need to set someting in the computer BIOS?

Link to comment
Share on other sites
Master Chief
Master Chief
Posted
Posted
How do I do the aluminum keyboard fix on my ep45-ds3l? It only has one "Device (EHCI)" listed, and if I try to make it look like mm67's, and I add the INIT part to my "Device (LPCB)" I get 55 errors on compilation.

By removing the unwanted parts of it and using the correct device name? And last time I checked mm67's DSDT he was using this: 

    Scope (_SB)
   {
       Device (PWRB)
       {
           Name (_CID, EisaId ("PNP0C0C"))
           Method (_STA, 0, NotSerialized)
           {
               Return (0x0B)
           }
       }

	Method (_INI, 0, NotSerialized)
	{
		Store (0x01,\_SB.PCI0.EHC1.WRTA)
		Store (0x19, \_SB.PCI0.EHC1.PMES) 
		Store (0x00,\_SB.PCI0.EHC1.WRTA)

		Store (0x01,\_SB.PCI0.EHC2.WRTA)
		Store (0x19, \_SB.PCI0.EHC2.PMES) 
		Store (0x00,\_SB.PCI0.EHC2.WRTA)
	}

Not under LPCB, where it doesn't belong IMHO. But anyway. This should work: 

Method (_INI, 0, NotSerialized)
{
Store (0x01,\_SB.PCI0.EHCI.WRTA)
Store (0x19, \_SB.PCI0.EHCI.PMES) 
Store (0x00,\_SB.PCI0.EHCI.WRTA)
}

Easy. Not?

Link to comment
Share on other sites
blackosx
blackosx
Posted
Posted
How do I do the aluminum keyboard fix on my ep45-ds3l? It only has one "Device (EHCI)" listed, and if I try to make it look like mm67's, and I add the INIT part to my "Device (LPCB)" I get 55 errors on compilation.

Hi banini_jeque

 

Here's a revised version of mm67's DSDT for the EP45-DS3L that I am using if you want.

You can read about the changes that have been made here.

dsdt.dsl.zip

Link to comment
Share on other sites
Master Chief
Master Chief
Posted
Posted
Is this a motherboard specific patch? I have EP35-DS3L.

Patch is already applied, but aluminum keyboard wake-up doesn't work.

Just keyboard or mouse also?

 

And are you sure that the patch has been applied correctly? Have you checked the values of register 0x52-0x53? With and without the patch?

 

Enter lspci -nn in a terminal window to get the device id and then lspci -d [device:id] -xxxvvv

 

What's the value of registers 0x52 and 0x53?

 

p.s. Oh eh you are using a ICH9 based board. Correct? That might be why it isn't working for you...

Link to comment
Share on other sites
leslieking
leslieking
Posted
Posted
Just keyboard or mouse also?

 

And are you sure that the patch has been applied correctly? Have you checked the values of register 0x52-0x53? With and without the patch?

 

Enter lspci -nn in a terminal window to get the device id and then lspci -d [device:id] -xxxvvv

 

What's the value of registers 0x52 and 0x53?

 

p.s. Oh eh you are using a ICH9 based board. Correct? That might be why it isn't working for you...

Yes, ICH9. Is there a solution?

 

Just keyboard or mouse also?

Mouse wake-up works!

Thanks, mate! I will try the lspci -nn, but where can I get lspci?

Link to comment
Share on other sites
FKA
FKA
Posted
Posted
Here is a version I assembled for my GA-EP35-DS4. Give this a whirl. The only extra is my GFX1 card a 512MB 8800GT.

dsdt_EP35_DS4_FKA.dsl.zip

 

as we say in Scouse land - Ta La' - works for me!

:)

 

Now Master Jedi- I have an issue that I know effects others - I'm booting a SW RAID (sure this is issue generally) also, my drives keep switching around. mainly my boots are 1s3 and 2s3 (this in it's self is odd as my 2 RAID'd drives are 0 ans 1 in BIOS.) but sometimes I have 0s3 and 2s3 or 3s3 etc etc .. i believe IRQ routing table issue ??

http://www.projectosx.com/forum/index.php?...ic=532&st=0 post14

 

Sh*t annoying especially if making changes to 2 drives (RAID setup.) and each boot you have too look them up!

 

Appol' for OT and appol' if I've missed a fix.

 

Any ideas?

 

D.

Link to comment
Share on other sites
Master Chief
Master Chief
Posted
Posted
Yes, ICH9. Is there a solution?

Most likely yes.

 

Mouse wake-up works!

USB mouse I presume. Which makes it even more interesting. I mean why would your mouse work, and your Apple keyboard (also USB) not?

 

Thanks, mate! I will try the lspci -nn, but where can I get lspci?

Here it is.

 

@FormelyKnownAs: Is the IRQ assignment different when this happens?

 

Edit: Good news for TSSTcorp drive owners. Read this!

lspci.zip

Link to comment
Share on other sites
FKA
FKA
Posted
Posted
@FormelyKnownAs: Is the IRQ assignment different when this happens?

 

As far as I can see no:

post-275122-1261016343_thumb.png

 

The 2 samsungs (slightly different models I know - can't truat suppliers these days and couldn't be arsed RMAing!) being my RAID drives.

 

Edit: Good news for TSSTcorp drive owners. Read this!

 

worth a pop ! :)

Link to comment
Share on other sites
Shaj
Shaj
Posted
Posted
Don't be lazy! Do some research; see page 2 and onwards...

 

 

I'm not being lazy. I've already got most everything working. Sleep. Speedtstep. C-States too (I think...coz I can see voltage fluctuations). Just wanted something to compare to in case I missed something crucial.

 

And it's weird you'd have a go at me after saying this on the other thread:

 

You might want to ask for a working DSDT in the DSDT fixed for GigaByte boards thread. This way you can skip a few parts. Make it work without too much hassle.

 

 

So chill.

Link to comment
Share on other sites
leslieking
leslieking
Posted
Posted

I have removed the "AAPL,clock-id" thing and wake-up from keyboard works!

Thanks Master Chief, mm67.

 

Device (USBE)
           {
               Name (_ADR, 0x001D0007)
               Method (_S3D, 0, NotSerialized)
               {
                   If (LEqual (OSFL, 0x02))
                   {
                       Return (0x02)
                   }

                   Return (0x03)
               }

               Method (_DSM, 4, NotSerialized)
               {
                   Store (Package (0x06)
                       {
                           "device-id", 
                           Buffer (0x04)
                           {
                               0x3A, 0x3A, 0x00, 0x00
                           }, 

                           "AAPL,clock-id", 
                           Buffer (One)
                           {
                               0x01
                           }, 

                           "device_type", 
                           Buffer (0x05)
                           {
                               "EHCI"
                           }
                       }, Local0)
                   DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                   Return (Local0)
               }

               Name (_PRW, Package (0x02)
               {
                   0x0D, 
                   0x03
               })
               OperationRegion (PWRC, PCI_Config, 0x52, 0x2F)
               Field (PWRC, ByteAcc, NoLock, Preserve)
               {
                       ,   11, 
                   PMES,   5, 
                           Offset (0x2E), 
                   WRTA,   1
               }
           }

Link to comment
Share on other sites
mm67
mm67
Posted
Posted
Yes, my EHCI Fixes are not needed anymore, the AAPL Entries need to be removed, or it doesn't work. The EHCI entries need to be like in mm67's DSDT. Great work!

 

I thought it was obvious that one doesn't use two patches for same problem, but I guess it wasn't.

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...