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.
Ok, I know that there are already threads about this, and I have tried following them but I am not getting hardware acceleration with my card. My card is an ATI Radeon 7500, and so ATI does not even provide Linux drivers for it, only windows drivers, and so under xorg I am using the generic Radeon driver. I would like to enable DRI and stuff like that to get things to work a little more smoothly, hopefully with zsnes, since I just compiled and tried to run it, and it runs so very slowly under Linux, but not under windows, for obvious reasons. I am not even sure what other kind of info I should provide, and I don't even know where to start, but any help is greatly appreciated.
Ok, I uncommented
section dri
mode 660
end section
and I couldn't even get into KDE.. This is the output of the Xorg.0.log
Code:
_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/slacker:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6
Release Date: 18 December 2003
X Protocol Version 11, Revision 0, Release 6.7
Build Operating System: Linux 2.4.26 i686 [ELF]
Current Operating System: Linux slacker 2.4.26 #6 Mon Jun 14 19:07:27 PDT 2004 i586
Build Date: 05 June 2004
Before reporting problems, check http://wiki.X.Org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sun May 8 00:08:57 2005
(==) Using config file: "/etc/X11/xorg.conf"
Parse error on line 464 of section ServerLayout in file /etc/X11/xorg.conf
"section" is not a valid keyword in this section.
(EE) Problem parsing the config file
(EE) Error parsing the config file
Fatal server error:
no screens found
Please consult the The X.Org Foundation support
at http://wiki.X.Org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.
this is my screen section
Code:
# **********************************************************************
# 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 "ATI All-in-Wonder"
Monitor "GatewayVX700"
DefaultDepth 24
Subsection "Display"
Depth 8
Modes "1024x768"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1024x768"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1024x768"
ViewPort 0 0
EndSubsection
EndSection
Graphics device section
Code:
# **********************************************************************
# 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 xf86config:
Section "Device"
Identifier "ATI All-in-Wonder"
Driver "ati"
#VideoRam 65536
# Insert Clocks lines here if appropriate
EndSection
Still no luck! I went back and tried the radeonGeneric instead of the ATI all in wonder... this is what graphics and screens sections looks like now..
Code:
# **********************************************************************
# 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 xf86config:
Section "Device"
Identifier "RadeonGeneric"
Driver "radeon"
#VideoRam 65536
# 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 "RadeonGeneric"
Monitor "GatewayVX700"
DefaultDepth 24
Subsection "Display"
Depth 8
Modes "1024x768"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1024x768"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1024x768"
ViewPort 0 0
EndSubsection
EndSection
I don't get it ,because under lsmod it shows radeon, so I am assuming it is loaded
My card seems to work under XFree86, with SuSE 9.2 - I say seems to work, as normally everything works OK, though DVD video playback is a bit jerky.
Here's what SuSE's SaX2 put in the XF86Config file:
and this is what I changed, and when I try to startx, it gives me a fatal error, so I have to revert back to the way it was before..
Code:
#EndSection
section "DRI"
mode 0666
EndSection
That's probably not correct. Remove the # of the above EndSection. Every Section needs an EndSection. By commenting out the EndSection over the Section "DRI", you probably have an unfinished Section.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.