Just wondering why there is no update to @dosdude1 installer for 3.3 beta ?
Just wondering why there is no update to @dosdude1 installer for 3.3 beta ?
Why do you feel there is a need for an update?
because it downloads downloads the 15.2 update only.
Are you saying that 15.3 is already available to the public?
Any updates needed for Mac Pro 2010 with the 10.15.3 betas (especially beta 3)? Apple has suggested some critical problems are resolved in 10.15.3 betas and would like for me to test these, but I'm a little bit hesitant given that I'm not sure if any patches will be needed @dosdude1...
[automerge]1580002680[/automerge]
10.15.3 is up to beta 3 right now. It's not "publicly" available yet - per se.
The Catalina patcher only installs point releases as not everybody wants to install a beta version since this is a widely used appJust wondering why there is no update to @dosdude1 installer for 3.3 beta ?
I don't know if it's supposed to work. For one thing, Catalina is not supported on 2009 iMac.
The latest Target Display Mode info is at:
Mac User Guide
Learn what’s new in macOS, how to get started with your Mac and use it with your Apple devices, and how to control privacy and security on macOS.support.apple.com
It seems any Mac running Catalina (or any other macOS version that has /System/Library/Extensions/AppleThunderboltEDMService.kext/Contents/PlugIns/AppleThunderboltEDMSource.kext) should be able to send Thunderbolt Target Display Mode packets to an iMac supporting Thunderbolt Target Display Mode input (/System/Library/Extensions/AppleThunderboltEDMService.kext/Contents/PlugIns/AppleThunderboltEDMSink.kext).
There are older versions of the Target Display Mode document on the wayback machine at:
Mar 17, 2016: https://web.archive.org/web/20160729123933/https://support.apple.com/en-us/HT204592
Jan 11, 2017: https://web.archive.org/web/20170210021730/https://support.apple.com/en-us/HT204592
Mar 10, 2017: https://web.archive.org/web/20190921164326/https://support.apple.com/en-us/HT204592
Dec 17, 2019: https://web.archive.org/web/20200102172421/https://support.apple.com/en-us/HT204592
According to the documents, the iMacs supporting Thunderbolt Target Display Mode are the 2011 to 2014 iMacs (non Retina).
For the 2009 and 2010 iMac, Thunderbolt is not used at all for Target Display Mode. Any computer with a DisplayPort output can connect to a 2009 and 2010 iMac. Since Thunderbolt is not used, and the input signal is DisplayPort, then I'm guessing there is some super simple mux switch to change the iMac display's input from the iMac's GPU to the iMac's DisplayPort connector.
Only the Thunderbolt Target Display Mode iMacs from 2012 to 2014 support Catalina so it makes sense that Apple might remove the DisplayPort Target Display Mode feature.
But first, read the documents to see if you missed anything. One note says:
I don't have any of those iMacs so I've never seen Target Display Mode in action. It seems to me that any Mac should be able to do Thunderbolt Target Display Mode if it's just a software thing (DMA the pixels to a buffer and transfer the buffer to the screen). Basically, Thunderbolt Target Display Mode is just a bunch of Thunderbolt packets, like Thunderbolt Target Disk Mode (macOS only), and Thunderbolt IP (macOS, Windows, Linux). If there's some extra hardware required to move those Thunderbolt packets to the display, then only the Thunderbolt Target Display Mode iMacs will work.
- If you're currently logged in on the iMac you want to use as a display, try logging out to return to the login window. Then press Command-F2 again.
The solution is to find out how High Sierra makes the DisplayPort switch (when you press Command-F2).
Command-Fn-F2 does something on my Mac mini 2018 running Catalina when I'm using the log stream command. There's a BRIGHTNESSINCREASE_DOWN event (F2 is the Brightness Increase button). There's also a "could not find smc-dppt service. Do not attempt EDM switch." message (both from the loginwindow process). EDM probably means external display mode or something like that (like in one of the Thunderbolt plugins I listed above). There's also a bunch of messages where the Intel graphics driver is reading DisplayPort (DPCD) registers and reads the display EDID.
Before use this script, you need to apply first the Sierra's swupatch (attached) from dosdude1 and Czo .
So apply first the swupatch script, then start to download a little part of OTA from Catalina Software Update, and during the downloading apply the catalinaswufix3 (hold CTRL key before open to allow unidentified developer) , then restart to install, after re-apply the post-install patches for your machine.
So on 10.15.2 on a Mac Pro 2010 that's already been installed via @dosdude1's method, running 'swupatch' seems to fail:
sudo bash /Volumes/downloads/swupatch.sh
Downloading "SUVMMFaker.dylib"...
###################################################################################################################### 100.0%
Backing up "com.apple.softwareupdated.plist"...
This file already exists in the backup location. Overwrite? (y/n): y
Continuing backup...
override rw-r--r-- root/wheel restricted for /System/Library/LaunchDaemons/com.apple.softwareupdated.plist? y
rm: /System/Library/LaunchDaemons/com.apple.softwareupdated.plist: Read-only file system
Downloading "com.apple.softwareupdated.plist"...
Warning: Failed to create the file
Warning: /System/Library/LaunchDaemons/com.apple.softwareupdated.plist:
Warning: Read-only file system
###################################################################################################################### 100.0%curl: (23) Failed writing body (0 != 2075)
Restarting softwareupdated...
Would you like to refresh available updates now? (y/n): y
Software Update Tool
Finding available software
No new software available.
\nOperation complete.\n
Apparently due to the Catalina read-only root... but what's one to do with this failure, skip it and then run yours?
sudo mount -uw / ; killall Finder
Upgraded my MacBook 7,1 (Mid2010) to Catalina - no issues - runs fine. (Upgrade to 500 Gig SSDD earlier)
I do have one question which I am fairly certain I already know the answer to and at the risk of sounding ridiculous to the MacRumor regulars..........
To Install Catalina I had to turn SIP off. I am assuming that I can't turn SIP back on and that I don't want to turn it back on (I tried but csrutil is not on the Recovery Disk and then I tried executing it off a USB and it crashed csrutil - it came from High Sierra).
So no SIP on a unsupported old MAC if you are running Catalina.
thanks
Followthebits
Much appreciated.They say that 80% of the world population don't think at all so there is nothing ridiculous about your question.
In order to run Catalina on the unsupported Mac, you have to "compromise the integrity" of your system. That is why SIP must be off.
Citation needed. Why would a GPU need video input? What GPUs have a DisplayPort input?Target Display Mode is an exclusive feature of those iMac series you indicated that requires an important GPU feature the video input (as the Capture cards).
AFAIK only ATI/AMD cards were capable to transport an input Display port video signal (while a video output signal is common to all the GPUs), so through for example a converter mini-dp to hdmi you could use the iMac display for external hdmi devices (as a tv receiver) , I guess it's very hard to patch this since Mojave, infact some users kept a small HighSierra volume (20 gb are suffice) to use TDM on their iMacs.
Use Final Cut Pro 10.4.6 or earlier. There's no way to run any Metal functionality on non-Metal GPUs.I've tried to go through this thread as best I can, but I haven't found an answer.
Running a 2011 MBP with the Intel 3000 GPU, Catalina 10.15.1 via DosDude's patch.
Final Cut version 10.4.8. Under Render/Share GPU it just says 'error,' and I get no video in the preview window. Audio is OK.
I assume this is because the iGPU doesn't support Metal.
Can this be fixed or worked around? I've seen the posts for increasing the amount of vRAM, but that's not going to trick FCPX into thinking the iGPU suddenly has Metal support.
Thanks!
Citation needed. Why would a GPU need video input? What GPUs have a DisplayPort input?
In the case of DisplayPort Target Display Mode, only a switch would be required to take DisplayPort input of the Display from the GPU to the Mini DisplayPort input.
In the case of Thunderbolt Target Display Mode, video is not being sent. Consider: if DisplayPort were being sent over Thunderbolt as normal Thunderbolt DisplayPort packets, then Macs would not need an AppleThunderboltEDMSource.kext driver and any PC with a Thunderbolt port could use the iMac as a display.
Since there is a AppleThunderboltEDMSource.kext, then it means the Thunderbolt is not transmitting DisplayPort, it is sending Thunderbolt Target Display Mode data. This might use some CPU resources - it may be interesting to compare benchmarks between using a normal Display and a Thunderbolt Target Display Mode display.
Only software would be required on the iMac side to get the Thunderbolt Target Display Mode packets to the GPU's frame buffer. Only iMacs allow this though but that could just be a limitation in the AppleThunderboltEDMSink.kext driver.
I have a late 2009 27" iMac, equipped with a ATI Radeon HD 4850 GPU.AFAIK only ATI/AMD cards were capable to transport an input Display port video signal (while a video output signal is common to all the GPUs), so through for example a converter mini-dp to hdmi you could use the iMac display for external hdmi devices (as a tv receiver) , I guess it's very hard to patch this since Mojave, infact some users kept a small HighSierra volume (20 gb are suffice) to use TDM on their iMacs.
I have a late 2009 27" iMac, equipped with a ATI Radeon HD 4850 GPU.
I can confirm that TDM works only on High Sierra and it is broken on Mojave and Catalina.
That's why I'm keeping a small High Sierra partition for that, as you explained.
Obviously, it is not the perfect solution and a patch for Catalina would be more than welcome.
If this is a Mac Pro, then you must install the Legacy Video Card Patch manually using the post-install tool, as it is not installed by default. Upgrading to a Metal-compatible video card, however, is a MUCH better option on a Mac Pro.Looks like that.
laggy system without transparency
2600XT
thanks for your answer. I have already installed the patches. No luck.If this is a Mac Pro, then you must install the Legacy Video Card Patch manually using the post-install tool, as it is not installed by default. Upgrading to a Metal-compatible video card, however, is a MUCH better option on a Mac Pro.
hello everyone,
I need some help, I have a MacBook Pro mid 2009 (5.3) Catalina is working fine (10.15.1)
but here comes the problem: when the Mac is in sleep every day it wil reboot because of a problem.
I guess it's the card reader the cause this problem, does anyone know if there is a fix for this or how to disable the card reader because I never use it
thanks in advanced
Rene
panic(cpu 1 caller 0xffffff80130279d7): "com_apple_driver_AppleUSBCardReaderInterfaceNub::setPowerState(0xffffff8034877200 : 0xffffff7f95b62f86, 2 -> 1) timed out after 30683 ms"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.41.3/iokit/Kernel/IOServicePM.cpp:5302
Backtrace (CPU 1), Frame : Return Address
0xffffff8114ba3b40 : 0xffffff8012939a3b
0xffffff8114ba3b90 : 0xffffff8012a70fe5
0xffffff8114ba3bd0 : 0xffffff8012a62a5e
0xffffff8114ba3c20 : 0xffffff80128e0a40
0xffffff8114ba3c40 : 0xffffff8012939127
0xffffff8114ba3d40 : 0xffffff801293950b
0xffffff8114ba3d90 : 0xffffff80130d17f9
0xffffff8114ba3e00 : 0xffffff80130279d7
0xffffff8114ba3e50 : 0xffffff8013027599
0xffffff8114ba3e60 : 0xffffff801303e94e
0xffffff8114ba3ea0 : 0xffffff8013026348
0xffffff8114ba3ec0 : 0xffffff801297b625
0xffffff8114ba3f40 : 0xffffff801297b151
0xffffff8114ba3fa0 : 0xffffff80128e013e
sudo kextunload /System/Library/Extensions/AppleStorageDrivers.kext/Contents/Plugins/AppleUSBCardReader.kext