My A1200 freezes all the time

[walkero]

Hello guys,
I have a problem with my amiga1200. Recently I bought
the 3.1 rom module to update my old 3.0 module. I used to have a partition with OS3.9. When I changed the roms I decided to format this partition. So I did a format with FFS and then changed my old 3.0 roms to 3.1.

I tried to boot from my WB3.1 boot disk so that I could install OS3.9 from my cd. When WB showed up the first freeze appeared. After many retries I managed to install 3.1 to the hd.

After a cold reboot I tried to boot from my hard disk so that I could install my powerflyer and my cdrom, to install OS3.9. Unfortunately, the freezes from times to times never stopped. After many tries I managed to install OS3.9 but now after the reboot I can't install anything because when the install comes up everything freezes. The CGX drivers are not installed yet because my system freezes at the start of the installer. Alse the setpatch command at the startup-sequence is "SETPATCH QUIET NOROMUPDATES scsi.device"

My hardware is an Amiga1200 with BVISION, blizzardPPC 603/175/040/25 with 96MBram and powerflyer, 6GB HD and 350W PSU. The motherboard is 1v1d.

I have to mention that before the update everything worked just fine with no problems at all.

Thanks for your time guys.

[lionstorm]

Hi Walkero,
most freezes/instability for A1200PPC+BVPPC are usually due to overheating of the ppc card but it may not be your case since it was working fine before.
Could also be a library problem (68040.library and 68060.library).
Could also be you did not plug the 3.1 rom to the bottom.
Could be you are using a outdated version of setpatch or installer.
Have a look on internet about OS3.9 FAQ from greg donner (was it dorner?). I am sure you will find a lot more info than I listed here.
Lio

Edit : I dig the address for you : http://www.gregdonner.org/   

[walkero]

Thanks my friend for your fast reply. I think that the heat is not a problem because the freaze of my computer comes after a few minutes of work. Even though the case is all open and two coolers working in full time.

Thanks also for the link. I'm gonna have a look there now.

[lionstorm]

Well there is a kind of contradiction with overheating :
what I read a little bit everywhere is that the contact between the blizzardPPC and the BVPPC needs to get warm to work properly so you will not see a freeze right from the start. But if it becomes too warm, you will experience sudden lockups and freezes with no apparent reason... except overheating. Be sure to have a fan on the BVPPC as well, not only on the BlizzardPPC.
Lio

And bear in mind that an open case is a very bad idea, ventilators are here to extract hot air out of the tower, so if the tower is open, they dont do their jobs and you still can get overheating problems, even more.

[Xand]

Hello walkero,
    Another thing that's mentioned in the PowerFlyer docs is commenting out the line for scsi.device in the NSDconfig file or adding NONSD (or something like that - I'll look it up when I get home) to your setpatch line.

    I have my setpatch line set up like yours and commented out the scsi.device line in the NSDconfig and don't have the lockups.

[walkero]

thanks guys for your help!
Xand: I tried that but nothing changed. Also I forgot to mention that when I boot from my hd partition, an error occures which is saying that MDH2: partition crashed and to reboot.
I removed and the memory simms one by one but nothing changed.
I checked the SETPATCH and the Installer version and these are the latest.
The one thing that I have to try is to raise more the  powerflyer because it is real close to the BVision.

[sumner7]

My A1200 freezes all the time

Then why don't you take it out of the fridge then?

[bloodline]

walkero wrote:
thanks guys for your help!
Xand: I tried that but nothing changed. Also I forgot to mention that when I boot from my hd partition, an error occures which is saying that MDH2: partition crashed and to reboot.
I removed and the memory simms one by one but nothing changed.
I checked the SETPATCH and the Installer version and these are the latest.
The one thing that I have to try is to raise more the  powerflyer because it is real close to the BVision.

Do you still get crashes if you boot from your Workbench Floppy disk?

[sumner7]

bloodline wrote:

walkero wrote:
thanks guys for your help!
Xand: I tried that but nothing changed. Also I forgot to mention that when I boot from my hd partition, an error occures which is saying that MDH2: partition crashed and to reboot.
I removed and the memory simms one by one but nothing changed.
I checked the SETPATCH and the Installer version and these are the latest.
The one thing that I have to try is to raise more the  powerflyer because it is real close to the BVision.

Do you still get crashes if you boot from your Workbench Floppy disk?

Don't keep it in your car or drive safely and it won't crash!

[walkero]

bloodline: Unfortunately yes...I believe that it is a matter of overheating.

Sumner7: Nice jokes my friend...

[sumner7]

Sumner7: Nice jokes my friend...Quote:

Cheers walkero. :pint:

[Framiga]

Hi walkero ,

the "SETPATCH QUIET NOROMUPDATES scsi.device" is a nonsense itself.

With the NOROMUPDATE option, you'll skip ALL the rom update.

If you want to skip ONLY the scsi.device you must type:

SETPATCH QUIET SKIPROMUPDATES "scsi.device"

Ciao

[walkero]

Lately I found out that the ata3.driver v6.1 of the
powerflyer freezes my amiga and returns an error:

"MDH2
Program failed (error #80000004)
Wait for disk activity to finish"
But nothing happens. Nor the mouse moves.

If I deactivate the driver. I see only the first two
devices but my amiga works fine...
Is this a compatibility problem of the ROM 3.1 with
the powerflyer?

If anyone has a clue about this, please help me....

[Thematic]

From what I remember of reading some mailing lists thoroughly, some drivers can gain from doing a 'cpu nodatacache' and 'cpu datacache' pair just about the driver activation.

Another thought: you can type 'version' in shell? It should say Kickstart 40.68. That is I think the driver is trying to use scsi.device and if it can't recognize it, has to fail/abort. Why it wouldn't recognize, is harder to tell.