View previous topic :: View next topic |
Author |
Message |
schroedinger n00b
Joined: 15 Jan 2003 Posts: 43 Location: Vienna
|
Posted: Mon Mar 03, 2003 4:06 pm Post subject: Xfree 4.3.0 and Powered by ATI Cards |
|
|
I installed Xfree 4.3.0 successfully, but it only works with the generic vesa driver. I didn't get Xfree working with the radeon driver, although
they should support the hole Radeon Series including mine:Radeon 9700 Saphire.
Is it possible, that Xfree only supports Build by Ati Cards?
Johannes |
|
Back to top |
|
|
bsolar Bodhisattva
Joined: 12 Jan 2003 Posts: 2764
|
Posted: Mon Mar 03, 2003 4:11 pm Post subject: |
|
|
Can you explain your problem? You get error messages? What is your configuration? Have you tried the 'ati' driver?
BTW. reading the driver enhancements of ther new Xfree it seems that radeon 9700 support is only 2d. _________________ I may not agree with what you say, but I'll defend to the death your right to say it. |
|
Back to top |
|
|
schroedinger n00b
Joined: 15 Jan 2003 Posts: 43 Location: Vienna
|
Posted: Mon Mar 03, 2003 4:26 pm Post subject: |
|
|
THX for this fast reply.
I tried every ATI driver. The ATI driver doesn't work with Xfree 4.3.0.
If i use the radeon driver from Xfree, i get these two error messages:
(WW) No section for instance BusID PCI:1:0:1
(EE) No valid mode found for this DFP/LCD
I also tried the r128 and the ati driver from Xfree, but i got the same errors. |
|
Back to top |
|
|
bsolar Bodhisattva
Joined: 12 Jan 2003 Posts: 2764
|
Posted: Mon Mar 03, 2003 4:32 pm Post subject: |
|
|
Can you provide XF86Config?
PS: and you have agp support enabled in your kernel? _________________ I may not agree with what you say, but I'll defend to the death your right to say it. |
|
Back to top |
|
|
schroedinger n00b
Joined: 15 Jan 2003 Posts: 43 Location: Vienna
|
Posted: Mon Mar 03, 2003 4:34 pm Post subject: |
|
|
Of course
# 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.
# **********************************************************************
# **********************************************************************
# 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 "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)
#
# 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).
#
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/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
# FontPath "/usr/X11R6/lib/X11/fonts/TrueType/"
# FontPath "/usr/X11R6/lib/X11/fonts/freefont/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
# 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><Fn> VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.
# Option "DontVTSwitch"
# 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).
# Option "AllowNonLocalModInDev"
EndSection
# **********************************************************************
# Input devices
# **********************************************************************
# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************
Section "InputDevice"
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"
# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"
# 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" ""
# Option "XkbDisable"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc105"
Option "XkbLayout" "de"
EndSection
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
Section "InputDevice"
# Identifier and driver
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
# Mouse-speed setting for PS/2 mouse.
# Option "Resolution" "256"
# 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"
EndSection
# **********************************************************************
# Other input device sections
# this is optional and is required only if you
# are using extended input devices. This is for example only. Refer
# to the XF86Config man page for a description of the options.
# **********************************************************************
#
# Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
# EndSection
#
# 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
Section "Monitor"
Identifier "BEL"
# 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.5 - 57.0
# 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 40-150
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 xf86config:
Section "Device"
Identifier "ATI"
Driver "radeon"
#VideoRam 131072
# 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 "ATI"
Monitor "BEL"
DefaultDepth 24
Subsection "Display"
Depth 8
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1280x1024" "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 |
|
Back to top |
|
|
bsolar Bodhisattva
Joined: 12 Jan 2003 Posts: 2764
|
Posted: Mon Mar 03, 2003 4:37 pm Post subject: |
|
|
Well it seems ok at first glance...
AGP support is enabled? _________________ I may not agree with what you say, but I'll defend to the death your right to say it. |
|
Back to top |
|
|
schroedinger n00b
Joined: 15 Jan 2003 Posts: 43 Location: Vienna
|
Posted: Mon Mar 03, 2003 4:39 pm Post subject: |
|
|
The agpgart module is loaded (cause of the build by ATI driver for XFree 4.2.0) |
|
Back to top |
|
|
bsolar Bodhisattva
Joined: 12 Jan 2003 Posts: 2764
|
Posted: Mon Mar 03, 2003 4:46 pm Post subject: |
|
|
schroedinger wrote: | The agpgart module is loaded (cause of the build by ATI driver for XFree 4.2.0) |
What do you mean? _________________ I may not agree with what you say, but I'll defend to the death your right to say it. |
|
Back to top |
|
|
schroedinger n00b
Joined: 15 Jan 2003 Posts: 43 Location: Vienna
|
Posted: Mon Mar 03, 2003 4:49 pm Post subject: |
|
|
I thought this kernel module is responsible for agp-support _________________ Imagination is more important than knowledge |
|
Back to top |
|
|
bsolar Bodhisattva
Joined: 12 Jan 2003 Posts: 2764
|
Posted: Mon Mar 03, 2003 4:51 pm Post subject: |
|
|
schroedinger wrote: | I thought this kernel module is responsible for agp-support |
Yes, it is. But what do you mean with 'cause of the build by ATI driver for XFree 4.2.0'. _________________ I may not agree with what you say, but I'll defend to the death your right to say it. |
|
Back to top |
|
|
schroedinger n00b
Joined: 15 Jan 2003 Posts: 43 Location: Vienna
|
Posted: Mon Mar 03, 2003 4:54 pm Post subject: |
|
|
sorry. I didn't compile the agpgart into the kernel, because the ATI driver need an agpgart module for compiling correctly. Sorry, the sentence (cause of the build by ATI driver for XFree 4.2.0) doesn't mean anything _________________ Imagination is more important than knowledge |
|
Back to top |
|
|
bsolar Bodhisattva
Joined: 12 Jan 2003 Posts: 2764
|
Posted: Mon Mar 03, 2003 4:59 pm Post subject: |
|
|
schroedinger wrote: | sorry. I didn't compile the agpgart into the kernel, because the ATI driver need an agpgart module for compiling correctly. Sorry, the sentence (cause of the build by ATI driver for XFree 4.2.0) doesn't mean anything |
Well I have a Radeon Mobility and AGP built in and had no problems with the compilation of the Xfree drivers. _________________ I may not agree with what you say, but I'll defend to the death your right to say it. |
|
Back to top |
|
|
bsolar Bodhisattva
Joined: 12 Jan 2003 Posts: 2764
|
Posted: Mon Mar 03, 2003 5:03 pm Post subject: |
|
|
Hey I found this. _________________ I may not agree with what you say, but I'll defend to the death your right to say it. |
|
Back to top |
|
|
schroedinger n00b
Joined: 15 Jan 2003 Posts: 43 Location: Vienna
|
Posted: Mon Mar 03, 2003 7:06 pm Post subject: |
|
|
Thx for this link, but it doesn't help. they discuss how to install the ATI driver (from ATI) on XFree 4.2.0. There is no magic in doing this. My problem is, that these drivers won't work with Xfree 4.3.0. So i have to use the Xfree Radeon driver, which only seem to work with Build by Ati
cards like yours.
You don't know a trick or a "hidden button" to get Powered by ATI Cards (like mine Radeon 9700 from Saphire) working? _________________ Imagination is more important than knowledge |
|
Back to top |
|
|
bsolar Bodhisattva
Joined: 12 Jan 2003 Posts: 2764
|
Posted: Mon Mar 03, 2003 7:13 pm Post subject: |
|
|
At this point I don't know how to help you... maybe someone else will have a better knowledge about this problem.
BTW. if I hear something that might help I'll tell you.
I am sorry... _________________ I may not agree with what you say, but I'll defend to the death your right to say it. |
|
Back to top |
|
|
schroedinger n00b
Joined: 15 Jan 2003 Posts: 43 Location: Vienna
|
Posted: Mon Mar 03, 2003 7:43 pm Post subject: |
|
|
nevertheless, thank you in spending some time trying to solve my problem
Johannes _________________ Imagination is more important than knowledge |
|
Back to top |
|
|
SQLBoy Guru
Joined: 17 Aug 2002 Posts: 381
|
Posted: Mon Mar 03, 2003 8:55 pm Post subject: |
|
|
I noticed you posted this:
Code: |
(WW) No section for instance BusID PCI:1:0:1
(EE) No valid mode found for this DFP/LCD
|
I remember just one day out of the blue I got an error much like this. Notice it says PCI:1:0:1
Well, do this:
and find your video card. Here is an example of mine: (its a laptop so don't laugh)
Code: |
Bus 1, device 0, function 0:
VGA compatible controller: ATI Technologies Inc Rage Mobility M3 AGP 2x (rev 2).
IRQ 11.
Master Capable. Latency=66. Min Gnt=8.
Prefetchable 32 bit memory at 0xf8000000 [0xfbffffff].
I/O at 0x2000 [0x20ff].
Non-prefetchable 32 bit memory at 0xf4100000 [0xf4103fff].
|
Ok, notice Bus 1, device 0, function 0. In my X config for my Nvidia, it won't work unless I define my busid in the X config. If I were defining it for this card I would put:
inside of the Section "Device" header of my ATI card config in XF86Config.
Anyway, hope that helps. |
|
Back to top |
|
|
schroedinger n00b
Joined: 15 Jan 2003 Posts: 43 Location: Vienna
|
Posted: Mon Mar 03, 2003 9:16 pm Post subject: |
|
|
THX for your reply. I still tried to define the BusID with no success.
Code: |
Bus 1, device 0, function 0:
VGA compatible controller: PCI device 1002:4e44 (ATI Technologies Inc) (rev 0).
IRQ 5.
Master Capable. Latency=32. Min Gnt=8.
Prefetchable 32 bit memory at 0xd0000000 [0xd7ffffff].
I/O at 0xd000 [0xd0ff].
Non-prefetchable 32 bit memory at 0xe5000000 [0xe500ffff].
Bus 1, device 0, function 1:
Display controller: PCI device 1002:4e64 (ATI Technologies Inc) (rev 0).
Master Capable. Latency=32. Min Gnt=8.
Prefetchable 32 bit memory at 0xd8000000 [0xdfffffff].
Non-prefetchable 32 bit memory at 0xe5010000 [0xe501ffff].
|
You can see, there are two devices for my Radeon (1xVGA and 1xDVI i asume). I tried PCI:1:0:1 and PCI:1:0:0.
With PCI:1:0:1 i get the following error:
Code: |
(WW) No section for instance BusID PCI:1:0:1
(EE) No valid mode found for this DFP/LCD
|
With PCI:1:0:0 i only get the folloeing error:
Code: |
(WW) No section for instance BusID PCI:1:0:1
|
Really funny
Johannes _________________ Imagination is more important than knowledge |
|
Back to top |
|
|
SQLBoy Guru
Joined: 17 Aug 2002 Posts: 381
|
Posted: Mon Mar 03, 2003 9:32 pm Post subject: |
|
|
Strange. Do you have 2 video cards? |
|
Back to top |
|
|
schroedinger n00b
Joined: 15 Jan 2003 Posts: 43 Location: Vienna
|
Posted: Mon Mar 03, 2003 9:37 pm Post subject: |
|
|
no, but i have TV-Out, 1 VGA Out and 1 DVI Out. That's the standard accessoir of Radeon 9700 Pro Cards, and should not make any problems.
PCI:1:0:0 is the card itself, and PCI:1:0:1 is the TV-Out or the DVI-Out. _________________ Imagination is more important than knowledge |
|
Back to top |
|
|
|