Jump to content

DSDT fixes for Gigabyte boards

iSoprano

By iSoprano,
in Guides

 Share
1,908 posts in this topic

Recommended Posts

SMF
SMF
Posted
Posted

All,

 

About using the Vanilla network kext - has anyone used it and gotten IPv6 to work? When I use it I no longer get provisioned with an IPv6 address - it's blank in the networks pref pane. IPv6 works fine with the RealtekR1000SL.

 

Regards,

 

SMF

Link to comment
Share on other sites
sk1nhead
sk1nhead
Posted
Posted
Try it vanilla .. the last bonjour SW update may have solved that problem for you.

 

no joy even with the new bonjour update.. actually i'm good with a disc in my DVD drive all the time but hoping for a much better idle sleep fix.. : P

 

working bonjour r1000sl kext

 

post-345318-1263392696_thumb.png

 

vanilla kext - lan working oob but no bonjour

 

post-345318-1263392754_thumb.png

Link to comment
Share on other sites
LocusOfControl
LocusOfControl
Posted
Posted
no joy even with the new bonjour update.. actually i'm good with a disc in my DVD drive all the time but hoping for a much better idle sleep fix.. : P

 

working bonjour r1000sl kext

 

post-345318-1263392696_thumb.png

 

vanilla kext - lan working oob but no bonjour

 

post-345318-1263392754_thumb.png

 

How do you know bonjour isn't working?

Link to comment
Share on other sites
mm67
mm67
Posted
Posted
Hi,

What does this scope do in Device (LPCB) ?

 

Scope (\)
{
OperationRegion (SCPP, SystemIO, 0xB2, One)
Field (SCPP, ByteAcc, NoLock, Preserve)
{
	SMIP,   8
}
}

 

Removing it cause a kernel panic. I just want to know what does it do..

 

Port 0xB2 is SMI command port, it is used to launch SMM handlers.

Link to comment
Share on other sites
sk1nhead
sk1nhead
Posted
Posted
How do you know bonjour isn't working?

 

1: 2nd screenshot above - TimeCapsule icon and D-Link DNS-323 icon (beta FW 1.08 w/ bonjour) are not suppose to be that way.

 

2: Airport Utility can't find my time capsule and can't connect on my sidebar (1st screenshot it's connected)

 

3: and a few more including iTunes : P

 

screenshot of my sidebar and airport utility (w/ r1000sl kext)

 

post-345318-1263394372_thumb.png

Link to comment
Share on other sites
kdawg
kdawg
Posted
Posted
Port 0xB2 is SMI command port, it is used to launch SMM handlers.
OK because I'm still trying to decipher all this how did you track that down when pouring through the spec?

 

1: 2nd screenshot above - TimeCapsule icon and D-Link DNS-323 icon (beta FW 1.08 w/ bonjour) are not suppose to be that way.

 

2: Airport Utility can't find my time capsule and can't connect on my sidebar (1st screenshot it's connected)

 

3: and many more : P

 

screenshot of my sidebar and airport utility (w/ r1000sl kext)

 

post-345318-1263394372_thumb.png

This is what I happen to have in my LAN devices. Bonjour works for me, however I'm not convinced it's because of this:
Device (LAN0) {
Name (_ADR, Zero)
Method (_DSM, 4, NotSerialized) {
	Store (Package (0x08) {
			"location", Buffer (0x02){"1"},
			"built-in", Buffer (0x02){0x01},
			"device_type", Buffer (0x09){"ethernet"},
			"name", Buffer (0x01F){"Realtek RTL8111C PCI-E Gigabit"}
		}, Local0)
	DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
	Return (Local0)
}
} // <-- Ethernet port 1

Worth a shot.

Link to comment
Share on other sites
sk1nhead
sk1nhead
Posted
Posted
Do you not need 'auto start after power fail' checked to resume properly from sleep?

 

EDIT -- FYI, I have 8111B chip!

 

D.

 

Nope - sleep and wake works here check or uncheck on auto start after power fail after mm67 derive dsdt..

 

according to lspci i'm using RTL8111/8168B but according to network utility it's RTL8168C hehe so i'm using the latter on my dsdt.

 

This is what I happen to have in my LAN devices. Bonjour works for me, however I'm not convinced it's because of this:

 

....................

 

Worth a shot.

 

this is what i'm currently using but i tried something like yours before but still the same...

 

Device (PEX1)
		..............
		  .................
			..................

		Device (GIGE)
			{
				Name (_ADR, Zero)
			 	Method (_DSM, 4, NotSerialized)
				{
					Store (Package (0x08)
						{
							"device-id", 
							Buffer (0x04)
							{
								0x68, 0x81, 0x00, 0x00
							}, 
			"AAPL,slot-name", 
							"Built In",	   
							"name",
							"Realtek",
							"model", 
							"Realtek RTL8168c Gigabit Ethernet"
							}, Local0)
					DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
					Return (Local0)
				}

Link to comment
Share on other sites
Sull
Sull
Posted
Posted

I have had a lot of success patching with the help of others. Well I am wondering about two things.

 

1. Is this just my experience with iasl or does this happen with all compilers for dsdt. It does not matter how you organize your dsdt because soon as you compile and then decompile it gets changed

 

This...

    Scope (_PR)
   {
       Name (PSS, Package (0x06)   // <--- Number of P-States as counted below
       {
		Package (0x06) { 3920, 74368, 10, 10, 0x82C, 0x82C },
		Package (0x06) { 3430, 72546, 10, 10, 0x726, 0x726 },
		Package (0x06) { 2940, 73694, 10, 10, 0x621, 0x621 }

 

Turns into this...

    Scope (_PR)
   {
       Name (PSS, Package (0x06)
       {
           Package (0x06)
           {
               0x0F50, 
               0x00012280, 
               0x0A, 
               0x0A, 
               0x082C, 
               0x082C
           }, 

           Package (0x06)
           {
               0x0D66, 
               0x00011B62, 
               0x0A, 
               0x0A, 
               0x0726, 
               0x0726
           }, 

           Package (0x06)
           {
               0x0B7C, 
               0x00011FDE, 
               0x0A, 
               0x0A, 
               0x0621, 
               0x0621
           }
       })

 

I am just curious about this.

 

2nd. I am wondering if I have the correct graphics in my dsdt. When booting and just when the the login screen loads my mouse pointer changes to another color and then changes back all within two seconds... My card is recognized correctly in system profiler or so I think. My card is Nvidia 8800 GTS 640mb.....

  Chipset Model:	NVIDIA Graphics Engine
 Type:	GPU
 Bus:	PCIe
 Slot:	PCI
 PCIe Lane Width:	x16
 VRAM (Total):	512 MB
 Vendor:	NVIDIA (0x10de)
 Device ID:	0x0193
 Revision ID:	0x00a2
 ROM Revision:	NVIDIA Graphics Engine DSDT
 Displays:
SyncMaster:
 Resolution:	1920 x 1200 @ 60 Hz
 Pixel Depth:	32-Bit Color (ARGB8888)
 Main Display:	Yes
 Mirror:	Off
 Online:	Yes
 Rotation:	Supported
Display Connector:
 Status:	No Display Connected

 

Here is what I have in dsdt

            Device (PEGP)                                       
           {
               Name (_ADR, 0x00010000)
               Device (GFX0)
               {
                   Name (_ADR, Zero)
                   Name (_SUN, One)
                   Method (_DSM, 4, NotSerialized)
                   {
                       Store (Package (0x16)
                           {
                               "@0,compatible", 
                               Buffer (0x0B)
                               {
                                   "NVDA,NVMac"
                               }, 

                               "@0,device_type", 
                               Buffer (0x08)
                               {
                                   "display"
                               }, 

                               "@0,name", 
                               Buffer (0x0F)
                               {
                                   "NVDA,Display-A"
                               }, 

                               "@1,compatible", 
                               Buffer (0x0B)
                               {
                                   "NVDA,NVMac"
                               }, 

                               "@1,device_type", 
                               Buffer (0x08)
                               {
                                   "display"
                               }, 

                               "@1,name", 
                               Buffer (0x0F)
                               {
                                   "NVDA,Display-B"
                               }, 

                               "NVCAP", 
                               Buffer (0x18)
                               {
                                   /* 0000 */    0x04, 0x00, 0x00, 0x00, 0x00, 0x00, 0x03, 0x00, 
                                   /* 0008 */    0x0C, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x07, 
                                   /* 0010 */    0x00, 0x00, 0x00, 0x00
                               }, 

                               "VRAM,totalsize", 
                               Buffer (0x04)
                               {
                                   0x00, 0x00, 0x00, 0x20
                               }, 

                               "device_type", 
                               Buffer (0x0C)
                               {
                                   "NVDA,Parent"
                               }, 

                               "model", 
                               Buffer (0x17)
                               {
                                   "NVIDIA Graphics Engine"
                               }, 

                               "rom-revision", 
                               Buffer (0x1C)
                               {
                                   "NVIDIA Graphics Engine DSDT"
                               }
                           }, Local0)
                       DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                       Return (Local0)
                   }
               }
           }

 

On that note as well... is this related to graphics as well... or this is just configuring the PCI slot... ?

        Device (PCI0)
       {
           Name (_HID, EisaId ("PNP0A03"))
           Name (_ADR, Zero)
           Name (_UID, One)            //<--PCI root value RC4 boot flag required if using GraphicsEnabler
           Name (_BBN, Zero)
           Name (_STA, 0x0F)
           Method (_CRS, 0, NotSerialized)
           {
               Name (BUF0, ResourceTemplate ()
               {
                   WordBusNumber (ResourceConsumer, MinNotFixed, MaxNotFixed, PosDecode,
                       0x0000,             // Granularity
                       0x0000,             // Range Minimum
                       0x003F,             // Range Maximum
                       0x0000,             // Translation Offset
                       0x0040,             // Length
                       ,, )
                   IO (Decode16,
                       0x0CF8,             // Range Minimum
                       0x0CF8,             // Range Maximum
                       0x01,               // Alignment
                       0x08,               // Length
                       )
                   WordIO (ResourceProducer, MinFixed, MaxFixed, PosDecode, EntireRange,
                       0x0000,             // Granularity
                       0x0000,             // Range Minimum
                       0x0CF7,             // Range Maximum
                       0x0000,             // Translation Offset
                       0x0CF8,             // Length
                       ,, , TypeStatic)
                   WordIO (ResourceProducer, MinFixed, MaxFixed, PosDecode, EntireRange,
                       0x0000,             // Granularity
                       0x0D00,             // Range Minimum
                       0xFFFF,             // Range Maximum
                       0x0000,             // Translation Offset
                       0xF300,             // Length
                       ,, , TypeStatic)
                   DWordMemory (ResourceProducer, PosDecode, MinFixed, MaxFixed, Cacheable, ReadWrite,
                       0x00000000,         // Granularity
                       0x000A0000,         // Range Minimum
                       0x000BFFFF,         // Range Maximum
                       0x00000000,         // Translation Offset
                       0x00020000,         // Length
                       ,, , AddressRangeMemory, TypeStatic)
                   DWordMemory (ResourceProducer, PosDecode, MinFixed, MaxFixed, Cacheable, ReadWrite,
                       0x00000000,         // Granularity
                       0x000C0000,         // Range Minimum
                       0x000DFFFF,         // Range Maximum
                       0x00000000,         // Translation Offset
                       0x00020000,         // Length
                       ,, , AddressRangeMemory, TypeStatic)
                   DWordMemory (ResourceProducer, PosDecode, MinFixed, MaxFixed, Cacheable, ReadWrite,
                       0x00000000,         // Granularity
                       0x00100000,         // Range Minimum
                       0xFEBFFFFF,         // Range Maximum
                       0x00000000,         // Translation Offset
                       0xFFF00000,         // Length
                       ,, _Y00, AddressRangeMemory, TypeStatic)
               })
               CreateDWordField (BUF0, _Y00._MIN, TCMM)
               CreateDWordField (BUF0, _Y00._LEN, TOMM)
               Add (AMEM, 0x00040000, TCMM) 
               Add (TCMM, 0x00010000, TCMM)
               Subtract (0xFEC00000, TCMM, TOMM)
               Return (BUF0)
           }

           Method (_PRT, 0, NotSerialized)
           {
               Return (Package (0x1B)
               {
                   Package (0x04){0x1BFFFF,Zero,Zero,0x16},
                   Package (0x04){0x1FFFF,Zero,Zero,0x10},
                   Package (0x04){0x1FFFF,One,Zero,0x11},
                   Package (0x04){0x1FFFF,0x02,Zero,0x12},
                   Package (0x04){0x1FFFF,0x03,Zero,0x13},
                   Package (0x04){0x6FFFF,Zero,Zero,0x10},
                   Package (0x04){0x6FFFF,One,Zero,0x11},
                   Package (0x04){0x6FFFF,0x02,Zero,0x12},
                   Package (0x04){0x6FFFF,0x03,Zero,0x13},
                   Package (0x04){0x1CFFFF,Zero,Zero,0x10},
                   Package (0x04){0x1CFFFF,One,Zero,0x11},
                   Package (0x04){0x1CFFFF,0x02,Zero,0x12},
                   Package (0x04){0x1CFFFF,0x03,Zero,0x13},
                   Package (0x04){0x1CFFFF,Zero,Zero,0x10},
                   Package (0x04){0x1CFFFF,One,Zero,0x11},
                   Package (0x04){0x1DFFFF,Zero,Zero,0x17},
                   Package (0x04){0x1DFFFF,One,Zero,0x13},
                   Package (0x04){0x1DFFFF,0x02,Zero,0x12},
                   Package (0x04){0x1DFFFF,0x03,Zero,0x10},
                   Package (0x04){0x1FFFFF,One,Zero,0x13},
                   Package (0x04){0x1FFFFF,One,Zero,0x13},
                   Package (0x04){0x1FFFFF,0x02,Zero,0x12},
                   Package (0x04){0x19FFFF,Zero,Zero,0x14},
                   Package (0x04){0x1AFFFF,Zero,Zero,0x10},
                   Package (0x04){0x1AFFFF,One,Zero,0x15},
                   Package (0x04){0x1AFFFF,0x02,Zero,0x12},
                   Package (0x04){0x1AFFFF,0x02,Zero,0x12}
               })
           }

 

Thanks

Link to comment
Share on other sites
leslieking
leslieking
Posted
Posted

I have this code for SBUS:

 

Device (SBUS) //<-- Renamed from PX43
{
   Name (_ADR, 0x001F0003)
   Method (_DSM, 4, NotSerialized)
   {
       Store (Package (0x02)
           {
               "device-id", 
               Buffer (0x04)
               {
                   0x30, 0x3A, 0x00, 0x00
               }
           }, Local0)
       DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
       Return (Local0)
   }

   Device (BUS0)
   {
       Name (_CID, "smbus")
       Name (_ADR, Zero)
       Device (DVL0)
       {
           Name (_ADR, 0x57)
           Name (_CID, "diagsvault")
           Method (_DSM, 4, NotSerialized)
           {
               Store (Package (0x03)
                   {
                       "address", 
                       0x57, 
                       Buffer (One)
                       {
                           0x00
                       }
                   }, Local0)
               DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
               Return (Local0)
           }
       }
   }
}

 

I think, it works:

 

86:~ zoliky$ kextstat | grep SMBus
  64	0 0xffffff7f80fff000 0x2000	 0x2000	 com.apple.driver.AppleSMBusPCI (1.0.4d0) <9 5 4 3>
  76	1 0xffffff7f81180000 0x2000	 0x2000	 com.apple.iokit.IOSMBusFamily (1.1) <5 4 3>
  77	0 0xffffff7f81182000 0xb000	 0xb000	 com.apple.driver.AppleSMBusController (1.0.4d0) <76 9 8 5 4 3>

 

But... Why I need to inject the "address, 0x57," in DVL0 ?

Link to comment
Share on other sites
kt6uk
kt6uk
Posted
Posted

So I've spent must be the past week learning all I could from this thread and it's been a real education - I nearly have a fully patched DSDT for my GA-P35-DS3L F9 motherboard.

 

Just have to edit up the CPU entry for my E5200 duo core and related P states - problem is I can't determine the P states as pstatechanger keeeps crashing.

 

Does anyone have this info or better still a DSDT entry for a E5200 ?

 

Rig notes:

 

Running 10.6.2 fully patched with a 8800GTS video card.

 

Chameleon RC4 triple booting in XP, SL or Unbuntu 9.10

Link to comment
Share on other sites
Sull
Sull
Posted
Posted
So I've spent must be the past week learning all I could from this thread and it's been a real education - I nearly have a fully patched DSDT for my GA-P35-DS3L F9 motherboard.

 

Just have to edit up the CPU entry for my E5200 duo core and related P states - problem is I can't determine the P states as pstatechanger keeeps crashing.

 

Does anyone have this info or better still a DSDT entry for a E5200 ?

 

Rig notes:

 

Running 10.6.2 fully patched with a 8800GTS video card.

 

Chameleon RC4 triple booting in XP, SL or Unbuntu 9.10

 

Try using voodoo monitor and kext to get p states!

 

Also do you mind sharing, I would like to take a look at your nvidia section ?

 

Attach your dsdt.dsl please :P

Link to comment
Share on other sites
kt6uk
kt6uk
Posted
Posted

Hi Sull,

 

Funny you should ask :-)

 

I've spent the last few days reading this thread from to start to finish and editing / improving my DSDT as I went along.

 

I have a 8800GTS file which worked perfectly from day one on my rig so I built it into my master dsdt.

 

Then I came across your dsdt which someone else fixed up for you just recently in this thread.

 

I compared it to yours and its practically identical. I've attached the relevant part.

 

Ok on the voodoo monitor - yeah I was thinking that might be a way forward...

 

Certainly have learnt a lot thanks to this thread :-)

 

Tim

 

Edit also here's my full dsdt - but I've not tested it yet.....

 

 

Try using voodoo monitor and kext to get p states!

 

Also do you mind sharing, I would like to take a look at your nvidia section ?

 

Attach your dsdt.dsl please :P

8800_dsdt_extract.txt

original_gt_usb_uhci_dsdt.zip

Link to comment
Share on other sites
leslieking
leslieking
Posted
Posted

kt6uk, SBUS works for you? I have a similar mobo.. type this command in terminal and send your output:

 

$kextstat | grep SMBus

 

Am I the only person who need device injection in SBUS? My DSDT compared to yours:

 

Device (SBUS) //<-- Renamed from PX43
{
   Name (_ADR, 0x001F0003)
   Method (_DSM, 4, NotSerialized)
   {
       Store (Package (0x02)
           {
               "device-id", 
               Buffer (0x04)
               {
                   0x30, 0x3A, 0x00, 0x00
               }
           }, Local0)
       DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
       Return (Local0)
   }

   Device (BUS0)
   {
       Name (_CID, "smbus")
       Name (_ADR, Zero)
       Device (DVL0)
       {
           Name (_ADR, 0x57)
           Name (_CID, "diagsvault")
           Method (_DSM, 4, NotSerialized)
           {
               Store (Package (0x03)
                   {
                       "address", 
                       0x57, 
                       Buffer (One)
                       {
                           0x00
                       }
                   }, Local0)
               DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
               Return (Local0)
           }
       }
   }
}

Link to comment
Share on other sites
FKA
FKA
Posted
Posted
OK because I'm still trying to decipher all this how did you track that down when pouring through the spec?

 

This is what I happen to have in my LAN devices. Bonjour works for me, however I'm not convinced it's because of this:

Device (LAN0) {
 Name (_ADR, Zero)
 Method (_DSM, 4, NotSerialized) {
	 Store (Package (0x08) {
			 "location", Buffer (0x02){"1"},
			 "built-in", Buffer (0x02){0x01},
			 "device_type", Buffer (0x09){"ethernet"},
			 "name", Buffer (0x01F){"Realtek RTL8111C PCI-E Gigabit"}
		 }, Local0)
	 DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
	 Return (Local0)
 }
} // <-- Ethernet port 1

Worth a shot.

 

I've just pinched this off you:

 

"name", Buffer (0x01F){"Realtek RTL8111B PCI-E Gigabit"}

 

I presume it's only cosmetic??

 

I was pouring over someone elses DSDT for their MSI P55 mobo and it seem to be very bloated with a lot of unused stuff. For example serial and GFX devices that don't exist. We'll have to start a MSI DSDT thread.

 

I wasn't expecting a free ride - that would be no fun at all! :blink:

 

D

Link to comment
Share on other sites
kt6uk
kt6uk
Posted
Posted

Hi Zoliky

 

I tried the command as you mention below both for SMBus and SBUS your typo :-) and got no output in either case.

 

I have now tested my final DSDT posted above and it works as expected.

 

No errors reported in the system or kernel logs and instant sleep when I hit sleep - but to come back out of sleep I need to hit the power button rather than click the mouse - no big deal though.

 

Now onto getting the c p states working for the CPU.....

 

Hope this helps

 

 

Tim

 

kt6uk, SBUS works for you? I have a similar mobo.. type this command in terminal and send your output:

 

$kextstat | grep SMBus

 

Am I the only person who need device injection in SBUS? My DSDT compared to yours:

 

Device (SBUS) //<-- Renamed from PX43
{
   Name (_ADR, 0x001F0003)
   Method (_DSM, 4, NotSerialized)
   {
       Store (Package (0x02)
           {
               "device-id", 
               Buffer (0x04)
               {
                   0x30, 0x3A, 0x00, 0x00
               }
           }, Local0)
       DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
       Return (Local0)
   }

   Device (BUS0)
   {
       Name (_CID, "smbus")
       Name (_ADR, Zero)
       Device (DVL0)
       {
           Name (_ADR, 0x57)
           Name (_CID, "diagsvault")
           Method (_DSM, 4, NotSerialized)
           {
               Store (Package (0x03)
                   {
                       "address", 
                       0x57, 
                       Buffer (One)
                       {
                           0x00
                       }
                   }, Local0)
               DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
               Return (Local0)
           }
       }
   }
}

Link to comment
Share on other sites
waldo_pepperjack
waldo_pepperjack
Posted
Posted
1. Control + eject brings up that menu on an apple keyboard.

2. As the apple keyboard doesn't have a power button there isnt a way to map that menu to the keyboard power button with the apple keyboard.

 

3. As far as that menu working on my imac - I cant get it to work via my power button

 

1. Yeah, thanks. I had always associated F12 with Eject - I'd forgotten that some keyboards actually have the Eject key. You are right - that works, and it is fine as a solution.

 

2. Some of my (older, I guess) USB Mac keyboards do have the power button on them, and on an actual Mac they bring up the Shutdown menu.

 

3. The power button on wifey's MacBookPro, on my DellMini10v (running Leopard 10.5.8), my old G4 tower @ work ... all give Shutdown Menu when the Power Button ( in each case has the O with the line at the very top) seems to consistently the Shutdown menu ...

 

well, anyway, I'm not that much of a purist that I need that function exactly ... I guess I was more interested in it as a problem to solve ...

 

Since my MacPro/HacPro is working in a Mac-esque manner otherwise, I guess that this is good enough for me atm. :)

 

==========================

 

Question to all: The statement "the fewer kexts one has in /Extra/Extensions/, the lower the potential of disruptions when updating from the OS" (intuitively) seems like it should be true.

 

For those of you running custom dsdt's over the last 6 months or so, has it actually held true? Do updates seem to cause less trouble on systems that have "more vanilla" in them, and a minimal /E/E ?

Link to comment
Share on other sites
Sull
Sull
Posted
Posted

@kt6uk, Ohh you have the same as me. I just want someone to confirm that I do have it correct in my dsdt.... just have that weird but where at login my mouse fades a different color.......

 

Anyone ?

Link to comment
Share on other sites
kdawg
kdawg
Posted
Posted
Is MCDP safe? A lot of people use DTGP instad of MCDP.. Why?
MCDP is MasterChief's method. It only takes two arguments instead of DTGP's four. Your choice. They're the same in the end.

 

I have this code for SBUS:

 

Device (SBUS) //<-- Renamed from PX43
{
   Name (_ADR, 0x001F0003)
   Method (_DSM, 4, NotSerialized)
   {
       Store (Package (0x02)
           {
               "device-id", 
               Buffer (0x04)
               {
                   0x30, 0x3A, 0x00, 0x00
               }
           }, Local0)
       DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
       Return (Local0)
   }

   Device (BUS0)
   {
       Name (_CID, "smbus")
       Name (_ADR, Zero)
       Device (DVL0)
       {
           Name (_ADR, 0x57)
           Name (_CID, "diagsvault")
           Method (_DSM, 4, NotSerialized)
           {
               Store (Package (0x03)
                   {
                       "address", 
                       0x57, 
                       Buffer (One)
                       {
                           0x00
                       }
                   }, Local0)
               DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
               Return (Local0)
           }
       }
   }
}

 

I think, it works:

 

86:~ zoliky$ kextstat | grep SMBus
  64	0 0xffffff7f80fff000 0x2000	 0x2000	 com.apple.driver.AppleSMBusPCI (1.0.4d0) <9 5 4 3>
  76	1 0xffffff7f81180000 0x2000	 0x2000	 com.apple.iokit.IOSMBusFamily (1.1) <5 4 3>
  77	0 0xffffff7f81182000 0xb000	 0xb000	 com.apple.driver.AppleSMBusController (1.0.4d0) <76 9 8 5 4 3>

 

But... Why I need to inject the "address, 0x57," in DVL0 ?

Seems it loading fine so I would skip it. You don't need it.

 

So you're using this then?

Device (SBUS) //<-- Renamed from PX43
{
   Name (_ADR, 0x001F0003)
   Method (_DSM, 4, NotSerialized)
   {
       Store (Package (0x02)
           {
               "device-id", 
               Buffer (0x04)
               {
                   0x30, 0x3A, 0x00, 0x00
               }
           }, Local0)
       DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
       Return (Local0)
   }

   Device (BUS0)
   {
       Name (_CID, "smbus")
       Name (_ADR, Zero)
       Device (DVL0)
       {
           Name (_ADR, 0x57)
           Name (_CID, "diagsvault")
       }
   }
}

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