Print

[patrick]

Recently my Apple collection got an over 20 years younger addition - a Mac Mini A1283 with Intel Core Duo CPU. This is my first macOS 10 machine, until now my favorite was macOS 6.0.8. Now it took me two days to get macOS 10.11 El Capitain running on this machine. Skip the next paragraph for the LisaEM bug report.

Apple sees no reason to create macOS installation media from Windows or Linux. There is no ISO file available, instead you have to run a program on a second Mac from the appropriate era to create a bootable USB drive. And it will boot. But macOS will not install because the "installation files cannot be verified". Yes, they use certificates for the EFI secure boot. And those certificates expired in 2019. So first I had to get Snow Leopard 10.6, which doesn't use Secure Boot yet, install it on the Mac Mini, and apply all available updates. Then I set the date to October 24, 2019, downloaded the El Capitain installer from Apple's support site, unplugged the LAN cable, and finally started the installation. The combination of download date, machine time, and signatures in the installer file is critical and must match. 


But now I have one good use for this modern machine in my museum: running LisaEM! Installation worked fine, configuration worked fine, but every time I want to boot anything, I get the fatal error "cpu68k_makeipclist: But! ipc is null! Stopped at cpu68k.c:cpu68k_makeipclist:1064 with code:501"

This is 1.2.7-RC4_2022.04.01 running on MacOS 10.11.6 (Core 2 Duo 2 GHz 8 GB). First I tried the dedicated installer for 10.11, then the fat one. Both installations behave the same.


---
Update: same applies to RC3a, but line 1085 instead of 1064.

[rayarachelian]

Recently my Apple collection got an over 20 years younger addition - a Mac Mini A1283 with Intel Core Duo CPU. This is my first macOS 10 machine, until now my favorite was macOS 6.0.8. Now it took me two days to get macOS 10.11 El Capitain running on this machine. Skip the next paragraph for the LisaEM bug report.

Apple sees no reason to create macOS installation media from Windows or Linux. There is no ISO file available, instead you have to run a program on a second Mac from the appropriate era to create a bootable USB drive. And it will boot. But macOS will not install because the "installation files cannot be verified". Yes, they use certificates for the EFI secure boot. And those certificates expired in 2019. So first I had to get Snow Leopard 10.6, which doesn't use Secure Boot yet, install it on the Mac Mini, and apply all available updates. Then I set the date to October 24, 2019, downloaded the El Capitain installer from Apple's support site, unplugged the LAN cable, and finally started the installation. The combination of download date, machine time, and signatures in the installer file is critical and must match. 

Yes, it's a mess what they did in terms of older machines and operating systems, this is why I want to continue supporting these machines anyway. I don't agree that older machines are useless or should be abandoned.

But now I have one good use for this modern machine in my museum: running LisaEM! Installation worked fine, configuration worked fine, but every time I want to boot anything, I get the fatal error "cpu68k_makeipclist: But! ipc is null! Stopped at cpu68k.c:cpu68k_makeipclist:1064 with code:501"

This is 1.2.7-RC4_2022.04.01 running on MacOS 10.11.6 (Core 2 Duo 2 GHz 8 GB). First I tried the dedicated installer for 10.11, then the fat one. Both installations behave the same.

---
Update: same applies to RC3a, but line 1085 instead of 1064.

I'm very sorry, but yes, RC4 is very much broken.

I didn't realize RC3a is broken in this way as well. Thank you, if that's confirmed as a bug I'd have to back much earlier.

You could try the binary for an earlier MacOS as well, maybe 10.8 or 10.7 and see if it does anything different, that would indicate a compiler/optimization issue, I suppose.