[TEMP-WORKAROUND] 290 NVIdia/3.2 kernel tests I've done

Question

It's not fixed as it is a kernel issue. Link to article in post #5.
But there is a workaround in the meantime to at least get you back up and running.
I have an up to date Arch x86_64 machine. And an NVidia GTX-560TI. Like others, today's updates broke "X" fatally, when both the new 3.2 kernel came down with the new NVidia driver family (290).
I've done some tests that may help folks smarter than me figure out what is going wrong.
Test:
a)  Removed nvidia, nvidia-utils, and all related NVidia packages. Handled the libgl dep issue.
b)  Killed the xorg.conf file, removed the nvidia module from memory, and installed the xf86-video-vesa package.
A subsequent call to startx had the DE come right up (just in a lower resolution than a native driver @ 1920x1200).
c)  Went to the NVidia site and downloaded the 285.05.09 drivers and installed the same from a true cli (I personally don't use GDM's). Allowed the NVidia drivers to create it's own xorg.conf. Dealt with the libgl issue. I know this is not Arch orthodoxy, but remember I'm trying to restore my main work system to operational status until the nvidia driver/packages/whatever get sorted out..
d)  Used the nvidia-xconfig to create a new xorg.conf, modprobe'd the new nvidia module, then tried startx. (It's how I choose to start my DE's)
Same issue as with the 290.10 driver. The error of "screen found but no valid configuration found..." that's well documented elsewhere in the forums.
While I am a veteran Arch user, and with other distro's have built hundreds of custom kernels (and a few for Arch), that does not make me a dev. In my humble experience, this test limited the variables down to one. Now the only difference was the kernel rev of 3.2.
At issue is:
a)  Is the nvidia module needing to do something different with the way it interacts with the new 3.2 kernel, meaning that NVIdia itself is doing something that the 3.2 kernel doesn't appreciate?
or
b)  Does the kernel need an adjusted .config file before being rebuilt?
I am not smart enough to know the answer.
Right now, I've of course removed all traces of nvidia, installed libgl, and am using the vesa driver so I could at least access my DE of choice and operate (somewhat). I cannot work until the NVidia things gets sorted out as I use video editing software that requires the use if the cuda toolset.
I post this test only as a source of information that hopefully may point the dev(s) in perhaps more directions than just nvidia. In the end, it may be totally NVidia's issue (like the last time)....But when I plug in the old working drivers in, and still cannot get "X" to function.....Then I start thinking about kernel configuration/compatibility issues.
If anyone wants me to do some other tests I haven't thought of...I'm totally game for it, anything to be of help.....Just let me know what you want done and I'll do it and post the results.
Sincerely and respectfully,
Dave
Last edited by dcbdbis (2012-01-19 09:06:33)

Answer 1

dcbdbis wrote:
For Jack450,
I'll be happy to work with you through this....
I need: What flavor of Arch x32 or x64?
How current?
If you are using the lts kernel, then you need to use the nvidia-lts package with it or no love between the kernel and nvidia module.
a)  Ensure you do not have anything but the lts's api's, headers, and kernel installed. If you're missing a piece, I'd recommend installing it. If you've still got 3.2.1 stuff in your system, get rid of it.
b)  Kill your '/etc/X11/xorg.conf' file. (hint : sudo)
c)  Remove your existing nvidia kernel mod from memory
sudo modprobe -r nvidia
d)  pacman in the nvidia-lts stuff.
e)  Modprobe in the new module
sudo modprobe nvidia (check my spelling, I don't know if the lts nvidia modules goes by 'nvidia' or 'nvidia-lts')
f)  From a cli do:
sudo nvidia-xconfig
g) startx, or reboot, whichever you prefer........
h)  And see if that doesn't give you back your GDM/DE.
And no this is not the only way to do things.....There may be easier ways, but being an old retired engineer...I do tend to be a bit retentive.....Others may have different suggestions just as worthy and perhaps easier. All I know is that, if your system was sitting on my desk, this is what I would do for starters.
Dave
PS: if this doesn't do it, as this is a laptop....then I need more info on your hardware. Please do an
lspci -v > HardwareInfo.txt
and PM me with that file, to conserve forum space and I'll then come up with a round two attempt if round one for some wierd reason doesn't solve your problem.
It was first x64 and I switched to x32 to see if it made any difference but it still kills the Xorg so I gave up. I tried LTS, different nvidia drivers plus nvidia-lts drives, intel_iommu=off didn't work. So I'm guessing I'm just out of luck and have to wait for an update.