macOS High Sierra (10.13) Unsupported Macs Thread

[macdos]

I would argue that the only people with the "will-not-wake-from-sleep" problem are the ones with 5770 GPUs like <this>.
There are other minor problems - such as loosing brightness setting after sleeping - that may be plaguing other ATI/AMD GPU MP3,1 (and other) systems.

I rather suspect that the 5770 "will-not-wake-from-sleep" problem is a graphic driver issue related to the 5770 only.

Here is a fellow with a 7950 and a wakeup problem: https://forums.macrumors.com/thread...ted-macs-thread.2048478/page-79#post-25195887

He is referring to an answer that I provided, but that now is no longer available. What's up with that? I guess it was rude of me to inform the Mac community that 7950 works just fine with HS.

 

[PitBullCH]

Hi Dosdude1,

Thanks for the response.

Maybe try using a different USB drive (or, better yet a second hard disk or partition) as the installer, and then see if you get any better results.

As I wrote earlier, 3 different USB sticks were tried - and actually I did also try using one of the internal SATA OCZ drives as the "USB Installer" and got the same results.

However - *some* progress has now been made

The latest attempt using a USB stick installer finished during the evening after around 12 hours - it was again at some sort of unrecoverable sleep/hibernation point, but when I power-cycled I was able to see a bootable 10.13.1 disk had been set up so I continued booting to the USB Installer, ran your patcher and that completed patching ok.

However, when I try to boot from this 10.13.1 disk it stops at "waiting for DSMOS" - I tried usual PRAM and SMC resets, SIP disable etc - no joy.

Interestingly, I also tried CCC cloning APFS and HFS+ 10.13.1 drives from my already upgraded MacPro 5.1 (Mid 2012) and tried to boot from these - these also both also stopped at "wait for DSMOS".

I understand DSMOS is "Don't Steal Mac OS" - some sort of authentication check introduced to prevent MacOS installation on non-Mac hardware. I know the Hackintosh community has a way around this using some sort of fake DSMOS responder but I don't understand how or why DSMOS would be an issue on a real Mac ?

I have since removed both the Sonnet Tempo USB3 card and the OWC Accellsior SSD PCI card - still no change. The GPU is a genuine Mac Edition from the Apple Store so this cannot be the issue (and in fact, I've used this on occasions to sort out upgrade boot loops on my MacPro 5.1 which normally has an nVidia Titan X so I know this is fine).

Not sure what else to try ? Quite perplexing given the success many others have had with their 3.1s...

 

[Machist]

Here is a fellow with a 7950 and a wakeup problem: https://forums.macrumors.com/thread...ted-macs-thread.2048478/page-79#post-25195887

He is referring to an answer that I provided, but that now is no longer available. What's up with that? I guess it was rude of me to inform the Mac community that 7950 works just fine with HS.

I think that post is removed? I don't know why?
If I remember correct you have update Sierra to High Sierra? And you do not have any issues?
I have these wake up/RED disorder problem all the time.

Look my latest status update:
#2070

 

[Skrzak]

Hi, any news on the trackpad in Macbook White 5.2 (mid 2009)? Maybe sth changed with the 2.5.0 High Sierra patcher from dosdude1? Would be nice if at least two finger tap was be available, for the function of right mouse button.

 

[pietrogregorini]

Hi there guys. I would like to know some quick info: I have a MacBook Pro 5,3 (Mid 2009) with Sierra and it works like a charm with @dosdude1 patch. I'd like to update to High Sierra but I've read about issues with NVIDIA GeForce 9400M: is the bug still present after 10.13.1? Does everybody have some issue with this graphic card?

Another question: did you notice any effective improvement using APFS instead of HFS+? Is the boot fast enough or slower than before?

One last question: @dosdude1 is there any possibility to do some aesthetic improvement to verbose mood boot? I mean, like hiding all the text with a black screen or something like that? I think it would be nicer to see to end users, but of course I don't know if it's something effectively possible to do.

 

[extrachrispy]

Awesome. Now if you can get Polaris support added back in, I'll give you a big kiss.

I don't know why you're not getting any traction on your repeated queries about this topic. I'll ask a stupid question: have you tried the GPU patch in @dosdude1 's tool? I'll shortly be in the same boat, as I have an RX580 on the way.

 

[Z1mDMan]

HI all have had a Hi sierra running on my mid 2009 macbook and actually had f keys sound and brightness working. have just got the first automated update from mac and the functions now don't work any ideas. have used dosdudes updater tool and no new updates available yet. Are you working on that yet mate?

Same here. I ended up wiping my HD and fresh installing 10.13 for now and everything is back working.

 

[slooksterPSV]

Same here. I ended up wiping my HD and fresh installing 10.13 for now and everything is back working.

Repatch the trackpad patch it has the keyboard functions in it. Just open patch updater click on view updates right click on the trackpad update and choose install. Mine says partial trackpad/keyboard

 

[MacPro3dot1]

So which was it 280°F or 140°F, it doesn't take much to confuse me since I gained octogenarian status. (fancy term for "really old")

Ohh... I meant 280°F / 140°C!
[doublepost=1510819627][/doublepost]

Here is a fellow with a 7950 and a wakeup problem: https://forums.macrumors.com/thread...ted-macs-thread.2048478/page-79#post-25195887

He is referring to an answer that I provided, but that now is no longer available. What's up with that? I guess it was rude of me to inform the Mac community that 7950 works just fine with HS.

I have the 5870 and had the same wake up problems. Switched to never sleep and that solved it obviously.
I'm also getting the red screen on PDF in preview....

 

[647156]

From Tiger to High Sierra, the 2008 eight-core Xserve does it all

 

[Essometer]

I tried the patch from dosdude1 on my Macbook Pro 2012 retina where the screens where changed so the brightness buttons didn't work anymore.
It couldn't replace the DisplayService.framework so I replaced it manually with pacifist and the 10.12.3 combo update, but with no luck. Brightness Keys are not working and I have the bug where the Macbook is not waking up after sleep.
I am at the brink of throwing this piece of **** out of the window, please tell me what I can do.

 

[Computers 4 U LLC]

I tried the patch from dosdude1 on my Macbook Pro 2012 retina where the screens where changed so the brightness buttons didn't work anymore.
It couldn't replace the DisplayService.framework so I replaced it manually with pacifist and the 10.12.3 combo update, but with no luck. Brightness Keys are not working and I have the bug where the Macbook is not waking up after sleep.
I am at the brink of throwing this piece of **** out of the window, please tell me what I can do.

The MacBook Pro 2012 is fully supported by High Sierra, no need to use the patch to install it, its a normal upgrade for this machine.

 

[Les Kern]

I saw this thread and tried to think back to when I patched my old Mac Pro to accept unsupported versions, and failed. It was a long time ago. Since then it upgrades normally and works better now than it did a few years ago, and everything I throw at it works perfectly.

 

[Essometer]

The MacBook Pro 2012 is fully supported by High Sierra, no need to use the patch to install it, its a normal upgrade for this machine.

Please read my post again. The display was replaced and is as of 10.12.3 no longer supported. I was able to get it working by running dosdude1s patch for 10.12.4 and up, but with 10.13.1 it would't work anymore. This problem was already discussed in this forum. Please don't piss me more off like I already am. Thanks.

 

[dosdude1]

Please read my post again. The display was replaced and is as of 10.12.3 no longer supported. I was able to get it working by running dosdude1s patch for 10.12.4 and up, but with 10.13.1 it would't work anymore. This problem was already discussed in this forum. Please don't piss me more off like I already am. Thanks.

In your case, I'd recommend you take the machine to Apple, and have them take a look at it. A supported machine like that should have no issues running an OS that was intended to be installed on it. There's a good chance they'll fix it for free. However, if you believe the backlight patch for unsupported machines will get it working on yours, you can apply the backlight control patch script.

 

[thicla01]

Maybe I'm mistaken and the problem occurs only in bootcamp in windows but it exists at least for some users.
P.S.: It works in macOS but not in windows, I think the problem is related to the drivers not detecting the switch in the jack. Sorry if I mislead anyone.

Look at this post: https://forums.macrumors.com/threads/1051665/

 

[olad]

Please read my post again... This problem was already discussed in this forum. Please don't piss me more off like I already am. Thanks.

Nothing @Computers 4 U LLC wrote merited your response. You wrote asking for 'help'. He/She made a polite suggestion. There was nothing in it that merited saying 'Don't piss me off'... If you don't want or like the suggestion, a 'thank you, it didn't help' would have sufficed. @dosdude1 hasn't been pissed off by questions repeated over and over again - and nobody has more right than he (I would have, God knows). Perhaps a little humility and being less prone to take umbrage?

 

[Essometer]

I apologize for my rudeness earlier. It's no excuse, but it was just late evening for me, had to work in the next morning and that was the last thing I wanted to deal with. To clearafy the situation: Yes, I know that the Macbook Pro 2012 should be supported without problems. But like I said, the screen has been replaced by a third party and the model number of the screen is just so slightly off the model number of the original screen. It's an OEM replacement because apple does't sell their original parts. Up untill 10.12.3 everything was fine, but after that the brightness broke and I wasn't able to control it anymore. The same thing happend to many hackintosh systems at the time.

Here is the thread with people who share the same fate: https://forums.macrumors.com/threads/screen-brightness-broken-sierra-10-12-4-beta-3.2033660/

If I were going to Apple, I'm pretty sure you can guess what they will tell me: Not an original part, replace the screen for $600+.

 

[olad]

and nothing says it better than you have done - the bigness to make an apology... you are doing okay. have a great day.

 

[IusAP]

Hi, I am new here. I have an MBP5,5 (mid 2009) and I want to install High Sierra on an SSD in this Computer. I successfully installed an external USB-Drive with the High sierra patcher on it. However after starting the installation on the MBP the process stopped after 1 minute because it said no known packages found and it cant be installed on this computer. Has anyone an ideaß Thanks

 

[dosdude1]

Hi, I am new here. I have an MBP5,5 (mid 2009) and I want to install High Sierra on an SSD in this Computer. I successfully installed an external USB-Drive with the High sierra patcher on it. However after starting the installation on the MBP the process stopped after 1 minute because it said no known packages found and it cant be installed on this computer. Has anyone an ideaß Thanks

Check your system's date and time, ensure it's set to the current date.

 

[pjschwartz]

Successfully updated my Mac Pro 3,1 from Sierra to High Sierra. First removed HD5770 graphics card and replaced it with the original HD2600. OS and Apps are on a SDD Drive, but have have not yet converted it to the APFS format.

Smooth upgrade and no issues to report . . .

 

[extrachrispy]

But like I said, the screen has been replaced by a third party and the model number of the screen is just so slightly off the model number of the original screen. It's an OEM replacement because apple does't sell their original parts. Up untill 10.12.3 everything was fine, but after that the brightness broke and I wasn't able to control it anymore. The same thing happend to many hackintosh systems at the time.

Here is the thread with people who share the same fate: https://forums.macrumors.com/threads/screen-brightness-broken-sierra-10-12-4-beta-3.2033660/

If I were going to Apple, I'm pretty sure you can guess what they will tell me: Not an original part, replace the screen for $600+.

Or you could pay the flat-rate repair fee, which is significantly less (it was $300 until recently). It surprises me that it works this way, but it does. I've always gotten MUCH more than $300 worth of repairs done on out-of-warranty machines that way.

 

[Computers 4 U LLC]

Please read my post again. The display was replaced and is as of 10.12.3 no longer supported. I was able to get it working by running dosdude1s patch for 10.12.4 and up, but with 10.13.1 it would't work anymore. This problem was already discussed in this forum. Please don't piss me more off like I already am. Thanks.

What display was it replaced with? I'm assuming it was not replaced with another retina display. I have an early 2012 MacBook Pro and does not have the retina display and it is completely supported by High Sierra, so I guess I still don't understand why you have to patch yours...?

 

[Essometer]

Did you have a look into the link to the other forum thread? Basically, the replacement screens are completely identical. The only difference is the screen controller chip that is responsible for the backlight. Maybe the chip uses a slightly altered protocol so that the newer backlight driver are not compatible.

@extrachrispy, thanks for the suggestion. The price was an estimate by me. But I already replaced the screen because of ghosting and had the battery replaced. That was the last money I am willing to invest into it, I mean if it were any other brand of laptop it would have hit the trash a long time ago.

By the way I solved the problem by installing the 10.13.1 combo update and apply dosdude1 patch again. But i guess it's just a matter of time until my backlight bites the dust for good in future updates.