macOS 10.15 Catalina on Unsupported Macs

[bige12]

there is a catalina patch out. http://dosdude1.com/catalina/

 

[L Caputo]

@L Caputo - I use the HDMI port on my 4k TCL 43" TV. However, I was able to connect a 27" Dell monitor and can get a signal on both the DVI ports, but not on the DisplayPort. I believe there are other posts that stated the same thing. At some point the DisplayPort stopped working. Hopefully, Apple will fix that in a later update, but I'm running fine with the HDMI port.

Ok so its Apples usual arseholery that has disabled the Displayport.
How do you get sound from the HDMI port, in previous versions of OS I have to install
an HDMIAudio.kext so I can select my TV in the Sound Output preferences.
Are you using anything to get sound through HDMI.

Thanks.

 

[joevt]

If the two APFS containers share the same mount point for Recoveries, after my script in the worst case the APFS Mojave Recovery would be replaced by a Catalina APFS Recovery, but that boot the same with CMD+R.

Mount points don't exist until you mount a partition. "diskutil mount Recovery" creates a mount point for the first partition with the Recovery label. The default mount point is /Volumes/Recovery. Typing "diskutil mount Recovery" again doesn't do anything because the first partition with the Recovery label is already mounted. To mount the second Recovery partition, you need to enter a unique identifier such as the disk slice "diskutil mount disk3s1". Since the default mount point is already used, diskutil appends a number e.g. "/Volumes/Recovery 1". Actually I did some tests in Catalina, and somehow got in a state where Recovery matches disk3s3 instead of disk1s3... Rebooting fixes that.

Another example if you replace the HighSierra (or El Capitan) "Recovery HD" content inside the APFS Catalina Recovery UUID path it will work too with CMD+R.

What's a Catalina Recovery UUID path? And why does it have HighSierra (or El Capitan) "Recovery HD" content? And what would I replace that content with?

The point is (till now) it's not possible to run with an "APFS Recovery role" the CMD+R with a customized/patched BaseSystem.dmg , only stock one will work due to an apple signature image integrity verification.

I thought my recovery didn't work because the folder in the Recovery partition had the wrong UUID. Now you say it also wouldn't work because the BaseSystem.dmg was not stock or that the folder UUID doesn't matter and only the non-stock BaseSystem.dmg caused the problem?

You say "till now", so what changed to make it now possible to run Recovery with a customized/patched BaseSystem.dmg? Your script uses the stock BaseSystem.dmg so you must be talking about something else.

However mine is just a simple script for those who use it from Catalina for Catalina, in this scope I don't need to retrieve the Preboot UUID.

The script is only for recreating the Recovery partition (replaces BaseSystem dmg and chunklist with stock, adds AppleDiagnostics dmg and chunklist, replaces immutablekernel with prelinkedkernel from system, and adds -no_compat_check to com.apple.Boot.plist) so I don't know why you mention Preboot UUID. What scope would you want to retrieve the Preboot UUID?

 

[kopspa]

That issue has been fixed in beta 2. Try again with the latest version.

Same problem here!

Where can I find the beta 2? On dosdude1 website, the last downloadable is 1.1.7

 

[zephar42]

Ok so its Apples usual arseholery that has disabled the Displayport.
How do you get sound from the HDMI port, in previous versions of OS I have to install
an HDMIAudio.kext so I can select my TV in the Sound Output preferences.
Are you using anything to get sound through HDMI.

Thanks.

I

Ok so its Apples usual arseholery that has disabled the Displayport.
How do you get sound from the HDMI port, in previous versions of OS I have to install
an HDMIAudio.kext so I can select my TV in the Sound Output preferences.
Are you using anything to get sound through HDMI.

Thanks.

I have external speakers connected to my MacPro, so I don't use the audio from the HDMI port. I also checked and there is no option to select the HDMI connection as an audio source.

 

[wesleyww]

Hello, I have a Macbook Pro 2009, I installed the catalina but it is freezing when using the Chrome browser, does anyone have the same problem have the solution?

 

[Starplayr]

Ok so its Apples usual arseholery that has disabled the Displayport.
How do you get sound from the HDMI port, in previous versions of OS I have to install
an HDMIAudio.kext so I can select my TV in the Sound Output preferences.
Are you using anything to get sound through HDMI.

Thanks.

I was able to hack my system literally and got the DisplayPort to function.

This is not recommended, but I have some follow up stuff that may be of interest to whoever wants to create a patch.

Using Clover and Clover Configurator, selecting only a SMBIOS profile of Mac Pro 3,1 profile for my system and only changing the Board ID to the Mac 10,1 board ID of 'Mac-F2268CC8', and using the Clover boot loader, I was able to get DisplayPort to function on a Mac Pro 3,1 with an Nvidia GTX 680 Card with 4K@60Hz on the Display Port just like it did on the the early betas.

Now I did a search high and low for that 27" iMac 2009 board ID F2268CC8 and it is present in 4 files:

IOBluetoothUSBDFUTool
IOBluetooth.framework/.../SystemParameters.plist
.../PrivateFrameworks/ServerInformation.framework/ServerInformation
/private/var/db/uuidtext/dsc/7D86856A80053540B79F20A432768DAB <!-- that # may vary

I don't know if this matters but the Mac Pro 3,1 board ID is not in the two IOBluetooth files.

Now I have not tried swapping out that data from my working Catalina Beta or tried doing any hex editing yet. It spent a good bit of time all day yesterday just swapping out .kext files to no avail.

I did see an osX86 user have the same issue and he chose a Mac Pro 6,1 profile. That just KPs my system.

Again, using Clover is not recommended and once there is a proper patch, I will discontinue using it. I think for troubleshooting purposes, it does show that the DisplayPort can still be made active on Cat 10.15 GM and this does not appear to be a Video driver issue at all. I don't even think it is actually an AppleSMBIOS or System.kext issue either as I originally had thought. Just that Apple probably removed DisplayPort access on certain configurations.

Hope this information is helpful and that someone finds a fix so Clover or another bootloader does not have to be used. Attached are some screenshots of my findings.

Also several iMac profiles do not allow the DisplayPort to be used either, so this issue could be fixed by Apple, but also they may only fix it with certain board types. We shall see what .1 and .2 bring.

If no one tackles this, I may run a few more tests next weekend. I am hoping we can collaborate on this problem as I know there are better patchers on here than me.

Only caveat to swapping on a board ID is Apple may deprecate another board ID in the future. We all might be on borrowed time, but so far I am just glad to have 4k@60Hz back and can start building my 10.15 system out.

 

[sawtoothmac]

Hi, my system is a late 2009 iMac 10.13 27, i7. A1312.
I followed Dosdude’s install video. Backed up my system to an internal Data drive using Time Machine. Installed the release version onto a memory stick. Reformatted my Mac SSD to apfs etc, and ran the install with the Patcher. No glitches, and all seemed well.

Problems started when I ran the Migration Assistant, which upon clicking on restore from a Time Machine, nothing happened. Needed a Force Quit to get out of it.

i then ran Time Machine, which doesn't recognise my Time Machine backup

Another glitch. As I loaded some of my photos to Photo, seems fine. When I double click on the images, they’re ’broken’ in psychedelic colours ????

I’ve manually restored a lot, and Catalina runs smoothly. Don't want to dig out the original software Apps, and hoped my backups would take care of things. ???

cheers, Bob

Thank you for dosdude1 and all that involve working to keep our old Macs running current OS.
I have the same problem with Photos, see pict., Final Catalina late 2009 iMac Radeon HD 4850.
Only when double click the picture though. Other than that so far no other side effects.

 

[MichelAngeloX]

I'm stuck with the Japanese Romaji input giving roman phonetic equivalents of kana. The fact that selecting kana input at Japanese Keyboard Input Sources works (but using the awful kana key layout) to display the correct Japanese character, while selecting Romaji input does not work is weird.
Everybody, including Japanese natives, uses Romaji input and not kana input so this is a big issue for the few Japanese nerds using this patch.
Do you have any ideas dosdude1 (Colin)?

I don't have the courage to go through the whole forum to see if someone has found a solution to this problem. I run Catalina on an old mid 2009 13" MBPro and I also cannot input japanese through romaji, only with the japanese hiragana keyboard layout. The romaji will just not convert into hiraganas. This is kind of a bummer for me since I live in japan and have to write in japanese quite often, for now I write on my phone but that's not very convenient. Any chance for such a fix ?

 

[nekton1]

Antony34 reports that installing either a free Google Japanese input alternative or a paid ATOK version overcomes the problem, but if you want to stick with Apple's Kotoeri it seems Asentientbot thinks the best short-term answer is to roll-back to Mojave (or get a Mac later than 2012 that officially supports Catalina). I am lucky because I do have a later model laptop so that's what I'll use for Japanese input now and the old MacPro 3,1 will be reserved for working in English.

 

[MichelAngeloX]

Antony34 reports that installing either a free Google Japanese input alternative or a paid ATOK version overcomes the problem, but if you want to stick with Apple's Kotoeri it seems Asentientbot thinks the best short-term answer is to roll-back to Mojave (or get a Mac later than 2012 that officially supports Catalina). I am lucky because I do have a later model laptop so that's what I'll use for Japanese input now and the old MacPro 3,1 will be reserved for working in English.

Thank you. Unfortunately, Google Japanese input doesn't seem to work either, when I select it my keyboard becomes straight up non functional

 

[lxmeta]

Sorry for wasting bandwidth with a success message: My mac mini from 2009 directly went from El Captain to Catalina! The dosdude1 patcher would fail when running directly from the mini (failing to load kernel extension), but after trying twice with USB, it was up and running. (failed the 1st time... just ran it again)

This is hilarious, and I never expected this to work, considering that my iMac 2011 is out (stupid Radeon HD).
One funny sidenote: It even shows the Sidecar pane in preferences! I never got this to work on my mac pro 5.1.
Congratulations and a big thank you to dosdude1 and team for reducing the waste on this planet!

 

[Vyzantion]

I was able to hack my system literally and got the DisplayPort to function.

This is not recommended, but I have some follow up stuff that may be of interest to whoever wants to create a patch.

Using Clover and Clover Configurator, selecting only a SMBIOS profile of Mac Pro 3,1 profile for my system and only changing the Board ID to the Mac 10,1 board ID of 'Mac-F2268CC8', and using the Clover boot loader, I was able to get DisplayPort to function on a Mac Pro 3,1 with an Nvidia GTX 680 Card with 4K@60Hz on the Display Port just like it did on the the early betas.

Now I did a search high and low for that 27" iMac 2009 board ID F2268CC8 and it is present in 4 files:

IOBluetoothUSBDFUTool
IOBluetooth.framework/.../SystemParameters.plist
.../PrivateFrameworks/ServerInformation.framework/ServerInformation
/private/var/db/uuidtext/dsc/7D86856A80053540B79F20A432768DAB <!-- that # may vary

I don't know if this matters but the Mac Pro 3,1 board ID is not in the two IOBluetooth files.

Now I have not tried swapping out that data from my working Catalina Beta or tried doing any hex editing yet. It spent a good bit of time all day yesterday just swapping out .kext files to no avail.

I did see an osX86 user have the same issue and he chose a Mac Pro 6,1 profile. That just KPs my system.

Again, using Clover is not recommended and once there is a proper patch, I will discontinue using it. I think for troubleshooting purposes, it does show that the DisplayPort can still be made active on Cat 10.15 GM and this does not appear to be a Video driver issue at all. I don't even think it is actually an AppleSMBIOS or System.kext issue either as I originally had thought. Just that Apple probably removed DisplayPort access on certain configurations.

Hope this information is helpful and that someone finds a fix so Clover or another bootloader does not have to be used. Attached are some screenshots of my findings.

Also several iMac profiles do not allow the DisplayPort to be used either, so this issue could be fixed by Apple, but also they may only fix it with certain board types. We shall see what .1 and .2 bring.

If no one tackles this, I may run a few more tests next weekend. I am hoping we can collaborate on this problem as I know there are better patchers on here than me.

Only caveat to swapping on a board ID is Apple may deprecate another board ID in the future. We all might be on borrowed time, but so far I am just glad to have 4k@60Hz back and can start building my 10.15 system out.

View attachment 869296View attachment 869297View attachment 869298View attachment 869299View attachment 869300

You could try a SMBIOS to point to a newer Mac Pro, in order to avoid some issues regarding updates and downloading the Catalina install app from App Store. But if this configuration seems to work, I guess you can stick to it. Do you also use FakeSMC?

 

[jackluke]

Mount points don't exist until you mount a partition. "diskutil mount Recovery" creates a mount point for the first partition with the Recovery label. The default mount point is /Volumes/Recovery. Typing "diskutil mount Recovery" again doesn't do anything because the first partition with the Recovery label is already mounted. To mount the second Recovery partition, you need to enter a unique identifier such as the disk slice "diskutil mount disk3s1". Since the default mount point is already used, diskutil appends a number e.g. "/Volumes/Recovery 1". Actually I did some tests in Catalina, and somehow got in a state where Recovery matches disk3s3 instead of disk1s3... Rebooting fixes that.


What's a Catalina Recovery UUID path? And why does it have HighSierra (or El Capitan) "Recovery HD" content? And what would I replace that content with?


I thought my recovery didn't work because the folder in the Recovery partition had the wrong UUID. Now you say it also wouldn't work because the BaseSystem.dmg was not stock or that the folder UUID doesn't matter and only the non-stock BaseSystem.dmg caused the problem?

You say "till now", so what changed to make it now possible to run Recovery with a customized/patched BaseSystem.dmg? Your script uses the stock BaseSystem.dmg so you must be talking about something else.


The script is only for recreating the Recovery partition (replaces BaseSystem dmg and chunklist with stock, adds AppleDiagnostics dmg and chunklist, replaces immutablekernel with prelinkedkernel from system, and adds -no_compat_check to com.apple.Boot.plist) so I don't know why you mention Preboot UUID. What scope would you want to retrieve the Preboot UUID?

The issue is not the "wrong UUID" (in some cases it could but not this) inside the "com.apple.boot.plist" Recovery rather is the patched/customized BaseSystem.dmg that is inherited from a patched Catalina Installer, only a createinstallmedia one will copy the unpatched BaseSystem.dmg there, I simply retrieve it from an apple catalogURL and copied it.

Each APFS current used roles S, D, V, R have internally different UUID but all point exactly to one unique UUID that is the Preboot aka B role, (that might change after each re-install or major version upgrade).

I wrote "till now" meant actually there is no way to associate to CMD+R (APFS Recovery R Role) a customized BaseSystem.dmg (the one with post-install tools), but only the stock Catalina BaseSystem.dmg.

Keeping intact the Recovery UUID structure, inside you can even copy an HighSierra Recovery and it will work with CMD+R because the HighSierra BaseSystem.dmg is also correctly apple signed.

Every Apple Recovery to work just need a BaseSystem.dmg, its chunklist, a booter plist file, a boot.efi and a prelinkedkernel.

The script could be improved with detecting the UUID, but to me this is totally unneeded, because there is no utility to keep more than an APFS Recovery (The APFS Mojave one you mentioned on the same container).

Yes, the script simply populate an APFS Recovery partition, but you haven't tried yet my script because if you run it works and I don't know why you don't trust the script since the source code is clearly unhidden hitting space bar on it.

After applied the script just from System Preferences - Startup Disk - select your Catalina Volume label, at power-on chime hold CMD+R for 15 seconds and it should work.

 

[Mikki77]

Thank you for dosdude1 and all that involve working to keep our old Macs running current OS.
I have the same problem with Photos, see pict., Final Catalina late 2009 iMac Radeon HD 4850.
Only when double click the picture though. Other than that so far no other side effects.

Guys, please read the thread properly (to avoid duplications, but I know many pages already).
The solution for messed photos in the photo app is described in comment #4672 on page 187:
Some AMD GPU cards (mainly iMacs 2009/10 affected) do not support 10bit resolution (billions of colors), but only 8bit. Therefore use a freeware tool like ResXtreme app (Version 1.0.1) and set your resolution to 8 instead of 10 bit/sample (working with Catalina 10.15 on iMac 11,1 i7).

 

[joevt]

I wrote "till now" meant actually there is no way to associate to CMD+R (APFS Recovery R Role) a customized BaseSystem.dmg (the one with post-install tools), but only the stock Catalina BaseSystem.dmg.

So instead of "until now", you mean "as of yet" or "currently".

Yes, the script simply populate an APFS Recovery partition, but you haven't tried yet my script because if you run it works and I don't know why you don't trust the script since the source code is clearly unhidden hitting space bar on it.

I didn't try it because I had already corrected the problem by using unpatched Catalina installer. I trust the script because it is unhidden. I just thought I would bring up things that might need clarification or that I had questions about. Thanks for answering my questions.

Guys, please read the thread properly (to avoid duplications, but I know many pages already).
The solution for messed photos in the photo app is described in comment #4672 on page 187

The first post is a WikiPost so confirmed problems/solutions could be added there? No one has confirmed my Recovery partition problem with supported Macs using the patched installer yet. Or my solution to the APFS startup.nsh script not searching all disks.

 

[s@chi]

I don't have the courage to go through the whole forum to see if someone has found a solution to this problem. I run Catalina on an old mid 2009 13" MBPro and I also cannot input japanese through romaji, only with the japanese hiragana keyboard layout. The romaji will just not convert into hiraganas. This is kind of a bummer for me since I live in japan and have to write in japanese quite often, for now I write on my phone but that's not very convenient. Any chance for such a fix ?

I'm also using the romaji-input. And it's working just fine.
Try something that refresh input sources, like remove and re-add the input source.

 

[Larz3n]

I have successfully installed the RTM version of Catalina on my MBP 8.3 with a faulty dGPU using Dosdudes patcher 1.1.7. I am running with the latest BlueSky as well and it works perfectly. I have one thing I'm struggling with. In order to keep my faulty GPU cool, I need to load the AMDRadeonX3000.kext, but that is not possible. There is nothing wrong with the kext itself. It just seems that the components it is dependant on have changed.

Does anyone know how to solve that? Is it maybe possible to compile a new kext file or something?

I have run kextutil -v with this result

Spoiler: Result

Defaulting to kernel file '/System/Library/Kernels/kernel'

Kext with invalid signature (-67030) allowed: <OSKext 0x7f9122c3bff0 [0x7fff98315b00]> { URL = "file:///System/Library/Extensions/IOSurface.kext/", ID = "com.apple.iokit.IOSurface" }

/AMD-kext/AMDRadeonX3000.kext appears to be loadable (not including linkage for on-disk libraries).

Loading /AMD-kext/AMDRadeonX3000.kext.

Disabling KextAudit: SIP is off

KextAudit initialized: audit=F

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The vtable '__ZTV29AMDRadeonX3000_AMDAccelDevice' is malformed. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The vtable '__ZTV29AMDRadeonX3000_AMDAccelShared' is malformed. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The super class vtable '__ZTV16IOAccelResource2' for vtable '__ZTV31AMDRadeonX3000_AMDAccelResource' is out of date. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The vtable '__ZTV31AMDRadeonX3000_AMDR8xxGLContext' is malformed. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The vtable '__ZTV32AMDRadeonX3000_AMDAccel2DContext' is malformed. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The vtable '__ZTV32AMDRadeonX3000_AMDAccelCLContext' is malformed. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The vtable '__ZTV32AMDRadeonX3000_AMDAccelMemoryMap' is malformed. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The vtable '__ZTV33AMDRadeonX3000_AMDAccelStatistics' is malformed. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The vtable '__ZTV35AMDRadeonX3000_AMDAccelEventMachine' is malformed. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The super class vtable '__ZTV20IOAccelVideoContext2' for vtable '__ZTV35AMDRadeonX3000_AMDAccelVideoContext' is out of date. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The super class vtable '__ZTV22IOGraphicsAccelerator2' for vtable '__ZTV37AMDRadeonX3000_AMDGraphicsAccelerator' is out of date. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The vtable '__ZTV29AMDRadeonX3000_AMDAccelDevice' is malformed. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The vtable '__ZTV29AMDRadeonX3000_AMDAccelShared' is malformed. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The super class vtable '__ZTV16IOAccelResource2' for vtable '__ZTV31AMDRadeonX3000_AMDAccelResource' is out of date. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The vtable '__ZTV31AMDRadeonX3000_AMDR8xxGLContext' is malformed. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The vtable '__ZTV32AMDRadeonX3000_AMDAccel2DContext' is malformed. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The vtable '__ZTV32AMDRadeonX3000_AMDAccelCLContext' is malformed. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The vtable '__ZTV32AMDRadeonX3000_AMDAccelMemoryMap' is malformed. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The vtable '__ZTV33AMDRadeonX3000_AMDAccelStatistics' is malformed. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The vtable '__ZTV35AMDRadeonX3000_AMDAccelEventMachine' is malformed. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The super class vtable '__ZTV20IOAccelVideoContext2' for vtable '__ZTV35AMDRadeonX3000_AMDAccelVideoContext' is out of date. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The super class vtable '__ZTV22IOGraphicsAccelerator2' for vtable '__ZTV37AMDRadeonX3000_AMDGraphicsAccelerator' is out of date. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The vtable '__ZTV29AMDRadeonX3000_AMDAccelDevice' is malformed. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The vtable '__ZTV29AMDRadeonX3000_AMDAccelShared' is malformed. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The super class vtable '__ZTV16IOAccelResource2' for vtable '__ZTV31AMDRadeonX3000_AMDAccelResource' is out of date. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The vtable '__ZTV31AMDRadeonX3000_AMDR8xxGLContext' is malformed. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The vtable '__ZTV32AMDRadeonX3000_AMDAccel2DContext' is malformed. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The vtable '__ZTV32AMDRadeonX3000_AMDAccelCLContext' is malformed. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The vtable '__ZTV32AMDRadeonX3000_AMDAccelMemoryMap' is malformed. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The vtable '__ZTV33AMDRadeonX3000_AMDAccelStatistics' is malformed. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The vtable '__ZTV35AMDRadeonX3000_AMDAccelEventMachine' is malformed. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The super class vtable '__ZTV20IOAccelVideoContext2' for vtable '__ZTV35AMDRadeonX3000_AMDAccelVideoContext' is out of date. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The super class vtable '__ZTV22IOGraphicsAccelerator2' for vtable '__ZTV37AMDRadeonX3000_AMDGraphicsAccelerator' is out of date. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The vtable '__ZTV29AMDRadeonX3000_AMDAccelDevice' is malformed. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The vtable '__ZTV29AMDRadeonX3000_AMDAccelShared' is malformed. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The super class vtable '__ZTV16IOAccelResource2' for vtable '__ZTV31AMDRadeonX3000_AMDAccelResource' is out of date. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The vtable '__ZTV31AMDRadeonX3000_AMDR8xxGLContext' is malformed. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The vtable '__ZTV32AMDRadeonX3000_AMDAccel2DContext' is malformed. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The vtable '__ZTV32AMDRadeonX3000_AMDAccelCLContext' is malformed. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The vtable '__ZTV32AMDRadeonX3000_AMDAccelMemoryMap' is malformed. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The vtable '__ZTV33AMDRadeonX3000_AMDAccelStatistics' is malformed. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The vtable '__ZTV35AMDRadeonX3000_AMDAccelEventMachine' is malformed. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The super class vtable '__ZTV20IOAccelVideoContext2' for vtable '__ZTV35AMDRadeonX3000_AMDAccelVideoContext' is out of date. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The super class vtable '__ZTV22IOGraphicsAccelerator2' for vtable '__ZTV37AMDRadeonX3000_AMDGraphicsAccelerator' is out of date. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The vtable '__ZTV29AMDRadeonX3000_AMDAccelDevice' is malformed. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The vtable '__ZTV29AMDRadeonX3000_AMDAccelShared' is malformed. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The super class vtable '__ZTV16IOAccelResource2' for vtable '__ZTV31AMDRadeonX3000_AMDAccelResource' is out of date. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The vtable '__ZTV31AMDRadeonX3000_AMDR8xxGLContext' is malformed. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The vtable '__ZTV32AMDRadeonX3000_AMDAccel2DContext' is malformed. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The vtable '__ZTV32AMDRadeonX3000_AMDAccelCLContext' is malformed. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The vtable '__ZTV32AMDRadeonX3000_AMDAccelMemoryMap' is malformed. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The vtable '__ZTV33AMDRadeonX3000_AMDAccelStatistics' is malformed. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The vtable '__ZTV35AMDRadeonX3000_AMDAccelEventMachine' is malformed. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The super class vtable '__ZTV20IOAccelVideoContext2' for vtable '__ZTV35AMDRadeonX3000_AMDAccelVideoContext' is out of date. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The super class vtable '__ZTV22IOGraphicsAccelerator2' for vtable '__ZTV37AMDRadeonX3000_AMDGraphicsAccelerator' is out of date. Make sure your kext has been built against the correct headers.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The __ZTV15AMDR8xxResource was not patched because its parent, the __ZTV31AMDRadeonX3000_AMDAccelResource, was not patchable.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The __ZTV16AMDR8xxCLContext was not patched because its parent, the __ZTV32AMDRadeonX3000_AMDAccelCLContext, was not patchable.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The __ZTV19AMDR8xxVideoContext was not patched because its parent, the __ZTV35AMDRadeonX3000_AMDAccelVideoContext, was not patchable.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The __ZTV26AMDR8xxGraphicsAccelerator was not patched because its parent, the __ZTV37AMDRadeonX3000_AMDGraphicsAccelerator, was not patchable.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The __ZTV27AMDBartsGraphicsAccelerator was not patched because its parent, the __ZTV26AMDR8xxGraphicsAccelerator, was not patchable.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The __ZTV27AMDCedarGraphicsAccelerator was not patched because its parent, the __ZTV26AMDR8xxGraphicsAccelerator, was not patchable.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The __ZTV27AMDTurksGraphicsAccelerator was not patched because its parent, the __ZTV26AMDR8xxGraphicsAccelerator, was not patchable.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The __ZTV28AMDCaicosGraphicsAccelerator was not patched because its parent, the __ZTV26AMDR8xxGraphicsAccelerator, was not patchable.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The __ZTV28AMDLombokGraphicsAccelerator was not patched because its parent, the __ZTV26AMDR8xxGraphicsAccelerator, was not patchable.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The __ZTV29AMDCypressGraphicsAccelerator was not patched because its parent, the __ZTV26AMDR8xxGraphicsAccelerator, was not patchable.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The __ZTV29AMDJuniperGraphicsAccelerator was not patched because its parent, the __ZTV26AMDR8xxGraphicsAccelerator, was not patchable.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The __ZTV29AMDRedwoodGraphicsAccelerator was not patched because its parent, the __ZTV26AMDR8xxGraphicsAccelerator, was not patchable.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The __ZTV30AMDRadeonX3000_AMDAccelSurface was not patched because its parent, the __ZTV15IOAccelSurface2, was not found.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The __ZTV34AMDRadeonX3000_AMDAccelDisplayPipe was not patched because its parent, the __ZTV19IOAccelDisplayPipe2, was not found.

(kernel) kxld[com.apple.kext.AMDRadeonX3000]: The __ZTV37AMDRadeonX3000_AMDAccelDisplayMachine was not patched because its parent, the __ZTV22IOAccelDisplayMachine2, was not found.

(kernel) Can't load kext com.apple.kext.AMDRadeonX3000 - link failed.

(kernel) Failed to load executable for kext com.apple.kext.AMDRadeonX3000.

(kernel) Kext com.apple.kext.AMDRadeonX3000 failed to load (0xdc008016).

(kernel) Failed to load kext com.apple.kext.AMDRadeonX3000 (error 0xdc008016).

Failed to load /AMD-kext/AMDRadeonX3000.kext - (libkern/kext) link error.
Failed to load /AMD-kext/AMDRadeonX3000.kext - (libkern/kext) link error.

Check library declarations for your kext with kextlibs(8).

And if I run kextlibs on it I get this:

Spoiler: Result

For all architectures:
com.apple.iokit.IOAcceleratorFamily2 = 438.1.23
com.apple.iokit.IOGraphicsFamily = 519.15
com.apple.iokit.IOPCIFamily = 2.9
com.apple.iokit.IOSurface = 269.6
com.apple.kpi.bsd = 19.0
com.apple.kpi.iokit = 19.0
com.apple.kpi.libkern = 19.0
com.apple.kpi.mach = 19.0

For x86_64:
106 symbols not found in any library kext.

EDIT: In the results, I have my kext in /AMD-kext, but I have also tried to have it stored i /L/E/Extensions-off. There is no difference. It can't be loaded with kextload.

 

[lamerz78]

there is a catalina patch out. http://dosdude1.com/catalina/

same as Saturday or not ?

 

[lamerz78]

If you need to disable SIP without a bootscreen, try this from your iMac HighSierra (assuming that is an HFS+ installation), open HighSierra Terminal and type:
sudo nvram boot-args="-no_compat_check"
(this should also allow to boot Catalina without patches)

Then from your HighSierra, open System Preferences - Startup Disk - pick your HighSierra Volume label, and let system reboot, right after the "power-on chime" hold CMD+R for 20 seconds, then wait at least 5 minutes, after that timeframe you should land on the official HighSierra Recovery and from there disable SIP with recovery terminal: csrutil disable

Ok thanks a lot. Tonight I’ll try.....

I’m pretty sure the system is installed over Mojave but something breaks out at the last reboot.

If I can disable SIP via Recovery From HS what do you suggest?

Trying to “fix” the installed Catalina over USB boot (wondering is all correct) and (re)apply the post install patchs or is better to perform a full installation (from HS or USB) ?

In this case is better to wipe out the exMojave/Catalina partition?

And the new one should be APFS right?

Thanks

 

[jhowarth]

I was able to hack my system literally and got the DisplayPort to function.
...
Only caveat to swapping on a board ID is Apple may deprecate another board ID in the future. We all might be on borrowed time, but so far I am just glad to have 4k@60Hz back and can start building my 10.15 system out.
...

We definitely are on borrowed time. The real question is whether Apple will bother to prune out the remaining legacy support in Catalina for the MacPro 5,1 in coming point releases? I suspect not but they definitely might inadvertently break parts of it when those sections get updated to fix bugs. As for the OS release beyond Catalina, I could see Apple bumping up their default compiler flags to expect AVX support across the board. After all, do we even have any supported machines left that don't have AVX-capable processors?

 

[Flacko]

The first post is a WikiPost so confirmed problems/solutions could be added there? No one has confirmed my Recovery partition problem with supported Macs using the patched installer yet. Or my solution to the APFS startup.nsh script not searching all disks.
[/QUOTE]
I suspect the startup.nsh script problem may have been the reason some were having problems booting to Mojave with cMP3.1 with mixed OS on separate disks. This only happened with the software APFS fix and was resolved with the APFS ROM update. See Mojave thread here: #10,452

I do not have a CAT supported machine but I am using the cMP5.1 unpatched. Using dosdude1's patcher the recovery partition is not functional. In fact, looking back at the many years and OS I have used the patcher the recovery partition was never functional. I have a vague recollection of dosdude1 confirming this somewhere but not entirely sure. Anyway, I always used the USB patcher or USB from "creatinstallmedia" to boot to a recovery if needed. Now that I do not have a boot screen I have found the recovery partition more useful. I have used this to make a fully operational recovery partition: Catalina Recovery HD Partition

 

[antony34]

Thank you. Unfortunately, Google Japanese input doesn't seem to work either, when I select it my keyboard becomes straight up non functional

I can use it without any problem...it is another case if you can not working on it...so interesting....

 

[Alex-Microsmeta]

I have activated Apple Arcade and it works fine also with my poor hardware: Core 2 Duo 2,4 GHz, 8 Gb RAM, Nvidia GeForce 320M. Remove all USB pendrives and hard disks and you will have a much faster system 4% CPU instead of 40% IDLE, due to the heavy Spotlight files indexing.

 

[chris1111]

I have used this to make a fully operational recovery partition: Catalina Recovery HD Partition
[/QUOTE]

Thank you for testing and confirm the good work of the program