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.
The xorg.conf-vesa is just an example file. It does not have any effect on your setup.
You can check what the X autodetection routines are setting by executing, as root, "X -configure". If those settings are OK, then you have no need for an xorg.conf at all.
Click here to see the post LQ members have rated as the most helpful post in this thread.
Distribution: Debian, edition depends on what i run it, wheezy on main box.
Posts: 91
Rep:
instead messing with xrandir and similar "detects hardware well malfunctions", use /etc/X11/xorg.conf file for setting modelines for your display under MONITOR section see example>
NB, those modelines are valid for my monitor, not yours.
that does not matter, what driver you use, vesa, nv, nouveau or proprietary, they are all capable using modeline-s.
but only with one driver, you will have PERFOMANCE with your GF3 card, is NVIDIA proprietary. and you will need legacy 96xx drivers and KMS parts for it, and they are not compatible with new xorg updates, so you have to stick with em, unless you do not want to reconfigure nvidia support again after xorg update.
in very short, nouveau suck at glx and flash perfomance. vesa and nv modules do not have glx support at all.
valid modelines can be generated by modeline configurator, available online from web. with older CRT-s use with extreme caution, because you can really broke your monitor if exceeding valid refresh rates.
Failed to load "xgi" invalid module using conf file /root/xorg.conf.new
No Dricreatepcibusid symbol
Number of created screens does not match number of detected devices.
Configuration failed.
Is this why my resolution keeps changing everytime I restart the computer?
If I install the Nvidia drivers will that stop the resolution from changing when i boot?
Those messages suggest that X is failing to detect your graphics setup.
My strong suggestion is to try the nVidia driver.
If you want to persist with the nouveau driver, please post the output of 'lspci' and the contents of /var/log/Xorg.0.log after starting X without a /etc/X11/xorg.conf file.
The 'lspci' output gives the PCI bus address of your graphics.
Quote:
The Xorg.0.log has a whole bunch of nouveau lines in it and is too big to post here.
It may be large, but it will have the information needed to suggest xorg.conf settings, such as details of monitor mode timings being detected and display names.
I tried to post it and its too big, I get a message to shorten it to about half of the size it is.
If I install the Nvidia drivers will that overide the nouveau driver?
And will that stop the massivea amount of lines that scroll by when i boot up that say nouveau ? LOL
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.