Talk:Ubuntu Hardy Installation Guide: Difference between revisions

From cchtml.com
(My problems (and solutions) installing on x86_64)
 
m (Reverted edits by 139.130.97.74 (talk) to last revision by Mooninite)
 
(44 intermediate revisions by 17 users not shown)
Line 1: Line 1:
==X RandR==
{{Talkpages}}
 
Can we enable the fglrx on RandR and do not write any things on xorg.conf?
==packages vs. installer==
 
What is everyone's opinion on the build-packages method versus running the automated installer?
 
I think we should start having a section explaining the install procedure with the auto-installer to, as begun on this page.
 
--- Arand, 21:16, Sunday, 09 March 2008
:Please make necessary changes to make it look like the [[Ubuntu Gutsy Installation Guide]] so they are easy to read. --[[User:Mooninite|Mooninite]] 10:46, 10 March 2008 (CDT)
 
This was the most helpful and concise explanation I found anywhere. It helped me no end. Couple of things though. My system couldn't find a library even though I had it installed. It was only in lib32 and lib64 so I copied a link to the lib folder. This was libGL.so.1.
 
Importantly, this installed the proprietary drivers but still didn't give me the hardware acceleration I needed. By accident I found that adding Option "TexturedVideo" under the Driver "fglrx" worked perfectly.
 
Thank you to the author.
 
== Installation guide not working for 8.476 ==
 
Hi,
 
It seems to me that the driver installation guide of 8-4 (8.476) does not work on Ubuntu 8.04. Following step-by-step the guide (method 2), I allways end up with 8.473 installed and running (while the system contains only 8.476 packages). If all instances, packages and modules of driver 8.473 are manually purged before 8.476 installation, the whole process ends up with the nonfunctional 3D (using mesa driver)
 
--- Eugenio, 10:30(CET), Tuesday, 22th April 2008
 
Eugenio, I have only tested it on a fresh install of Hardy, with only the mesa driver installed previously.
I updated the guide to 8.476 and am worried that it fails on some machines.
 
--- ilcavero
 
Thanks for your effort to solve the problem. I've been also looking for the solution on my local Ubuntu forum. I've met the other Ubuntu 8.04 who encountered the exactly same problem. After a week of googling and searching we still have found no solution. However, I found some notices on the web and it says, that the problem will be hopefully solved with the release of ubuntu 8.04.1 on July 6th. On the other hand, the previous driver 8.3 (8.473) works pretty well and hence there is no urgent need to install 8.4.
 
-- Eugenio, 9:00(CET), Sunday 27th April 2008


== Cleanup ==
== Cleanup ==
Line 51: Line 18:
--- Eugenio, 10:45(CET), Monday, 12th May 2008
--- Eugenio, 10:45(CET), Monday, 12th May 2008


== Problem with vboxdrv and fglrx ==


==Additional xorg.conf Edits==
May it worth mention https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/284505/comments/14 at the bottom of the page ? I have been all day long looking for how to solve it!! :)
===AIGLX===
A while back, I think in feisty it was recommended to add
Option "AIGLX" "off"
to xorg.conf to get compiz to work.
This will need to be removed when removing xgl or the desktop will break.
 
== My problems (and solutions) installing on x86_64 ==
 
I've had a problem creating the package from the installer that I got from ATI's website. It complained about not finding libGL.so.1, but I didn't have any file such as <code>/usr/lib/libGL.*</code>
 
My solution was this: I extracted the files from the installer
<pre>sudo sh ati-driver-installer-8-5-x86.x86_64.run --extract driver</pre>
 
and copied over the files from the newly created directory
<pre>sudo cp driver/arch/x86_64/usr/X11R6/lib64/libGL.so.1.2 /usr/lib/libGL.so.1</pre>
 
I then tried to create the package again, but it didn't work because it complained it couldn't find libfglrx_gamma.so.1, so like before
<pre>sudo cp driver/arch/x86_64/usr/X11R6/lib64/libfglrx_gamma.so.1.0 /usr/lib/libfglrx_gamma.so.1</pre>


And then this worked:
--alejandro 18:24(GMT+1)
<pre>sudo sh ati-driver-installer-8-5-x86.x86_64.run --buildpkg Ubuntu/8.04</pre>


Another thing that didn't work for me was dpkg-ing the packages, copy & pasting from this guide didn't work, but giving the full file names (and not with asterisks) worked. In my case it was:
== DISABLED_MODULES="fglrx" ==
<pre>sudo dpkg -i --force-overwrite xorg-driver-fglrx_8.493.1-0ubuntu1_amd64.deb fglrx-kernel-source_8.493.1-0ubuntu1_amd64.deb fglrx-amdcccle_8.493.1-0ubuntu1_amd64.deb</pre>
I don't know if it's only on my system or if it's by-design in dpkg, but I think it should be made clearer in case other people have this problem.


My system: Asus M2A-VM HDMI with integrated X1250, AMD X2 64 and Ubuntu Hardy (8.04) (64 bits, obviously)
With 8-10 driver and Ubuntu 8.04 is no more necessary to disable fglrx in the restricted modules.
The package fglrx-modaliases_* , in fact, provides compatibility with Jockey and in the restricted drivers window, the driver appears as present and in use.
--[[Special:Contributions/85.18.14.45|85.18.14.45]] 16:31, 6 November 2008 (UTC)


p.s. A warning about the special case for 64 bit should be above the installation instructions, not below, as some people might follow step-by-step and not notice those instructions :)
== Hardy ==
(I'm always uneasy about directly editing wiki pages myself)
Quote: ..("hardy" is not a typo)..
You've put a big smile on my face - lolz :)

Latest revision as of 14:50, 13 December 2012

TALK PAGES ARE NOT SUPPORT FORUMS

If you require help with installing the AMD fglrx driver, please consider a web forum or mailing list.

Cleanup

I did a little cleanup and formatting, and clarified the configuration section in Method 2. I inserted a comment about TexturedVideo on the newer cards for Xv, as well. I hope nobody minds. --Porter 08:11PM EDT 29 April 2008

I've also done a little cleanup on method two. I removed some extra steps that were not needed and rephrased some of the text so that it flows better. I also changed some incorrect statements. --Compwiz18 07:56, 22 May 2008 (CDT)

Updating a manually installed driver

Would it be good to add some notes on how to update the driver when new releases are available. I'm a little unsure of this myself; is it as simple as building the packages as per the instructions and doing the usual sudo apt-get install or is there more to it?

There is no auto-update routine as of yet. Upgrading will require a simple download, build, and install per the existing method. --Porter 02:10PM EDT 06 May 2008

OK, thanks. I should also mention I did a manual install on a clean install of Kubuntu Hardy - everything is fine but the restricted drivers GUI tool (jockey-kde) notes that fglrx is "In Use" AND "enabled". Shouldn't be any need to panic :)

"In USE" and "ENABLED" is also shown by Restricted drivers manager in Gnome after using the second manual instalation method. However, the driver works fine.

--- Eugenio, 10:45(CET), Monday, 12th May 2008

Problem with vboxdrv and fglrx

May it worth mention https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/284505/comments/14 at the bottom of the page ? I have been all day long looking for how to solve it!! :)

--alejandro 18:24(GMT+1)

DISABLED_MODULES="fglrx"

With 8-10 driver and Ubuntu 8.04 is no more necessary to disable fglrx in the restricted modules. The package fglrx-modaliases_* , in fact, provides compatibility with Jockey and in the restricted drivers window, the driver appears as present and in use. --85.18.14.45 16:31, 6 November 2008 (UTC)

Hardy

Quote: ..("hardy" is not a typo).. You've put a big smile on my face - lolz :)