Closed Plunger55 closed 5 years ago
Not currently - I haven't had time to put together the ivy process yet as there are some special considerations to make. I plan to work through some of that in the near future though.
Thanks for responding.
Looking forward to the update.
Sent from my iPad
On Nov 27, 2018, at 6:17 PM, CorpNewt notifications@github.com wrote:
Not currently - I haven't had time to put together the ivy process yet as there are some special considerations to make. I plan to work through some of that in the near future though.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
I have been struggling to learn about and install a working version of Mojave. Dell Optiplex 9010 SFF. (It has Windows 10 Pro installed and works.) CPU: i7 3770 Chipset: Q77 GPU: Intel HD 4000 RAM: 8GB
I was able to get the Mojave installer on the USB Disk to mount and had a first attempt to install to a crucial SSD in the Dell. It did one restart and then seemed to freeze. I looked at the SSD on my Mac and saw that many installer pieces had copied over but the full installation never completed.
Any advice would be very much appreciated.
I have been struggling to learn about and install a working version of Mojave. Dell Optiplex 9010 SFF. (It has Windows 10 Pro installed and works.) CPU: i7 3770 Chipset: Q77 GPU: Intel HD 4000 RAM: 8GB
I was able to get the Mojave installer on the USB Disk to mount and had a first attempt to install to a crucial SSD in the Dell. It did one restart and then seemed to freeze. I looked at the SSD on my Mac and saw that many installer pieces had copied over but the full installation never completed.
Any advice would be very much appreciated.
Make sure you ONLY have the 1 SSD in there for the Mac 'side'. Pull the Windows drive OUT of the chassis completely.
Even on real macs (I have 7..!!) Mojave gets 'confused' if there is more than one drive/partition, or even a USB installer - a proper "create install media" one - present.
As I do research to find out what works, or is intended to work with, the different processors and chipsets I realize that there might be a way to remove the guess work. I don't know. This idea occurred to me this evening. Can someone organize a list that shows what each processor group needs to function on a basic level. I am not sure if that is clear. I am referring to the vanilla settings needed to boot each processor + chipset group. I feel that this could help reduce the number of repetitive sounding messages on the forums or just at least provide a reference point. If it was a visual representation that would also help some of us to better understand where to start;-) I have managed to get one Hackintosh running, except for the ethernet port (which might need an intel driver). Also, had anyone suggested creating a repository database for each of the CPU+chipset groups? I think that the information for each submittal doesn't need to be tested, but should include a description of the hardware and a Config.plist. I am asking this just to make the whole process a little more efficient. I could be wrong, or could be asking for something very large and expensive to implement and support. I really don't know what it would take to do this. Also, I am thinking that it would be very helpful, but don't have any way to gather or present data showing there is a need. Anyway, good night!
@TemKu Ultimately that's the goal with the guide this repo is attached to. To be fair though, it's a hefty chunk of work to maintain, and keeping up with the pace of the community (and Apple's releases) can be a bit much. I haven't been able to sit down and work on the Ivy changes - but they're typically pretty close to the Haswell setup with a few changes:
0x0166000A
for the AAPL,ig-platform-id if you connect your display to the mobo's outputs - or 0x01620006
/0x01620007
for iMac13,1/iMac13,2 respectively if you only use the iGPU for compute tasks (none of these are required if you don't have a compatible iGPU)0x1e3a8086
As an aside, I have experienced what @13parsecs mentioned as well - Mojave's installer seems to be quite easy to confuse if multiple drives are present (it always picks one of my random data drives to search for the macOS Install Data folder) - so limiting the variables there could help.
-CorpNewt
I have a GA-Z68M-D2H motherboard with a i7-3770 CPU. Do you have the matching Ivy Bridge config.plist?