Troubleshooting - Revision history

Mooninite: Protected "Troubleshooting": Excessive vandalism (‎[edit=autoconfirmed] (expires 19:11, 30 March 2013 (UTC)) ‎[move=autoconfirmed] (expires 19:11, 30 March 2013 (UTC)))

2013-03-16T19:11:02Z

Protected "Troubleshooting": Excessive vandalism (‎[edit=autoconfirmed] (expires 19:11, 30 March 2013 (UTC)) ‎[move=autoconfirmed] (expires 19:11, 30 March 2013 (UTC)))

Mooninite: Reverted edits by 63.138.193.130 (talk) to last revision by 192.139.30.199

2013-03-16T19:10:52Z

Reverted edits by 63.138.193.130 (talk) to last revision by 192.139.30.199

63.138.193.130: /* References */

2013-03-16T18:48:25Z

‎References

192.139.30.199: /* Installer Issues */

2013-02-15T19:12:55Z

‎Installer Issues

82.37.175.161 at 19:53, 26 January 2013

2013-01-26T19:53:58Z

18.18.0.227: /* January 22, 2013 - Catalyst 13.1 Install on Ubuntu 11.04 (natty) */

2013-01-22T16:34:50Z

‎January 22, 2013 - Catalyst 13.1 Install on Ubuntu 11.04 (natty)

18.18.0.227: /* Installer Issues */

2013-01-22T16:33:08Z

‎Installer Issues

Mooninite: Reverted edits by 64.22.124.230 (talk) to last revision by 68.216.101.226

2012-09-06T02:10:44Z

Reverted edits by 64.22.124.230 (talk) to last revision by 68.216.101.226

64.22.124.230: /* An Example of a working Xorg.conf */

2012-09-05T03:11:36Z

‎An Example of a working Xorg.conf

68.216.101.226: /* No high-resolution video modes available */

2012-09-03T00:09:00Z

‎No high-resolution video modes available

← Older revision		Revision as of 19:10, 16 March 2013
Line 566:		Line 566:
	}		}

−	JL, Yes I'm thinking of ruinnng the title vertically but I also like your idea of changing the color of the text to white. Now I have to figure out how.Thank you for pointing out the ad size. I didn't really test that one out before I put it there.I'm using the Abigail theme from VintageKin.com they have some great family history related themes. I totally recommend them if you are looking for a family history theme. There was another one that I also liked so if this one doesn't work out, I'll switch and see if that helps.I guess the theme doesn't have built-in navigation coding because the built in navigation isn't there.	+	==References==
		+	<references/>
		+
		+	[[Category:Installation Documentation]]
		+
		+
		+	[[Category:NeedsUpdating]]
		+	{{VCT}}

@@ Line 566: / Line 566: @@
+}
-==References==
+JL, Yes I'm thinking of ruinnng the title vertically but I also like your idea of changing the color of the text to white.  Now I have to figure out how.Thank you for pointing out the ad size.  I didn't really test that one out before I put it there.I'm using the Abigail theme from VintageKin.com    they have some great family history related themes.  I totally recommend them if you are looking for a family history theme.  There was another one that I also liked so if this one doesn't work out, I'll switch and see if that helps.I guess the theme doesn't have built-in navigation coding because the built in navigation isn't there.
-<references/>
-−
-[[Category:Installation Documentation]]
-−
-−
-[[Category:NeedsUpdating]]
-{{VCT}}

@@ Line 1: / Line 1: @@
 ==Installer Issues==
 When the installer fails to produce results, check the directory where the ati catalyst installer has been placed. If it contains international characters or spaces, weird errors will arise. (The issue has been reported to ATI some time ago, but even in the newest releases they seem to like to prefer to conserve the bug)
 ===== January 22, 2013 - Catalyst 13.1 Install on Ubuntu 11.04 (natty) =====

@@ Line 23: / Line 23: @@
 . Create sym link for the "#SRCOTHERARCH#" directory that the installer is expecting to find:
-    cd amd/srch
+    cd amd/arch
     ln -sf x86_64 '#SRCOTHERARCH#'

@@ Line 16: / Line 16: @@
    dpkg-buildpackage: error: debian/rules binary gave error exit status 2
-That '#SRCOTHERARCH#' looked a bit suspicious.
+That '#SRCOTHERARCH#' looked a bit suspicious. I found a directory arch/x86_64/etc/OpenCL/vendors with an "icd" file in it. I guessed that was what the installer was looking for.
 . I then extracted the files from the installer:
-sh amd-driver-installer-catalyst-13.1-linux-x86.x86_64.run --extract amd
+  sh amd-driver-installer-catalyst-13.1-linux-x86.x86_64.run --extract amd
 . Create sym link for the "#SRCOTHERARCH#" directory that the installer is expecting to find:

← Older revision		Revision as of 16:33, 22 January 2013
Line 2:		Line 2:
	When the installer fails to produce results, check the directory where the ati catalyst installer has been placed. If it contains international characters or spaces, weird errors will arise. (The issue has been reported to ATI some time ago, but even in the newest releases they seem to like to prefer to conserve the bug)		When the installer fails to produce results, check the directory where the ati catalyst installer has been placed. If it contains international characters or spaces, weird errors will arise. (The issue has been reported to ATI some time ago, but even in the newest releases they seem to like to prefer to conserve the bug)

		+	===== January 22, 2013 - Catalyst 13.1 Install on Ubuntu 11.04 (natty) =====
		+
		+	Just wanted to document my problems with this install and the workaround I came up with.
		+
		+	1. I got the installer from AMD (amd-driver-installer-catalyst-13.1-linux-x86.x86_64.run) and attempted this:
		+
		+	sh amd-driver-installer-catalyst-13.1-linux-x86.x86_64.run --buildpkg Ubuntu/natty
		+
		+	This failed with:
		+
		+	dh_install: fglrx missing files (arch/#SRCOTHERARCH#/etc/OpenCL/vendors/*.icd), aborting
		+	make: *** [binary-arch] Error 2
		+	dpkg-buildpackage: error: debian/rules binary gave error exit status 2
		+
		+	That '#SRCOTHERARCH#' looked a bit suspicious.
		+
		+	2. I then extracted the files from the installer:
		+
		+	sh amd-driver-installer-catalyst-13.1-linux-x86.x86_64.run --extract amd
		+
		+	3. Create sym link for the "#SRCOTHERARCH#" directory that the installer is expecting to find:
		+	cd amd/srch
		+	ln -sf x86_64 '#SRCOTHERARCH#'
		+
		+	4. Back up to the installer directory and retried the "buildpkg" step - this time it worked and created the three deb package files. I was then able to continue with the install as normal.

	==X Server Related Issues==		==X Server Related Issues==

@@ Line 390: / Line 390: @@
 Solved ! New ATI drivers conflict with kms. So you have to disable kms ( for example append "nomodeset" on your kernel boot line )
-Last time I explained how I inetallsd the xserver-xorg-video-intel driver from the X.org SWAT Launchpad PPA. This resulted in a performance increase and a fix for the swap-hogging problem. Behold, I was wrong about that last bit. Mock me behind the cut.It only seemed to have slowed it down. I'm talking about vanilla Jaunty kernel with:
+=== An Example of a working Xorg.conf ===
 === Sticky mouse cursor ===

@@ Line 390: / Line 390: @@
 Solved ! New ATI drivers conflict with kms. So you have to disable kms ( for example append "nomodeset" on your kernel boot line )
-=== An Example of a working Xorg.conf ===
+Last time I explained how I inetallsd the xserver-xorg-video-intel driver from the X.org SWAT Launchpad PPA. This resulted in a performance increase and a fix for the swap-hogging problem. Behold, I was wrong about that last bit. Mock me behind the cut.It only seemed to have slowed it down. I'm talking about vanilla Jaunty kernel with:
-Lots of trial and error changing Options to get Compiz-Fusion running under Mandriva 2008-2010.  X Server 1.6.5
-(Sadly, the 'drak' tools that come with Mandriva to configure are worthless.)
-−
-In this instance it was chosen to remove packaged drivers and install from .bin file from AMD/ATI.
-−
-Most Options were added per 'aticonfig -f --initial ... ...'.
-And the rest were added as needed.  Constantly checking '/var/log/Xorg.0.log' for errors and warnings.
-−
-<pre> Section "ServerLayout"
-        Identifier     "aticonfig Layout"
-        Screen      0  "aticonfig-Screen[0]-0" 0 0  # The extra zeros are necessary for some reason
-        Option         "AIGLX"
-EndSection
-−
-Section "Files"
-EndSection
-−
-Section "Module"
-        Load "dbe"
-        Load "v4l"
-        Load "extmod"
-        Load "type1"
-        Load "freetype"
-        Load "glx"
-        Load "dri"
-EndSection
-−
-Section "Monitor"
-        Identifier "aticonfig-Monitor[0]-0"
-        Option "VendorName" "Hewlett-Packard"
-        Option "ModelName" "HP D2845 Ergo 1600 21-inch Display"
-        HorizSync 31.5-95.0
-        VertRefresh 50.0-160.0
-        Option      "DPMS" "true"
-EndSection
-−
-Section "Device"
-        Identifier  "aticonfig-Device[0]-0"
-        Driver      "fglrx"
-        BusID       "PCI:1:0:0"
-        Option      "UseFastTLS" "2"
-        Option      "Textured2D" "on"
-        Option      "TexturedXrender" "off"
-        Option      "BackingStore" "on"
-        Option      "VideoOverlay" "off"
-        Option      "OpenGLOverlay" "off"
-EndSection
-−
-Section "Screen"
-        Identifier "aticonfig-Screen[0]-0"
-        Device     "aticonfig-Device[0]-0"
-        Monitor    "aticonfig-Monitor[0]-0"
-        DefaultDepth     24
-        SubSection "Display"
-                Viewport   0 0
-                Depth     24
-        EndSubSection
-EndSection
-−
-Section "Extensions"
-        Option      "Composite" "on"
-        Option      "RENDER" "on" # essential for proper window border rendering
-        Option      "DAMAGE" "on" # compiz-fusion calls for explicitly
-EndSection
-</pre>
-−
-Open for scrutiny and testing.
-−
 === Sticky mouse cursor ===

@@ Line 5: / Line 5: @@
 ==X Server Related Issues==
-=== No high-resolution video modes available ===
+This "free sharing" of information seems too good to be true. Like comnmusim.
-* Versions of the fglrx driver following 7.12 had problems with video resolutions higher than 1280 x 1024. The modes of the xorg.conf are simply ignored, and the server starts up e.g. with a resolution 1280 x 1024 (even if this resolution is not defined in xorg.conf). This is particularly a problem on LCD displays.
-* [http://ati.cchtml.com/show_bug.cgi?id=160 This bug] documents the problem; it is '''fixed''' since driver version 8.2
-* Looks like it reappeared again some version above ati-driver-installer-8-12-x86.x86_64.run . Version ati-driver-installer-9.2-x86.x86_64.run, and ati-driver-installer-9-4-x86.x86_64.run has this bug. At least on integrated HD3200 card.
 === No XVideo support on 690G integrated graphic chipset ===