Difference between revisions of "Talk:Ubuntu Hardy Installation Guide"

From cchtml.com
Jump to: navigation, search
(ronhaziHtwpZ)
(32 intermediate revisions by 16 users not shown)
Line 1: Line 1:
==DKMS disaster with multiple kernels==
+
Hello  It's been three months since the Hardy Heron was relaesed,   How are you feeling about it now? Are you still using it, or were you just test-driving?Thanks
 
+
Hi all. A few days ago, i receieved a linux-image update form the repos, and since i was using a manually installed driver, i lost support for fglrx in the current kernel (2.6.24-18-generic). Trying to solve this issue manually, i bumped into a lot of problems, but in the end, all seemed to point to DKMS. on startx, fglrx complianed about "Multiple version found in DKMS, Unsure what to do. Resolve manually" and reverted to Mesa.
+
 
+
After some disappointing google, i found some threads in french on mandriva forums about a DKMS kernel mixup with more than one image installed. Since i had no experience with DKMS, i ended up uninstalling every kernel image prior to current, remove --purge dkms && install DKMS, and any trace of fglrx to get a clean slate to work on.
+
 
+
Then i used the "ubuntu method" for the first time, and it worked (only after i rememebered to enable the fglrx module i had blacklisted before, silly me), but got a little concerned aboput this esoteric kernel mixup using the manual method with recent kernel updates.
+
 
+
I wanted to put some notice in the How-to, but since i didn't have much patience and quickly reverted to the "clean slate and auto install" way, i didn't know how to explain it effectively.
+
 
+
Could someone lookup this up and see how to put it in the wiki? I'm not sure, but i think that something in the line of "If you are having problems getting X to start with fglrx, or fglrx complains about multiple versions in dkms, you should probably check your multiple kernel setup", but this hardly explains the issue, and i really don't know anything in more detail.
+
 
+
I hope someone will be able to chek into this. [[User:209.88.159.4|209.88.159.4]] 12:29, 5 June 2008 (CDT)
+
 
+
:UPDATE: seems to be fixed in the latest release: "#  The Linux kernel module is no longer installed to wrong location if the Linux kernel is updated. Further details can be found in topic number 737-34288". http://www2.ati.com/drivers/linux/catalyst_85_linux.html
+
 
+
Thanks for giving some information about this problem. I also experienced that the fglrx module was not loading correctly after a kernel update (2.6.24-18-generic). I also used the manual method to install fglrx (8.4.276). What I did was to remove the module in dkms, then add, rebuild and install for the current kernel. I think that before I ran the dkms commands below, that I already had fglrx.ko in:
+
/var/lib/dkms/fglrx/8.476/2.6.24-18-generic/i686/module/. I am not sure if was already installed /lib/modules/2.6.24-18-generic/updates/dkms.
+
 
+
The dkms commands I ran (depend on the module source still being in /usr/src/fglrx-8.476):
+
 
+
<pre>
+
sudo dkms remove -m fglrx -v 8.4.276
+
sudo dkms add -m fglrx -v 8.4.276
+
sudo dkms build -m fglrx -v 8.4.276
+
sudo dkms install -m fglrx -v 8.4.276
+
</pre>
+
 
+
Anyway, it is probably enough to just build and install the module with dkms. I could not find the 737-34288 article at ati.com, although it is mentioned there. The issue I had might be related, but I am not sure. Guess I have to install 8.5 and wait for a kernel update ;) [[User:Whocarez|Whocarez]] 12:02, 7 June 2008 (CDT)
+
 
+
==X RandR==
+
 
+
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
+
 
+
might this be related to my comment above about dkms and multiple versions? the symptons seem to be the same... [[User:209.88.159.4|209.88.159.4]] 12:30, 5 June 2008 (CDT)
+
 
+
== 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.  --[[User:Porter|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. --[[User:Compwiz18|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.  --[[User:Porter|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
+
 
+
 
+
==Additional xorg.conf Edits==
+
===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:
+
<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:
+
<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)
+
 
+
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 :)
+
(I'm always uneasy about directly editing wiki pages myself)
+
 
+
---
+
 
+
Thank you, this worked on my Hardy/x86_64 machine as well.
+
 
+
== Crashes with x86_64 and more that 2 gigs of RAM ==
+
 
+
It seems that the combination of fglrx, more than 2 gigs of RAM and certain motherboards will cause X to crash hard.  More details can be found here:
+
 
+
http://www.phoronix.com/forums/showthread.php?s=b76d9053dd37456a6c50e2588fb32b9b&t=7507
+
 
+
The workaround is to disable memory remapping in the motherboard bios.  Unfortunately, this also reduces the amount of memory accessible to the system.
+

Revision as of 19:10, 10 December 2012

Hello It's been three months since the Hardy Heron was relaesed, How are you feeling about it now? Are you still using it, or were you just test-driving?Thanks