From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-discuss/20120119/006297.html | 79 +++++++++++++++++++++++++++++ 1 file changed, 79 insertions(+) create mode 100644 zarb-ml/mageia-discuss/20120119/006297.html (limited to 'zarb-ml/mageia-discuss/20120119/006297.html') diff --git a/zarb-ml/mageia-discuss/20120119/006297.html b/zarb-ml/mageia-discuss/20120119/006297.html new file mode 100644 index 000000000..19d985811 --- /dev/null +++ b/zarb-ml/mageia-discuss/20120119/006297.html @@ -0,0 +1,79 @@ + + + + [Mageia-discuss] Glitch with nvidia FX 5500 card driver + + + + + + + + + +

[Mageia-discuss] Glitch with nvidia FX 5500 card driver

+ Maarten Vanraes + alien at rmail.be +
+ Thu Jan 19 21:28:24 CET 2012 +

+
+ +
Op donderdag 19 januari 2012 15:17:39 schreef TJ:
+> On 01/19/2012 06:37 AM, AL13N wrote:
+> > [...]
+> > this "new driver" what is it? is it, is it different from the one used
+> > before?
+> 
+> Sorry, I guess I wasn't as clear as I thought.
+> 
+> The FX cards use a different nvidia driver than the 6000 series. When I
+> first booted with the 6200, the "new" card, Mageia was still using the
+> FX driver, the "old" driver. Using MCC, I had Mageia install the driver
+> for the 6000 series, the "new" driver, but it didn't take effect until I
+> did a reboot. So, when I began the restart process, Mageia was still
+> using the FX driver("old") with the card, and the 6200 card acted as the
+> FX card had. After the reboot Mageia was using the 6000 series
+> driver("new"), and all worked as it should.
+> 
+> Hope that clears things up. Again, I'm sorry if I was confusing.
+> 
+> TJ
+
+oic, so you think it's something that's fixed in nvidia-current, but nvidia-
+legacy still has this problem?
+
+ + + +
+

+ +
+More information about the Mageia-discuss +mailing list
+ -- cgit v1.2.1