LinuxQuestions.org
Page 1 of 2 1 2
Show 50 post(s) from this thread on one page

LinuxQuestions.org (/questions/)
-   Fedora (https://www.linuxquestions.org/questions/fedora-35/)
-   -   Fedor core 2 and ATI fglrx drivers (https://www.linuxquestions.org/questions/fedora-35/fedor-core-2-and-ati-fglrx-drivers-188259/)

fitz9948 05-31-2004 11:14 PM
Fedor core 2 and ATI fglrx drivers
 
I installed FC2, installed there kernel source, and then compiled the kernel, just using the default settings that the original FC2 kernel was set to, I had to compile the kernel inorder to build ati drivers. So I reboot, and everything goes just fine, so now I downloaded the newest drivers from ATI version 3.9.0 everything compiled and loaded up just fine, then I ran fglrxconfig created an XF86Config-4 and moved that to xorg.conf. I rebooted the system everything seemed to go fine, ran glxinfo and says direct rendering is not going. I checked and fglrx module is loaded up and being used. I checked dmesg and no errors reported. I have no clue what to do from here. I really hope I can figure how to get this going because so far I really like fedora core 2.

motub 06-01-2004 06:06 AM
Could you post the config file so that we could see what might be wrong with it?

It would seem (if the fglrx module is loading, and dmesg reports no errors) that the problem might be that DRI is not turned on in the xorg config. But we can't know if that's really the case until we see it, can we ;) ?

fitz9948 06-01-2004 08:29 AM
Here ya go:



# **********************************************************************
# 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

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/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
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><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" "pc101"
Option "XkbLayout" "us"

EndSection


# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

# Identifier and driver

Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Device" "/dev/input/mice"

# 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 "Monitor0"
HorizSync 30-50
VertRefresh 50 - 70
Option "DPMS"

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
# installed.

# BusID "PCI:0:10:0"

# VideoRam 256

# Clocks 25.2 28.3

EndSection

# === ATI device section ===

Section "Device"
Identifier "ATI Graphics Adapter"
Driver "fglrx"
# ### generic DRI settings ###
# === disable PnP Monitor ===
#Option "NoDDC"
# === disable/enable XAA/DRI ===
Option "no_accel" "no"
Option "no_dri" "no"
# === misc DRI settings ===
Option "mtrr" "off" # disable DRI mtrr mapper, driver has its own code for mtrr
# ### FireGL DDX driver module specific settings ###
# === Screen Management ===
Option "DesktopSetup" "0x00000000"
Option "MonitorLayout" "AUTO, AUTO"
Option "IgnoreEDID" "off"
Option "HSync2" "unspecified"
Option "VRefresh2" "unspecified"
Option "ScreenOverlap" "0"
# === TV-out Management ===
Option "NoTV" "yes"
Option "TVStandard" "NTSC-M"
Option "TVHSizeAdj" "0"
Option "TVVSizeAdj" "0"
Option "TVHPosAdj" "0"
Option "TVVPosAdj" "0"
Option "TVHStartAdj" "0"
Option "TVColorAdj" "0"
Option "GammaCorrectionI" "0x00000000"
Option "GammaCorrectionII" "0x00000000"
# === OpenGL specific profiles/settings ===
Option "Capabilities" "0x00000000"
# === Video Overlay for the Xv extension ===
Option "VideoOverlay" "on"
# === OpenGL Overlay ===
# Note: When OpenGL Overlay is enabled, Video Overlay
# will be disabled automatically
Option "OpenGLOverlay" "off"
# === Center Mode (Laptops only) ===
Option "CenterMode" "off"
# === Pseudo Color Visuals (8-bit visuals) ===
Option "PseudoColorVisuals" "off"
# === QBS Management ===
Option "Stereo" "off"
Option "StereoSyncEnable" "1"
# === FSAA Management ===
Option "FSAAEnable" "no"
Option "FSAAScale" "1"
Option "FSAADisableGamma" "no"
Option "FSAACustomizeMSPos" "no"
Option "FSAAMSPosX0" "0.000000"
Option "FSAAMSPosY0" "0.000000"
Option "FSAAMSPosX1" "0.000000"
Option "FSAAMSPosY1" "0.000000"
Option "FSAAMSPosX2" "0.000000"
Option "FSAAMSPosY2" "0.000000"
Option "FSAAMSPosX3" "0.000000"
Option "FSAAMSPosY3" "0.000000"
Option "FSAAMSPosX4" "0.000000"
Option "FSAAMSPosY4" "0.000000"
Option "FSAAMSPosX5" "0.000000"
Option "FSAAMSPosY5" "0.000000"
# === Misc Options ===
Option "UseFastTLS" "0"
Option "BlockSignalsOnLock" "on"
Option "UseInternalAGPGART" "no"
Option "ForceGenericCPU" "no"
BusID "PCI:1:0:0" # vendor=1002, device=514c
Screen 0
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 "Screen0"
Device "ATI Graphics Adapter"
Monitor "Monitor0"
DefaultDepth 24
#Option "backingstore"

Subsection "Display"
Depth 24
Modes "1280x1024"
ViewPort 0 0 # initial origin if mode is smaller than desktop
# Virtual 1280 1024
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 "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".

InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"

EndSection

### EOF ###

fitz9948 06-01-2004 04:23 PM
I had to apply a patch for the ati drivers. The patch can be found here for anyone that might be trying to get the new drivers to workd with FC 2. http://rambo.its.tudelft.nl/~ewald/p....9.0-fc2.patch

moax_cp 06-02-2004 01:24 PM
Quote:
I installed FC2, installed there kernel source, and then compiled the kernel, just using the default settings that the original FC2 kernel was set to, I had to compile the kernel inorder to build ati drivers.
Is this true? I can understand the need to have the kernel source but why do you have to compile the kernel?

fitz9948 06-02-2004 01:35 PM
If I just had the kernel source the ati drivers complain about not being able to build the module. So all I did was compile the kernel using the fedora config file. I always have to compile a kernel for these ati drivers. I have used serveral distro's and thats what I have always had to do.

boxsterman 06-02-2004 02:25 PM
I also experienced the problem of having a segmentation fault when loading the fglrx module. The following steps helped me getting rid of the problem, with lots of help from this site of course :-)
[Environment: IBM Thinkpad T41p with clean Fedora Core 2]

1. Fetch a clean kernel 2.6.6 from kernel.org and extract it to /usr/src
2. Do a "make mrproper" and "make clean" to clear up previous kernel experiments if no clean kernel src package was used
3. copy *"original" .config from /boot/config-2.6.5-1.358 to /usr/src/linux-2.6.6
4. Do "make menuconfig" and set the following options
- Enable agp as module instead of build-in (Device Drivers -> Character devices -> AGP support)
- Enable your AGP chipset support (for me INTEL i865)
- Disable "Direct Rendering Management" just below AGP support
- Disable "Processor type and features -> Use register arguments" (not sure if really required)
- Enable "Kernel hacking -> Use 4Kb for kernel stacks instead of 8Kb"
5. Do a "make all && make modules_install && make install"
6. Reboot and make sure that the correct kernel is selected for the new boot process
7. Boot should work without problems ;-)
8. Fetch the ATI drivers drivers and install with "rpm -ivh --replacefiles fglrx-4.3.0-3.9.0.i386.rpm"
9. It should complain about not finding matching kernel modules and then start building them, including a modprobe of the new driver module (which caused segmentation faults problems on my system)
10. Use the configuration utility fglrxconfig to configure a sample XF86Config-4 file. Set the option "UseInternalAGPGART" to no
11. Copy at least the device section with identifier "ATI Graphics Adapter" and device "fglrx" to your existing xorg.conf and set the Device entry in the Screen section to "ATI Graphics Adapter".

After that I was able to reboot and have the fglrx device active (check /var/log/Xorg.0.log), but without 3D support due to problems with the agpgart modules. That was due to the fact that the agpgart and the appropriate AGP chipset support were not loaded automatically (at least the chipset module intel_agp was not loaded on my system). I added the following line to /etc/modprobe.conf to force loading of the AGP support including chipset support:

install agpgart /sbin/modprobe --ignore-install agpgart && /sbin/modprobe intel_agp

This solved my problem so far ... now I'm encountering problems when resuming the laptop from suspend mode. Does anybody has a clue what that problem might be? BTW, I using ACPI instead of APM, could this cause the problem? I remember an entry in the Xorg log about not finding APM support ....

ricguitar 06-03-2004 05:49 AM
I am trying to install the ATI driver 3.0.9 too. But when I type:
rpm -Uh --force [name of the file].rpm (as they suggest in ati website), the following message appears:

Tailored kernel module for fglrx not present in your system.
You must go to /lib/modules/fglrx/build_mod subdir
and execute './make.sh' to build a fully customed kernel module.
Afterwards go to /lib/modules/fglrx and run './make_install.sh'
in order to install the module into your kernel's module repository.

So, I went to /lib/modules/fglrx/build_mod subdir, but when I try to execute ./make.sh, a error message appears saying Permission Denied. (Yes, I was logged as root)

I already have the kernel source installed. Please, could you tell me what I have to do to install that driver properly??

motub 06-03-2004 05:55 AM
First of all, the file make.sh is not what you were instructed to run. Try running make_install.sh (which probably calls make.sh when building the module).

Sometimes you have to run sh ./make_install.sh instead, to explicitly indicate that sh should run the script.

Hope this helps.

ricguitar 06-03-2004 07:41 AM
Sorry man, but it didnt work!
I received the same message:
bash: ./make_install.sh: Permission denied
In the ATI website is writen that I need the folowing softwares installed:

Kernel source code
Kernel header (include) files
GCC compiler
Make Utility

How can I find out wich of them are missing?

motub 06-03-2004 08:59 AM
None of those should prevent the running of the script.... missing them might cause the script to fail once running, but you aren't even getting to run the script.

Make and gcc are installed by the distribution, and should not be missing.

You said you already have the kernel-source installed.

You might be missing the kernel-headers, but if you have the kernel-source installed, I don't know what you'd need the headers for as well.

You could check that the script is in fact marked as executable, which is the only thing left that I can think of that might be the problem, but I don't remember having to set them executable myself during previous installs.

Unfortunately, I can't check this for you myself, as Gentoo compiles and installs the drivers automatically for me, so I don't have a fglrx directory in /lib/modules. Good for me, but not helpful for you, sorry :( .

fitz9948 06-03-2004 11:33 AM
ricguitar: with both make.sh and make_install.sh simply does this to them at the command line: chmod +x make.sh and do chmod +x make_install.sh this will make them executable and now you could do ./make.sh and then do ./make_install.sh you must do the make.sh before you do make_install.sh

ricguitar 06-03-2004 12:01 PM
Thanks fitz9948, that chmod thing worked well, but now I am having another problem. When I try to exexute ./make.sh appear the following message:

Error:
XFree86 drm includes at /lib/modules/2.6.5-1.358/build/include/../drivers/char/drm do not fit this driver.
This driver is designed to only work with X4.1.0 or higher.
You can match this by getting Linux kernel 2.4.8 or higher.

But the Fedora Core 2 has the Linux Kernel 2.6.5-1.358, so I dont understand that stupid error message! Maybe is because Fedora Core 2 doesnt use Xfree86 anymore (they are using Xcore instead that is compatible with Xfree86 4.3.0), but how can I fix that?

Maybe that patch that you metioned before resolves the problem, but how I do to install it?

fitz9948 06-03-2004 12:16 PM
I think the problem is that you dont have the kernel headers. I got this same error, and also didnt know where to get the kernel headers from so you have to compile the kernel. There are guides on this board on how to do it. What I would suggest is copying the default fedora config file /usr/src/linux-2.6.5-1.358/configs/kernel-2.6.5-i686.config and use this to compile your kernel. basically copy this file into the root directory of the kernel source rename it to .config and then just do make oldconfig other then that just follow those guides on this bored and you should be good.

motub 06-03-2004 12:18 PM
Have you downloaded the ATI driver for the 4.3 version of XFree86 ? That 4.1.0 business indicates that you may have the wrong RPM.


All times are GMT -5. The time now is 04:38 PM.
Page 1 of 2 1 2
Show 50 post(s) from this thread on one page