Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1087869

Summary: [NVS 450] [multi-head] Splash not covering the whole screen
Product: Red Hat Enterprise Linux 7 Reporter: Michal Domonkos <mdomonko>
Component: xorg-x11-drv-nouveauAssignee: Ben Skeggs <bskeggs>
Status: CLOSED CURRENTRELEASE QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: mdomonko, rstrode
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-21 15:58:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
journal log with plymouth debug active
none
journal log with plymouth debug active and drm.debug=15 none

Description Michal Domonkos 2014-04-15 13:34:54 UTC
Created attachment 886489 [details]
journal log with plymouth debug active

Description of problem:
In a dual head setup (1920x1080 and 1280x1024) the splash graphics on both monitors shows up in the resolution of the smaller monitor (1280x1024), thus not covering the whole screen of the larger monitor.

Version-Release number of selected component (if applicable):
plymouth-0.8.9-0.2013.03.26.4.el7.x86_64
kernel-3.10.0-121.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1. Connect two monitors to the card's DisplayPorts
2. Boot up

Comment 1 Ray Strode [halfline] 2014-04-15 14:02:28 UTC
can you reproduce with drm.debug=15 on the kernel command line and reattach the log?

Comment 2 Michal Domonkos 2014-04-15 14:11:16 UTC
Created attachment 886495 [details]
journal log with plymouth debug active and drm.debug=15

Comment 3 Ray Strode [halfline] 2014-04-15 15:11:14 UTC
Looks like a driver issue of some sort unless i'm misappraising the situation.  It looks from the log as if the returned connector count is set to 2. plymouth iterates over the first two connectors and sees they're disconnected, so falls back to using /dev/fb0.  the log also shows there are two other connectors not accounted for in the connector count. those connectors are the connected ones.  presumably if plymouth knew about them (because the connector count was 4 instead of 2) then things would have worked.

Comment 4 Michal Domonkos 2014-04-15 15:22:05 UTC
Just for the record, the last 2 of those 4 connectors don't work on this card for some reason; they don't even display anything during POST so it looks like a hardware issue.

Comment 5 Ben Skeggs 2014-04-28 01:18:32 UTC
(In reply to Michal Domonkos from comment #4)
> Just for the record, the last 2 of those 4 connectors don't work on this
> card for some reason; they don't even display anything during POST so it
> looks like a hardware issue.

This isn't a bug at all.  The board is actually *two* GPUs glued together, so two of the display connectors belong to the non-primary device which isn't initialised at POST.

Comment 6 Ben Skeggs 2014-04-28 01:20:29 UTC
(In reply to Ray Strode [halfline] from comment #3)
> Looks like a driver issue of some sort unless i'm misappraising the
> situation.  It looks from the log as if the returned connector count is set
> to 2. plymouth iterates over the first two connectors and sees they're
> disconnected, so falls back to using /dev/fb0.  the log also shows there are
> two other connectors not accounted for in the connector count. those
> connectors are the connected ones.  presumably if plymouth knew about them
> (because the connector count was 4 instead of 2) then things would have
> worked.

See the above comment.  Does plymouth correctly deal with multiple-GPU setups like this, and select one with connected heads?

Comment 7 Ray Strode [halfline] 2014-07-16 15:20:35 UTC
(In reply to Ben Skeggs from comment #6)
> See the above comment.  Does plymouth correctly deal with multiple-GPU
> setups like this, and select one with connected heads?

Not plymouth-0.8.9-0.2013.03.26.4.el7.x86_64 but later versions do.

Michal, can you retest against GA?

Comment 8 Michal Domonkos 2014-07-21 15:58:53 UTC
Bug resolved on GA, plymouth now fully covers each of the screens on NVS 450.  Closing now.