Correct configuration of nvidia kernel modules with new Xorg
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Correct configuration of nvidia kernel modules with new Xorg
I am setting up a computer for a church that is a public computer: anyone can log into it using a limited account available on the machine.
My problem is that I've never screwed around with nvidia, at least not in a few years. I want to use the default kernel drivers with Xorg but when I am in init level 4, one user can log in, but when you log out, Xorg locks hard and never goes back to the login screen. This is using the VESA xorg.conf that is provided with Slackware 13.0-rc2.
I can go from Xorg to the virtual terminal (i.e. control+alt+F6/F7) without problems.
I have tried going without an xorg.conf but then the monitor complains that it cannot display this mode. It's an old Dell LCD capable of a maximum of 1024x768.
I have tried changing "vesa" to "nv" in the copy of the vesa config included with Slackware 13.0-rc2 and that results in the "can't display that mode" on the monitor.
Basically, with vesa I can't log out and log back in (not without manually going to a virtual terminal and killing Xorg because it locks hard, and the logs don't seem to give me much useful information). Without using the vesa config as-is, xorgsetup and X -configure both cannot properly configure a working config, as I get the "can't display".
I don't want to compile the nvidia driver for this machine because I will want to keep it "frozen in time", i.e. be able to recompile kernel without problems.
The kernel is 2.6.30.5 (a copy of the generic-smp config included in 13.0-rc2, just with ext4 <*>).
I don't have "xorgconfig" so I can't really configure this thing manually....
Hmm. OK, so the 'nv' driver (so far) doesn't lock the server hard, but also won't display an acceptable mode. And xorgsetup doesn't give a working mode either.
Maybe you ought to run xorgsetup, then show us the resulting xorg.conf file.
If it needs editing, and it's beyond your ability/patience/time or whatever, perhaps we can fix the file up so it'll always default to 1024x768 (which should work, right?)
If you are booting to run level 4 and using kdm, then you can try adding TerminateServer=true in kdmrc so that the Xserver is restarted after logout.
Didn't work, but thanks.
Quote:
Originally Posted by GrapefruiTgirl
Hmm. OK, so the 'nv' driver (so far) doesn't lock the server hard, but also won't display an acceptable mode. And xorgsetup doesn't give a working mode either.
Maybe you ought to run xorgsetup, then show us the resulting xorg.conf file.
If it needs editing, and it's beyond your ability/patience/time or whatever, perhaps we can fix the file up so it'll always default to 1024x768 (which should work, right?)
You shouldn't have to reconfigure the kernel.
I'm assuming you're using the kernel module and driver from slackbuilds.
All you should have had to do was install the correct module first and then the driver.
I'm not using that driver or module either as I had trouble with it also and am using the proprietary driver.
I'd recommend running 'nvidia-switch --cleanup, rm the nvidia driver and download/install the proprietary one from nvidia.
Download the driver to your desktop.
Change your inittab to boot to run level three.
Browse to the desktop and do ls so you can see the name of the driver.
Install it with sh and allowit to build your kernel module for you as well as set up your xorg.conf.
It should give you the 1024x768 res as well as the nvidia x server settings tool in your menu.
If you go the proprietary route you may consider editing your xorg.conf with the options listed below:
Perhaps your old monitor is being asked to use frequencies that are too high for it to handle. You do not quote a model number, but if you can get the model number (perhaps from the on screen display) then google for the monitor's horizontal and vertical frequencies. Then in the Monitor section of your xorg.conf add lines for HorizSync and VertRefresh. This should restrict the graphics driver to using modes that your monitor supports.
As windtalker10 pointed out, add a Modes line to the Screen section in subsection Display under Depth 24.
I've put an updated file there. I'm not exactly sure which of the highlighted "modes" lines will work for you, because I use "MetaModes" on my machine, and I haven't used a "Modes" line in a long time. However, Windalker's "Modes" line(s) in the Display Subsection look suitable and proper.
There're comments to help you, in the file.
Good luck! And if it won't start X, no matter what you do, check the xorg.0.log file for the reason.
Sasha
Last edited by GrapefruiTgirl; 08-26-2009 at 09:15 PM.
Perhaps your old monitor is being asked to use frequencies that are too high for it to handle. You do not quote a model number, but if you can get the model number (perhaps from the on screen display) then google for the monitor's horizontal and vertical frequencies. Then in the Monitor section of your xorg.conf add lines for HorizSync and VertRefresh. This should restrict the graphics driver to using modes that your monitor supports.
I have to do this with my older HP M70 monitor. I bought the monitor in 1999, and it's still going strong, but I also have to specify its horizontal and vertical frequencies in my xorg.conf file. Actually, xorgconfig prompts me for those values.
I'm a big believer in the xorgconfig utility. It'll be interesting to see if I need to use it with Slackware 13.
No thanks, I'd rather use what comes with Slackware.
Quote:
Originally Posted by allend
Perhaps your old monitor is being asked to use frequencies that are too high for it to handle. You do not quote a model number, but if you can get the model number (perhaps from the on screen display) then google for the monitor's horizontal and vertical frequencies. Then in the Monitor section of your xorg.conf add lines for HorizSync and VertRefresh. This should restrict the graphics driver to using modes that your monitor supports.
As windtalker10 pointed out, add a Modes line to the Screen section in subsection Display under Depth 24.
I tried that and it didn't help.
Quote:
Originally Posted by GrapeFruitGirl
http://pastebin.com/m1883af7d
I've put an updated file there. I'm not exactly sure which of the highlighted "modes" lines will work for you, because I use "MetaModes" on my machine, and I haven't used a "Modes" line in a long time. However, Windalker's "Modes" line(s) in the Display Subsection look suitable and proper.
There're comments to help you, in the file.
Good luck! And if it won't start X, no matter what you do, check the xorg.0.log file for the reason.
Sasha
Tried that. My pastebin got "lost" but I'll try it again very soon.
I am starting to feel that I am punching in the dark.
What is the actual graphics adapter?
What is the actual monitor model?
Are there any clues in the output of xorg.0.log?
What happens if you use the standard 2.6.29.6 kernel?
Does the proprietary nVidia driver make a difference?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.