Graphics corruption

[delshay]

I also have the latest flash,but every now and then I have to reflash it again due to changes.

[Damion]

The motherboard seems to be playing some role here, any chance of getting one of them re-capped?

[Boot_WB]

so, every screen after the first 1024x768/15bit screen has artifacts. its not related to the bvision. its not related to the memory on the ppc. its not related to the motherboard. its not related to software. its not related to any other on-board component. how can it be anything else than the ppc board itself? and if thats the case, which specific component is probably at fault here? Stachu? Delshay? ..is this something that is cured with a new 300mhz 603?

Ah, Franken-Amigas! I chased a 'Ramlib error' problem around like this for months, only to eventually realise that the physical structure of the Power-tower was slightly kinked, which 'bowed' the motherboard slightly when it was tightly screwed in causing the error. Somehow.

Silly questions:
1) You've listed every component except the psu, hard-drive/cable, CD/cable and floppy/cable. Have you tried others?
2) Have you tried it in a different plug socket in the house (silly, I know) just in case something is a bit iffy in the wiring department, or causing severe groundplane intereference.

[rvo_nl]

Yes, I did actually try different HD cables
 
I indeed did not try with a different PSU or Elbox tower, so who knows.. but do you really think that is going to cause artifacts on every second RTG screen opened? :/
 
I did try in my current home and my previous one, with the same results. Again I cannot believe such a thing will cause such a specific glitch in my display.
 
I guess I can do one more test, in a different tower with a different PSU..
 
One thing that keeps bothering me, could it be that - something - in my tower is damaging all my bvisions? For example that little wired PCB you plug in that Bvision 'hole', which comes with the Elbox tower and is used for the LED's? Did it short circuit the video memory of all my bvisions? :| There is 12v on it, after all..
 
I ask this because, I remember having had similar graphical artifacts way back that I solved by getting a new bvision. At that time I got 3 (one broken) of which 2 I am constantly using for testing. (with and without that little circuit board I mentioned)
 
Can someone tell me where the video memory is located on the Bvision? Is it near the hole in the middle?
 
edit: OMG, reading back this actually seems plausible..
 
This is the LED PCB Im talking about: http://eu-shop.elbox.com/cgibin/shop?info=562ELED&sid=7c715f4b
 
This is the Bvision: http://www.amiga-hardware.com/download_photos/bvision_front_big.jpg
 
Note that this is the side where the PCB touches the Bvision. Also note that OFCOURSE I did protect the bvision against shorting by wrapping the PCB in ducttape, but you know, over time I guess the pins of the PCB will go right through it..
 
btw delshay, I see now that you already pointed out a possible short circuit resulting in graphics output looking like this.

[delshay]

You don't have to wrap anything in duct tape, normal installation is fine even with A1200 shieiding ( desktop A1200 only )

Bvision carries 12v but is not used, however 5v is present with-in the cable,but i would expect your problem to be a lot worse if 5v is sent back into the Permedia 2.

It is recommended that all users add the minimum heatsink to permedia 2 even if its not overclocked.

If using indivision care must be taken of cable routing as not to put to much stress on Bvision connector. Same applies when installing Bvision,do not over tighten screws.

As you don't know where the memory is STOP.  Get a expert to look at your system.

[rvo_nl]

Well, its hard to find experts these days..
 
Also I think you misunderstood. Its the floppy power connector in which I have to put this little Elbox circuit boards that powers my LED's, it also provides extra power to the motherboard. This circuit boards is a bit bigger than the hole inside the bvision, so the sides of it press against the bvision circuit board itself. Since there is power being fed over this PCB, perhaps this has damaged the Bvision components near the hole?
 
Here, see this drawing I made:
 


Also I must say the version of this Elbox LED thingie that I have looks a bit different.

[Karlos]

The SGRAM chips are the ones just visible at the bottom of your screenshot. There should be 8 of them in total, 4 on each side of the card.

[rvo_nl]

thanks for clearing that up. although I cant be sure one of the other components is affecting the SGRAM. What about the chips on the backside of the bvision, can they be damaged by touching the motherboard? Not too uncommon in A1200T's I guess..

[rvo_nl]

Hello, it's been a while. But for those that are interested, after much fiddling around I bought a new bvision and the problems are gone. I've added a 80mm fan to my machine that blows cold air on the permedia chip all the time, since many suspected heating issues. And to be honest, Ive ruled everything else out. Im probably a very unlucky person having burned 3 or 4 bvisions in a short time.

Thanks for all your help!

[J-Golden]

UG!  What a way to get it figured out!  Since you now know it was the Bvision, what are you going to do with the "zapped" ones?  Delshay  might be able to fix them for you, maybe even upgrade them.

[delshay]

I hope you are right about the fault,but I find it very strange that you have tryed 3 different Bvision and all show the same fault.

If the fault reappears then you know its not the Bvision.

Check other Bvision(s) on another Blizzard card.

[rvo_nl]

I did in fact, there too the artifacts showed up. Perhaps I didnt make myself clear. My first ever bvision started showing the artifacts. I then bought 2 new ones, that initially worked. only over time, say 6 months, they too started misbehaving. another bvision never worked from the start. Yes, I now have 5.

[AmiDude]

So, let this be a warning to everyone; DON'T BUY A BVISION, IT'S CRAP!!! :rtfm:

[delshay]

The Bvision to the left will not work, its missing some components. Nice to see correct size heatsink on one of the Bvision.

Bvision can perform, it needs the right modification(s) to perform with or without overclocking.

Users with Micron Sgram may have better overclocking with users with Fujitsu Sgram,this type of Sgram is fitted as standard on Bvision. Some users may have another type of Sgram fitted as standard.

There are other factors which also affect how far you can overclock,but overclocking Sgram does not get the best performance out of the Bvision,its the bus speed which gives the best performance which is working here upto 41.83Mhz and shows benchmarks I have never seen before.

Flashrom & Bvision driver may gain more performance.

[rvo_nl]

delshay, you really know your stuff, no doubt. but right now Im just happy with the standard bvision, I will not overclock indeed, one of the bvisions is missing components, you have a good eye for details

actually I think the bvision is an excellent card. sure, its not very fast anymore but its more or less the only way to get rtg to your a1200 without buying a pc card like voodoo. for me, that counts. for many others, it doesnt.

[delshay]

If Bvision was working in the past,then stop working then you have to assume the problem may return as it seems you have done nothing other than just changed Bvision.

The PCB you insert maybe work itself a little loose and comes into contact with Bvision maybe when you move the unit or due to vibration.

If the PCB is very near to Bvision then I recommend a very thin piece of flexible plastic cut to size and glued to the underside of the PCB to cover all solder contact. Glue just the four corners of the PCB not all of the card.

HOT GLUE recommended,but I would get a expert to do this for you.

Before doing all above you need to be sure the PCB is not damaging your Bvision and given that it is now working going back and disturbing the card(s) may trigger of the fault again and may permanently damage the Bvision again.

If the fault returns you are going to think I should have looked into it further.