Jump to content

RehabMan! DSDT for Dell Inspiron 3x21 :help:


sugarface
 Share

30 posts in this topic

Recommended Posts

Can you plz help me patch my dsdt/ssdt*.aml?? 

 

What I want is:

Sleep

Disable NVDA

Brightness(I tried your patch, it allows me to change brightness only once per boot, then it becomes unusable)

HDMI

 

 

Is it okay to start patching on dsdt.aml or do I need to decompile it first into .dsl (I use Maciasl). Decomplie + patching leads to more error :huh:...

Thanks

 

My hardware info is below:

origin.zip

Link to comment
Share on other sites

Can you plz help me patch my dsdt/ssdt*.aml?? 

 

What I want is:

Sleep

Disable NVDA

Brightness(I tried your patch, it allows me to change brightness only once per boot, then it becomes unusable)

HDMI

 

 

Is it okay to start patching on dsdt.aml or do I need to decompile it first into .dsl (I use Maciasl). Decomplie + patching leads to more error :huh:...

 

Thanks

 

My hardware info is below:

Use: https://github.com/RehabMan/Laptop-DSDT-Patch

Fix errors with:

"Fix _PLD Buffer/Package Error"

"Fix *pnp/pnp lower case Error"

Link to comment
Share on other sites

Rehabman, Can you give me all the steps....

 

I'm on windows now my Yosemite Public Beta has no internet. :(

I'll try out all the patches and report with screenshots.

Link to comment
Share on other sites

Rehabman, Can you give me all the steps....

 

I'm on windows now my Yosemite Public Beta has no internet. :(

I'll try out all the patches and report with screenshots.

Read the README. There are instructions for using MaciASL with the repo without internet.

  • Like 1
Link to comment
Share on other sites

Rehabman, I have MaciASL and have set it up already :yes:

 

I used this command to get decompiled DSDT.

iasl -da DSDT.aml SSDT*.aml

I applied the patches you told;

Changed Not Serialized to Serialized;

 

After tht I get this >>

 

Screen%20Shot%202014-08-01%20at%202.54.3

 

how do I remove the rest of the warning, remarks, opt??

 

DSDT >> cl.ly/Wq9y/download/DSDT.dsl

Link to comment
Share on other sites

So I add patches and compile with errors/remarks?? :huh:

 

And what patches should I apply (HD4000/7 series laptop)

 

For >>

 

Sleep
Disable NVDA
Brightness (I tried your patch, it allows me to change brightness only once per boot, then it becomes unusable) :frantics:
HDMI

Link to comment
Share on other sites

So I add patches and compile with errors/remarks?? :huh:

Post #7 shows "0 Errors".

 

And what patches should I apply (HD4000/7 series laptop)

 

For >>

 

Sleep

Disable NVDA

Brightness (I tried your patch, it allows me to change brightness only once per boot, then it becomes unusable) :frantics:

HDMI

Brightness:

"Rename GFX0 to IGPU"

"Brightness Fix (HD3000/HD4000)"

 

HDMI will work OOB provided your laptop display is 1366x768 and you're injecting ig-platform-id 0x01660003. If you have higher resolution screen, you must use 0x01660004 or 0x01660009. With 0004 you need to patch the capri framebuffer kext. DSDT patches cannot be used to fix that particular problem.

 

Disabling Nvidia involves calling _OFF from _INI in the SSDT that defines your nvidia device...

 

For sleep, it depends on specifically what is wrong with sleep. Note: native power management is a pre-req for sleep.

Link to comment
Share on other sites

Okay one problem at a time....

First >> Brightness

 

I added the two patches( gfx>>igpu; brightness hd3000/4000 ) and use the patched acpi-backlight.kext

 

But still the problem persists, of being able to change brightness only once per login, then it becomes unusable.

 

_____________________________________________________________________________________________________________

 

Also what is the diff b/w, and which should I use??

 

https://github.com/RehabMan/Laptop-DSDT-Patch/blob/master/usb/usb_7-series-id.txt

 

https://github.com/RehabMan/Laptop-DSDT-Patch/blob/master/usb/usb_7-series-multiplex.txt

 

_______________________________________________________________________________________________________________

 

aand..

 

my battery indicator works with just the acpibatterymanager.kext should I also use this patch, it says 3251(which is my laptop)??

 

https://github.com/RehabMan/Laptop-DSDT-Patch/blob/master/battery/battery_Dell-Vostro-15xx.txt

 

 

THANX :)

Link to comment
Share on other sites

Okay one problem at a time....

First >> Brightness

 

I added the two patches( gfx>>igpu; brightness hd3000/4000 ) and use the patched acpi-backlight.kext

 

But still the problem persists, of being able to change brightness only once per login, then it becomes unusable.

What do you mean once per login?

 

So... if you go to SysPrefs->Displays and change brightness, then logout, and go back to SysPrefs->Displays to change it again it doesn't work the second time?

 

_____________________________________________________________________________________________________________

 

Also what is the diff b/w, and which should I use??

 

https://github.com/RehabMan/Laptop-DSDT-Patch/blob/master/usb/usb_7-series-id.txt

 

https://github.com/RehabMan/Laptop-DSDT-Patch/blob/master/usb/usb_7-series-multiplex.txt

First is to avoid instant wake (and other problems caused by USB). Second is to multiplex USB2 (EHC) with USB3 (XHC) for use with AppleUSBXHCI.kext (not necessary if you're using GenericUSBXHCI). There are comments in some of the patches. You should read them.

 

 

_______________________________________________________________________________________________________________

 

aand..

 

my battery indicator works with just the acpibatterymanager.kext should I also use this patch, it says 3251(which is my laptop)??

 

https://github.com/RehabMan/Laptop-DSDT-Patch/blob/master/battery/battery_Dell-Vostro-15xx.txt

I only see "Dell 3521" in that patch (not "Dell 3251"), but as for your question..

 

If you have working battery status without DSDT patches it could be because of two reasons:

1) You installed Snow Leopard version of AppleACPIPlatform.kext (will break proper power management and possibly other things, such as sleep)

2) Your DSDT does not require patches (if there are no EC fields larger than 8-bit that are accessed directly or indirectly by ACPI battery methods)

Link to comment
Share on other sites

1.What I meant was if I log into my system, I can change brightness only once using the fn key + brightness key (either increase or decrease) and then it stays tht way; the key combination no longer works. This problem is not there with Multimedia keys. But I'm able to change brightness from SysPrefs->Displays at all times, no problem there.

 

2. I heard GenericUSBXCHI breaks sleep, and want to do away with it, so tht means I'll be needing the multiplex (PJALM) patch too. :yes:

 

3. I'm not using a fallback version of AppleACPIPlatform.kext so I guess I won't be needing any patches :)

Link to comment
Share on other sites

1.What I meant was if I log into my system, I can change brightness only once using the fn key + brightness key (either increase or decrease) and then it stays tht way; the key combination no longer works. This problem is not there with Multimedia keys. But I'm able to change brightness from SysPrefs->Displays at all times, no problem there.

Problem in keyboard driver. Not a backlight issue. It is likely your keys are registering a 'down' event (make), but no 'up' event (break). My PS2 driver has a feature to deal with such keys in Info.plist ("Breakless PS2")...

 

2. I heard GenericUSBXCHI breaks sleep, and want to do away with it, so tht means I'll be needing the multiplex (PJALM) patch too. :yes:

GenericUSBXHCI does not break sleep. I use it all the time... If you can get AppleUSBXHCI.kext to work it is preferable as it is more native, but it is not possible all the time.

 

3. I'm not using a fallback version of AppleACPIPlatform.kext so I guess I won't be needing any patches :)

You should verify with 'kextstat|grep -y acpiplat' in Terminal.

Link to comment
Share on other sites

 

Problem in keyboard driver. Not a backlight issue. It is likely your keys are registering a 'down' event (make), but no 'up' event (break). My PS2 driver has a feature to deal with such keys in Info.plist ("Breakless PS2")...

 

 

 But I can't use your driver since I have Elan trackpad. How do I fix it then?? :huh:

 

GenericUSBXHCI does not break sleep. I use it all the time... If you can get AppleUSBXHCI.kext to work it is preferable as it is more native, but it is not possible all the time.

 

 Is it possible to have the multiplex patch and GenericUSBXHCI at same time?

 

You should verify with 'kextstat|grep -y acpiplat' in Terminal.

 

 

I'm sure abt this m on yosemite public beta :)

Link to comment
Share on other sites

But I can't use your driver since I have Elan trackpad. How do I fix it then?? :huh:

Read the documentation/contact the author of the kext that you're using.

 

Is it possible to have the multiplex patch and GenericUSBXHCI at same time?

Possible: Yes (you can do what ever you want). There is no reason to multiplex with GenericUSBXHCI and it probably would not work. Usually -gux_defer_usb2 is used when you have Intel 7/8-series chipset and GenericUSBXHCI.kext.

 

I'm sure abt this m on yosemite public beta :)

You should really start with Mavericks and get your system working there first... After you have everything figured out, it will be easy to translate to future versions.

 

FYI: Looking at the DSDT.dsl you provided a while back, I see no EmbeddedControl, so EC field access would not be an issue...

Link to comment
Share on other sites

Hi Rehabman

 

Here is an update, I Googled, found suitable patches for DSDT and SSDTs, and it blocked my NVDA gpu, it won't show up on my Sys Info anymore. :):thumbsup_anim:

#But with the patched *.aml(s) and after a reboot, my screen had dimmed even though it was @100% brightness. I fixed tht by deleting acpibacklight.kext. I know this might not be a fix but this works for now. :yes:

 

Screen%20Shot%202014-08-02%20at%204.02.4

 

>> I also found that Elan VoodooPS2 controller is a port of your kext (Synaptics one), so breakless PS2 features apply to that as well. Can you help me with that??

 

Thanks

Link to comment
Share on other sites

Hi Rehabman

 

Here is an update, I Googled, found suitable patches for DSDT and SSDTs, and it blocked my NVDA gpu, it won't show up on my Sys Info anymore. :):thumbsup_anim:

#But with the patched *.aml(s) and after a reboot, my screen had dimmed even though it was @100% brightness. I fixed tht by deleting acpibacklight.kext. I know this might not be a fix but this works for now. :yes:

 

Screen%20Shot%202014-08-02%20at%204.02.4

This is why I suggest you do Mavericks instead...

 

>> I also found that Elan VoodooPS2 controller is a port of your kext (Synaptics one), so breakless PS2 features apply to that as well. Can you help me with that??

 

Thanks

As far as I know, it is not related to my kext...

Link to comment
Share on other sites

oops :blush:

 

Its an ALPS that I use, not an ELAN. Sorry about that, my intention was not to confuse you (https://github.com/RehabMan/OS-X-Voodoo-PS2-Controller/pull/2) ....and, I'm getting mavericks 10.9.5 beta :yes::)

 

:shock: When I  use the Alps kext it detects trackpad as Alps GlidePoint, with your kext it is detected as a Synaptics. On Windows it is detected as a Synaptics. Both of them work equally well though. (I'm confused now, as to which to use :unsure: )

 

Screen%20Shot%202014-08-02%20at%2011.15.

 

That 's exactly my problem (and I have the same key combo) >> http://www.tonymacx86.com/mavericks-laptop-support/87182-new-voodoops2controller-keyboard-trackpad-clickpad-support-12.html#post555276

 

But you seem to have sorted it, in your kexts, but I still have the problem >> http://www.tonymacx86.com/mavericks-laptop-support/87182-new-voodoops2controller-keyboard-trackpad-clickpad-support-13.html#post555352

Link to comment
Share on other sites

oops :blush:

 

Its an ALPS that I use, not an ELAN. Sorry about that, my intention was not to confuse you (https://github.com/RehabMan/OS-X-Voodoo-PS2-Controller/pull/2) ....and, I'm getting mavericks 10.9.5 beta :yes::)

 

:shock: When I  use the Alps kext it detects trackpad as Alps GlidePoint, with your kext it is detected as a Synaptics. On Windows it is detected as a Synaptics. Both of them work equally well though. (I'm confused now, as to which to use :unsure: )

Post ioreg in both scenarios... (use IORegistryExplorer v2.1)

 

I don't think your links are working correctly. And it is probably a good idea to respond directly at tmx. IM has a disregard for tmx and the links will probably be mangled here.

Link to comment
Share on other sites

okay this is with the Alps driver loaded....

 

Screen%20Shot%202014-08-03%20at%204.22.5

 

This is the ioreg with Synaptics drivers>> http://cl.ly/WrUu

                           with Alps drivers >>        http://cl.ly/WrRU

 

I don't think your links are working correctly. And it is probably a good idea to respond directly at tmx. IM has a disregard for tmx and the links will probably be mangled here.

 

Okay I'll post tht on tmx, I'm noobman (username) there...

Link to comment
Share on other sites

okay this is with the Alps driver loaded....

 

Screen%20Shot%202014-08-03%20at%204.22.5

 

This is the ioreg with Synaptics drivers>> http://cl.ly/WrUu

                           with Alps drivers >>        http://cl.ly/WrRU

Both files are using the Synaptics driver. With the ALPS driver loaded, the system is checking for ALPS and not finding it. Conclusion: Your device is Synaptics.

  • Like 1
Link to comment
Share on other sites

  • 3 weeks later...

Hey RehabMan :D

 

M back again...

 

So you helped me fix the Brightness issue, HDMI, disabling Nvidia, found its Synaptics over ALPS.....

 

What remains is : SLEEP (I tried darkwake=0/1/10 already, didn't work; and I have all the prerequisites for SLEEP, i.e proper powermanagement, based on your article on tmx)

 

can you help me fix this one?? :frantics:

 

Thnx

Link to comment
Share on other sites

 Share

×
×
  • Create New...