Talk:Debian - Revision history

99.119.2.242: /* Oddness in "Jessie AKA TESTING Installation ..." subsection */ new section

2016-02-27T21:53:41Z

Oddness in "Jessie AKA TESTING Installation ..." subsection: new section

← Older revision		Revision as of 21:53, 27 February 2016
Line 34:		Line 34:

	The build instructions for 12.8 are what would have worked in earlier versions. But 12.8 unzips to amd-driver-installer-8.982-x86.x86_64.run so the build command should be reflecting this.		The build instructions for 12.8 are what would have worked in earlier versions. But 12.8 unzips to amd-driver-installer-8.982-x86.x86_64.run so the build command should be reflecting this.

			== Oddness in "Jessie AKA TESTING Installation ..." subsection ==

			Regarding ...

			''"Do you use debian or Just do things to feel important, there has been a working fglrx in the repo for along time and the latest one is in experimental with in a week or two"''.

			... Ad hominem trollishness at the start (directed at an undefined target) seems unnecessary/unproductive and the latter part makes vague chronological assertions without a point of reference.

			Someone knowledgeable may wish to pare it down or remove ... meh ... I went ahead and looked it up in synaptic via antiX 15.1 (with default Debian Jessie repos) and, yes, fglrx packages are there. I'll re-word into a more neutrally toned update note.

			—kevjonesin—

Mooninite at 00:40, 6 July 2013

2013-07-06T00:40:50Z

← Older revision		Revision as of 00:40, 6 July 2013
Line 1:		Line 1:
			{{Talkpages}}

	0. about wait & sleep modes on catalyst-12.10 and kernel-3.2.0		0. about wait & sleep modes on catalyst-12.10 and kernel-3.2.0
Line 33:		Line 34:

	The build instructions for 12.8 are what would have worked in earlier versions. But 12.8 unzips to amd-driver-installer-8.982-x86.x86_64.run so the build command should be reflecting this.		The build instructions for 12.8 are what would have worked in earlier versions. But 12.8 unzips to amd-driver-installer-8.982-x86.x86_64.run so the build command should be reflecting this.

	~~== Problems with multiple cards and multiple monitors ==~~

	~~When encountering problems under the following circumstances:~~

	~~1. Multiple monitors on one card AND a monitor attached to VGA port.~~
	~~2. More than one card.~~

	...you may encounter problems that the resolution of the first monitor on the first card (usually identified as "CRT-1") may (a) not be recognized by manufacturer/model and instead the "Default Monitor" setting be used, and (b) therefore the resolution be set to a different resolution (e.g. 1600x1200) no matter what the xorg.conf file says.

	~~If this happens, check if the log file '''/var/log/Xorg.0.log''' contains an entry like this one:~~

	~~'''(II) fglrx(0): Cannot get EDID information for CRT1'''~~

	~~...which may be followed later with:~~

	~~'''(II) fglrx(0): Output CRT1 connected'''~~

	~~'''(II) fglrx(0): Using user preference for initial modes'''~~

	~~'''(II) fglrx(0): Output CRT1 using initial mode 1600x1200'''~~

	The reason for this behavior seems to be either a timing problem during Xorg initialization (EDID info for CRT-1 not received quickly enough) or a problem with a dcc probe itself. A possible work-around is to not use the VGA connector (CRT-1) on the first card at all and use only the DVI and HDMI port (possibly with a HDMI-to-DVI adapter cable) and the problem disappears immediately (monitor gets recognized immediately and correct resolution is being used).

	~~To avoid confusion with the Xorg configuration, you may want to delete '''/etc/X11/xorg.conf''' file and use the following command to have it generated (assuming 2 monitors per card):~~

	~~''' prompt$ aticonfig --initial --adapter=all --heads=2'''~~

	This will create a complete and correct configuration file (you may want to change layout later) even if a VGA monitor is attached to the first card but that VGA monitor will not be recognized upon reboot.

174.7.35.210: /* Problems with multiple cards and multiple monitors */

2013-07-05T22:53:50Z