I also have the 6150 SE in my tower and saw that there's a new driver available. So far the 304.108 works fine with 14.1. I'll download the newer driver and install that later.

Just installed the latest NVidia 304.116 and it works fine

Same here. The new driver works just fine on my system as well.

Well I can Honestly say with the 3.12 testing kernel none of the patches work for me none of the patched nvidia stuff those are the official nvidia patches for several different drivers.
seems Nvidia is more in to android. and may be time to look for a AMD card.

Makes you wonder why all the consoles will be getting AMD.

Newest NVidia driver is ready for 3.12 without any need to patch: http://rglinuxtech.com/?p=924

Well, I think this thread is about legacy GPUs using the 304.xx drivers.

For more recent NVidia GPUs the latest working drivers are 319.49 and 325.15.

the 304 builds fine in 14.0 and 13.37 and there stock kernel. 14.0 to 14.1 we have seen some very big changes in the xorg and mesa programs
I am sure things will come about. the 304 driver works well on my GT 640 2gb ram in the previous environments.
right now the 319.49 builds with the 14.1 and if I go to the 319.60 it builds but breaks all my video capture and breaks all my video software using libva.
and ffmpeg. there is other drivers that do build and work but still breaks my software.
This is not good or bad just data.
I patched the 304 and the build failed I am still looking into it. I am only using the 3.12 testing config until Pat sets out another kernel to test
then I will try it.
One kernel at a time.

Just updated one box to 304.119 - installed unpatched and works just like 304.116 as far as I can tell on first looks.

I have been experiencing a small problem since I replaced my monitor with a new "widescreen" thrift-store treasure, 1368x768. About every third or fourth time I start X it comes up in the wrong resolution, once in a while offset on the screen or the monitor reports "no signal".

I am using Fluxbox, I include the nvidia-settings.rc in the startup script and I have the correct modeline in xorg.conf. I was hoping 304.119 might fix it, but alas... (might not be an Nvidia problem).

For now I wrote simple xrandr script in my home directory which I can invoke even when blinded by no signal, and it seems to reset fine. I can also exit Fluxbox or Ctl-Alt-BS and kill X. More annoying than anything else.

Are sure that it is correct? Why don't you let the driver use the modeline from the EDID?

1 members found this post helpful.

I added the modeline while trying to fix this behavior, which did not change anything but I left it there. Before I added it I would guess the driver was using the EDID values (although I am far from an expert in how that all works).

I originally had a Dell 1024x768 (?) monitor. It never came up with the wrong resolution, but once in a while it would fail when X started. I tinkered with it a few times but never got a handle on it and mostly ignored it and restarted X when it happened. Then I got an Acer 1368x768 which I really like (easy on my eyes and extra width that still fits on my crowded desk). It has the more frequent problem of starting at incorrect resolution, and sometimes fails with "no signal" as did the Dell, so I expect they are the same problem.

Today I saw there was a new Nvidia driver for it so I installed it thinking it "might" be an Nvidia problem, but no change.

Additional info: It is a GeForce 6150SE video controller, the problem occurs with or without the nvidia-settings loaded from the Fluxbox startup script, and with assorted startx options that I have tried at various times. In short - nothing I have done has seemed to make any difference.

All of that said, I am not in very active pursuit of a solution at this point, but as you were kind enough to reply - thanks! Any guidance or suggestions will be appreciated.

If the built-in EDID modeline doesn't work, there is a good chance, that just your display is broken. You should remove the modeline, because it overrides the defaults which work best with your display, especially if the modeline doesn't help anything.

Which display connector do you use? Did you try a different one?

I'll comment out the modeline - it did not change anything.

I am using the VGA connector and yes, I have tried a different cable.

At times over the past few months I have tried to troubleshoot it and read much and tried several things along the way. It might just be a hardware problem, either in the monitor or the computer. It is not "flakey" in any other way, but this particular problem has been like gravity - nothing else seems to interact with it. Hence, my decision to mostly just live with it.

I'm bumping this thread just to ask if someone has successfully installed either the 304.108 or 304.121 Nvidia's driver along with the 3.13 Linux kernel ?

121 should build against kernel 3.13.x and Xserver 1.15... Are you having trouble with it?

I don't know at the moment.

I'm just considering compiling a 3.13 branch kernel because of the enhancements of the snd_usb_audio module of the Linux kernel.