Talk:Ubuntu Oneiric Installation Guide
Other fixes that may not appropriate for the guide.
Unity 3D Slowness
In natty/oneiric ubuntu (11.04 + 11.10) some fglrx drivers and unity are extremely slow by default, it can be improved a lot :
1. via compizconfig settings manager, general set the refresh rate ( re-draw speed of compiz ) to the highest you can ( up to 200 ) and disable "auto detect refresh rate" ,
2. disable in OpenGL settings of compiz : vsync, but enable it ( "tear-free" ) in the Ati Control Panel
In the daily 12.04 build of today and fglrx from ubuntus own repo all this is no longer necessary, unity3d is finally very fast out of the box and "just works" wonderful. But for all earlier versions the above tweaks do a lot improvements.
a german hd4650 mobility , M96/ device id 0x9480 (1gb vram ) user
--184.108.40.206 14:47, 28 February 2012 (CST)
"Jittery" Video After Installing Manual ATI Drivers From AMD Website
I am 270% (down from 300%) new to Ubuntu, Video Settings and Mathematical Percentages. So if this is covered somewhere else, please excuse this post, I was unable to find those in my searches and I wanted to help.
In two installs of Ubuntu (11.10 and 11.04), after installing the drivers from ATI, the video would get choppy as though two interlaced streams were offset. When taking screenshots, the video looked normal (making asking for support difficult). After using this guide, I enabled Tear-Free video with no effect. Through a stroke of genius (dumb luck), I changed the image options to "use grpahics processor for scaling" (Catalyist Control Center > Display Manager > Display In Use > Adjustments) . After hitting apply, the problem was resolved.
Update Guide Suggestions
Suggestions that should be fixed/added/subtracted from the guide.
GDM is not being used any more in Ubuntu 11.10, instead LightDM has replaced it. Therefore the section "Slow Maximizing Windows/General 2D Slowness" is outdated.
Using "sudo aticonfig --set-pcs-str="DDX,EnableRandR12,FALSE"" is redundant as well. It either does not apply any more or it will be ignored anyway, judged by the xorg log.
When trying to completely remove fglrx, the package "xorg-driver-fglrx" can not be removed (any more?) because it's a virtual package. It can therefore be left out in the guide.
Things like these should not be just taken over without actually checking if it is still required. What is the point of creating a new page for a new distributing version if the contents is just being copied anyway? I bet there's plenty of other stuff that does not apply any more because of a new distro update or new driver versions. These things should be checked first before taking them over. Just copying might do more harm then good to a system. It might also unnecessarily reduce system performance.
Also. It has never been clear to me why this guide is going through all the trouble of creating .deb file of the proprietary driver. What's the point? Why make things more difficult for a user if he can just as well run the installer provided by ATI right away? I'd say stick to that and create a separate page explaining why and how to create the .deb files. This way the info does not have to keep duplicated every time and things become less complicated for the casual user because you're sticking to the essentials in the main guide.--Forage 12:10, 31 October 2011 (CDT)
(**Response to above) Thanks for pointing these things out. I wrote/edited a lot of the Ubuntu guide beginning with Lucid, and I "inherited" 2 obsolete tips you pointed out, so I wasn't exactly sure about them. I didn't like the thought of removing peoples' work if I wasn't 100% sure that it was obsolete/harmful. TBH, I personally don't use Ubuntu much anymore (and usually run it in Virtualbox when I do), so I didn't think about the lightdm thing. FWIW, I don't see those sections/commands as being too dangerous (though I'll definitely remove them). On the other hand, running the ati installer without building packages is dangerous because it doesn't properly handle libgl(x) alternatives (and there are other Debian policy violations too). It can easily leave inexperienced users with no X if they install a normal update of mesa (which overwrites the proprietary ATI version of libgl(x).so as a side effect). I'm personally not going to recommend that on a distro where a lot of users have no terminal experience/skill beyond copying and pasting commands.
The "manually install Catalyst" portion of the guide existed because Ubuntu would only provide one version of fglrx per release and leave it at that. With the advent of the fglrx-updates package to automatically get/install Catalyst updates, I'll probably recommend that (but I'm personally not going to remove the manual build in case users need it). I haven't used fglrx-updates yet, so give me a few days to play with it (or, better yet, someone who has more interet/experience can add that section). --Dtl131 15:06, 31 October 2011 (CDT)
On amd64, amdcccle crashes when clicking 'apply' after trying to set Multi-display desktop. Is there a work-around? Still broken with 11.12.
Root Privledges, Package Creation Unnecessary
Building a package doesn't require root permission. Instead this can be used:
./amd-driver-installer-12-2-x86.x86_64.run --buildpkg Ubuntu/oneiric
Hi, I had the 12.2 proprietary driver working really well. Unfortunately I fear a apt-get upgrade may have broken the driver, so I'm trying to upgrade the driver. I've followed the instructions to first remove the existing driver which seemed to work ok - cmd line suggested I autoremove a few packages in addition to the instruction, which I have done. I've downloaded the new 12.3 driver and get to the line, sudo sh ./amd-driver-installer-12-3-x86.x86_64.run --buildpkg Ubuntu/oneiric which fails. Follows is the last bit of the script before failure......
#Run the normal stuff dh binary-arch dh_auto_install -a -Nfglrx -Nfglrx-amdcccle dh_install -a -Nfglrx -Nfglrx-amdcccle dh_installdocs -a -Nfglrx dh_installchangelogs -a -Nfglrx dh_installexamples -a -Nfglrx dh_installman -a -Nfglrx dh_installcatalogs -a -Nfglrx dh_installcron -a -Nfglrx dh_installdebconf -a -Nfglrx dh_installemacsen -a -Nfglrx dh_installifupdown -a -Nfglrx dh_installinfo -a -Nfglrx dh_pysupport -a -Nfglrx dh_installinit -a -Nfglrx dh_installmenu -a -Nfglrx dh_installmime -a -Nfglrx dh_installmodules -a -Nfglrx dh_installlogcheck -a -Nfglrx dh_installlogrotate -a -Nfglrx dh_installpam -a -Nfglrx dh_installppp -a -Nfglrx dh_installudev -a -Nfglrx dh_installwm -a -Nfglrx dh_installxfonts -a -Nfglrx dh_installgsettings -a -Nfglrx dh_bugfiles -a -Nfglrx dh_ucf -a -Nfglrx dh_lintian -a -Nfglrx dh_gconf -a -Nfglrx dh_icons -a -Nfglrx dh_perl -a -Nfglrx dh_usrlocal -a -Nfglrx dh_link -a -Nfglrx dh_compress -a dh_fixperms -a dh_strip -a dh_makeshlibs -a objdump: debian/fglrx/usr/lib/pxpress/alt_ld.so.conf: File truncated objdump: debian/fglrx/usr/lib/pxpress/ld.so.conf: File format not recognized objdump: debian/fglrx/usr/lib/fglrx/alt_ld.so.conf: File truncated objdump: debian/fglrx/usr/lib/fglrx/ld.so.conf: File format not recognized debian/rules override_dh_shlibdeps make: Entering directory `/tmp/fglrx.0W1fVM' dh_shlibdeps -l/tmp/fglrx.0W1fVM/debian/fglrx/usr/lib/fglrx:/tmp/fglrx.0W1fVM/debian/fglrx/usr/lib32/fglrx -Xlib32 dpkg-shlibdeps: warning: debian/fglrx/usr/lib/fglrx/libAMDXvBA.so.1.0 contains an unresolvable reference to symbol dlsym: it's probably a plugin. dpkg-shlibdeps: warning: 21 other similar warnings have been skipped (use -v to see them all). dpkg-shlibdeps: warning: debian/fglrx/usr/lib/fglrx/bin/atieventsd contains an unresolvable reference to symbol XauFileName: it's probably a plugin. dpkg-shlibdeps: warning: debian/fglrx/usr/lib/fglrx/libGL.so.1.2 contains an unresolvable reference to symbol XOpenDisplay: it's probably a plugin. dpkg-shlibdeps: warning: 31 other similar warnings have been skipped (use -v to see them all). dpkg-shlibdeps: error: no dependency information found for /usr/share/ati/lib64/libQtCore.so.4 (used by debian/fglrx/usr/lib/fglrx/bin/amdnotifyui). dh_shlibdeps: dpkg-shlibdeps -Tdebian/fglrx.substvars debian/fglrx/usr/lib/fglrx/libAMDXvBA.so.1.0 debian/fglrx/usr/lib/fglrx/libatiadlxx.so debian/fglrx/usr/lib/fglrx/libfglrx_dm.so.1.0 debian/fglrx/usr/lib/fglrx/libXvBAW.so.1.0 debian/fglrx/usr/lib/fglrx/libamdocl64.so debian/fglrx/usr/lib/fglrx/libaticalcl.so debian/fglrx/usr/lib/fglrx/libaticaldd.so debian/fglrx/usr/lib/fglrx/libaticalrt.so debian/fglrx/usr/lib/fglrx/libatiuki.so.1.0 debian/fglrx/usr/lib/fglrx/libOpenCL.so.1 debian/fglrx/usr/lib/fglrx/libSlotMaximizerAg.so debian/fglrx/usr/lib/fglrx/libSlotMaximizerBe.so debian/fglrx/usr/lib/fglrx/libGL.so.1.2 debian/fglrx/usr/lib/fglrx/xorg/modules/amdxmm.so debian/fglrx/usr/lib/fglrx/xorg/modules/glesx.so debian/fglrx/usr/lib/fglrx/xorg/modules/extensions/libglx.so debian/fglrx/usr/lib/fglrx/xorg/modules/linux/libfglrxdrm.so debian/fglrx/usr/lib/fglrx/xorg/modules/drivers/fglrx_drv.so debian/fglrx/usr/lib/fglrx/dri/fglrx_dri.so debian/fglrx/usr/lib/fglrx/bin/amdnotifyui debian/fglrx/usr/lib/fglrx/bin/atieventsd debian/fglrx/usr/lib/fglrx/bin/aticonfig debian/fglrx/usr/lib/fglrx/bin/atiodcli debian/fglrx/usr/lib/fglrx/bin/atiode debian/fglrx/usr/lib/fglrx/bin/fgl_glxgears debian/fglrx/usr/lib/fglrx/bin/fglrxinfo returned exit code 2 make: *** [override_dh_shlibdeps] Error 2 make: Leaving directory `/tmp/fglrx.0W1fVM' make: *** [binary-arch] Error 2 dpkg-buildpackage: error: debian/rules binary gave error exit status 2 Removing temporary directory: fglrx-install.mMmVPT
any thoughts on how to fix this? Many thanks, Russ 220.127.116.11 12:35, 31 March 2012 (CDT)
Actually scrub this - it wasn't an update that screwed my existing driver but my SSD hardrive dying - had to reinstall from scratch anyway. --18.104.22.168 18:44, 3 April 2012 (CDT)