How to Fix Changing DVMT pre-allocated using the RU.efi, expert advice needed

By Freirburro
0

opencore

How to Fix Changing DVMT pre-allocated using the RU.efi, expert advice needed

Network issues on Hackintosh or unsupported Macs are typically caused by chipset incompatibility, incorrect kext pairing, or corrupted network preferences.

Quick Fix Steps

  1. Identify your network chipset: Open System Information > Wi-Fi/Bluetooth or use Hackintool.
  2. Use the correct kext: For Intel Wi-Fi use AirportItlwm, for Broadcom use BrcmPatchRAM, for Ethernet use IntelMausi or RealtekRTL8111.
  3. Reset network preferences: Delete /Library/Preferences/SystemConfiguration/com.apple.airport.preferences.plist and reboot.
  4. Check privacy settings: System Settings > Privacy > Location Services must be enabled.

Verification

  • Wi-Fi connects after reboot.
  • Bluetooth pairs and stays connected.
  • Location Services works in Maps.

Related Searches


Original Question: "Changing DVMT pre-allocated using the RU.efi, expert advice needed"

So I saw the method on how to unlock the CFG lock [here] (https://www.reddit.com/r/hackintosh/comments/hz2rtm/cfg_lockunlocking_alternative_method/) and successfully did so.

Now the next step: change the DVMT pre-allocated to 64MB.

The problem: the variable for the DVMT might be saved in a different location, and that´s the point where I´m not a 100% sure if my findings are right.

So i extracted my BIOS to a readable .txt format and that is what it says for the DVMT:

0xA2F39 One Of: DVMT Pre-Allocated, VarStoreInfo (VarOffset/VarName): 0xDF, VarStore: 0x2, QuestionId: 0x1DB, Size: 1, Min: 0x0, Max 0xFE, Step: 0x0 {05 91 33 13 46 13 DB 01 02 00 DF 00 10 10 00 FE 00}

0xA2F4A Default: DefaultId: 0x0, Value (Other) {5B 85 00 00 08}

0xA2F4F Value {5A 82}

0xA2F51 QuestionId: 0xB3A equals value in list (0x73, 0x74) {14 8A 3A 0B 02 00 73 00 74 00}

0xA2F5B 64 Bit Unsigned Int: 0x1 {45 0A 01 00 00 00 00 00 00 00}

0xA2F65 64 Bit Unsigned Int: 0x2 {45 0A 02 00 00 00 00 00 00 00}

0xA2F6F Conditional {50 02}

0xA2F71 End {29 02}

0xA2F73 End {29 02}

0xA2F75 End {29 02}

0xA2F77 One Of Option: 0M, Value (8 bit): 0x0 {09 07 34 13 00 00 00}

0xA2F7E One Of Option: 32M, Value (8 bit): 0x1 (default) {09 07 35 13 30 00 01}

0xA2F85 One Of Option: 64M, Value (8 bit): 0x2 {09 07 36 13 00 00 02}

.

.

.

Notice the VarStore: 0x2 in the first line!

for the CFG lock this value was VarStore: 0x3 which referred to this section: VarStore: VarStoreId: 0x3 [B08F97FF-E6E8-4193-A997-5E9E9B0ADB32], Size: 0x209, Name: CpuSetup and therefore I had to use the "CPUSetup" within the RU.efi tool.

now if I´m right, for the DVMT with a different VarStore I would have to change the variable in a different section of the RU.efi tool: VarStore: VarStoreId: 0x2 [72C5E28C-7783-43A1-8767-FAD73FCCAFA4], Size: 0x1EB, Name: SaSetup

so to conclude: for the DVMT I had to change offset 0xDF within the SaSetup of the RU.efi tool

If anyone here is experienced with this kind of BIOS editing I´d be really happy to get my findings somehow verified.

submitted by /u/Kasti0
[link] [comments]
Share:

Leave a Reply

Loading comments...