cchtml.com - User contributions [en]

Scientific Linux

2007-11-19T17:14:59Z

207.163.116.20:

getviouorc
== Scientific Linux 5.0 ==

The ATI driver installer ati-driver-installer-8.36.5-x86.x86_64.run has the ability to build RPMs.

ati-driver-installer-8.36.5-x86.x86_64.run --listpkg

shows the packages it can build.
There is no RHEL 5 option yet, but I've read somewhere that RHEL5 is based on FC6.
Given that I tried to build

ati-driver-installer-8.36.5-x86.x86_64.run --buildpkg Fedora/FC6

and it generated the following RPMs:

ATI-fglrx-8.36.5-1.fc6.x86_64.rpm
ATI-fglrx-control-center-8.36.5-1.fc6.x86_64.rpm
ATI-fglrx-devel-8.36.5-1.fc6.x86_64.rpm
ATI-fglrx-IA32-libs-8.36.5-1.fc6.x86_64.rpm
fglrx_6_8_0-8.36.5-1.i386.rpm
kernel-module-ATI-fglrx-2.6.18-8.1.3.el5-8.36.5-1.fc6.x86_64.rpm

fglrx_6_8_0-8.36.5-1.i386.rpm is for 32-bit.

To install these RPMs run

rpm -Uvh ATI-fglrx* kernel-module-ATI-fglrx-2.6.18-8.1.3.el5-8.36.5-1.fc6.x86_64.rpm

Run

aticonfig --initial

and you could try it with:

startx

or

telinit 5

When you happy with the new driver you need to ensure that you have

id:5:initdefault:

in your /etc/inittab and reboot the box.
Please note, that SL5.0 installation did not recognise my card: ATI X1600 [Asus A6000KT laptop] so I had no X running and the default init mode was '''3''' [not '''5''']. YMMV.

I still do not know how to rebuild the kernel module for the different kernels.
By default the kernel module is being build for the current kernel [uname -r]
Today was the first security kernel upgrade revision 2.6.18-8.1.4.el5.
So after new kernel installation I repeated the same procedure and installed new kernel module with

rpm -ivh kernel-module-ATI-fglrx-2.6.18-8.1.4.el5-8.36.5-1.fc6.x86_64.rpm

{{VCT}}
[[Category:Distributions]]
[[Category:NeedsUpdating]]

Frequently Asked Questions

2007-11-19T17:14:15Z

207.163.116.20:

vinoaceldo
==Installation==
===How do I know fglrx is installed correctly?===
There are several ways to check if fglrx is loaded and running.
<br>1. Check your X.org or XFree86 log. You should see "DRI Initialization Successful."
# less /var/log/Xorg.0.log
or
# less /var/log/XFree86.0.log
2. Check glxinfo. You should see "direct" and not "indirect."
# glxinfo | grep direct
3. Check your kernel log. You should see fglrx messages near the bottom.
# dmesg
4. Check your modules. You should see fglrx loaded.
# lsmod | grep fglrx
*NOTE: [[Glxgears is not a Benchmark|glxgears]] is not a definite way of checking the installation of fglrx.

=== Is the rebooting really necessary? ===

No.

However, rebooting is the easiest method to ensure that the kernel module(s) from the old driver are unloaded and the fglrx module is loaded instead. If you don't want to reboot for some reason, you may manually shut down Xorg, unload any old "drm", "radeon" or "fglrx" modules and then start Xorg again.

==Kernel==
===Why does fglrx not work for my bleeding-edge kernel?===
The development process of the fglrx driver and the Linux kernel are not on the same level. The fglrx driver requires some special interactions with the kernel memory API and these tend to change between kernel versions.

There is also an 11-12 week cycle required to develop, validate and test each release of an ATI driver <ref>http://www.phoronix.com/scan.php?page=article&item=735&num=1</ref>. ATI will only look to support the latest kernel that is officially out (no -rc or -git releases are supported) at the time they release a driver. Example: fglrx version A comes out Monday, but kernel version B comes out Tuesday. Kernel version B is not supported by fglrx version A. (but might be able to work anyway by doing a 'modprobe -f fglrx' in a shell)

The binary part of ATI's kernel module has no explicit dependency on the Linux kernel. There are a set of source files that provide the glue to the kernel. This is where the dependency to different kernels exist. As a result, user contributed patches for newer kernels can often be found by searching [http://ati.cchtml.com Bugzilla].

==X Configuration==
===How do I configure my system to use the fglrx driver?===
*ati-xconfig
:Command line program to modify the /etc/X11/xorg.conf file.
*amdcccle
:GUI program that allows detailed configuration over the driver's controls.

==Troubleshooting==
* See [[Troubleshooting]] page.

==See Also==
*[http://ati.amd.com/products/catalyst/linux.html Official ATI Linux Driver FAQ]

==References==
<references/>

Configuring

2007-11-19T17:14:07Z

207.163.116.20:

zelnorolirol
{{VCT-on-top}}
== aticonfig ==

Since version 8.18.6 the fglrx driver includes the '''aticonfig''' tool which simplifies ''xorg.conf'' editing. Here are some useful commands this tool offers (for a complete list see [http://wiki.cchtml.com/index.php/aticonfighelp ''aticonfig --help'']).

=== Changes taking effect on startup ===
''Changes will change the config file!''

;Initial setup (creates device section using fglrx):
:<pre>sudo aticonfig --initial</pre>

;Enable Video acceleration (Xv Overlay):
:<pre>sudo aticonfig --overlay-type=Xv</pre>

;Force fglrx to use kernel's AGP driver instead of own implementation (only use when internal agpgart doesn't work):
:<pre>sudo aticonfig --internal-agp=off</pre>
*Note: Newer fglrx driver versions do not include an internal AGPGART so the kernel agpgart is used no matter what.

;Use extended desktop with two monitors (dual-head and big desktop):

Assuming you successfully completed the 'Ubuntu Gutsy Installation Guide' with two monitors connected:

:<pre>sudo aticonfig --initial=dual-head --screen-layout=right</pre>

This command will generate a dual head configuration file with the second screen located to the right of the first screen.

:<pre>sudo aticonfig --dtop=horizontal --overlay-on=1</pre>

This command will set up big desktop to horizontal and set overlay on the secondary display.

=== Changes taking effect immediately ===
''Changes will not change the config file.''

;Print information about power states.
:<pre>aticonfig --list-powerstates</pre>
Or, for us lazy folk, the shorter version is ''aticonfig --lsp''

;Set a power state to the lowest (battery friendly):
:<pre>aticonfig --set-powerstate=1</pre>
*Note: check out available power states using ''aticonfig --list-powerstates''
*Note: this option does not work when an external monitor is connected

;Print information about connected and enabled monitors:
:<pre>aticonfig --query-monitor</pre>

;Examples how to enable two monitors on the fly:
* Assume you have two monitors already setup correctly ([http://ubuntuforums.org/showthread.php?t=301941 Dual monitor support] at Ubuntuforums)
* This example enable laptop internal monitor (lvds) and external monitor (crt1)
:<pre>aticonfig --enable-monitor=lvds,crt1 --effective=now</pre>
*Note: ''aticonfig --enable-monitor=STRING,STRING'' where STRING can be one of the following set, separated by commas: none,crt1,crt2,lvds,tv,tmds1,tmds2,auto. Only 2 displays can be enabled at the same time. Any displays that are not on the list will be disabled.
*Note: check out connected and enabled monitors using ''aticonfig --query-monitor''

;Turn off the second monitor on the fly and start to use only laptop internal monitor (lvds)
:<pre>aticonfig --enable-monitor=lvds --effective=now</pre>

;Swap monitors on the fly when using big desktop mode
* Assume you have two monitors already setup correctly ([http://ubuntuforums.org/showthread.php?t=301941 Dual monitor support] at Ubuntuforums)
:<pre>aticonfig --swap-monitor --effective=now</pre>
* Note: This only works for big desktop setup. This will swap the contents on the two monitors.

=== Troubleshooting ===

Still not working? Go to the [[Troubleshooting]] page.

[[Category:NeedsUpdating]]
{{VCT}}

Category:NeedsUpdating

2007-11-19T17:12:41Z

207.163.116.20:

olorolchig
Here is your opportunity to support this site. Any of the linked pages below need updating. Please update and remove the NeedsUpdating flag.