FirePro W600 problem

FirePro W600 problem

[Andrey Germakovski]

[-- Attachment #1.1: Type: text/plain, Size: 214 bytes --]

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

Andrey

[-- Attachment #1.2: Type: text/html, Size: 2112 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: FirePro W600 problem

[Alex Deucher]

On Wed, Oct 8, 2014 at 4:41 PM, Andrey Germakovski
<germakovskia@ainfosec.com> 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.

Alex

Re: FirePro W600 problem

[Michel Dänzer]

On 14.10.2014 00:39, Alex Deucher wrote:
> On Wed, Oct 8, 2014 at 4:41 PM, Andrey Germakovski
> <germakovskia@ainfosec.com> 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änzer            |                  http://www.amd.com
Libre software enthusiast          |                Mesa and X developer

Re: FirePro W600 problem

[Alex Deucher]

On Tue, Oct 14, 2014 at 2:29 AM, Michel Dänzer <michel@daenzer.net> wrote:
> On 14.10.2014 00:39, Alex Deucher wrote:
>>
>> On Wed, Oct 8, 2014 at 4:41 PM, Andrey Germakovski
>> <germakovskia@ainfosec.com> 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?

Oh, right, 3.18.  Sorry.  Please try 3.18.

Alex
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel