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.
You need to apply the APFS patch in the post-install tool.

Hi and many thanks for your help. I did convert my SSD to APFS, applied the patch and everything works. The boot time increased (no problem) but right after startup I get this scrolling command line screen before the apple appears. Is this normal behavior?
 

Attachments

  • IMG_4582.jpg
    IMG_4582.jpg
    92.6 KB · Views: 405
Hi and many thanks for your help. I did convert my SSD to APFS, applied the patch and everything works. The boot time increased (no problem) but right after startup I get this scrolling command line screen before the apple appears. Is this normal behavior?

Yes, that's what makes booting from APFS volumes possible on unsupported Macs.
 
I guess I can live with it. Feels a bit like the old days of MSDOS. :)
Yeah, it works fine, but given the DOS-like aesthetics, I reverted to HFS+ for these old machines. The scrolling text would freak out my wife too. Also, the Recovery Partition doesn't work on APFS, but that's OK, because we can use the USB method. So if it's your only machine and you're on APFS, it may pay to keep a patched USB drive installer around just in case.

Luckily it doesn't matter as much for us for our two patched HS machines. They're secondary machines for us, and we keep them fairly clean mainly for basic light office type use and surfing, so the advantages of APFS are not quite as significant for us on these. My two main drivers however are 2017 models, and they are APFS (mandatory).

It should be noted too that APFS has some bugs that I've already come across on my supported machines.

---

BTW, Office 2016 loads really slowly on these old Core 2 Duo SATA II SSD machines (MacBookPro5,5, MacBook5,1) despite both having 8 GB and SSD. Runs fine after loading, but it really emphasizes the age of these machines. Office 2011 is quicker to load, but there are rare minor bugs with Office 2011 in High Sierra (patched or not) that may never get fixed, as it is not officially supported. Pick your poison.
 
Last edited:
As one of the users having issues with the ATI Radeon HD 5770 card - i.e. red artefacts during certain screen activity, and the major issue with waking from sleep, I ordered a refurbished nVidia GTX 285 from eBay which arrived this morning.

Having removed the 5770 and installed the nVidia GTX 285, it would seem that High Sierra is working smoothly so far. There are no red flashes on the switch to full screen or when scrolling PDFs in preview; I visited the iPhone X website, and that all displayed correctly; videos play correctly in preview, Quicktime and within Safari. The Mac wakes from sleep with no issues so far.
View attachment 722868

This seems very interesting. May I know which GTX 285 ? I have a few questions :
- is it a native PC Card ?
- Do you need to flash it ?
- Do you have to install the Nvidia drivers ?
- Do you have the boot screen (to select a boot drive) ?
 
Yeah, it works fine, but given the DOS-like aesthetics, I reverted to HFS+ for these old machines. The scrolling text would freak out my wife too.

can you revert back without doing a clean install? 'cause whatever benefits of APFS, a clean and fast boot are more important to me.
 
can you revert back without doing a clean install? 'cause whatever benefits of APFS, a clean and fast boot are more important to me.
Dunno. I did a clean install back to HFS+. Also, dosdude1 earlier provided a command to delete the extra EFI partition that is unused with HFS+. (The clean install of HFS+ overwrote the APFS partition, but did not delete the EFI partition IIRC.)
 
Dunno. I did a clean install back to HFS+. Also, dosdude1 earlier provided a command to delete the extra EFI partition that is unused with HFS+. (The clean install of HFS+ overwrote the APFS partition, but did not delete the EFI partition IIRC.)

Here is what Apple posted for Fusion hard drive users to migrate back from APFS to HFS+ for the final GM release of High Sierra...

https://beta.apple.com/sp/betaprogram/apfsfusion
 
BTW, Office 2016 loads really slowly on these old Core 2 Duo SATA II SSD machines (MacBookPro5,5, MacBook5,1) despite both having 8 GB and SSD. Runs fine after loading, but it really emphasizes the age of these machines. Office 2011 is quicker to load, but there are rare minor bugs with Office 2011 in High Sierra (patched or not) that may never get fixed, as it is not officially supported. Pick your poison.

That's why I said — many posts back — that C2D is not up to snuff these days, no matter the SSD or amount of RAM, unless for a very light use :). I too still have two C2D machines (MacBookPro 5,1 and MacBook 3,1) that get used from time to time — and they're painful to use (both have SSDs and sufficient amount of RAM) for anything even a little bit more demanding.

Although I guess that's subjective; what's slow and painful to me might be perfectly acceptable to someone.
 
That's why I said — many posts back — that C2D is not up to snuff these days, no matter the SSD or amount of RAM, unless for a very light use :). I too still have two C2D machines (MacBookPro 5,1 and MacBook 3,1) that get used from time to time — and they're painful to use (both have SSDs and sufficient amount of RAM) for anything even a little bit more demanding.

Although I guess that's subjective; what's slow and painful to me might be perfectly acceptable to someone.
Definitely subjective. IMO for Office 2011, email, surfing, banking, etc. the speed is OK, with a clean install, SSD, and 8 GB RAM.

Put it this way. I have my 2017 Core m3 MacBook in my home office and my 2008 MacBook5,1 in my kitchen/living room one floor down. If I am already in the living room and want to surf MacRumors and check my email, I just grab the MacBook5,1 and have no big issues with the speed. If I want to do a big PowerPoint editing session though, I'll go upstairs and use neither. I will use my dual 27" screen iMac.
 
I ordered a GTX 680 2 GB card to replace my 5770. Hopefully with this I can limp along and see a bit of boost until i replace this beloved but aged Mac Pro. Will report back after I install it.
 
This seems very interesting. May I know which GTX 285 ? I have a few questions :
- is it a native PC Card ?
- Do you need to flash it ?
- Do you have to install the Nvidia drivers ?
- Do you have the boot screen (to select a boot drive) ?

1. The card is a native Mac card (Apple Mac Pro nVidia GTX285 1GB Dual DVI CUDA) ...
2. ... therefor no need to flash it
3. No additional installs over and above the magnificent dosdude1's patches
4. It boots completely normally, and if I hold the option key I get the choice of boot disks.
 
Last edited:
  • Like
Reactions: dabotsonline
i have strange problem with my high sierra installation. my app store updates and installations works only when i enable SIP, when disabled app store just freezes. any ideas? @dosdude1 ? i am on macbook 5,1
 
  • Like
Reactions: Teutone
I ordered a GTX 680 2 GB card to replace my 5770. Hopefully with this I can limp along and see a bit of boost until i replace this beloved but aged Mac Pro. Will report back after I install it.

Yeah, it should serve you well. And if I'm not mistaken, GTX 680 is the highest model that's supported natively by the system (built-in drivers), so you won't have to install nVidia's Web Driver, which is really not yet ready for High Sierra and could cause you problems.
 
Yeah, it should serve you well. And if I'm not mistaken, GTX 680 is the highest model that's supported natively by the system (built-in drivers), so you won't have to install nVidia's Web Driver, which is really not yet ready for High Sierra and could cause you problems.

Yup, call me old fashioned, but I wanted a completely native card and not one that would not work until custom drivers engage. If I wanted the best speeds I'd go for a higher end card, but then again I'd also go for a newer machine at that point.
 
@dosdude1 is there a workaround for the mouse issues and backlight on the Macbook 5,2? I can't even use touch scrolling on my trackpad anymore, and the workarounds for 10.12 don't work, nor do the el capitan brightness frameworks (I can't even open display settings with the el capitan display services framework). Losing tap-to-click and two-finger right click was a minor annoyance, but I'm surprised touch scrolling doesn't work at all now for me. Comes with the territory of installing unsupported software for sure, but none the less surprising.
 
@dosdude1 is there a workaround for the mouse issues and backlight on the Macbook 5,2? I can't even use touch scrolling on my trackpad anymore, and the workarounds for 10.12 don't work, nor do the el capitan brightness frameworks (I can't even open display settings with the el capitan display services framework). Losing tap-to-click and two-finger right click was a minor annoyance, but I'm surprised touch scrolling doesn't work at all now for me. Comes with the territory of installing unsupported software for sure, but none the less surprising.
Did you check the patch updater? Both of those patches should be available from there.
 
Did you check the patch updater? Both of those patches should be available from there.

Nevermind, I got it working through kext replacement. Even got the keyboard buttons working again. Still can't view display settings however; Is this part of the patch updater?
 
I've installed High Sierra on a MacBook Pro Mid-2009 17" (macbookpro5,2) using macOS High Sierra Patcher 2.3.1. Kudos to @dosdude1 for the tool - it's nicely designed and extremely easy to use.

So far, everything works as you would expect on a supported machine, except for sleep: If I close the macbook's lid, it obviously doesn't go to sleep. Apparently, just the display's backlight is turned off and the (in case of sleep) normally pulsing LED remains permanently on. If the lid is re-opened, the LED is turned off again and the display's backlight is returning at some point (it's often necessary to either press some keys or to remove the power cord from the machine to get the display into a lightened state again).

I'm currently a bit unsure whether that behaviour is owed to the fact that I'm on an unsupported machine or if it's a bug generally affecting older, also supported MacBook Pros, because the dozens of reports of such problems in Apple's own forums would suggest it's the latter and you're actually not better off with a supported machine.

Update: Further analysis has revealed sleep mode actually is working most of the time, but needs ~40 seconds (!) to get activated after the macbookpro5,2's lid is closed. For these ~40 seconds, the Sleep Indicator Light (SIL) will be on permanently, it will start pulsing afterwards.

This happens on an HFS+ installation upgraded from Sierra, but neither booting into safe mode nor booting a clean High Sierra install from an external drive has shown a different behaviour.

In some rare cases, sleep does not get activated at all, not even after the above-mentioned ~40 seconds.

If anybody has made similar or contrary observations on this sleep issue, I'd be more than happy if you could share them.
 
Update: Further analysis has revealed sleep mode actually is working most of the time, but needs ~40 seconds (!) to get activated after the macbookpro5,2's lid is closed. For these ~40 seconds, the Sleep Indicator Light (SIL) will be on permanently, it will start pulsing afterwards.

This happens on an HFS+ installation upgraded from Sierra, but neither booting into safe mode nor booting a clean High Sierra install from an external drive has shown a different behaviour.

In some rare cases, sleep does not get activated at all, not even after the above-mentioned ~40 seconds.

If anybody has made similar or contrary observations on this sleep issue, I'd be more than happy if you could share them.
Sleep works fine with MacBookPro5,5 and MacBook5,1.

I estimate it takes about 15 seconds for the light to start pulsing. Before it is pulsing it is solid. Wake from this pulsing sleep mode is just a couple of seconds.

Battery energy loss is 1-2% per hour during sleep. That 2% percentage is high, but that’s because the capacity of both batteries is low now, as both are still the original batteries from 2008/2009! The batteries still report a capacity that is about 2/3rds of normal, to my surprise. I suspect the energy loss would be closer to 1% on a new battery, at least for the MacBook Pro, since its new battery capacity is larger. The MBP is reporting 39xx out of 5800, and the MB is reporting 3475 out of 4800.
 
Last edited:
@Hackintosh HD: Perhaps that long period until sleep is because of "your" Hibernate mode. It of course takes some time to write the sleep image. You could type "pmset -g | grep hibernate" in the terminal; the result will be the type of hibernation. Maybe sleep image will be written always (hibernate mode 1, as far as I know)
You could try "sudo pmset -a hibernatemode 0" which sets the mode to not saving anything to disc. Should be the fastest sleep mode.
 
@Hackintosh HD: Perhaps that long period until sleep is because of "your" Hibernate mode. It of course takes some time to write the sleep image. You could type "pmset -g | grep hibernate" in the terminal; the result will be the type of hibernation. Maybe sleep image will be written always (hibernate mode 1, as far as I know)
You could try "sudo pmset -a hibernatemode 0" which sets the mode to not saving anything to disc. Should be the fastest sleep mode.

@EugW , @virk : Many thanks for your feedback! "pmset -g" reveals my macbookpro5,2 is on hibernatemode 3, the default for MacBooks, which will indeed write its RAM contents to /var/vm/sleepimage entirely while maintaining the RAM's voltage. That's a bit strange, because I remember macOS 10.12 Sierra was much faster at that, but it's possible my MBP was on hibernatemode 0 during its 'Sierra year' and the High Sierra upgrade may simply have restored the default hibernatemode 3. Considering the pros and cons of the different hibernatemodes 0, 3 and 25, I think I'll remain on hibernatemode 3.

In any way, the machine's sleep behaviour is now much more explainable to me and thanks to both of you, I can consider the issue as solved/explained on my personal, increasingly shorter list of High Sierra 'early-adopter hassles'.

If now only somebody would still manage to fix Cody Krieger's gfxCardStatus application for use under High Sierra, I'd already be as happy with this now eight year old piece of hardware as I was under Sierra (which is quite remarkable for an Apple "dot-zero" OS release ;)).
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.