macOS High Sierra (10.13) Unsupported Macs Thread

[mrploppy]

Yes, there is a nice difference. You can do a little experiment: delete a Photo or little videofile in a iMessage threat of choice. On MacOS 10.13.3, you will see this media file will be deleted, but it will not be deleted in the same threat on your iOS device. (In beta MacOS and beta-iOS it does) This will also be the case for individual threats between Mac OS and iOS.

Ah, OK. Dank je wel.

 

[SpinThis!]

DosDude1 came to the rescue for me: apparently nVidia is the way to go. I bought a GTX 680 graphics card and now High Sierra works on my Mac Pro 3,1

Can anyone recommend a reputable seller to get a 680 for my 3,1?

10.13 works pretty well on my Mac Pro 3,1 aside from the red/blue redraw errors on the 5770 and wake from sleep is broken. Appears like swapping out to nVidia would solve both issues.

 

[nekton1]

dosdude1

Could there be a way to support fast M.2 NVMe SSD boot drives on a MP3,1 using an PCIe x 4 slot to NVMe adapter card by adding EFI NVMe support now in the clover bootloader to your bootloader we are using to get APFS support?

Just a thought about how to squeeze more speed from the aging 3,1.

Thanks for all your work on this BTW,

Best

nekton1

 

[dosdude1]

dosdude1

Could there be a way to support fast M.2 NVMe SSD boot drives on a MP3,1 using an PCIe x 4 slot to NVMe adapter card by adding EFI NVMe support now in the clover bootloader to your bootloader we are using to get APFS support?

Just a thought about how to squeeze more speed from the aging 3,1.

Thanks for all your work on this BTW,

Best

nekton1

Yeah, shouldn't be too difficult, just have to load the EFI driver when it starts.

 

[jmp473]

Can anyone recommend a reputable seller to get a 680 for my 3,1?

10.13 works pretty well on my Mac Pro 3,1 aside from the red/blue redraw errors on the 5770 and wake from sleep is broken. Appears like swapping out to nVidia would solve both issues.

I got a used EVGA off eBay (for PC) it works near-perfectly OOTB on my 3,1. Are you specifically looking for one that's already been flashed?

(So, I have no experience with (for example) Mac Vid Cards but I have learned a great deal from their posts - would likely use them if I could afford the additional ±$50)


P.S. Many Thanks Dosedude1

 

[nekton1]

I did exactly that—bought (for 3000 yen) evga 680 for PC and flashed it in a Windows machine with the Mac efi rom available at the netkas site. Been rock solid ever since.

I got a used EVGA off eBay (for PC) it works near-perfectly OOTB on my 3,1. Are you specifically looking for one that's already been flashed?

(So, I have no experience with (for example) Mac Vid Cards but I have learned a great deal from their posts - would likely use them if I could afford the additional ±$50)


P.S. Many Thanks Dosedude1

[doublepost=1521623854][/doublepost]
[doublepost=1521623922][/doublepost]

Yeah, shouldn't be too difficult, just have to load the EFI driver when it starts.

There is a scrap here about it:

https://sourceforge.net/p/cloverefiboot/discussion/1726372/thread/8b69cb9b/

 

[danyMRF]

Hi All,

I can not create the USB bootable pendrive for upgrade to macOS High Sierra 10.13.3 on Mac mini (Late 2009) - 2.26 GHz Intel Core 2 Duo processor - 4GB DDR3 1067 MHz memory - NVIDIA GeForce 9400 graphics 256MB - OS X 10.11.6 El Capitan (Build 15G19009) - System Integrity Protection: Disabled.

For the creation I use macOS High Sierra Patcher Tool version 2.5.4 and install macOS High Sierra.app 10.13.3 version 13.3.02 (I have downloaded through the tool).

As a USB device I use a 16GB pendrive formatted in HFS+ (journaled) with GUID partition map, volume name "install".

The creation procedure is done from the internal disk with OS X El Capitan, but I'm going to upgrade macOS Sierra 10.12.6 (with all the security updates installed) that I have on an external USB drive.

Trying to boot with the Alt/Option key presses displays a USB drive with the name "install" but, selecting it, the Apple logo appears for a few seconds, immediately afterwards, the prohibition signal and the Mac starts with the internal hard disk.

What can I do?

Finally, the following messages are logged in the Console after booting from the internal disk, which may be related to the problem:

25/03/18 13:40:27,000 kernel[0]: hfs: mounted install on device disk1s2
25/03/18 13:44:26,459 com.apple.kextd[45]: Note: /Volumes/install/System/Library/Kernels/kernel: No such file or directory
25/03/18 13:46:18,040 deleted[303]: normalizeUserMountpoint:791 volRoot failed for /Volumes/install
25/03/18 13:46:18,040 deleted[303]: _validateVolume:813 unable to normalize volume: "/Volumes/install", vol: (null)

Thank you all!


Note:

I tried to perform the procedure of creating also from my installation of macOS Sierra (patched) but the result is the same: the Mac mini does not boot from the USB stick!

The SHA1 Checksum of "InstallESD.dmg" is 726c7516fdbe33ae3f2384ba1ce7efcda4335776 and the SHA1 Checksum of "BaseSystem.dmg" is d64fd8e6ca5287b80fd785a3a1a151da92b8369d and coincide perfectly to those published on this page:

https://github.com/notpeter/apple-installer-checksums#mac-osx-installers-sha1-checksums

 

[Computers 4 U LLC]

Hi All,

I can not create the USB bootable pendrive for upgrade to macOS High Sierra 10.13.3 on Mac mini (Late 2009) - 2.26 GHz Intel Core 2 Duo processor - 4GB DDR3 1067 MHz memory - NVIDIA GeForce 9400 graphics 256MB - OS X 10.11.6 El Capitan (Build 15G19009) - System Integrity Protection: Disabled.

For the creation I use macOS High Sierra Patcher Tool version 2.5.4 and install macOS High Sierra.app 10.13.3 version 13.3.02 (I have downloaded through the tool).

As a USB device I use a 16GB pendrive formatted in HFS+ (journaled) with GUID partition map, volume name "install".

The creation procedure is done from the internal disk with OS X El Capitan, but I'm going to upgrade macOS Sierra 10.12.6 (with all the security updates installed) that I have on an external USB drive.

Trying to boot with the Alt/Option key presses displays a USB drive with the name "install" but, selecting it, the Apple logo appears for a few seconds, immediately afterwards, the prohibition signal and the Mac starts with the internal hard disk.

What can I do?

Finally, the following messages are logged in the Console after booting from the internal disk, which may be related to the problem:

25/03/18 13:40:27,000 kernel[0]: hfs: mounted install on device disk1s2
25/03/18 13:44:26,459 com.apple.kextd[45]: Note: /Volumes/install/System/Library/Kernels/kernel: No such file or directory
25/03/18 13:46:18,040 deleted[303]: normalizeUserMountpoint:791 volRoot failed for /Volumes/install
25/03/18 13:46:18,040 deleted[303]: _validateVolume:813 unable to normalize volume: "/Volumes/install", vol: (null)

Thank you all!


Note:

I tried to perform the procedure of creating also from my installation of macOS Sierra (patched) but the result is the same: the Mac mini does not boot from the USB stick!

The SHA1 Checksum of "InstallESD.dmg" is 726c7516fdbe33ae3f2384ba1ce7efcda4335776 and the SHA1 Checksum of "BaseSystem.dmg" is d64fd8e6ca5287b80fd785a3a1a151da92b8369d and coincide perfectly to those published on this page:

https://github.com/notpeter/apple-installer-checksums#mac-osx-installers-sha1-checksums

You need to try a different USB stick, then it should work fine.

 

[danyMRF]

@dosdude1

In macOS High Sierra Patcher Tool version 2.5.5 (released today) the following messages appear in the Verbose Output:

cp: /Volumes/macOS High Sierra Patcher/macOS High Sierra Patcher.app/Contents/Resources/CDIS: No such file or directory
cp: directory /Volumes/install/System/Installation/CDIS/macOS Installer.app/Contents/Resources does not exist

And, of course, the USB stick still will not boot on Mac mini (Late 2009).

Many Thanks @dosdude1 for your indispensable help for users with old Macs!


UPDATE:
Also with the "Second Edition" of the version 2.5.5, despite the messages in the Verbose Output have disappeared, the USB stick refuses to booting the Mac mini (Late 2009).

Output from bless --info... command:

bless --info /Volumes/install
finderinfo[0]:     33 => Blessed System Folder is /Volumes/install/System/Library/CoreServices
finderinfo[1]:  44903 => Blessed System File is /Volumes/install/System/Library/CoreServices/boot.efi
finderinfo[2]:      2 => 1st dir in open-folder list is /Volumes/install/
finderinfo[3]:      0 => No alternate OS blessed file/folder
finderinfo[4]:      0 => Unused field unset
finderinfo[5]:     33 => OS X blessed folder is /Volumes/install/System/Library/CoreServices
64-bit VSDB volume id:  0x2A7F730BE392E33A

They are correct?

 

[jhowarth]

Has anyone been testing the beta seeds of 10.13.4? When applying the beta Software Updates for 10.13.4, I have been seeing an error notification appear that some updates could be installed. Otherwise, this seems like a non-fatal error in the upgrade from 10.13.3 and the machine works fine as 10.13.4. This issue appears somewhat sporadic in its occurrence.

 

[Computers 4 U LLC]

Has anyone been testing the beta seeds of 10.13.4? When applying the beta Software Updates for 10.13.4, I have been seeing an error notification appear that some updates could be installed. Otherwise, this seems like a non-fatal error in the upgrade from 10.13.3 and the machine works fine as 10.13.4. This issue appears somewhat sporadic in its occurrence.

So far all the betas have been working fine on my iMac 9,1 test machine.

 

[jhowarth]

So far all the betas have been working fine on my iMac 9,1 test machine.

The issue is rather perplexing. I reproduced the 10.13.4 update 'failure' last night on an AppleRAID volume which was freshly erased and installed with the 10.13.3 full installer using the current High Sierra Patcher. However I have also seen this issue with a non-AppleRAID volume on a separate HD. The only commonality is that I have been testing Ubuntu bionic and the exact macOS volume whose EFI partition 'gets' the ubuntu directories has varied over time. So I guess it is possible that I am seeing some weird interaction with that. If that is the cause of the problem, it is rather strange that the High Sierra Patcher installer never has an issue reinstalling over a previous installation with those EFI directories (which survive erasing the volume afaik).

 

[roronl]

it's working fine on this very old beast.

 

[RogueB]

I found two things that cause the non working AirDrop/Continuity.
- Did u removed the old BT Card, or if you replaced only the WiFi? Both 94360CD and 94331CD comes with BT so u need to remove or disconnect the original module.
- U need to repatch the WiFi.kext and a BT plist every time when Apple overwrites it.

I have a mid 2009 MacBook Pro 5,2. I did not have to replace bluetooth or wifi, however, air-drop still does not work. What is the procedure for updating the WIFI.kext and the BT plist?
Thanks for any information on the subject.

 

[danyMRF]

You need to try a different USB stick, then it should work fine.

I tried with another USB stick, but this, one difference of the other, is not even shown in Startup Manager!

You could give me some other suggestions, I thank you in advance!

 

[Computers 4 U LLC]

I tried with another USB stick, but this, one difference of the other, is not even shown in Startup Manager!

You could give me some other suggestions, I thank you in advance!

Others might have some other suggestions but I still feel it is probably the USB drive(s) you are using. The installer seems to be kind of picky about what drives it likes.

 

[jhowarth]

The issue is rather perplexing. I reproduced the 10.13.4 update 'failure' last night on an AppleRAID volume which was freshly erased and installed with the 10.13.3 full installer using the current High Sierra Patcher. However I have also seen this issue with a non-AppleRAID volume on a separate HD. The only commonality is that I have been testing Ubuntu bionic and the exact macOS volume whose EFI partition 'gets' the ubuntu directories has varied over time. So I guess it is possible that I am seeing some weird interaction with that. If that is the cause of the problem, it is rather strange that the High Sierra Patcher installer never has an issue reinstalling over a previous installation with those EFI directories (which survive erasing the volume afaik).

Looking through the install log, the issue seems to be cause by the 10.13.4 SU being overly aggressive in applying the associated 10.13.4 Recovery Partition update (which an AppleRAID drive will lack).

 

[EugW]

The 10.13.4 install went well.

Interestingly, the 2.3 GB install on this 2.0 GHz Core 2 Duo with old slow Kingston V+100 SSD was way faster than the 7xx MB iOS 11.3 install on my iPhone 7 Plus.

Unfortunately, the NVIDIA GeForce 9400M h.264 video glitch is still there.

 

[swamprock]

The 10.13.4 install went well.

View attachment 756147

Interestingly, the 2.3 GB install on this 2.0 GHz Core 2 Duo with old slow Kingston V+100 SSD was way faster than the 7xx MB iOS 11.3 install on my iPhone 7 Plus.

Unfortunately, the NVIDIA GeForce 9400M h.264 video glitch is still there.

I'm about to give the update a go on my 2009 MBP 13" with the same video chip. Sad to hear that the glitch is still there, but I can live with it...

 

[EugW]

I'm about to give the update a go on my 2009 MBP 13" with the same video chip.

Worked fine on my 2009 MacBook Pro 13" 2.26 GHz too.

Sad to hear that the glitch is still there, but I can live with it...

Same here. I'd rather have that rare glitch than stick with Sierra, mainly for file format and disk format support.

One can only hope though that Apple will fix this by summer.

Edit:

Now that I think about it I did get a message saying not everything was installed but when I checked the App Store it said there were no updates and About This Mac confirmed 10.13.4.

The reason I thought about this again though is because it is taking significantly longer to install on my 2017 i5 iMac with 1 TB PCIe SSD and 24 GB RAM.

 

[swamprock]

Now that I think about it I did get a message saying not everything was installed but when I checked the App Store it said there were no updates and About This Mac confirmed 10.13.4.

The reason I thought about this again though is because it is taking significantly longer to install on my 2017 i5 iMac with 1 TB PCIe SSD and 24 GB RAM.

I got the same message but everything seems ok.

 

[evertjr]

I had filled a bug report to Apple about the 9400m glitch and an engineer replied to me saying to test again on 13.4 GM and if it's not fixed then fill another bug report. So it is still happening? Unfortunately I've downgraded to El Capitan because of this issue.

Someone please send a bug report to Apple including sysdiagnose file (as he requested to me), I hope we get this issue fixed by the end of high Sierra cicle

 

[EugW]

I had filled a bug report to Apple about the 9400m glitch and an engineer replied to me saying to test again on 13.4 GM and if it's not fixed then fill another bug report. So it is still happening? Unfortunately I've downgraded to El Capitan because of this issue.

Someone please send a bug report to Apple including sysdiagnose file (as he requested to me), I hope we get this issue fixed by the end of high Sierra cicle

I’ve been asking the supported MacBook6,1 owners to file the bug report.

 

[doobydoooby]

Installed 10.13.4 update on my Mac pro 3.1 2008 today - installation went well with no error messages but it turned off and greyed out bluetooth availability. Running Onyx automation scripts and rebooting the machine fixed it.

 

[EugW]

I got the same message but everything seems ok.

Interesting. I wonder if something actually isn’t installing. But 10.13.4 is working fine so far.