Toggle sidebar Toggle sidebar
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

Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
dosdude1 said:
Yeah, it's your GPU that's the issue. The AMD drivers for newer cards in High Sierra (and Mojave) require the SSE4.2 instruction set, which the CPUs in the Mac Pro 3,1 do not support. Unfortunately, the only solution is to replace the card with an nVidia one.
Click to expand...

Figures... I have an AMD HD 6870 that used to be in this computer. Will that work, or have the same issue?

Thanks for the help!
[doublepost=1550517150][/doublepost]
mryingster said:
Figures... I have an AMD HD 6870 that used to be in this computer. Will that work, or have the same issue?

Thanks for the help!
Click to expand...
Sorry. I’m an idiot. I need nVidia. You clearly said that. Now, nVidia cards won’t have a boot screen will they?
 
Last edited:
mryingster said:
Figures... I have an AMD HD 6870 that used to be in this computer. Will that work, or have the same issue?

Thanks for the help!
[doublepost=1550517150][/doublepost]
Sorry. I’m an idiot. I need nVidia. You clearly said that. Now, nVidia cards won’t have a boot screen will they?
Click to expand...
Some do, for example, a GTX680 can be flashed with a Mac ROM to get a boot screen.
 
AHOY! New version of macOS installer down from the 2.6.2 patcher. Previous was 13.6.02 w/2018 date, latest is 13.6.02 with Feb.20, 2019 date. Payload is a bit bigger, too. Making a new USB stick, next.
 
I’ve installed the 2019-001 security update and now my MacBookPro5,1 is constantly refreshing the login screen. How I can fix that? Thanks...
 
mrploppy said:
I'm on HFS+. I've run Disk Utilities' First Aid and no problems.

Yes, I've seen the complaints about photoanalysisd. I'm not sure why it should even have bene doing anything yesterday because I haven't added new photos for ages.

The clue to my problem, I suspect, is in the ReportCrash that's running at the time but I can't find out what's crashed. I don't think it's an app because I don't get the warning dialog. Whatever it is that adds entries to the syslog has stopped for sure (or it's lost its connection to the file) - not sure how the new unified logging works.
Click to expand...
For those of you interested in my "Strange Goings On" a couple of pages ago, it's happened again.

This time it wasn't Dropbox that alerted me to the problem. I was trying to trash a file and it failed (I think with Error 50 but can't be sure). As before, there hadn't been any entries in the syslog for a long time since the night before (at 23:00) - it was now 13:00 the following day. I was still able to browse. In activity monitor, this time it was spindump that was consuming most cpu, but ReportCrash was there as well. In Console, I could see a lot of failures, especially those trying to create files on disk. When I did "less /var/log/system.log", it displayed a screenful of control characters, as if I was looking at a binary file - no text. The /var/log directory contained a file something like system.logT1234567 timestamped at 23:00 last night. I was hoping that this would contain a clue as to what had happened, but after a reboot the file had gone. I can't remember whether I tried to look at the contents of this file before reboot - I almost certainly did, but maybe it looked "binary" like the other syslog.

Again, it's OK after a reboot. Still in the dark. It looks like a filesystem problem - whatever that means - because anything involving writing to or reading from files doesn't work. Whether that implies a disk problem, I don't know.

Any idea where I could look for clues?
 
mrploppy said:
When I did "less /var/log/system.log", it displayed a screenful of control characters, as if I was looking at a binary file - no text.

Any idea where I could look for clues?
Click to expand...

The last time I saw anything resembling this was on a Redhat Linux system twenty years ago. There was a fault in the disk cache system that was eventually fixed in an upgrade. For a workaround I created a "cron job" (automated task) that ran the "sync" and "purge" commands once a day to flush the disk cache, which I recall did the trick at the time. Those two commands are in Darwin/MacOS, so maybe they can help you.

Do you have anything like iCloud cacheing active? Is it a spinning disk or SSD?
 
nospamboz said:
The last time I saw anything resembling this was on a Redhat Linux system twenty years ago. There was a fault in the disk cache system that was eventually fixed in an upgrade. For a workaround I created a "cron job" (automated task) that ran the "sync" and "purge" commands once a day to flush the disk cache, which I recall did the trick at the time. Those two commands are in Darwin/MacOS, so maybe they can help you.

Do you have anything like iCloud cacheing active? Is it a spinning disk or SSD?
Click to expand...
Thanks - that's interesting. It looks to me like something deep in the bowels of the system is going wrong, so that would be the kind of thing. Unfortunately, I don't have Content Caching on at all (didn't even know such a thing existed!).

My disk is a spinner.
 
dosdude1 said:
10.13.6
Click to expand...

I've upgraded from iMac late 2007 (with High Sierra Patch) to mid 2011 (supported by High Sierra) and now I can't enable SIP anymore.
I installed a fresh High Sierra on the "new" iMac and then recovered all my files and applications from a Time Machine backup. After that, I downloaded from the Appstore the latest updates until the Security Update 2019.1 and it clearly performed an EFI update (the long BEEP, the thick status bar…).
I thought that SIP was normally enabled, but in Terminal I get this:

csrutil status
System Integrity Protection status: disabled.

I booted from the recovery partition, and in Terminal I wrote "csrutil enable" and after that, a message told me that System Integrity Protection was enabled.

I reboot again but in Terminal I get again

System Integrity Protection status: disabled.

Is it possible that the SIP Disable Patch is still active on my system, even after a fresh install? Was maybe recovered from the Time Machine backup?
If I launch the Patch Updater I can see all the patches that I installed in the previous system (see screenshot), but I think this is not really the actual situation of my Mac, or is it?

I can live with SIP disabled, obviously, but since I'm using an EXP GDC Beast eGPU with Nvidia web drivers, I'm doing some experiments and I wanted to check if this setup can work even when SIP is enabled or not.
Screenshot 2019-02-24 15.40.41.png
 
gavonder said:
Sorry ahead of time as this may have been covered, but it's difficult to read through over 150 pages of info.

I have an iMac 8.1 updated to High Sierra & the wifi does not work. Any chance someone can tell me what wifi card will fit & work with this setup?

Thanks so much in advance.

GAV
Click to expand...


Anyone know??
 
gavonder said:
Anyone know??
Click to expand...

It seems that you did the upgrade without looking at this Dosdude's page that says this:

- Unsupported WiFi modules in some systems. Macs that use the Broadcom BCM4321 WiFi module will not have functional WiFi when running High Sierra. A fix for this is to open up your machine and install a compatible WiFi card. Machines affected include some MacPro3,1, MacBook5,2, MacBookPro4,1, iMac8,1, Macmini3,1, and MacBookAir2,1 systems. Please note that not all these machines will have an unsupported card, this is just a list of machines known to have shipped with that card in some configurations.

-- You can find out whether or not you have an unsupported card by opening System Profiler (About this Mac>System Report...), and clicking on WiFi under the Network section. Take note of the value listed for "Card Type".

IDs that DO NOT work under High Sierra:

- (0x14E4, 0x8C)
- (0x14E4, 0x9D)
- (0x14E4, 0x87)
- (0x14E4, 0x88)
- (0x14E4, 0x8B)
- (0x14E4, 0x89)
- (0x14E4, 0x90)

Any ID not listed, such as (0x14E4, 0x8D), is a supported card, and will work perfectly fine under High Sierra.​

If you want to change your Wifi card you can read this post on iFixit.
It's about iMac 7,1 and 9,1 but it should be the same for your model too.
I followed that guide for an iMac 7,1 and everything worked fine.
 
kautame said:
It seems that you did the upgrade without looking at this Dosdude's page that says this:

- Unsupported WiFi modules in some systems. Macs that use the Broadcom BCM4321 WiFi module will not have functional WiFi when running High Sierra. A fix for this is to open up your machine and install a compatible WiFi card. Machines affected include some MacPro3,1, MacBook5,2, MacBookPro4,1, iMac8,1, Macmini3,1, and MacBookAir2,1 systems. Please note that not all these machines will have an unsupported card, this is just a list of machines known to have shipped with that card in some configurations.

-- You can find out whether or not you have an unsupported card by opening System Profiler (About this Mac>System Report...), and clicking on WiFi under the Network section. Take note of the value listed for "Card Type".

IDs that DO NOT work under High Sierra:

- (0x14E4, 0x8C)
- (0x14E4, 0x9D)
- (0x14E4, 0x87)
- (0x14E4, 0x88)
- (0x14E4, 0x8B)
- (0x14E4, 0x89)
- (0x14E4, 0x90)

Any ID not listed, such as (0x14E4, 0x8D), is a supported card, and will work perfectly fine under High Sierra.​

If you want to change your Wifi card you can read this post on iFixit.
It's about iMac 7,1 and 9,1 but it should be the same for your model too.
I followed that guide for an iMac 7,1 and everything worked fine.
Click to expand...


I did read that & I knew I would loose wifi. I just wanted to know if there is a known card that can be swapped in.
Thanks so much for the link!
 
I have a Mac Pro 3,1 running El Capitan with an ATI 4870 and was looking to upgrade to High Sierra. Two questions:

1. will this graphics card work with High Sierra - are there any issues?
2. how can I start my Mac in Utilities mode? I tried command-R, option-command-R and all I get is the regular boot screen.
 
nospamboz said:
OK, after trying several scenarios with the 2019-001 security update, here's what works for me.

High Sierra security updates also update the Recovery HD, unlike Sierra and earlier. That recovery update process is buggy and often fails, but there's a workaround.

If you want the Recovery update:

Download and expand the security update package as in post 1. Then copy four files (AppleDiagnostics.chunklist, AppleDiagnostics.dmg, BaseSystem.chunklist, BaseSystem.dmg) from RecoveryHDMeta.dmg in EmbeddedOSFirmware.pkg in the update package, to the root of a dosdude 10.13.6 installer (replacing what's there), then boot and run the dosdude installer as usual. That resets the system to pure 10.13.6, but the Recovery HD will be the latest. (Remember that Mac OS installs do not affect installed applications or user data.) Once that's done, install the editted security update as in post 1, or simply use "softwareupdate -i -a" to install direct from Apple. Once all that's done, both your system and recovery will be up-to-date.

If you don't want the Recovery update:

Download and expand the security update package as in post 1. In addition to the edits in post 1, locate the RecoveryHDUpdate.pkg/Scripts/ directory and edit the replaceRecovery file. Edit the two lines starting "/usr/bin/hdiutil" to start "echo /usr/bin/hdiutil". Edit the two lines starting "./Tools/dm" to start "echo ./Tools/dm". (In all cases you simply add "echo " to the beginning.) Then flatten and install the update package as described in post 1. This updates your system but leaves the recovery unaffected.

(In my case I don't even have a Recovery partition. Who needs one when you have an installer stick? The second option suits me fine.)

I hope these workarounds work for other people. Please let us know if they do not.
[doublepost=1548207165][/doublepost]

Among my many, MANY jobs over the past few decades, I've been a software release manager. I know how they think. 🙂
Click to expand...


Thanks! I followed your instructions to install 2019-001 (without the Recovery update) and it seemed to work without any problems. The build number is now 17G5019 and I see the update in the "Installations" area of System Report. However, it is not listed as installed in the App Store installed area. Is that normal?
 
turtlebud said:
I have a Mac Pro 3,1 running El Capitan with an ATI 4870 and was looking to upgrade to High Sierra. Two questions:

1. will this graphics card work with High Sierra - are there any issues?
2. how can I start my Mac in Utilities mode? I tried command-R, option-command-R and all I get is the regular boot screen.
Click to expand...

Okay, so I was able to get to utilities mode by pressing option and then selecting the base install usb drive. I was able to turn off SIP from there, reboot, and do the installation. Everything seems to be working fine (fingers crossed).

Can I enable SIP now?
 
mrploppy said:
My disk is a spinner.
Click to expand...

See whether the free SMARTReporter lite 2.7.3 works on your system.

https://www.corecode.io/smartreporter_lite/

In particular, try the command-line smartctl tests, like:

sudo /Applications/SMARTReporter.app/Contents/Resources/smartctl -s on -t short /dev/disk0

More on smartctl (also for Linux) here:

https://www.thomas-krenn.com/en/wiki/SMART_tests_with_smartctl

https://www.thomas-krenn.com/en/wiki/Analyzing_a_Faulty_Hard_Disk_using_Smartctl
 
Lahmy88 said:
Hi guys,

On behalf of my Aunty, I had upgraded her Mid-2009 13” MBP to High Sierra using this patch process which went quite well 😉

Problem I now have is I’ve just migrated her data over to her new 2018 13” MBP (with Mojave installed) using her Time Machine backup and whilst browsing for things to make sure are all good (initialise Photos & iTunes, activate Office licence again etc.), I noticed the Patch Updater app in the Utilities folder and reminded me of where this data migration has come from and what it still contains.

What I would like to know is, what ‘under the hood’ operations do I have to do to remove any of the patch associated software and it’s potential effect on this new Mac (that obviously doesn’t need a patch to have the latest macOS)? Or is it just a matter of dropping the Patch Updater in trash and that’s it?

Edit: Also realised it may be responsible for the “SIP Enabled” dialog box showing up every boot?
Click to expand...
Sorry to effectively bump my own post, but haven't seen any other replies that could help. @dosdude1, I emailed you before I remembered that I had posted here sorry 😉
 
mrploppy said:
I have the same laptop and mine's OK. Which screen are you referring to? The one showing user accounts or the Apple log or what?

BTW, mine chimes twice.
Click to expand...
The one showing user account. Also mine chimes twice (it reboot before showing Apple logo)
 
avz said:
Post #4446.
Click to expand...
Thanks for reply. I had already figured out that since I had previously made a USB installer using the same patcher and OS source, it had to be macOS Mojave. Even after making the USB installer it still failed saying "no eligible packages...." so I used same patched USB installer on another Mac with the target drive connected by a SATA to USB adapter.

I think issue was related to system clock being reset to whatever the default might be when changing battery. So problem was Mojave related when using High Sierra patcher and system clock when using successfully made patched USB installer.
 
Last edited:
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back