Contribute
Register

[Guide] Install Big Sur on the Dell Optiplex 9010 with OpenCore

Status
Not open for further replies.
I updated to 11.3 and I’m stuck at Lilu on the loading screen. Pretty disappointing. Maybe I just need to refresh my OpenCore folder. Anyone else had this issue on their Optiplex?

UPDATE: I'm back in. I didn't change much, but I did make sure I had the latest BrcmFixup/etc kexts, refreshed Lilu and others (even though they were the same version). I ran the OpenCoreConfigurator check as well and fixed one small thing. Anyway, I am back in after another reboot and things are working.
 
Last edited:
Thank you.
i can't fix usb 3. :D
did you managed to fix usb3 ?
just installed, i was ready in an hour, no problems..
but no usb3 support...
 

Attachments

  • Screen Shot 2022-02-26 at 7.59.58 PM.png
    Screen Shot 2022-02-26 at 7.59.58 PM.png
    27.4 KB · Views: 66
Below is some information about getting USB 3 ports working with Big Sur and the Optiplex 7010. You might need to start off with 11.2.3 or 11.3 using USBinjectall Kext, make the a new kext called USBports for USB3 in Hackintool, then swap USBInjectAll for USBports, and finally upgrade to 11.6.x.

You will need some extra SSDTs and to add a patch in your opencore EFI to get USB 3 working. (Read the hyperlink below carefully and check the EFI that I uploaded to guide you). The attached EFI enables USB 3 to work on the Optiplex 7010 with Big Sur.

Reposted:
I recently installed Big Sur with opencore on the 7010, and it performs flawlessly and super smooth. I fixed sound and USB 3 issues by studying THIS, making config.plist adjustments, and.....

I started off with 11.2.3, mapped the USB ports with Hackintool, then swapped out the USBinjectAll with USBports made from Hackintool, and then finally updated to 11.6.X. What works: EVERYTHING smooth like butter (including USB3!), as well as continuity and handoff (thanks again to trs96 for writing about the Fenvi FV-T919 in the High Sierra/Mojave Guide!).

The 7010 is still as snappy as ever on BS.

edit: see post #34 of this thread for EFI.
 
Last edited:
Below is some information about getting USB 3 ports working with Big Sur and the Optiplex 7010. You might need to start off with 11.2.3 or 11.3, make the kext for USB3, and then upgrade. Also below is an EFI that enables USB 3 to work on the Optiplex 7010 with Big Sur. Good luck!

Reposted:
I recently installed Big Sur with opencore on the 7010, and it performs flawlessly and super smooth. I fixed sound and USB 3 issues by studying THIS, making config.plist adjustments, and.....

I started off with 11.2.3, mapped the USB ports with Hackintool, then swapped out the USBinjectAll with USBports made from Hackintool, and then finally updated to 11.6.X. What works: EVERYTHING smooth like butter (including USB3!), as well as continuity and handoff (thanks again to trs96 for writing about the Fenvi FV-T919 in the High Sierra/Mojave Guide!).

The 7010 is still as snappy as ever on BS.
not sure that this is correct:
Code:
<dict>
                <key>All</key>
                <true/>
                <key>Comment</key>
                <string>Delete Cpu0Ist</string>
                <key>Enabled</key>
                <false/>
                <key>OemTableId</key>
                <data>Q3B1MElzdAA=</data>
                <key>TableLength</key>
                <integer>0</integer>
                <key>TableSignature</key>
                <data>U1NEVA==</data>
                <key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14</key>
                <dict>
                    <key>DefaultBackgroundColor</key>
                    <data>AAAAAA==</data>
                </dict>
            </dict>

your patches section is not correct for opencore:
Code:
<key>Patch</key>
        <array>
            <dict>
                <key>Comment</key>
                <string>_OSI to XOSI</string>
                <key>Enabled</key>
                <true/>
                <key>Find</key>
                <data>X09TSQ==</data>
                <key>Replace</key>
                <data>WE9TSQ==</data>
            </dict>
        </array>
may also need any irq renames with your HPET.aml ?
 
I don't know what to say except for that "it just works", and when I added these things to my EFI, USB3 was magically fixed....Voila! Perfection! So, I think that you may be incorrect about it being incorrect..... If you think there is a correct way of doing, please post the solution (instead of the perceived problem that doesn't exist), and I may give it try and report back.

I will write another post soon about how I realized what had broken sleep with Optiplex 7010 and Big Sur--it is totally unrelated to the EFI. The EFI that I uploaded, that you have labeled as incorrect has provided me with a fully functional Big Sur 7010 optimac that has with sleep, USB3, and EVERYTHING working just as well as it did with trs96's Catalina 7010 guide....

I'm no expert, but I took advice about how to get USB 3 to work on the Optiplex 7010 from THIS
and it empirically works, my friend. It works! If you think that you have better way of doing it or helping the person in this thread, then please, by all means, take a snapshot of what I should enter in proper tree to make the EFI "correct", and I'll give it a try and report back.

You shouldn't scare people away from real solutions, just because something doesn't look right to you on paper.

not sure that this is correct:
Code:
<dict>
                <key>All</key>
                <true/>
                <key>Comment</key>
                <string>Delete Cpu0Ist</string>
                <key>Enabled</key>
                <false/>
                <key>OemTableId</key>
                <data>Q3B1MElzdAA=</data>
                <key>TableLength</key>
                <integer>0</integer>
                <key>TableSignature</key>
                <data>U1NEVA==</data>
                <key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14</key>
                <dict>
                    <key>DefaultBackgroundColor</key>
                    <data>AAAAAA==</data>
                </dict>
            </dict>

your patches section is not correct for opencore:
Code:
<key>Patch</key>
        <array>
            <dict>
                <key>Comment</key>
                <string>_OSI to XOSI</string>
                <key>Enabled</key>
                <true/>
                <key>Find</key>
                <data>X09TSQ==</data>
                <key>Replace</key>
                <data>WE9TSQ==</data>
            </dict>
        </array>
may also need any irq renames with your HPET.aml ?
 

Attachments

  • Screen Shot 2022-02-28 at 21.17.50.png
    Screen Shot 2022-02-28 at 21.17.50.png
    22.6 KB · Views: 60
  • Screen Shot 2022-02-28 at 21.21.21.png
    Screen Shot 2022-02-28 at 21.21.21.png
    140.8 KB · Views: 62
Last edited:
I don't know what to say except for that "it just works", and when I added these things to my EFI, USB3 was magically fixed....Viola! Perfection! So, I think that you may be incorrect about it being incorrect..... If you think there is a correct way of doing, please post the solution (instead of the perceived problem that doesn't exist), and I may give it try and report back.

I will write another post soon about how I realized what had broken sleep with Optiplex 7010 and Big Sur--it is totally unrelated to the EFI. The EFI that I uploaded, that you have labeled as incorrect has provided me with a fully functional Big Sur 7010 optimac that has with sleep, USB3, and EVERYTHING working just as well as it did with trs96's Catalina 7010 guide....

I'm no expert, but I took advice about how to get USB 3 to work on the Optiplex 7010 from THIS
and it empirically works, my friend. It works!
You shouldn't scare people away from real solutions, just because something doesn't look right to you on paper.
Code:
<key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14</key>
                <dict>
                    <key>DefaultBackgroundColor</key>
                    <data>AAAAAA==</data>
                </dict>
does not belong where you have it

renames should be in this format:
Code:
<dict>
                <key>Base</key>
                <string></string>
                <key>BaseSkip</key>
                <integer>0</integer>
                <key>Comment</key>
                <string>_OSI to XOSI</string>
                <key>Count</key>
                <integer>0</integer>
                <key>Enabled</key>
                <true/>
                <key>Find</key>
                <data>X09TSQ==</data>
                <key>Limit</key>
                <integer>0</integer>
                <key>Mask</key>
                <data></data>
                <key>OemTableId</key>
                <data></data>
                <key>Replace</key>
                <data>WE9TSQ==</data>
                <key>ReplaceMask</key>
                <data></data>
                <key>Skip</key>
                <integer>0</integer>
                <key>TableLength</key>
                <integer>0</integer>
                <key>TableSignature</key>
                <data></data>
            </dict>

this is also required for HPET.aml:
Code:
<dict>
                <key>Base</key>
                <string>\_SB.PCI0.LPCB.HPET</string>
                <key>BaseSkip</key>
                <integer>0</integer>
                <key>Comment</key>
                <string>HPET _CRS to XCRS</string>
                <key>Count</key>
                <integer>1</integer>
                <key>Enabled</key>
                <true/>
                <key>Find</key>
                <data>X0NSUw==</data>
                <key>Limit</key>
                <integer>0</integer>
                <key>Mask</key>
                <data></data>
                <key>OemTableId</key>
                <data></data>
                <key>Replace</key>
                <data>WENSUw==</data>
                <key>ReplaceMask</key>
                <data></data>
                <key>Skip</key>
                <integer>0</integer>
                <key>TableLength</key>
                <integer>0</integer>
                <key>TableSignature</key>
                <data></data>
            </dict>

you can check all this yourself in the sample.plist:
 
Code:
<key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14</key>
                <dict>
                    <key>DefaultBackgroundColor</key>
                    <data>AAAAAA==</data>
                </dict>
does not belong where you have it

renames should be in this format:
Code:
<dict>
                <key>Base</key>
                <string></string>
                <key>BaseSkip</key>
                <integer>0</integer>
                <key>Comment</key>
                <string>_OSI to XOSI</string>
                <key>Count</key>
                <integer>0</integer>
                <key>Enabled</key>
                <true/>
                <key>Find</key>
                <data>X09TSQ==</data>
                <key>Limit</key>
                <integer>0</integer>
                <key>Mask</key>
                <data></data>
                <key>OemTableId</key>
                <data></data>
                <key>Replace</key>
                <data>WE9TSQ==</data>
                <key>ReplaceMask</key>
                <data></data>
                <key>Skip</key>
                <integer>0</integer>
                <key>TableLength</key>
                <integer>0</integer>
                <key>TableSignature</key>
                <data></data>
            </dict>

this is also required for HPET.aml:
Code:
<dict>
                <key>Base</key>
                <string>\_SB.PCI0.LPCB.HPET</string>
                <key>BaseSkip</key>
                <integer>0</integer>
                <key>Comment</key>
                <string>HPET _CRS to XCRS</string>
                <key>Count</key>
                <integer>1</integer>
                <key>Enabled</key>
                <true/>
                <key>Find</key>
                <data>X0NSUw==</data>
                <key>Limit</key>
                <integer>0</integer>
                <key>Mask</key>
                <data></data>
                <key>OemTableId</key>
                <data></data>
                <key>Replace</key>
                <data>WENSUw==</data>
                <key>ReplaceMask</key>
                <data></data>
                <key>Skip</key>
                <integer>0</integer>
                <key>TableLength</key>
                <integer>0</integer>
                <key>TableSignature</key>
                <data></data>
            </dict>

you can check all this yourself in the sample.plist:

Thanks. Could you please show me exactly what it should look like in proper tree? It is difficult for me to decipher the data in the format that you posted. If you could please take a screenshot of how the data above should appear in proper tree (like the attached file), I will gladly give it a try and report back....

But like I said.... It ain't broken, so I'm not sure if I should try to fix it.....
I'm not pretending to be an expert, but I am typing on a fully functional Big Sur 7010 OptiMac, so the small errors that you believe are in my EFI are not affecting the performance, and this EFI is empirically enabling USB3.

If you can post a proper tree snapshot, that would be great for those of us that want to learn how to translate what you wrote into proper tree entries. If you could show us with a screen shot exactly how it should look in proper tree, that will help all of us learn. Cheers.
 

Attachments

  • Screen Shot 2022-02-28 at 21.34.15.png
    Screen Shot 2022-02-28 at 21.34.15.png
    190.9 KB · Views: 55
Thanks. Could you please show me exactly what it should look like in proper tree? It is difficult for me to decipher the data in the format that you posted. If you could please take a screenshot of how the data above should appear in proper tree (like the attached file), I will gladly give it a try and report back....

But like I said.... It ain't broken, so I'm not sure if I should try to fix it.....
I'm not pretending to be an expert, but I am typing on a fully functional Big Sur 7010 OptiMac, so the small errors that you believe are in my EFI are not affecting the performance, and this EFI is empirically enabling USB3.

If you can post a proper tree snapshot, that would be great for those of us that want to learn how to translate what you wrote into proper tree entries. If you could show us with a screen shot exactly how it should look in proper tree, that will help all of us learn. Cheers.
true, don't fix something that isn't broken, but at least get it in a correct format...
1.jpg
 
Thank you very much. What you are saying about the patches is now crystal clear, when I look at it in proper tree. That's right--I don't have a patch for HPET, and the format the XOSI patch is different in my EFI.... I'm curious what will happen if I change that, so I will try.

You mentioned that the "4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14" does not belong where I have it. Where should it go then? Could you please show me with a proper tree screen shot?

Even though, some things may not be in the perfect format, the computer is still working great (including USB3 and sleep) with the EFI I uploaded above. I would prefer it to be perfect on paper and empirically, so I'll try these changes with USB stick EFI in the next week or so. Thank you for your advice. I really appreciate it.
 
Thank you very much. What you are saying about the patches is now crystal clear, when I look at it in proper tree. That's right--I don't have a patch for HPET, and the format the XOSI patch is different in my EFI.... I'm curious what will happen if I change that, so I will try.

You mentioned that the "4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14" does not belong where I have it. Where should it go then? Could you please show me with a proper tree screen shot?

Even though, some things may not be in the perfect format, the computer is still working great (including USB3 and sleep) with the EFI I uploaded above. I would prefer it to be perfect on paper and empirically, so I'll try these changes with USB stick EFI in the next week or so. Thank you for your advice. I really appreciate it.
4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14 section goes in the NVRAM section
check sample.plist:
https://github.com/acidanthera/OpenCorePkg/blob/master/Docs/Sample.plist

2.jpg


yes, always test on a usb stick first to make sure it works ok

if it doesn't work out well, then you didn't need those edits in the first place :)
 
Status
Not open for further replies.
Back
Top