[Bug 100553] New: Linux drivers for Intel-Braswell N3000 not detecting displays correctly

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Apr 4 11:54:13 UTC 2017


https://bugs.freedesktop.org/show_bug.cgi?id=100553

            Bug ID: 100553
           Summary: Linux drivers for Intel-Braswell N3000 not detecting
                    displays correctly
           Product: DRI
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: critical
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: mw at 3cte.pl
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 130667
  --> https://bugs.freedesktop.org/attachment.cgi?id=130667&action=edit
log when HDMI and eDP are connected.

HW : Intel Braswell N3000/N3710/J3710
FW : coreboot+FSP MR2

Linux drivers (latest taken from 01.org website) are not detecting connected
displays correctly.
The same linux with kernel option "nomodeset" boots properly... but graphics HW
acceleration is not working.
1)
When LFP display is connected on eDP port (port B) - all seems to work fine -
display is working, graphics drive is also fine.
     ---> however - a second display connected on port C (HDMI) is not even
detected.
2)
When LFP display is not connected - HDMI is actvie at boot time, by starting
from kernel driver - display is black and not active.  HDMI display device is
not detected.

Is this a known problem ???
What's the fix ?

The same HW/FW works fine with Windows 10 OS - no matter what's display
configuratuion.

Thanks,
Marek.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20170404/87014a68/attachment.html>


More information about the intel-gfx-bugs mailing list