From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 107919] New: RandR unable to set Screen Size when using Intel+nouveau
Date: Thu, 13 Sep 2018 11:03:55 +0000 [thread overview]
Message-ID: <bug-107919-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2872 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107919
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-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Reporter: main.haarp-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.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:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4186 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2018-09-13 11:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 11:03 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-107919-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2018-10-03 9:59 ` [Bug 107919] RandR unable to set Screen Size when using Intel+nouveau bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-21 19:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-21 20:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-02-05 13:13 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-02-25 22:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-107919-8800@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox