VA2000 Support Thread

[asrael22]

Alright. So I take this opportunity.

I just installed the VA2000 plus VA2000CX today in my A4000D with 3640 (with riser for 68060).
16MB on board.
Picasso96 version 2.1e (CybergraphX installed, too, but not not enabled)
AmigaOS 3.9BB2

Didn't know exactly which firmware was installed on the VA2000 when I got it (about 1 week ago).

Pulled out all other Zorro cards.

After installing the drivers 1.7.1 and restarting the modes are available in Screenmode Prefs. Choosing one and clicking test shows the default test image but the computer freezes. Only reboot possible.

Then I've flashed 1.7.1 on the card. Didn't know what was on it before as I mentioned.
Didn't change the drivers.
Now when choosing a screenmode and clicking test I'm getting a black screen. Only reboot possible.

Then I've tried flashing firmware 1.4. Copied the drivers of 1.4 (mntgfx.card, Picasso96Settings).
But that doesn't let me boot, when the Picasso96 monitor loads I'm getting a Guru Meditation.

Hmm, what else can I try?


Manfred

[asrael22]

Hi Manfred,



I didn't test this version yet, so far I use only the official Picasso96 2.0 from Aminet for development. That could make a difference. I will test it, too, tomorrow.

I recommend to stay with the latest 1.7.1 if it shows you the Screenmodes and you get the test image. What happens if you click "Use" without Test?

Cheers
Lukas

OK. Back to 1.7.1.
When I click "Use" I see a grey screen and the computer freezes.
Have to make a reset.

It can happen then that it goes into a sequential 5 or 6 reset cycle until it boots again properly.

I'll try the aminet version of Picasso96 later this afternoon.

Regarding the PAL output of the va2000cx. Some colors seem to cycle which gives a flickering kind of feeling, visually.


Manfred

[asrael22]

OK. Back to 1.7.1.
When I click "Use" I see a grey screen and the computer freezes.
Have to make a reset.

It can happen then that it goes into a sequential 5 or 6 reset cycle until it boots again properly.

I'll try the aminet version of Picasso96 later this afternoon.

Regarding the PAL output of the va2000cx. Some colors seem to cycle which gives a flickering kind of feeling, visually.


Manfred

OK. With Picasso96 2.0 from aminet it seems to be working.
All good so far.


Manfred

[asrael22]

@ mntmn

thanks for creating this support thread:D I'm the guy that can only use v1.4 firmware else my X-Surf-100 isn't seen..I'm hoping the next update or two will fix this issue but in the mean time v1.4 is working fine for me

Hmm, 1.7.1 works nicely here. I'm also having BigRam, X-Surf 100 and FastATA next to the VA2000.
Where VA1000 is the first card (bottom).


Manfred

[asrael22]

Just installed 1.8.3 today in my A4000.
But there is no gfx output on the HDMi port after boot.
I have to soft-reset to make it show something.

Manfred

[asrael22]

Just installed 1.8.3 today in my A4000.
But there is no gfx output on the HDMi port after boot.
I have to soft-reset to make it show something.

Manfred

Also the display goes to sleep mode after a while because there seems to be no signal at all.

Another question: how are the performance improvements progressing?
I think there is still a lot of room for higher speed.


Manfred

[asrael22]

You had it working on a previous version?  Was the card in the Amiga or outside the amiga when you flashed 1.8.3.

Yes, the last version that was on it was 1.7.1 I believe.

I flashed it while still in the Amiga using the procedure described here.
But I should have updated the drivers first because after flashing it would display only garbage.

Anyway, after powering on the Amiga (4000D), I wait 2-5 secs and make a soft-reset, then I get a picture.
Seems like some timing issue to me.


Manfred

[asrael22]

Additionally it seems like the 8 bit screen modes are unstable. They start to flicker and after a while the screen gets black.
Switching back to 16 bit screenmode whcih is used on Workbench it's all good again.

Is there anything I can do to determine what the problem is?
Hmm, all worked pretty well on 1.7.1. So I'll try restoring to 1.7.1 and see if the problem are gone.