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.
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 ?
I'd try with a clean install, not one needing patches to run - if you create one on your 2,1 you will need to emulate EFI64 at least, no?

The last time I had trouble like this with my Mac Pro 2008 (when I was trying to learn how to clean install 10.13 and did more mess than I could clean) I had to clear NVRAM, boot with a standard El Capitan downloaded/created on a supported Mac and fully erase the disk with diskutil zerodisk diskXX. Only then, I could start again.

Sometimes we need to take two or three steps back to move forward.
 
Okay guys, its all done and I got it fixed at last, I took out all the drives and reformatted the main SSD and the Windows SSD, in my MacPro 2.1, I did a SMC and a NVRAM reset I took out the graphis card and replaced it with a 8800 and reinstalled the main SSD and plugged in a El Capitan install flash drive and booted up and crossed my fingers, at first nothing happened, then the screen went white and then the apple logo came up and the progress bar, I clicked on install and it installed okay and rebooted and all was well if a little slow, I shut down and took out the 8800 card and replaced it with the 5870, and rebooted, and I sat and sat listening to the fans whirring and was about to give up when the screen went white and then black and a boot up began and all went well. Eventually I was brave enough to run DosDudes High Sierra installer and that went okay and now I am back to how it was 2 days ago.

What I did find out when I reformatted my Apple SSD was that on the install of boot Camp originally it had formatted my Apple SSD into NTFS! that's why I couldn't get bck to High Sierra from Windows, but all is okay now and bootcamp will never be installed again, so Mojave is off the menu.

My thanks to one and all who tried to help, I really do appreciate the help.

Keith
 
Okay guys, its all done and I got it fixed at last, I took out all the drives and reformatted the main SSD and the Windows SSD, in my MacPro 2.1, I did a SMC and a NVRAM reset I took out the graphis card and replaced it with a 8800 and reinstalled the main SSD and plugged in a El Capitan install flash drive and booted up and crossed my fingers, at first nothing happened, then the screen went white and then the apple logo came up and the progress bar, I clicked on install and it installed okay and rebooted and all was well if a little slow, I shut down and took out the 8800 card and replaced it with the 5870, and rebooted, and I sat and sat listening to the fans whirring and was about to give up when the screen went white and then black and a boot up began and all went well. Eventually I was brave enough to run DosDudes High Sierra installer and that went okay and now I am back to how it was 2 days ago.

What I did find out when I reformatted my Apple SSD was that on the install of boot Camp originally it had formatted my Apple SSD into NTFS! that's why I couldn't get bck to High Sierra from Windows, but all is okay now and bootcamp will never be installed again, so Mojave is off the menu.

My thanks to one and all who tried to help, I really do appreciate the help.

Keith

Don't worry a Windows installation could cause this issue but cannot destroy any Mac, ONLY Clover bootloader and some Linux distros can really destroy a Mac EFI EEPROM CHIP.

So doing correctly from the MacOS Utilities "Bootcamp Assistant" you can safely re-install Windows in Bootcamp mode.
 
  • Like
Reactions: TimothyR734
Well thats what I originally did was install from MacOS utilities, I am very loathe to try again as I really am now not bothered about having Mojave on the 3.1, I have my MacBook Pro that is 2015 and that is running it okay, I will still run my 2.1 and 3.1 Mac Pro's until end of life with the OS that is in them now, unless of course I can source a graphics card that will work and not require flashing, to enable me to use DosDudes Mojave patcher .
 
  • Like
Reactions: TimothyR734
Well thats what I originally did was install from MacOS utilities, I am very loathe to try again as I really am now not bothered about having Mojave on the 3.1, I have my MacBook Pro that is 2015 and that is running it okay, I will still run my 2.1 and 3.1 Mac Pro's until end of life with the OS that is in them now, unless of course I can source a graphics card that will work and not require flashing, to enable me to use DosDudes Mojave patcher .

Unless you are using MacOS in APFS (cause using APFS is not simple installing Windows in Bootcamp mode), using HFS+ there should be no issues installing Windows 10 in Bootcamp Mode, I did installed a Windows 64 bit in EFI mode from a Mac EFI 32 bit patched.

Anyway, give a try re-installing Windows in Bootcamp mode, since now you know how to fix it again in case something went wrong. Might try installing through Bootcamp Assistant using a Windows 7 64 bit DVD, and after you can SAFELY upgrade directly from windows 7 to windows 10 even from a Mac.

But if you don't need Windows, agree don't install it.

edit:
If during your previous issue you had a "Windows Reserved partition" that was been your issue that partition should not be created on a Mac.

Even if it's doable manually booting directly from a Windows DVD, it's not advisable, so split the partition for Windows Installing ONLY from Bootcamp Assistant in your case.

You must allow Bootcamp Assistant to create a FAT partition for you, after it will boot from Windows disk and you need to format the "BOOTCAMP" partition in NTFS, then installing, after done from Windows's Bootcamp Panel you can switch back to your MacOS partition.
 
Last edited:
  • Like
Reactions: TimothyR734
I am having a issue with airpods on macpro 3.1 my airpods have no sound until a reboot. Kind of hit and miss when they work.
 
  • Like
Reactions: TimothyR734
Hi Again, An update on the Bootcamp situation on my 3.1. I did try again and actually got it to work okay with a windows 7 disc I had, I decided I wouldn't really need it and wiped it off.

I have found a MSI GT 710 card in my box of computer stuff I have and installed that, it works okay with the default Nvidia Mac driver and the Web Driver, however I get jittery video playback in iTunes and my tv card. Do I need to flash this card for High Sierra?, I read on another forum it works okay in El Capitan/Sierra with the standard drivers, not a big deal if it doesn't work with my setup as I can still use the 5870 1GB card, but would be nice to have the 710 up and running okay as its a 2GB one.

Any help out there at all ?

Thanks
 
  • Like
Reactions: TimothyR734
Running 10.13.6 , 3,1 MacPro, all appears ok, but in MacMail the fist character is not capitalized. I do have the settings enabled in System Pref /keyboard/text. Anyone else with this issue? Any suggestions ? This does work normally on my MacBook running 10.13.6
 
  • Like
Reactions: TimothyR734
@dosdude1 i flashed this card successfully
EVGA GeForce GTX 680 Classified

https://www.evga.com/products/specs/gpu.aspx?pn=5e58e11b-7c49-44c0-9348-bd7be168bd1b

but trying to boot up it goes in a boot loop and there are green lines everywhere it gets as far as when the screen usually turns to black with a white apple logo so i never see that part ..... are you sure this version of the card is compatible ? i have 2 power cables running to it 6pin to 8 pin

@dosdude1 excited that i received the video card ....do you know any instructions / link on how to flash this thing so it will work in my mac ?

i'm looking at this video here but wanted to make sure its the right deal with you first ...its the not the same video card but does that matter ?
 
  • Like
Reactions: TimothyR734
@dosdude1 i flashed this card successfully
EVGA GeForce GTX 680 Classified

https://www.evga.com/products/specs/gpu.aspx?pn=5e58e11b-7c49-44c0-9348-bd7be168bd1b

but trying to boot up it goes in a boot loop and there are green lines everywhere it gets as far as when the screen usually turns to black with a white apple logo so i never see that part ..... are you sure this version of the card is compatible ? i have 2 power cables running to it 6pin to 8 pin

You linked the specs for the 4GB RAM version. Did you used the 4GB ROM for flashing?
 
  • Like
Reactions: TimothyR734
@dosdude1 i flashed this card successfully
EVGA GeForce GTX 680 Classified

https://www.evga.com/products/specs/gpu.aspx?pn=5e58e11b-7c49-44c0-9348-bd7be168bd1b

but trying to boot up it goes in a boot loop and there are green lines everywhere it gets as far as when the screen usually turns to black with a white apple logo so i never see that part ..... are you sure this version of the card is compatible ? i have 2 power cables running to it 6pin to 8 pin
Make sure you remove the AMD video card patch. You can do so using this script.
 
  • Like
Reactions: TimothyR734
  • Like
Reactions: TimothyR734
thank you so much @tsialex for pointing out the 4gb issue and @dosdude1 for the tip on the AMD uninstall .....great news figured out why the boot got stuck ! if i load the nvidia web drivers instead of mac os which they give you an option to when your machine is running (i had my old card to see by) i selected load those not the mac os ones and voila i'm writing to you from a mac with the new card powering video

Yes, that thread has the correct ROM for the 4GB RAM model. Flash the correct ROM and remove the AMD patch like dosdude1 posted above.
 
Last edited:
@dosdude1

I have the following problem:

I can not use the "keyboard" + "mouse" + "trackpad" menu in the settings.
What I have found out is that it works fine after reinstall but it stops working after i update 2 patches with the patch updater. the patches which got updated are "night shift" + "backlight"

I reinstalled to confirm and it happend again. I do not want to reinstall. Please help me find out whats going on.

Night Shift works fine but backlight is buggy, it gets reseted after I switch tabs in the monitor menu.

iMac 7.1
High Sierra

the error is in german, in englisch it means "error in the system settings - you can not open the keyboard settings because it is not possible on a intel based mac"
 

Attachments

  • Ohne Titel.png
    Ohne Titel.png
    147 KB · Views: 199
  • Like
Reactions: TimothyR734
Okay, I was trying to upgrade from a working Sierra install to Mojave since I've never been able to get High Sierra working on my late 2009 macPro (4.1 flashed to 5.1 a few years back) - That didn't work, so after a a lot of tips in the Mojave thread, I figured maybe I'd try to do the upgrade to High Sierra again, first. Since it seems there is an issue with the OtherWorld Computers SSD, I figured I'd go back to a conventional drive, just to be sure.

Since it takes a few hours to work through this so I decided to try again today. And I was asked to include details, so here is the best I can offer.

- Last night I pulled the SoldState Drives and time-machine restored Sierra 10.12.6 to a seagate Barracuda 1.5TB 7200rpm (conventional) drive. This morning I planned to update to High Sierra, and THEN if that works, I could do the Mojave upgrade later.

I did the Firmware Update and the reboot. Then into Terminal and typed csrutil disable- and then reboot into Sierra.

Downloaded a fresh copy of HS Installer util from Dosdude site.
Downloaded a fresh copy of HS Install from Apple. (Yep, my machine looks compatible to them)

Created a HS Install Thumbdrive (Kingston 8GB drive) and rebooted, then into installer
"A Firmware Update is required" - clicked restart, did the restart as suggested,
reboot- option and selected Installer Thumb, and into installer.
"A Firmware Update is required" - got this screen AGAIN. (??)
Again, clicked "restart" on the screen itself. Nothing happened - so I waited -
15 mins later and still, no visible change, so I clicked the Restart option from the drop down menu,
and did the technique again (hold power until tone, let it reset and
THIS TIME was different - CD tray opened, and a kind of a lower resolution screen came up
with the fatter progress bar. I let it run and it restarted on its own.

It restarted with the current system start screen (Sierra), so I rebooted, did the option-restart,
and selected the Install HS thumb drive again.

Got a progress bar, ran for 6 mins, restarted at around 2 minutes,
it went back to the install process on its own, with a 49 minute progress bar.
That ran uninterrupted - I came back after it completed and saw a grey circle with slash in it - Bad disc!
Tried to restart it a couple times, same result.
So I powered down, pulled the new HDD, put last night's working Sierra OWC SSD drive back in, just to get it going again, and restarted successfully in Sierra again. And here I am.

Been working with it all day now and I am no further along.

There is one thing -
Before I did this install, when I ran "About this mac" this morning, I got

Boot ROM Version: MP51.0087.B00

After all the work, when I run About this Mac now, I get this:

Hardware Overview:

Model Name: Mac Pro
Model Identifier: MacPro5,1
Processor Name: 6-Core Intel Xeon
Processor Speed: 3.33 GHz
Number of Processors: 1
Total Number of Cores: 6
L2 Cache (per Core): 256 KB
L3 Cache: 12 MB
Memory: 24 GB
Processor Interconnect Speed: 6.4 GT/s
Boot ROM Version: MP51.0089.B00
SMC Version (system): 1.39f5
SMC Version (processor tray): 1.39f5

(Everything else is the same, only the Boot Rom number changed)

So, the Firmware Update part of the install DID work this time, at least ...

But I'm at a complete loss as to why a theoretically supported machine cannot be updated to High Sierra,
I do want to upgrade to Mojave real soon now!

(as I said, its a late 2009 MacPro 4.1 that was updated to 5.1 a few years back, and has been running Sierra no problem for a few years)
The leap to High Sierra should have been equally painless on a supported machine - unless somehow something got cobbled up on one of the early Sierra betas that is still causing problems at upgrade time ??

I am open to suggestions!
 
  • Like
Reactions: TimothyR734
my suggestion astray making a new HS bootable usb and do a clean install maybe something with your time machine back up of Sierra is not jiving with the installation of HS if you do get HS up you could always use the migration utility
 
Okay, I was trying to upgrade from a working Sierra install to Mojave since I've never been able to get High Sierra working on my late 2009 macPro (4.1 flashed to 5.1 a few years back) - That didn't work, so after a a lot of tips in the Mojave thread, I figured maybe I'd try to do the upgrade to High Sierra again, first. Since it seems there is an issue with the OtherWorld Computers SSD, I figured I'd go back to a conventional drive, just to be sure.

Since it takes a few hours to work through this so I decided to try again today. And I was asked to include details, so here is the best I can offer.

- Last night I pulled the SoldState Drives and time-machine restored Sierra 10.12.6 to a seagate Barracuda 1.5TB 7200rpm (conventional) drive. This morning I planned to update to High Sierra, and THEN if that works, I could do the Mojave upgrade later.

I did the Firmware Update and the reboot. Then into Terminal and typed csrutil disable- and then reboot into Sierra.

Downloaded a fresh copy of HS Installer util from Dosdude site.
Downloaded a fresh copy of HS Install from Apple. (Yep, my machine looks compatible to them)

Created a HS Install Thumbdrive (Kingston 8GB drive) and rebooted, then into installer
"A Firmware Update is required" - clicked restart, did the restart as suggested,
reboot- option and selected Installer Thumb, and into installer.
"A Firmware Update is required" - got this screen AGAIN. (??)
Again, clicked "restart" on the screen itself. Nothing happened - so I waited -
15 mins later and still, no visible change, so I clicked the Restart option from the drop down menu,
and did the technique again (hold power until tone, let it reset and
THIS TIME was different - CD tray opened, and a kind of a lower resolution screen came up
with the fatter progress bar. I let it run and it restarted on its own.

It restarted with the current system start screen (Sierra), so I rebooted, did the option-restart,
and selected the Install HS thumb drive again.

Got a progress bar, ran for 6 mins, restarted at around 2 minutes,
it went back to the install process on its own, with a 49 minute progress bar.
That ran uninterrupted - I came back after it completed and saw a grey circle with slash in it - Bad disc!
Tried to restart it a couple times, same result.
So I powered down, pulled the new HDD, put last night's working Sierra OWC SSD drive back in, just to get it going again, and restarted successfully in Sierra again. And here I am.

Been working with it all day now and I am no further along.

There is one thing -
Before I did this install, when I ran "About this mac" this morning, I got

Boot ROM Version: MP51.0087.B00

After all the work, when I run About this Mac now, I get this:

Hardware Overview:

Model Name: Mac Pro
Model Identifier: MacPro5,1
Processor Name: 6-Core Intel Xeon
Processor Speed: 3.33 GHz
Number of Processors: 1
Total Number of Cores: 6
L2 Cache (per Core): 256 KB
L3 Cache: 12 MB
Memory: 24 GB
Processor Interconnect Speed: 6.4 GT/s
Boot ROM Version: MP51.0089.B00
SMC Version (system): 1.39f5
SMC Version (processor tray): 1.39f5

(Everything else is the same, only the Boot Rom number changed)

So, the Firmware Update part of the install DID work this time, at least ...

But I'm at a complete loss as to why a theoretically supported machine cannot be updated to High Sierra,
I do want to upgrade to Mojave real soon now!

(as I said, its a late 2009 MacPro 4.1 that was updated to 5.1 a few years back, and has been running Sierra no problem for a few years)
The leap to High Sierra should have been equally painless on a supported machine - unless somehow something got cobbled up on one of the early Sierra betas that is still causing problems at upgrade time ??

I am open to suggestions!

Let's test something different this time. Could you please fully erase your HDD like this?

1) First list your disks with:
Code:
diskutil list

2) Find what's the disk number of the HDD that you're gonna erase/install High Sierra, like on my screenshot:
Screen Shot 2018-08-11 at 23.10.31.png


Replace diskXX on the command below to zero disk your HDD:
Code:
diskutil zerodisk diskXX
You don't need to wait until the end of zero disk, 5% and you can terminate it, unless you suspect that your disk have some bad sector or another defect.

3) Now shutdown your Mac Pro and remove your OWC SSD, put your createinstallmedia created 10.13.6 pendrive, don't use dosdude1 one since your Mac Pro is a supported one.

4) Boot from your createinstallmedia pendrive and install 10.13.6 on your HDD without restoring your TimeMachine.
[doublepost=1534040219][/doublepost]P.S: When upgrading Mac Pro 5,1 firmware, you need to do it from your macOS installation. You can't do it from a createinstallmedia pendrive, like on every other Mac. Now you're on the current BootROM, 0089, the same needed for Mojave betas.
 
Last edited:
Hello, dosdude1. I'm trying to do this on my mid-2009 Macbook 5,2. I've made the installer but I cannot boot from it. It always takes me back to my original 10.7.5. I am using a external HDD with USB 3.0. Does this affect the booting? Should I use USB 2.0 instead? Thank you.
 
  • Like
Reactions: TimothyR734
Hello everyone. Many thanks to @dosdude1 for his work on the patch. I finally made the jump to High Sierra 10.13.6 from El Capitan yesterday on my Mac Pro 3,1. All seems to be working well except for wake from sleep. I understand from searching this thread that this may still be an ongoing issue unless I missed the fix somewhere?

My system specs are as follows:
1. Mac Pro 3,1 with 8GB RAM
2. AMD Radeon HD 7950
3. Boot disk is a WD Blue 1TB SSD
4. Using HFS+ until @dosdude1 releases patch to add native APFS support to BootROM.

I left my machine last night with the standard 10 minute CPU and monitor sleep settings just to test before going to bed. Woke up this morning to find the machine will not wake from sleep; or rather I feel it did but the monitor did not power back on.

Reset SMC and NVRAM and will try again. I've verified that the AMD patch was installed post-installation.

Any suggestions or should I just leave sleep off for the time being? The latter won't be much of an issue since sleep was pretty much broken for me since 10.9 and I've had to resort to using in the past 3rd party apps such as 'Please Sleep'.

TIA for any suggestions.
 
Ok, nvram and SMC reset did not work. Mac went to sleep after an hour and when I came back, I could see that the unit was in sleep mode due to the front panel light oscillating in brightness. Tapping the keyboard, the computer awoke but the graphics card did not. No signal was sent to the monitor.

Any suggestions? Unfortunately remote access is turned off so I can't SSH and reboot. I always hate doing a hard reset if I can avoid it.
 
  • Like
Reactions: TimothyR734
Ok, nvram and SMC reset did not work. Mac went to sleep after an hour and when I came back, I could see that the unit was in sleep mode due to the front panel light oscillating in brightness. Tapping the keyboard, the computer awoke but the graphics card did not. No signal was sent to the monitor.

Any suggestions? Unfortunately remote access is turned off so I can't SSH and reboot. I always hate doing a hard reset if I can avoid it.
That's a side-effect of the modern AMD card on the Mac Pro 3,1. The only solution is to replace the card with an nVidia one.
 
  • Like
Reactions: TimothyR734
That's a side-effect of the modern AMD card on the Mac Pro 3,1. The only solution is to replace the card with an nVidia one.

Unfortunately I suffer the same issue with my 3,1 (Mac does not wake up 8 time on 10) even If I use a NVIDIA GeForce GTX480 MP (1526Mb) (it's a patched video card from MacVidCards). I decided not to use sleep anymore and power off when I do not use it (not very user-frindely but acceptable for a 2008 Mac).

I'm still running 10.13.5 (Recovery + HFS) and I'm not sure I can upgrade to 10.13.6 directly from Apple Software Update Panel... Is it supposed to upgrade well this way ?
 
  • Like
Reactions: TimothyR734
(from the other thread of possibilities)

Having got the firmware updated, now:
1. Boot from USB installer you have and set SIP back to on from terminal with csrutil enable
2. Check SIP is on with csrutil status
2a. Boot back into Sierra
3. Build a new clean HighSierra installer from terminal using the APPLE guidelines—you DO NOT need a dosdude installer

4. Put an SSD into the Mac, partition/erase it as APFS.
5. Boot from the Apple USB installer and see how the install proceeds


So, I have already done steps 1-3 listed above ... and am still on the 1.5TB Seagate HDD on Sierra 10.12.6 -

So, you say now to zerodisk to wipe my 1.5TB Seagate HDD, and do NOT format the SDD in APFS to do the install?


Let's test something different this time. Could you please fully erase your HDD like this?


Replace diskXX on the command below to zero disk your HDD:
Code:
diskutil zerodisk diskXX
You don't need to wait until the end of zero disk, 5% and you can terminate it, unless you suspect that your disk have some bad sector or another defect.

3) Now shutdown your Mac Pro and remove your OWC SSD, put your createinstallmedia created 10.13.6 pendrive, don't use dosdude1 one since your Mac Pro is a supported one.

4) Boot from your createinstallmedia pendrive and install 10.13.6 on your HDD without restoring your TimeMachine.
[doublepost=1534040219][/doublepost]P.S: When upgrading Mac Pro 5,1 firmware, you need to do it from your macOS installation. You can't do it from a createinstallmedia pendrive, like on every other Mac. Now you're on the current BootROM, 0089, the same needed for Mojave betas.
 
  • Like
Reactions: TimothyR734
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.