1.0-8174 for Linux x86 released

[bloxyman]

I am running ubuntu breezy using kernel 2.6.12.10-k7.. driver 7676 has worked just fine for me, but the 8174 broke my tvout

I get no error or anything when i open a seperate xserver using tvout, but the tvout is showing a corrupted xserver screen, with no sight of the nvidia logo or the desktop.
Downgrading to 7676 seemed to solve this issue...

The main specs: msi kt333, msi gf4 ti4200, 512meg ram..

[neuschnee]

RenderAccel still crashes Xorg when using Firefox on certain pages (doesn't crash when it's off, and I can make it crash on the same page every time when RenderAccel is on.. I'm guessing it's something font related).

HW cursor bug also still happens once in a while.

So.. this is just another lame update. Stability over features please. I'd much rather have some 2D acceleration than play silly 3D games slightly faster.

[firephoto]

I keep hearing people with renderaccel issues but that's one thing I've never had issues with. Are you guys using composite, because that's far more unstabe.

[Spyke]

Speeds are back up to how they always were before the 8168 driver. 8168 had some bugs which most likely slowed things down.

[snader]

Originally Posted by neuschnee

RenderAccel still crashes Xorg when using Firefox on certain pages (doesn't crash when it's off, and I can make it crash on the same page every time when RenderAccel is on.. I'm guessing it's something font related).

HW cursor bug also still happens once in a while.

So.. this is just another lame update. Stability over features please. I'd much rather have some 2D acceleration than play silly 3D games slightly faster.

Could you mention on which sites it crashes so we can test that as well?

[pzgren]

Originally Posted by snader

Could you mention on which sites it crashes so we can test that as well?

Wow! I must agree. My first X crash since years...with firefox on an stable KDE 3.5 tested (RenderAccel on). I say only: 4 months for next driver?...

@ Bratag

You do realise that nvclock is not written by nvidia? In fact in most cases I believe they caution against overclocking (or at least the card manufacturers do). I know you can OC stuff (my BFG card comes OCed out of the box) but its at your own risk. I cant see nvidia providing something potentially damaging.

I know nvclock and use it, its linked on my homepage since years...WIM

The GF 6800 Go mobile runs here with my big battery always with full speed in 2D mode! Means: 290/590 full speed! No nVidia powermixer support on linux. With powermixer or an option to clock it down, it would/could only be 125/318 in 2D mode. That is a lot of saving for a hw device in a notebook consuming the most energy! I can also ver stable and fine clock to 400/700 and can play cool 56 celsius for hours BF2 under XP, its more stable than most PC nVidia GFX cards I have used and seen...

Marcus

[zander]

If you experience crashes, please try to locate a thread describing your problem and reply with as much information as possible there, else create a new thread (see http://www.nvnews.net/vbulletin/showthread.php?t=46678).

Please note that COMPOSITE is still experimental and that the crashes you're seeing may be caused by bugs in the core X server, see e.g. http://www.nvnews.net/vbulletin/showthread.php?t=61111.

[neuschnee]

It is not a composite problem. I never use composite, because you're right, it's experimental and buggy. But RenderAccel is buggy enough by itself.

chango:~$ tail -3 /etc/X11/xorg.conf
Section "Extensions"
Option "Composite" "Disable"
EndSection

No I cannot link to the site, because it's a private forum. I might try and isolate what part of the page causes the crash though. I don't really have a way of collecting info after the crash, because the way X dies my console is fried and I don't have another computer for dialing in (though that might be because I use a fb console so I could try using a kernel without it).

Again my best guess is that it's a problem with fonts, specifically anti-aliasing. I could try without autohinting just to be sure.

[joaorf]

Originally Posted by oli993

Same situation here! The driver doesn't work on my GeForce4 420 Go 32M.

I have the same problem.
When have you generated the nvidia-bug-report.log if the system freezes when X starts?

[game-master]

Originally Posted by gollo

Ummmmmmm...... it is released for AMD64 (but not for BSD)

What I mean is the AMD64 port of FreeBSD.

[LubosD]

Originally Posted by neuschnee

So.. this is just another lame update. Stability over features please. I'd much rather have some 2D acceleration than play silly 3D games slightly faster.

I have 100% stability with RenderAccel, Composite and OpenGL at once. Only a few glitches with Kopete messenger but it looks more like a Composite bug.

What card do you have?

[BrianzaMan]

Err, now the fonts are rendered correcly by disabling UseEdidDpi and using DisplaySize option. It isn't sufficient to disable UseEdidDpi or setting it to DFP-0 or whatever else. Why the old driver worked without a glitch ?

Bye

Marcello