On 14/05/2015 20:01:21 GMT, Adam Williamson adamwill@fedoraproject.org wrote:
Hi folks!
We have a somewhat-worrying proposed blocker for F22:
I have tested Workstation (x86_64) TC3 and TC4 on my HP laptop with dual graphics (Intel and AMD):
00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Kernel driver in use: i915 Kernel modules: i915
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (rev ff) (prog-if ff) Kernel driver in use: radeon Kernel modules: radeon
While both TC3 and TC4 exhibit the flickering screen bug[1] at login, neither fails to display the GDM screen, leaving the machine stuck at a black screen as described in the bug under test.
As such, I'm not going to comment on Bugzilla with a useless "didn't affect me", but if there is any data I could collect from this working dual-GPU system that would be beneficial please let me know. The laptop in question is a test machine, so repeated clean installs are no problem.
Replying through a copy-paste, so apologies if this breaks somebody's threading.
--- Richard Bradfield
Hello,
On 14/05/2015 20:01:21 GMT, Adam Williamson adamwill@fedoraproject.org
wrote:
Hi folks!
We have a somewhat-worrying proposed blocker for F22:
I have some issues with two different laptops, one with an Intel/Nvidia combo and one with an Intel/Radeon combo. Although not strictly related to have a gdm login on Wayland I think it's worth describing.
Intel/Nvidia (binary driver):
The Nvidia one (intel + nvidia blob) is working perfectly with Fedora 21 but not on Fedora 22 with the "Optimus offloading configuration" as depicted in Nvidia's README [1]. The X server simply crashes, and there is no way to have a GDM login screen with this method. I was using the X configuration file described in the docs plus the script /etc/gdm/Init/:0 for running the xrandr commands at login. Also, glamor is loaded even though its loading is explicitly disabled in xorg.conf.
Unfortunately the laptop can only work with such configuration, the included GTX 860m does not work with nouveau reliably (lot of console errors and some crashes, no 3d) and there's no way to disable one of the cards through the bios.
I've tried updating xorg with some 1.18 patches [2], removing glamor, forcing root access for everybody in Xwrapper.config to no avail, I always got the same crash. I'm considering this a regression... should I open a bug or it will be simply closed because there is the Nvidia binary involved?
Intel/Nouveau and Intel/Radeon:
When using wayland, there's no way to use the second card (DRI_PRIME), it will simply use the first card for GL programs or crash directly (nothing useful in the logs). Is prime supported on Wayland? The server is also always started as root, wasn't it supposed to start inside a user session by default on Open KMS drivers?
Thanks & regards, --Simone
[1] http://us.download.nvidia.com/XFree86/Linux-x86/352.09/README/randr14.html [2] http://lists.x.org/archives/xorg-devel/2014-December/045050.html