E-VGA GeForce 6200 LE non-compatible?

Bug #132232 reported by nl2br
2
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Invalid
Undecided
Brian Murray

Bug Description

First of all, sorry for my english.

One month ago, i bought a E-VGA Geforce 6200 A-LE, and i installed the latest driver of nvidia's website.
This worked fine for me, but while i was using my Ubuntu, Beryl running, (more details down), my screen freezes, and when i restart my PC, my screen became unlegible, then my xorg crashes.

I tried with ALL of the official drivers from nvidia and all of them returned the same problem.

My Xorg log says that my video card chipset is not recognized, or something like that.

This is strange, cause i've installed many nvidia cards, and i cant install this one.

I post here my question, this is my last resource.

System Specs:
Motherboard asrock k8upgrade vm-800
system RAM: 2x512 dimm ddr400
processor: AMD Sempron 2600+.
video card: E-VGA GeForce 6200 LE

S.O: Ubuntu Feisty Fawn (i386)

i've tried with the Gusty Tribe 3 and i get the same error.

Thanks for all, nl2br.

//Edit: note that it is not the same chipset of the normal GEFORCE's, this is one made by E-VGA, and i think this card is a low-profile one.

nl2br (mdibot)
description: updated
Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

Thank you for your bug report.

nl2br:
I think your best bet is to try and report the issue to NVIDIA via http://www.nvnews.net/vbulletin/forumdisplay.php?f=14 given that you have tried the official drivers and had the same problem too. It could be some subtle issue between your motherboard and your graphics card...

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

nl2br:
Which motherboard chipset are you using?

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

nl2br:
Better yet post the output of
lspci
...

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

Setting to incomplete pending reply from nl2br...

Revision history for this message
Brian Murray (brian-murray) wrote :

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and feel free to submit bug reports in the future.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.