4.8-rc1: it is now common that machine needs re-run of xrandr after resume
Martin Steigerwald
martin at lichtvoll.de
Tue Sep 13 20:38:45 UTC 2016
Hi.
Am Dienstag, 13. September 2016, 22:23:50 CEST schrieb Pavel Machek:
> I have
>
> 00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset
> Integrated Graphics Controller (rev 03)
00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation
Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09)
Phoronix Test Suite system-info:
System Information
Hardware:
Processor: Intel Core i5-2520M @ 3.20GHz (4 Cores), Motherboard: LENOVO
42433WG, Chipset: Intel 2nd Generation Core Family DRAM, Memory: 16384MB,
Disk: 300GB INTEL SSDSA2CW30 + 480GB Crucial_CT480M50, Graphics: Intel 2nd
Generation Core Family IGP, Audio: Conexant CX20590, Monitor: P24T-7 LED,
Network: Intel 82579LM Gigabit Connection + Intel Centrino Advanced-N 6205
Software:
OS: Debian unstable, Kernel: 4.8.0-rc6-tp520-btrfstrim+ (x86_64), Desktop: KDE
Frameworks 5, Display Server: X Server 1.18.4, Display Driver: modesetting
1.18.4, OpenGL: 3.3 Mesa 12.0.2, Compiler: GCC 6.2.0 20160901, File-System:
btrfs, Screen Resolution: 3840x1080
> In previous kernels, resume worked ok. With 4.8-rc1, I quite often (1
> in 10 resumes?) get in state where primary monitor (DVI) is dead (in
> powersave) and all windows move to secondary monitor (VGA). Running
> "xrandr" fixes that.
I have seen this in 4.8 up to rc5 as well. I am not sure yet about rc6 which I
am currently running.
I didnĀ“t run xrandr by hand. But I ran systemsettings, dragged the second,
deactivated external display back beneath the internal laptop display,
activated it again and applied this changes. I think this has a somewhat
similar effect as Plasma uses RANDR as well.
> I'll update to newer rc and see if it happens again, but if you have
> any ideas, now would be good time.
No ideas, sorry.
Thanks,
--
Martin
More information about the dri-devel
mailing list