Jump to content

DSDT Auto-Patcher


MaLd0n
 Share

5,753 posts in this topic

Recommended Posts

@MaLd0n,

 

Fixed finally. It was a combination of things. 10.6.3 might have been one of the reason coupled with the RTL1111E Ethernet Driver from Kexts.com which I removed and installed a better one, a Linux to mac release.

 

I did read that even this driver previous version was causing issues with sleep/wake.

 

So everything is working now. Updated to 10.6.5 and CSTinfo was gone and had to do another Optimized Defaults and it came back. Man I hope this motherboard is not going out on me :)

 

Can I ask you two questions:

 

1) Should I change HPET from 32 bit to 64 bit since OS is 64 bit

2) What does your brother's Serial-ATA look like in System Profiler? IS it like my screenshot if so no big deal then.

 

 

Now just need to fix the audio. The LegacyHDA_ALC888B.kext v2 t is not doing the trick so I will most likely go VoodooHDA!!

 

 

Thanks

Link to comment
Share on other sites

@MaLd0n,

 

Fixed finally. It was a combination of things. 10.6.3 might have been one of the reason coupled with the RTL1111E Ethernet Driver from Kexts.com which I removed and installed a better one, a Linux to mac release.

 

I did read that even this driver previous version was causing issues with sleep/wake.

 

So everything is working now. Updated to 10.6.5 and CSTinfo was gone and had to do another Optimized Defaults and it came back. Man I hope this motherboard is not going out on me :thumbsup_anim:

 

Can I ask you two questions:

 

1) Should I change HPET from 32 bit to 64 bit since OS is 64 bit

2) What does your brother's Serial-ATA look like in System Profiler? IS it like my screenshot if so no big deal then.

 

 

Now just need to fix the audio. The LegacyHDA_ALC888B.kext v2 t is not doing the trick so I will most likely go VoodooHDA!!

 

 

Thanks

:unsure:

This BIOS option is linked to the HPET Support BIOS option. HPET Support must be enabled for this BIOS option to be active.

 

The HPET, short for High Precision Event Timer, is a new system timer developed by Intel and Microsoft to replace the four system timers currently in use. Some HPETs have 64-bits wide registers which can also run in the 32-bit mode. This is where the HPET Mode BIOS option comes in.

 

Setting it to the 64-Bit Mode allows the 64-bit operating systems and applications to make full use of the HPET's 64-bit registers.

 

Setting it to the 32-Bit Mode forces the HPET's 64-bit registers to run in the 32-bit mode. This allows proper operation when used with a 32-bit operating system.

 

If you are using a 64-bit operating system, you should select the 64-Bit Mode so that the operating system and 64-bit applications can make full use of the HPET's 64-bit registers. There is no harm in selecting the 32-Bit Mode although it will mean a potential reduction in counter resolution and/or functionality.

 

If you are using a 32-bit operating system, you should select the 32-Bit Mode.

 

If you are dual-booting between a 64-bit operating system and a 32-bit operating system and both support the HPET, select the 32-Bit Mode. If the 64-bit operating system supports HPET while the 32-bit operating system does not (e.g. Windows XP), then you can select the 64-Bit Mode.

Tech arp

uname -v

------------------------------------------

System profile serial ATA is cosmetic, will not make any difference

Link to comment
Share on other sites

:) You're wrong.

 

You're wrong.(2)

 

ICH7 base(GA G31, GA G41 etc)

has no AHCI

 

no need for controller kext(extra)

works natively(sata)

 

no difference

if you're talking without testing what was discussed

I ask that you read the topic

or

does not make wrong guesses

 

Thanks

Link to comment
Share on other sites

Can you please check my laptop HP Compaq 6910P DSDT and see if you can apply a patch.

 

Thanks,

 

Efi

 

 

 

 

 

I forgot to attached the file.

 

Here it is.

 

send me

kextstat

kextstat > ~/Desktop/kextstat.txt

 

ioreg output

ioreg -fl > ~/Desktop/ioreg.txt

 

Log

tail -200 /var/log/kernel.log > ~/Desktop/kernel.txt

Link to comment
Share on other sites

@MaLd0n

 

If I upgrade my BIOS, do I need to make a new DSDT file then?

 

BR

 

Peter

yes

if the bios updated

generate a new original DSDT and apply fixs again

Link to comment
Share on other sites

If you like, could you send me the fixes you added to my DSDT file ?

 

Then I could play with this, I would like to learn this also :)

 

Thanks

 

Peter

 

IRQs

REMOVED

RENAMED

RTC

FIX WARNINGS

DTGP

EHCI

 

Thank you. I still can't wake up my system from sleep using the mouse or keyboard. I have to use the power button to wake up the system. Anyway, it is not a big issue.

 

Rgds,

 

EfiGy

 

:)

 

confirm that the sleep function by closing the lid

Link to comment
Share on other sites

IRQs

REMOVED

RENAMED

RTC

FIX WARNINGS

DTGP

EHCI

 

 

 

:)

 

confirm that the sleep function by closing the lid

 

 

 

The screen blanks out when I close the lid and turn back on when opening the lid. But it does not go to full sleep. I do not know if that is normal. I was kind of hoping that I should press the keyboard or touchpad before the screen should come back on.

 

Ef

Link to comment
Share on other sites

But where can I found these ? in AutpP atcher I need to chose a MB but my MB are not in that list ? confused :-)

The patches are in a folder called "packs" into Contents/Resources/Java. The "patch.txt" has the patches in some kind of "language" I created to script patches, it is pretty simple.

 

If you want to play around with code/individual patches use the DSDT Editor, this Auto-Patcher is a simplified interface to it by the way. It just turn things automated so unexperienced users can easily patch based on mobo "packs".

 

These patches maldon listed are packed into the editor, they are also in the editor topic.

 

Editor: http://www.insanelymac.com/forum/index.php?showtopic=223205

Link to comment
Share on other sites

OK Thanks

 

But what are these

 

REMOVED

RENAMED

FIX WARNINGS

 

The other one I found :-)

 

most of the patches are not available there (yet)

I am doing according to the needs of each motherboard

Link to comment
Share on other sites

@Peter_sm

 

These should be "generic" patches maldon use on many packages, just check one of them. I picked one randomly (Gigabyte GA EP35-DS3R), in the description it states the package has RENAMED, REMOVED, etc. In the patch.txt you can easily find each part since the code is commented.

# Rename device AZAL to HDEF and change all references to it

*I think* these code blocks may vary depending on the mobo, so I don't know from which maldon took the code to fix your dsdt, but picking up any you can have an idea on what it is doing and having the patched dsdt you can look it out.

Link to comment
Share on other sites

Remove

into device label SPKR remove_entry;
into device label FDC remove_entry;
into device label FDC0 remove_entry;
into device label LPT1 remove_entry;
into device label LPTE remove_entry;
into device label LPT remove_entry;
into device label ECP1 remove_entry;
into device label MEM remove_entry;
into device label ^^RMEM remove_entry

 

Rename

*Example

into device label FWH set_label begin FWHD end;
into device label MCH set_label begin MCEH end;
into device label PIC set_label begin IPIC end;
into device label DMA1 set_label begin DMAC end;
into device label TMR set_label begin TIMR end;
into device label RTC0 set_label begin RTC end;
into device label COPR set_label begin MATH end;
into device label OMSC set_label begin LDRC end;
into device label IDE1 set_label begin SATA end;
into device label CHN0 set_label begin PRT0 end;
into device label CHN1 set_label begin PRT1 end;
into device label USB0 set_label begin UHC1 end;
into device label USB1 set_label begin UHC2 end;
into device label USB2 set_label begin UHC3 end;
into device label US31 set_label begin UHC4 end;
into device label USB4 set_label begin UHC5 end;
into device label USB5 set_label begin UHC6 end;
into device label USBE set_label begin EHC1 end;
into device label USE2 set_label begin EHC2 end;
into device label PRIM set_label begin PRT0 end;
into device label SECD set_label begin PRT1 end;
into device label PX40 set_label begin LPCB end;
into_all all code_regex DMA1 replaceall_matched begin DMAC end;
into_all all code_regex TMR replaceall_matched begin TIMR end;
into_all all code_regex RTC0 replaceall_matched begin RTC end;
into_all all code_regex COPR replaceall_matched begin MATH end;
into_all all code_regex OMSC replaceall_matched begin LDRC end;
into_all all code_regex CHN0 replaceall_matched begin PRT0 end;
into_all all code_regex CHN1 replaceall_matched begin PRT1 end;
into_all all code_regex PX40 replaceall_matched begin LPCB end;
into_all all code_regex USB0 replaceall_matched begin UHC1 end;
into_all all code_regex USB1 replaceall_matched begin UHC2 end;
into_all all code_regex USB2 replaceall_matched begin UHC3 end;
into_all all code_regex US31 replaceall_matched begin UHC4 end;
into_all all code_regex USB4 replaceall_matched begin UHC5 end;
into_all all code_regex USB5 replaceall_matched begin UHC6 end;
into_all all code_regex USBE replaceall_matched begin EHC1 end;
into_all all code_regex USE2 replaceall_matched begin EHC2 end;
into device name_adr 0x001E0000 set_label
begin
PCIB
end;
into_all all code_regex HUB0 replaceall_matched
begin
PCIB
end

 

what warnings?

Link to comment
Share on other sites

Post #1

 

If you want to send me information about your system so I can make an auto-patcher for it, please download and run the attached "run_me" script and attach the "send_me.zip" file it creates on your desktop. The included data is your DSDT, a list of loaded kexts, an ioreg dump and the kernel log. If you want to see the commands it runs, just open the script with "Automator".

http://www.insanelymac.com/forum/index.php...st&id=81816

Link to comment
Share on other sites

Hi MaLd0n,

 

I like the work you're doing with this thread. DSDT Auto Patcher is a great application.

May I kindly ask you to assist me with the below DSDT for Asus P5KPL-AM/PS.

I patched the original DSDT using your patcher and I would like to point me to the P and C states section in the attached DSDT. I want to be sure there are no P and C states sections in this DSDT cause I plan to use the Chameleon's automatic P and C generation.

DSDT_P5KPL_AM_PS_Patched.dsl.zip

Once again thank you for your endless enthusiasm and kindness :) Cheers

Link to comment
Share on other sites

Hi,

have a Gigabyte P35-DS3 rev 2.1, Intel Q6600 Core2Quad 2,4GHz, Nvidia 8600GTS 512MB

 

while i run DSDT AutoPatcher i got only that:

[Line 88 type Error message Object does not exist (\_SB.PCI0.UHC1)]

[Line 89 type Error message Object does not exist (\_SB.PCI0.UHC2)]

[Line 90 type Error message Object does not exist (\_SB.PCI0.UHC3)]

[Line 91 type Error message Object does not exist (\_SB.PCI0.UHC4)]

[Line 92 type Error message Object does not exist (\_SB.PCI0.UHC5)]

[Line 93 type Error message Object does not exist (\_SB.PCI0.UHC6)]

[Line 116 type Error message Object does not exist (\_SB.PCI0.UHC1)]

[Line 121 type Error message Object does not exist (\_SB.PCI0.UHC2)]

[Line 126 type Error message Object does not exist (\_SB.PCI0.UHC3)]

[Line 131 type Error message Object does not exist (\_SB.PCI0.UHC4)]

[Line 136 type Error message Object does not exist (\_SB.PCI0.UHC5)]

[Line 141 type Error message Object does not exist (\_SB.PCI0.UHC6)]

[Line 146 type Error message Object does not exist (\_SB.PCI0.EHC1)]

[Line 147 type Error message Object does not exist (\_SB.PCI0.EHC2)]

[Line 149 type Error message Object does not exist (\_SB.PCI0.HDEF)]

[Line 150 type Error message Object does not exist (\_SB.PCI0.IGBE)]

[Line 202 type Error message Object not found or not accessible from scope ( PCI0.EHC1.WRTA)]

[Line 203 type Error message Object not found or not accessible from scope ( PCI0.EHC2.WRTA)]

[Line 205 type Error message Object not found or not accessible from scope ( PCI0.EHC1.PMES)]

[Line 206 type Error message Object not found or not accessible from scope ( PCI0.EHC2.PMES)]

[Line 719 type Error message Object does not exist (GP9_)]

[Line 719 type Error message Object does not exist (GP9_)]

[Line 723 type Error message Object does not exist (GP9_)]

[Line 723 type Error message Object does not exist (GP9_)]

[Line 725 type Error message Object does not exist (GP9_)]

[Line 1044 type Error message Name already exists in scope (_STA)]

[Line 1050 type Error message Object does not exist (ATT3)]

i am totally noob, anyone help me?

 

my problem is:

have no sound

fresh install with BlackOsx guide and with http://www.insanelymac.com/forum/index.php...222316&st=0

 

my retail install dvd is 10.6.3, i am update up to 10.6.4

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...