LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 03-11-2006, 11:22 AM   #1
kimothy
Member
 
Registered: Jun 2005
Location: Norway
Distribution: Slackware 11.0
Posts: 87

Rep: Reputation: 15
New ATI Driver Trouble


Hi. I just installed the ATI drivers on my Slackware 10.2 (current) system. I installed as written at the ati site and then i ran;

Code:
aticonfig --initial --input=/etc/X11/xorg.conf
After I restarted I tried glx gears

Code:
kim@KIMOTHY:~$ glxgears
libGL error: failed to open DRM: Operation not permitted
libGL error: reverting to (slow) indirect rendering
769 frames in 5.0 seconds = 153.684 FPS
the "radeon" drivers are better then this!

how to I fix it?

Thanks
 
Old 03-11-2006, 11:48 AM   #2
lestoil
Member
 
Registered: Apr 2004
Location: new york
Distribution: win2k,ubuntu,sw13,arch,centos5.3
Posts: 815

Rep: Reputation: 31
What video card or chip? What kernel? Desktop or lappy? IS it fglrx that you installed so later used fglrx.conf?
 
Old 03-11-2006, 08:19 PM   #3
kimothy
Member
 
Registered: Jun 2005
Location: Norway
Distribution: Slackware 11.0
Posts: 87

Original Poster
Rep: Reputation: 15
this is my computer

Desktop

AMD Athlon 2400+ Mobility
Radeon 9800 PRO (128MB)
Corsair 1024 MB ram

Slackware 10.2 (Upgraded to Current)
Kernel 2.6.15.6 (My Own)
xorg 6.9
 
Old 03-11-2006, 09:12 PM   #4
noxious
Member
 
Registered: May 2004
Location: Ohio, USA
Distribution: LinuxMint Gloria, Ubuntu 9.10
Posts: 299

Rep: Reputation: 30
I just used the latest driver for my laptop's Rage Mobility 9600. However, I ran "aticonfig --initial" only - then, for some reason, it wanted a full reboot, not just a ctrl+alt, backspace to restart x, for the drivers to work.
 
Old 03-12-2006, 12:04 AM   #5
j79zlr
Member
 
Registered: Dec 2005
Location: Chicago
Distribution: Gentoo, Slackware, and FreeBSD
Posts: 38

Rep: Reputation: 15
Sounds like a permissions problem, do you have this in your xorg.conf:

Code:
Section "DRI"
        Mode            0666
EndSection
 
Old 03-12-2006, 04:50 AM   #6
kimothy
Member
 
Registered: Jun 2005
Location: Norway
Distribution: Slackware 11.0
Posts: 87

Original Poster
Rep: Reputation: 15
Thank YOU!

Quote:
Originally Posted by j79zlr
Sounds like a permissions problem, do you have this in your xorg.conf:

Code:
Section "DRI"
        Mode            0666
EndSection
Thanks! That did the trick!
 
Old 03-12-2006, 11:25 AM   #7
kimothy
Member
 
Registered: Jun 2005
Location: Norway
Distribution: Slackware 11.0
Posts: 87

Original Poster
Rep: Reputation: 15
Hi again. I still got some trouble... glxgears gives me around 6500fps, which should be about right, but superkaramba themes with transparensy can take up over 50% of the prossessor power and ppracer (or tuxracer) performs so bad it's not usable. So bad that is hard to get out of the game again. The terminal will show this when I have played ppracer:

Code:
__FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
fglX11AllocateManagedSurface: __FGLTexMgrCreateObject failed!!
FGLTexMgr: open of shared memory object failed (Function not implemented)
__FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
fglX11AllocateManagedSurface: __FGLTexMgrCreateObject failed!!
FGLTexMgr: open of shared memory object failed (Function not implemented)
__FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
fglX11AllocateManagedSurface: __FGLTexMgrCreateObject failed!!
FGLTexMgr: open of shared memory object failed (Function not implemented)
__FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
fglX11AllocateManagedSurface: __FGLTexMgrCreateObject failed!!
FGLTexMgr: open of shared memory object failed (Function not implemented)
__FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
fglX11AllocateManagedSurface: __FGLTexMgrCreateObject failed!!
FGLTexMgr: open of shared memory object failed (Function not implemented)
__FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
fglX11AllocateManagedSurface: __FGLTexMgrCreateObject failed!!
FGLTexMgr: open of shared memory object failed (Function not implemented)
__FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
fglX11AllocateManagedSurface: __FGLTexMgrCreateObject failed!!
kim@KIMOTHY:~$
This is a copy of my xorg.conf:

Code:
# File generated by xf86config.
#
# Copyright (c) 1999 by The XFree86 Project, Inc.
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
# 
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
# 
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL
# THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
# 
# Except as contained in this notice, the name of the XFree86 Project shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from the
# XFree86 Project.
#
# **********************************************************************
# Refer to the XF86Config(4/5) man page for details about the format of 
# this file.
# **********************************************************************
# NOTE:  This is a NEW IMPROVED version of XF86Config-fbdev that uses the vesa
# driver instead of the fbdev driver.  Thanks to Kenneth Fanyo who pointed
# this out to me. :)
# This XF86Config file is designed for use with the VESA framebuffer.
# This generic interface should work with nearly all video cards
# (although not every card will support every resolution).
# With the new driver, it should no longer be required to have frame buffer
# support in the kernel, or to run it on the console.
#
# Enjoy! :)
# -- volkerdi@slackware.com
#
# **********************************************************************
# Module section -- this  section  is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
# **********************************************************************
# Files section.  This allows default font and rgb paths to be set
# **********************************************************************
# **********************************************************************
# Server flags section.
# **********************************************************************
# **********************************************************************
# Input devices
# **********************************************************************
# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
# Some examples of extended input devices
# Section "InputDevice"
#    Identifier "spaceball"
#    Driver     "magellan"
#    Option     "Device"        "/dev/cua0"
# EndSection
#
# Section "InputDevice"
#    Identifier "spaceball2"
#    Driver     "spaceorb"
#    Option     "Device"        "/dev/cua0"
# EndSection
#
# Section "InputDevice"
#    Identifier "touchscreen0"
#    Driver     "microtouch"
#    Option     "Device"        "/dev/ttyS0"
#    Option     "MinX"          "1412"
#    Option     "MaxX"          "15184"
#    Option     "MinY"          "15372"
#    Option     "MaxY"          "1230"
#    Option     "ScreenNumber"  "0"
#    Option     "ReportingMode" "Scaled"
#    Option     "ButtonNumber"  "1"
#    Option     "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
#    Identifier "touchscreen1"
#    Driver     "elo2300"
#    Option     "Device"        "/dev/ttyS0"
#    Option     "MinX"          "231"
#    Option     "MaxX"          "3868"
#    Option     "MinY"          "3858"
#    Option     "MaxY"          "272"
#    Option     "ScreenNumber"  "0"
#    Option     "ReportingMode" "Scaled"
#    Option     "ButtonThreshold"       "17"
#    Option     "ButtonNumber"  "1"
#    Option     "SendCoreEvents"
# EndSection
# **********************************************************************
# Monitor section
# **********************************************************************
# Any number of monitor sections may be present
# **********************************************************************
# Graphics device section
# **********************************************************************
# Any number of graphics device sections may be present
# **********************************************************************
# 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.
# **********************************************************************
# 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
# 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.
# 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".
	Identifier     "Simple Layout"
	Screen      0  "aticonfig Screen 0" 0 0
	InputDevice    "Mouse1" "CorePointer"
	InputDevice    "Keyboard1" "CoreKeyboard"
EndSection

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.
# 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)
# 
# If you don't have a floating point coprocessor and emacs, Mosaic or other
# programs take long to start up, try moving the Type1 and Speedo directory
# to the end of this list (or comment them out).
# 
# ModulePath can be used to set a search path for the X server modules.
# The default path is shown here.
#    ModulePath "/usr/X11R6/lib/modules"
	RgbPath      "/usr/X11R6/lib/X11/rgb"
	FontPath     "/usr/X11R6/lib/X11/fonts/local/"
	FontPath     "/usr/X11R6/lib/X11/fonts/misc/"
	FontPath     "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
	FontPath     "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
	FontPath     "/usr/X11R6/lib/X11/fonts/Type1/"
	FontPath     "/usr/X11R6/lib/X11/fonts/CID/"
	FontPath     "/usr/X11R6/lib/X11/fonts/Speedo/"
	FontPath     "/usr/X11R6/lib/X11/fonts/75dpi/"
	FontPath     "/usr/X11R6/lib/X11/fonts/100dpi/"
	FontPath     "/usr/X11R6/lib/X11/fonts/cyrillic/"
EndSection

Section "Module"

# This loads the DBE extension module.
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
# This loads the font modules
# This loads the GLX module
	Load  "dbe"  	# Double buffer extension
	SubSection "extmod"
		Option	    "omit xfree86-dga"   # don't initialise the DGA extension
	EndSubSection
	Load  "type1"
	Load  "freetype"
    #Load        "speedo"
	Load  "glx"
	Load  "dri"
EndSection

Section "InputDevice"

# 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"
# Set the keyboard auto repeat parameters.  Not all platforms implement
# this.
#    Option     "AutoRepeat"    "500 5"
# Specifiy which keyboard LEDs can be user-controlled (eg, with xset(1)).
#    Option     "Xleds" "1 2 3"
# To disable the XKEYBOARD extension, uncomment XkbDisable.
#    Option     "XkbDisable"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a European
# keyboard, you will probably want to use one of:
#
#    Option     "XkbModel"      "pc102"
#    Option     "XkbModel"      "pc105"
#
# If you have a Microsoft Natural keyboard, you can use:
#
#    Option     "XkbModel"      "microsoft"
#
# If you have a US "windows" keyboard you will want:
#
#    Option     "XkbModel"      "pc104"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
#
#    Option     "XkbLayout"     "de"
#
# or:
#
#    Option     "XkbLayout"     "de"
#    Option     "XkbVariant"    "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
#
#    Option     "XkbOptions"    "ctrl:swapcaps"
# These are the default XKB settings for X.Org
#
#    Option     "XkbRules"      "xorg"
#    Option     "XkbModel"      "pc101"
#    Option     "XkbOptions"    ""
	Identifier  "Keyboard1"
	Driver      "kbd"
	Option	    "XkbLayout" "no"
#    Option     "XkbVariant"    ""
EndSection

Section "InputDevice"

# Identifier and driver
#    Option     "zAxisMapping" "4 5"
# On platforms where PnP mouse detection is supported the following
# protocol setting can be used when using a newer PnP mouse:
#    Option     "Protocol"      "Auto"
# The available mouse protocols types that you can set below are:
#    Auto BusMouse GlidePoint GlidePointPS/2 IntelliMouse IMPS/2
#    Logitech Microsoft MMHitTab MMSeries Mouseman MouseManPlusPS/2
#    MouseSystems NetMousePS/2 NetScrollPS/2 OSMouse PS/2 SysMouse
#    ThinkingMouse ThinkingMousePS/2 Xqueue
# which is usually a symbolic link to the real device.
#   Option "Device"      "/dev/ttyS0"
#   Option "Device"      "/dev/ttyS1"
# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.
#    Option "Protocol"	"Xqueue"
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.
#    Option "BaudRate"		"9600"
#    Option "SampleRate"	"150"
# Emulate3Buttons is an option for 2-button Microsoft 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"
	Identifier  "Mouse1"
	Driver      "mouse"
	Option	    "Protocol" "IMPS/2"
# The mouse device.  The device is normally set to /dev/mouse,
	Option	    "Device" "/dev/mouse"
#   Option "Device"      "/dev/psaux"
EndSection

Section "Monitor"

# 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	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.
	Identifier   "My Monitor"
	HorizSync    30.0 - 107.0
	VertRefresh  48.0 - 120.0
EndSection

Section "Monitor"
	Identifier   "aticonfig Monitor 0"
EndSection

Section "Device"

    #VideoRam    4096
    # Insert Clocks lines here if appropriate
	Identifier  "VESA Framebuffer"
	Driver      "radeon"
EndSection

Section "Device"
	Identifier  "ATI Graphics Adapter 0"
	Driver      "fglrx"
	BusID       "PCI:1:0:0"
EndSection

Section "Screen"

# If your card can handle it, a higher default color depth (like 24 or 32)
# is highly recommended.
#   DefaultDepth 8
#   DefaultDepth 16
#   DefaultDepth 32
# "1024x768" is also a conservative usable default resolution.  If you
# have a better monitor, feel free to try resolutions such as
# "1152x864", "1280x1024", "1600x1200", and "1800x1400" (or whatever your
# card/monitor can produce)
	Identifier "Screen 1"
	Device     "VESA Framebuffer"
	Monitor    "My Monitor"
	DefaultDepth     24
	SubSection "Display"
		Depth     24
		Modes    "1280x1024" "1600x1200" "1024x768"
	EndSubSection
	SubSection "Display"
		Depth     16
		Modes    "1280x1024" "1024x768" "800x600" "640x480"
	EndSubSection
	SubSection "Display"
		Depth     24
		Modes    "1280x1024" "1024x768" "800x600" "640x480"
	EndSubSection
	SubSection "Display"
		Depth     32
		Modes    "1280x1024" "1024x768" "800x600" "640x480"
	EndSubSection
EndSection

Section "Screen"
	Identifier "aticonfig Screen 0"
	Device     "ATI Graphics Adapter 0"
	Monitor    "aticonfig Monitor 0"
	DefaultDepth     24
	SubSection "Display"
		Viewport   0 0
		Depth     24
	EndSubSection
EndSection

Section "DRI"
	Mode         0666
EndSection
Please help me... :-(

I'm sorry, but I might not reply before next week.

Thanks For ANY reply :-)
 
Old 03-12-2006, 11:55 AM   #8
lestoil
Member
 
Registered: Apr 2004
Location: new york
Distribution: win2k,ubuntu,sw13,arch,centos5.3
Posts: 815

Rep: Reputation: 31
What about uncommenting #videoram and putting 131072 instead of what you have?

Last edited by lestoil; 03-12-2006 at 12:17 PM.
 
Old 03-12-2006, 01:50 PM   #9
noxious
Member
 
Registered: May 2004
Location: Ohio, USA
Distribution: LinuxMint Gloria, Ubuntu 9.10
Posts: 299

Rep: Reputation: 30
For what it's worth, I've had no luck getting any 3-D support in Slackware... Debian, Ubuntu (with the exact same fglrx drivers) work great. But, Slackware won't give me any 3-D. fgl_glxgears gives me the same gibberish you got. I used the exact same installation procedure on each distro, and Slackware won't move into the 21st century.
 
Old 03-12-2006, 02:00 PM   #10
dunric
Member
 
Registered: Jul 2004
Distribution: Void Linux, former Slackware
Posts: 498

Rep: Reputation: 100Reputation: 100
kimothy:
Check if you have some similar entry in /etc/fstab
Code:
shm              /dev/shm         tmpfs       defaults         0   0
and device shm _is_ mounted.
 
Old 03-12-2006, 02:02 PM   #11
odevans
Member
 
Registered: Nov 2005
Location: Columbus, OH, USA
Distribution: Slackware
Posts: 246

Rep: Reputation: 30
Do you guys have POSIX shared memory enabled? Try adding the following to /etc/fstab
Code:
tmpfs  /dev/shm  tmpfs  defaults  0  0
and mount it with mount /dev/shm

Although I have given up completely on the ATi drivers myself (wouldn't play nice w/ widescreen laptop) this one had me for a while...

EDIT:

dunric, ya beat me to it!
 
Old 03-16-2006, 01:45 PM   #12
kimothy
Member
 
Registered: Jun 2005
Location: Norway
Distribution: Slackware 11.0
Posts: 87

Original Poster
Rep: Reputation: 15
Thanks. It works now! Everything seems to work now... :-) Thanks a lot!
 
Old 03-16-2006, 01:56 PM   #13
rickh
Senior Member
 
Registered: May 2004
Location: Albuquerque, NM USA
Distribution: Debian-Lenny/Sid 32/64 Desktop: Generic AMD64-EVGA 680i Laptop: Generic Intel SIS-AC97
Posts: 4,250

Rep: Reputation: 62
Code:
tmpfs  /dev/shm  tmpfs  defaults  0  0
Should that be there for any distro in addition to

Code:
/dev/hda8       none            swap    sw              0       0
or is that a Slackware thing?

Edit after trying:
Didn't make any difference in glxgears reporting in either of my systems.

Last edited by rickh; 03-16-2006 at 02:44 PM.
 
Old 03-17-2006, 12:42 AM   #14
kimothy
Member
 
Registered: Jun 2005
Location: Norway
Distribution: Slackware 11.0
Posts: 87

Original Poster
Rep: Reputation: 15
swap should be there

swap should be in the fstab. do you have a swap partition?

heres my fstab:

Code:
/dev/hda8        swap             swap        defaults          0   0
/dev/hda6        /                reiserfs    defaults          1   1
/dev/hda7        /home            reiserfs    defaults          1   2
/dev/hda1        /mnt/hda1        ntfs        ro                1   0
/dev/hda5        /mnt/hda5        vfat        defaults          1   0
/dev/cdrom       /mnt/cdrom       auto        noauto,owner,user 0   0
/dev/fd0         /mnt/floppy      auto        noauto,owner      0   0
devpts           /dev/pts         devpts      gid=5,mode=620    0   0
proc             /proc            proc        defaults          0   0
shm              /dev/shm         tmpfs       defaults          0   0
tmpfs            /dev/shm         tmpfs       defaults          0   0
have you typed "aticonfig --initial --input=/etc/X11/xorg.conf" as root?
 
Old 03-17-2006, 09:26 AM   #15
rickh
Senior Member
 
Registered: May 2004
Location: Albuquerque, NM USA
Distribution: Debian-Lenny/Sid 32/64 Desktop: Generic AMD64-EVGA 680i Laptop: Generic Intel SIS-AC97
Posts: 4,250

Rep: Reputation: 62
I think that manual entry was needed with kernel 2.4 on older systems, but on modern ones, it's built in ... at least on my Debian systems it seems to be. I don't have any such line in fstab, but:

Code:
debian:~$ df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/hdb1             897M  205M  645M  25% /
tmpfs                 218M     0  218M   0% /dev/shm
/dev/hdb9              62G   20G   40G  33% /home
/dev/hdb8             449M  8.1M  417M   2% /tmp
/dev/hdb5             6.0G  2.5G  3.3G  44% /usr
/dev/hdb6             3.3G 1014M  2.1G  33% /var
/dev/hda2              30G   16G   14G  55% /mnt/windata1
/dev/hda3              31G   20G   11G  66% /mnt/windata2
tmpfs                  10M  108K  9.9M   2% /dev
debian:~$
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
ATI fglrx driver trouble Alexey Andriyanov Linux - Hardware 4 08-17-2005 01:35 AM
Trouble with ATI Driver/Card CircuitSix Fedora 1 04-04-2005 09:52 PM
Trouble in installing ati driver Kami.JZ Linux - Newbie 1 11-25-2004 12:53 PM
[SuSE 9.1] ATi driver -> login trouble 4hp SUSE / openSUSE 5 10-18-2004 05:26 PM
Trouble with Official ATI driver for Radeon amp Linux - Hardware 2 07-24-2003 07:34 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 03:23 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration