Editing Ubuntu Maverick Installation Guide

From cchtml.com

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 185: Line 185:
 
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.  
 
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.  
  
 +
=== Using a Newer control File ===
 
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.
 
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}}/
 
  $ cd ~/; mkdir catalyst{{Catalystversion}}; cd catalyst{{Catalystversion}}/
Line 192: Line 193:
 
  $ sudo mv /etc/ati/control ~/control.bak
 
  $ sudo mv /etc/ati/control ~/control.bak
 
  $ sudo cp driver/common/etc/ati/control /etc/ati
 
  $ sudo cp driver/common/etc/ati/control /etc/ati
 +
 +
If the above workaround causes issues, restore the original control file:
 +
 +
$ sudo mv ~/control.bak /etc/ati/control
 +
 +
=== Another Possible Fix ===
 +
 +
If you already have the newest Catalyst release, there is one more hack you can try to make the watermark go away. Write (or paste) the following commands in the terminal (Applications-> Accessores->Terminal)
 +
 +
  cd /etc/init.d/
 +
 +
then create a script which will remove the watermark:
 +
 +
  sudo gedit ati.sh
 +
 +
then paste the following:
 +
 +
  #!/bin/sh
 +
  DRIVER=/usr/lib/fglrx/xorg/modules/drivers/fglrx_drv.so
 +
  for x in $(objdump -d $DRIVER|awk '/call/&&/EnableLogo/{print "\\x"$2"\\x"$3"\\x"$4"\\x"$5"\\x"$6}'); do
 +
  sed -i "s/$x/\x90\x90\x90\x90\x90/g" $DRIVER
 +
  done
 +
 +
then, to make it possible to run the script, issue:
 +
 +
  sudo chmod +x ati.sh
 +
 +
and, as the last step, add it to autostart:
 +
 +
  sudo update-rc.d -f ati.sh start 1 0 6 .
 +
 +
that is it, reboot.
 +
 +
solution posted on [http://ubuntuforums.org/showthread.php?t=1614444&page=7 ubuntuforums] by jniklast and currently only tested on Ubuntu x64. See thread for additional info, and maybe to express your appreciation.
  
 
== Mesa drivers ==
 
== Mesa drivers ==

Please note that all contributions to cchtml.com are considered to be released under the Public Domain (see cchtml.com:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

Cancel Editing help (opens in new window)