[solved] Requesting help for Sierra installation on Dell Inspiron 15 7548 4k TouchScreen

[RehabMan]

Success ^_^ Thank you!
I had to comment out 4 lines after applying the patch, cause it was causing errors, after i commented those out, sleep works correctly now (added a screenshot in case anyone gets to the same error as me and does not know what to do).

I applied "USB3 _PRW 0x6D Skylake (instant wake)" to your ACPI/patched/DSDT.aml without any errors.

 

[mave123]

I applied "USB3 _PRW 0x6D Skylake (instant wake)" to your ACPI/patched/DSDT.aml without any errors.

Roger, I tried with the non Skylake one, will replace it with the Skylake one, will post updates regarding display override once i get the free time to work on it(most probably tonight).

 

[RehabMan]

Roger, I tried with the non Skylake one, will replace it with the Skylake one, will post updates regarding display override once i get the free time to work on it(most probably tonight).

I was thinking your laptop was Skylake for some reason, but now I see Broadwell in your profile.
the non-Skylake is probably the more correct patch.
But the code in _Q83/_Q84 (calling _PRW) is nonsense (has no effect, since those _PRW methods have no side effects) and can be simply removed.

 

[mave123]

I was thinking your laptop was Skylake for some reason, but now I see Broadwell in your profile.
the non-Skylake is probably the more correct patch.
But the code in _Q83/_Q84 (calling _PRW) is nonsense (has no effect, since those _PRW methods have no side effects) and can be simply removed.

Roger, patched ^_^ will test it right away!

Btw, I was just going to work on display override, but I have no Overrides directory in /S/L/E/Displays
praxiss-mbp:~ praxis$ cd /System/Library/Displays/

praxiss-mbpisplays praxis$ ls

Contents

praxiss-mbpisplays praxis$ ls -a

. .. Contents

But from what I see, in About this Mac - Displays, it shows as Built-in Display(attached screenshot), which should be correct, right?

Any other ideas regarding the resolution problem I'm facing? I would like to leave the DMVT-prealloc as a last resort(I'm certain that I've tested it with 128MB as well, although I did not have the proper ACPI patches at that time).

Thank you!

 

[RehabMan]

Roger, patched ^_^ will test it right away!

Btw, I was just going to work on display override, but I have no Overrides directory in /S/L/E/Displays
praxiss-mbp:~ praxis$ cd /System/Library/Displays/

praxiss-mbpisplays praxis$ ls

Contents

praxiss-mbpisplays praxis$ ls -a

. .. Contents

But from what I see, in About this Mac - Displays, it shows as Built-in Display(attached screenshot), which should be correct, right?

Any other ideas regarding the resolution problem I'm facing? I would like to leave the DMVT-prealloc as a last resort(I'm certain that I've tested it with 128MB as well, although I did not have the proper ACPI patches at that time).

Thank you!

See here for clues on display override locations: https://www.tonymacx86.com/threads/adding-using-hidpi-custom-resolutions.133254/

 

[mave123]

See here for clues on display override locations: https://www.tonymacx86.com/threads/adding-using-hidpi-custom-resolutions.133254/

Thank you!
Also gave a try to see if I can find anything related to F11 & F12 (brightness keys).
Nothing came up in System.log with ioio and the VoodooPS2Controller.kext (debug version).
Nothing came up in System.log with DSDT patches and ACPIDebug.kext.

Should I try to use the following method? (I don't know if I understood correctly, but this would be in the case that my brightness keys goes all the way up or all the way down?)

Note on certain Dell laptops

Some Dell laptops generate PS2 codes for the brightness keys. There is built-in support for these PS2 codes in my VoodooPS2Controller.kext. But often these keyboards generate 'make' codes without 'break' codes. That is, they generate codes for the keys going down, but no code for the key being released. This causes the key to infinitely repeat.

The VoodooPS2Keyboard.kext driver has a mechanism to fix this called "Breakless PS2". And there is a built-in Dell profile that has the correct "Breakless PS2" setttings. But you have to select the profile with an SSDT.

The SSDT is checked into the VoodooPS2 project as SSDT-DELL-WN09.dsl: https://github.com/RehabMan/OS-X-Voodoo-PS2-Controller

To use it, save as AML, and place in ACPI/patched so it can be loaded by Clover. If you're using SortedOrder, make sure it refers to the file you place in ACPI/patched.

 

[RehabMan]

Thank you!
Also gave a try to see if I can find anything related to F11 & F12 (brightness keys).
Nothing came up in System.log with ioio and the VoodooPS2Controller.kext (debug version).
Nothing came up in System.log with DSDT patches and ACPIDebug.kext.

Keep in mind Sierra does not use system.log for kernel logs.
Read here: https://www.tonymacx86.com/threads/readme-common-some-unsolved-problems-in-10-12-sierra.202316/

 

[mave123]

Keep in mind Sierra does not use system.log for kernel logs.
Read here: https://www.tonymacx86.com/threads/readme-common-some-unsolved-problems-in-10-12-sierra.202316/

Roger, will do as soon as I finish the HiDPI guide you provided earlier!

 

[mave123]

I'm at a bit of a loss, in the guide( https://www.tonymacx86.com/threads/override-edid-for-display-problem.47200/ ) it shows the IODisplayEDID in this format:

"IODisplayEDID" = <00ffffffffffff004c83464c0000000000180104952213780ace859e5b4c942617505400000001010101010101010101010101010101d8cc00a0f07019803020260058c21000001ad8cc00e0f17071813020260058c21000001a000000fe00323033385780313536464c0a200000000000024121a4610000000a010a202000df>

"IODisplayEDID" = <00ffffffffffff004ca354330000000000120103802615780a859599574f8f2 ........ etc.

And his edited "plist" shows in this format:

<key>IODisplayEDID</key>
<data>
AP///////wBMo1QzAAAAAAASAQOAJhV4CoWVmVdPjyYhUFQAAAABAQEBAQEBAQEBAQEB
AQEBHCpATGGEHjAwICUAftcQAAAZAAAADwAAAAAAAAAAAC76BngAAAAA/gBTQU1TVU5H
CiAgICAgAAAA/gAxNzNLVDAxLUswMQogAEs=
</data>

Am I missing anything? Should I convert it in any way? Or just replace the AP//////.... with my 00fffff....
Guess I'll try just using the 00fff... as EDID in the plist and see what happens, can always delete it if anything goes wrong.

 

[mave123]

Tried it like that, no dice, most likely I have to change the EDID into another format?
Guess I could live with the resolution I currently have.
Will proceed with FN Brightness Keys, maybe there's more luck for me over there.

kernel: (ACPIDebug) ACPIDebug: "EC _Q81 enter"
kernel: (ACPIDebug) ACPIDebug: "EC _Q81 exit"
kernel: (ACPIDebug) ACPIDebug: "EC _Q80 enter"
kernel: (ACPIDebug) ACPIDebug: "EC _Q80 exit"

well, these were easy! _Q81 is Brightness Down && _Q80 is Brightness up ^_^