MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro

[Dayo]

Probably is still a NOOP as it doesn't look like the kext innards has changed since last Sept.

Does indeed seem that RadeonBoost, a generally useless kext with a misleading name in that it only boosts Geekbench results and does not boost actual performance, is likely the culprit.

Would be interesting to see what turns up.

 

[cdf]

Odd that it includes stuff for MP41 and MP51 in that case

Since the kext is apparently built on the fly from that plist, the real board ID is probably used to indicate the data that should be used in the kext with the spoofed board ID.

But if one was to add it to their OC config, then should the board ID in the kext's plist file be the "native" one for your Mac Pro (i.e., MacPro5,1) or for the board being spoofed in the OC config ("Mac-27AD2F918AE68F61" if this guide has been followed).

I think it should be the spoofed one because that's the board ID macOS actually sees.

 

[PeterHolbrook]

I’m not following the discussion regarding the AGPM-Override kext. Are you saying that kext isn’t really necessary for Monterey 12.3?

 

[cdf]

I’m not following the discussion regarding the AGPM-Override kext. Are you saying that kext isn’t really necessary for Monterey 12.3?

Right. We'll see how things work out for @Dewdman42, but I don't think that AGPM-Override (not to be confused with ASPP-Override) is necessary in general.

 

[Dewdman42]

Add keepsyms=1 to boot-args to get more detail from the stack trace.

Booted with this arg and got more info.....pointing to Radeon....

Spoiler: kernel Panic Log

panic(cpu 4 caller 0xffffff80191d38e3): Kernel trap at 0xffffff7f9a4462bf, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x0000000003000000, CR3: 0x000000182915b03f, CR4: 0x00000000000226e0
RAX: 0xffffff7f9a446280, RBX: 0xffffff90cf36e014, RCX: 0x0000000002000000, RDX: 0x0000000003000000
RSP: 0xffffffd12eea39b0, RBP: 0xffffffd12eea39c0, RSI: 0x0000000000008200, RDI: 0xffffff90cf36e014
R8:  0xffffff8c0287d9d0, R9:  0x00000000ffffffff, R10: 0x000000000000001d, R11: 0xffffff9a6869d7c0
R12: 0xffffff7fb216bf21, R13: 0xffffff90ced3be80, R14: 0x0000000003000000, R15: 0x0000000000000006
RFL: 0x0000000000010206, RIP: 0xffffff7f9a4462bf, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x0000000003000000, Error code: 0x0000000000000002, Fault CPU: 0x4, PL: 0, VF: 1

Panicked task 0xffffff8c01d8b3b0: 10 threads: pid 167: WindowServer
Backtrace (CPU 4), panicked thread: 0xffffff959c368000, Frame : Return Address
0xffffffd12eea3360 : 0xffffff8019083e1d mach_kernel : _handle_debugger_trap + 0x41d
0xffffffd12eea33b0 : 0xffffff80191e3ca6 mach_kernel : _kdp_i386_trap + 0x116
0xffffffd12eea33f0 : 0xffffff80191d34fd mach_kernel : _kernel_trap + 0x51d
0xffffffd12eea3440 : 0xffffff8019023a60 mach_kernel : _return_from_trap + 0xe0
0xffffffd12eea3460 : 0xffffff80190841ed mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffd12eea3580 : 0xffffff80190839a6 mach_kernel : _panic_trap_to_debugger + 0x2b6
0xffffffd12eea35e0 : 0xffffff80199164af mach_kernel : _panic + 0x84
0xffffffd12eea36d0 : 0xffffff80191d38e3 mach_kernel : _sync_iss_to_iks + 0x2c3
0xffffffd12eea3850 : 0xffffff80191d35d2 mach_kernel : _kernel_trap + 0x5f2
0xffffffd12eea38a0 : 0xffffff8019023a60 mach_kernel : _return_from_trap + 0xe0
0xffffffd12eea38c0 : 0xffffff7f9a4462bf com.apple.kext.AMDRadeonX4000HWLibs : __ZN34AMDRadeonX4000_AMDRadeonHWLibsCAIL20callPlatformFunctionEPKcbPvS2_S2_S2_ + 0x16434f
0xffffffd12eea39c0 : 0xffffff7f9a500c60 com.apple.kext.AMDRadeonX4000HWLibs : __ZN34AMDRadeonX4000_AMDRadeonHWLibsCAIL20callPlatformFunctionEPKcbPvS2_S2_S2_ + 0x21ecf0
0xffffffd12eea39d0 : 0xffffff7f9a4ffa80 com.apple.kext.AMDRadeonX4000HWLibs : __ZN34AMDRadeonX4000_AMDRadeonHWLibsCAIL20callPlatformFunctionEPKcbPvS2_S2_S2_ + 0x21db10
0xffffffd12eea3a00 : 0xffffff7f99dc8d58 com.apple.kext.AMD9500Controller : __ZN22BaffinPowerPlayManager24setupPowerTuneParametersEv + 0x1c8
0xffffffd12eea3a40 : 0xffffff7f99dc8583 com.apple.kext.AMD9500Controller : __ZN22BaffinPowerPlayManager10initializeEv + 0x2a3
0xffffffd12eea3a70 : 0xffffff7f99db7cdb com.apple.kext.AMD9500Controller : __ZN17AMD9500Controller19initializePowerPlayEv + 0x8b
0xffffffd12eea3aa0 : 0xffffff7f99e0b81a com.apple.kext.AMDFramebuffer : __ZN14AMDFramebuffer14enableHardwareEv + 0x1ea
0xffffffd12eea3b00 : 0xffffff7f99dfcc20 com.apple.kext.AMDFramebuffer : __ZN14AMDFramebuffer16enableControllerEv + 0x20
0xffffffd12eea3b50 : 0xffffff7fb215bcc1 com.apple.iokit.IOGraphicsFamily : __ZN13IOFramebuffer4openEv + 0x60f
0xffffffd12eea3be0 : 0xffffff7f99dfbda0 com.apple.kext.AMDFramebuffer : __ZN14AMDFramebuffer4openEv + 0x40
0xffffffd12eea3c10 : 0xffffff7fb2151f0e com.apple.iokit.IOGraphicsFamily : __ZN13IOFramebuffer13newUserClientEP4taskPvjPP12IOUserClient + 0x25e
0xffffffd12eea3ca0 : 0xffffff8019814aac mach_kernel : __ZN9IOService13newUserClientEP4taskPvjP12OSDictionaryPP12IOUserClient + 0x6c
0xffffffd12eea3d00 : 0xffffff80198830cb mach_kernel : _is_io_service_open_extended + 0x17b
0xffffffd12eea3d60 : 0xffffff8019189b87 mach_kernel : _iokit_server_routine + 0x4967
0xffffffd12eea3db0 : 0xffffff801908a6cb mach_kernel : _ipc_kobject_set_kobjidx + 0x39b
0xffffffd12eea3e10 : 0xffffff801905ecf3 mach_kernel : _ipc_kmsg_send + 0x243
0xffffffd12eea3e60 : 0xffffff8019075249 mach_kernel : _mach_msg_overwrite_trap + 0x2c9
0xffffffd12eea3ef0 : 0xffffff80191b6198 mach_kernel : _mach_call_munger64 + 0x1d8
0xffffffd12eea3fa0 : 0xffffff8019024246 mach_kernel : _hndl_mach_scall64 + 0x16
      Kernel Extensions in backtrace:
         com.apple.iokit.IOGraphicsFamily(594.0)[3ECB2385-311A-374E-9C0F-65639BA26A05]@0xffffff7fb2141000->0xffffff7fb216ffff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[03565C8B-2960-3B32-92FD-E6E86917FE61]@0xffffff801bc03000->0xffffff801bc2efff
         com.apple.kext.AMD9500Controller(4.0.8)[73F58F88-8BFB-39FD-ADD4-B8D9169D4369]@0xffffff7f99d7f000->0xffffff7f99de3fff
            dependency: com.apple.AppleGraphicsDeviceControl(6.5.4)[3BBDC2AD-9889-3863-82EA-864DCE9D0DEF]@0xffffff7fb092c000->0xffffff7fb092ffff
            dependency: com.apple.iokit.IOACPIFamily(1.4)[CF250EA9-AE5C-3215-BCF5-763DB70A0228]@0xffffff801b760000->0xffffff801b761fff
            dependency: com.apple.iokit.IOGraphicsFamily(594)[3ECB2385-311A-374E-9C0F-65639BA26A05]@0xffffff7fb2141000->0xffffff7fb216ffff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[03565C8B-2960-3B32-92FD-E6E86917FE61]@0xffffff801bc03000->0xffffff801bc2efff
            dependency: com.apple.kext.AMDSupport(4.0.8)[C9BA70CD-D5CA-32B9-B28F-45EE36A83E3F]@0xffffff7fb0628000->0xffffff7fb06edfff
         com.apple.kext.AMDRadeonX4000HWLibs(1.0)[731EE448-F9F2-34F7-B05A-A986391D762D]@0xffffff7f9a2e0000->0xffffff7f9a5ddfff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[03565C8B-2960-3B32-92FD-E6E86917FE61]@0xffffff801bc03000->0xffffff801bc2efff
         com.apple.kext.AMDFramebuffer(4.0.8)[CCC9B796-5C11-38B9-807E-CAC9CE502386]@0xffffff7f99dfb000->0xffffff7f99e1ffff
            dependency: com.apple.iokit.IOACPIFamily(1.4)[CF250EA9-AE5C-3215-BCF5-763DB70A0228]@0xffffff801b760000->0xffffff801b761fff
            dependency: com.apple.iokit.IOGraphicsFamily(594)[3ECB2385-311A-374E-9C0F-65639BA26A05]@0xffffff7fb2141000->0xffffff7fb216ffff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[03565C8B-2960-3B32-92FD-E6E86917FE61]@0xffffff801bc03000->0xffffff801bc2efff
            dependency: com.apple.kext.AMDSupport(4.0.8)[C9BA70CD-D5CA-32B9-B28F-45EE36A83E3F]@0xffffff7fb0628000->0xffffff7fb06edfff

Process name corresponding to current thread (0xffffff959c368000): WindowServer
Boot args: keepsyms=1 debug=0x100 chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
21E230

Kernel version:
Darwin Kernel Version 21.4.0: Mon Feb 21 20:34:37 PST 2022; root:xnu-8020.101.4~2/RELEASE_X86_64
Kernel UUID: 9619904E-EA6D-3D08-89C4-B1C0451D39B8
KernelCache slide: 0x0000000018e00000
KernelCache base:  0xffffff8019000000
Kernel slide:      0x0000000018e10000
Kernel text base:  0xffffff8019010000
__HIB  text base: 0xffffff8018f00000
System model name: MacPro5,1 (Mac-27AD2F918AE68F61)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 33537706168
Last Sleep:           absolute           base_tsc          base_nano
  Uptime  : 0x00000007cf00d264
  Sleep   : 0x0000000000000000 0x0000000000000000 0x0000000000000000
  Wake    : 0x0000000000000000 0x00000026972a14e0 0x0000000000000000
Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space
Zone info:
  Foreign : 0xffffff801f6a3000 - 0xffffff801f6b1000
  Native  : 0xffffff80ce94f000 - 0xffffffa0ce94f000
  Readonly: 0xffffff859b61b000 - 0xffffff8734fb4000
  Metadata: 0xffffffe4040fe000 - 0xffffffe424bf1000
  Bitmaps : 0xffffffe424bf1000 - 0xffffffe444bf1000

last started kext at 32649545441: |IOAVB!F    1040.6 (addr 0xffffff7fb1f31000, size 77824)
loaded kexts:
com.khronokernel.FeatureUnlock    1.0.7
as.vit9696.WhateverGreen    1.5.8
as.vit9696.Lilu    1.6.0
>AGPM    127
>!AUpstreamUserClient    3.6.9
>!AMCCSControl    1.15
@kext.AMDFramebuffer    4.0.8
>AudioAUUC    1.70
>!AMikeyHIDDriver    131
>!AMikeyDriver    340.2
@kext.AMDRadeonX4000    4.0.8
>!AHDAHardwareConfigDriver    340.2
@filesystems.autofs    3.0
>!AHDA    340.2
@kext.AMDRadeonServiceManager    4.0.8
>!AGFXHDA    140.3
>!AGraphicsDevicePolicy    6.5.4
@AGDCPluginDisplayMetrics    6.5.4
>pmtelemetry    1
|IOUserEthernet    1.0.1
>!ALPC    3.1
>usb.!UUserHCI    1
>!AHV    1
>!ADiskImages2    126.100.13
>!AFWOHCI    5.7.5
@kext.AMD9500!C    4.0.8
>!AFIVRDriver    4.1.0
>!A!ISlowAdaptiveClocking    4.0.0
>!A!IMCEReporter    115
>ACPI_SMC_PlatformPlugin    1.0.0
>usb.!UHostBillboardDevice    1.0
>!AFileSystemDriver    3.0.1
@filesystems.tmpfs    1
@filesystems.lifs    1
@filesystems.hfs.kext    583.100.10
@BootCache    40
@!AFSCompression.!AFSCompressionTypeZlib    1.0.0
@!AFSCompression.!AFSCompressionTypeDataless    1.0.0d1
|SCSITaskUserClient    456.100.7
@filesystems.apfs    1934.101.3
>!I82574LEthernet    2.7.2
>AirPort.BrcmNIC    1400.1.1
>!AAHCIPort    351.100.4
@private.KextAudit    1.0
>!ARTC    2.0.1
>!AHPET    1.8
>!AACPIButtons    6.1
>!ASMBIOS    2.1
>!AACPIEC    6.1
>!AAPIC    1.7
>!A!ICPUPowerManagementClient    222.0.0
@!ASystemPolicy    2.0.0
@nke.applicationfirewall    402
|IOKitRegistryCompatibility    1
|EndpointSecurity    1
@Dont_Steal_Mac_OS_X    7.0.0
>!A!

I removed RadeonBoost.kext and it boots up fine.

I guess this means RadeonBoost is no longer compatible with MacOS 12.3 for whatever reason.

 

[Lyndon92]

Hello,
Just bought a Mac Pro 4.1 today, flashed into 5.1 , added a M2 adapter for SSD NVME.
I built Opencore, could boot on Big Sur installer. But when i have to reboot, Opencore will never show my NVME, only my Sata disks.

Any fix ? I'm using Sabrent NVME.
Thanks

 

[Macschrauber]

Hello,
Just bought a Mac Pro 4.1 today, flashed into 5.1 , added a M2 adapter for SSD NVME.
I built Opencore, could boot on Big Sur installer. But when i have to reboot, Opencore will never show my NVME, only my Sata disks.

Any fix ? I'm using Sabrent NVME.
Thanks

guess you will need to update the Mac firmware to 144.0.0.0, first by installing High Sierra, second by installing Mojave.

MP5,1: What you have to do to upgrade to Mojave (BootROM upgrade instructions thread)

Please fully read this first post, you will probably find that you have one or more problems described into the various notes below. Mojave will only install if you have upgraded your BootROM to the current release and your Mac Pro have a Metal capable GPU*. If you are trying to install Mojave...

forums.macrumors.com

or, even better, ask tsialex for a bootrom reconstruction. 4.1-5.1 crossflash have a high chance for firmware issues. With a rebuilt firmware you dont need to do all those installations for a firmware update.

 

[Lyndon92]

guess you will need to update the Mac firmware to 144.0.0.0, first by installing High Sierra, second by installing Mojave.

MP5,1: What you have to do to upgrade to Mojave (BootROM upgrade instructions thread)

Please fully read this first post, you will probably find that you have one or more problems described into the various notes below. Mojave will only install if you have upgraded your BootROM to the current release and your Mac Pro have a Metal capable GPU*. If you are trying to install Mojave...

forums.macrumors.com

or, even better, ask tsialex for a bootrom reconstruction. 4.1-5.1 crossflash have a high chance for firmware issues. With a rebuilt firmware you dont need to do all those installations for a firmware update.

Thank you for your reply but i alread did that.
In fact, Mojave will show me the NVME. Only Opencore picker (when booting) doesn't detect it.

 

[Macschrauber]

Stick in a GPU with native boot screen, like the GT120 or HD5770.

If the native boot picker also dont show the nvme it has nothing to do with openCore.

 

[Lyndon92]

https://ibb.co/ysXg2S9 This is my actual bootrom, is that the problem maybe ?
Is it flashed to 144.00 ? I'm a bit lost.
EDIT : Fixed, built again OC without MartinLO Package

 

[Macschrauber]

https://ibb.co/ysXg2S9 This is my actual bootrom, is that the problem maybe ?
Is it flashed to 144.00 ? I'm a bit lost.
EDIT : Fixed, built again OC without MartinLO Package

this is the fake Firmware Version String OpenCore injects.

use an old System without OpenCore or my Dumper to get the real Firmware Version.

Dropbox - File Deleted - Simplify your life

www.dropbox.com

 

[PeterHolbrook]

use an old System without OpenCore or my Dumper to get the real Firmware Version.

Does your Dumper work even when the computer is booted via OpenCore?

 

[Macschrauber]

Does your Dumper work even when the computer is booted via OpenCore?

yes, it decodes the firmware version directly from the dumped file, not via system calls.

 

[PeterHolbrook]

I meant the dumping process itself. Is it valid even when booted via OpenCore?

 

[Macschrauber]

I meant the dumping process itself. Is it valid even when booted via OpenCore?

yes, as written, it dumps directly the spi flash chip, no system calls were used.

of course there are some nvram settings OpenCore writes into the nvram, but those stay in the nvram when you boot natively.

But for the best, prestine dump - and for checking the health of the firmware - the best way to dump is:

-force a manual garbage collection (four times nvram reset, hold the keys all the time and dont release them until you hear the 4th chime). OpenCore Blessing and all personal nvram settings are deleted and you have to re-bless OC after.
-boot a system without s.i.p (I use mavericks)
-dump the rom, it should have 2nd store empty and one set of variables in the first store with plenty of free space

if this prestine dump has problems you should considder a firmware reconstruction


... if you "just" need a rom dump for reconstruction - or want to check the state as is - imo it is ok dumping with OC.

 

[tyroiii]

I have a cMP 5.1 that I just upgraded to 12.3 using Martin Lo's instructions on OC 0.7.7. The only addition that I added was the ASPP-Override.kext so I can boot with VMM off. As part of the upgrade, I also upgraded the BT to 4.0 using card from iMac 2015. Everything seems to be working well except for Universal Control. I see the preference pane on the display preference. They are on the same WIFI network and I have turned off my ethernet. Handoff is working, airplay works. However, I am not able to get the link keyboard to show up. I have a 2021 MBP on 12.3 and I can use universal control with my iPad, but it is not working on the cMP. Any suggestions on areas that I can look to see if I can get this working?

Thanks in advance.

Update: I made a few additional attempts to get UC working:
1) changed the SMBIOS spoof to MacPro 7.1 vs iMacPro 1.1.
2) used a second iPad with a different appleid and logged into my Mac with a new logon and appleid, to avoid conflict with my MBP.

Both attempts did not work. I looked through my console and found this error, not sure it it's related.
bluetoothd - stopTrackingForSession: sensor tracking is not supported on this platform

Parts of UC works, I am able to copy a file from my cMP and paste it on my MBP. However, I can not sure the keyboard/mouse, which is really what I want to do.

 

[sfalatko]

I have a cMP 5.1 that I just upgraded to 12.3 using Martin Lo's instructions on OC 0.7.7. The only addition that I added was the ASPP-Override.kext so I can boot with VMM off. As part of the upgrade, I also upgraded the BT to 4.0 using card from iMac 2015. Everything seems to be working well except for Universal Control. I see the preference pane on the display preference. Handoff is working, airplay works. However, I am not able to get the link keyboard to show up. I have a 2021 MBP on 12.3 and I can use universal control with my iPad, but it is not working on the cMP. Any suggestions on areas that I can look to see if I can get this working?

Thanks in advance.

It is working for me - it seemed to start working after I hard reset my iPad. Let the iPad sit active near your cMP with your MBP off and see if it works after a bit. I don't know any magic other than making sure the preferences are set on both cMP and iPad.

 

[Dewdman42]

Universal control works for me, but my only complaint is that MacOS incorrectly determines the location of my iPad relative to my actual cheese grater on the floor....and so its on the wrong side for the feature to work correctly.

 

[tyroiii]

Universal control works for me, but my only complaint is that MacOS incorrectly determines the location of my iPad relative to my actual cheese grater on the floor....and so its on the wrong side for the feature to work correctly.

You can goto the display settings to change the orientation of the iPad relative to the display.

 

[Dewdman42]

really? Where is that? I'm not talking about sidecar...which does not work with the 5,1

 

[abe101]

This guide explains how to use the excellent OpenCore boot loader to install, run, and update the latest version of macOS on the MacPro5,1, resulting in a clean, unaltered operating system just like on a supported Mac.

View attachment 1899553

Hi everyone I'm new to the forum and opencore as well. So far I have OCLP running on my flashed cMP 5,1 running Big Sur 11.2.3 and everything works perfectly. Now I have some software that requires windows to run and that's were I've been stuck. I tried following the guide here and on dortania to no avail. I changed the configplist in the OC folder as well as putting the exFat driver into the proper place, but everytime I restart to the bootloader, my windows usb does not show up as the guides say it would. If someone could please help I'd really appreciate it! Thanks!

 

[flaubert]

Ever since the Meltdown and Spectre attacks became public, I've always been conscious of the fact that I'm running my Mac with a pretty vulnerable CPU (due to its age). Consequently, on operating systems up through Mojave I turned off Hyperthreading feature, using the instructions here:

How to enable full mitigation for Microarchitectural Data Sampling (MDS) vulnerabilities - Apple Support

This option is available for macOS Mojave, High Sierra, and Sierra after installing security updates.

support.apple.com

Now that I'm on Monterey 12.3, I'd like to implement the same protection (I don't need to worry about cutting the apparent number of processors from 24 down to 12 for what I do on my Mac Pro).

The instructions are pretty simple: you need a string in boot-args, and you need to store a parameter in NVRAM. I know where the boot-args string is under NVRAM section of config.plist, so I can modify that easily. The instructions for the NVRAM portion look simple enough:

nvram SMTDisable=%01

It seems like this should go under NVRAM > Add in the plist file, but it needs a dictionary identifier, right? How would I come up with that? Examine a ROM dump from my Mojave machine to see where I might find SMTDisable? Or does someone happen to know what dictionary identifier might work?

Thanks, as always, for your advice.

 

[hwojtek]

really? Where is that? I'm not talking about sidecar...which does not work with the 5,1

Did you check your Displays prefpane and tried to move the green one around?

 

[cdf]

It seems like this should go under NVRAM > Add in the plist file, but it needs a dictionary identifier, right? How would I come up with that? Examine a ROM dump from my Mojave machine to see where I might find SMTDisable? Or does someone happen to know what dictionary identifier might work?

For a list of variables and GUIDs, see

NVRAM Variables

docs.google.com

Unfortunately, SMTDisable is not included in that list. However, I'm pretty sure that the variable has the AppleBoot GUID. So under under NVRAM > Add, you would just add

<key>SMTDisable</key>
<data>AQ==</data>

to the dictionary of the key 7C436110-AB2A-4BBB-A880-FE41995C9F82 (the same one as for boot-args).

 

[TECK]

Did you check your Displays prefpane and tried to move the green one around?

Not related to this thread, but the "green one" is related to your iPad wallpaper, which is green. I use the default wallpaper on both devices.

I posted this reply because I had a hard time getting the Universal Control working, the trick that did it for me was to sign-out and sign-in into iCloud, on my iPad mini. Anything else would not work. Devices are not connected through Bluetooth:

@Dewdman42 if you have the third option checked like I do, when you unlock the iPad display, it will automatically connect if is nearby your Mac. I have my iPad mini on my desk about 5 feet away from my Mac and it automatically connects. Bluetooth does not affect this functionality, since devices are not connected through Bluetooth. If you are too far, you cannot connect, even by forcing a connection to the iPad from "Add Display" dropdown menu on your Mac.

If you don't have the third option enabled, follow these steps:

1. Unlock iPad
2. Open System Preferences > Displays on your Mac
3. Add Display > Link Keyboard and Mouse > iPad

This is what you should see when everything is connected correctly: