Ubuntu Jaunty Installation Guide - Revision history

Mooninite: Protected "Ubuntu Jaunty Installation Guide": Excessive vandalism (‎[edit=autoconfirmed] (indefinite) ‎[move=autoconfirmed] (indefinite))

2013-01-29T21:17:01Z

Protected "Ubuntu Jaunty Installation Guide": Excessive vandalism (‎[edit=autoconfirmed] (indefinite) ‎[move=autoconfirmed] (indefinite))

Mooninite: Reverted edits by 88.36.56.194 (talk) to last revision by Mooninite

2013-01-29T21:16:38Z

Reverted edits by 88.36.56.194 (talk) to last revision by Mooninite

88.36.56.194: /* Installation */

2013-01-29T15:41:06Z

‎Installation

Mooninite: Protected "Ubuntu Jaunty Installation Guide": Excessive spamming ([edit=autoconfirmed] (expires 14:05, 10 January 2013 (UTC)) [move=autoconfirmed] (expires 14:05, 10 January 2013 (UTC)))

2012-12-10T14:05:44Z

Protected "Ubuntu Jaunty Installation Guide": Excessive spamming ([edit=autoconfirmed] (expires 14:05, 10 January 2013 (UTC)) [move=autoconfirmed] (expires 14:05, 10 January 2013 (UTC)))

Mooninite at 14:05, 10 December 2012

2012-12-10T14:05:38Z

164.67.204.73: /* This module/version combo is already installed */

2012-12-10T13:48:15Z

‎This module/version combo is already installed

207.104.28.181: /* Installing Open Source Edge Drivers */

2012-12-10T09:38:12Z

‎Installing Open Source Edge Drivers

Mooninite: Reverted edits by 189.75.11.29 (talk) to last revision by Mooninite

2012-11-04T16:27:29Z

Reverted edits by 189.75.11.29 (talk) to last revision by Mooninite

189.75.11.29: /* HOW TO REMOVE DRIVER */

2012-11-04T12:06:57Z

‎HOW TO REMOVE DRIVER

Mooninite: Protected "Ubuntu Jaunty Installation Guide": Excessive vandalism ([edit=autoconfirmed] (expires 00:02, 2 October 2012 (UTC)) [move=autoconfirmed] (expires 00:02, 2 October 2012 (UTC)))

2012-09-02T00:02:41Z

Protected "Ubuntu Jaunty Installation Guide": Excessive vandalism ([edit=autoconfirmed] (expires 00:02, 2 October 2012 (UTC)) [move=autoconfirmed] (expires 00:02, 2 October 2012 (UTC)))

@@ Line 259: / Line 259: @@
 = Issues =
-I'm gonna have to give the new driver a try. I have Beryl woknirg, but it occasionally hogs the cpu and doesn't settle back down, so any productivity must be done under Gnome. I've been having too many other random problems with fglrx, and I have still yet to get my tv-input woknirg under any driver. It's disappointing that what was once great hardware on Windoze is now buggy hardware on Ubuntu because of corporate stubbornness (ATI 9600 AIW, SB Audigy). Oh well, at least there are alternatives to choose from next time I buy new hardware.
+== Installation ==
 == Mesa drivers ==

@@ Line 259: / Line 259: @@
 = Issues =
-== Installation ==
+I'm gonna have to give the new driver a try. I have Beryl woknirg, but it occasionally hogs the cpu and doesn't settle back down, so any productivity must be done under Gnome. I've been having too many other random problems with fglrx, and I have still yet to get my tv-input woknirg under any driver. It's disappointing that what was once great hardware on Windoze is now buggy hardware on Ubuntu because of corporate stubbornness (ATI 9600 AIW, SB Audigy). Oh well, at least there are alternatives to choose from next time I buy new hardware.
-There are some system configurations on which '''none''' of the installation alternatives work with the latest 9.5 driver (please add; also please add if you got it to work in one of the listed setups):
-* Ubuntu 9.04 (x64 and i386) on x86_64 with Radeon HD4870X2 and 9.5 driver: Framebuffer error ("No valid linear framebuffer address"), garbled screen.
-** Working 9.04 (x64) on x86_64 with Radeon4870X2 and 9.4 driver: use 'aticonfig --initial -f --adapter=all'
-** Working 9.04 (x64) on x86_64 with Radeon4870X2 and 9.6 driver: use 'aticonfig --initial -f' (without adapter=all, if you only have one screen)
-* Ubuntu 9.04 (x64) on x86_64 with Radeon HD3870X2 and 9.5 driver: "No supported adapters detected."
-* Ubuntu 9.04 (x64) on x86 and x86_64 with Radeon HD4850X2: Framebuffer error, garbled screen.
-* Ubuntu 9.04 (x64) on x86_64 with Radeon HD4850: Framebuffer error, garbled screen (with automatic log-on, using the restricted drivers manager installation).
-* Ubuntu 9.04 (x64) on x86_64 with Radeon HD 3300 (790GX): garbled screen.
-**Working Radeon HD 3300 connected to an HDTV, I had a garbled screen before, I reinstalled Ubuntu, then follow manual steps closely. Reinstalled because I didn't know how to remove fglrx, but you may be able to avoid reinstalling by following fglrx complete removal in this guide.
-**Working 790GX (A790GMH/128M) with 9.5 driver after manual install (following install with envyng, which might be older version as of 25/5/09). Able to change display resolution which before was not working.
-**Working 790GX (MSI 790GX-G65): Now able to call System/Video Configuration which hang up. This driver also reduced the power consumption by 15 W (from 93 W down to 78 W). Thank you for that great installation guide.
-** Working Radeon HD 3450 connected to an HDTV on Kubuntu 9.04. Followed manual install of latest drivers (9.6) to the letter, rebooted, and works fully.
 == Mesa drivers ==

@@ Line 31: / Line 31: @@
 There's an ongoing debate about how and if the radeon and radeonhd drivers will be used in the future.  For more information, see http://wiki.x.org/wiki/RadeonFeature
-Well the slope is slippery for a resoan. I know people with 1600 1200 screens who can't get that resolution without using the binary nvidia driver. I know someone whose nvidia card fan will sound like a jet engine unless the binary driver is installed. I know people who can't use their dual head screens without the nvidia binary driver. It can be argued that in these cases the nv driver doesn't work. If ubuntu is going to ship with the driver on by default I guess I will point these people towards ubuntu and won't look back.My take is that I prefer free/open source drivers in the box and having to manually enable the drivers as it indicates that I can't go to ubuntu for support with problems arising from the binary driver (my binary driver problems are between me and the binary driver vendor). If you are enabling the drivers out of the box then ubuntu must take responsibility for the problems that arise from them. I don't know what your kernel devs are going to think about that but that is the extra burden you accept for happier users.Hopefully nvidia would respond to this step and provide engineers with nvidia addresses to look at (reply and fix!) nvidia related bugs in launchpad.Of course if nvidia are being invited to the party it seems unfair to leave out other binary driver vendors So long as responsibility is being accepted for bugs arising from binary drivers shipped by default (and those bugs are fixed) it is hard to argue with ubuntu's stance. It would be interesting to see if that will lead to ubuntu pushing things like a stable api in the kernel (or some glue shim to try and achieve the same results).
+= Installing Open Source Edge Drivers =
 = The Ubuntu way to install the Proprietary Drivers =
@@ Line 392: / Line 403: @@
 If dpkg really-really refuses to remove an older fglrx-package, it might be needed to edit /var/lib/dpkg/diversions and remove a few lines. This is a hack and should be avoided.
-A perfect reply! Thanks for taking the trbuole.
+== This module/version combo is already installed ==
 == New kernel installed? ==

@@ Line 392: / Line 392: @@
 If dpkg really-really refuses to remove an older fglrx-package, it might be needed to edit /var/lib/dpkg/diversions and remove a few lines. This is a hack and should be avoided.
-== This module/version combo is already installed ==
+A perfect reply! Thanks for taking the trbuole.
-−
-If you get this error-message, simply uninstall the previous version before installing the new one with:
-{{Box Terminal|
-sudo dkms remove -m fglrx -v 8.522 --all
-}}
 == New kernel installed? ==

@@ Line 31: / Line 31: @@
 There's an ongoing debate about how and if the radeon and radeonhd drivers will be used in the future.  For more information, see http://wiki.x.org/wiki/RadeonFeature
-= Installing Open Source Edge Drivers =
+Well the slope is slippery for a resoan. I know people with 1600 1200 screens who can't get that resolution without using the binary nvidia driver. I know someone whose nvidia card fan will sound like a jet engine unless the binary driver is installed. I know people who can't use their dual head screens without the nvidia binary driver. It can be argued that in these cases the nv driver doesn't work. If ubuntu is going to ship with the driver on by default I guess I will point these people towards ubuntu and won't look back.My take is that I prefer free/open source drivers in the box and having to manually enable the drivers as it indicates that I can't go to ubuntu for support with problems arising from the binary driver (my binary driver problems are between me and the binary driver vendor). If you are enabling the drivers out of the box then ubuntu must take responsibility for the problems that arise from them. I don't know what your kernel devs are going to think about that but that is the extra burden you accept for happier users.Hopefully nvidia would respond to this step and provide engineers with nvidia addresses to look at (reply and fix!) nvidia related bugs in launchpad.Of course if nvidia are being invited to the party it seems unfair to leave out other binary driver vendors So long as responsibility is being accepted for bugs arising from binary drivers shipped by default (and those bugs are fixed) it is hard to argue with ubuntu's stance. It would be interesting to see if that will lead to ubuntu pushing things like a stable api in the kernel (or some glue shim to try and achieve the same results).
-−
-These drivers are built regularly from the X.Org git repository.  So sometimes they work, sometimes they don't.  However, they have been stable for me, and are the only drivers that work for me.   The fglrx drivers hang my system, and the standard "radeon" driver does not support a 2560x1600 resolution.
-−
-To install:
-−
-First add the repository https://launchpad.net/~tormodvolden/+archive/ppa.  Instructions on how to do that are on that page.  Then update your packages using Update Manager, and then add the ''xserver-xorg-video-radeonhd'' package.  When you log in, you may be using the new driver, but you will probably still be using the radeon driver.  To switch to the radeonhd driver, add this to '''/etc/X11/xorg.conf''' :
-−
-<pre>Section "Device"
-	Identifier	"Default Device"
-	Driver		"radeonhd"
-EndSection</pre>
 = The Ubuntu way to install the Proprietary Drivers =

@@ Line 240: / Line 240: @@
 It is very important that you COMPLETELY remove the old driver which includes the config files because when upgrading without uninstalling the old driver I noticed even though the new driver installed and worked there were some annoying problems that I experienced but after I completely uninstalled the old driver then installed the new one, it worked perfectly.
-Not sure if you meant in 12.04 or 11.10. I've just booted into a Live CD for 12.04, so here are my diaetls for that. I'll post 11.10 in a minute or two when I reboot.Grub parameters, although I did boot with  nomodeset' enabled from the Live CD menu as well:GRUB_CMDLINE_LINUX_DEFAULT= quiet splash And my Kernel: Linux ubuntu 3.2.0-8-generic #15-Ubuntu SMP Wed Jan 11 13:57:44 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
+=HOW TO REMOVE DRIVER=
 =Tweaks=