BlueSCSI / BlueSCSI-v2

GNU General Public License v3.0
208 stars 20 forks source link

Issues installing OS X 10.2 on G4 Upgraded Power Macintosh 7600 #88

Open evanboonie opened 8 months ago

evanboonie commented 8 months ago

I have a Power Macintosh 7600 with an 800MHz G4 CPU upgrade. When attempting to install OS X 10.2 using XPostfacto, the machine will not boot. It works perfectly fine with the stock 200MHz 604e CPU and will also work with a 400MHz G3 upgrade I have if I set the CPU throttling option in XPosfacto to "8". No level of throttling seems to let the machine boot with the 800MHz CPU. When booting, I just see an OpenFirmware screen with the message "Can't LOAD from this device". It loops on this forever, with the light on the BlueSCSI turning solid blue for several seconds, then going off again. The debug logs show "scsi_accel_rp2040_finishRead timeout" with some repeating commands. I have tried using the fastest SD card I have (Samsung PRO Plus) freshly formatted with the recommended SD formatting tool as suggested by the help docs, but this didn't change the behavior. I have attached a full log of letting it attempt to boot for a few cycles. This was attempted with the latest v2023.10.12 firmware. log.txt

androda commented 8 months ago

Just to restate and make sure we're on the same page:

Is this correct?

evanboonie commented 8 months ago

That is correct in the case when trying to boot OS X 10.2. I am able to boot Mac OS 8.6 and 9.2.2 from the BlueSCSI without issue using any of the CPUs.

emellisa commented 6 months ago

I have a small update on this. I recently acquired a 450MHz G4 CPU that will boot OS X 10.2 on my 7600 with the BlueSCSI, so the issue doesn't seem to be specific to a G4 CPU. It feels like the probelm has something to do with the clockspeed, as the faster the CPU I use, the higher I have to set the "CPU throttling" option in XPostfacto to. It is probably also worth mentioning that the 800MHz CPU I have has an L3 cache, where all other CPUs I own do not. This issue doesn't seem to occur with a real Quantum SCSI HDD, so it does seem to have something to do with the BlueSCSI. I'm not knowledgeable enough about the boot process and SCSI bus in these machines, but my rough guess is that the faster CPUs under OS X are trying to initialize the SCSI device faster and are not waiting long enough for the BlueSCSI to respond. I have also tried the v2023.11.16 firmware but that made no difference.

erichelgeson commented 1 month ago

Could you try 1) powering via external power, and 2) using a different scsi cable? I've used BlueSCSI on G4's and very fast SCSI cards without issue. We have seen when the actual scsi controller is overclocked it can mess with timing, but the BlueSCSI and the controller can stay in sync and negotiate up to 10mb/sec. If you havent please also checkout the Troubleshooting guide in the wiki.