cchtml.com - User contributions [en]

Red Hat Enterprise Linux

2012-02-28T10:56:51Z

203.157.240.13: /* Red Hat Enterprise Linux 4 Update 3 (RHEL 4.3 and CentOS 4.3) */

"Red Hat Enterprise Linux is the leading platform for open source computing. It is sold by subscription, delivers continuous value and is certified by top enterprise hardware and software vendors. From the desktop to the datacenter, Enterprise Linux couples the innovation of open source technology and the stability of a true enterprise-class platform." -redhat.com

Please note that Red Hat Enterprise Linux and Fedora Core are distantly related and are not the same product. Please see the [[Fedora]] distribution page for more details.

Another option for those wanting the stability of RHEL, there are various RHEL clones, some of them listed below:

- [http://centos.org/ CentOS] is a community effort which tracks each RHEL release and update and offers up2date and yum service. All this for free, donations encouraged.

- The [http://linux.startcom.org/ StartCom Linux] operating systems, are based on the RedHat Enterprise and Fedora source code each modified with reliability, security and efficiency in mind, to fit the tasks assigned to each flavor of StartCom Linux.

==Installation Workaround for RHEL clones==
Installation of current RPMs like fglrx_6_8_0-8.42.3-1.i386.rpm may fail on RHEL clones with this error message:

FATAL: Module fglrx not found.
/var/tmp/rpm-tmp.5182: line 807: [: =: unary operator expected

The problem is that the installation script searches for the string "Red Hat" in /etc/redhat-release. So before installing the RPM simply replace "CentOS" by "Red Hat" in /etc/redhat-release using a text editor. After the RPM has installed successfully I recommend to restore your old /etc/redhat-release. For StartCom Linux create the file /etc/redhat-release with the string "Red Hat" in it. This seems to have been fixed as of CentOS 5.1.

I am hnaivg the same problem.Happily I found that someone had the same problem. Happily only to know, because the problem is the same and I could not SOLVE it. I skiped the Media Test, than choose language and Kind of keyboard.Then it asks about the kind of installation.In my case, I choose CD/DVDI thought about Skip Media test, too. And it goes a bit more steps until this message error: The CentOS disc was not found in any of your drives. Please insert the CentOSSkip Media testChoose URL> Config TCP/IP (all default) Waiting the NetworkManager config eth0Gave and ERROR to config network interface, too.The unique option is: REPEAT.I have tried to open the CDROM driver severall times. Did not work!CentOs 6.2 (x86_64) NET INSTALL (not that BIG default iso >> this one is for HOST pourposes).Intel Core i3, 2Gb ram, 500Gb hd.It has a Linux distro called Satus (brazilian one).I want to install KVM, BUT FIRST, I need an O.S. Like VPS companies usually use CENTOS, I'd like to use the same. But I need to be honest: it's been very difficult.It is this kind of thing that make people prefer to use WINDOWS. I have tried to install CentOS for SEVERAL DAYS. If I try to install Windows, it'll install in 30min.

== Important Note as of 5/18/2009 ==
None of the above seems to work for an ATI Radeon HD4670 (512 MB) with the Dell S2409W 24" widescreen LCD on a Dell XPS 435MT (core i7-920) running under 64 bit CentOS 5.3 with the latest updates as of 5/18/2009. "Automatic" installation of the ATI Catalyst 9.4 driver seems to run smoothly, fglrxinfo detects and reports the graphics hardware, and aticonfig --initial reports that it saved a backup of xorg.conf. However, restart X11 (or reboot the PC) and what you get is an incomprehensible screen full of big squares peppered with little dots. Alt-R will reboot the PC and allow use of CD 1 to reboot linux in rescue mode, after which the driver's uninstall script works nicely. So no permanent harm seems to be done.

Here is what finally worked on this particular hardware:

First, to save time and effort, as root edit /etc/inittab and change runlevel to 3. Replace this line
<pre>id:5:initdefault:</pre>
with
<pre># id:5:initdefault:
# for tinkering with display and xorg.conf
# boots to text mode, requires startx to start X
id:3:initdefault:</pre>
Then the system will boot to multiuser with text display, and X can be started by startx.

Next, make sure that the required packages have been installed. After reading the installation instructions, I used CentOS 5.3's graphical Package Manager to install the Development Libraries, Gnome Software Development, and X Software Development. Undoubtedly this adds more than the bare minimum, but disk space is cheap and (my) time is not.

I took the path of generating and testing rpms. This made it easy to back out of any drivers that failed to work (and plenty failed)--just ^-Alt-Backspace to break out of X, then at the command line
<pre>rpm -e drivername</pre>
e.g.
<pre>rpm -e fglrx64_7_1_0</pre>
and finally make sure that /etc/X11/xorg.conf was restored to a copy of its original form.

'''Caution:''' when testing, one version (8.6) responded to startx by blanking the screen for several seconds, during which the fans in the Dell XPS 435 revved up and stayed revved up. This made me nervous as I imagined the possibility that the video card might overheat (read something about that somewhere on the WWW in connection with a different card and a different driver). I had to repeatedly press ^-Alt-Del and ^-Alt-Backspace to stop it and reboot.

Finally I discovered that the 8.8 version worked with my hardware.

'''Installing the version 8.8 driver'''

The ATI page for the 8.8 version actually placed a file called ati-driver-installer-8-7-x86.x86_64.run on my Desktop. The name suggests that it's 8.7, but I tried it anyway.

As root,
<pre>sh ./ati-driver-installer-8-7-x86.x86_64.run</pre>
brought up a panel that I used to select "Generate Distribution Specific Driver Package." I selected RedHat/RHEL5_64a (RedHat/RHEL5 for 32 bit). The driver package turned out to be an rpm called fglrx64_7_1_0-8.512-1.x86_64.rpm (fglrx_7_1_0-8.512-1.i386.rpm for 32 bit).

Then I ran
<pre>rpm -Uvh fglrx64_7_1_0-8.512-1.x86_64.rpm</pre>
which failed with an error message that indicated it needed compat-libstdc++-33. After installing that, I tried installing the fglrx... rpm again, which succeeded. Finally, I typed
<pre>aticonfig --initial</pre>
at the system prompt.

I rebooted, logged in as myself (not root), ran startx, and was relieved to see that the display was in a higher resolution mode, and ATI Catalyst Control Center now appeared in the System / Preferences and System / Administration menus.

Turns out I couldn't run ATI Catalyst Control Center as myself--had to su, then run amdcccle at the command line.

After verifying that all was well, as root I restored the boot runlevel to 5 by editing /etc/inittab again.

Did a bit of tinkering and got the following performance out of glxgears: 720 frames in 5.4 sec = 133 FPS.
Doesn't seem too impressive. fgl_glxgears causes a segmentation fault and exits. Dragging windows around the screen, I see a distinct lag between when I drag something and when it finally gets to its location. But at least I'm not looking at a 1200x800 display.

==Tips and Tricks==
If you have SELinux enabled and set to enforcing you may need to change the context of the fglrx_dri.so file for it to load properly:

chcon -t textrel_shlib_t /usr/lib/dri/fglrx_dri.so

Substitute lib with lib64 where appropriate.

Tip for Centos 5.4 x86_64 kernel 2.6.18+
Before installing the driver package it is absolutely vital to ensure that version/build number in /lib/modules/{your kernel build}/build/include/linux/utsrelease.h number is EXACTLY the same as the output of uname -r

for example
uname-r
2.6.18-164.el5
cat /lib/modules/2.6.18-164.el5/build/include/linux/utsrelease.h
#define UTS_RELEASE "2.6.18-164.'''1.15'''.el5"

fglrx.ko will NOT be built and installed properly due to the discrepancy (1.15) in utsrelease.h.

In most cases modifying utsrelease.h solves the problem

==Related Resources==
[http://ati.amd.com/support/drivers/linux/linux-radeon.html Follow link "ATI Driver Installer"]

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

Frequently Asked Questions

2011-11-08T05:12:40Z

203.157.159.2: /* Troubleshooting */

==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 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].

Note: That's why an opensource hardware driver is necessary. Hopefully, AMD will continue releasing more documentation and we will be able to code our own maintainable and free driver, thus freeing ourselves from this dependency on AMD's good will - and freeing AMD to focus on hardware.

==X Configuration==
===How do I configure my system to use the fglrx driver?===
*aticonfig
:Command line program to modify the /etc/X11/xorg.conf file.
*amdcccle
:GUI program that allows detailed configuration over the driver's controls.
*/etc/X11/xorg.conf
:X configuration file. Find the Device section for your ATI card and edit the Driver line to read
Driver "fglrx"
:Note: This is the least-preferred method. Many things can stop working.

You have the monopoly on useful informationaren't mnoopoiles illegal? ;)

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

==References==
<references/>

Gentoo Installation Guide

2008-05-07T19:31:16Z

203.157.116.14: /* Introduction */

Orginally found on the [http://gentoo-wiki.com/HOWTO_ATI_Drivers Gentoo Wiki], the GNU Free Documentation license allows me to copy/paste it here.

this post is fantastic <a href=" dcoreanal ">hentailesbian</a> %))

== Kernel Configuration ==

Get into menuconfig (cd /usr/src/your-kernel && make menuconfig) and check the following:
{{Box Code|menuconfig|<pre>
Loadable Module Support --->
[*] Enable loadable module support
[*] Module unloading

Processor type and features --->
[*] Enable VM86 support
[*] MTRR (Memory Type Range Register) support

Device Drivers --->
Character Devices --->
<M> /dev/agpgart (AGP Support)
<M> Your_AGP_Chipset_Here
[ ] Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)

Graphics support --->
[ ] Support for framebuffer devices

Kernel Hacking --->
[ ] Kernel debugging
</pre>
}}
Sync your kernel menuconfig with the selected portions posted here. (note: you can compile /dev/agpgart & your agp chipset [most likely ati-agp] into the kernel if you want.)

'''Please be aware that -mm and -rc(1,2,3,4,...) kernels often break fglrx due to unexpected changes in syntax, etc. If you want to use ati-drivers, use the stock gentoo-sources or at the very least, a STABLE 2.4 or 2.6 kernel!'''

Don't forget to compile, install, and reboot into the kernel. Directions for this are beyond the scope of this file; if you need help recompiling the kernel, [http://gentoo-wiki.com/HOWTO_Compile_a_Kernel_Manually click here].

== Grabbing a Driver Set ==

For installation it will be easier to drop out of X to a command prompt. Do this using whatever command your Window Manager uses.
I use fluxbox so it's just rightclick -> fluxbox menu -> exit. For KDE or GNOME it's probably just a matter of logging out. When all else fails, hit CTL+ALT+BACKSPACE to kill the X server ungracefully. If the X server only reboots or for some reason you've disabled this hotkey, log in as root and type '''init 3''' to bring the system run level down.

There is also the possibility to stop the xdm service by entering ''/etc/init.d/xdm stop'' as root.

Thanks to portage, installing the drivers is easy. If you have not already done it recently, start by synchronising your portage tree:

emerge --sync

Getting the latest drivers will probably mean unmasking them.

echo "x11-drivers/ati-drivers ~arch" >> /etc/portage/package.keywords
echo "x11-drivers/ati-drivers-extra ~arch" >> /etc/portage/package.keywords

Replace {{Codeline|<~arch>}} with your system architecture; it's going to be either {{Codeline|~x86}} or {{Codeline|~amd64}}, the only two CPU architectures supported by the ATI driver.

Now let's install the drivers. ati-drivers-extra is a (god-awful) control panel for the driver you probably won't use; you can leave that part out if you want, but for completeness we mention it here.

su -
emerge -av ati-drivers ati-drivers-extra

The next step is switch to the ATi OpenGL subsytem:

(#opengl-update ati)
eselect opengl set ati
(very important!)(opengl-update is deprecated)
Configure X:
First, make a standard config file.

xorgconfig

For a single screen

aticonfig --initial --input=/etc/X11/xorg.conf

For a dual head, second screen is {left|right|above|below}

aticonfig --initial=dual-head --input=/etc/X11/xorg.conf --screen-layout={left|right|above|below}

Adapt input with your path to xorg's conf file

If for some reason this command doesn't work, then try manually executing from its default location:

/opt/ati/bin/aticonfig [...]

Now, let's get back into X.

startx

Open up a command prompt and run:

fglrxinfo

If the OpenGL vendor string says "ATI Technologies," then congrats! You've got the drivers working and hardware acceleration going great. If not...read on...

== Troubleshooting ==

=== Config Files ===
By default, the driver uses the Internal AGPGART. Sometimes the internal one doesn't work, and you will have to use the one provided with the kernel. Search your xorg.conf for the line that has the option "UseInternalAGPGART." Simply change the "yes" to "no."

{{Box File|xorg.conf|
Option "UseInternalAGPGART" "no"
}}

Now simply add the modules to {{Filename|/etc/modules.autoload.d/kernel-2.x}} where x is your kernel version.

Add the following (ORDER IS VERY IMPORTANT);
{{Box File|/etc/modules.autoload.d/kernel-2.x|
agpgart
intel-agp # change intel-agp to your chipset. eg: via-agp, nvidia-agp sis-agp.
fglrx
}}

Finally, run

modules-update

Then you can reboot and everything should work. If you have are having problems, check dmesg and /var/log/Xorg.0.log for more info.

=== Blank screen or monitor turning off after startx ===

Versions of ati-drivers >= 8.16.20 have an issue with this that's easily corrected by inserting:
{{Box File|xorg.conf|
Option "ForceMonitors" "notv"
}}
in the device section of xorg.conf (discussed here: http://bugs.gentoo.org/show_bug.cgi?id=103028)

Check if you have a non-DDC monitor connected via VGA/HD15 connector. If so change your xorg.conf:
{{Box File|xorg.conf|
# Option "DesktopSetup" "0x00000000"
Option "MonitorLayout" "NONE, CRT"
Option "IgnoreEDID" "off"
Option "HSync2" "30-85"
Option "VRefresh2" "50-160"
# Option "ScreenOverlap" "0"
}}
where HSync2 and VRefresh2 are your monitor parameters.

Also, try changing the MonitorLayout option. The default is "AUTO, AUTO", which is to say X will attempt to autodetect what kind of monitor you've got on the first and second display heads. This can theoretically fail (though I have never observed it). Try changing it around a bit. For example, if you have an LCD and no secondary monitor, change the line to read:

{{Box File|xorg.conf|
Option "MonitorLayout" "TMDS, NONE"
}}

if you have a CRT, simply replace "TMDS" with "CRT".

=== Crashes on startup ===
'''If you are unable to use any 3d applications and get this error instead:'''

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!!!

'''Then you do not have tmpfs mounted on /dev/shm, which the driver requires.''' Make yourself sure you have tmpfs support compiled into kernel. It's under

File systems -->
Pseudo filesystems -->
[*] Virtual memory file system support (former shm fs)

To mount this, add to following line to {{filename|/etc/fstab}} (if it isn't there already):

{{Box File|/etc/fstab|
tmpfs /dev/shm tmpfs defaults 0 0
}}

Then just do a:
mount /dev/shm

If the drivers still crap out on you, or for example you get a black screen on X init, try going into your system BIOS and change graphics-related stuff around. Believe it or not, for me my 9800 gives a black screen on X init if I have the AGP Aperture set at anything other than 128MB. I don't know what causes this, and I don't care; I'm just relating to you how I overcame ''my'' problem ;)

Also, '''whenever you update your compiler''', you '''must''' recompile your kernel otherwise you won't be able to insert the fglrx module. Note that recompiling your kernel means you must also unmerge/emerge ati-drivers!

=== Duplicate symbol errors in X log ===
If you are unable to start X or X fails to load the fglrx driver and you have multiple symbol errors in your Xorg log, chances are that you have compiled X with the ''dlloader'' flag. This flag can not be used with the fglrx driver. To fix this problem, remove the dlloader flag by editing your /etc/portage/package.use file as follows:
{{Box File|/etc/portage/package.use|
x11-base/xorg-x11 -dlloader
}}
Now re-emerge the ''xorg-x11'' package and reinstall the fglrx driver.

=== Crashes on the exit of X.org / X won't shutdown ===
Perform the following if you can get the fglrx drivers working with hardware acceleration, but are suffering from a complete system crash when trying to quit X. You should boot into your system, login, then start on this. You don't need to boot into X, and shouldn't need to edit your xorg.conf file (as fglrx is already setup as the driver and working)

You've emerged the "stable" version of the ati-drivers, these are out of date -- remove them (emerge --unmerge ati-drivers), to add the most recent you should either add them to the keywords file (/etc/portage/package.keywords) or emerge your local ebuild (emerge /usr/portage/x11-drivers/ati-drivers/ati-drivers-8.22.5.ebuild) if you're told it requires a dependency, emerge the local e-build for that, then try again. (usually eselect-opengl is required.)
Once you have the most recent ati-drivers emerged, run (eselect opengl set ati). Now you can (startx) and hopefully quit without any problems.

=== glxinfo says "error: failed to open DRM: Operation not permitted" ===
If a check with the glxinfo fails for ordinary users though works fine for root it might be related to filepermissions of the device-file.
Here is how to solve it:

Make sure that the filepermissions on the card-device allows the video-group to read and write. The common group in gentoo with X is "video". All normal users should be part of this group. Also, the device must have permissions for this group to read and write the card-device.

Check the permissions on the card-device:

root:/#ls -lcF /dev/dri/card0

crw-rw---- 1 root root 226, 0 Oct 5 16:19 /dev/dri/card0

It can be changed with:

root:/dev/dri#chgrp video card0

Check if user is part of video:

paddlaren:~>id paddlaren

uid=1000(paddlaren) gid=1000(paddlaren)

groups=1000(paddlaren),10(wheel),11(floppy),18(audio),19(cdrom),80(cdrw),85(usb),100(users),35(games)

To add a user to the video-group:

root:~#gpasswd -a my_user video

paddlaren:~>id paddlaren

uid=1000(paddlaren) gid=1000(paddlaren)

groups=1000(paddlaren),10(wheel),11(floppy),18(audio),19(cdrom),27(video),80(cdrw),85(usb),100(users),35(games)

Logoff and on to ensure that the membership of the group is known to the system.

== See Also ==

*[http://ati.cchtml.com/ ATi Unofficial Bugzilla (occasionally monitored by ATi personnel)]
*Check out user Wedge_'s excellent ATI Radeon [http://odin.prohosting.com/wedge01/gentoo-radeon-faq.html FAQ here]

[[Category:Installation Documentation]]