Quote:
Originally Posted by david08
reconfigured xorg.conf bilions times, but doesn't work.If you could help me with bash commands about replacing files and installing driver, I'd be glad because I didn't used so much terminal because.I've used a lot deb packages.
Thanks in advance.
|
There are numerous ways to replace files
Remove - "rm -f /path/to/file"
Move - "mv /source/file /destination/file"
or "cat /source/file > /destination/file"
Copy (over) "cp /source/file /destination/file"
Note: if source and destination file have same name, source will overwrite destination
Also and perhaps of more value is the Text Editor. In Slackware the default text editor is "vi" or "vim". This is an extremely powerful tool but it is made for programming and is NOT a word processor. There are hundreds of commands and options associated with vim. To get you started here are the most basic ones, say for editing "/etc/X11/xorg.conf". First to get into the file (or create it if it doesn't yet exist) type
"vim /etc/X11/xorg.conf"
It defaults to Read Mode and you can scroll down and across and at the bottom it will report the line and column. With vim (which stands for vi improved) you can delete characters with the Delete key but to add characters or lines you must enter Insert mode by striking the "I" key. If you just want to read and make no changes first strike the "Esc" key and you'll get a beep and a blinking cursor at the bottom. Here you type "Q" to Quit and then Carriage Return AKA the "Enter" key. If you have made changes you want to keep you hit "Esc" then "W" (Write) as well as "Q" (Quit) and then "Enter".
Some people consider it an annoyance but the Console login default of Slack is a massively cool feature, especially for the kinds of problem you are experiencing. When X fails to load it keeps a log of what happened in "/var/log/Xorg.0.log" and you can read it anytime with "vim /var/log/Xorg.0.log". Errors are marked with [E] and Warnings with [W]. While we're on this subject an important aside - to avoid typing errors and speed up command line entries all you need to type is enough letters so the system can rule out all others and hit the "Tab" key and the line will autocomplete. For example if you type "vim /v" and hit the "Tab" key it will add the "ar" since there is no other directory beginning with "v". When you get to Xorg.0.log just the "X" is likely enough since it is the only file in that directory beginning with capital "X". This is extremely usefull.
To sum up what we started in the previous paragraph, check the Xorg log for error messages so you know what to fix. It is far more common that X will have problems with monitors than video cards because so many have EDIDs that suck. If you see that this is the problem you may have to research your monitor's specs and declare them in "/etc/X11/xorg.conf". This monitor upon which I am writing requires "Option 'UseEDIDdpi' 'False'" or the fonts are ginormous.
Installing the proprietary nVidia driver
You need to have the kernel source matching your booting kernel version exactly unpacked in "/usr/src/" where it will create a new directory "/usr/src/linux-version". This needs to be configured and made as well as modules made and installed. I cannot remember if installing the kernel-source package and kernel-modules package does all this for you. I always build my own so I'll have to get back to you on that or hope someone else is more familiar with the package aspect.
Download the nVidia driver for your card and system architecture and copy it to the "/root" directory and make sure it is tagged "executable". Upon booting and logging in as root you will be in that directory. Verify the file is present with the "ls" command and then type "sh ./NVI" and hot the Tab key and then "Enter". Follow the prompts and it will build the "nvidia" kernel module, search out any conflicting files, and offer to alter your "xorg.conf" for you and that has always worked fine for me.
To get to X I prefer running "kdm" as opposed to "startx" but that's possibly more habit than anything else by now but I also don't like "xdm" or "gdm" and prefer declaring what I want... besides it's 3 less letters.
VESA or the "nv" driver should work so before getting too deep, look at Xorg.0.log. It will narrow the field faster.
