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.
Distribution: Slackware, Gentoo's and Funtoo's, Roll your Own (LFS, not doobies)
Posts: 67
Rep:
ati proprietary and xorg problem
i installed the drivers just fine without problems but after running (aticonfig --initial --input=/etc/X11/xorg.conf) and trying to run startx it tries to load but then it spits an error like no screens found. here is my xorg.conf EDITED WITH MY NEW ONE:
Code:
#**********************************************************************
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"
# This loads the DBE extension module.
Load "dbe" # Double buffer extension
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
# This loads the font modules
Load "type1"
# Load "speedo"
Load "freetype"
# Load "xtt"
# This loads the GLX module
Load "glx"
# This loads the DRI module
Load "dri"
EndSection
# **********************************************************************
# Files section. This allows default font and rgb paths to be set
# **********************************************************************
Section "Files"
# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.
RgbPath "/usr/X11R6/lib/X11/rgb"
# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
#
#
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/TTF/"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/CID/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/local/"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/cyrillic/"
# The module search path. The default path is shown here.
# ModulePath "/usr/X11R6/lib/modules"
EndSection
# **********************************************************************
# Server flags section.
# **********************************************************************
# **********************************************************************
# Input devices
# **********************************************************************
# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************
Section "InputDevice"
Identifier "Keyboard1"
Driver "kbd"
# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.
# Option "Protocol" "Xqueue"
Option "AutoRepeat" "500 30"
Option "XkbRules" "xorg"
Option "XkbModel" "pc104"
Option "XkbLayout" "us"
EndSection
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
Section "InputDevice"
# Identifier and driver
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "Auto" # Auto detect
Option "Device" "/dev/mouse"
Option "ZAxisMapping" "4 5 6 7"
# Emulate3Buttons is an option for 2-button mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"
# ChordMiddle is an option for some 3-button Logitech mice
# Option "ChordMiddle"
EndSection
# **********************************************************************
# Monitor section
# **********************************************************************
# Any number of monitor sections may be present
Section "Monitor"
Identifier "Gateway EV910"
# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
HorizSync 31-95
# HorizSync 30-64 # multisync
# HorizSync 31.5, 35.2 # multiple fixed sync frequencies
# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies
# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
VertRefresh 50-160
EndSection
# **********************************************************************
# Graphics device section
# **********************************************************************
# Any number of graphics device sections may be present
# Standard VGA Device:
Section "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"
# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.
# Chipset "generic"
# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.
Driver "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# intalled.
# BusID "PCI:0:10:0"
# VideoRam 256
# Clocks 25.2 28.3
EndSection
# Device configured by xorgconfig:
Section "Device"
Identifier "radeon"
Driver "fglrx"
#VideoRam 32768
# Insert Clocks lines here if appropriate
EndSection
# **********************************************************************
# Screen sections
# **********************************************************************
# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
Identifier "Screen 1"
Device "radeon"
Monitor "Gateway EV910"
DefaultDepth 24
Subsection "Display"
Depth 8
Modes "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
EndSection
# **********************************************************************
# ServerLayout sections.
# **********************************************************************
# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.
Section "ServerLayout"
# The Identifier line must be present
Identifier "Simple Layout"
# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen. In this example, screen 2 is located to the
# right of screen 1.
Screen "Screen 1"
# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection
Section "DRI"
Mode 0666
EndSection
Seems that aticonfig never does a proper job huh?
Basically, it looks like aticonfig just ADDED its own junk to the file, without removing the other stuff that might have been in there. You only have ONE card, ONE monitor, right?
Remove or comment out the duplicate SCREEN, DEVICE and MONITOR sections (probably be best to remove the ones with the 'ati-config[0]' stuff, as it is probably what got added..
Now, make sure the correct driver you want, is in the DRIVER line in the Device section. Make sure the right DEVICE is named in the Screen Section. Make sure the correct MONITOR is named in the Screen section.
Check the Horiz & Vert rates for the monitor--- make sure they are suitable.
Finally, the file would be a WHOLE LOT easier to work on if for two things:
1 - Delete all the commented out junk, and
2--- when you post a long file like that, surround it with [ code ] tags [ / code ] <-- like that, but without the spaces.
Hope this helps you fix the file; if you still have trouble, re-paste your new file into your original post, and we'll have another look
below is my xorg I just removed all the stuff not relating to the ati device that you should check, this is not a complete working xorg file, so dont remove yours and use mine, but these are items that need to be addressed in the xorg conf file without all the chatter and clutter in a stock xorg file
Section "Monitor"
Identifier "ati-monitor"
# big fat waring be sure to check your
# monitor settings these could hurt you
HorizSync 50.0 - 90.0
VertRefresh 50.0 - 160.0
Option "DPMS" "true"
EndSection
The biggest thing is that you MUST keep the Identifier names consistent throughout, to which I can see in your xorg you posted are not the same thru and thru, hence the no screen's issue.
Distribution: Slackware, Gentoo's and Funtoo's, Roll your Own (LFS, not doobies)
Posts: 67
Original Poster
Rep:
i edited my above post and in this one i will include the exact error code i get.
Code:
[R200 Setup] X version mismatch - detected x.org 7.0.0 required 6.8.0
(EE) failed to load module "fglrx"(module requirement mismatch, 0)
(EE) no drivers available
No screens found
Well,, there are two issues here, likely one as a result of the other:
First, the driver is failing to load.
Second, this makes it impossible to find a screen.
That's how I see it anyhow. Can you look into teh fact that the error claims that it is a version mismatch? I mean, can you specifically locate/download & install the fglrx which matches the 7.0.0 X server?
7.0.0 is the newer one, which I personally am not using yet, so I don't know much more about it, but I would think that there is a newer compatible driver set to work with it.
After that is fixed, we can see if/anything is still affecting the Screen being not found.
How did you install the drivers? Was it with the .RUN package or did you use the rpm and convert it to tgz?
what kernel are you using?
i found out (and very recently, cuz as you can see i have a post about a similar issue) that when i was on the 2.4 kernel i had issues trying to install the drivers. i reinstalled with the 2.6 kernel (im using slack11 and all included kernels), loaded the modules and source. after that i installed the ati drivers and everything worked just great. i had to modify the xorg.conf obviously, but i got it working.
*sidenote
the one thing i noticed different about the 2.4 and the 2.6 kernel is that a module it loaded was amd64_agp which gets used by agpgart. im wondering if this had a significant role in why it wasn't working for me on 2.4... im not sure but i think before i get too comfortable im going to find out for sure.
Distribution: Slackware, Gentoo's and Funtoo's, Roll your Own (LFS, not doobies)
Posts: 67
Original Poster
Rep:
on atis website they only have drivers for x.org 6.8 so i dont know of any new ones i downloaded the rpm and converted it because im on dialup and cant download 50 megabytes worth of stuff at one time... takes forever. i am also using kernel 2.4.33 the stock slack 11 one, i think amd64 might be for a 64 bit platform which i do not have.
Humm, I sympathize about the dialup speed; I am in the same boat @ 28.8k.
However, you may have to download something. As you can see, the version mismatch won't go away, until either the fglrx gets updated, or X gets reverted to 6.8. Maybe there's a compromize at X 6.9 ??
Anything AMD64 won't work on a 32 bit machine either.
Finally, I can't comment on the kernel versions, but there is **very probably** a suitable combination of X and fglrx for your system and kernel But unfortunately, you likely have to download something..
I'd suggest using Kget, as it will download in pieces, and will resume after logouts/reboots etc..
Install a 2.6 series kernel and run the ati installer again. Then just run aticonfig --initial without the input file crap. Edit xorg.conf as needed and it will work.
Heres the weird thing i found about the RPM package. it says xorg 6.8 but the RUN package says 6.8 to 7.1 (i think that far) anyways, when i installed the RPM xorg only package i had an error that said i didn't have the right version of xorg. when i switched to the RUN package i didn't have that problem.
maybe you should try leaving the download open all night remember to save it to a usbdrive too or something so you don't have to do it again. hahaha.
try switching to 2.6 too. it comes with the slackware CD's if thats what you have. its the huge26.s kernel. once you've installed it besure to put in the 3rd CD (i think it's that one) and install the module and source. after that i just followed these steps from this sticky
Code:
From /usr/src
ln -s linux-2.6.X linux
X being the rest of the folder name of the kernel... .17 if you use what comes with the cd.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
. i am also using kernel 2.4.33 the stock slack 11 one, i think amd64 might be for a 64 bit platform which i do not have.
