cchtml.com - User contributions [en]

Features

2012-06-22T01:26:28Z

94.23.1.28: vdfTSVSleXA

I am a happy owner of this laptop. Here are my notes on it after using it for few days.. - Cool!! Only warm after hours of video. For non-video invnesite application, it is just slightly warm on upper left part of the laptop. Amazing !! The fan is quiet but it is not silent. How can HP run AMD Quad Core with little heat?! I spent $1000+ to build a Home Theater PC 7 years ago So I know how difficult to keep the heat down. - The Microsoft movie maker, word+excel (limited function) are useful, all other Microsoft application are very basic! Lucky HP provides Corel VideoStudio and PaintShop Pro apps. The HP MediaSmart is not bad, it handles most of your multimedia needs. - The Cyberlink DVD/CD burning apps is also very basic. - To create a recovery DVD, it took 6 DVD discs and about 3 to 4 hours .. Each DVD is about 4GB, I wonder what is on these 24GB !! You can only create it once. Don't start it before you go to sleep, or you will need to stay up for 4 hours. - The LED 17.3 screen is very nice. Video and pictures look very nice on it. It is also very cool to touch. But you can't use it in front of a window. The screen is quite reflective. - The blue ray drive is a little slow, or may be the software is slow. It takes about 1 to 2 minutes to start a blue ray movie. But the HP Blue Ray player software has an easy interface. - HDMI connection to TV is very easy. I played Avatar on it, it is my first blue ray disc. Very clear and beautiful color. Better than DVD even on my 720P (not 1080p) 50 TV! - The hinges of the screen is very tight. I can not open the screen with one hand. - The multi-touch mouse pad is good. I can use two fingers to scroll and zoom. - The finger print reader is so easy to use. It is also very accurate. Any member of my family can just swipe one of their finger and switch to his/her account on the window. - USB 3.0 with SATA wow, I have not tried them yet, but I am sure they are fast . The built-in multi card reader is very convenient too. - When charging the battery, it is making some noticeable shhhhh noice until it gets to 85% or higher. And it recharges quickly. It seems than the recharge light is Amber when it charging and change to white when it finishes. The charger is warm to touch. - The webcam is in HD mode with left and right mic. When in use, its white LED turns on. - The Fences software group the desktop icons into smaller windows. It is not bad. When you double click the desktop, all icons disappear. Then double click to get them back. - The audio is very good for a laptop. It has a subwoofer on the bottom of this laptop Of course, it can't replace your external speakers with external subwoofer. - I also like the Desktop Gadgets. There are many free and good apps from the web. I recommend the talking clock, zCalendar, WeatherBug, and couple radio apps. I wish I can run Google Honeycomb 3.0 on this laptop. It would be even faster. M.S. Windows tends to slow down the more you use it. It just collects more and more garbage and makes its register huge with a lot of mess. I need to find a good clean up software for it. Don't forget to install some type of anti-virus and auti-spy software. There are some good free one out there. There are not many blue ray laptop out there. This unit is one of the best deal for a 17.3 . I checked the smaller 15.6 model at Amazon, it is only $50 less. So which one do you choose ? The same model with Intel iCore 5 is about $200 more w/ 6GB memory . Hummm, I chose AMD quad cores That is all for now. One month update: My mistake. I checked the spec again recently, the USB is 2.0 (not 3.0 ;-() So I reduce my rating by half star .. I also noticed that the function keys are not normal . Each function key can do 2 things. Its multimedia control is the primary function. If you need the F1 to F12, you need to hit and hold fn key first. Since I use this lap top mostly for entertainment, so I like it As a result, I add half star back to my rating :-0 If you need the F1 to F12 functions very often, then you may want to think about it Few days ago, I connected my laptop to a 21 external LED monitor and I noticed that this laptop screen is not white enough. Again, it is ok for entertainment (kind of like movie mode in my projector). But if you need a very white color (like some graphic design), then this may concern you too . But I did not notice the difference in whiteness and brightness until I put them side by side.

Catalyst 12.4

2012-06-21T22:54:41Z

94.23.1.28: LsczIECQsFp

All games are released for dienerfft operating systems but not for dienerfft graphics processing units, this is because the graphics cards all use the same basic technology. They are all small processors with cooling.Some are better than others but not exclusive. Take Crysis , it's optimized for Intel and Nvidia but plays just as well om Ati and AMD.Log in to Reply</a>Was this answer helpful?Like</a>Dislike</a>

Ubuntu Natty Installation Guide

2012-06-21T18:34:15Z

94.23.1.28: /* Issues */

Catalyst 11.6

2012-06-21T18:20:04Z

94.23.1.28: ukzxQhsRrmcANQlWkJF

While linux may seem like a small segment of users, the martjioy of those users are geeks who other people others turn to to build their computers and fix things when they go wrong. I switched many years ago from ATI to nVidia because of their flacky linux support. Additionally, four of my friends ended up following me to nVidia because I'm their human version of Tom's Hardware Guide. Well not really, but my opinions on things carry weight and I have no opinion on ATI because I've just ignored them since I switched. I'm trying to convert these people to linux as well, so I have a vested interest in ensuring their hardware is support. Alienating the linux community, is likely hurting their sales a lot. Assuming there are only 2 million real users and say only half of them have abandoned ATI for nVidia with say four friends which have followed them (who don't use linux), that's 5 million people who haven't bought an ATI video card, which at an average cost of about $150 CDN/card, that is a loss of $750 million in sales every three or so years. That alone would account for a good chunk of their $600 million in loses a year. And that is just from ubuntu's share of the linux world I have no proof to back this up, but I can't see how their crappy linux support is helping them.

Hardware

2012-06-21T17:55:46Z

94.23.1.28: VEfbNdObISsoPEfdeR

Hello Ms. Miller, I'm Randee, I'm a Cousin of the Bride's Mom. You did a FANTASTIC JOB on taking all of these phoots. I absolutely LOVE them. The one where The Groom , Craig is kissing The Bride , Jessica's cheek is my absolute Favorite. They make such a Beautiful Married Couple! I just love them both to death. It was a Beautiful Wedding. Thank you so much for being a part of it. Love Always , Randee

Ubuntu Precise Installation Guide

2012-06-21T17:43:26Z

94.23.1.28: /* Just in case */

__TOC__

= The Options =
Users with ATI cards have the following driver options:
* '''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.
* '''ati''' - actually a thin wrapper that will invoke the radeon driver (or another ati open-source driver for pre-Radeon cards).
* '''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. Power management is now comparable to the Catalyst driver.
* '''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.

= Updated Open Source Driver PPA's =
* '''"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
* '''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

= Installing Proprietary Drivers a.k.a. Catalyst/fglrx =
*PLEASE READ FIRST!
'''Which cards are no longer supported by ATI?'''
The ATI Radeon 9500-9800, Xpress200-1250, 690G, 740G, X300-X2500 (including Mobility RadeonHD 2300, since it is really a DirectX 9 part). See the complete list [http://wiki.cchtml.com/index.php/9.4 here.]
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.
{| WIDTH="650" cellpadding=0 cellspacing=0 style="background-color: red; border: solid 1px #666666; color: #ffffff; text-align: center;"
| style="background-color: #666666; border: solid 1px #666666; border-bottom: 1px solid #888;" | '''ATTENTION RADEON USERS'''
|-
| 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. 
|}

== Using Ubuntu-supplied fglrx/Catalyst ==

This may not give you the latest drivers, but should be safest. On Ubuntu Precise, this will install Catalyst 8.960, which is roughly equivalent to Catalyst 12-4. NOTE: You must have the restricted repository enabled in Applications -> Ubuntu Software Center -> Edit -> Software Sources... for this to work. After you complete the install, skip to [[Ubuntu_Precise_Installation_Guide#Generate_a_new_.2Fetc.2FX11.2Fxorg.conf_file|Generate a new /etc/X11/xorg.conf file]].

=== Command line ===

sudo apt-get install fglrx fglrx-amdcccle

=== GUI ===

You must have jockey-common and jockey-gtk (or jockey-kde for Kubuntu) packages installed. For the default Ubuntu desktop (Unity), go to the dashboard home and search for "Additional Drivers" in the applications search field (or double-click the "available driver" notification icon) and activate the "ATI/AMD proprietary FGLRX graphics driver".

== Installing Catalyst Manually (from AMD/ATI's site) ==

IMPORTANT NOTE: Installing Catalyst 12-4 on 32-bit Precise currently requires a patch. It is recommended to use the fglrx package from Ubuntu instead, but the patch procedure can be found here: http://ubuntuforums.org/showthread.php?t=1969827

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).

===''Before you start''===
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).
or Applications->Ubuntu Software Center->Edit->Software sources->Other software: check canonical partners.

Install the prerequisite packages:
sudo apt-get install build-essential cdbs dh-make dkms execstack dh-modaliases fakeroot libqtgui4

''If you are using the x86_64 architecture (64 bit)'':
sudo apt-get install ia32-libs-multiarch:i386 lib32gcc1 libc6-i386
cd /usr ; sudo ln -svT lib /usr/lib64

===''Download the latest Catalyst package.''===
This package contains both the 32-bit and 64-bit driver.
cd ~/; mkdir catalyst{{Catalystversion}}; cd catalyst{{Catalystversion}}/
wget <nowiki>http://www2.ati.com/drivers/linux/amd-driver-installer-</nowiki>{{Catalystdashversion}}-x86.x86_64.run
chmod +x amd-driver-installer-{{Catalystdashversion}}-x86.x86_64.run

===''Create and install .deb packages.'' ===
sh ./amd-driver-installer-{{Catalystdashversion}}-x86.x86_64.run --buildpkg Ubuntu/precise
sudo dpkg -i fglrx*.deb

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]

===''In case of failure:''===

Remember these steps before you reboot your computer.

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.

sudo startx

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/.

If all else fails, revert your xorg.conf and reboot.

sudo cp /etc/X11/xorg.conf.orig /etc/X11/xorg.conf

This should return your original display.

==''Generate a new /etc/X11/xorg.conf file''==

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.

hahhaahahahahah! DO Not do that on your first date, EVER! I love this guys facts though fuck! haahhah. Either way, his tips do make a good point. I ve always like the random profile pics that have been taken straight from the internet. With high contrast resolution and professional lighting. unless theyre a model. Anyways. good stuff. And if you to see to good dating site go to my profile, and go to the website stated enjoy .good video man

=== Minimal Config ===
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:

Section "Device"
Identifier "ATI radeon 6870"
Driver "fglrx"
EndSection

=== X2/Dual GPU Cards ===
If you have an X2 card (e.g. 4870X2 or 5970), use... '''!!Do not use for two separate cards in crossfire!!'''
sudo amdconfig --initial -f --adapter<nowiki>=</nowiki>all

=== Dual/Multi Monitors ===
If you have a dual monitor display (also known as "Big Desktop"), use:
sudo amdconfig --initial -f
sudo amdconfig --set-pcs-str<nowiki>=</nowiki>"DDX,EnableRandR12,FALSE"
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.

==''Force use of the new xorg.conf (if necessary)''==
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:

sudo amdconfig <nowiki>--input=/etc/X11/xorg.conf --tls=1</nowiki>

==''Test your installation''==
NOTE: if you don't reboot first, fglrxinfo gives an error message.
Reboot the computer and type
fglrxinfo
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:
<pre>
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Radeon HD 4550 (This line may be different depending on what graphics card you are using.)
OpenGL version string: 3.3.11566 Compatibility Profile Context (This line may be different depending on what graphics card and
Catalyst version you are using.)
</pre>
Now, try:
fgl_glxgears
If you experience issues or a hang, you may need to disable fast TLS.
sudo amdconfig --tls=0

This is a raelly intelligent way to answer the question.

= Alternative Manual Installation =
WARNING: This method is incompatible with Debian/Ubuntu Filesystem Hierarchy and may cause issues, especially when trying to remove or upgrade Catalyst. It is highly recommended to build .deb pakages. USE AT OWN RISK.

This is another method of manual installation that may work best for laptop users who have a hybrid setup (i.e. Intel HD onboard graphics with an AMD discrete GPU).

sudo cp /etc/X11/xorg.conf /etc/X11/xorg.conf.orig
./amd-driver-installer-{{Catalystdashversion}}-x86/x86_64.run

Click "Install Driver on X.Org" rather than "Generate distribution specific driver package". Select the "Automatic" install option.

= Hardware Video Decode Acceleration (EXPERIMENTAL) =

== Using XBMC player (XvBA) ==

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:

sudo apt-add-repository ppa:wsnipex/xbmc-xvba-eden
sudo apt-get update
sudo apt-get install xbmc

== Using the xvba-va Driver (VA-API) ==
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

sudo apt-get install xvba-va-driver libva-glx1 libva-x11-1 vainfo
vainfo

vainfo should return something like the following (and no errors):
libva: libva version 0.32.0
Xlib: extension "XFree86-DRI" missing on display ":0.0".
libva: va_getDriverName() returns 0
libva: Trying to open /usr/lib/dri/fglrx_drv_video.so
libva: va_openDriver() returns 0
vainfo: VA API version: 0.32
vainfo: Driver version: Splitted-Desktop Systems XvBA backend for VA-API - 0.7.8
vainfo: Supported profile and entrypoints
VAProfileH264High : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLD

If vainfo returns an error, you may need to create a symlink:

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
sudo ln -s /usr/lib/va/drivers/fglrx_drv_video.so /usr/lib/dri/fglrx_drv_video.so #for 32-bit

Once you've confirmed that vainfo is correct, you can test video playback. A good test player for xvba is VLC. You can enable xvba in Tools -> Preferences -> Input and Codecs. Check the box named "Use GPU acceleration (experimental)" and then restart VLC.

=Updating Catalyst/fglrx=

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.

=Removing Catalyst/fglrx=
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.
sudo sh /usr/share/ati/fglrx-uninstall.sh
sudo apt-get remove --purge fglrx fglrx_* fglrx-amdcccle* fglrx-dev*

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]
sudo apt-get remove --purge xserver-xorg-video-ati xserver-xorg-video-radeon
sudo apt-get install xserver-xorg-video-ati
sudo apt-get install --reinstall libgl1-mesa-glx libgl1-mesa-dri xserver-xorg-core
sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.backup
sudo rm -rf /etc/ati

If you receive

$ E: Internal Error, No file name for libgl1-mesa-dri

Change the third command above to:

sudo apt-get install --reinstall libgl1-mesa-glx:i386 libgl1-mesa-glx:amd64 libgl1-mesa-dri:i386 libgl1-mesa-dri:amd64 xserver-xorg-core

= Issues =

== Video Tearing ==

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.
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:
sudo amdconfig --sync-video=on
The option will not take effect until you restart X (i.e. log out).

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.

=== kwin ===
You can enable vsync for kwin in System Settings -> Desktop Effects -> Advanced tab

=== Compiz (Unity/GNOME-Shell) ===
TODO: See if there's a friendlier way to make sure vsync is enabled without installing ccsm.

Install the compiz settings manager:
sudo apt-get install compizconfig-settings-manager
ccsm

The 'Sync to Vblank' is found in the 'OpenGL' subsection of the 'General' group

== Hybrid Graphics and Catalyst==

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.

=== ATI/ATI Hybrids ===
As of Catalyst 11-8, switching between two ATI cards (and maybe Intel/ATI muxless too?) is supposed to be doable, though I don't know 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:

amdconfig --pxl # List current activated GPU
sudo amdconfig --px-dgpu # Activate discrete GPU (High-Performance mode), must re-start X to take effect
sudo amdconfig --px-igpu # Activate integrated GPU (Power-Saving mode), must re-start X to take effect

After switching, one would log out and back in to restart X.

=== Intel/ATI Hybrids ===

TODO: Status unknown at this time

== Build Fails and Log Shows "mixed implicit and normal rules. Stop." ==

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:
ls -la /usr/bin/gcc
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:
sudo ln -sf /usr/bin/gcc-4.6 /usr/bin/gcc
When you're finished installing the driver, return the gcc link to its original value:
sudo ln -sf /usr/bin/builder-cc /usr/bin/gcc
Launchpad link for this bug: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/555957

How could any of this be better satetd? It couldn't.

== Problems Starting Xserver ==

If you get a black screen hang, the first thing to check is if xorg.conf is the problem.

You can disable the xorg.conf with:
sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.disabled

Reboot and check to see if things work now.

You can reinstate the file with:
sudo mv /etc/X11/xorg.conf.disabled /etc/X11/xorg.conf

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 -

start on filesystem

script
chmod 0666 /dev/null
chmod 0666 /lib/udev/devices/null
end script

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!

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:
sudo amdconfig --acpi-services=off
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.

== Unsupported Hardware Watermark ==
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.

If you installed the proprietary driver included with Ubuntu or you do not want to upgrade to a newer version, it may be possible to work around the issue by using a control file from a newer version of Catalyst than the one you're running.
cd ~/; mkdir catalyst{{Catalystversion}}; cd catalyst{{Catalystversion}}/
wget <nowiki>http://www2.ati.com/drivers/linux/amd-driver-installer-</nowiki>{{Catalystdashversion}}-x86.x86_64.run
chmod +x amd-driver-installer-{{Catalystdashversion}}-x86.x86_64.run
sh amd-driver-installer-{{Catalystdashversion}}-x86.x86_64.run --extract driver
sudo mv /etc/ati/control ~/control.bak
sudo cp driver/common/etc/ati/control /etc/ati

== Hang at logout ==

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.

Before the following commands verify that /etc/ati/authatieventsd.sh exists after build and install, if not just do:
(assuming that the installer is in the directory we used to install)

cd ~/catalyst{{Catalystversion}}
sh amd-driver-installer-{{Catalystversion}}-x86.x86_64.run --extract driver
sudo cp driver/packages/Ubuntu/dists/lucid/replacements/authatieventsd.sh /etc/ati/authatieventsd.sh
sudo chmod +x /etc/ati/authatieventsd.sh

This problem can be fixed permanently with:

sudo mkdir -p /var/lib/xdm/authdir
sudo ln -s /var/run/xauth /var/lib/xdm/authdir/authfiles

If that doesn't work then you can disable atieventsd with this command:

sudo /usr/sbin/update-rc.d -f atieventsd remove

You'll have to restart for this to take effect.

== Can't remove fglrx with dpkg (diversion issue) ==

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:
<pre>dpkg-divert: mismatch on divert-to
when removing `diversion of /usr/lib/libGL.so.1.2 to /usr/share/fglrx/diversions/libGL.so.1.2 by xorg-driver-fglrx'
found `diversion of /usr/lib/libGL.so.1.2 to /usr/lib/fglrx/libGL.so.1.2.xlibmesa by xorg-driver-fglrx'</pre>
then:
sudo dpkg-divert --remove /usr/lib/libGL.so.1.2

== This module/version combo is already installed ==

If you get this error-message, simply uninstall the previous version before installing the new one with:
sudo dkms remove -m fglrx --all

== New kernel installed? ==
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:
sudo dkms build -m fglrx -k `uname -r`
sudo dkms install -m fglrx -k `uname -r`

if amdcccle doesn't work and says Identifier is not a valid word. Use lower case letter in xorg.conf
[[Category:Installation Documentation]]

== amdconfig not found after installation ==
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:
<pre>amdconfig: command not found</pre>
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
ls /usr/lib/fglrx/bin
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
update-alternatives --get-selections | grep gl_conf
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
sudo update-alternatives --set gl_conf /usr/lib/fglrx/ld.so.conf
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:
sudo update-alternatives --auto gl_conf
After that, the alternatives should automatically be configured correctly when the graphics driver .debs are installed.

== "update-alternatives: error" during install ==
During installation you may receive the following message:
<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>
This can be easily solved by creating directory "drivers" under /usr/lib/xorg/modules/
sudo mkdir /usr/lib/xorg/modules/drivers

== 'Can't exec "debian/rules": Permission denied at /usr/bin/dpkg-buildpackage line 507.' during deb generation ==
During installation you may receive the following message:
<pre>Can't exec "debian/rules": Permission denied at /usr/bin/dpkg-buildpackage line 507.</pre>
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.
A workaround can be found here: [http://serialized.net/2010/03/getting-around-tmpfs-noexec-problems/]

== Black screen after uninstalling old amd drivers ==
Start you computer in recovery mode and exit to root shell.
Remount your partitions in rw mode:
mount -rw -o remount /
...
Go to your download directory and proceed with building and installing the drivers in recovery mode.
All should be fine after a reboot.

== References ==

<references/>

Hardware

2012-06-21T17:37:54Z

94.23.1.28: ywBMTMcRxXVrI

, I don't think you can do anything to fend off the atcktas. I don't think you got attacked because of something you did, but because lots of people admire you and your work. That's apparently enough for some people to hate you. Only by unpassionating your readers, can you hope to actually stop the haters. I hope you will reject that option., demi lovato naked, DD, avril lavigne porn, :]]], sasha alexander nude, 86491, katrina kaif nude pics, oyoda, elisha cuthbert naked, >:-[[[, denise richards naked, cabjte, emma stone naked, xcj, kelly brook naked, 80820, maggie gyllenhaal nude, =P, mariah carey sex tape, 395, kim kardashian nude pics, tfby, anne hathaway nude, 640, alice eve naked, 0240, diane kruger nude, >:-[, |

Mandriva

2012-06-21T17:22:25Z

94.23.1.28: KNmjQOsQuHIqKi

Tapez votre commentaire Vous poeuvz utiliser ces mots-cle9s HTML : <a> <abbr> <acronym> <blockquote> <cite> <code> <del> <q> <strike> var RecaptchaOptions = { theme : 'red', lang : 'fr' , tabindex : 5 }; #submit {display:none;}

8.29.6

2012-06-21T14:35:38Z

94.23.1.28: /* Additional Information */

pasliroour
ATI Linux fglrx driver version 8.29.6

Release date: September 20, 2006

== New Features ==

The ATI Proprietary Linux software driver introduces Linux Kernel 2.6.18 support.

== Resolved Issues ==

The following section provide a brief description of resolved issues with the latest version of the ATI Proprietary Linux driver. These include:
* Unreal Tournament 2004: Using the in-game options to change the desktop display resolution no longer results in the display failing to refresh properly when exiting the game. Further details can be found in topic number 737-23307
* SpecViewPerf: Running the sub-test UGS-04 no longer results in the operating system failing to respond. Further details can be found in topic number 737-23308

== Known Issues ==

The following section provides a brief description of known issues associated with the latest version of ATI Proprietary Linux driver. These issues include:
* Attempting to install the ATI Proprietary Linux driver on distributions that have updated certain 3D components outside of the stock XOrg 6.8.2 may result in the driver not initializing 3D applications properly. Further details can be found in topic number 737-20868
* A system hang may occur when attempting to resume from hibernation mode. Further details can be found in topic number 737-22059
* Loading the XVideo Extension on 64-bit Xorg 6.9+ systems causes the X Server to segfault on launch with ATI Radeon X1K products. Further details and the workaround can be found in topic number 737-22837
* Users with X Server X.org 7.1 can not play any video using XV. The ATI AVIVO Video adaptor is not present. Further details and the workaround can be found in topic number 737-22852

For further information and general help on driver or software installation, game issues, and more, visit the [https://support.ati.com/ics/support/default.asp?deptID=894&task=knowledge ATI FAQ website].

This is both sertet smart and intelligent.

== Links ==

* Download: [http://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-8.29.6.run 32-bit and 64-bit Unified Installer]
* Full Release Notes: [http://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/linux_8.29.6.html Release notes]
* [http://ati.amd.com/products/catalyst/linux.html ATI Proprietary Linux Driver FAQ]

[[Category:Releases]]

Fedora 16 Installation Guide

2012-06-21T13:48:54Z

94.23.1.28: /* Amd-driver-installer Compilation Problems on i686 Fedora 16 */

= Installing the Official AMD driver =

== Introduction ==

There are two methods to get the Official AMD driver installed on Fedora. The first is by running the amd-driver-installer package supplied by amd.com. This method is covered in the section "'''Official AMD Driver Package from Amd.com'''". The second is to use the rpm packages supplied by the rpm fusion repos. This method is covered in the section "'''Pre-built packages from RPMFusion'''".

The sections titled '''Amd-driver-installer Compilation Problems on x86_64 Fedora 16''' and '''Amd-driver-installer Compilation Problems on i686 Fedora 16''' are subject to being resolved by Catalyst updates and therefore may not be relevant to installations after Catalyst version 12.4.

== Requirements ==

The Amd-driver-installer from Amd.com will work best in most cases if there is no xorg.conf file present before you begin the installation process. Move any existing xorg.conf files out of the /etc/X11 directory before installation.

You will need at least version 11.11 (or greater) of the ATI driver for Fedora 16, earlier versions will not work with the version of Xorg that F16 ships with.

For Catalyst 12.5 or above, a Radeon HD5000 series (or greater) is required. Radeon HD 2000/3000/4000 series GPU's will not be recognized by 12.5 Catalyst and above.

=== Amd-driver-installer Compilation Problems on x86_64 Fedora 16 ===

''Note: This section '''applies directly''' to users using the Official amd-driver-installer package downloaded from amd.com''

Due to an upstream sourcecode change in the Fedora ''kernel-headers'' package, building of AMD's ''fglrx'' module will currently fail with kernels 3.2.9-2.fc16 and later. If you are getting the following error in your /usr/share/ati/fgrlx-install.log:

<pre>

make[1]: Entering directory `/usr/src/kernels/3.3.0-4.fc16.x86_64'
CC [M] /lib/modules/fglrx/build_mod/2.6.x/firegl_public.o
CC [M] /lib/modules/fglrx/build_mod/2.6.x/kcl_acpi.o
In file included from /usr/src/kernels/3.3.0-4.fc16.x86_64/arch/x86/include/asm/uaccess.h:575:0,
from include/asm-generic/termios.h:51,
from /usr/src/kernels/3.3.0-4.fc16.x86_64/arch/x86/include/asm/termios.h:1,
from include/linux/termios.h:5,
from include/linux/tty.h:41,
from include/linux/vt_kern.h:11,
from /lib/modules/fglrx/build_mod/2.6.x/kcl_acpi.c:35:
/usr/src/kernels/3.3.0-4.fc16.x86_64/arch/x86/include/asm/uaccess_64.h: In function ‘copy_from_user’:
/usr/src/kernels/3.3.0-4.fc16.x86_64/arch/x86/include/asm/uaccess_64.h:57:7: error: called object ‘2’ is not a function
make[2]: *** [/lib/modules/fglrx/build_mod/2.6.x/kcl_acpi.o] Error 1
make[1]: *** [_module_/lib/modules/fglrx/build_mod/2.6.x] Error 2
make[1]: Leaving directory `/usr/src/kernels/3.3.0-4.fc16.x86_64'
make: *** [kmod_build] Error 2
build failed with return value 2
[Error] Kernel Module : Failed to compile kernel module - please consult readme.
</pre>

Then this procedure is confirmed to work on 64 bit Fedora 16.

Open the file '''/usr/src/kernels/`uname -r`/arch/x86/include/asm/uaccess_64.h''' in a text editor.

On line 56 and 57 you will see:

<pre>
else
WARN(1, "Buffer overflow detected!\n");
</pre>

Comment this out so it reads:

<pre>
// else
// WARN(1, "Buffer overflow detected!\n");
</pre>

After saving this edit, if you have previously run amd-driver-installer unsuccessfully, you will need
to run /usr/share/ati/fgrlx-uninstall.sh to reset the system to previous starting conditions. Now follow
the procedure in the section below titled "Official AMD Driver Package from Amd.com".

* Reference: http://forums.fedoraforum.org/showthread.php?t=277547

TYVM you've solved all my pbroelms

=== Multiple Monitor Setups ===

If you have an existing multiple monitor setup, move your existing xorg.conf to a safe place. Let amd-driver-installer generate a fresh working xorg.conf file for you based on what it probes from EDID monitor info. If you are having difficulties after generating a new xorg.conf, use your old xorg.conf as a reference and transfer sections of that file as needed to the new one.

Here are some resources for those having difficulty getting their multiple monitors running:

* http://www.thinkwiki.org/wiki/Xorg_RandR_1.2
* http://wiki.debian.org/XStrikeForce/HowToRandR12
* aticonfig --help
* One of the [[Ubuntu]] guides on this Wiki.
* AMD's own Catalyst documentation

If you need to start with a clean slate and all your monitors are connected, you can force a fresh xorg.conf to be generated taking into account the monitors present:

<pre>
su -
aticonfig --initial -f
</pre>

== Pre-built packages from RPMFusion ==

''Note: This section '''does not''' apply to users using the Official amd-driver-installer package downloaded from amd.com''

'''RECOMMENDED METHOD'''

This is easier than manually building the driver from AMD as you don't need to worry about passing kernel options via GRUB2, configuring DKMS, rebuilding the kernel module every time you do a kernel upgrade, or cleaning up any mess if you want to remove the driver.

=== Clean up previous Offical AMD driver installation ===

If you're coming from the Official AMD driver to RPMFusion's AMD driver, you'll need to reinstall the ''mesa-libGL'' package as the Official AMD driver installation changes files it contains.

<pre>
su -
yum reinstall mesa-libGL
</pre>

=== Other issues before install driver ===
On Acer Aspire 722 (A0722) with Radeon HD 6290 (and i suppose on other machines with the same card) you must disable SELinux or the follow error will occured :
<pre>
SELinux is preventing gnome-session-c from execmod access on the file /usr/lib/dri/fglrx_dri.so. For complete SELinux messages run sealert -l <SELinux alert id>
</pre>
To disable SELinux open /etc/selinux/config file as root and set SELINUX to disabled (SELINUX=disabled).
After that driver will work as expected. 
Note: Disabling SELinux is not a very good idea. It's better to just modify the policy, by running these two commands (as root):
<pre>semanage fcontext -a -t textrel_shlib_t '/usr/lib/dri/fglrx_dri.so'
restorecon -v '/usr/lib/dri/fglrx_dri.so'</pre>

'''glxinfo'''
<pre>
direct rendering : Yes
...
OpenGL vendor string : Advanced Microd Devices Inc.
OpenGL render string : AMD Radeon HD 6290 Graphics
...
</pre>

=== Setup RPMFusion ===

There are instructions on http://www.rpmfusion.org/ but this should do it.

<pre>
su -
rpm -Uvh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm
</pre>

=== Install Catalyst driver packages ===

This procedure is the same for 32-bit and 64-bit, yum will automatically install the correct driver and libs for your architecture.

<pre>
su -
yum install akmod-catalyst xorg-x11-drv-catalyst xorg-x11-drv-catalyst-libs
</pre>

''' 32-bit Libraries on 64-bit OS'''

If you want to play 32-bit games on a 64-bit Fedora installation, you will need to install the 32-bit libraries in addition to the above step.

<pre>
su -
yum install xorg-x11-drv-catalyst-libs.i686
</pre>

''' Kernel module packages '''

Note that there are individual ''kmod-catalyst-'' packages in RPMFusion which supply kernel modules for specific Fedora kernel versions. If you use these and you upgrade the kernel without upgrading the ''kmod-catalyst-'' package, loading the proprietary driver will fail and you'll revert back to the Free ''radeon'' graphics driver. Sometimes there is a day or so between Fedora upgrading their kernel and RPMFusion building a new ''kmod-catalyst-'' package.

The ''akmod-catalyst'' package we installed above automatically builds a new kernel module at boot-time when the kernel is upgraded, so you'll never have to worry about this.

== Official AMD Driver Package from Amd.com==

''Note: This section '''applies directly''' to users using the Official amd-driver-installer package downloaded from amd.com''

=== Installation Prep for Amd-Driver-Installer ===

The script from AMD builds the kernel module and a set of modules for XOrg. The Official AMD installer requires some development packages to be installed:

<pre>
su -
yum install kernel-devel kernel-headers gcc gcc-c++
</pre>

There can be only one copy of ''kernel-devel'' and it needs to match the running kernel. Same applies to
''kernel-headers''. "Yum update" will always ensure that there's one latest copy of ''kernel-headers'', but
it does not do that for ''kernel-devel'', so you need to look at that yourself. The running kernel
should be the latest one available on the update repos. Check your current kernel version with:

<pre>
uname -a
</pre>

Check all installed kernel packages with

<pre>
su -
rpm -qa | grep kernel
</pre>

Remove any ''kernel-devel'' packages which do not match the latest installed kernel version. Example:

<pre>
su -
rpm -ev --nodeps kernel-devel-3.2.9-1.fc16.x86_64
</pre>

Note we are careful to specify the exact package name that was given to us by the rpm command above.

Boot into the latest kernel before continuing. Building the module on a kernel which you don't have ''-devel'' packages for will fail. Building the module on one kernel then booting into another will result in the compiled module not working.

Most users that are installing the Official Amd-driver-installer are looking for maximum performance with direct rendering
and OpenGL performance. Amd-driver-installer requires that Mesa libraries be in place before it's installed, as it replaces
some of those libraries. Therefore if you are a Crossover or Wine user, the mesa lib set will need to be in place before you
run the installer. The following is a working example pulled from a known-good Fedora 16 x86_64 platform running Crossover:

<pre>
su -
yum install mesa-dri-filesystem.i686 mesa-libGL.x86_64 mesa-dri-drivers.x86_64 mesa-libGL.i686
mesa-dri-filesystem.x86_64 mesa-libEGL.x86_64 mesa-dri-drivers.i686 mesa-libGLU.x86_64
</pre>

Note that Crossover and Wine are 32 bit and therefore require i686 mesa libs in conjunction with the 64 bit versions.

From here, you should be ready to run the Official Amd-driver-installer.

=== Download driver ===

Download the driver for your particular card from http://support.amd.com/

It will look similar to: ''amd-driver-installer-XX-X-XXX.XXX_XX.run''.

=== Install driver ===

Run the file as root in the ''sh'' shell.

<pre>
su -
chmod 700 amd-driver-installer-XX-X-XXX.XXX_XX.run
sh ./amd-driver-installer-XX-X-XXX.XXX_XX.run
</pre>

Select the default install, do not generate distribution packages.

=== Confirming Installation ===

Check the build install log:

<pre>tail /usr/share/ati/fglrx-install.log</pre>

You should see data confirming the module build worked:

<pre>build succeeded with return value 0
duplicating results into driver repository...
done.</pre>

=== Uninstalling Official AMD driver ===

Run AMD's uninstall script:

<pre>
su -
sh /usr/share/ati/fglrx-uninstall.sh
</pre>

The following steps are not strictly required because the amd-driver-installer is written to put all files back as they were before the install. One set of files that amd-driver-installer alters is the mesa library set. To be sure of a mint-condition installation (especially if you are upgrading to the next Official driver version) reinstall the following package:

<pre>
su -
yum reinstall mesa-libGL
</pre>

For those running Wine or Crossover from Codeweavers.com, the following command will reinstall all the mesa libraries that (should) be on your system. This example is for users running Wine/Crossover on a 64 bit system:

<pre>
su -
yum reinstall mesa-dri-filesystem.i686 mesa-libGL.x86_64 mesa-dri-drivers.x86_64 mesa-libGL.i686
mesa-dri-filesystem.x86_64 mesa-libEGL.x86_64 mesa-dri-drivers.i686 mesa-libGLU.x86_64
</pre>

At this point you should be prepped to start a new amd-driver-installer session to get the latest Fglrx version.

= Troubleshooting =

In the event you install the driver and are greeted with a blank screen or corrupted video signal when starting X, you are able to manually disable the Free Software ''radeon'' driver to troubleshoot.

There are two methods to disable radeon module. The first is a two-step process and the other approach is listed below.

''Approach #1:''

1) Edit the /etc/modprobe.d/blacklist.conf and add radeon to the list.

2) Run the following:

<pre>
su -
/sbin/new-kernel-pkg --package kernel --mkinitrd --dracut --depmod --install $(uname -r)
</pre>

That's it. This will generate a new initramfs that does not have radeon built in. This method has the advantage of not affecting kernel mode setting as well as not needing any grub edits. On the next boot, the radeon module should be gone. You can now reboot to console and execute steps in section above titled "''Official AMD Driver Package from Amd.com''"

''Approach #2:''

Turn your system off and on again. On the GRUB boot screen, press '''e''' to edit the default boot entry, scroll down to the kernel line (which begins ''linux''), then press '''e''' again to edit the line.

Add the entries '''radeon.modeset=0 blacklist=radeon''' to the end. For example, if your kernel line is

<pre>linux /vmlinuz-3.2.9-1.fc16.x86_64 LANG=en_US.UTF-8</pre>

we'll want to edit it so it is

<pre>linux /vmlinuz-3.2.9-1.fc16.x86_64 LANG=en_US.UTF-8 radeon.modeset=0 rdblacklist=radeon blacklist=radeon</pre>

These entries do the following:
* '''radeon.modeset=0''' disables "Kernel Mode Settting" for the Free Software driver (ie: the driver telling the kernel to setup the screen resolution, instead of XOrg doing it)
* '''rdblacklist=radeon blacklist=radeon''' stops the kernel from loading the Free Software ''radeon'' driver altogether

From here you can manually remove and reinstall the proprietary drivers, either with yum or with PackageKit's ''Add/Remove Software'' application, as desired.

Category:FeatureUseCase

2012-06-21T13:08:35Z

94.23.1.28: OMmFhThEUU

Seitan is coagulated wheat prtioen. I can see why this would confuse people used to using it, because while it *is* derived from wheat, it is pretty much pure gluten (prtioen) and wouldn't carry the same carb threat that other grain products would. It is not a super-processed food anyone could make it in their own kitchen by super-kneading dough until it is extremely rubbery and the starch and bran can be washed out. The texture is about like cheese curds, and it absorbs flavored readily.