Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #174347 > unrolled thread

Subject=Re: Re: Third Monitor Stopped Working

Back to article view | Back to linux.debian.user

Contents

  Subject=Re: Re: Third Monitor Stopped Working "Barak A. Pearlmutter" <barak@pearlmutter.net> - 2016-11-08 16:40 +0100
    Re: Subject=Re: Re: Third Monitor Stopped Working deloptes <deloptes@gmail.com> - 2016-11-08 20:50 +0100
      Re: Subject=Re: Re: Third Monitor Stopped Working Felix Miata <mrmazda@earthlink.net> - 2016-11-09 00:00 +0100
        Re: Subject=Re: Re: Third Monitor Stopped Working Mark Fletcher <mark27q1@gmail.com> - 2016-11-09 00:20 +0100
        Re: Subject=Re: Re: Third Monitor Stopped Working deloptes <deloptes@gmail.com> - 2016-11-09 01:40 +0100
          Re: Subject=Re: Re: Third Monitor Stopped Working Felix Miata <mrmazda@earthlink.net> - 2016-11-09 02:00 +0100
            Re: Subject=Re: Re: Third Monitor Stopped Working deloptes <deloptes@gmail.com> - 2016-11-09 08:20 +0100
              Re: Subject=Re: Re: Third Monitor Stopped Working Felix Miata <mrmazda@earthlink.net> - 2016-11-09 10:10 +0100
                Re: Subject=Re: Re: Third Monitor Stopped Working deloptes <deloptes@gmail.com> - 2016-11-09 19:10 +0100

#174347 — Subject=Re: Re: Third Monitor Stopped Working

> The X server may need a little more explicit configuration:

Thanks, that sounded like a good idea.

But it didn't work either for a new size or even when I give a size
which was the same as the default size:

$ cat /etc/X11/xorg.conf
Section "Screen"
    Identifier "TarskTripleTrouble"
    SubSection "Display"
        Virtual 8192 8192
    EndSubSection
EndSection

The server fails to come up, with the tail of
~/.local/share/xorg/Xorg.0.log reading

[   621.616] (II) modeset(0): Using default gamma of (1.0, 1.0, 1.0)
unless otherwise stated.
[   621.616] (==) modeset(0): DPI set to (96, 96)
[   621.616] (II) Loading sub module "fb"
[   621.616] (II) LoadModule: "fb"
[   621.616] (II) Loading /usr/lib/xorg/modules/libfb.so
[   621.616] (II) Module fb: vendor="X.Org Foundation"
[   621.616] compiled for 1.18.4, module version = 1.0.0
[   621.616] ABI class: X.Org ANSI C Emulation, version 0.4
[   621.616] (II) UnloadModule: "fbdev"
[   621.616] (II) Unloading fbdev
[   621.616] (II) UnloadSubModule: "fbdevhw"
[   621.616] (II) Unloading fbdevhw
[   621.616] (II) UnloadModule: "vesa"
[   621.616] (II) Unloading vesa
[   621.616] (==) Depth 24 pixmap format is 32 bpp
[   621.680] (==) modeset(0): Backing store enabled
[   621.680] (==) modeset(0): Silken mouse enabled
[   621.680] (II) modeset(0): RandR 1.2 enabled, ignore the following
RandR disabled message.
[   621.680] (==) modeset(0): DPMS enabled
[   621.680] (II) modeset(0): [DRI2] Setup complete
[   621.681] (II) modeset(0): [DRI2]   DRI driver: i965
[   621.681] (II) modeset(0): [DRI2]   VDPAU driver: i965
[   621.721] (EE) modeset(0): failed to set mode: No space left on device
[   621.721] (EE)
Fatal server error:
[   621.721] (EE) AddScreen/ScreenInit failed for driver 0
[   621.721] (EE)
[   621.721] (EE)

[toc] | [next] | [standalone]

#174373

Barak A. Pearlmutter wrote:

> [ 621.721] (EE) modeset(0): failed to set mode: No space left on device

self explaining

[toc] | [prev] | [next] | [standalone]

#174396

deloptes composed on 2016-11-08 20:45 (UTC+0100):

> Barak A. Pearlmutter wrote:

>> [ 621.721] (EE) modeset(0): failed to set mode: No space left on device

> self explaining

What device???
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

  Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[toc] | [prev] | [next] | [standalone]

#174400

On Tue, Nov 08, 2016 at 05:59:25PM -0500, Felix Miata wrote:
> deloptes composed on 2016-11-08 20:45 (UTC+0100):
> 
> >Barak A. Pearlmutter wrote:
> 
> >>[ 621.721] (EE) modeset(0): failed to set mode: No space left on device
> 
> >self explaining
> 
> What device???
> -- 

Yes, I have to say that is what went through my head when I saw that 
error message too. That no space left on device message is usually 
talking about a storage device like a hard disk -- and why would a hard 
disk be involved in setting the display mode??? Sounds almost 
Microsoft... yuck!

Sorry I am not able to help, but perhaps the sympathy / validation will 
be worth something.

Mark

[toc] | [prev] | [next] | [standalone]

#174402

Felix Miata wrote:

> deloptes composed on 2016-11-08 20:45 (UTC+0100):
> 
>> Barak A. Pearlmutter wrote:
> 
>>> [ 621.721] (EE) modeset(0): failed to set mode: No space left on device
> 
>> self explaining
> 
> What device???

Barak did not say what video card/chip he has, but this comes in conjunction
to NVidia

https://bugs.freedesktop.org/show_bug.cgi?id=94577

https://devtalk.nvidia.com/default/topic/928743/linux/cannot-start-x-from-february-2016-nvidia-optimus/

regards

PS: Self explaining is that the error needs to be traced.

[toc] | [prev] | [next] | [standalone]

#174403

deloptes composed on 2016-11-09 01:31 (UTC+0100):

> Felix Miata wrote:

>> deloptes composed on 2016-11-08 20:45 (UTC+0100):

>>> Barak A. Pearlmutter wrote:

>>>> [ 621.721] (EE) modeset(0): failed to set mode: No space left on device

>>> self explaining

>> What device???

> Barak did not say what video card/chip he has, but this comes in conjunction
> to NVidia

lspci output provided included only one Intel line.

> https://bugs.freedesktop.org/show_bug.cgi?id=94577

> https://devtalk.nvidia.com/default/topic/928743/linux/cannot-start-x-from-february-2016-nvidia-optimus/

What did you see in OP to suggest poster has Optimus?
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

  Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[toc] | [prev] | [next] | [standalone]

#174405

Felix Miata wrote:

> deloptes composed on 2016-11-09 01:31 (UTC+0100):
> 
>> Felix Miata wrote:
> 
>>> deloptes composed on 2016-11-08 20:45 (UTC+0100):
> 
>>>> Barak A. Pearlmutter wrote:
> 
>>>>> [ 621.721] (EE) modeset(0): failed to set mode: No space left on
>>>>> [ device
> 
>>>> self explaining
> 
>>> What device???
> 
>> Barak did not say what video card/chip he has, but this comes in
>> conjunction to NVidia
> 
> lspci output provided included only one Intel line.
> 
>> https://bugs.freedesktop.org/show_bug.cgi?id=94577
> 
>>
https://devtalk.nvidia.com/default/topic/928743/linux/cannot-start-x-from-february-2016-nvidia-optimus/
> 
> What did you see in OP to suggest poster has Optimus?

I did not see the original post - I looked for it, but perhaps I missed it.
Perhaps OP needs a recent intel driver

regards

[toc] | [prev] | [next] | [standalone]

#174411

deloptes composed on 2016-11-09 08:15 (UTC+0100):

> Felix Miata wrote:

>> What did you see in OP to suggest poster has Optimus?
>
> I did not see the original post - I looked for it, but perhaps I missed it.

https://lists.debian.org/debian-user/2016/11/msg00236.html

 > Perhaps OP needs a recent intel driver

http://www.phoronix.com/scan.php?page=news_item&px=Ubuntu-Debian-Abandon-Intel-DDX 
suggests it's dying. Last official (upstream) Intel driver update was 
2.99.917 23 months ago.

But maybe the modesetting driver has a problem with more than two displays. I 
can't recall ever seeing "No space left on device" in any Xorg.#.log before.

I now suspect the problem is that the modesetting driver is limited to 8192 X 
8192, and he has 3840 + 3840 + 1920 = 9600, and that points out the "device" 
that is "out of space" might be the framebuffer? Maybe indeed his solution is 
the Intel driver's 32767 X 32767 buffer. Looks to me like moving his 
1920x1200 under or over one of the other two would light it up with the 
modesetting driver but to keep them all side by side would indeed require the 
intel driver instead of the new in Stretch modesetting default.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

  Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[toc] | [prev] | [next] | [standalone]

#174434

Felix Miata wrote:

> I now suspect the problem is that the modesetting driver is limited to
> 8192 X 8192, and he has 3840 + 3840 + 1920 = 9600, and that points out the
> "device" that is "out of space" might be the framebuffer? Maybe indeed his
> solution is the Intel driver's 32767 X 32767 buffer. Looks to me like
> moving his 1920x1200 under or over one of the other two would light it up
> with the modesetting driver but to keep them all side by side would indeed
> require the intel driver instead of the new in Stretch modesetting
> default.

Yes this sound plausible. I use Intel with two external monitors, but they
are both 1920 max.

He can try with sizes in the given range and see if it works.

regards

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web