Dell Vostro 3450 Advanced Options unlocking in progress

[TimeWalker]

To recompile DSDT properly change the MBT code to this:

Code:

Device (MBT) { Name (_HID, EisaId ("PNP0C32")) // _HID: Hardware ID Method (_STA, 0, NotSerialized) // _STA: Status { If (LOr (LEqual (OSYS, 0x07D6), LEqual (OSYS, 0x07D9))) { Return (0x0F) } Else { Return (0x00) } } Method (GHID, 0, NotSerialized) { Return (Buffer (One) { 0x02 }) } }

Try setting these options:

It will then prompt you with this windows:

Confirm when you are done and you will be presented with:

The log will say


Try playing around with this ..

[TimeWalker]

Tried reintegrating using the *right* way .. still got the black screen.
What I did was change MBT as posted above and swap PS2M ids for compatible ones ...
There might be some sort of CRC sanity check in one of the Platform drivers which compares DSDt's checkumm to what has been defined inside the efi driver. Or it may be just our struggle of not doing this operation properly ..

[HairyCube]

Yeah, mine failed too no matter what I did.
I think there is a way to run the OS with the modified DSDT (without patching the BIOS) just to verify our claims. I'm pretty sure you can do that with MacOS and Linux, but I don't know if it's possible for Windows... Wouldn't "asl -loadtable dsdt.aml" do the trick?
...Or did I miss something and we are able to inject DSDT file into BIOS already?

[TimeWalker]

.... you get my point

[HairyCube]

Yeah, I've tried that... This value gets replaced by default DSDT every time the system reboots. I actually tried editing it (replacing DELL with [censored] lol), and it didn't really work out XD

[TimeWalker]

i see .. so we have to figure out why it's causing black screen.
meanwhile im fiddling with a somewhat pragmatic thing .. how the heck my brightness keys stop working every time I reboot or shut down Windows 8 ? they stop working in bios and osx .. but remain functional across windows and ubuntu ?

[TimeWalker]

Note to self:
Battery charge cycle count is stored in EC register 0x1D (according to data from ePSA)

Code:

OperationRegion (ECRM, EmbeddedControl, Zero, 0x0100) Field (ECRM, ByteAcc, Lock, Preserve) { WKEV, 8, Offset (0x18), PRTC, 8, SSTA, 8, SADR, 8, SCMD, 8, SMID, 8, SDAT, 8, //0x1D SDT1, 8, }

Technically this means that cycles can be monitored .. and not approximated like right now.

Code:

Name (PAK0, Package (0x0E) // extend from 0x0D to 0x0E { One, 0xFFFFFFFF, 0xFFFFFFFF, Zero, 0xFFFFFFFF, Zero, Zero, 0x64, Zero, "BAT0", "123456789", "LiON", "PTL", Zero //extend the blank cliche battery info array })

Code:

Method (_BIF, 0, NotSerialized) // _BIF: Battery Information { Store ("BIF0", Debug) Acquire (^^PCI0.LPCB.EC0.MUT0, 0xFFFF) Store (^^PCI0.LPCB.EC0.DCP0, Index (PAK0, One)) Store (^^PCI0.LPCB.EC0.FCP0, Local0) Store (Local0, Index (PAK0, 0x02)) Store (^^PCI0.LPCB.EC0.DVT0, Index (PAK0, 0x04)) Store (^^PCI0.LPCB.EC0.DNN0, Local1) Store (^^PCI0.LPCB.EC0.BSN0, Local2) Store (^^PCI0.LPCB.EC0.BCN0, Local3) Store (^^PCI0.LPCB.EC0.MNN0, Local4) Release (^^PCI0.LPCB.EC0.MUT0) Store (Divide (Local0, 0x0A, ), Index (PAK0, 0x05)) Store (Zero, Index (PAK0, 0x06)) Store (^^PCI0.LPCB.EC0.SDAT, Index (PAK0, 0x0E)) //store real value from the actual cycle register --------------------------------------------

[remytran]

Hey guys, your work is awesome! I have a question, that is the UEFI Boot, I completely installed windows 8 on UEFI but I got stuck when using Fn+F2 turn on Wifi/Blue, when I hit that button, windows freezes immediately, anyone has any idea?

[HairyCube]

This is a well-known issue with Vostro 3450 UEFI boot and Windows 8. Supposedly this can be fixed by altering DSDT tables, but unfortunately we haven't found a way to properly inject modified DSDT into the BIOS firmware image.

[remytran]

Oh, that's a pity, without Wifi, laptop is not laptop.... Have you guys successfully update the Intel VBIOS? I have watched this thread for long time and forgot my password. It seems that our Bios reaches to an end?