The new driver -- 1.8776 -- fixes a security hole in the drivers which has been around since 2004 and is now available for download from the NVidia site. Cheers. -- This morning my administration released the budget numbers for fiscal 2006. These budget numbers are not just estimates; these are the actual results for the fiscal year that ended February the 30th. George W. Bush 11 Oct 2006
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2006-10-22 at 01:59 +1000, Basil Chupin wrote:
The new driver -- 1.8776 -- fixes a security hole in the drivers which has been around since 2004 and is now available for download from the NVidia site.
That's the one I have been using for a day and a half. I have experienced several X locks and one full lock needing a hard rebot. Quite unstable. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFOrePtTMYHG2NR9URAlQaAJkBk1BgBTdf4WOkwC70BsjjHc/RTgCfdAuh novQargj6jyhTbdVVx0ZOnA= =ShOL -----END PGP SIGNATURE-----
Carlos E. R. wrote:
The Sunday 2006-10-22 at 01:59 +1000, Basil Chupin wrote:
The new driver -- 1.8776 -- fixes a security hole in the drivers which has been around since 2004 and is now available for download from the NVidia site.
That's the one I have been using for a day and a half. I have experienced several X locks and one full lock needing a hard rebot. Quite unstable.
Hmmm, at this end no problems (?so far). We are talking here about the final release of the new driver (1.0.8776) and not the beta version (1.0.9625) in which the security hole was first plugged? Cheers. -- This morning my administration released the budget numbers for fiscal 2006. These budget numbers are not just estimates; these are the actual results for the fiscal year that ended February the 30th. George W. Bush 11 Oct 2006
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2006-10-22 at 11:29 +1000, Basil Chupin wrote:
That's the one I have been using for a day and a half. I have experienced several X locks and one full lock needing a hard rebot. Quite unstable.
Hmmm, at this end no problems (?so far).
Look at my thread "Slow 3D with NVidia", I posted logs there.
We are talking here about the final release of the new driver (1.0.8776) and not the beta version (1.0.9625) in which the security hole was first plugged?
Yes, the final. I just chanced to be looking for a driver at the time it was released. Tell me, the beta 1.0.9625 then is more or less the same as the stable 1.0.8776 at this moment? Because I was thinking of trying it. I can live with the driver being slow in 3D for me, but I can't stand the machine locking on me, I prefer to keep using the open "nv" driver instead :-( - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFO0uDtTMYHG2NR9URArj3AJsHTZZ/T5JcejKxN2WmBg0xyyPjGQCfcLnZ P9r+FqJXRCNL7MuDjLXSs5I= =dzOq -----END PGP SIGNATURE-----
Carlos E. R. wrote:
The Sunday 2006-10-22 at 11:29 +1000, Basil Chupin wrote:
That's the one I have been using for a day and a half. I have experienced several X locks and one full lock needing a hard rebot. Quite unstable. Hmmm, at this end no problems (?so far).
Look at my thread "Slow 3D with NVidia", I posted logs there.
I saw that but only read it superficially. (See below.)
We are talking here about the final release of the new driver (1.0.8776) and not the beta version (1.0.9625) in which the security hole was first plugged?
Yes, the final. I just chanced to be looking for a driver at the time it was released.
Tell me, the beta 1.0.9625 then is more or less the same as the stable 1.0.8776 at this moment? Because I was thinking of trying it. I can live with the driver being slow in 3D for me, but I can't stand the machine locking on me, I prefer to keep using the open "nv" driver instead :-(
Even though I merely glanced over your original post, one thing which now comes to mind is that I believe you mentioned there that you are using an MX400 card and the results you got were for that card? Am I correct? If so then you had better read the blurb on the nVidia site about what is supported by the latest drivers. I am pretty sure that the MX 400 is not supported and that one has to go back to a much earlier driver for the MX 400 card. Some months ago someone had a question about the MX 400/(?)440 and I pointed this out to him at the time. (BTW, I am using a 6600 card and glxgears is showing ~3891 fps.) Cheers. -- This morning my administration released the budget numbers for fiscal 2006. These budget numbers are not just estimates; these are the actual results for the fiscal year that ended February the 30th. George W. Bush 11 Oct 2006
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2006-10-23 at 17:18 +1000, Basil Chupin wrote:
Even though I merely glanced over your original post, one thing which now comes to mind is that I believe you mentioned there that you are using an MX400 card and the results you got were for that card? Am I correct?
Right.
If so then you had better read the blurb on the nVidia site about what is supported by the latest drivers. I am pretty sure that the MX 400 is not supported and that one has to go back to a much earlier driver for the MX 400 card.
It is supported, it is listed here: http://www.nvidia.com/object/IO_18897.html: Back Supported Products List GeForce2 Go 0x0112 GeForce2 Integrated GPU 0x01A0 GeForce2 MX 100/200 0x0111 ===> GeForce2 MX/MX 400 0x0110 GeForce3 0x0200 The log says it detects it as: (II) NVIDIA(0): NVIDIA GPU GeForce2 MX/MX 400 at PCI:1:0:0
Some months ago someone had a question about the MX 400/(?)440 and I pointed this out to him at the time.
Yes, I read that mail the other day, I searched the list. Anyhow, I did try the "legacy driver", x86-1.0-7184 (published las august), and it is as slow, with the added problem that text mode doesn't work after starting graphics: I only see strange colours.
(BTW, I am using a 6600 card and glxgears is showing ~3891 fps.)
And the main cpu usage? Mine goes to 100%, and that is what I don't consider normal. I can't be certain, of course, but I think I got more two years back than now with the same hardware. I'll have to go back and try in SuSE 9.3 or earlier. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFO4KJtTMYHG2NR9URAuH8AKCDqpY7XW+7rg3i2l5xXTZHPLyqKACfcbEP YAaj4r9RKZTmqtxKRp9GImM= =Bx/q -----END PGP SIGNATURE-----
Hi! I have Nvidia Gforce4 MX 420 with the driver 1.0-8774. When I run glxgears I can see that cpu usage is 100%. If I then start for example the game Neverball everything runs fine. I also can start up a couple of more programs everything still running fine. This couldn´t be done if glxgears was realy using 100 % of the cpu ??? Or does it grab as much as it can get and let loose when asked ? I have never had any problems. On Sun, 2006-10-22 at 16:39 +0200, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Monday 2006-10-23 at 17:18 +1000, Basil Chupin wrote:
Even though I merely glanced over your original post, one thing which now comes to mind is that I believe you mentioned there that you are using an MX400 card and the results you got were for that card? Am I correct?
Right.
If so then you had better read the blurb on the nVidia site about what is supported by the latest drivers. I am pretty sure that the MX 400 is not supported and that one has to go back to a much earlier driver for the MX 400 card.
It is supported, it is listed here:
http://www.nvidia.com/object/IO_18897.html:
Back Supported Products List GeForce2 Go 0x0112 GeForce2 Integrated GPU 0x01A0 GeForce2 MX 100/200 0x0111 ===> GeForce2 MX/MX 400 0x0110 GeForce3 0x0200
The log says it detects it as:
(II) NVIDIA(0): NVIDIA GPU GeForce2 MX/MX 400 at PCI:1:0:0
Some months ago someone had a question about the MX 400/(?)440 and I pointed this out to him at the time.
Yes, I read that mail the other day, I searched the list. Anyhow, I did try the "legacy driver", x86-1.0-7184 (published las august), and it is as slow, with the added problem that text mode doesn't work after starting graphics: I only see strange colours.
(BTW, I am using a 6600 card and glxgears is showing ~3891 fps.)
And the main cpu usage? Mine goes to 100%, and that is what I don't consider normal. I can't be certain, of course, but I think I got more two years back than now with the same hardware.
I'll have to go back and try in SuSE 9.3 or earlier.
- -- Cheers, Carlos E. R.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76
iD8DBQFFO4KJtTMYHG2NR9URAuH8AKCDqpY7XW+7rg3i2l5xXTZHPLyqKACfcbEP YAaj4r9RKZTmqtxKRp9GImM= =Bx/q -----END PGP SIGNATURE-----
/Peo Registered Linux user #432116 http://counter.li.org/ http://www.whylinuxisbetter.net/
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2006-10-22 at 20:46 +0200, Peo Nilsson wrote:
I have Nvidia Gforce4 MX 420 with the driver 1.0-8774. When I run glxgears I can see that cpu usage is 100%. If I then start for example the game Neverball everything runs fine. I also can start up a couple of more programs everything still running fine.
3D games like the penguin downhill jerks now and then in mine.
This couldn´t be done if glxgears was realy using 100 % of the cpu ??? Or does it grab as much as it can get and let loose when asked ?
It could be. Some other thing... Your email is big, it has 14 KiB. Besides the normal text part, you are also sending an html copy and a graphic logo. Plus the full previous email. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFO/dvtTMYHG2NR9URAi7zAKCGhV2SDIvYYgZ5nqe8+nDcMo5dmACfcGNk hY9jdbyiaMrQiQjlubCkdPI= =CpEr -----END PGP SIGNATURE-----
On Oct 22, 06 01:59:55 +1000, Basil Chupin wrote:
The new driver -- 1.8776 -- fixes a security hole in the drivers which has been around since 2004 and is now available for download from the NVidia site.
Alternatively you can just add Option "RenderAccel" "off" to the driver section in /etc/X11/xorg.conf. You typically don't loose much speed by that. Matthias -- Matthias Hopf <mhopf@suse.de> __ __ __ Maxfeldstr. 5 / 90409 Nuernberg (_ | | (_ |__ mat@mshopf.de Phone +49-911-74053-715 __) |_| __) |__ labs www.mshopf.de
participants (4)
-
Basil Chupin -
Carlos E. R. -
Matthias Hopf -
Peo Nilsson