Comment # 4
on bug 107919
from main.haarp@gmail.com
Thanks for your reply, Ilia. (In reply to Ilia Mirkin from comment #3) > The intel max > on IVB is most likely 8k, but having trouble confirming it. This is correct, xrandr reports a maximum of 8192x8192. However, when not using nouveau (i.e. this bug is not triggered), I'm getting the error message xrandr: screen cannot be larger than 8192x8192 (desired size 9999x9999) While the error I'm getting when this bug is triggered is different: 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 It's also weird that something that shouldn't touch the FB, such as setting a primary output, also fails with this. Another note: Before Nouveau, I ran the Nvidia card with the propietary driver on a separate X server together with intel-virtual-output. i-v-o provides virtual outputs on the Intel side and proxies them to the second X server. While the performance was terrible (which is why I switched to nouveau+provideroutputsource, thanks so much for creating Nouveau!), there were no problems setting screen sizes. But maybe i-v-o also used some sort of magic. > There's no real benefit to using nouveau ddx for the secondary screens, so > you should also experiment with using modesetting for those. Ah, I didn't know this was possible. I will of course lose the last remnants of rendering performance from the Nvidia, but if it allows monitors to work well, that's worth it. I will try that once I have the time. I assume this will not help with IVB's small FB, correct?
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ Nouveau mailing list Nouveau@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/nouveau
