At last bought the GTX 680, mac flashed. No success. Still no GPU acceleration.
It´s the 10.13.6 that ****s it all, don´t know why
Anyone can help me?
Got a tip for us?
Let us know
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
- Thread starter foxlet
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
At last bought the GTX 680, mac flashed. No success. Still no GPU acceleration.
It´s the 10.13.6 that ****s it all, don´t know why
Anyone can help me?
did you install the post install patches with dosdude1's MacOS High Sierra patcher
[doublepost=1532660193][/doublepost]
you might try and find a utiliy called SWUSwitcher that might help or enroll in the Apple beta software program
Thanks. Yes. Here is the thing: In a clean 10.13.6 instalation everything works like a charm. It´s the update of my 10.13.5 to 10.13.6 that makes the GPU acceleration not to work, repatch don´t work.
So I´m making a Migration Assistant, with my old system, and importing the accounts.
I will tell you when done
Thanks
So I´m making a Migration Assistant, with my old system, and importing the accounts.
I will tell you when done
Thanks
Last edited:
Ok. Finished Migration.
10.13.6 works like a charm now. With the GTX 680 working properly, no red windows in PDF, the welcome screen is now perfect, not a less resolution red one.
GPU acceleration is great.
Thank you sop much for your help.
10.13.6 works like a charm now. With the GTX 680 working properly, no red windows in PDF, the welcome screen is now perfect, not a less resolution red one.
GPU acceleration is great.
Thank you sop much for your help.
Are you using the Nvidia web driver or the built-in Mac OS driver?
FWIW 10.13.6 was a sketchy update for my 3,1 too. Had these same thing happen as you, same card the 680. 10.13.6 lost acceleration and wouldn't wake from sleep sometimes. Updated the Nvidia driver, did some PRAM zapping, reapplied the patches, seemed to fix the issues. However, wake on sleep takes a lot longer now, not sure sure why but at least it's not freezing on wake like the 5770.
Built-in
For your information, that slow wake up happens also in my other Mac Pro, High Sierra native, it seems to be in the update.
Strangely my Early 2009 iMac 9,1 seems to wake faster with 10.13.6. I only sleep the hard drives. But I no longer wait for them to spin up for a couple minutes.
Odd…. maybe only with Mac Pro´s? cause in my Macbook Pro 17" and Macbook Air 2015 nothing has changed about the wake/sleep...
Is the Night Shift patch working for anyone with a MacPro 3,1 on 10.13.6? The Patcher Updater applications shows v3 of the patch is installed but the Night Shift tab doesn't appear in the Monitors System Preferences panel. Note that this is from a full installation with the 10.13.6 installer patched by High Sierra Patcher 2.6.2.
Today my MacBook (13 Zoll, Aluminium, Late 2008) got upgraded automated to 13.10.6 (would have done via dosdudes installer this weekend), but okay - everything went well.
sometimes if you reinstall the backlight patch from the macOS High Sierra patcher and force rebuild caches then reboot then load the patch updater reapply the backlight and night shift only reboot then sometimes it works
Weird. That worked. Rebuilding the caches after reinstalling the patches from within the High Sierra patcher usb installer didn't solve the problem, but selecting the night shift patch in patch updater and reinstalling it under High Sierra did.
Hi All, I just wondered if anyone can help me. Please bear with me as this seems very freaky to me. i have a Mac Pro 3.1 and patched with Dosdudes High Sierra patcher that was running great, that is until I read that maybe I could install Mojave with his patcher as well, no joy and then I emailed him about it and he said my GTX 5780 wouldn't work properly unless flashed and pointed me to his video on YouTube, I watched it several times and eventually decided to have a go. I needed to install BootCamp and Windows so set about doing that on a spare SSD, all went well after a few hiccups and I was able to install Windows 10 Pro, however there was no icon to right click on, on the taskbar to go back to High Sierra, so I rebooted and pressed the alt key on the chime as you should. No boot up at all, in fact all it showed was a black screen, no apple logo, no nothing, I rebooted again with out pressing the alt key and it booted to Windows, I took out the Windows HD and tried again, all I got was a cursor on a black screen, I did a SMC reset and tried a PRAM one which didn't happen, I even went inside and pressed the little buttons, one by the Graphics card and one under the memory case.
I tried several times with these resets to no avail, it only boots in Windows 10, I put a fresh HD in and tried to re-install HS via the flash drive patcher I still had, it wouldn't load at all just hung, so all in all I have now got a very fast Mac Pro Windows 10 computer, has anyone any thoughts on how I can get my beloved Mac Pro back up and running the OS it is designed for ? I can live with it being Windows only,if I have screwed it completely as regards having a an Apple OS in it, at least it isn't fully broken and heading for the smelter.
Well thanks for hanging in.
Keith
I tried several times with these resets to no avail, it only boots in Windows 10, I put a fresh HD in and tried to re-install HS via the flash drive patcher I still had, it wouldn't load at all just hung, so all in all I have now got a very fast Mac Pro Windows 10 computer, has anyone any thoughts on how I can get my beloved Mac Pro back up and running the OS it is designed for ? I can live with it being Windows only,if I have screwed it completely as regards having a an Apple OS in it, at least it isn't fully broken and heading for the smelter.
Well thanks for hanging in.
Keith
That's a very curious case, I suppose you have personal datas on the old High Sierra partition you don't want lose. Most probably something has altered the EFI Apple Boot structure.
Probably you have a corrupted EFI partition, it is fixable in most cases.
TRY THESE STEPS ONLY if your HIGH SIERRA was installed in HFSplus, cause these steps won't work with an APFS file system.
I'd suggest you to create a MacOS USB Installer (minimum El Capitan), then booting from it holding the option key, and launch "First Aid" from Disk Utility, after check if from there you can see any HFS partition apart the NTFS Windows one.
You could create an HFS EFI bootable USB even from Windows with the proper tools!
One advise: don't user Clover on real Mac, never.
If you don't have another Mac, you will need to do from Windows using the diskpart (that is the equivalent of diskutil in unix) to convert your 16 GB USB empty drive in GPT partition scheme (the only one any Mac adopts).
Wait, you could use "Rufus" windows software to format your USB drive in GPT, much simpler.
You could use even an older MacOS Installer DVD to gain access to an unix Terminal or Disk Utility to check what's going on your main HDD, maybe a couple of "First Aid" could even fix.
------------------------------------------
Or since your Windows from Mac is working you could try:
a windows software "transmac", plug in an empty 16 GB USB drive, launch transmac, right click the USB Drive and select Format Disk for Mac, then right click the USB Drive and select Restore with Disk Image, select your (pre-downloaded) dmg (OSX El Capitan Installer) file and click Open. It will take some time to create the USB MacOS Installer, then holding option at boot you could be able to boot from it trying the DiskUtility's First Aid.
Last edited:
[doublepost=1533112814][/doublepost]Well I have tried the steps you said and still no joy, it only boots into windows despite holding the alt key down, I have tried with a mac wired keyboard and a windows wired keyboard and still nothing, its as if windows has configured everything for windows and kicked all the mac settings out, I am wondering whether to swap the memory, there is 26GB of in on two trays and the ATI Radeon GTX 5780 card for a 8800 I have, but basically I am at my wits end and may just use it as a windows computer, at least it's not scrapable.
Do you have a El Capitan installer pen drive? It's the last supported macOS on a 3,1 and it's the best for recovering. Try to boot from it and install on a empty drive. Then you can diagnose what Windows did with your other macOS install.[doublepost=1533112814][/doublepost]Well I have tried the steps you said and still no joy, it only boots into windows despite holding the alt key down, I have tried with a mac wired keyboard and a windows wired keyboard and still nothing, its as if windows has configured everything for windows and kicked all the mac settings out, I am wondering whether to swap the memory, there is 26GB of in on two trays and the ATI Radeon GTX 5780 card for a 8800 I have, but basically I am at my wits end and may just use it as a windows computer, at least it's not scrapable.
Maybe you have done a Windows installation in EFI mode, formatting the partition in GPT from the Windows Installer, and it has overwritten the Mac EFI partition with only the Windows BOOTloader files.
The only right way would be, doing a backup first of your disk, formatting it from a working MacOS system in GPT/GUID mode it will recreate the correct EFI Apple boot loader, and the "option" key should work again.
edit:
There could be other ways for example using Gparted CD, maybe "unflag" the "boot" parameter from the Windows Boot Partition while "flag" the others HFS+ partitions making them bootable.
Last edited:
I used my MacBook Pro to install El Capitan using DosDudes patcher an a SSD HD and patched it up as a Mac Pro 3.1 and installed that in my Mac Pro and tried to boot just from that, still no joy and get the black screen, I have a feeling its the graphics card that has just Windows drivers in it now as Windows updated all my drivers and that makes me not seeing Mac installers, does that make sense? I don't know.. I am desperate now
I used my MacBook Pro to install El Capitan using DosDudes patcher an a SSD HD and patched it up as a Mac Pro 3.1 and installed that in my Mac Pro and tried to boot just from that, still no joy and get the black screen, I have a feeling its the graphics card that has just Windows drivers in it now as Windows updated all my drivers and that makes me not seeing Mac installers, does that make sense? I don't know.. I am desperate now
Maybe connecting the two Macs through a Firewire 800 cable could even work for this scope and diagnose what's happened to your HDD.
In my opinion you need to fix your EFI Boot partition or Disk Utility your others HFS+ partitions, could you take out your internal MacPro HDD using a USB adapter connecting to your MBP and from its DiskUtility try to First Aid your HDD?
Or much more simpler/quicker connecting your MacPro HDD using an USB external adapter to your MBP, then from your MacBook Pro holding "option" key, if in your MBP Startup Manager you can see every Disk Partition of your MacPro HDD, then I am afraid it's your MacPro EFI CHIP EEPROM altered, in this case I cannot help you in any way.
Last edited:
I did as you said and took out the MacPro HDD and hooked into my MBP and it doesn't show up, just my MPB HDD, when booted up on the desktop it shows the MacPro HDD in two partitons, one the main boot (Windows) and a System Reserved partition with nothing showing in it. I don't have a Firewire cable anyway, but do have another Mac Pro which is a 2.1 running El Capitan Dosdudes Patcher one.
[doublepost=1533118240][/doublepost]Should have said when pressing the option key I only see my MBP HD
[doublepost=1533118240][/doublepost]Should have said when pressing the option key I only see my MBP HD
Ok, if you care you have to take backups first through a working Mac, then you need to format your MacPro HDD from another DiskUtility working Mac, then reinstall a MacOS on the MacPro3,1 External HDD directly from another Mac.
Okay here is what I am going to do, that is create a HD running El Capitan in my Mac Pro 2.1 and then put that drive in my Mac Pro 3.1 and try to boot, is that what you think I should do ?