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.
macOS High Sierra (10.13) Unsupported Macs Thread
- Thread starter foxlet
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Okay, looked a bit more carefully at the System Report. Evidently, DIMM Riser A/DIMM 1 and 2 are showing as empty, though I've populated them. I wonder if the riser card is having issues. I can get 24GB running using two of the DIMM slots, which really is enough for me, but a bad riser card is all I can think of.
Probably, but try changes RAM modules from position. Sometimes it helps. Mac Pro is exquisite about RAM modules.
Also If not are they all the same GBs, They must be put in a concrete order.
If nothing works maybe I have some riser that I don´t use anymore.
Anyone else with media keys (play/pause, forward, reverse) that stopped working? The same keys do work when switching to “Function” keys so it is not hardware related.
MacbookPro5,2 fresh install to 10.13.4.
Edit: Restart clears issue. Maybe random bug?
MacbookPro5,2 fresh install to 10.13.4.
Edit: Restart clears issue. Maybe random bug?
Last edited:
Hi. I'm using a 5,1 MacBook and high Sierra.
I installed it two weeks ago, fully updated.
A few days ago, it appeared a new update: 2018-001 or something like that. I installed it, and rebooted and everything was fine. Now, I have restarted again, and the keyboard and trackpad aren't working anymore.
I have done a reset of the smc and pram . Also, I have booted into the installer, and patched again and no effect.
Also usb not working. Is the patch for usb dead? Should I reinstall high Sierra ? I don't know if I can install an older version if I have installed 2018 001 patch after
What can I do??
I installed it two weeks ago, fully updated.
A few days ago, it appeared a new update: 2018-001 or something like that. I installed it, and rebooted and everything was fine. Now, I have restarted again, and the keyboard and trackpad aren't working anymore.
I have done a reset of the smc and pram . Also, I have booted into the installer, and patched again and no effect.
Also usb not working. Is the patch for usb dead? Should I reinstall high Sierra ? I don't know if I can install an older version if I have installed 2018 001 patch after
What can I do??
Last edited:
Installed Security Update on my iMac 8,1 it restarted ok so reinstalled patches one at time using Patch Updater and found that the Night Shift patch gave the same problem you had. Had to do a Time Machine restore.
+1, I found the cause of my problem (suddenly no usb, keyboard or trackpad after reboot) is also the nigh shift patch.
I reinstalled the OS without formatting nor recovering time machine, and it worked again. Installed 2018-001, and then I made like... 20 reboots. Everything fine. After that, I reinstalled night enabler and after reboot, no usb, no keyboard, no trackpad...
Again, I reinstalled the OS, without formatting, and it's working fine again. I reinstalled the nightshift patch from patch updater, and still working after reboot. 2018-001 is not installed yet.
I hope this info can help developers.
Thanks, I'll have to update the Night Shift Patch it seems.
MacPro3,1 running 10.13.4...
When trying to start in Safe-Mode, pressing the Shift key on startup.
all I get is the dreaded "circle/slash" forbidden sign.
Anyone else experience this?
Other then this issue my system works just super fine.
When trying to start in Safe-Mode, pressing the Shift key on startup.
all I get is the dreaded "circle/slash" forbidden sign.
Anyone else experience this?
Other then this issue my system works just super fine.
Attachments
Last edited:
Hello,
I've converted HFS+ to APFS in unsupported mac (Mac mini Late 2009).
Everything seems correct but now EFI boot in verbose mode. Is it possible to hide this verbose mode ?
Is it due to an issue ?
Last login: Thu May 3 21:23:14 on ttys000
Mac-mini:~ Arnaud$ diskutil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *275.1 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_APFS Container disk1 274.9 GB disk0s2
/dev/disk1 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +274.9 GB disk1
Physical Store disk0s2
1: APFS Volume SSD HIGH SIERRA 152.5 GB disk1s1
2: APFS Volume Preboot 20.3 MB disk1s2
3: APFS Volume Recovery 507.2 MB disk1s3
4: APFS Volume VM 20.5 KB disk1s4
I've converted HFS+ to APFS in unsupported mac (Mac mini Late 2009).
Everything seems correct but now EFI boot in verbose mode. Is it possible to hide this verbose mode ?
Is it due to an issue ?
Last login: Thu May 3 21:23:14 on ttys000
Mac-mini:~ Arnaud$ diskutil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *275.1 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_APFS Container disk1 274.9 GB disk0s2
/dev/disk1 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +274.9 GB disk1
Physical Store disk0s2
1: APFS Volume SSD HIGH SIERRA 152.5 GB disk1s1
2: APFS Volume Preboot 20.3 MB disk1s2
3: APFS Volume Recovery 507.2 MB disk1s3
4: APFS Volume VM 20.5 KB disk1s4
Last edited:
I had a problem playing certain videos on my iMac after updating it to High Sierra (as noted earlier in this thread). But, I appear to have fixed it.
Check out the description on this page:
http://www.martin-thoburn.com/vj/install-apple-prores-codec-without-final-cut/
And, some of the images are missing, so I used the wayback machine to see the images... check this link:
https://web.archive.org/web/2016032...install-apple-prores-codec-without-final-cut/
That's a cached image of the page with the missing pictures in place.
The directions link to an older version of Pro Video Formats. There is a newer version, currently 2.0.6. And that's what I used.
Use this link:
https://support.apple.com/kb/DL1947?viewlocale=en_US&locale=en_US
Then perform the steps in the directions using the newer version of the codecs / Pro Video Formats collection.
In my case, I put the codecs in place, and rebooted, and then tried, and everything was good. The videos started playing fine.
Now, there was a couple codecs in that pack that were already on my Mac. And, in that case, I went through and did a right click, get info, and compared version numbers for the codecs to make sure I used the most up to date version, regardless of whether it was from High Sierra or from the Codec pack.
I also copied all contents from the folders that were described in the directions, instead of just the selected / noted files. I didn't touch any other directories, only the directories described in the directions. But, for those directories, I grabbed everything, not just the ones it told me to grab. But, like I said, when there was already a comparable file, I compared version numbers to make sure I kept the most recent.
Also, I'd advise making a backup copy of your original directories before altering anything. Just so it's simple to put things back (if something went wrong).
And, yes, the Library contents are generally blocked / hidden in the Finder. Use the go menu, then down to "Go To folder" and type where you want to go.
Hope this helps you like it helped me.
Did your problem was the same as some Macbooks Pro are having? Like the iPhone X website glitch, some youtube videos, twitter gifs on tweetdeck?
I reverted to Sierra as HS doesn't have any new features I use. I don't think Apple will fix this. The only hope is the next MacOS release have this fixed and still be compatible with our machines.
My problem was certain handbrake ripped dvd movies wouldn’t play properly (most did, some didn’t) and some YouTube videos wouldn’t play properly.
They would play fine in VLC and QuickTime 7.6.6 Pro, and Apple TV streaming. But not in QuickTime 10 (High Sierra default) or iTunes.
The symptom was a scrambled looking video with audio playing fine. Similar to a blocked cable channel or bad reception on 1980’s Television signals.
The same videos and YouTube movies play fine now after adding the codecs that I linked in my prior post.
So, if I have installed the night shift patch (v.2 according to patch updater) and then I install the 2008-001 update, it will fail again, right?
Or is there any way to patch 2018-001 in order to avoid the problem/incompatibility?
Weird issues: last time, I installed 2018-001 in my Macbook5,1 with diy fussion drive using app store. Everything was fine. After that, when patching night shift and rebooting, it failed.
Now, I'm trying to install 2018-001 using the patching method explained in the first page of this thread, JIC that's the reason why it fails, and the modified installer gives me an error when approaching to the end, so it does not update...
Now, I'm trying to install 2018-001 using the patching method explained in the first page of this thread, JIC that's the reason why it fails, and the modified installer gives me an error when approaching to the end, so it does not update...
All you need to do is re-install the AMD video card patch using the Patch Updater tool, or apply it using the post-install tool, ensuring that you select "Force Cache Rebuild" before rebooting.
So if you have modified the Security Update and it fails towards the end of the install it is failing trying to install the Recovery HD update part. This is because the PlatformSupport.plist in the Recovery HD, does not have your Macs board ID and model identifier in its list. you would need to alter that, and hopefully it would fully install. Even though you get the failed notice at the end, it has installed the other parts included in the Update, just not the Recovery HD update.
As you know re-installing the NightShift patch will get NightShift back functioning.
Another thing you could do before going ahead with updates is to make a copy of the CoreBrightness.framework, this is where NightShift resides. It is located in the System> Library> PrivateFrameworks folder, copy and paste it to your Desktop, and then after you have done any OS updates or Security Updates that stop NightShift working then just copy and paste the one on your Desktop into the PrivateFrameworks folder.
You can install the security update but don't reinstall the night shift patch, you wont have night shift but that's no big deal.