Jump to content

DSDT fixes for Gigabyte boards

iSoprano

By iSoprano,
in Guides

 Share
1,908 posts in this topic

Recommended Posts

xjasx
xjasx
Posted
Posted

I just got it for the first time while watching Sherlock Holmes today, I download vids all the time but have never noticed it before.. HD vids included, never noticed any stutters, got it today though, so just remove the AppleUpstreamUserClient.kext ?

Link to comment
Share on other sites
mm67
mm67
Posted
Posted
did we ever figure out/confirm if it is the Gigabyte DES that causes the flicker/stutter/lag in videos?

 

It might be one reason, though not very likely. Do you have it turned on ? And do you still have this Store (0x99, SMIP) in method PTS because that is needed to save status of DES. Without it DES gets turned off at shutdown, and when using restart it gets turned off anyway because method PTS is not used then. That's what I found out when I did some experimenting with DES.

Link to comment
Share on other sites
MacUser2525
MacUser2525
Posted
Posted
I just got it for the first time while watching Sherlock Holmes today, I download vids all the time but have never noticed it before.. HD vids included, never noticed any stutters, got it today though, so just remove the AppleUpstreamUserClient.kext ?

 

If that is the only time you have had it happen then I would say there is something about that video the machine does not like. You can remove it but it will just be put back again on some system update that contains it in there so best off with the Disabler.kext in your /Extra folder it will never get touched.

Link to comment
Share on other sites
xjasx
xjasx
Posted
Posted

Well I tried to rewind the vid back to the parts where I found it to stutter, but I couldn't make it reproduce, it was just random, then again I've played videos at much higher resolutions, without any problem at all :\

(this was a DVDrip, vs HD content with no probs at all)

 

I haven't played with the DES setting at all, so I'm assuming it's enabled, I just remember seeing something about it earlier in this thread.

 

And nope I don't have that in my PTS, my PTS looks like:

Method (_PTS, 1, NotSerialized)

{

Or (Arg0, 0xF0, Local0)

Store (Local0, DBG1)

Store (Zero, \_SB.PCI0.LPCB.AG3E)

If (LEqual (Arg0, 0x05))

{

Store (Zero, SLPE)

Sleep (0x10)

}

}

Link to comment
Share on other sites
mm67
mm67
Posted
Posted
Well I tried to rewind the vid back to the parts where I found it to stutter, but I couldn't make it reproduce, it was just random, then again I've played videos at much higher resolutions, without any problem at all :\

(this was a DVDrip, vs HD content with no probs at all)

 

I haven't played with the DES setting at all, so I'm assuming it's enabled, I just remember seeing something about it earlier in this thread.

 

And nope I don't have that in my PTS, my PTS looks like:

Method (_PTS, 1, NotSerialized)

{

Or (Arg0, 0xF0, Local0)

Store (Local0, DBG1)

Store (Zero, \_SB.PCI0.LPCB.AG3E)

If (LEqual (Arg0, 0x05))

{

Store (Zero, SLPE)

Sleep (0x10)

}

}

 

I'm almost sure you don't have DES on, you have to turn it on by running a Windows program and with your dsdt it gets turned off anyway as soon as you do a shutdown or restart.

Link to comment
Share on other sites
xjasx
xjasx
Posted
Posted

Yeah, I didn't think I had it on after reading your post about the PTS, just wondering what caused the lag/stutter in my vid after all this time.... it's possible for it to be a VLC fluke, i duno though :\ every single time i noticed it flicker, I'd rewind it, and it wouldn't happen again, so it definitely wasn't a problem with the AVI file

 

Also, update about the hard lockups I had, after adjusting my PSS after comparing with SSDT, not a single lockup:

0:47 up 7 days, 7:45, 2 users, load averages: 0.12 0.42 0.84

 

advise all to compare P-States given from OS X utilies (CPU-i/Voodoo Monitor/P-State changer) with SSDT (NPSS) table.....

you may not even realize it being unstable if you don't utilize CPU much on daily basis, as it will appear stable...

Link to comment
Share on other sites
keeza
keeza
Posted
Posted
Yeah, I didn't think I had it on after reading your post about the PTS, just wondering what caused the lag/stutter in my vid after all this time.... it's possible for it to be a VLC fluke, i duno though :\ every single time i noticed it flicker, I'd rewind it, and it wouldn't happen again, so it definitely wasn't a problem with the AVI file

 

Also, update about the hard lockups I had, after adjusting my PSS after comparing with SSDT, not a single lockup:

0:47 up 7 days, 7:45, 2 users, load averages: 0.12 0.42 0.84

 

advise all to compare P-States given from OS X utilies (CPU-i/Voodoo Monitor/P-State changer) with SSDT (NPSS) table.....

you may not even realize it being unstable if you don't utilize CPU much on daily basis, as it will appear stable...

I've had some minor glitches similar to yours with video stutter. Does your machine "stutter" or does it "skip" frames? I downloaded and watched a trailer and video would be fine then it would appear to skip, as if it missed a few frames. It would happen about every 20 seconds.

 

Seems that Quicktime is the culprit for me.

Link to comment
Share on other sites
Sull
Sull
Posted
Posted
Yeah, I didn't think I had it on after reading your post about the PTS, just wondering what caused the lag/stutter in my vid after all this time.... it's possible for it to be a VLC fluke, i duno though :\ every single time i noticed it flicker, I'd rewind it, and it wouldn't happen again, so it definitely wasn't a problem with the AVI file

 

Also, update about the hard lockups I had, after adjusting my PSS after comparing with SSDT, not a single lockup:

0:47 up 7 days, 7:45, 2 users, load averages: 0.12 0.42 0.84

 

advise all to compare P-States given from OS X utilies (CPU-i/Voodoo Monitor/P-State changer) with SSDT (NPSS) table.....

you may not even realize it being unstable if you don't utilize CPU much on daily basis, as it will appear stable...

 

How do we get SSDT ?

Link to comment
Share on other sites
Sull
Sull
Posted
Posted

Bit of a of a question here.. HPET in the bios has been set to 32bit, I read somewhere that it would need to be set to 64 if you want to run osx in 64, well I have been running 64 soo I changed HPET to 64... I don't notice anything.....

 

Anyone have any info on this ?

Link to comment
Share on other sites
Slice
Slice
Posted
Posted
Bit of a of a question here.. HPET in the bios has been set to 32bit, I read somewhere that it would need to be set to 64 if you want to run osx in 64, well I have been running 64 soo I changed HPET to 64... I don't notice anything.....

 

Anyone have any info on this ?

You need always set HPET to 64bit if you have 64bit processor like Intel Core 2 Duo etc. But you set HPET to 32 bit if you have Pentium 4.

No matter what is your system.

Link to comment
Share on other sites
leslieking
leslieking
Posted
Posted
New version of pc_efi 10.5 and chameleon RC4 forks

 

pc_efi 10.5+restartfix+uuidfix+fadt+ecdt+..... (note : cputype auto detection now work) =>

 

chameleon RC4+restartfix+uuidfix+fadt+ecdt+..... =>

 

note: for both, random id (the built-in UUID fix) and restart fix, are now by default, to disable those settings:

 

<key>RandomID</key> 
<string>No</string>

 

<key>RestartFix</key> 
<string>No</string>

 

have fun :P

I removed PlatformUUID.kext. After reboot I have the same ID in system profiler.

 

DF5577FA2-C304-556B-A442-960AB835CB5D (with PlatformUUID.kext)

DF5577FA2-C304-556B-A442-960AB835CB5D (with patched PCEFI)

 

Does your PCEFI obtain the same UUID ?

Link to comment
Share on other sites
Johnny V
Johnny V
Posted
Posted
You need always set HPET to 64bit if you have 64bit processor like Intel Core 2 Duo etc. But you set HPET to 32 bit if you have Pentium 4.

No matter what is your system.

 

Hmm... my DSDT has the below HPET... does the 32 mean 32 bit? I thought com.apple.Boot.plist sets the 32/64 bit system:

 

 Device (HPET)
               {
                   Name (_HID, EisaId ("PNP0103"))
                   Name (_STA, 0x0F)
                   Name (_CRS, ResourceTemplate ()
                   {
                       IRQNoFlags ()
                           {0}
                       IRQNoFlags ()
                           {8}
                       Memory32Fixed (ReadWrite,
                           0xFED00000,         // Address Base
                           0x00000400,         // Address Length
                           )
                   })
               }

Link to comment
Share on other sites
cparm
cparm
Posted
Posted
I removed PlatformUUID.kext. After reboot I have the same ID in system profiler.

 

DF5577FA2-C304-556B-A442-960AB835CB5D (with PlatformUUID.kext)

DF5577FA2-C304-556B-A442-960AB835CB5D (with patched PCEFI)

 

Does your PCEFI obtain the same UUID ?

 

no,

 

to use PlatformUUID.kext, u need to disable the built-in UUID fix (by default now) with

 

<key>RandomID</key> 
<string>No</string>

Link to comment
Share on other sites
Sull
Sull
Posted
Posted
You need always set HPET to 64bit if you have 64bit processor like Intel Core 2 Duo etc. But you set HPET to 32 bit if you have Pentium 4.

No matter what is your system.

 

What happens if you don have it set correctly. I had it at 32 for a while....

 

Instability ?

Link to comment
Share on other sites
FKA
FKA
Posted
Posted
I don't have PlatformUUID.kext. It's already removed.

I need to edit com.apple.Boot.plist ? or pcefi sets the uuid automaticaly ?

 

if you're using the variant of PC_EFi that defaults to generate UUID you need add nothing.

Link to comment
Share on other sites
mitch_de
mitch_de
Posted
Posted
I don't have PlatformUUID.kext. It's already removed.

I need to edit com.apple.Boot.plist ? or pcefi sets the uuid automaticaly ?

Perhaps it stays in some caches .mkext of /EXTRA or system .mkext ?!

Also that ....NO key should be removed.

Link to comment
Share on other sites
kdawg
kdawg
Posted
Posted

@mm67

 

mm67 take a look at this article. Very interesting. You think it might solve the IOAHCIBlockStorageInjector.kext issue? It even suggests you can temporarily modify bits with WPCREDIT and WPCRSET to test the effects. I've been searching for a solution ever since you brought it up.

 

Anyone have any ideas how to access bit 18 of this register:

PxCMD—Port [5:0] Command Register (D31:F2)

 

On my MSI board value of that bit is 0 and it doesn't need IOAHCIBlockStorageInjector.kext. On my Gigabyte board that bit is set and the kext file is necessary. Only problem is that the bit is marked as R/WO, maybe there is no other way to modify it but to modify bios ?

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