Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
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.
Sleep / wake works fine for me on my MBP5,5. However, I have HS installed on the internal SSD.
Sleep/wake works fine on my MBP5,2 which has HS on APFS on an external (USB) SSD.
Also works well with an external (Firewire) spinning disk with HS on JHFS. By the way this JHFS disk was prepared as a clone of the APFS SSD using CCC5.0. Boots OK from the JHFS clone without further intervention after CCC finished.
Also everything else I've tested works perfectly well with the external APFS SSD as well as with the external JHFS spinning disk.
Confident it will be like this with the final HS release on the internal SSD with APFS. And good to know that CCC5.0 provides a working backup solution to JHFS.
(While I was not successful when I tried cloning with CCC to the spinning disk when this was formatted as APFS - perhaps not surprising after many of the contributions in this thread).
 
Is everything else working? I had thought that MBP5,2 was one of the problematic ones.
Yes it is, at least I didn't observe problems. But other than using it during a few days for the standard tasks like mailing, keynote, numbers and excel..., I didn't do more complicated things than compiling/linking a few 10000 lines of c++.
After all that, disk utility still reports the APSF on the external SSD as intact, and it still boots fine.
 
Yes it is, at least I didn't observe problems. But other than using it during a few days for the standard tasks like mailing, keynote, numbers and excel..., I didn't do more complicated things than compiling/linking a few 10000 lines of c++.
After all that, disk utility still reports the APSF on the external SSD as intact, and it still boots fine.
OK thanks. I was mistaken. It was MacBook5,2 that was the problem, not MacBookPro5,2.
 
I have a Mac Pro 3,1 with Radeon 5770 installed that I bought from Apple a while back when they still sold them. Sierra works fine on my machine. If I'm reading everything correctly here, the 5770 will not work anymore with High Sierra? Are we seeing that flashed Nvidia cards are working fine?
Just wanted to get confirmation on the above. Debating if I need to upgrade my Radeon video card to a flashed NVidia card so I can run High Sierra.
 
It is NOT the GM, it is the GM candidate and people have been asked to file reports on remaining reproducible bugs some of which will get fixed in the GM and some in the 10.13.1 release (and some much later or never).

High Sierra GM is now out (on the Dev portal). Can't get to my hackintosh to download the GM image yet as my son is playing a game in Windows.

I assume like past releases there wont be an upgrade from the betas to GM, and it will require an "upgrade" install from the USB stick.
 
Just wanted to get confirmation on the above. Debating if I need to upgrade my Radeon video card to a flashed NVidia card so I can run High Sierra.
Based on what I've seen, modern nVidia cards should work just fine. However, I haven't been able to confirm this (as I don't have a Mac Pro 3,1). If somebody is successfully using an nVidia card newer than the GeForce GT 120 in a Mac Pro 3,1 running High Sierra, then all nVidia cards should work without issue.
 
Frankly, it might be better to think of getting a pre-owned supported MP like the 2010 or 2012. Although the MP3,1 can be got to run and quite nicely too, spending quite big bucks for a flashed nVidia GPU from MacVidcards or a DIY flash of a PC Card might be a waste of money that would be better put into a later model. Apple is going to make it harder and harder to get modern GPUs running in these older Macs.
Just wanted to get confirmation on the above. Debating if I need to upgrade my Radeon video card to a flashed NVidia card so I can run High Sierra.
[doublepost=1505423044][/doublepost]Yes, I'd like to read confirmation from somebody running a higher-end nVidia card in a 3,1 too. And if you do, remember the issues with power draw over the PCIe bus.
Based on what I've seen, modern nVidia cards should work just fine. However, I haven't been able to confirm this (as I don't have a Mac Pro 3,1). If somebody is successfully using an nVidia card newer than the GeForce GT 120 in a Mac Pro 3,1 running High Sierra, then all nVidia cards should work without issue.
[doublepost=1505423116][/doublepost]BTW, the latest GM candidate build is a FULL INSTALLER; there is no update this time around.
 
Has parrot geek said this fix works or is it a shot in the dark? I know people who've tried the relevant 10.12.6 kexts and it has not worked. I'm willing to try it on the GM candidate if there is a chance.

Yes, they're from 10.12.6. Should hopefully work in 10.13, but not 100% sure.
 
Has parrot geek said this fix works or is it a shot in the dark? I know people who've tried the relevant 10.12.6 kexts and it has not worked. I'm willing to try it on the GM candidate if there is a chance.
This is just a shot in the dark, I believe. Just try it in an install you don't care about. Nether him nor I have a Mac Pro 3,1 to use for testing (it's the only one of the unsupported machines I don't actually have).
 
Has parrot geek said this fix works or is it a shot in the dark? I know people who've tried the relevant 10.12.6 kexts and it has not worked. I'm willing to try it on the GM candidate if there is a chance.
The important difference is that these are the USERLAND drivers (bundles) not kexts. You can't use 10.12 framebuffer kexts on 10.13. But you can use bundles. (my rMBP can boot 10.13 with 10.12's hd5000 bundle)
 
Dosdude, I can confirm your 2.2.5 patcher works with the 10.13 GM candidate (17A362a) full installer. Just got it up and running installing over the beta 9 install.
 
  • Like
Reactions: dosdude1
Dosdude, I can confirm your 2.2.5 patcher works with the 10.13 GM candidate (17A362a) full installer. Just got it up and running installing over the beta 9 install.
Ditto.

HighSierraMBP55-NoSerial.jpg
 
Dosdude, I can confirm your 2.2.5 patcher works with the 10.13 GM candidate (17A362a) full installer. Just got it up and running installing over the beta 9 install.

I can't wait to install the GM candidate since i'm still stuck at work. But I do have some questions before I get to try this.

I also have a MBP5,5 that has High Sierra using dosdude1's patch tool. My questions:
  • Will the GM candidate show up on my AppStore (updates) so I could update it from there?
  • or do I need to go thru the complete patch process again (using v2.2.5) - install and post patch?
Thank you for your input.

Mahalo and ~Aloha!~
 
Like the previous betas, my mid-2009 13" MacBook Pro's SSD has stayed on HFS+.
In contrast, my 2017 MacBook 12" was switched to APFS. Didn't even ask for my permission.

BTW, I had TRIM active before with Beta 9 on my 2009 MacBook Pro, and that stayed active with the install of this GM Candidate. I didn't have to reactivate TRIM.

My Service Battery warning has returned though. This is not an error, as the battery does need to be replaced (since it's the original 2009 battery), but I find it interesting that in El Capitan it said Service Battery, and then with the various High Sierra betas, the Service Battery warning disappeared. Now that I'm on the High Sierra GM Candidate, the Service Battery message has returned.

I don't know if this is just a coincidence or not, but the timing might seem to indicate the betas had different behaviour regarding the battery warning.

I also have a MBP5,5 that has High Sierra using dosdude1's patch tool. My questions:

Will the GM candidate show up on my AppStore (updates) so I could update it from there?
No.

or do I need to go thru the complete patch process again (using v2.2.5) - install and post patch?
Yes.
 
Last edited:
So my MacBook Pro Early 2008 runs an SSD, does that mean if I would upgrade to High Sierra (17A362a), Mac OS would just automatically reformat my drive to APFS without asking me, which would keep my Mac from booting?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.