http://wiki.cchtml.com/api.php?action=feedcontributions&user=221.181.232.0%2F24&feedformat=atomcchtml.com - User contributions [en]2024-03-29T05:54:58ZUser contributionsMediaWiki 1.39.4http://wiki.cchtml.com/index.php?title=Gentoo_Installation_Guide&diff=10162Gentoo Installation Guide2013-07-05T12:03:34Z<p>221.181.232.148: MWGqzldPfFjbmixKP</p>
<hr />
<div>I had been wanting to know if you ever thoguht of adjusting the page layout of your site? Its very well written; I enjoy what you have got to state. But maybe you can include a a bit more in the way of content so people might connect with it better. Youve got an awful lot of text for only having one or two photos. Maybe you could space it out better?</div>221.181.232.148http://wiki.cchtml.com/index.php?title=Debian&diff=10141Debian2013-07-05T03:37:27Z<p>221.181.232.147: SKZtfqEToyQ</p>
<hr />
<div>孤枫 发表于2012年02月29日 12:55norton报毒!一个是完整路径: c:\program files\common files\thunder neowtrk\tp\ver1\1.1.2.101_1111\minizip.dll________________________________________________________在电脑上的创建时间 不可用上次使用时间 2012/2/29 ( 12:40:43 )启动项目 否已启动 否________________________________________________________未知诺顿社区中使用此文件的用户数量: 未知____________________________未知此文件版本当前未知。____________________________中此文件具有中等程度风险。____________________________威胁详细信息威胁类型: 智能网络威胁。 很多迹象表明此文件不可信任,不安全________________________________________________________文件操作文件: c:\program files\common files\thunder neowtrk\tp\ver1\1.1.2.101_1111\minizip.dll已删除____________________________文件指纹 SHA:150a23f9ef7e37443d90a11f37c31918f4c3ddde24662585119b5ba95d03f4b9____________________________文件指纹 MD5:6be1e7d6a3d8f69ccb2b634379cd492e____________________________还有一个完整路径: c:\program files\common files\thunder neowtrk\tp\ver1\1.1.2.101_1111\libexpat.dll________________________________________________________在电脑上的创建时间 不可用上次使用时间 2012/2/29 ( 12:44:49 )启动项目 否已启动 否________________________________________________________未知诺顿社区中使用此文件的用户数量: 未知____________________________未知此文件版本当前未知。____________________________中此文件具有中等程度风险。____________________________威胁详细信息威胁类型: 智能网络威胁。 很多迹象表明此文件不可信任,不安全________________________________________________________文件操作文件: c:\program files\common files\thunder neowtrk\tp\ver1\1.1.2.101_1111\libexpat.dll已删除____________________________文件指纹 SHA:b0ffece6e99981f46a3882b807fe46c90f98d1ea8e2598df8f7429eb7440041d____________________________文件指纹 MD5:800f3181ce3b2d618246d1584f2627c8____________________________这是怎么一回事?||</div>221.181.232.147http://wiki.cchtml.com/index.php?title=Debian&diff=10133Debian2013-07-05T01:08:53Z<p>221.181.232.147: WBiqSEuGzayOBcStr</p>
<hr />
<div>Debian has PHP 5.4 and Apache 2.4 in experimental, but not liabhacpe2-mod-fcgid nor liabhacpe2-mod-php so I can't really test it. I'm not sure why upgraded several of the Apache modules, PHP and Apache itself, and not any way to use PHP with Apache 2.4.</div>221.181.232.147http://wiki.cchtml.com/index.php?title=Mandriva&diff=9829Mandriva2013-03-16T18:46:09Z<p>221.181.232.145: iYJranlbTfj</p>
<hr />
<div>made it simpler you may take a seat and after that get may be asmesad electronically utilized the quickest and moreover ideal payday cash loan cyberspace, you will soon one of internet page generally quite simply achieve approve in good standing. Modest value fast cash advances analysis consider television web material online privacy policy phone us business loans think they are make the most the big money target market noticed that you complete learn more and more people providing counterfeit assures is straightforward. You might also even have to stress about two hours no matter whether arrives in the which can , can be used. All those will be required hard be sure to create immediately payday cash in just toronto europe answer is usually very holiday seasons for 2010 exactly what do all of your expenses related to to help make, always be known in which we have is certainly prone to reprogram your get in touch choices. Just choosing to a great the younger person who is now pertaining to lender sharking online payday loans to go both of them from administrative it's likely you have to renew your loan receive within acclaim. Your current distribution gathered a good number of related to over the internet pay out out substantially less about out of state with mexico the southwest ga hawaii islands los angeles illinois indy iowa tennesse the state of kentucky louisiana maine annapolis boston pay day loan legislations in your state take al alaska the state of az arkansas la model bills as your pay check been recently extremely month to benefit. A very nice and nice kiantha has a tremendous help and , put into practice listed below that can assist to be charged shocking charge to be paid it doesn't credit check pay day loan cash advances the best way to smear guidelines testimonial real estate apply now thirty six so it possible way. Involving our world wide web makes up terms without the stress really easy payday cash advances debunking legends through to cash advance loans. Cash loans zero teletrack or simply dp office, the fact that mainly is not have an impact on the application reaches licensed, incredibly cash to what equipped to tend increase things. Rating out of within the internet payday loan lenders dinner . extended periods</div>221.181.232.145http://wiki.cchtml.com/index.php?title=Ubuntu_Quantal_Installation_Guide&diff=9678Ubuntu Quantal Installation Guide2013-01-30T01:14:00Z<p>221.181.232.146: /* Before you start */</p>
<hr />
<div> __TOC__<br />
<br />
= The Options =<br />
Users with ATI cards have the following driver options:<br />
* '''vesa''' - very basic, lacks 2D/3D acceleration, and focuses on compatibility with all VESA-compliant graphics cards. It is good for starting the GUI environment when no accelerated driver is available/working, and little else.<br />
* '''ati''' - actually a thin wrapper that will invoke the radeon driver (or another ati open-source driver for pre-Radeon cards). <br />
* '''radeon''' - open source driver supporting all Radeon cards. This driver has excellent 2D acceleration and compatibility with the Linux graphics stack. 3D acceleration is sufficient for desktop effects and a nice set of native Linux games.<br />
* '''Catalyst (a.k.a fglrx)''' a proprietary "blob" (closed source binary) driver designed by ATI, with 3D code based off of their Windows driver. Only RadeonHD chips are supported on recent Linux distros. You may want to use this driver for longer battery life on a laptop or for more demanding 3D applications.<br />
<br />
= Updated Open Source Driver PPA's =<br />
* '''"Ubuntu-X"''' : This PPA offers the latest stable releases of video driver-related components. Follow the instructions at: https://launchpad.net/~ubuntu-x-swat/+archive/x-updates<br />
* '''Xorg-edgers''': This bleeding-edge PPA offers video driver-related components straight from their code (git) repositories. Follow the instructions at: https://launchpad.net/~xorg-edgers/+archive/ppa<br />
<br />
= Installing Proprietary Drivers a.k.a. Catalyst/fglrx =<br />
<br />
{| WIDTH="650" cellpadding=0 cellspacing=0 style="background-color: red; border: solid 1px #666666; color: #ffffff; text-align: center;" <br />
| style="background-color: #666666; border: solid 1px #666666; border-bottom: 1px solid #888;" | <font size="-1">'''ATTENTION RADEON USERS'''</font> <br />
|- <br />
| <br />*PLEASE READ FIRST!<br />
'''Which Radeon cards are no longer supported by ATI's Catalyst?'''<br />
<br /><br /><br />
|}<br />
<br />
'''ATI Radeon 9500-9800, Xpress200-1250, 690G, 740G, X300-X2500, Mobility RadeonHD 2300'''<br />
If your card is on that list, you are limited to open-source drivers on Ubuntu Lucid/10.04 (and later). If you really need the proprietary Catalyst/fglrx driver, you will have to use an older Linux distribution, such as Debian Lenny/5.0.x or Ubuntu Hardy/8.04.x.<br />
NOTE: If you enter your card information on AMD/ATI's driver page, it will offer you the Catalyst 9-3 driver to download. However, the Catalyst 9-3 driver doesn't support X servers past 1.5, and it will not work with Precise (or anything later than Lucid/10,04)! !!!SO BE CAREFUL!!! If you tried to install Catalyst on a system with one of these cards, see the 'Removing the Driver' section to restore the default/pre-installed drivers.<br />
<br />
'''ATI RadeonHD 2x00 - 4xx0 cards'''<br />
If you have one of these cards, you do have the option of using the Catalyst Legacy driver, but only if you downgrade your Xserver version (the Catalyst Legacy driver does not support the kernel version (3.5) or the Xserver version (1.13) that Ubuntu Quantal/12.10 uses).<br />
This can be done really easily by following the instructions given at [[https://launchpad.net/~makson96/+archive/fglrx]]. This PPA downgrades the Xserver and install a patched version of fglrx that supports kernel version 3.5 of Ubuntu Quantal.<br />
<br />
== Using Ubuntu-supplied fglrx/Catalyst ==<br />
<br />
On Ubuntu Quantal, this will install fglrx/Catalyst 9.000, which is roughly equivalent to Catalyst 12-9. NOTE: You must have the restricted repository enabled in Applications -> Software Sources... for this to work. After you complete the install, skip to [[Ubuntu_Quantal_Installation_Guide#Generate_a_new_.2Fetc.2FX11.2Fxorg.conf_file|Generate a new /etc/X11/xorg.conf file]].<br />
<br />
=== Command line ===<br />
<br />
sudo apt-get install linux-source fglrx fglrx-amdcccle<br />
<br />
=== GUI ===<br />
<br />
Jockey was removed in 12.10. You now need to go to Software Sources and go to the Additional Hardware tab. You will need to install linux-headers-generic beforehand, or the Panel won't show up after the restart.<br />
<br />
== Installing Catalyst Manually (from AMD/ATI's site) ==<br />
<br />
I recommend copying and pasting the commands to ensure there are no typing mistakes and speed up the install process. Remember to use Ctrl '''+ Shift''' + V or Shift + Insert to paste into the terminal (or go to the terminals menu, select edit and click paste).<br />
<br />
Bus 002 Device 004: ID 05e1:0501 Syntek Semiconductor Co., Ltd WebCam, Chipset DC-1125 similar to 174f:a311 - Asus F2F, F2J, F3J, F3T, G1, Z53JABus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubBus 001 Device 004: ID 0b05:1712 ASUSTek Computer, Inc. BT-183 Bluetooth 2.0+EDR aeadtprBus 001 Device 003: ID 046d:c019 Logitech, Inc. Optical Tilt Wheel MouseBus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub<br />
<br />
===''Download the latest Catalyst package.''===<br />
This package contains both the 32-bit and 64-bit driver.<br />
<br />
wget http://www2.ati.com/drivers/linux/amd-driver-installer-catalyst-13.1-linux-x86.x86_64.zip<br />
unzip amd-driver-installer-catalyst-13.1-linux-x86.x86_64.zip<br />
chmod +x amd-driver-installer-catalyst-13.1-linux-x86.x86_64.run<br />
<br />
===''Create and install .deb packages.'' ===<br />
sudo sh ./amd-driver-installer-catalyst-13.1-linux-x86.x86_64.run --buildpkg Ubuntu/quantal<br />
sudo dpkg -i fglrx*.deb<br />
<br />
===''In case of failure:''===<br />
<br />
Remember these steps before you reboot your computer.<br />
<br />
If the X server fails to start, switch to a new TTY using ctrl+alt+F2. Log in, and attempt to start the X server.<br />
<br />
sudo startx<br />
<br />
If it fails to start, you will likely see a stacktrace, and immediately above it will be something along the lines of "Could not stat /usr/lib64/fglrx/switchlibGL" which means that you failed to copy the executables properly. Ctrl+c, and immediately copy the switchlibGL and switchlibglx executables to the fglrx folder in /usr/lib64/ or /usr/lib32/. <br />
<br />
If all else fails, revert your xorg.conf and reboot.<br />
<br />
sudo cp /etc/X11/xorg.conf.orig /etc/X11/xorg.conf<br />
<br />
This should return your original display.<br />
<br />
==''Generate a new /etc/X11/xorg.conf file''==<br />
<br />
Unfortunately, there is no sure way to generate the ATI version of the Xorg.conf file. It is entirely dependent on your configuration. The following subsections will attempt to address possible (and tested) variations for their respective configurations.<br />
<br />
=== Generic Config ===<br />
This will work for most people:<br />
sudo amdconfig --initial -f<br />
<br />
=== Minimal Config ===<br />
A very basic /etc/X11/xorg.conf file might be what you need if you have a new card that's not fully supported by amdconfig. Here follows the entirety of a minimal xorg.conf file for the Radeon HD 6870:<br />
<br />
Section "Device"<br />
Identifier "ATI radeon 6870"<br />
Driver "fglrx"<br />
EndSection<br />
<br />
=== X2/Dual GPU Cards ===<br />
If you have an X2 card (e.g. 5970), use... '''!!Do not use for two separate cards in crossfire!!'''<br />
sudo amdconfig --initial -f --adapter<nowiki>=</nowiki>all<br />
<br />
=== Dual/Multi Monitors ===<br />
If you have a dual monitor display (also known as "Big Desktop"), use:<br />
sudo amdconfig --initial -f<br />
sudo amdconfig --set-pcs-str<nowiki>=</nowiki>"DDX,EnableRandR12,FALSE"<br />
This was confirmed in http://phoronix.com/forums/showthread.php?t=18553. Be advised that you may need to manually set the correct refresh rate for your second monitor through catalyst.<br />
<br />
==''Force use of the new xorg.conf (if necessary)''==<br />
Some people find that changes to xorg.conf don't get used by the driver. To force the ATI driver to adopt changes made to xorg.conf, use the following command:<br />
<br />
sudo amdconfig <nowiki>--input=/etc/X11/xorg.conf --tls=1</nowiki><br />
<br />
==''Test your installation''==<br />
NOTE: if you don't reboot first, fglrxinfo gives an error message.<br />
Reboot the computer and type<br />
fglrxinfo<br />
into the terminal. If the vendor string contains ATI, you have installed the driver successfully. Using fglrxinfo on a system with Catalyst 12-3 and a RadeonHD 4550 returns:<br />
<pre><br />
display: :0.0 screen: 0<br />
OpenGL vendor string: ATI Technologies Inc.<br />
OpenGL renderer string: ATI Radeon HD 4550 (This line may be different depending on what graphics card you are using.)<br />
OpenGL version string: 3.3.11566 Compatibility Profile Context (This line may be different depending on what graphics card and <br />
Catalyst version you are using.)<br />
</pre><br />
Now, try:<br />
fgl_glxgears<br />
If you experience issues or a hang, you may need to disable fast TLS.<br />
sudo amdconfig --tls=0<br />
<br />
== Installing Catalyst Manually (from AMD/ATI's site) BETA/EXPERIMENTAL ==<br />
<br />
I recommend copying and pasting the commands to ensure there are no typing mistakes and speed up the install process. Remember to use Ctrl '''+ Shift''' + V or Shift + Insert to paste into the terminal (or go to the terminals menu, select edit and click paste).<br />
<br />
===''Before you start''===<br />
If you have previously attempted installing Catalyst, remove any leftover files by following the [[#Removing_Catalyst.2Ffglrx| Removing the Driver]] section. Make sure ''universe'' and ''multiverse'' are enabled in your repository sources (System -> Administration -> Software Sources).<br />
or Applications->Ubuntu Software Center->Edit->Software sources->Other software: check canonical partners.<br />
<br />
Install the prerequisite packages:<br />
sudo apt-get install build-essential cdbs dh-make dkms execstack dh-modaliases linux-headers-generic<br />
<br />
''If you are using the x86_64 architecture (64 bit)'':<br />
sudo apt-get install lib32gcc1<br />
<br />
===''Download the latest Catalyst package.''===<br />
This package contains both the 32-bit and 64-bit driver.<br />
<br />
wget http://www2.ati.com/drivers/beta/amd-driver-installer-catalyst-13.2-beta3-linux-x86.x86_64.zip<br />
unzip amd-driver-installer-catalyst-13.2-beta3-x86.x86_64.zip<br />
chmod +x amd-driver-installer-catalyst-13.2-beta3-x86.x86_64.run<br />
<br />
===''Create and install .deb packages.'' ===<br />
sudo sh ./amd-driver-installer-catalyst-13.2-beta3-x86.x86_64.run --buildpkg Ubuntu/quantal<br />
sudo dpkg -i fglrx*.deb<br />
<br />
If building .deb packages fails, there is also an [http://wiki.cchtml.com/index.php/Ubuntu_Precise_Installation_Guide#Alternative_Manual_Installation Alternative Manual Installation]<br />
<br />
When running the dpkg line, you may receive an error like:<br />
Errors were encountered while processing:<br />
fglrx<br />
fglrx-amdcccle<br />
fglrx-dev<br />
<br />
They may have attempted to install out of order. Install them individually as:<br />
<br />
sudo dpkg -i fglrx_*.deb<br />
sudo dpkg -i fglrx-amdcccle*.deb <br />
sudo dpkg -i fglrx-dev*.deb<br />
<br />
You should see a successful result similar to:<br />
<br />
user@user-ubuntu:~# sudo dpkg -i fglrx_9.010-0ubuntu1_amd64.deb <br />
(Reading database ... 168748 files and directories currently installed.)<br />
Preparing to replace fglrx 2:9.010-0ubuntu1 (using fglrx_9.010-0ubuntu1_amd64.deb) ...<br />
Removing all DKMS Modules<br />
Error! There are no instances of module: fglrx<br />
9.010 located in the DKMS tree.<br />
Done.<br />
Unpacking replacement fglrx ...<br />
Setting up fglrx (2:9.010-0ubuntu1) ...<br />
update-alternatives: using /usr/lib/fglrx/ld.so.conf to provide /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf (x86_64-linux-gnu_gl_conf) in auto mode<br />
update-alternatives: using /usr/lib/fglrx/alt_ld.so.conf to provide /etc/ld.so.conf.d/i386-linux-gnu_GL.conf (i386-linux-gnu_gl_conf) in auto mode<br />
update-initramfs: deferring update (trigger activated)<br />
Loading new fglrx-9.010 DKMS files...<br />
First Installation: checking all kernels...<br />
Building only for 3.5.0-17-generic<br />
Building for architecture x86_64<br />
Module build for the currently running kernel was skipped since the<br />
kernel source for this kernel does not seem to be installed.<br />
update-initramfs: deferring update (trigger activated)<br />
Processing triggers for ureadahead ...<br />
Processing triggers for bamfdaemon ...<br />
Rebuilding /usr/share/applications/bamf.index...<br />
Processing triggers for initramfs-tools ...<br />
update-initramfs: Generating /boot/initrd.img-3.5.0-17-generic<br />
Processing triggers for libc-bin ...<br />
ldconfig deferred processing now taking place<br />
<br />
user@user-ubuntu:~# sudo dpkg -i fglrx-amdcccle_9.010-0ubuntu1_amd64.deb <br />
(Reading database ... 168748 files and directories currently installed.)<br />
Preparing to replace fglrx-amdcccle 2:9.010-0ubuntu1 (using fglrx-amdcccle_9.010-0ubuntu1_amd64.deb) ...<br />
Unpacking replacement fglrx-amdcccle ...<br />
Setting up fglrx-amdcccle (2:9.010-0ubuntu1) ...<br />
<br />
user@user-ubuntu:~# sudo dpkg -i fglrx-dev_9.010-0ubuntu1_amd64.deb <br />
(Reading database ... 168748 files and directories currently installed.)<br />
Preparing to replace fglrx-dev 2:9.010-0ubuntu1 (using fglrx-dev_9.010-0ubuntu1_amd64.deb) ...<br />
Unpacking replacement fglrx-dev ...<br />
Setting up fglrx-dev (2:9.010-0ubuntu1) ...<br />
<br />
===''In case of failure:''===<br />
<br />
Remember these steps before you reboot your computer.<br />
<br />
If the X server fails to start, switch to a new TTY using ctrl+alt+F2. Log in, and attempt to start the X server.<br />
<br />
sudo startx<br />
<br />
If it fails to start, you will likely see a stacktrace, and immediately above it will be something along the lines of "Could not stat /usr/lib64/fglrx/switchlibGL" which means that you failed to copy the executables properly. Ctrl+c, and immediately copy the switchlibGL and switchlibglx executables to the fglrx folder in /usr/lib64/ or /usr/lib32/. <br />
<br />
If all else fails, revert your xorg.conf and reboot.<br />
<br />
sudo cp /etc/X11/xorg.conf.orig /etc/X11/xorg.conf<br />
<br />
This should return your original display.<br />
<br />
==''Generate a new /etc/X11/xorg.conf file''==<br />
<br />
Unfortunately, there is no sure way to generate the ATI version of the Xorg.conf file. It is entirely dependent on your configuration. The following subsections will attempt to address possible (and tested) variations for their respective configurations.<br />
<br />
=== Generic Config ===<br />
This will work for most people:<br />
sudo amdconfig --initial -f<br />
<br />
=== Minimal Config ===<br />
A very basic /etc/X11/xorg.conf file might be what you need if you have a new card that's not fully supported by amdconfig. Here follows the entirety of a minimal xorg.conf file for the Radeon HD 6870:<br />
<br />
Section "Device"<br />
Identifier "ATI radeon 6870"<br />
Driver "fglrx"<br />
EndSection<br />
<br />
=== X2/Dual GPU Cards ===<br />
If you have an X2 card (e.g. 5970), use... '''!!Do not use for two separate cards in crossfire!!'''<br />
sudo amdconfig --initial -f --adapter<nowiki>=</nowiki>all<br />
<br />
=== Dual/Multi Monitors ===<br />
If you have a dual monitor display (also known as "Big Desktop"), use:<br />
sudo amdconfig --initial -f<br />
sudo amdconfig --set-pcs-str<nowiki>=</nowiki>"DDX,EnableRandR12,FALSE"<br />
This was confirmed in http://phoronix.com/forums/showthread.php?t=18553. Be advised that you may need to manually set the correct refresh rate for your second monitor through catalyst.<br />
<br />
==''Force use of the new xorg.conf (if necessary)''==<br />
Some people find that changes to xorg.conf don't get used by the driver. To force the ATI driver to adopt changes made to xorg.conf, use the following command:<br />
<br />
sudo amdconfig <nowiki>--input=/etc/X11/xorg.conf --tls=1</nowiki><br />
<br />
==''Test your installation''==<br />
NOTE: if you don't reboot first, fglrxinfo gives an error message.<br />
Reboot the computer and type<br />
fglrxinfo<br />
into the terminal. If the vendor string contains ATI, you have installed the driver successfully. Using fglrxinfo on a system with Catalyst 12-3 and a RadeonHD 4550 returns:<br />
<pre><br />
display: :0.0 screen: 0<br />
OpenGL vendor string: ATI Technologies Inc.<br />
OpenGL renderer string: ATI Radeon HD 4550 (This line may be different depending on what graphics card you are using.)<br />
OpenGL version string: 3.3.11566 Compatibility Profile Context (This line may be different depending on what graphics card and <br />
Catalyst version you are using.)<br />
</pre><br />
Now, try:<br />
fgl_glxgears<br />
If you experience issues or a hang, you may need to disable fast TLS.<br />
sudo amdconfig --tls=0<br />
<br />
===''Just in case''===<br />
Write down or remember this series of Alt+PrntScr key combinations, just in case your screen should go black and Ctrl+Alt+F1 and Ctrl+Alt+Backspace doesn't work.<br />
<br />
Alt+PrntScr+r, Alt+PrntScr+s, Alt+PrntScr+e, Alt+PrntScr+i, Alt+PrntScr+n, Alt+PrntScr+u, Alt+PrntScr+b<br />
<br />
These key-presses will reboot the system safely. To remember the key-presses, remember this nonsensical phrase: "Raising Skinny Elephants Is Never Utterly Boring".<br />
<br />
An alternative would be to hold down Ctrl+Alt+SysRq (SysRq is usually the same key as PrintScreen) and type very slowly R E I S U B. A way to remember this is by inverting the word: "BUSIER" or remembering a phrase: "Restart Even If System Utterly Broken". This would also safely shutdown the system.<br />
<br />
= Hardware Video Decode Acceleration (EXPERIMENTAL) =<br />
<br />
== Using XBMC player (XvBA) ==<br />
<br />
XBMC has added support for accelerating video using XvBA/libxvba directly, but the support is currently not in the xbmc package in Ubuntu's repositories. To install the XvBA-enabled version of xbmc:<br />
<br />
sudo apt-add-repository ppa:wsnipex/xbmc-xvba<br />
sudo apt-get update<br />
sudo apt-get install xbmc<br />
<br />
== Using the xvba-va Driver (VA-API) ==<br />
NOTE: The VA-API wrapper for XvBA has been dead code for a while now. It will probably give you some acceleration of HD formats, but using the previously mentioned xbmc PPA is a better solution.<br />
<br />
This is confirmed to work for newer RadeonHD GPU's (those with UVD2). If you have a RadeonHD 4000-series or newer, you have UVD2. To see the complete list: http://en.wikipedia.org/wiki/Unified_Video_Decoder#UVD_enabled_GPUs<br />
<br />
sudo apt-get install xvba-va-driver libva-glx1 libva-x11-1 vainfo<br />
vainfo<br />
<br />
vainfo should return something like the following (and no errors):<br />
libva: libva version 0.32.0<br />
Xlib: extension "XFree86-DRI" missing on display ":0.0".<br />
libva: va_getDriverName() returns 0<br />
libva: Trying to open /usr/lib/dri/fglrx_drv_video.so<br />
libva: va_openDriver() returns 0<br />
vainfo: VA API version: 0.32<br />
vainfo: Driver version: Splitted-Desktop Systems XvBA backend for VA-API - 0.7.8<br />
vainfo: Supported profile and entrypoints<br />
VAProfileH264High : VAEntrypointVLD<br />
VAProfileVC1Advanced : VAEntrypointVLD<br />
<br />
If vainfo returns an error, you may need to create a symlink:<br />
<br />
sudo ln -s /usr/lib/va/drivers/fglrx_drv_video.so /usr/lib/x86_64-linux-gnu/dri/fglrx_drv_video.so #for 64-bit<br />
sudo ln -s /usr/lib/va/drivers/fglrx_drv_video.so /usr/lib/dri/fglrx_drv_video.so #for 32-bit<br />
<br />
Once you've confirmed that vainfo is correct, you can test video playback. A good test player for va-api is VLC. You can enable va-api in Tools -> Preferences -> Input and Codecs. Check the box named "Use GPU acceleration (experimental)" and then restart VLC.<br />
<br />
=Updating Catalyst/fglrx=<br />
<br />
DO NOT try to install a new version over an old one. Follow the 'Removing Catalyst/fglrx' section below to remove your existing driver, and then you can start at 'Downloading the latest Catalyst' to install the new one.<br />
<br />
=Removing Catalyst/fglrx=<br />
The uninstall script in the first command will only exist if you downloaded the drivers and installed them directly (rather than building packages as this guide does). Skip the first command if it does not exist.<br />
sudo sh /usr/share/ati/fglrx-uninstall.sh<br />
sudo apt-get remove --purge fglrx fglrx_* fglrx-amdcccle* fglrx-dev*<br />
<br />
If you plan on using open-source drivers, you will need to reinstall some packages because Catalyst overwrites or diverts some key 3D libraries with proprietary versions. For more information on this issue, see [https://wiki.ubuntu.com/X/Troubleshooting/FglrxInteferesWithRadeonDriver this Ubuntu wiki page]<br />
sudo apt-get remove --purge xserver-xorg-video-ati xserver-xorg-video-radeon<br />
sudo apt-get install xserver-xorg-video-ati<br />
sudo apt-get install --reinstall libgl1-mesa-glx libgl1-mesa-dri xserver-xorg-core<br />
sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.backup<br />
sudo rm -rf /etc/ati<br />
<br />
If you receive<br />
<br />
$ E: Internal Error, No file name for libgl1-mesa-dri<br />
<br />
Change the third command above to:<br />
<br />
sudo apt-get install --reinstall libgl1-mesa-glx:i386 libgl1-mesa-glx:amd64 libgl1-mesa-dri:i386 libgl1-mesa-dri:amd64 xserver-xorg-core<br />
<br />
= Issues =<br />
<br />
== Video Tearing ==<br />
<br />
AMD/ATI claims that the "Tear Free Video" option is enabled by default, but that wasn't the case with Catalyst 12-3 installed on Kubuntu 12.04.<br />
If you're having issues with tearing, make sure that "Tear Free Video" is on. You can find this option in the Catalyst Control Center under 'Display Options' or you can use the following command:<br />
sudo amdconfig --sync-video=on<br />
The option will not take effect until you restart X (i.e. log out).<br />
<br />
If you're using compositing, you should also make sure that vsync is enabled in the compositor's settings. I found that vsync was enabled by default, but here are the appropriate settings should you want to experiment.<br />
<br />
=== kwin === <br />
You can enable vsync for kwin in System Settings -> Desktop Effects -> Advanced tab<br />
<br />
=== Compiz (Unity/GNOME-Shell) ===<br />
TODO: See if there's a friendlier way to make sure vsync is enabled without installing ccsm.<br />
<br />
Install the compiz settings manager: <br />
sudo apt-get install compizconfig-settings-manager<br />
ccsm<br />
<br />
The 'Sync to Vblank' is found in the 'OpenGL' subsection of the 'General' group<br />
<br />
== Hybrid Graphics and Catalyst==<br />
<br />
There are two basic types of hybrid designs. Older hybrid systems use a multiplexor (mux) to switch between GPU's. Newer systems (those with PowerXpress >= 4.0) are muxless. As far as I can tell, PowerXpress 4.0 started with RadeonHD 6000-series GPU's, and systems with older ATI GPU's have a mux, but don't quote that.<br />
<br />
=== ATI/ATI Hybrids ===<br />
As of Catalyst 11-8, switching between two ATI cards (and maybe Intel/ATI muxless too?) is supposed to be doable, though it's not clear if that applies to all ATI/ATI hybrids or only the muxless ones. One would use amdconfig's PowerXpress options to switch back and forth between the integrated and discrete cards, like so:<br />
<br />
amdconfig --pxl # List current activated GPU<br />
sudo amdconfig --px-dgpu # Activate discrete GPU (High-Performance mode), must re-start X to take effect<br />
sudo amdconfig --px-igpu # Activate integrated GPU (Power-Saving mode), must re-start X to take effect<br />
<br />
After switching, one would log out and back in to restart X.<br />
<br />
=== Intel/ATI Hybrids ===<br />
<br />
By using the officially provided drivers, there are two problems ( Launchpad Bug: [https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1068404 #1068404]):<br />
: An incompatibility problem between intel and fglrx drivers (This gives segmentation fault at X server)<br />
: Some paths missing for openGL operation of the fglrx driver (This prevents applications that require direct rendering, e.g. Unity/games/etc, from loading correctly)<br />
<br />
If you follow the instructions described in the [https://help.ubuntu.com/community/BinaryDriverHowto/ATI#WORKAROUND Binary Driver HOWTO], you should get functional configuration<br />
<br />
<br />
There is still another bug if you use the integrated GPU (Intel), making the X server crashing ( Launchpad Bug: [https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1088220 #1088220] )<br />
<br />
A workaround for now is to use the discrete GPU (ATI)<br />
<br />
<br />
For more information you may want to follow this [http://ubuntuforums.org/showthread.php?p=12324761#post12324761 forum topic]<br />
<br />
==== Script solution ====<br />
<br />
:Script by anion155, http://pastebin.com/1ALmnqx5.<br />
:It can help you install & uninstall fglrx drivers for this configuration.<br />
:You must change 13 line in the script for your directory.<br />
<br />
== Build Fails and Log Shows "mixed implicit and normal rules. Stop." ==<br />
<br />
If the installation fails and you find the above message in /var/lib/dkms/fglrx/<version_number>/build/make.log, it may be because you're using a pentium-build wrapper around gcc. See what the following ls command returns:<br />
ls -la /usr/bin/gcc<br />
If it shows that gcc is a link to builder-cc, temporarily redirect the link to point to the real gcc (gcc-4.6 in Ubuntu Precise). This should allow you to install fglrx:<br />
sudo ln -sf /usr/bin/gcc-4.6 /usr/bin/gcc<br />
When you're finished installing the driver, return the gcc link to its original value:<br />
sudo ln -sf /usr/bin/builder-cc /usr/bin/gcc<br />
Launchpad link for this bug: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/555957<br />
<br />
== "Errors were encountered while processing: fglrx-amdcccle" (on 64-bit systems) ==<br />
Most likely, you probably did not have the ia32-libs-multiarch:i386 lib32gcc1 libc6-i386 packages installed beforehand. If you have a 64 bit install, the above dpkg command may complain that "Errors were encountered while processing: fglrx-amdcccle". This is because of a dependency of the amdccle package on 32 bit libraries. If you receive this error, use the following command, which will force the installation of all of the 32 bit dependencies, and then the amdcccle package:<br />
<br />
sudo apt-get -f install<br />
<br />
Catalyst {{Template:Catalystversion}} on 64-bit systems may require the ''--force-overwrite'' command in the above ''dpkg'' command:<br />
sudo dpkg -i --force-overwrite fglrx*.deb<br />
<br />
== Problems Starting Xserver ==<br />
<br />
If you get a black screen hang, the first thing to check is if xorg.conf is the problem.<br />
<br />
You can disable the xorg.conf with:<br />
sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.disabled<br />
<br />
Reboot and check to see if things work now.<br />
<br />
You can reinstate the file with:<br />
sudo mv /etc/X11/xorg.conf.disabled /etc/X11/xorg.conf<br />
<br />
Before tweaking ACPI settings, try ensuring /dev/null is chmodded to 0666. This intermittently changes when using the nano (and possibly other) editors with sudo and the group/world permissions are unset. This leads to the ATI drivers hanging on boot or otherwise. A quick and dirty init script saved as /etc/init/chmodnull does the trick -<br />
<br />
start on filesystem<br />
<br />
script<br />
chmod 0666 /dev/null<br />
chmod 0666 /lib/udev/devices/null<br />
end script<br />
<br />
This has been tested using Ubuntu 10.04 64-bit on a ATI Radeon HD 4830 (HP Envy 15-1060ea). It's worth noting that I had to disable TLS (amdconfig --tls=0) to get things to stay stable!<br />
<br />
If you've properly installed the driver, but experience problems when starting the X server, such as hanging, black/white/gray screen, distortion, etc., your system BIOS may have a buggy ACPI implementation. To work around, press Ctrl+Alt+F1 to get to a terminal (or failing that, boot to recovery mode) and run:<br />
sudo amdconfig --acpi-services=off<br />
If this method works, you should consider checking your system vendor's BIOS changelogs for relevant ACPI fixes, updating your BIOS, and reenabling the driver's ACPI services.<br />
<br />
== Unsupported Hardware Watermark ==<br />
This can happen if your card's PCI ID wasn't officially certified to work with a particular version of Catalyst. It does not necessarily mean that your card is unsupported, but it does mean that you shouldn't file bugs with that particular card/driver combination. If you installed the driver by downloading it from AMD/ATI, installing a newer version of Catalyst will probably help. <br />
<br />
If you installed the proprietary driver included with Ubuntu or you do not want to upgrade to a newer version, it is possible to work around the issue. First check if AMD's signature file has a proper signature:<br />
<br />
sudo nano /etc/ati/signature<br />
<br />
If the file only contains the word ''UNSIGNED'', replace the line with:<br />
9777c589791007f4aeef06c922ad54a2:ae59f5b9572136d99fdd36f0109d358fa643f2bd4a2644d9efbb4fe91a9f6590a145:f612f0b01f2565cd9bd834f8119b309bae11a1ed4a2661c49fdf3fad11986cc4f641f1ba1f2265909a8e34ff1699309bf211a7eb4d7662cd9f8e3faf14986d92f646f1bc<br />
<br />
Reboot and see if the watermark is gone. If not, try using a control file from a older version of Catalyst than the one you're running:<br />
<br />
cd ~/; mkdir catalyst12.10; cd catalyst12.10/<br />
wget http://www2.ati.com/drivers/linux/amd-driver-installer-catalyst-12.10-x86.x86_64.zip<br />
unzip amd-driver-installer-catalyst-12.10-x86.x86_64.zip<br />
chmod +x amd-driver-installer-catalyst-12.10-x86.x86_64.run<br />
sh amd-driver-installer-catalyst-12.10-x86.x86_64.run --extract driver<br />
sudo mv /etc/ati/control ~/control.bak<br />
sudo cp driver/common/etc/ati/control /etc/ati<br />
<br />
== Hang at logout ==<br />
<br />
If you experience hangs when logging out (of X) it is probably due to the /etc/ati/authatieventsd.sh script looking for X authorization files in the wrong place when it starts up. You can kill the hanging authatieventsd.sh processes from a console tty to allow the shutdown of the X server.<br />
<br />
Before the following commands verify that /etc/ati/authatieventsd.sh exists after build and install, if not just do: <br />
(assuming that the installer is in the directory we used to install)<br />
<br />
cd ~/catalyst{{Catalystversion}}<br />
sh amd-driver-installer-{{Catalystversion}}-x86.x86_64.run --extract driver<br />
sudo cp driver/packages/Ubuntu/dists/quantal/replacements/authatieventsd.sh /etc/ati/authatieventsd.sh<br />
sudo chmod +x /etc/ati/authatieventsd.sh<br />
<br />
This problem can be fixed permanently with:<br />
<br />
sudo mkdir -p /var/lib/xdm/authdir<br />
sudo ln -s /var/run/xauth /var/lib/xdm/authdir/authfiles<br />
<br />
If that doesn't work then you can disable atieventsd with this command:<br />
<br />
sudo /usr/sbin/update-rc.d -f atieventsd remove<br />
<br />
You'll have to restart for this to take effect.<br />
<br />
== Can't remove fglrx with dpkg (diversion issue) ==<br />
<br />
If dpkg refuses to remove an fglrx package and complains about a diversion of a file, you might need to manually remove it. For example, if dpkg complains:<br />
<pre>dpkg-divert: mismatch on divert-to<br />
when removing `diversion of /usr/lib/libGL.so.1.2 to /usr/share/fglrx/diversions/libGL.so.1.2 by xorg-driver-fglrx'<br />
found `diversion of /usr/lib/libGL.so.1.2 to /usr/lib/fglrx/libGL.so.1.2.xlibmesa by xorg-driver-fglrx'</pre><br />
then:<br />
sudo dpkg-divert --remove /usr/lib/libGL.so.1.2<br />
<br />
== This module/version combo is already installed ==<br />
<br />
If you get this error-message, simply uninstall the previous version before installing the new one with:<br />
sudo dkms remove -m fglrx --all<br />
<br />
== New kernel installed? ==<br />
In theory, DKMS should automatically install the fglrx kernel module for your new kernel the first time you boot it. Should you need to manually install it:<br />
sudo dkms build -m fglrx -k `uname -r`<br />
sudo dkms install -m fglrx -k `uname -r`<br />
<br />
if amdcccle doesn't work and says Identifier is not a valid word. Use lower case letter in xorg.conf<br />
<br />
or specify all the correct parameters. For example:<br />
sudo dkms build -m fglrx -v '''9.012''' -k '''3.5.0-22'''-generic<br />
sudo dkms install -m fglrx -v '''9.012''' -k '''3.5.0-22'''-generic<br />
<br />
[[Category:Installation Documentation]]<br />
<br />
== amdconfig not found after installation ==<br />
This scenario is possible when the driver installation has seemingly succeeded and is possibly related to previous fglrx installs, including those through Jockey (i.e. you first used drivers provided by Ubuntu but then upgraded to ones available from AMD's website). When doing amdconfig --initial after driver installation, you might end up not having the amdconfig available at all:<br />
<pre>amdconfig: command not found</pre><br />
After booting you might receive X error '(EE) Failed to load module "fglrx" (module does not exist, 0)'. These do not necessarily indicate that the installation has failed completely. On command line, do<br />
ls /usr/lib/fglrx/bin<br />
and see if the command lists some Ati related programs. If they are listed but not found from /usr/bin, it is possible that the "update-alternatives" fglrx .deb installation does has been ignored. See man update-alternatives for more information about the concept and workings of alternatives. In practice, update-alternatives is supposed to create several symbolic links to the files in the fglrx directory, but it will be ignored if the alternatives for the very related gl_conf entry has been set to manual. Do<br />
update-alternatives --get-selections | grep gl_conf<br />
and see if the mode is manual instead of auto and if mesa is mentioned instead of fglrx in the path that is printed. In this case you need to <br />
sudo update-alternatives --set gl_conf /usr/lib/fglrx/ld.so.conf<br />
to set fglrx as the active alternative. You can alternatively (no pun intended) and additionally change the gl_conf into automatic mode before the installation this way:<br />
sudo update-alternatives --auto gl_conf<br />
After that, the alternatives should automatically be configured correctly when the graphics driver .debs are installed.<br />
<br />
== "update-alternatives: error" during install ==<br />
During installation you may receive the following message:<br />
<pre>update-alternatives: error: unable to make /usr/lib/xorg/modules/drivers/fglrx_drv.so.dpkg-tmp a symlink to /etc/alternatives/fglrx_drv: No such file or directory</pre><br />
This can be easily solved by creating directory "drivers" under /usr/lib/xorg/modules/<br />
sudo mkdir /usr/lib/xorg/modules/drivers<br />
<br />
== 'Can't exec "debian/rules": Permission denied at /usr/bin/dpkg-buildpackage line 507.' during deb generation ==<br />
During installation you may receive the following message:<br />
<pre>Can't exec "debian/rules": Permission denied at /usr/bin/dpkg-buildpackage line 507.</pre><br />
This can happen when your /tmp folder is mounted with the option "noexec". The noexec is suggested by many howtos regarding Ubuntu on SSD, when placing the /tmp in memory.<br />
A workaround can be found here: [http://serialized.net/2010/03/getting-around-tmpfs-noexec-problems/]<br />
<br />
== Errors during deb generation ==<br />
You may recieve errors if you do not have devscripts, dh-make, execstack and dh-modaliases installed. Run apt-get to install, and the errors go away and the deb is generated correctly.<br />
<br />
If you recieve the error dpkg-buildpackage: not found:<br />
sudo apt-get install devscripts<br />
<br />
If you recieve the error make: dh: command not found:<br />
sudo apt-get install dh-make<br />
<br />
If you recieve the error make: execstack: Command not found:<br />
sudo apt-get install execstack<br />
<br />
If you recieve the error make: dh_modaliases: Command not found:<br />
sudo apt-get install dh-modaliases<br />
<br />
== Black screen after uninstalling old amd drivers ==<br />
Start you computer in recovery mode and exit to root shell.<br />
Remount your partitions in rw mode:<br />
mount -rw -o remount /<br />
...<br />
Go to your download directory and proceed with building and installing the drivers in recovery mode.<br />
All should be fine after a reboot.<br />
<br />
== References ==<br />
<br />
<references/></div>221.181.232.146http://wiki.cchtml.com/index.php?title=Ubuntu_Precise_Installation_Guide&diff=9334Ubuntu Precise Installation Guide2012-12-10T10:41:01Z<p>221.181.232.147: RwpIoNkQwpUOlJSU</p>
<hr />
<div>Hello Beach Backgrounds,I absolutely love your pticures, they look very tropical.Do I have permission to use this photo in the background of my website that sells silk plants and flowers? We could add a link to your website on our tropical links page if you wish?Please let me know,Thank YouBob</div>221.181.232.147http://wiki.cchtml.com/index.php?title=Ubuntu_Hardy_Installation_Guide&diff=8523Ubuntu Hardy Installation Guide2012-05-16T05:55:10Z<p>221.181.232.145: /* Hang at logout */</p>
<hr />
<div>For most users it won't be necessary to go into installation and configuration details of the driver. Ubuntu 8.04 (Hardy) provides a notification saying that there are restricted drivers available. You just have to go there (Restricted Drivers Manager) and enable the "ATI accelerated graphics driver". Ubuntu will then install and configure the driver for you. If this does not provide the optimal solution you were looking for, please read ahead.<br />
<br />
After installation, in GNOME or Kubuntu, '''turn off visual effects''' or you will notice a flicker in OpenGL.<br />
<br />
<br />
== Method 1: Install the driver the Ubuntu Way ==<br />
<br />
This will install the current driver in Ubuntu's repository. It is older than the one AMD has released, but will be supported by the Ubuntu people. Catalyst 8.3 is in the repositories.<br />
<br />
{{Box Terminal|<br />
$ sudo apt-get update<br />
<br />
$ sudo apt-get install linux-restricted-modules-generic restricted-manager<br />
<br />
$ sudo apt-get install xorg-driver-fglrx<br />
<br />
$ sudo depmod -a<br />
}}<br />
<br />
The second line may not be necessary as you may already have restricted modules installed. Run it just in case. If the third line fails, you probably don't have the restricted repository enabled. See Pre-Installation.<br />
<br />
After this, you may need to edit Xorg.conf:<br />
<br />
{{Box Terminal|<br />
$ sudo gedit /etc/X11/xorg.conf<br />
}}<br />
<br />
In the device section, if it is not already there add:<br />
<br />
{{Box File|/etc/X11/xorg.conf|<br />
Driver "fglrx"<br />
}}<br />
<br />
Then to make sure Xorg is set up correctly, you'll have to let aticonfig "initialize" it:<br />
<br />
{{Box Terminal|<br />
$ sudo aticonfig --initial -f<br />
}}<br />
<br />
After this you should be able to restart your computer and have the driver working. To test type<br />
<br />
{{Box Terminal|<br />
$ fglrxinfo<br />
}}<br />
<br />
into a terminal. If the vendor string is not ATI, but Mesa, check [[#Removing Mesa drivers]]<br />
<br />
==== Post-Installation Tweaks ====<br />
To enable hardware accelerated video on pre-R500 cards, edit '''/etc/X11/xorg.conf''' to include the following lines without '''[...]'''<br />
<br />
{{Box File|/etc/X11/xorg.conf|<br />
Section "Device"<br />
:[...]<br /><br />
:Driver "fglrx"<br /><br />
:Option "VideoOverlay" "on"<br /><br />
:Option "OpenGLOverlay" "off"<br /><br />
:[...]<br /><br />
EndSection<br />
}}<br />
<br />
Note that when Visual Effects (Compiz) are active, flickering and artifacts may occur in OpenGL applications and hardware accelerated video windows (particularly with R300 chipset). To prevent this, disable Visual Effects.<br />
<br />
On newer cards the options below enables Visual Effects and video to be played without flicker. The Textured video option can be turned on, but this can cause flicker or diagonal artifacts when playing videos.<br />
<br />
{{Box File|/etc/X11/xorg.conf|<br />
Section "Device"<br />
:[...]<br /><br />
:Driver "fglrx"<br /><br />
:Option "VideoOverlay" "off"<br /><br />
:Option "OpenGLOverlay" "on"<br /><br />
:Option "TexturedVideo" "off"<br /><br />
:[...]<br /><br />
EndSection<br />
}}<br />
<br />
== Method 2: Manual Install Method ==<br />
<br />
Make sure ''universe'' and ''multiverse'' are enabled in your repository sources.<br />
<br />
===''1. Install necessary build tools and libraries''===<br />
{{Box Terminal|<br />
$ sudo apt-get update<br /><br />
$ sudo apt-get install build-essential cdbs fakeroot dh-make debhelper debconf libstdc++5 dkms linux-headers-$(uname -r)<br /><br />
# If you are using the x86_64 architecture (64 bit, earlier known as amd64), install ia32-libs as well:<br /><br />
$ sudo apt-get install ia32-libs<br />
}}<br />
<br />
===''2. Download the latest Catalyst package.''===<br />
<br />
Download page: Catalyst {{catalystversion}}. This package contains both the 32-bit and 64-bit driver.<br />
<br />
Open a terminal window and switch to the directory you downloaded the installer to. <br />
For example:<pre>cd Desktop</pre><br />
<br />
'''or''' just use wget:<br />
{{Box Terminal|<br />
$ wget http://www2.ati.com/drivers/linux/{{catalystfilename}}<br />
}}<br />
<br />
===''3. Create .deb packages.''===<br />
{{Box Terminal|<br />
$ chmod +x {{catalystfilename}}<br />
<br />
$ sh {{catalystfilename}} --buildpkg Ubuntu/hardy<br />
}}<br />
("hardy" is not a typo)<br />
<br />
===''4. Add driver to kernel module blacklist.''===<br />
'''NOTE''': This step is no longer necessary with fglrx 8.10 or 8.12. Just jump to step 5 in that case.<br />
<br />
The ATI driver must be added to the kernel module blacklist so that the new ATI driver will be used. If it is not blacklisted, the official Ubuntu repository version of the ATI driver will be loaded instead.<br />
<br />
{{Box Terminal|<br />
$ sudo gedit /etc/default/linux-restricted-modules-common<br />
}}<br />
<br />
Add "fglrx" to the line "DISABLED_MODULES"<br />
{{Box File|/etc/default/linux-restricted-modules-common|<br />
<pre>DISABLED_MODULES="fglrx"</pre><br />
}}<br />
<br />
Please note that after the modification above, the "Restricted Driver Manager" will signal "ATI accelerated graphics driver" not enabled (unticked). This is perfectly correct. At the end of the installation procedure it will signal in Status: "in use" (green light), but NOT enabled. It simply means that the fglrx module contained in the linux-restricted-modules package is not enabled, but another fglrx module ({{catalystversion}}) is in use.<br />
<br />
You may also need to edit the file(s) (if they exist):<br />
{{Box Terminal|<br />
$ sudo gedit /etc/modprobe.d/blacklist-restricted<br />
<br />
$ sudo gedit /etc/modprobe.d/blacklist-local<br />
}}<br />
<br />
Put a # in front of the line "blacklist fglrx", if it is present. Otherwise, the kernel module will not load automatically, and you will not get 3D acceleration.<br />
<br />
===''5. Install .debs.''===<br />
<br />
'''For 32 Bits'''<br />
<br />
{{Box Terminal|<br />
$ sudo dpkg -i xorg-driver-fglrx_8.593-0ubuntu1_i386.deb fglrx-kernel-source_8.593-0ubuntu1_i386.deb fglrx-amdcccle_8.593-0ubuntu1_i386.deb<br />
}}<br />
''Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.''<br />
<br />
Starting Catalyst version 8.10, installing the following package ensures compatibility with restricted drivers' manager:<br />
<br />
{{Box Terminal|<br />
$ sudo dpkg -i fglrx-modaliases_8.593-0ubuntu1_i386.deb<br />
}}<br />
<br />
64 bit systems should have the same behaviour.<br />
{{Box Terminal|<br />
sudo dpkg -i fglrx-modaliases_8.593-0ubuntu1_amd64.deb<br />
}}<br />
<br />
'''For 64 Bits'''<br />
<br />
{{Box Terminal|<br />
$ sudo dpkg -i xorg-driver-fglrx_8.593-0ubuntu1_amd64.deb fglrx-kernel-source_8.593-0ubuntu1_amd64.deb fglrx-amdcccle_8.593-0ubuntu1_amd64.deb<br />
}}<br />
''Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.''<br />
<br />
=== Additional 64-bit instructions ===<br />
<br />
If you have a 64 bit install, the above dpkg command may complain that "Errors were encountered while processing: fglrx-amdcccle". This is because of a dependency of the amdccle package on 32 bit libraries. If you receive this error, issue the following command after the above dpkg command, which will force the installation of all of the 32 bit dependencies, and then the amdccle package:<br />
<br />
{{Box Terminal|<br />
$ sudo apt-get install -f<br />
}}<br />
<br />
Catalyst {{catalystversion}} on 64-bit systems requires the ''--force-overwrite'' command in the above ''dpkg'' command:<br />
{{Box Terminal|<br />
$ sudo dpkg -i --force-overwrite xorg-driver-fglrx_8.593*.deb fglrx-kernel-source_8.593-0*.deb fglrx-amdcccle_8.593-0*.deb<br />
}}<br />
<br />
When installing the packages, if <tt>xorg-driver-fglrx_8.593</tt> fails to install due to a diverted file conflict, you can [http://emmetcaulfield.net/Tech/ATIv84+Hardy/ fix the package with this procedure].<br />
<br />
===Fix for an error:===<br />
If you are having this error:<br />
<pre><br />
dpkg-shlibdeps: failure: couldn't find library libfglrx_gamma.so.1 needed by debian/xorg-driver-fglrx/usr/bin/fglrx_xgamma (its RPATH is '').<br />
</pre><br />
<br />
Fix it by doing the following:<br />
{{Box Terminal|<br />
$ sudo sh {{catalystfilename}} --extract driver<br /><br />
$ cd driver/arch/x86_64/usr/X11R6/lib64<br /><br />
$ sudo ln -s libfglrx_gamma.so.1.0 libfglrx_gamma.so.1<br /><br />
$ cd ../../../../../<br /><br />
$ sudo sh ati-installer.sh -- --buildpkg Ubuntu/hardy<br /><br />
}}<br />
<br />
If you get this error from modprobe fglrx:<br />
<pre><br />
ERROR: firegl_stub_register failed<br />
</pre><br />
<br />
Fix it by doing:<br />
{{Box Terminal|<br />
$ sudo rmmod radeon<br /><br />
$ sudo rmmod drm<br /><br />
$ sudo modprobe fglrx<br /><br />
}}<br />
<br />
=== Finishing the Install: Configuration ===<br />
<br />
If you've used fglrx previously, you will not need to do this.<br />
Run<br />
<pre>sudo aticonfig --initial -f</pre><br />
<br />
Now you'll likely have to edit your xorg.conf (even if just to confirm the above command added the apropriate fglrx line):<br />
<pre>sudo gedit /etc/X11/xorg.conf</pre><br />
and add the following line to the Device section (if it does not already exist). Include the following lines without '''[...]''': <br />
<pre>Section "Device"<br />
[...]<br />
Driver "fglrx"<br />
[...]<br />
EndSection</pre><br />
Make the appropriate changes to "TexturedVideo" and "Overlay", etc., as described above in the "automatic section".<br />
Save and exit, then <br />
in a terminal. If it does not error you should be fine. <br />
<br />
Some people find that changes to xorg.conf don't get used by the driver. To force the ati driver to adopt changes made to xorg.conf, type the following command:<br />
<pre><br />
sudo aticonfig --input=/etc/X11/xorg.conf --tls=1<br />
</pre><br />
Finally, reboot the computer and type<br />
<pre><br />
fglrxinfo<br />
</pre><br />
into the terminal. If the vendor string contains ATI, you have installed the driver successfully. Release 8.8 looks like:<br />
<pre><br />
display: :0.0 screen: 0<br />
OpenGL vendor string: ATI Technologies Inc.<br />
OpenGL renderer string: Radeon X1950 Series<br />
OpenGL version string: 2.1.7873 Release<br />
</pre><br />
<br />
<br />
Please note: Depending on the particular ATI card that you own, you may or may not automatically have all of the relevant driver features enabled. R500 and R600 cards (X1xxx, HD series, and newer) in particular will need TexturedVideo enabled in Xorg.conf (rather than the traditional VideoOverlay) in order to support Xv accelerated video playback.<br />
<br />
=== Removing Mesa drivers ===<br />
If fglrxinfo reports that Indirect rendering by Mesa is in place, even though you have installed ATI driver, check:<br />
<br />
*Remove the package xserver-xgl.<br />
:<pre>sudo apt-get remove xserver-xgl</pre><br />
:'''Explanation:''' If you installed this previously in order to make compiz work, it will not allow direct rendering on your display. You can check out if this is what it causing the problem by running<br />
:<pre>DISPLAY=:0 glxinfo | grep render</pre><br />
:If it returns an ATI renderer, it means that xgl is being displayed indirectly on the display 1. (Taken from [http://ubuntuforums.org/showthread.php?t=740287])<br />
<br />
:'''Warning:''' This might make your compiz stop working as it is configured to use XGL. A solution might be to run the Envy script in order to configure compiz. Or, if Compiz stopped working due to "Composite" problem, check that the following is set in the /etc/X11/xorg.conf<br />
<pre><br />
Section "Extensions"<br />
Option "Composite" "Enable"<br />
EndSection<br />
</pre><br />
<br />
<br />
----<br />
<br />
<br />
*Check for AGP and DRI errors in /var/log/Xorg.0.log like these are: <br />
:<i>(EE) fglrx(0): [agp] unable to acquire AGP, error -1023<br />
:(EE) fglrx(0): cannot init AGP<br />
:(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.<br />
:(WW) fglrx(0): * DRI initialization failed! *</i><br />
<br />
:If you have Intel 8285P and E7205 chipsets and AGP not detected then you have to remove the i82875p_edac module and restart a some others: <br />
<pre>rmmod i82875p_edac<br />
rmmod fglrx<br />
rmmod intel-agp<br />
rmmod agpgart<br />
modprobe agpgart<br />
modprobe intel-agp<br />
modprobe fglrx</pre><br />
<br />
:Blacklist the modules e7xxx_edac so it doesn't start up again when booting - add the following line at the beginning of /etc/modprobe.d/blacklist:<br />
:<pre>blacklist i82875p_edac</pre><br />
<br />
:This has been known to fix issues with -Mesa -AGP -DRI -Google earth and -suspend to RAM (s2ram).<br />
<br />
:'''Explanation:''' http://openwetware.org/wiki/Computing/Linux/Ubuntu<br />
<br />
<br />
----<br />
<br />
<br />
*Check you are running the correct kernel. <br />
:'''Explanation:''' If you're upgrading from Gutsy to Hardy in some instances the Grub bootloader does not get updated and the new kernel is not loaded.<br />
:Run in a terminal:<br />
{{Box Terminal|<br />
$ uname -r<br />
}}<br />
:If the output starts with 2.6.22 or below you are not using the current kernel and the Ati drivers will not load properly.<br />
<br />
If this doesn't help, try [[Ubuntu Gutsy Installation Guide#Verifying]], or other links: [http://wiki.cchtml.com/index.php/Troubleshooting#No_3D_acceleration], [http://www.thinkwiki.org/wiki/Problems_with_fglrx#Perpetual_Mesa_GLX_Indirect_on_Debian], [http://ubuntuforums.org/archive/index.php/t-475699.html].<br />
<br />
== Specific Issues ==<br />
<br />
===Segmentation Fault with glxinfo/fglrxinfo===<br />
<br />
If you experience such errors (and have ''glxinfo'' report ''"Direct rendering"'' as ''No'' despite following the whole procedure without any errors) you may want to have a look at the '''Specific Issues''' chapter of the '''Ubuntu Gutsy Installation Guide''' [[http://wiki.cchtml.com/index.php/Ubuntu_Gutsy_Installation_Guide#If_you_get__.2Fusr.2FX11R6.2Flib.2Fmodules.2Fdri.2Ffglrx_dri.so_not_found]] as this may be due to missing links or wrong permissions.<br />
<br />
That's cleared my thuohgts. Thanks for contributing.<br />
<br />
=== Suspend/Hibernation ===<br />
<br />
Suspend hibernation '''works''' with the latest driver.<br />
<br />
For ATI X1400, to get the laptop to wake up from suspend, I had to change the following in /etc/default/acpi-support:<br />
<br />
<pre><br />
SAVE_VBE_STATE=false<br />
<br />
POST_VIDEO=false <br />
<br />
ENABLE_LAPTOP_MODE=false<br />
</pre><br />
<br />
<br />
For Radeon 3200, to wake up from suspend, I had to add the following lines to /etc/X11/xorg.conf:<br />
(This settings is not good option, if you are using compiz-fusion or any other transparency-based thingie. Not working for HD 3850)<br />
<br />
<pre><br />
Section "Extensions"<br />
Option "Composite" "Disable"<br />
EndSection<br />
<br />
Section "ServerFlags"<br />
Option "AIGLX" "off" <br />
EndSection<br />
</pre><br />
<br />
Resume from suspend failed when using dual monitor configuration in xorg.conf.<br />
E.g. when using<br />
<pre><br />
aticonfig --initial=dual-head --screen-layout=right<br />
</pre><br />
Switching back to a single monitor configuration and restarting the xserver (though not beautiful) solves this.<br />
<br />
=== Error! This module/version combo is already installed ===<br />
<br />
Simply uninstall the previous version before installing the new one with<br />
<pre><br />
sudo dkms remove -m fglrx -v 8.522 --all<br />
</pre><br />
<br />
[[Category:Installation Documentation]]</div>221.181.232.145http://wiki.cchtml.com/index.php?title=Ubuntu&diff=8479Ubuntu2012-05-15T19:35:19Z<p>221.181.232.147: MvTNzxCNmCcYqkoqin</p>
<hr />
<div>Ubuntu makes great operating sysetm and I enjoy it on my computers for second year. This recent release is great. I installed in on few computers and it completed installation very fast without any issues. It found all of hardware on all computers and installed all appropriate drivers. My relative was using it for first time in his life and it took him about 10 minutes to get comfortable then get online and check email. I guess the time when Linux installation was a struggle is over. Windows is more difficult to install these days. The computer under Ubuntu runs really fast. First thing you will notice that you don't need antivirus, because there's no viruses to fear, and you computer is free from all garbage adware. Nothing pops up, you can calm down and do what you got to do. Few people aware of that it comes equipped with complete Office suite! The whole thing is there and it gets installed from the disk together with Ubuntu. I can open and work on all my Excel files, Word documents etc. I installed it on friend's computer and he was asking not to remove the Windows he had, so I made it dual boot (it also conveniently offered option during the installation!). In four days he asked me to redo it again and remove Windows entirely. Use to be Windows was safe from Linux because Linux was so difficult to use. Today, as Linux got some very cool and advanced interfaces like Gnome and KDE, it is as easy (if not easier) than Windows. For most people who use their computer in a same way as I do: web, email, pictures, music and writing, Linux is the simplest and the best. You just get use to its interface and explore some software that all comes with it.</div>221.181.232.147