macOS 10.14 Mojave on Unsupported Macs Thread

[Kevbasscat]

I updated supplemental 2 on my 8,2 via QTA and I got the partial loading screen then a quick black screen and then the white screen, as shown below. I tried rebooting three times, same story. I booted verbose and got almost 3 pages of info, but the last page ended at the very top with the flashing bar, and I was not able to record the output. How can I record the output?

Also, @dosdude1 this is the 8,2 that you performed your firmware fix to disable the GPU from being recognized, but I'm not so sure it worked.. My wife, being even less computer wise than me was watching Netflix on it, when she gave it back, she said, "oh btw, it shut down 5 times while I was watching my movie and it got very hot." I started it up this morning and all seemed good, then this with the update. Could any of these behaviors be related in any way? You loaded 10.14.4 on it, and I'll need to make a USB patcher from my 18,3 iMac if I need to reinstall. I read somewhere that 10.14.4 was the last version that had hardware support, is that true and can I re download it from a version of your patcher to keep it, or am I mistaken?
Dang! The things I don't know, fill libraries. I'll also need to remove that ssd and replace it if it needs to be erased as I juust put some photos on it 10 mins before this issue and obviously didn't back it up, and no longer have access to those photos, or can I install and kepp my data?

Edit:
After reading some more, should I just make a patcher and run post install on it with rebuild?

 

[Macschrauber]

@dosdude1

Mac Pro 3.1 with Kepler GPU

Patcher 1.3.3

Doesnt get 10.14.6.00 to 14.6.06 to boot.

Downloaded Patcher and Mojave Install thru Patcher 1.3.3 today

Got stuck in the middle of the progress bar, verbose boot pic attached where it stucks. Looks like graphics kext got a memory leak.

View attachment 864899

solved it:

deleted / renamed NVDAStartup.kext in s/l/e in Patcher Disk to dont get loaded.

I just waited a while and the screen got black. So I knew the system was not stuck. It was alive but got no picture. I even was able to shut down the mac with ctrl-alt-cmd-eject.

So I fiddled a while with the nvidia kexts - if NVDAStartup.kext got disabled the patcher continued to boot and displayed the GUI.

Problem sorted.

 

[M3Stang]

Hello! I am having a little trouble with installation. I used my brothers MacBook to get the Mojave installer on a flash drive (64gb) I had erased to right before to set it to the right format. I have the Mojave Patcher and it verified the macOS Mojave installer. Just last night I factory reset my MacBook so theres no other files or applications (except for the installer of Minecraft that I was planning on installing but then I found this forum). My problem is that whenever I click "Start Operation" it goes through this log


/dev/disk1 GUID_partition_scheme
/dev/disk1s1 EFI
/dev/disk1s2 Apple_HFS /private/tmp/installesd
Validating target...done
Validating source...done
Could not unmount volume "/Volumes/Jonathan" (Resource busy)
"disk1" unmounted
"disk1" ejected


Then I get an error saying

Restore Error
An error occurred while restoring the BaseSystem image to the target volume.

(I manually typed this is the space between each message might be altered)

Other info;
mid 2010 macbook pro 13 inch
the flash drive was a SanDisk Cruzer Glide
my macbook is version 10.12.6

I have tried installing it through the USB and ive copied it to my desktop and tried that too
my discord is DrThrax_#4592
someone, please give me a hand with this.

I am using this guide from dosdude1 and received this error from verbose output

/dev/disk2 GUID_partition_scheme
/dev/disk2s1 EFI
/dev/disk2s2 Apple_HFS /private/tmp/installesd
Validating target...done
Validating source...
The volume on device "" is not of the type Apple_HFS or Apple_UFS
Could not validate source - Device not configured
"disk2" unmounted
"disk2" ejected

Note that the tool does not allow copying directly from log, I had to type by hand, typo may happen What I find strange:

• After this message, the USB drive icon is still showing on the desktop, so no idea what disk2 is.
• The USB's label is Untitled, but the error said device "".

What I have tried:

• I formated my usb, both using a Mojave machine and a El Capitan machine, using format OSX extended (Journaled)

Has any of you successed with a usb stick / thumb drive and not an external hard drive?

I would suggest that both of you try a different flash drive. I had a similar issue with one flash drive, tried another one, and it worked fine.

 

[EmilHolub]

(Not sure if cross-posting is a rules violation, but just in case there are lurkers here who don't visit the Catalina thread: )

I've been away from Mac development for a few months, but now I'm back.

Guinea Pigs Beta Testers Wanted

Some months ago, I created an SSE 4.2 emulator for the Mac Pro 3,1 (and potentially older systems as well). I didn't get to broadly test or release it before my focus had to shift elsewhere. It's been in more or less daily use here, mostly on Mojave, but it's also been tested (at least briefly) on High Sierra and Catalina Beta 7. It allows newer AMD video cards to run full Metal.

It's only ever been tested on my one Mac Pro 3,1, with my one AMD RX 570 video card. I'd like to test it on a broader sample of machines/video cards before throwing it out for public use. So, if you have a Mac Pro 3,1, a newer (metal-compatible) AMD video card, and some time to spare, send me a DM/PM/Whatever-they-call-private-messages-on-this-forum and I'll send you the package. NOTE: The installer is still a work in progress, so if you're not comfortable copying files to /S/L/E and invalidating the cache, we both might be better served if you wait for the full release.

Thanks in advance. (Here's where I find out if I'm one of the last three or four MP3,1 users in existence...)

Is there still a chance to receive a package for testing? Thank you.

 

[tn-xyz]

does anyone know about the state of continuity for unsupported macs on mojave and perhaps point me in the right direction?
with an upgraded bluetooth/wi-fi card i can't seem to get it working and CAT hasn't been updated for a while now.

 

[the griffin]

So I've opened my mini and the chip ID is MX25L3205D.

Still I'm wary about running the APFS ROM patcher because of the other 2 guys on this thread who confirmed the chip ID and still bricked their mini 3,1.

The patcher default ID for this model is MX25L3206E. It'd be great if anyone who ran the patch on the same machine (late 2009 mini 3,1, mine is a 2.53 Ghz but other models would be helpful too) could let me know which one they chose.

 

[K two]

So I've opened my mini and the chip ID is MX25L3205D.

View attachment 866064

Still I'm wary about running the APFS ROM patcher because of the other 2 guys on this thread who confirmed the chip ID and still bricked their mini 3,1.

The patcher default ID for this model is MX25L3206E. It'd be great if anyone who ran the patch on the same machine (late 2009 mini 3,1, mine is a 2.53 Ghz but other models would be helpful too) could let me know which one they chose.

I managed to brick a Mini3,1 using the APFS ROM patcher by being impatient. I quit the process after 43 minutes, apparently the patcher can require 45 minutes to complete on a Mini3,1. That SOS Mini3,1 contains the MX25L3205D chip. YMMV

 

[the griffin]

I managed to brick a Mini3,1 using the APFS ROM patcher by being impatient. I quit the process after 43 minutes, apparently the patcher can require 45 minutes to complete on a Mini3,1. That SOS Mini3,1 contains the MX25L3205D chip. YMMV

Thanks for your reply, so yours is the third bricked mini 3,1 by running the APFS ROM patcher on this thread. Now I understand why it's so easy to brick them, 45 minutes is more than I would wait unless I knew it takes that long. I guess I'll go with it then when I get some time. Thanks for the input.

 

[Macschrauber]

but you can unbrick the mini by programming the sip chip with a sip programmer.

Doesnt the apfs rom patcher stores a backup of the current rom ?

 

[the griffin]

Yes it does though according to this post the back up could be corrupted.

Yesterday I was thinking of buying the programmer beforehand and get the rom from the chip before running the patcher to make sure I have a good copy.

I think it would be a useful addition to the patcher to be able to create a backup without writing to the chip so one can check it and store it safely before attempting the writing. That's assuming there isn't already another way of doing that that I don't know of.

 

[Caveman672]

I’m running a Mac Pro 3,1 with Mojave 10.4.6. Everything is running great except for one of my usb devices not being recognized by its dedicated software but definitely being listed as a USB Device under system profiler. The device is a Clavia Nord Modular G2. It uses a software editor that works perfectly fine on the same computer under High Sierra and under Mojave when used on a natively Mojave supported Mac but under Mojave for unsupported on my Mac Pro 3,1, it doesn’t get recognized by its software editor. Does anyone have any suggestions as to what I can do?

 

[macinfo]

I’m running Lightroom Classic 8.x on a MacBookPro4,1 (512 MB VRAM) and on earlier versions the "Enhance Details" feature was working - but now at 8.4.1 - I get the following error:

Hardware not supported. Graphics card with Metal support is required.

Is there any hope, to get this still working with a patch, or are we (with those older gfx-cards) just out of luck here?

 

[jackluke]

After updated and patched to the latest 10.14.6 release (supplemental update 2), I encountered this very weird issue on a MacBook mid 2010, when I use it on battery everything works right as a supported Mac.

But if I plug the MagSafe charger, randomly (every 10 or 30 or 60 minutes) I got "kernel panic" essentially regarding this:

"panic(cpu 1 caller 0xffffff7f8586d3af): "key.hdr.kind != NEW && numsnapshots == 0\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/apfs/apfs-945.275.7/nx/jobj.c:2587"

BSD process name corresponding to current thread: warmd
(http://www.macinside.info/process.php?id=2476#)

if I force close the "warmd" process from activity monitor, it seems doesn't occur, unless warmd reload itself, anyway on battery warmd process doesn't cause any issues.

Already tried to rebuild all the caches, fresh-install, reinstall, but on power adapter the issue is still there.

From what I read on the other official apple forum sites seems a random issue also on some supported machines.

 

[saudor]

does anyone know about the state of continuity for unsupported macs on mojave and perhaps point me in the right direction?
with an upgraded bluetooth/wi-fi card i can't seem to get it working and CAT hasn't been updated for a while now.

It works perfect for me. You need to add in your board id to the white list as the CAT or the BT4L kext method isnt doing this part properly

Find your board id by running the following:

ioreg -l | grep "board-id" | awk -F\" '{print $4}'

Then run the following by replacing the board ID with yours

sudo /usr/libexec/PlistBuddy -c "Set Mac-F22586C8:ContinuitySupport true" /System/Library/Frameworks/IOBluetooth.framework/Versions/A/Resources/SystemParameters.plist

 

[KernkraftX360]

Does Mac Pro 2008, 3,1, already support Nvidia GT730 natively or with Nvidia Software update? Do let me know, because currently running Radeon without graphics acceleration and it's a pain.

 

[tn-xyz]

It works perfect for me. You need to add in your board id to the white list as the CAT or the BT4L kext method isnt doing this part properly

Find your board id by running the following:

ioreg -l | grep "board-id" | awk -F\" '{print $4}'

Then run the following by replacing the board ID with yours

sudo /usr/libexec/PlistBuddy -c "Set Mac-F22586C8:ContinuitySupport true" /System/Library/Frameworks/IOBluetooth.framework/Versions/A/Resources/SystemParameters.plist

i tried that. it doesn't work. my model is the same as yours.
CAT kills wifi after first reboot and the BT4L kext + lilu don't seem to do anything either.

 

[joevt]

Does Mac Pro 2008, 3,1, already support Nvidia GT730 natively or with Nvidia Software update? Do let me know, because currently running Radeon without graphics acceleration and it's a pain.

Mojave comes with Fermi and Kepler Nvidia drivers, so it should work?

 

[KernkraftX360]

Mojave comes with Fermi and Kepler Nvidia drivers, so it should work?

Let me spare an hour to insert the GPU and upgrade, I'll let you know if it works or not, cheers.

 

[saudor]

i tried that. it doesn't work. my model is the same as yours.
CAT kills wifi after first reboot and the BT4L kext + lilu don't seem to do anything either.

That's odd. What version of macOS are you running? Im running 10.14.3 since anything above it causes the mouse to lag horribly when the intel HD graphics is activated. Make sure you're also clearing the cache too (and see if the BT4L kext is loaded in the system info)

 

[LuisN]

Does Mac Pro 2008, 3,1, already support Nvidia GT730 natively or with Nvidia Software update? Do let me know, because currently running Radeon without graphics acceleration and it's a pain.

Don't know about gt730 but gt710 works well enough

 

[FlorisVN]

but you can unbrick the mini by programming the sip chip with a sip programmer.

Doesnt the apfs rom patcher stores a backup of the current rom ?

yep, should be easy to unbrick these eeproms.
I've done now several dumps of 2011 iMac's using a standard CH341A eeprom programmer, with clipper on these kind of eeprom chips.
It works fine, and if you made a backup you should be abble to bring live back in to your Mac.

If you did not made a backup, you can perhaps find a backup on the internet of your model, and set your own serial number inside it..

Ive used Rom tool from dosdude1 in the past before, to make backups of the rom.
can be found here :

Index of /apps/

I always make sure to make several backups and compare them. also make some using the CH341A flasher and compare them.
Do all this before even applying the APFS patcher from dosdude1, and I would say you are pretty safe here..
[automerge]1570357346[/automerge]

Let me spare an hour to insert the GPU and upgrade, I'll let you know if it works or not, cheers.

Mojave only has kepler drivers..
[automerge]1570357379[/automerge]

Mojave comes with Fermi and Kepler Nvidia drivers, so it should work?

Mojave only has kepler driver support.

 

[the griffin]

yep, should be easy to unbrick these eeproms.
I've done now several dumps of 2011 iMac's using a standard CH341A eeprom programmer, with clipper on these kind of eeprom chips.
It works fine, and if you made a backup you should be abble to bring live back in to your Mac.

If you did not made a backup, you can perhaps find a backup on the internet of your model, and set your own serial number inside it..

Ive used Rom tool from dosdude1 in the past before, to make backups of the rom.
can be found here :

Index of /apps/

I always make sure to make several backups and compare them. also make some using the CH341A flasher and compare them.
Do all this before even applying the APFS patcher from dosdude1, and I would say you are pretty safe here..

Thank you for the info, I'll use dosdude1's ROM tool app, I wasn't aware it existed.

EDIT: so I dumped the ROM with the ROMTool app using MX25L3205D and it looks ok, the S/N is showing up. One of the coming days I'll do the flashing.

 

[joevt]

Mojave only has kepler driver support.

That's what I thought, but I wasn't sure since my /System/Library/Extensions has both a NVDAGF100Hal.kext and NVDAGK100Hal.kext file (kexts dated Jun 11/2018, binaries dated Sep 20/2019).

 

[Syncretic]

@Prophet96ix and @EmilHolub -
re: SSE 4.2 emulator - please check your private messages (conversations). Sorry it took so long.

 

[Caveman672]

Does anyone have any clue as to what would cause a USB device to work fine under High Sierra on a Mac Pro 3,1 and on a natively supported Mojave MacBook Air but not work on Mac Pro 3,1 using Mojave via Dosdude’s software? The USB device is class compliant and never needed a driver installed.