From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?Michel_D=c3=a4nzer?= Subject: Re: FirePro W600 problem Date: Tue, 14 Oct 2014 15:29:22 +0900 Message-ID: <543CC2C2.901@daenzer.net> References: <5E6D2D8C499849489A8124B44A08854F12D61B25@AISXSV10.ainfosec.com> Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1252"; Format="flowed" Content-Transfer-Encoding: quoted-printable Return-path: Received: from mail.gna.ch (darkcity.gna.ch [195.226.6.51]) by gabe.freedesktop.org (Postfix) with ESMTP id F01736E07A for ; Mon, 13 Oct 2014 23:29:26 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: Alex Deucher , Andrey Germakovski Cc: "dri-devel@lists.freedesktop.org" List-Id: dri-devel@lists.freedesktop.org On 14.10.2014 00:39, Alex Deucher wrote: > On Wed, Oct 8, 2014 at 4:41 PM, Andrey Germakovski > wrote: >> FirePro W600 does not work with more than 4 monitors, >> >> >> >> After 5th monitor attached X acting very slow. >> >> >> >> Or if I call drmModeSetCrtc function 5 times one time for each of the >> monitors, it failing out > > I suspect you are running out of CPU accessible vram depending on your > configuration. There are patches for mesa and the kernel to allow the > use of non-CPU accessible vram for display buffers in kernel 3.17 and > mesa git so you might try a newer kernel and mesa. The kernel changes for that will only be in 3.18, right? -- = Earthling Michel D=E4nzer | http://www.amd.com Libre software enthusiast | Mesa and X developer