Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with 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.
Like PixelView PlayTV PRO.... I can not make this card work. To be more exact, it works, with some form of 3D, but not fully functional.
I have read tons of manuals, and what was most helpufull was on from this forum... regarding DRI compilation into kernel.... what I have done, and finally got fgl_glxgears->
1524 frames in 5.0 seconds = 304.800 FPS
1207 frames in 5.0 seconds = 241.400 FPS
1198 frames in 5.0 seconds = 239.600 FPS
1199 frames in 5.0 seconds = 239.800 FPS
but with flickering of the monitor, and if I run Tuxracer.... it just garbles my screen.... like it is devided to squares, and messed up... I can recognize what is on the screen, but only 'cause I know what I have started...(and Tuxracer music )
Once again, it is Slackware 9.1, 2.4.23 kernel precompiled so DRI is in there, reinstalled XFree, tryed with source drivers, with ATI drivers (even newest one, that is currently running), but nothing can make this card produce valid 3D... yes, I want to play games on Slack
here is my XF86Config-4:
Quote:
File: XF86Config-4
# File generated by fglrxconfig (C) ATI Research, a substitute for xf86config.
# Note by ATI: the below copyright notice is there for servicing possibly
# pending third party rights on the file format and the instance of this file.
#
# 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.
# **********************************************************************
# **********************************************************************
# DRI Section
# **********************************************************************
Section "dri"
# Access to OpenGL ICD is allowed for all users:
Mode 0666
# Access to OpenGL ICD is restricted to a specific user group:
# Group 100 # users
# Mode 0660
EndSection
# **********************************************************************
# 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 Type1 and FreeType font modules
Load "type1"
Load "freetype"
# This loads the GLX module
Load "glx" # libglx.a
Load "dri" # libdri.a
Load "v4l"
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)
#
# 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).
#
# The module search path. The default path is shown here.
# ModulePath "/usr/X11R6/lib/modules"
EndSection
# **********************************************************************
# Server flags section.
# **********************************************************************
Section "ServerFlags"
# Uncomment this to cause a core dump at the spot where a signal is
# received. This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging
# Option "NoTrapSignals"
# Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.
# Option "DontZap"
# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
# sequences. This allows clients to receive these key events.
# Option "Dont Zoom"
# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.
# Option "DisableVidModeExtension"
# Uncomment this to enable the use of a non-local xvidtune client.
# Option "AllowNonLocalXvidtune"
# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.
# Option "DisableModInDev"
# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).
Identifier "Keyboard1"
Driver "Keyboard"
# 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"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# 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 XFree86
# Option "XkbRules" "xfree86"
# Option "XkbModel" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# 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 "fglrx"
# 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
# installed.
# 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 "Screen0"
Device "ATI Graphics Adapter"
Monitor "Monitor0"
DefaultDepth 24
#Option "backingstore"
Subsection "Display"
Depth 24
Modes "1280x1024" "1024x768" "800x600"
ViewPort 0 0 # initial origin if mode is smaller than desktop
# Virtual 1280 1024
EndSubsection
EndSection
# 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 "Server 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.
Screen "Screen0"
# 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".
[fglrx] Maximum main memory to use for locked dma buffers: 431 MBytes.
[fglrx] module loaded - fglrx 3.7.0 [Dec 18 2003] on minor 0
[fglrx] AGP detected, AgpState = 0x1f00421b (hardware caps of chipset)
[fglrx] To use AGP on this CPU with this kernel, you really should have 4MB pages disabled. Use `mem=nopentium` on the bootloader commandline.
[fglrx] AGP enabled, AgpCommand = 0x1f004312 (selected caps)
[fglrx] free AGP = 54800384
[fglrx] max AGP = 54800384
[fglrx] free LFB = 116391936
[fglrx] max LFB = 116391936
[fglrx] free Inv = 0
[fglrx] max Inv = 0
[fglrx] total Inv = 0
[fglrx] total TIM = 0
[fglrx] total FB = 0
[fglrx] total AGP = 16384
If any1 has an idea how to make this card work.... please tell me...
Try those instead,
dmesg | grep agp
cat /var/log/XFree86.0.log | grep EE ...WW ...agp
> Option "UseInternalAGPGART" "no" ...in your config file, means the driver will use the kernel's agpgart, as opposed to the one supplied by the driver. Remember the difference, it might come in handy if you want to try it both ways, but you need to have the kernel's agpgart as a module [...and not loaded] in order to use the driver's.
Anyhow that's just generally speaking, so you know what's happening, for I'm pretty sure your problem lies with agp, like a lot of other users, and since dmesg shows [fglrx] as loaded, I would assume there's nothing wrong with your kernel's drm settings or the fglrx module itself.
Some chipsets work only with the kernel's agpgart, some only with the driver's, some require patches.Do a search for radeon and your motherboard chipset, chances are you'll find what you're looking for.
well I have resolved my problem... I am going to change my Radeon 9200 for Nvidia FX 5200
I have lost too much time trying to make it work, looked all over the web, called friends, even I tried to get a response from ATI.... no luck. All that ATI said is autoresponded message, that they will use my input for their purposes, and will not answer me (basically), and that was almost month ago.
I have wrote them a farewell letter, and I will post it here now. This is just a step to encourage other unhappy ATI Radeon owners, to write to ATI, and to try to force them to do their job!
"I just cannot force your card to work under Linux. I have tried Mandrake 9.2 and Slackware 9.1, compiled Kernel, read tons of manuals all over the web, and still I can not have 3D and TV OUT. I have used Fire GL drivers, and both current and previous driver from download section of this site. NOTHING WORKS!!!!
So basically what am I saying here is that I am going to change my ATI card for NVIDIA tomorrow, and I will never, ever purchase any of your products again, and I will spread the word among my friends, and people I chat with over several forums. You do not deserve nothing better than this. Customer Care??? You do not know meaning of these words...
Maybe in time, and if letters like this one come pouring down (and I do expect so), you will find out the power of market, and power of customers.
Thank you for nothing!"
If this is not allowed, I am sorry, admins are more than welcome to delete this post. I do not want to "polute" such a great forum with something that do not belong here.
Distribution: Mandrake 10.0 Official, Freebsd 5.2.1 mini
Posts: 40
Rep:
Well Drax, I'm starting to feel exactly the same way you are. I have a 9600 pro and can't even get x to start. So I also am selling my video card and purchasing an nvidia.
I love ati cards on windows machines, but i agree, they need to definitely do something about this driver issue of theirs.
Hey I'm quite the newbie around here, as I just installed mandrake 9.1 last night. I had to install it under text mode because the 9800pro in my box didnt' seem to have any sort of native support. Anyway, I downloaded the 9800pro driver from ATI's site and burnt the .rpm file to a cd-rw. Anyway, since I'm a total newbie that's about as far as I can get. Do you have any advice for me as to how to get this card to work? My system specs are in my profile below. Everything seems to be working fine in text mode, however I get an error when i try to stat kde. Also, do I need any specific info for my monitor (samsung 191t). When I initially set up the gui from text mode I selected the correct resolutions and such, but is there more information that i'm missing?
There is a Readme file with installation instructions that you should get :-)
The steps briefly are as follows (as root),
1) Install the rpm
2) change to /lib/modules/fglrx/build/ and do "./make.sh"
3) CD up one level and do "./make-install.sh"
3) DO "fglrxconfig" and answer the questions about your hardware (make sure you have your monitor specs handy)
I did have a bit of a problem though (of course I'm a newbie what can I say)
Anyway, I installed the rpm as instructed and it said that it was successfully installed. However, it also stated that "Tailored kernel module for fglrx not present in your system" I assumed this was because I am instructed to make that module in the next step. Anyway, I went to /lib/modules/fglrx/build and did a "./make.sh". It came up with the ATI module gen 2.0; however, I got a message saying "kernel includes at /usr/src/linux/include not found or incomplete file: /usr/src/linux/include/linux/version.h
As i'm quite the newbie I dont' know what to make of this information. I was hoping someone could point out the undoubtably easy error that I'm making all the time.
I just finnished following the quick guide posted by Aussie. The three or four steps have given me an easy install of my Radeon 9200se and everything is working. I have not tried the TV out yet but thats not too important. Thanks, I didn't even need to post the question. The config tool even got my mouse to make use of the scroll wheel.
I've never used the tv out on either of my 9800pro cards, the one in my main workstation only connects to a 17" LCD and the one that I use to watch tv connects to a 46" plasma display. Both of them work great though....games and DVD's on the plasma display are awesome.
Ok guys ... I'm trying to get a 9600 pro in my laptop working ... Slack 9.1 with the acpi kernel ... load base ati driver and it locks the machine hard ... run thru the make make install scripts and no change ... even better I would settle for the no 3d version you now the lame default radeon drive with Xfree but that won't find any screens ... right now i'm left with just vesa driver and a really poor resolution ... I typed all that and didn't tell you about the hardware ... sager np4780 17" lcd 1440x900 and the radeon 9600 pro with an optional 4x/8x switch in the bios.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.