Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MP 1,1-5,1 MP3,1 (& others?) SSE 4.2 emulation (to enable AMD Metal driver)
- Thread starter Syncretic
- Start date
- Sort by reaction score
Correct, with a
kextcache -i / between the overwrite and the reboot. I have updated the first post in the thread to include this information.
The black screen is a feature, not a bug! ;-)
OK, I'm assuming the following:
1) You only have one copy of MouSSE installed (i.e. not one in /S/L/E and another one in /L/E)
2) You performed a successful kernel relink (kextcache -i /) after installing MouSSE, prior to reboot
Are you able to boot to recovery, or a different copy of MacOS, and see if any logs are being generated? A blinking arrow cursor on a black screen usually means WindowServer is repeatedly crashing in the background, which in turn usually means MouSSE isn't loaded. Are you running Catalina, Mojave, or something else? Do you have a non-AMD video card that you could swap in (if needed) to check on logs and such?
OK, I'm assuming the following:
1) You only have one copy of MouSSE installed (i.e. not one in /S/L/E and another one in /L/E)
2) You performed a successful kernel relink (kextcache -i /) after installing MouSSE, prior to reboot
Are you able to boot to recovery, or a different copy of MacOS, and see if any logs are being generated? A blinking arrow cursor on a black screen usually means WindowServer is repeatedly crashing in the background, which in turn usually means MouSSE isn't loaded. Are you running Catalina, Mojave, or something else? Do you have a non-AMD video card that you could swap in (if needed) to check on logs and such?
Have only one installed, did the kext cache thing and on Mojave.
I think there might be a conflict with Refind as it seems to work when booting directly to the disk.
Anyway, rolling back to the previous from CCC for now.
Will try to figure it out later as can't debug right now.
I think there might be a conflict with Refind as it seems to work when booting directly to the disk.
Anyway, rolling back to the previous from CCC for now.
Will try to figure it out later as can't debug right now.
FWIW, I'm running Refind on a MP3,1 (no OpenCore yet), both Mojave and Catalina, so I don't think there's a direct conflict there. Let me know if I can help.
I have never tried injecting it from elsewhere (OpenCore/Clover/other), so I don't know if that will work or not. Having it linked into the kernel is normally sufficient to get it loaded before the AMD driver needs it, so injection isn't strictly necessary. (If you decide to try injecting it, I'll be curious to hear how - or if - it works).
OK. Would have a look at things over the weekend.
BTW, which version of Refind are you using? is it the one from here? https://forums.macrumors.com/threads/boot-menus-for-graphics-output-protocol.2089181/
BTW, which version of Refind are you using? is it the one from here? https://forums.macrumors.com/threads/boot-menus-for-graphics-output-protocol.2089181/
The text drawing problem in WoW is now fixed with 0.92 of MouSSE (I guess that means earlier versions were not emulating instructions 100% correctly). WoW is playable in 10.12 Sierra, 10.13 High Sierra, and 10.14 Mojave.
MouSSE hasn't worked with 10.11 El Capitan since version 0.35. WoW has extreme graphics glitches in that version of macOS so I don't think an updated MouSSE would help (WoW mentions that graphics drivers in 10.12 Sierra are old but it is still very playable). Anyone know a reason to have MouSSE work in El Capitan except that El Capitan was the last supported version of macOS that supports MacPro3,1?
I used the method (and version) in this post, and I haven't updated it since I got it working last October ("if it ain't broke, don't fix it"). I don't know offhand what version it is; I'll have a look the next time I reboot.
I will remove the reference to El Capitan in the first post of this thread.
Cheers. I believe it's the same one. Just needed to eliminate that potential item of difference.
I keep a script and run it when there's an update. Works on all macOS versions (SIP disabled):
Code:
# Copy newest version to /System/Library/Extensions and load
cd /Volumes/Updates/Misc_Software/MouSSE/MouSSE_0.92_RELEASE # for Sierra and later
#cd /Volumes/Updates/Misc_Software/MouSSE/MouSSE_0.35 # for ElCapitan
mount | grep ' on / ' | grep 'read-only' && sudo mount -uw /
kextstat | grep AAA.LoadEarly.MouSSE && sudo kextunload -b AAA.LoadEarly.MouSSE
[[ -d /AAAMouSSE.kext ]] && sudo rm -R /AAAMouSSE.kext
sudo cp -R *.kext /AAAMouSSE.kext
cd /
sudo chown -R root:wheel AAAMouSSE.kext
sudo find AAAMouSSE.kext -type d -exec /bin/chmod 0755 {} \;
sudo find AAAMouSSE.kext -type f -exec /bin/chmod 0644 {} \;
[[ -d /System/Library/Extensions/AAAMouSSE.kext ]] && sudo rm -R /System/Library/Extensions/AAAMouSSE.kext
[[ -d /Library/Extensions/AAAMouSSE.kext ]] && sudo rm -R /Library/Extensions/AAAMouSSE.kext
sudo mv AAAMouSSE.kext /System/Library/Extensions
sudo kextload -v 6 /System/Library/Extensions/AAAMouSSE.kext
kextstat | grep AAA.LoadEarly.MouSSE
sudo kextcache -i /
echo "done"Nice. Will just use KextBeast in my case.
BTW, I thought this was supposed to go into L/E and not S/L/E. Does it make a difference? I note Dosdude puts it in L/E
It doesn't much matter. I wrote MouSSE under High Sierra, and ended up needing to use /S/L/E for reasons I've since forgotten, so that started out as the preferred location. /L/E works just fine, and now that Catalina makes the root filesystem read-only, it's simpler to just use /L/E.
BTW, my Refind version shows as 0.10.3+GOPScreen+MemLog.
I clicked "Don't Remind Me Again". That option appears to stop all checks though (changes ~/Library/Preferences/com.dosdude1.Patch-Updater.plist ). Not just the one for the SSE4.1 patch (installed patches listed at /Library/Application Support/macOS Catalina Patcher/installedPatches.plist )
There doesn't seem to be an option to undo the option. I guess you can edit the file and change checkPatchIntegrity back to true?
There doesn't seem to be an option to uninstall a patch. To do that you need to understand how a patch is installed by looking at the code or scripts. There is usually two versions of a patch - one for the post installer (in code) and one for the Patch Updater (scripts). For the post installer, look at source code in github. For the patch updater, updates are downloaded from dosdude's website. see #17,966.
For what it’s worth I use OpenCore to inject this kext and have not encountered any issues with that.
The first time you booted with this, DosDude Patch Updater would have flagged the absence of the default version (I tried this a while ago and went back to just installing) and you probably clicked "Don't Remind Me Again".
From @joevt findings, this may have switched all such notifications off ... even for other components.