I wish I had known Thunderbolt security was/is the problem, before forking the money on another laptop. I'm afraid I may be back in the same error code 12 hell with the Clevo 870DM3, which should arrive in 2-3 weeks. Even just flashing the BIOS was overly complicated and constant warning of bricking the laptop. It took someone with extensive coding experience 6-24 hours (each mod is specific to the laptop model and BIOS) to perform the hack. As soon as I figure out how to use and extract the information, I will post it here.Īlso, keep in mind, this BIOS mod is very specific to MSI laptops. I'm still a tadpole (not even a baby yet) when it comes to using the tools Nando4 suggested. Seems to be a significant factor for resolving the eGPU error code 12. In the end, we are just interested in what the legacy mode actually does "automatically", right? Posted by: in mind that these settings are not yet fully available for Linux, they are under development as far I know but help us understand how to call directly the Thunderbolt controller. I will try to give the information without violating my NDA to the modder.ġ) Run AMI tool to extract OEM MSI BIOSģ) Modder emails back modded BIOS plus a patchĤ) Per modder instruction, download and use USB BIOS tool to a) perform special formatting of the USB b) compile modded BIOS with patch and OEM BIOS from live memory in Windowsĥ) Shut down system, reboot in UEFI mode (secure boot disabled) and let the USB flash tool run a batch job in EFI ShellĦ) Boot normally to allow Windows to execute 'New Devices Getting Ready', then shut down againħ) Set the BIOS to boot in legacy mode and boot from USBĨ) Run custom Memtest (performs memory test within seconds to ensure compatibility), ignore warning about bricking laptopĩ) Exit Memtest, reboot into custom DOS, do short prayer then ignore second warning about bricking laptop, then finally flash the modded, recompiled BIOSġ0) Type an obscure (this is now proprietary information) command to run yet another batch job in custom DOS modeġ1) Shut down laptop, unplug and remove battery for five minutes (waited 10 minutes to make sure the EC controller registers the new BIOS and wipe remaining information in nvram).ġ2) Boot into BIOS, searched for anything resembling Thunderbolt security (the legacy mode was the closest, so I selected it)ġ3) Reset BIOS into UEFI, secure boot disabledġ5) Plug the Cubix with modded Aki Node+Aki T3 Thunderbolt controller, cross fingersġ8) Pickup jaw from ground, stare at screen to ensure no more error code 12 in Device Managerġ9) Run Hash Suite Pro - pickup jaw from ground again - marvel at 192 billion NTLM passwords processed per second. That E5470 didn't have a Thunderbolt controller on it, but the BIOS had remnants of supporting Thunderbolt. Thunderbolt Security Legacy Mode could be NVRAM toggled on the E5470 with 'setup_var 0xFF5 0x1'. eg: I applied the procedure here and was able to extract a Dell E5470's IFR file containing UEFI variables from a BIOS dump. No DSDT fix needed!!! I asked an MSI BIOS genius to unlock the MSI BIOS, switched Thunderbolt security from unique ID to legacy, and boom!!! Both 1080 Ti are active without error code 12!!!Ĭonsider if a modified BIOS is necessary.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |