Clover configuration and required/related Kexts to run macOS on your GPD Pocket 2. At long last, we've got it!
Special thanks go out to Tonymacx86 user fnanao, who kindly shared their EFI folder and configuration files that helped us get to working hardware acceleration, something that had stumped me personally in the ~6 or so months I off-and-on tried to make it work.
Download Clover Configurator, mount EFI partition of newly created drive/stick, place EFI folder from this repository in there. Open config.plist
with Clover Configurator.
Under SMBIOS
click Generate New
to generate a new serial number. Copy the entire serial number and in the Board Serial Number
paste it whilst leaving the last five characters of whatever number is already there in place, so that the board serial number ends up looking like {serial number}{five more characters}
. Then go to System Parameters
and click Generate New
to create a new UUID too. While you're there, ensure Inject Kexts
is still set to Detect
. Save the config file, and you're set. Either use this EFI on a macOS Mojave installer USB stick or for an already installed system, both should work.
Required Kexts to be able to run macOS on your GPD Pocket 2 are included in this repo already. You might want to check to see if there are newer versions available, or just go ahead with what's here and start this way.
A few required or otherwise useful steps to take on a running macOS system on your GPD Pocket 2:
To correct the display orientation within macOS, press and hold down cmd+opt
(Windows+alt
) and open System Preferences
. Keep holding down those two buttons and click on Displays
(may not work with monterey). The screen orientation option will now appear even for the built-in display. Set it to 270 degrees
for the correct orientation. Alternatively...just download the Display Rotation Menu app and set the view to portrait flipped
I recommend running the following command post-installation to enable HiDPI mode (thanks to fnanao for this tip), as the default resolution of 1920x1200 makes everything quite small:
sudo defaults write /Library/Preferences/com.apple.windowserver.plist DisplayResolutionEnabled -bool true
If you started by cloning an existing system drive of another machine or if you used a USB-C hub that has built-in networking for example, you might want to fix the order of network devices to ensure things like the App Store will work. Included in this repo is NullEthernet, which I included in case you're not planning to (always) have an ethernet or wifi USB device plugged in. If you don't need this because you're always planning to have such a device plugged in, you can remove kexts/Other/NullEthernet.kext
as-well as ACPI/patched/ssdt-rmne.aml
. The easiest way to ensure the order of network devices is optimal is to delete all of them, reboot, and have macOS automatically re-populate the list (after which you can make whatever changed you might want to make). To do this, open System Preferences and head to Network
. Then use the minus button to remove each of the networks shown, selecting "yes" whenever macOS asks if it should re-add them should they appear later on again. Once you have done that, open Terminal and run the following command to fully delete the network configuration's config file:
sudo rm /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist
Then, reboot your Pocket 2. Once back in macOS, re-open System Preferences, head to Network
and you can set up VLANs or whatever else you might have to do for your network. If you want to make sure this set things up the right way, you can check the contents of the config file, searching for the interface named en0
(which, if you kept NullEthernet, should be the interface simply called "Ethernet"). To check, you can run the following command which prints out the entire file's contents for you to read through (or cmd+f
through, anyway ;):
cat /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist
Wifi dongle driver(older adapters)
Latest AutoBuild of Intel WiFi Driver & HeliPort App
* Not unless someone decides to make custom kexts for these, of course.
You can use the "right orientation" to have Clover boot in proper landscape orientation, but be aware that if you want to access Clover's boot options (e.g. enabling verbose mode, disabling loading of certain kexts, etc.) this will cause graphical issues to the point where you cannot actually read the names of these options. For this to work you must change the screen orientation in BIOS back to the screen's default mode. This is not an issue for normal usage, however, only when debugging for example, but I wanted to mention it here just in case.