(UEFI) Dell XPS 15z L511z modded BIOS - and HOWTO

[nebster]

@kasar
What's the Lucid Virtu patch? I thought it was a driver?

@jkbuha
Which VBIOS should I upgrade to on the L702X? It has SB processor and NVIDIA 555M. I'm currently on the same version as the (L511z?) A13 VBIOS.
What patches do I need to apply to my VBIOS? It's weird because there's a few more differences between the L702X A19 VBIOS and the (L511z?) A13 VBIOS.

Code:

0000 0018: BD 72 59 DB -> 4A D5 E4 D3
0000 0AEA: D5          -> 06
0000 0C07: 81 00       -> 01 40
0000 0C6B: D2          -> D6
0000 0C79: 07 00 00 05 -> 08 00 00 04
0000 0C82: 00          -> 20
0000 0FB3: 1D          -> 00
0000 1069: 43          -> 4A
0000 107F: 7F 02       -> 71 00
0000 144B: 04          -> 00
0000 1457: 00          -> 20
0000 19F6: C8 00 15    -> D2 00 00

[TimeWalker]

@nebster
please take a look
http://www.insanelymac.com/forum/topic/2...try1865872
I have already reintegrated the VBIOS along with PlatformSmm

[kasar]

@jkbuha

yeah, it was some kind of driver.

however installation asked for license stuff in bios, for that reason timewalker helped me by inserting the license into the DSDT, but I couldnt flash a modified DSDT bios yet


post edited due small missunderstanding ^^

[TimeWalker]

I can't actually change brightness AT ALL ! NOT AT BIOS LEVEL, NOT IN BOOTLOADER .. NOT IN OSX.
Only in Windows and Ubuntu ... what the [censored] is up with this POS? I have tried going back to a stock A04 and doing /CVAR just in case.. nothing helps???

---

Ught .. I guess I found the reason. A07 changes the following:
10.Brightness hotkey loss pop up after flash BIOS

I guess I will have to install A07 then ...

[nebster]

@TimeWalker
Would you mind posting the original 2137?

I'm probably going to integrate a scripting language into my patcher so I'm researching how much of this can be automated.

[TimeWalker]

I don't have the original, sorry. @jkbuha has posted an edited one right away ..
search by product code H0ET70WW and you will end up on Lenovo's support page, get the latest bios and extract the vbios from it.

For mobile vbioses the connector table is 0xC20 to 0xD1F .. as pointed out by @jkbuha

[mackyreddy]

Great work guys really appreciate ur time. Here are few suggestions based on things which i encountered. If possible correct these things in the bios.

1.On L702x USB 2.0 doesnt work natively on OS X, every time i add the EHCI Patch for sandy bridge processors using DSDTEditor-Linux-Mac-Win. This is the reason why i have released an A.19 DSDT, without DSDT in place we cant even boot the USB to install OS X. Is there any probability to add USB 3.0 support naively to the bios without the need of PXHCD.kext ?

2. Fn brightness keys are not working on OS X, i think its a common problem for all XPS laptops

3. On Windows 7 or 8 the brightness levels at the lowest point and second lowest point are same. There is no difference in brightness levels at these 2 points, as soon we hit 3rd brightness point Brightness start increasing and the same vice versa. I think both Lowest brightness level and second lowest brightness level have same brightness values. I haven't tested stock A.19, directly jumped the gun from A.12 to this custom A.19. So i dont know whether this a bug in A.19. Anyway i am planning to check the DSDT.

regards

[TimeWalker]

1. IRQ conflict between HPET and EHC2. Dell has stubornly forgot to define at least one IRQ to HPET, so it steals one from EHCI. DSDT has to be altered in the bios.

2. Use recompiled IOWMIFamily.kext from hotkoffy

3. One would assume it's _BCL method in DSDT, but no .. since there are only 8 steps of brightness levels.. so it's a poorly coded driver, noghing can be done because Dell screwed up (like always)

Sent from my LG-P500 using Tapatalk 2

[nebster]

@TimeWalker
What's the difference between the BIOS1.WPH and BIOS1_OSX.WPH?
I'm guessing both have their menus unlocked and the OSX one has an updated Sandy bridge VBIOS and backported PlatformSmm?
Are there any problems with the OSX one in Windows 8?

[TimeWalker]

Your guess is correct.
There are no issues that I know of.