Blizzard 1260 and FastATA mkIV issues
- Thread starter thgill
- Start date
- Replies 33
- Views 3871
Hmmmm. Interesting.
I am starting to wonder if this is a 3.0 rom issue?
I tried blizkicking a 3.1 rom into memory but that didn't seem to help.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
---------- Post added at 08:29 ---------- Previous post was at 08:02 ----------
Or perhaps a SFS filesystem related issue?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
I am starting to wonder if this is a 3.0 rom issue?
I tried blizkicking a 3.1 rom into memory but that didn't seem to help.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
---------- Post added at 08:29 ---------- Previous post was at 08:02 ----------
Or perhaps a SFS filesystem related issue?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Here is my startup-sequence
I have the scsi.device lines commented out as the ATA3.driver handles that.
Setpatch is called via the usual way.
I have moved the ATA3.driver line both at the top of the startup seq and below Setpatch and it doesn't make a difference.
I have the scsi.device lines commented out as the ATA3.driver handles that.
Setpatch is called via the usual way.
I have moved the ATA3.driver line both at the top of the startup seq and below Setpatch and it doesn't make a difference.
I am thinking the FastATA is keeping the Blizzard 1260 from initializing.
When the machine boots up I get a brief amount of activity from the HD and floppy drive clicks once and then a black screen and nothing.
Press Ctrl+A+A and after a few seconds I see the flashing color bars from the Blizzard 1260 and the machine boots up ok.
If I disable the FastATA board in the startup-sequence and power off the machine and power it back up, I straight away see the flashing color bars and it boots into workbench.
It SEEMS that the FastATA is prohibiting the 1260 from even initializing until I soft reset the machine.
When the machine boots up I get a brief amount of activity from the HD and floppy drive clicks once and then a black screen and nothing.
Press Ctrl+A+A and after a few seconds I see the flashing color bars from the Blizzard 1260 and the machine boots up ok.
If I disable the FastATA board in the startup-sequence and power off the machine and power it back up, I straight away see the flashing color bars and it boots into workbench.
It SEEMS that the FastATA is prohibiting the 1260 from even initializing until I soft reset the machine.
Do you have another A1200 to install the hardware in? Does the same thing happen? If so it's probably a revision/timing issue.
Otherwise I would still try to find some 3.1 Roms, they will be worth having for OS3.9 and also might just fix this issue
If the hardware isn't initializing then it can't be anything in the SS
Otherwise I would still try to find some 3.1 Roms, they will be worth having for OS3.9 and also might just fix this issue
If the hardware isn't initializing then it can't be anything in the SS
SORTED!!
Here what I did to fix it:
I uncommented out the lines for Scsi.device. I commented them out originally because I would get an error message at boot (after Ctrl+A+A) about the scsi.device already being present.
Next I moved the ATA3.driver line in the startup-sequence to BELOW the Setpatch line. The combination of these two things now allow the machine to boot up right away with no soft reset being involved. Either one by themselves wasn't enough.
Not sure why this is as I thought the ATA3.driver handled all scsi.device calls, but I will take it.
Now to tackle this noisy fan on it...
im glad you got it sorted
+1
Mozilla/5.0 (Linux; U; Android 2.3.5; en-gb; HTC_DesireHD Build/GRJ90) AppleWebKit/533.1 (KHTML, like Gecko) Version/4.0 Mobile Safari/533.1
I believe that the ATA3.driver intercepts calls to the SCSI.device and changes just the hardware enabling of the advanced PIO modes. Using the more recent scsi.device increases the ability to use other devices and makes it more reliable. So the scsi.device needs to be "in place" prior to the ATA3.driver overlay.
