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.
Yes, any card that works in OS X, but is not the stock Radeon HD 2600 or GeForce 8800GT.

I'll do this tomorrow for a Radeon HD6870 that works perfectly in Sierra with efi boot screens and for an RX460 that also works perfectly in Sierra but without boot screens. In both cases when I have looked at the logs in Sierra, it has been caused (I think) by a WindowServer crash due to a GL driver bundle. And in the case of the RX460, if I Safe boot, it can get to a desktop that has no acceleration.

I'll also try to that tonight, with either GTX 670 or GTX 970, or maybe both.
 
So are you saying that this currently resolved or that it will be in a future release of Dosdude's patch?

No it isn't resolved you cannot install system updates at all right now the latest system update developer version included as well as public beta version 9 verify's the firmware if the firmware version doesn't match the o.s will not boot it says invalid firmware.

Both dosdudes and Aus enabler do not function for system updates
 
No it isn't resolved you cannot install system updates at all right now the latest system update developer version included as well as public beta version 9 verify's the firmware if the firmware version doesn't match the o.s will not boot it says invalid firmware.

Both dosdudes and Aus enabler do not function for system updates
So, if I understand you correctly, then that's what I was afraid of earlier. I guess we'd have to a full manual install at every point update. However, wouldn't we need a completely new local version of the installer each update? Or a patched combo updater?

Any hope of getting the trackpad to be fully functional on the mid-2009 MBP? Touch to tap?
IIRC it worked fine on my MBP5,5, but I don't use it and I turned it off so I don't know if it works consistently.
 
So, if I understand you correctly, then that's what I was afraid of earlier. I guess we'd have to a full manual install at every point update. However, wouldn't we need a completely new local version of the installer each update? Or a patched combo updater?


IIRC it worked fine on my MBP5,5, but I don't use it and I turned it off so I don't know if it works consistently.


What it means is every time you want to update the machine you have to redownload the high sierra installer every time they release a update but even that isn't going to work if the firmware validation tool is a part of the final release the o.s won't boot at all it says invalid firmware then refuses to boot.

I'm looking into this myself and will post updates if there is a way to bypass it.
 
So, if I understand you correctly, then that's what I was afraid of earlier. I guess we'd have to a full manual install at every point update. However, wouldn't we need a completely new local version of the installer each update? Or a patched combo updater?


IIRC it worked fine on my MBP5,5, but I don't use it and I turned it off so I don't know if it works consistently.

Are you sure about this? Last week when Beta 9 was released, initially the Beta 8 full installer was still downloading inside of the High Sierra Patch application. So when I recreated the USB installer, it used Beta 8 which then had no problem in downloading and installing the Beta 9 software update.
 
What it means is every time you want to update the machine you have to redownload the high sierra installer every time they release a update but even that isn't going to work if the firmware validation tool is a part of the final release the o.s won't boot at all it says invalid firmware then refuses to boot.

I'm looking into this myself and will post updates if there is a way to bypass it.
But the latest beta 9 installs fine with the installer patch.


Are you sure about this? Last week when Beta 9 was released, initially the Beta 8 full installer was still downloading inside of the High Sierra Patch application. So when I recreated the USB installer, it used Beta 8 which then had no problem in downloading and installing the Beta 9 software update.
Good to know.
 
tried both patches it would appear that if you have installed the patch before september 5th the o.s will accept patches however after september 5th the o.s will refuse updates.

this seems to be a new bug. figured it out just now.

same is being reported for sierra with the sierra patcher several testers on youtube are reporting the same issue with sierra being blocked as well.

so it would seem a issue with the app store on the high sierra side or they are updating the app store for new security.

So if your updates stop working. here is how you fix it

set your clock to september 5th reenabled the catalog patch run the update and then reset your clock to the correct time

simple fix
 
I too - and many others - have successfully updated to Developer Beta 9 through the Mac App Store.
 
Hopefully the GM lands tomorrow. I'll test the update out then.

Hopefully they won't try to forcibly convert these machines to APFS.
 
Yep, just updated an APFS install to Developer Beta 9 with no issues whatsoever.
Dosdude as promised here are the Diagnostic Reports for a MacPro3,1 running beta 9.
The earlier WindowServer crash (08:47) is for an HD6870 with full boot screens (shows as RadeonAMDX3000 crash). I enclose a screenshot as well where the boot fails to complete with a spinner. It runs fine in Sierra.
The later WindowServer crashes (about 09:05) are for a Sapphire RX460 4 GB that works fine in Sierra. In this case, the crashes are the RadeonAMDX4000GL drivers.
IMG_0076.JPG

[doublepost=1505263071][/doublepost]Dream on. No GM until 25 September. There will be at least 2 more and perhaps 3 beta seeds and they are sorely needed because beta 9 has plenty of things that need fixing.

Hopefully the GM lands tomorrow. I'll test the update out then.

Hopefully they won't try to forcibly convert these machines to APFS.
 

Attachments

  • DiagnosticReports.zip
    340.3 KB · Views: 138
Dream on. No GM until 25 September. There will be at least 2 more and perhaps 3 beta seeds and they are sorely needed because beta 9 has plenty of things that need fixing.
? iOS 11 GM is already out, and the release isn't until Sept. 19.

So it makes perfect sense for the HS GM to come out this week, for release Sept. 25.
 
I am hoping for the gm soon because the update on dev 9 is nasty on MacBook air's without the patch I had to redownload the updater 5 times every time it came with dev 9 could not be installed on this machine and this machine is a supported machine not a unsupported machine so hopefully the crashes and bugs will get fixed there getting weird
 
I am hoping for the gm soon because the update on dev 9 is nasty on MacBook air's without the patch I had to redownload the updater 5 times every time it came with dev 9 could not be installed on this machine and this machine is a supported machine not a unsupported machine so hopefully the crashes and bugs will get fixed there getting weird
I'm starting to think it's your setup. Most of us didn't have this problem. Furthermore, it's quite possible the GM will be beta 9. In fact, that was what I was predicting, just like my prediction that the iOS 11 GM would be beta 10, which turned out to be correct.
 
I'm starting to think it's your setup. Most of us didn't have this problem. Furthermore, it's quite possible the GM will be beta 9. In fact, that was what I was predicting, just like my prediction that the iOS 11 GM would be beta 10, which turned out to be correct.

my setup is fine I have 2 machines one unsupported and one supported the unsupported is running better then the supported machine.

thank you very much.

whats happening is a bug on the supported machine where it trys to install and restart the computer without the update being done downloading which causes a headache.
[doublepost=1505265952][/doublepost]https://forums.developer.apple.com/thread/78847

This is what is happening across multiple machines using the legit update or trying to legit update there MacBook pro's airs and other machines
 
Dosdude as promised here are the Diagnostic Reports for a MacPro3,1 running beta 9.
The earlier WindowServer crash (08:47) is for an HD6870 with full boot screens (shows as RadeonAMDX3000 crash). I enclose a screenshot as well where the boot fails to complete with a spinner. It runs fine in Sierra.
The later WindowServer crashes (about 09:05) are for a Sapphire RX460 4 GB that works fine in Sierra. In this case, the crashes are the RadeonAMDX4000GL drivers.View attachment 717184
[doublepost=1505263071][/doublepost]Dream on. No GM until 25 September. There will be at least 2 more and perhaps 3 beta seeds and they are sorely needed because beta 9 has plenty of things that need fixing.
Great, thank you! Try installing this file: SkyLight.framework.zip. To install it, open Terminal, cd into the directory containing the file, and run these commands:

Code:
cp -R /System/Library/PrivateFrameworks/SkyLight.framework ~/SkyLight-backup.framework
sudo cp -R SkyLight.framework /System/Library/PrivateFrameworks
sudo chmod -R 755 /System/Library/PrivateFrameworks/SkyLight.framework
sudo chown -R 0:0 /System/Library/PrivateFrameworks/SkyLight.framework

Then, reboot your machine and see if it successfully boots with the other video card. This may cause the system to stop booting entirely, in which case just copy the backup back into the original "/System/Library/PrivateFrameworks/" directory.

EDIT:

Do not try this, it doesn't work.
 
Last edited:
here is a crash report with the latest installer dev 9 from App Store using the patch on MacBook Pro 5,5

hope it helps.
[doublepost=1505267485][/doublepost]this is the only machine I couldn't get to boot high Sierra it crashes no matter what but Sierra patched works fine
 

Attachments

  • Installer Log 12-Sep-2017 crash dev 9.txt
    124 KB · Views: 604
Great, thank you! Try installing this file: SkyLight.framework.zip. To install it, open Terminal, cd into the directory containing the file, and run these commands:

Code:
cp -R /System/Library/PrivateFrameworks/SkyLight.framework ~/SkyLight-backup.framework
sudo cp -R SkyLight.framework /System/Library/PrivateFrameworks
sudo chmod -R 755 /System/Library/PrivateFrameworks/SkyLight.framework
sudo chown -R 0:0 /System/Library/PrivateFrameworks/SkyLight.framework

Then, reboot your machine and see if it successfully boots with the other video card. This may cause the system to stop booting entirely, in which case just copy the backup back into the original "/System/Library/PrivateFrameworks/" directory.

EDIT:

Do not try this, it doesn't work.

OK, I won't try it.
 
Update: It appears the GPU issue is the result of SSE4.2 requirements in some of the High Sierra GPU kexts, which the CPUs in the Mac Pro 3,1 do not support. As such, it may not be possible to get these cards working in the Mac Pro 3,1 running High Sierra.

Also, has anybody tried an aftermarket nVidia card? It appears these changes may have only been made to the drivers for AMD cards.
 
So why does an HD2600XT, which is a much earlier card than either the HD6870 or RX460, work? Also I have read reports that the RX460 2 GB version and the RX580 both work. It seems that it is "just" a matter or Apple modifying the relevant kexts to support the older cards, which they won't do of course.
 
So why does an HD2600XT, which is a much earlier card than either the HD6870 or RX460, work? Also I have read reports that the RX460 2 GB version and the RX580 both work. It seems that it is "just" a matter or Apple modifying the relevant kexts to support the older cards, which they won't do of course.
Apple modified the drivers for all the AMD cards newer than the 2600 Pro. That's why it works just fine with the stock cards.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.