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.
Sweet. To my surprise my AirPods work great this old machine. No support with El Capitan, but supported with Sierra or High Sierra. The old Bluetooth 2.1 is still fine which I guess shouldn't be a surprise since the oldest officially supported Macs also only have Bluetooth 2.1.

This really is a complete High Sierra experience.
 
  • Like
Reactions: dosdude1
I got this email earlier tonight from the Apple Beta Program

Your feedback helped us make these our best releases yet.
The iOS 11, tvOS 11, and macOS High Sierra GM candidates are now available for you to install.
Please send us any feedback you might have.
The final releases for iOS and tvOS will be available on September 19th.
And the final release for macOS will be available on September 25th.
 
thewebgal said:
I got this email earlier tonight from the Apple Beta Program

Your feedback helped us make these our best releases yet.
The iOS 11, tvOS 11, and macOS High Sierra GM candidates are now available for you to install.
Please send us any feedback you might have.
The final releases for iOS and tvOS will be available on September 19th.
And the final release for macOS will be available on September 25th.
Click to expand...
I suspect most of us who registered in the Beta program got the same email.
 
With the old MacBookPro5,5 with High Sierra, of course 4K HEVC is unplayable. However, playback is fine for 1080p 8-bit HEVC trailers and such (which are likely lower complexity than some other HEVC content). Relatively heavy CPU usage but plays smoothly.
 
EugW said:
Sweet. To my surprise my AirPods work great this old machine. No support with El Capitan, but supported with Sierra or High Sierra. The old Bluetooth 2.1 is still fine which I guess shouldn't be a surprise since the oldest officially supported Macs also only have Bluetooth 2.1.

This really is a complete High Sierra experience.
Click to expand...

That's because they officially require Sierra or later:

System Requirements
  • iPhone, iPad and iPod touch models with iOS 10 or later
  • Apple Watch models with watchOS 3 or later
  • Mac models with macOS Sierra or later
Click to expand...
 
Lubidubi said:
Just installed High Sierra GM on my MacBook Pro Early 2008 (MBP 4,1) and everything works fine!
Backlit Keyboard, Screen Brightness, Battery Indicator and Trackpad.. all good 🙂
Thanks so much DosDude1!!

Is it right that it won't be possible to update high sierra through the mac app store?
Click to expand...

@tarasis meant it probably won't be possible to upgrade from the betas to the GM through the Mac App Store. Once High Sierra is officially released and you install it and patch it, you will be able to perform regular system upgrades through the Mac App Store.
[doublepost=1505571369][/doublepost]
EugW said:
Yes I know. I just thought the hardware could be an issue too but no, it’s purely a software issue.
Click to expand...

Yeah, they work with pretty much any bluetooth device, even on 2.1, which is nice 🙂. If you use a compatible Apple device, they work with the special magic sauce thanks to the W1 chip (you get easy and fast pairing, better reliability, lower latency, etc). With any other device, they work as a plain old dumb bluetooth headphones.
 
  • Like
Reactions: dosdude1
roziek said:
Yeah, they work with pretty much any bluetooth device, even on 2.1, which is nice 🙂. If you use a compatible Apple device, they work with the special magic sauce thanks to the W1 chip (you get easy and fast pairing, better reliability, lower latency, etc). With any other device, they work as a plain old dumb bluetooth headphones.
Click to expand...
Good point about the latency but I haven’t noticed any audio latency issues on the old MBP for video playback. This is in stark contrast to some other Bluetooth headphones I’ve tried which have quite noticeable latency. I guess more important may be the speed of the processor in the headphones. Presumably the AirPods have a very fast processor minimizing latency.

Also, for the little I’ve used it on the MBP, it’s been reliable. Pairing may be a bit slower though.
 
EugW said:
Good point about the latency but I haven’t noticed any audio latency issues on the old MBP for video playback. This is in stark contrast to some other Bluetooth headphones I’ve tried which have quite noticeable latency. I guess more important may be the speed of the processor in the headphones. Presumably the AirPods have a very fast processor minimizing latency.

Also, for the little I’ve used it on the MBP, it’s been reliable. Pairing may be a bit slower though.
Click to expand...

That latency is thanks to that W1 of Apple's own making, not the processor (which is an ARM Cortex-M0+, if anyone is curious).

Try pairing and listening on, say, some Android phone. You'll probably notice latency then.
[doublepost=1505583558][/doublepost]Dave Nanian of Shirt Pocket, creator of SuperDuper! wrote a blog post about APFS, High Sierra and current state of affairs in general that's well worth a read for everyone interested in the topic and not sure about upgrading to High Sierra/converting to APFS.
 
  • Like
Reactions: tarasis
nekton1 said:
Thanks dosdude1. So the only hope for better graphics is that some later nVidia GPUs flashed with efi will do the job. Nobody has come forward to confirm this.
[doublepost=1505527587][/doublepost]I've asked on the netkas forums whether anyone has successfully used the MP3,1 with an efi-flashed recent nVidia card.
Click to expand...
Try copying all of the kexts that start with AMD (not just the bundles) from 10.12.6
 
  • Like
Reactions: rosuna
nekton1 said:
Thanks dosdude1. So the only hope for better graphics is that some later nVidia GPUs flashed with efi will do the job. Nobody has come forward to confirm this.
[doublepost=1505527587][/doublepost]I've asked on the netkas forums whether anyone has successfully used the MP3,1 with an efi-flashed recent nVidia card.
Click to expand...

I can confirm that this works. I run HS on Mac Pro 3,1 with a Nvidia 680 (flashed EVGA)
 

Attachments

  • 680.png
    680.png
    79.6 KB · Views: 303
  • mp1.png
    mp1.png
    87.5 KB · Views: 305
  • Like
Reactions: rosuna and dosdude1
While testing High Sierra GM Candiate on my Mac Pro 2008 (3,1), I encountered a strange problem. When I hit CTRL-SHIFT-SPACE to bring up track writing for Chinese, trackpad screen not showed up. and stopped accept input, until I either hit CTRL-SHIFT-SPACE again or ESC twice to exist trackpad writing mode. It is working on MacBook Pro 2017. Any one encountered the same issues. Bluetooth on Mac Pro is original chipset (not sure may be a issue on bluetooth driver or not), trackpad function as mouse and gestures works, but just not trackpad writing.. Anyone have encountered the same issues?
 
Hi

I am a newbie and was hoping someone could help me.

I upgrade installed (i.e. not clean installed) the High Sierra 10.13 (17A362a) golden master candidate on my Mid 2009 Macbook Pro (5.5) using Dosdude's Patcher (version 2.2.5).
I have a 128GB SSD installed on my Macbook Pro, so I then converted the file system from HFS to APFS by booting into my patched High Sierra usb drive, selecting diskutility, and converting to APFS.

Everything seems to be working fine but I have the following questions which I hope someone can help me with:

1) when booting a "terminal kind of screen" is shown for a few seconds before the Apple logo appears and the system boots. is it at all possible to not have this "terminal kind of screen" appear when booting ?

2) when i converted from HFS to APFS i lost around 4.4GB of drive space on my ssd. when i open diskutility and view my SSD drive i see something called "other volumes" which has a size of 4.4GB. This "other volumes" was not there prior to me converting to APFS. In the container disk I see something called "VM" with a size of 4.29GB - which I think is related in some way to the 4.4GB "other volumes".
Would it be possible to delete this 4.4GB "other volumes" and how would i go about deleting it ?

Thank you
 
mashy said:
Hi

I am a newbie and was hoping someone could help me.

I upgrade installed (i.e. not clean installed) the High Sierra 10.13 (17A362a) golden master candidate on my Mid 2009 Macbook Pro (5.5) using Dosdude's Patcher (version 2.2.5).
I have a 128GB SSD installed on my Macbook Pro, so I then converted the file system from HFS to APFS by booting into my patched High Sierra usb drive, selecting diskutility, and converting to APFS.

Everything seems to be working fine but I have the following questions which I hope someone can help me with:

1) when booting a "terminal kind of screen" is shown for a few seconds before the Apple logo appears and the system boots. is it at all possible to not have this "terminal kind of screen" appear when booting ?

2) when i converted from HFS to APFS i lost around 4.4GB of drive space on my ssd. when i open diskutility and view my SSD drive i see something called "other volumes" which has a size of 4.4GB. This "other volumes" was not there prior to me converting to APFS. In the container disk I see something called "VM" with a size of 4.29GB - which I think is related in some way to the 4.4GB "other volumes".
Would it be possible to delete this 4.4GB "other volumes" and how would i go about deleting it ?

Thank you
Click to expand...

Everything you've mentioned seems to be normal.

1) The "terminal screen" you see at startup is completely normal, that is the custom APFS bootstrap implementation being executed, as the system's firmware doesn't natively support booting from APFS volumes. Unfortunately, at this point there's not much that can be done to suppress the output of that, but I may be able to figure something out at some point.

2) That loss of space and volume configuration is normal, that's just how the APFS volume configuration is. It is necessary that those volumes remain and are not deleted.
 
dosdude1 said:
Everything you've mentioned seems to be normal.

1) The "terminal screen" you see at startup is completely normal, that is the custom APFS bootstrap implementation being executed, as the system's firmware doesn't natively support booting from APFS volumes. Unfortunately, at this point there's not much that can be done to suppress the output of that, but I may be able to figure something out at some point.

2) That loss of space and volume configuration is normal, that's just how the APFS volume configuration is. It is necessary that those volumes remain and are not deleted.
Click to expand...


Thank you for the reply and explanation Dosdude.
Sincerely appreciate it.
 
Hi,

I converted my HFS to APFS on my Mac pro (3,1) with dosdude1's APFS boot enabled, I was able to boot up successfully, However, when I restarted, it stuck on boot with white screen Apple Logo, progress bar for a long time, 10+ minutes, I decided to power down and power back up and was able to boot down up white screen Apple Logo, Black screen Apple logo, then login screen. I was able to login and everything seems to be ok. Is it nornal it stuck on boot for a long time or something not quite configure correctly?
 
parrotgeek1 said:
Try copying all of the kexts that start with AMD (not just the bundles) from 10.12.6
Click to expand...
Gets me one step further. It gives me a bright red screen with mouse pointer and the standard voiceover message, which suggests it finalizes the boot process.

Interestingly: The order of screens is standard light grey, bright red, standard dark grey with mouse pointer, bright red with pointer...
 
  • Like
Reactions: rosuna
dosdude1 said:
Everything you've mentioned seems to be normal.

1) The "terminal screen" you see at startup is completely normal, that is the custom APFS bootstrap implementation being executed, as the system's firmware doesn't natively support booting from APFS volumes. Unfortunately, at this point there's not much that can be done to suppress the output of that, but I may be able to figure something out at some point.

2) That loss of space and volume configuration is normal, that's just how the APFS volume configuration is. It is necessary that those volumes remain and are not deleted.
Click to expand...

So might it be perhapt better to stay on HFS+ for those unsupported Macs? I mean is the performance differencce big enough to give up 4GB of SSD space?
 
Thanks to this community, I've been happily running Sierra on a MBP5,5 and Mac mini 3,1, off home-brewed fusion drives. Had a few questions about the potential upgrade to High Sierra:

1. Is it safe to upgrade-in-place over Sierra? If so, is there a way to do this from the App Store? (I used to use AusEnabler to keep Sierra updated, but it has lately been giving me an "invalid certificate" error.
2. What is the recommended upgrade method (if not via App Store+AusEnabler)?
3. Any downside to waiting until after the OS upgrade to switch to AFPS?

Thanks in advance!
 
Ultracyclist said:
I keep getting these errors... Any idea? If tried reformatie multiple times.View attachment 713339
Click to expand...


have you tried opening disk utility and formatting the drive first? I had the same issue before, and that fix it for me, I believe it is not formatting the drive, from the patcher. I could be wrong though, but yeah lol that fix it for me, GL. let me know if I'm wrong please correct me, have a good day.
 
dhcyberwalker said:
have you tried opening disk utility and formatting the drive first? I had the same issue before, and that fix it for me, I believe it is not formatting the drive, from the patcher. I could be wrong though, but yeah lol that fix it for me, GL. let me know if I'm wrong please correct me, have a good day.
Click to expand...
The post you just replied to is exactly 1 month old, and back then they did mention that they had reformatted multiple times.
I'm pretty the OP has sorted this out by now.
 
  • Like
Reactions: Ultracyclist
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