User
|
Profile
|
Basic
|
GL
|
Suspend
|
Outputs
|
References
|
AMD HD7730M em DELL Inspiron 7520
|
w 8086:0166 1002:682f
|
pass warn
|
|
|
|
|
AnassAhmed
|
w 8086:0166 10de:1292
|
pass [1]
|
pass
|
pass [2]
|
pass
|
- ↑ Tested under Wayland only with the Live Test Day Image.
- ↑ Worked with External Displays connected to HDMI, but Backlight brightness doesn't work with Lenovo Ideapad Z500 (which needs custom kernel parameters to work).
|
AndyC
|
w 8086:191b 10de:13b1
|
pass
|
pass [1]
|
pass
|
pass
|
- ↑ $ glxinfo | grep renderer
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
Extended renderer info (GLX_MESA_query_renderer):
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2)
|
DamionGans
|
w 8086:1916 1002:6900
|
pass [1]
|
pass [2]
|
|
|
- ↑ works with wayland
- ↑ works
|
Danniello
|
3|5 nouveau|2|2
|
pass [1]
|
pass [2]
|
pass [3]
|
warn [4]
|
- ↑ Boot animation: OK; after boot animation - full screen of text with informations about starting services; after that - GNOME login screen. Everything in native laptop screen resolution.
- ↑ Laptop internal screen - everything OK.
- ↑ Laptop internal screen only - OK. Internal + DP - OK. Internal + HDMI - OK. HDMI only - OK.
- ↑ Default setup (changed nothing): Fedora see "third unknown screen" (not real!) and it is enabled by default (even when nothing connected to DP/HDMI). When third screen is enabled (by default!) - there are glitches on DP/HDMI screens. When "third screen" is manually disabled via gnome-control-center display - everything looks OK (tested internal+DP; internal+HDMI; HDMI only).
|
DarkSwanITA
|
w 8086:0116 10de:1058
|
pass [1] pass pass
|
pass
|
pass [2]
|
pass [3]
|
- ↑ Tested on Wayland on Live CD on an ASUS F55V (Intel Core i3-M2350 Sandybridge HD Graphics + Nvidia Geforce 610M 1Gb)
- ↑ Suspend+backlight keys works perfectly. Also tested with a Samsung TV attached via HDMI as second monitor with glxgears on it. Both screens shutdown perfectly and then resume without any corruption and with the backlight keys working.
- ↑ Tested with a Samsung TV (Model LE32S86BD) as second monitor via HDMI. All works, no problem (changing resolution, from 720p to 1080i, disconnect and reconnect, suspension OK!). Small nitpick, Display says that the Samsung TV is 7" where it is a 32" TV (bad EDID?).
|
GiordanoB
|
3|3 nouveau|2|5
|
pass
|
pass
|
pass
|
warn [1]
|
- ↑ The secondary display works. Suspending resuming works too.
However when I plugin the secondary display it is set in "mirroring" mode. If I set it as "secondary" and then suspend/resume the mode is always reset to "mirroring".
|
Joffrey
|
w 8086:191b 10de:139b
|
warn [1] pass [2]
|
pass [3]
|
|
|
- ↑ 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06)
01:00.0 3D controller: NVIDIA Corporation GM107M [GeForce GTX 960M] (rev a2)
- ↑ BOOT_IMAGE=/vmlinuz-4.8.6-300.fc25.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/root rd.lvm.lv=fedora/swap acpi=off rhgb quiet LANG=fr_FR.UTF-8
- ↑ [joffrey@localhost ~]$ glxinfo | grep renderer
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
Extended renderer info (GLX_MESA_query_renderer):
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2)
|
Lekensteyn
|
3|1 modesetting|4|3
|
warn [1] warn [2] fail [3] warn [4] warn [5]
|
pass
|
fail [6]
|
fail [7]
|
- ↑ RHBZ #1354256 Had to boot with nouveau.runpm=0 or else a lockup occured on switching to a text console (or any other activity that triggers runtime resume). Upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=156341 (hardware is Clevo P671RA, similar to Clevo P651RA).
- ↑ RHBZ #1354256 Had to boot with nouveau.runpm=0 or else a lockup occured on switching to a text console (or any other activity that triggers runtime resume, keyboard was unresponsible). Upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=156341
- ↑ RHBZ #1354256 Had to boot with nouveau.runpm=0 or else a lockup occured on switching to a text console (or any other activity that triggers runtime resume, keyboard was unresponsible). Upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=156341
- ↑ RHBZ #1354256 Had to boot with nouveau.runpm=0 or else a lockup occured on switching to a text console (or any other activity that triggers runtime resume, keyboard was unresponsible). Upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=156341
- ↑ RHBZ #1354256 Had to boot with nouveau.runpm=0 or else a lockup occured on switching to a text console (or any other activity that triggers runtime resume, keyboard was unresponsible). Upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=156341
- ↑ Brightness hotkeys are (known broken), likely https://bugs.freedesktop.org/show_bug.cgi?id=81762.
While suspend/resume works fine, GNOME displays management seems broken (hence FAILED).
Upon connection of HDMI port (wired to dGPU), the laptop display turned off (confirmed in Displays). After changing it to Primary/Secondary, it reverted to Mirror after suspend/resume (can be reproduced every time). Changing from mirror->primary for one monitor is insufficient, had to change the other screen from secondary->off->secondary to have something other than "mirror".
glxgears on both screens work though.
- ↑ RHBZ #1392157 Upon connection of HDMI port (wired to dGPU), the laptop display turned off (confirmed in Displays). After changing it to Primary/Secondary, it reverted to Mirror after suspend/resume (can be reproduced every time). Changing from mirror->primary for one monitor is insufficient, had to change the other screen from secondary->off->secondary to have something other than "mirror".
Gnome settings daemon also crashed on repeatedly inserting/removing HDMI cable.
|
LuK1337
|
4|4 modesetting|0|0
|
pass
|
pass
|
fail [1]
|
fail [2]
|
- ↑ Backlight keys don't work on ASUS R510JK, the suspend does work though.
- ↑ The display looks 'fuzzy' under Wayland but it works under Xorg just fine.
|
Luya Tshimbalanga
|
w 1002:130d 1002:6665
|
pass
|
pass [1]
|
|
|
- ↑ Tinyf jerkiness while moving the glxgears window otherwise fine
|
Luya Tshimbalanga
|
w 1002:130d 1002:6665 AMD Radeon R7 M265DX
|
pass
|
pass
|
warn [1]
|
pass
|
|
Magbed
|
w 8086:0416 10de:13d8
|
pass
|
pass
|
pass
|
pass
|
|
QuLogic
|
w 8086:0116 1002:6741
|
pass
|
pass [1]
|
pass
|
|
- ↑ Tried glxgears with both integrated graphics and discrete by settings DRI_PRIME=1.
|
a1Do255
|
3|3 nouveau|2|2
|
pass
|
|
|
|
|
a1Do255
|
3|3 nouveau|2|2 native display resolution: 1366x768, processor: Intel Core i5-460M, dedicated graphics: NVIDIA Geforce 425M, outputs: VGA (probably provided by Intel), HDMI (probably provided by NVIDIA)
|
pass [1] pass
|
pass [2]
|
fail [3]
|
|
- ↑ After logging in there is an unknown display in the display manager without(!) an attached monitor connected. I can even move windows to it by moving them to right side of the laptop display, but cannot see them because of the lack of a display. But I can still interact with the windows.
- ↑ Almost everything worked perfectly. Maximizing the glxgears window to the left or right side of the screen resulted in a fps drop to ~40 fps. Maximizing the glxgears window to the top so that almost the full screen is occupated by the window resulted in a fps drop to ~30 fps and clearly visible tearing.
- ↑ external display connected via hdmi: suspend and resume functioned but after adjusting the brightness via the gnome panel the system froze (not reproducible). At the attempt to repdroduce the error, the internal, external and unknown display got mirrored to 1024*768 @60Hz (biggest common denominator). After multiple hours of suspending, the configurations of the external connected monitor and the native display got confused after resuming (both presenting again 1024*768 @60Hz). The reconfiguration via the gnome display manager every time after the mirroring was a PITA btw.
external display connected via VGA: Suspend and resume functioned properly.
Suspend and resume functioned properly without external monitors connected.
|
ahawthorne
|
3|1 modesetting|4|3
|
pass
|
pass
|
pass [1] pass [2]
|
fail [3]
|
- ↑ Suspend works as expected. Backlight keys do not function at all.
- ↑ Backlight keys do not function before or after suspend.
- ↑ External display was correctly initialized (native 2560x1440) and desktop extended.
Dragging applications between displays worked as expected.
After resuming from suspend, both displays flickered several times and recovered with the external display at an incorrect resolution (1920x1080, expected 2560x1440) and mirrored rather than secondary display. After switching the external monitor back to secondary display gnome shell crashed and the liveusb login screen appeared. I was not able to log back in after.
|
ama
|
w 8086:191b 10de:139b
|
pass
|
pass [1]
|
pass [2]
|
warn [3]
|
- ↑ Runs perfectly fine using the MESA DRI Intel HD Graphics 530 (Skylake GT2) on Dell XPS 15 9550
- ↑ XPS 15 9550 internal screen only. Works fine.
- ↑ Not tested.
|
aneilan
|
4|4 nouveau|0|0
|
pass warn [1]
|
|
|
|
- ↑ when running the script under xorg, i get:
WARNING: Graphical server is X.org, but only one provider seems to have
connected outputs! This is not expected. Please report this in #fedora-test-day.
Paste the output of 'xrandr --listproviders':
Providers: number : 2
Provider 0: id: 0x87 cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 4 outputs: 4 associated providers: 1 name:Intel
Provider 1: id: 0x5f cap: 0x5, Source Output, Source Offload crtcs: 0 outputs: 0 associated providers: 1 name:nouveau
|
aslaikov
|
w 8086:191b 10de:134d
|
pass
|
pass
|
pass
|
pass
|
|
biji
|
w 8086:1616 1002:6900
|
pass [1]
|
pass [2] pass [3]
|
pass [4]
|
warn [5]
|
- ↑ You **SHOULD NOT** run the 'Power' test case! But please run the others!
- ↑ when running: Unigine_Valley-1.0 using DRI_PRIME=1 , i can see random black and white in full screen for seconds, after that renders correctly
and using DRI_PRIME=1 fps is slower than intel :D
- ↑ ok bro
- ↑ ok
- ↑ not tested
|
brianjorgensen
|
w 8086:0416 10de:1392
|
pass pass pass warn
|
pass
|
pass [1]
|
pass
|
- ↑ The brightness indicator appeared to be shifting small distances left and right as I adjusted the brightness.
|
cialu
|
4|4 Intel|3|5
|
pass [1]
|
pass
|
pass [2]
|
pass [3]
|
- ↑ You are testing under Xorg!
But I'm under Wayland and I removed the xorg.conf file.
- ↑ RHBZ #1379965 Unable to login after suspend, but backlight keys also work on the gnome-login screen.
- ↑ RHBZ #1379965 All works fine, just unable to login after suspend but it isn't a graphic issue.
|
cicciofritz
|
3|5 nouveau|2|1
|
pass [1]
|
pass [2]
|
fail [3]
|
fail [4]
|
- ↑ Ok
- ↑ Ok
- ↑ RHBZ #1391301 Backlight control key are not always responding well, brightness change is not smooth and sometimes it's stuck at the min/max value even if trying to modify it with keys. The test is very sensitive to the state of the ghost screen (see the bug). If ghost screen is on, often connecting an external monitor through VGA cable corrupts the desktop (not always). With the ghost screen off, the suspension works well even with external monitors connected.
- ↑ RHBZ #1391301 Behavior depends on the state of ghost monitor (see bug) with ghost monitor off everything works well. With ghost monitor on: the internal display graphically corrupted, external display glitchy and the whole system not responding to mouse click/keyboard (sometimes everything work even in this configuration)
|
dddw
|
3|5 nouveau|2|2 nouveau|2|2
|
pass [1] warn
|
pass [2]
|
pass
|
pass
|
- ↑ You **SHOULD** run the 'Power' test case!
- ↑ bit slow with gnome super key, but could be my system.
|
enno
|
4|3 nouveau|2|5
|
pass pass
|
pass
|
warn [1]
|
fail [2]
|
- ↑ backlight key haven't work neither before suspending the system nor after. lenovo t430. thought it never worked with optimus for me only with intel and backlight=vendore
- ↑ RHBZ #1391516 often defaults to broken display arrangements. for detailed info the bug
|
enunes
|
4|3 nouveau|2|5
|
pass
|
pass
|
fail [1]
|
|
- ↑ This is a Thinkpad T430.
The backlight "window" shows up and the bar increases/decreases when I press the backlight buttons, however it does not actually change the backlight.
I noticed that when I use the backlight keys, /sys/class/backlight/nv_backlight gets increased/decreased instead of /sys/class/backlight/intel_backlight .
Suspend works fine.
|
fredlima
|
w 8086:0a16 10de:1140
|
pass
|
pass
|
fail [1]
|
pass [2]
|
- ↑ the backlight keys works before suspend but the animation is flickering,
after suspend back from suspend the backlight keys works but after 3 seconds the system freezes.
- ↑ the external video output works, but my laptop has a problem with suspend, so the external monitor works after suspend but at some point after return from suspend my system hangs, but the eternal monitor worked well before that.
|
froqstar
|
w 8086:191b 10de:134d
|
pass
|
pass
|
pass
|
pass
|
|
fulminemizzega
|
w 8086:191b 10de:139b
|
pass [1]
|
pass [2]
|
warn [3]
|
pass
|
- ↑ Dell XPS 15 9550 FHD
- ↑ Dell XPS 15 9550 FHD
- ↑ Dell XPS 15 9550 FHD, On first try it did not turn completely off, then on second and third try worked just fine. On resume it's possible to see for a fraction of a second the screen of the running session before gdm locks it, this is a privacy issue. Why do we even care to use password login then? Running on Wayland.
|
german
|
w 8086:1616 10de:137a
|
pass
|
pass
|
pass
|
|
|
german
|
4|6 modesetting|0|0
|
pass [1]
|
pass
|
pass
|
|
- ↑ WARNING: Graphical server is X.org, but only one provider seems to have
connected outputs! This is not expected. Please report this in #fedora-test-day.
Paste the output of 'xrandr --listproviders':
Providers: number : 2
Provider 0: id: 0x79 cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 4 outputs: 6 associated providers: 1 name:Intel
Provider 1: id: 0x3f cap: 0x5, Source Output, Source Offload crtcs: 0 outputs: 0 associated providers: 1 name:modesetting
|
hoboprimate
|
w 8086:0a16 10de:1341
|
pass [1]
|
pass [2]
|
fail [3]
|
pass [4]
|
- ↑ Display shows up fine during in laptop's screen.
- ↑ Tested fine under Wayland
- ↑ RHBZ #1390008 Did not wake up correctly from suspend. Reported this bug a few days ago already.
- ↑ Only had a tv to try, worked as expected.
|
hp-1206g
|
3|5 CAICOS @ pci:0000:01:00.0|4|1
|
pass
|
pass [1]
|
pass [2]
|
pass [3]
|
- ↑ 299 frames in 5.0 seconds = 59.722 FPS
- ↑ Closing laptop lid doesn't go suspend, but using ALT+Click every thing is ok
- ↑ FULL HD monitor connected via HDMI and everything is ok. Sound and Video is ok
|
ilbozo
|
w 8086:191b 10de:13d8
|
pass
|
pass
|
pass
|
pass [1]
|
- ↑ worked with external hdmi and both external display ports
|
jenskuehnel
|
w 8086:0416 10de:1199
|
pass
|
pass
|
pass
|
|
|
jstodola
|
4|3 nouveau|2|5
|
pass
|
pass
|
warn [1]
|
|
- ↑ Backlight doesn't change
|
keepitreall89
|
w 1002:9903 1002:6840
|
pass [1]
|
pass [2]
|
pass [3]
|
pass [4]
|
- ↑ You are testing under Wayland!
You **SHOULD NOT** run the 'Power' test case! But please run the others!
- ↑ [liveuser@localhost ~]$ glxinfo | grep renderer
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
Extended renderer info (GLX_MESA_query_renderer):
OpenGL renderer string: Gallium 0.4 on AMD ARUBA (DRM 2.46.0 / 4.8.4-301.fc25.x86_64, LLVM 3.8.0)
[liveuser@localhost ~]$ glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
298 frames in 5.0 seconds = 59.548 FPS
301 frames in 5.0 seconds = 60.000 FPS
301 frames in 5.0 seconds = 60.010 FPS
300 frames in 5.0 seconds = 59.987 FPS
300 frames in 5.0 seconds = 60.000 FPS
301 frames in 5.0 seconds = 60.002 FPS
301 frames in 5.0 seconds = 60.000 FPS
301 frames in 5.0 seconds = 60.004 FPS
300 frames in 5.0 seconds = 59.993 FPS
301 frames in 5.0 seconds = 59.989 FPS
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
after 3061 requests (37 known processed) with 0 events remaining.
Worked fine
- ↑ Worked fine. Brightness keys worked before suspend, and after suspend.
- ↑ Tested with 1 external monitor via HDMI. Auto-recognized to 1080p and extended desktop to it. Worked fine after suspending and coming back on.
|
krouma
|
Intel HD Graphics 4000
|
|
pass
|
pass
|
|
|
l4rry
|
w 8086:0416 10de:139b
|
pass [1]
|
pass [2]
|
fail [3]
|
pass [4]
|
- ↑ Using test day image
asus rog g501j laptop
nvidia 960m 4gb
4k screen rending perfectly as well as screen brightness
- ↑ Rendering is working 100%
- ↑ Screen back light keys are not working before or after suspend , works under fedora 24
- ↑ Monitor connects and initializes immediately. Applications move fluidly between screens both 4k resolution.
|
laairoy
|
w 1002:9647 1002:6741
|
pass
|
|
|
|
|
lbrabec
|
3|7 modesetting|0|0
|
pass
|
pass
|
pass
|
pass
|
|
maarten
|
w 8086:0416 10de:11e3
|
pass [1]
|
pass [2]
|
pass [3]
|
pass [4]
|
- ↑ RHBZ #1326148
- ↑ RHBZ #1326148 passing i915.enable_psr=0 makes the flickering stop
- ↑ nitpick: when changing the back light in the system menu by dragging the slider using the mouse, the knob trails the mouse. It is visually displeasing (in my opinion). I would suggest to let the knob track the mouse and let the blue background/bar track the actual back light.
- ↑ At first, after hot plugging a VGA CRT monitor, the monitor was not detected correctly (wrong maximum resolution, barely readable). A reboot corrected the situation. I did not try disconnecting and reconnecting the monitor. I cannot reproduce the problem anymore.
|
mar
|
w 8086:0a16 10de:1341
|
warn warn pass pass
|
warn pass
|
warn
|
warn
|
|
mardan
|
w 8086:0a16 10de:1341
|
warn
|
|
|
|
|
maxwell
|
3|5 nouveau|2|3
|
warn
|
|
|
|
|
mep
|
3|3 nouveau|2|2
|
pass
|
|
|
|
|
metocean_sysadmin
|
w 8086:0166 10de:1291
|
pass
|
pass
|
fail [1]
|
warn [2]
|
- ↑ Keys did not backlight before the suspend operation. Backlighting worked as expected after suspend/resume. This was done on the Beta 1.1 Live Image, Sony Vaio Model SVF15AA1QL
- ↑ No available external display to test with.
|
mgewe
|
w 8086:191b 10de:139b
|
pass
|
pass
|
pass
|
pass [1]
|
- ↑ This works really great! If I close the lid all windows move to the external display and if I open it again they move back to their previous position.
|
mgewe
|
3|5 modesetting|0|0
|
pass [1]
|
pass
|
pass
|
pass
|
- ↑ Providers: number : 2
Provider 0: id: 0x77 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 3 outputs: 5 associated providers: 1 name:modesetting
Provider 1: id: 0x3f cap: 0x5, Source Output, Source Offload crtcs: 0 outputs: 0 associated providers: 1 name:modesetting
|
mochapenguin
|
w 8086:0116 1002:6740 [System: HP dv6t-6000 CTO Quad Edition - CPU: i7-2630QM graphics: dis=Radeon(TM) HD 6770M int=Intel]
|
pass [1]
|
pass [2]
|
pass [3]
|
pass [4]
|
- ↑ Tested on Wayland with the Live Test Day Image.
- ↑ Extended renderer info (GLX_MESA_query_renderer):
OpenGL renderer string: Mesa DRI Intel(R) Sandybridge Mobile
Screen lock after resume from suspend - After resuming from suspend, briefly the app windows are visible (for about a second) before the lock screen kicks in
Brightness control keys fail to alter the brightness of the display.
- ↑ Screen lock after resume from suspend - After resuming from suspend, briefly the app windows are visible (for about a second) before the lock screen kicks in
Brightness control keys fail to alter the brightness of the display.
- ↑ Tested with Samsung 40" LED TV
|
onai
|
w 8086:0416 10de:1292
|
pass [1] pass [2]
|
|
|
|
|
oneyoyopanda
|
w 8086:0166 10de:0fd1
|
pass
|
pass
|
pass
|
pass
|
|
onlyesterday16
|
w 8086:0416 10de:1391
|
pass
|
pass
|
pass
|
|
|
opensourcerer
|
w 8086:191b 10de:13d8
|
pass
|
pass
|
pass [1] pass
|
pass [2]
|
- ↑ Passed with HDMI connected displays, both via mini-video port and direct. Not tested with thunderbolt
- ↑ HDMI, HDMI via mini-display port,
|
pacof
|
w 8086:0416 10de:1391
|
pass
|
pass
|
pass [1]
|
warn [2]
|
- ↑ suspend resume works but brightness adjustment keys didn't work (before and after)
- ↑ RHBZ #1391775 DP output works
HDMI works if the display is connected before boot. The display is not detected when connected while the system is running. Switch to a console window and then switching back to Gnome will get the display detected.
Both outputs still work after a suspend/resume. A suspend/resume cycle will also allow the HDMI display to be detected after hotpluging.
|
plipp
|
3|1 modesetting|4|3
|
pass
|
pass
|
pass
|
fail [1]
|
- ↑ The testday live image starts an X desktop
I get no picture on my external display connected to displayport, although it is detected at the correct resolution (3840x2160@59Hz)
Changing to 30Hz does not improve the situation
Disconnecting the display works after a short stall
Re-connecting the display crashes X
After X restarts, logging in makes X crash again
The live beta 1.1 image boots to a WL desktop, but does not detect my external display
|
pschiffe
|
w 8086:191b 10de:134d
|
pass
|
pass
|
pass
|
|
|
r2d42
|
w 8086:0166 10de:0fd3
|
pass
|
pass
|
pass
|
pass
|
|
rathann
|
|
pass
|
pass
|
|
|
|
rillian
|
4|2 nouveau|4|4
|
pass [1]
|
pass [2]
|
pass [3]
|
fail [4]
|
- ↑ Got login screen after some vertical streaks, like the output wasn't sync'd correctly.
- ↑ Mesa DRI Intel(R) Ivybridge Mobile
- ↑ Only tried laptop screen, no external displays.
USB ethernet didn't reconnect after resume, had to unplug and replug to get back online.
- ↑ Connected an HP LP2475w to laptop HDMI port. External monitor was detected and enabled at native resolution.
1. Display was mirroring a subset of the laptop screen.
2.
Displays settings app was confused about whether display was mirrored or secondary. i.e. inconsistent selector behaviour.
3. Setting it to secondary, then mirrored resulted in full mirroring with the laptop display scaled to match the resolution of the external display.
4. Setting it to secondary resulted in flashing on the laptop screen, nothing on the external display. Had to wait for the 'keep this setting?' dialog to time out.
5. External display did not wake up on resume.
6. After unplugging external display in mirror mode, laptop screen stayed scaled until I opened the Displays settings app again. Not 100% repeatable.
7. Displays reported the monitor as <Hewlett Packard 26" > instead of 24"
|
sgk1980
|
4|2 modesetting|3|6
|
fail [1] fail [2]
|
pass [3]
|
pass
|
pass
|
- ↑ no login screen , black screen as if powered off . However startx from a different console works
- ↑ Black screen , looks like powered off . Not blank but black .
52.482] (II) NVIDIA(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 52.482] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[ 52.482] (==) NVIDIA(0): RGB weight 888
[ 52.482] (==) NVIDIA(0): Default visual is TrueColor
[ 52.482] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 52.483] (II) Applying OutputClass "nvidia" options to /dev/dri/card1
[ 52.483] (**) NVIDIA(0): Option "SLI" "Auto"
[ 52.483] (**) NVIDIA(0): Option "BaseMosaic" "on"
[ 52.483] (**) NVIDIA(0): Option "AllowEmptyInitialConfiguration"
[ 52.483] (**) NVIDIA(0): NVIDIA SLI auto-select rendering option.
[ 52.483] (**) NVIDIA(0): Enabling 2D acceleration
[ 52.484] (WW) NVIDIA(0): Failed to initialize Base Mosaic! Reason: Only one GPU
[ 52.484] (WW) NVIDIA(0): detected. Only one GPU will be used for this X screen.
[ 52.939] (--) NVIDIA(0): Valid display device(s) on GPU-0 at PCI:1:0:0
[ 52.939] (--) NVIDIA(0): DFP-0
[ 52.939] (--) NVIDIA(0): DFP-1
[ 52.941] (II) NVIDIA(0): NVIDIA GPU Quadro K1100M (GK107GL) at PCI:1:0:0 (GPU-0)
[ 52.941] (--) NVIDIA(0): Memory: 2097152 kBytes
[ 52.941] (--) NVIDIA(0): VideoBIOS: 80.07.ac.00.20
[ 52.941] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[ 52.941] (--) NVIDIA(GPU-0): DFP-0: disconnected
[ 52.941] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[ 52.941] (--) NVIDIA(GPU-0): DFP-0: 165.0 MHz maximum pixel clock
[ 52.941] (--) NVIDIA(GPU-0):
[ 52.941] (--) NVIDIA(GPU-0): DFP-1: disconnected
[ 52.941] (--) NVIDIA(GPU-0): DFP-1: Internal DisplayPort
[ 52.941] (--) NVIDIA(GPU-0): DFP-1: 960.0 MHz maximum pixel clock
[ 52.941] (--) NVIDIA(GPU-0):
[ 52.941] (==) NVIDIA(0):
[ 52.941] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[ 52.941] (==) NVIDIA(0): will be used as the requested mode.
[ 52.941] (==) NVIDIA(0):
[ 52.941] (--) NVIDIA(0): No enabled display devices found; starting anyway because
[ 52.941] (--) NVIDIA(0): AllowEmptyInitialConfiguration is enabled
[ 52.941] (II) NVIDIA(0): Validated MetaModes:
[ 52.941] (II) NVIDIA(0): "NULL"
[ 52.941] (II) NVIDIA(0): Virtual screen size determined to be 640 x 480
[ 52.941] (WW) NVIDIA(0): Unable to get display device for DPI computation.
[ 52.941] (==) NVIDIA(0): DPI set to (75, 75); computed from built-in default
[ 52.941] (==) modeset(G0): Depth 24, (==) framebuffer bpp 32
[ 52.941] (==) modeset(G0): RGB weight 888
[ 52.941] (==) modeset(G0): Default visual is TrueColor
- ↑ works fine under statx session from different console
|
steampoweredlawngnome
|
w 8086:1916 10de:1347
|
pass warn
|
|
|
|
|
sweard
|
w 8086:191b 10de:139b
|
pass
|
pass
|
pass
|
|
|
temjin747
|
w 1002:9874 1002:6660
|
pass [1]
|
pass [2]
|
pass [3]
|
|
- ↑ Run using live image
- ↑ [liveuser@localhost-live ~]$ glxinfo | grep renderer
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
Extended renderer info (GLX_MESA_query_renderer):
OpenGL renderer string: Gallium 0.4 on AMD CARRIZO (DRM 3.3.0 / 4.8.4-301.fc25.x86_64, LLVM 3.8.0)
[liveuser@localhost-live ~]$ glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
298 frames in 5.0 seconds = 59.395 FPS
301 frames in 5.0 seconds = 59.990 FPS
301 frames in 5.0 seconds = 60.008 FPS
301 frames in 5.0 seconds = 59.980 FPS
301 frames in 5.0 seconds = 60.027 FPS
300 frames in 5.0 seconds = 59.990 FPS
301 frames in 5.0 seconds = 59.997 FPS
300 frames in 5.0 seconds = 59.995 FPS
301 frames in 5.0 seconds = 60.015 FPS
300 frames in 5.0 seconds = 59.987 FPS
301 frames in 5.0 seconds = 60.001 FPS
300 frames in 5.0 seconds = 59.997 FPS
301 frames in 5.0 seconds = 60.013 FPS
300 frames in 5.0 seconds = 59.987 FPS
301 frames in 5.0 seconds = 59.996 FPS
300 frames in 5.0 seconds = 60.000 FPS
301 frames in 5.0 seconds = 59.996 FPS
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
after 5422 requests (1578 known processed) with 0 events remaining.
- ↑ backlight keys - brightness icon slightly wobbles when changing brightness at above halfway brightness levels
|
vorpalblade
|
4|4 modesetting|6|5
|
pass
|
pass
|
pass [1]
|
fail [2]
|
- ↑ Running on desktop system -- no backlight control on monitors
- ↑ Display does not disappear when disconnected (desktop system, not laptop)
|
wardme
|
3|1 modesetting|4|3
|
pass
|
pass
|
fail [1]
|
|
- ↑ Lenovo ThinkPad P50 with two external monitors connected via docking station (1 on DVI port and 1 on HDMI port). Note that with F24 I have to connect external monitors to the laptop ports (not docking station) and select "discrete graphics" (as opposed to "hybrid graphics" which is enabled for this test) in BIOS in order for the external monitors to be consistently detected and detected as two separate external monitors instead of one. In this configuration for F24, I am able to use both external monitors as well as the built-in laptop display for a three-screen setup. For this test, I connected the monitors through the docking station, hoping the detection issue might be fixed. Both monitors came up, but they are detected as a single device and both display the same output. I ran the test in this configuration, so I don't know if I should submit a bug report, or if this is not considered a supported configuration.
Test results:
1) Closed lid. External displays went dark.
2) Several seconds later, with lid still closed, external displays came on at 1400 x 1050 resolution, 74 Hz (native 1920 x 1200, which was the setting prior to closing lid). I believe the display settings showed "lid closed" for the built-in display.
3) Opened lid. External monitors change back to 1920 x 1280, but laptop display is off, and shows "off" in display settings. Built-in display was on at native 1920 x 1080 before closing lid.
4) Tested keyboard backlight keys per test procedure. They work after suspend as they did before suspend.
5) Turned on built-in display via settings. Came up, but with arrangement swapped (built-in was on left before closing lid; now on right).
6) Changed arrangement via settings. This caused built-in and external monitor resolution to change to 1400 x 1050 and went to "Mirror" mode with all three displays showing the same output. Refresh rate of built-in display shown as 59 Hz. External shown as 74 Hz.
7) Attempted to change external monitor(s) to primary. Still remained in "Mirror" mode at 1400 x 1050, and this is shown as the max available resolution for both built-in and external monitors in the settings dialog.
At this point, I didn't record every step because nothing seemed to be working. At one point, I selected the built-in monitor as secondary and the option for 1920 x 1280 appeared again. Able to successfully select built-in as secondary if I keep 1400 x 1050, but if I try to select as secondary at native resolution, or if I try to arrange displays after selecting built-in as secondary at 1400 x 1050, it drops back to mirror mode with all three displays at 1400 x 1050. Attempting to change resolution of external display(s) also results in dropping back to mirror mode at 1400 x 1050. Was able to get back to native resolution on built-in display at one point, but attempting to get external monitors back to native resolution resulted in mirror mode at 1400 x 1050 again. So far, I have found no way to recover all displays to native resolution in the proper arrangement through the display settings interface.
If it would be appropriate, I can submit a bug report for this with the output of the commands requested for bug reports. I attempted to include the output in this comment, but got "There was an error when saving the result (Malformed JSON data (HTTP 400))" when trying to submit.
|
witko
|
w 8086:0166 1002:6601
|
pass
|
pass
|
pass
|
pass
|
|
3|5 modesetting|0|0|x 8086:191b 10de:139b modesetting|3|5 modesetting|0|0
|
|
pass
|
|
|
|
|
3|5 modesetting|0|0|x 8086:191b 10de:139b modesetting|3|5 modesetting|0|0
|
xps9550
|
pass [1] pass
|
pass
|
pass
|
|
- ↑ /tmp/switchcheck
WARNING: Graphical server is X.org, but only one provider seems to have
connected outputs! This is not expected. Please report this in #fedora-test-day.
Paste the output of 'xrandr --listproviders':
Providers: number : 2
Provider 0: id: 0x77 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 3 outputs: 5 associated providers: 1 name:modesetting
Provider 1: id: 0x3f cap: 0x5, Source Output, Source Offload crtcs: 0 outputs: 0 associated providers: 1 name:modesetting
You are testing under Xorg!
You **SHOULD NOT** run the 'Power' test case! But please run the others!
Paste the following line as your 'profile' in the results page:
x 8086:191b 10de:139b modesetting|3|5 modesetting|0|0
[phil@mobile ~]$ xrandr --listproviders
Providers: number : 2
Provider 0: id: 0x77 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 3 outputs: 5 associated providers: 1 name:modesetting
Provider 1: id: 0x3f cap: 0x5, Source Output, Source Offload crtcs: 0 outputs: 0 associated providers: 1 name:modesetting
cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-4.8.8-300.fc25.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/root rd.lvm.lv=fedora/swap rhgb quiet LANG=en_US.UTF-8
glxinfo | grep renderer
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
Extended renderer info (GLX_MESA_query_renderer):
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2)
glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
after 233 requests (39 known processed) with 0 events remaining.
glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
300 frames in 5.0 seconds = 59.895 FPS
300 frames in 5.0 seconds = 59.996 FPS
300 frames in 5.0 seconds = 59.997 FPS
299 frames in 5.0 seconds = 59.792 FPS
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
after 1557 requests (745 known processed) with 0 events remaining.
|