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

From cchtml.com
Jump to: navigation, search
m (Reverted edits by 139.130.97.74 (talk) to last revision by Mooninite)
 
(17 intermediate revisions by 11 users not shown)
Line 1: Line 1:
==Installing Support for an ATI Graphics card did not work==
+
{{Talkpages}}
  
excuse me, I am an absolute newby in Linux and Ubuntu.
+
== Cleanup ==
  
I have a PC with an ATI Fire GL2, which is an AGP graphics adapter. It is not recognized automaticallsy, so Ubuntu can not enter the graphical mode. Therefore I used the Alternate Installation CD, after the Live CD ended without graphics mode.
+
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
  
After installing in the text mode I followed the instructions on
+
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)
  
[http://wiki.cchtml.com/index.php/Ubuntu_Hardy_Installation_Guide]
+
== Updating a manually installed driver ==
  
Method 1 ("the ubuntu way"), to be exact.
+
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
  
I logged into a terminal and typed
+
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 :)
  
sudo apt-get update
+
"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.
sudo apt-get install linux-restricted-modules-generic restricted-manager
+
sudo apt-get install xorg-driver-fglrx
+
sudo depmod -a
+
  
During these commands, the computer had an internet connection and the message lines did not look like having failed.
+
--- Eugenio, 10:45(CET), Monday, 12th May 2008
  
Then I wanted to edit xorg.conf using
+
== Problem with vboxdrv and fglrx ==
  
sudo gedit /etc/X11/xorg.conf
+
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!! :)
  
but that did not work, because a graphical mode is not available - the reason to do this all.
+
--alejandro 18:24(GMT+1)
  
I found that there is another editor which works in the text mode so I typed:
+
== DISABLED_MODULES="fglrx" ==
  
sudo nano /etc/X11/xorg.conf
+
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)
  
I searched for a section "Device", below it was a line, that it is an autoconfigured device (I missed to note the exact line of the original xorg.conf). I left that line in the file and below it, I added:
+
== Hardy ==
 
+
Quote: ..("hardy" is not a typo)..
    Driver "fglrx"
+
You've put a big smile on my face - lolz :)
 
+
I quit nano saving the modified xorg.conf.
+
 
+
Then I executed the command
+
 
+
sudo aticonfig --initial -f
+
 
+
which gave the message: Uninitialized file found, configuring Using /etc/X11/xorg.conf
+
 
+
I do not know, if this indicates right or wrong!
+
 
+
Then I was not sure, if I should first reboot or do the test
+
 
+
fglrxinfo
+
 
+
so I did that first which yielded
+
 
+
Error: unable to display(null).
+
 
+
I concluded, that I should do the reboot. Doing so, Ubuntu did not enter a graphical mode.
+
 
+
I could just enter a terminal and check the fglrxinfo command again (giving the same sad result) and then I checked /etc/X11/xorg.conf. Now it looked like this:
+
 
+
...
+
 
+
Section "Monitor"
+
  Identifier "aticonfig-Monitor[0]"
+
  Option    "VendorName" "ATI Proprietary Driver"
+
  Option    "ModelName" "Generic Autodetecting Monitor"
+
  Option    "DPMS" "true"
+
EndSection
+
 
+
Section "Device"
+
  Identifier "aticonfig-Device[0]"
+
  Driver    "fglrx"
+
EndSection
+
 
+
Section "Screen"
+
  Identifier "aticonfig-Screen[0]"
+
  Device    "aticonfig-Device[0]"
+
  Monitor    "aticonfig-Monitor[0]"
+
  DefaultDepth  24
+
  SubSection "Display"
+
      Viewport 0 0
+
      Depth  24
+
  EndSubSection
+
EndSection
+
 
+
 
+
Whad did I do wrong and how to proceed to get the graphical mode with this adapter running?
+
 
+
--[[User:Melolontha|Melolontha]] 18:58, 19 October 2008 (UTC)
+

Latest revision as of 09: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.

Contents

[edit] 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)

[edit] 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

[edit] 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)

[edit] 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)

[edit] Hardy

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