-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2024.12.03 prevents booting from ZuluSCSI v1.1 #480
Comments
@Jakeysp thanks for the report. it would be helpful to have a debug log from the ZuluSCSI V1.1 when it enters this state. I will attempt to replicate on this end with an LC III and V1.1 running the same firmware. |
@Jakeysp I'm able to reproduce what I believe is the same behavior, and can confirm that there appears to be a regression. For now, the appropriate course of action is to downgrade to the previous release, v2024.11.1 if you are using a ZuluSCSI V1.0 (mini only), V1.1, or V1.2. We will investigate and resolve this regression in the coming days, at which point we will release a V1.x-specific hotfix. |
Thanks! I think I also updated the firmware on my V1.0 mini and couldn't replicate it. I've downgraded the V1.1 and am having no issues now. |
@Jakeysp try the firmware for the V1.1 here https://github.com/ZuluSCSI/ZuluSCSI-firmware/actions/runs/12247149653 |
Confirmed fixed, thanks guys! |
@Jakeysp I've now cut a V1.1/V1.2-specific hotfix release, which can be downloaded at https://github.com/ZuluSCSI/ZuluSCSI-firmware/releases/download/v2024.12.09-v1.1plus/ZuluSCSIv1_1_plus_2024-12-09.bin |
Problem
I have a ZuluSCSI v1.1, which hangs on boot after ZuluSCSIv1_1_plus_2024-12-03.bin is loaded. The system being used is an Apple Macintosh LC III.
Symptoms
Troubleshooting Attempted
I've attached the zululog from 2024.12.03, the only difference between this and one from 2024.11.01 is that the following two lines are missing from the newer firmware's output:
[908ms] Initialization complete!
[9906ms] Toolbox enabled = 0
zululog.txt
The text was updated successfully, but these errors were encountered: