[Bug 107919] New: RandR unable to set Screen Size when using Intel+nouveau

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]<

 



Bug ID 107919
Summary RandR unable to set Screen Size when using Intel+nouveau
Product xorg
Version unspecified
Hardware Other
OS All
Status NEW
Severity normal
Priority medium
Component Driver/nouveau
Assignee nouveau@lists.freedesktop.org
Reporter main.haarp@gmail.com
QA Contact xorg-team@lists.x.org

I am using a Thinkpad W530 which features an Intel GPU (Ivy Bridge) hooked up
to the internal LCD and an Nvidia K2000M (NVE7/GK107) hooked up to the
DisplayPorts.

Gentoo Linux
Kernel: 4.14.65
xorg-server-1.19.5
xf86-video-intel-2.99.917_p20180214
xf86-video-nouveau-1.0.15


Both GPUs drive outputs via "xrandr --setprovideroutputsource nouveau Intel".
Under these conditions, changing monitor layouts works once. Then, when the
laptop is suspended and brought to a different workplace with a different
monitor layout, most subsequent xrandr calls fail. RRSetScreenSize refuses to
work. Example:

    xrandr --output LVDS1 --mode 1920x1080 --pos 0x0 --rotate normal
    xrandr --output DP-1-2 --primary --mode 2560x1440 --pos 1920x0 --rotate
normal
    xrandr --output DP-1-3 --mode 2560x1440 --pos 4480x0 --rotate normal

Result:

X Error of failed request:  BadValue (integer parameter out of range for
operation)
  Major opcode of failed request:  139 (RANDR)
  Minor opcode of failed request:  7 (RRSetScreenSize)
  Value in failed request:  0x0
  Serial number of failed request:  57
  Current serial number in output stream:  58


Once this bug appears, xrandr behaves pretty strangely and "randomly" as far as
requested changes go:

- xrandr refuses to set some modes/positions/rotations
- This can be partially mitigated by toggling outputs off entirely and on
again. xrandr will still complain, but do as told
- Trying many different modes/positions/rotations and off/on cycles may
eventually yield the desired layout
- Attempts to change the screen size directly with e.g. "xrandr --db 9999x9999"
fails with the same error
- Something simple like making an active output primary, e.g. "xrandr --output
DP-1-2 --primary" fails with the same error
- Setting the same layout that is currently active is also complained about
- xrandr calls that previously failed may suddenly work after waiting a few
hours

Neither the kernel nor X show any relevant logs. I will check other debug
levels as instructed.

If you would like me to test anything or need more information, please let me
know.
Thanks!


You are receiving this mail because:
_______________________________________________
Nouveau mailing list
Nouveau@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/nouveau

[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux