[Bug 101163] [drm:intel_modeset_init] *ERROR* LSPCON init failed on port B
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Wed May 24 16:59:21 UTC 2017
https://bugs.freedesktop.org/show_bug.cgi?id=101163
--- Comment #11 from Imre Deak <imre.deak at intel.com> ---
(In reply to Pacho Ramos from comment #10)
> (In reply to Imre Deak from comment #9)
> > I assume that BIOS doesn't light up the HDMI output either. My guess is that
> > the HDMI connector is wired to the Nvidia card, while the panel to the IGD.
> >
> > You could confirm what is the actual wiring either asking from DELL, or if
> > possible in Windows by disabling the Intel driver, leaving only the Nvidia
> > driver enabled. You could also check if there is a BIOS setup option to
> > change the output, although it could be hard-wired without muxing capability.
>
> I have no option in BIOS to change the output sadly :( and, as I don't have
> Windows... I guess I will need to contact Dell :/
Yes, unfortunately I don't know of a better way to determine this, unless you
manage to enable it with Nouveau.
> >
> > If the output is connected to the Nvidia card, you wouldn't need reverse
> > PRIME to enable it. Depending on the connection (native HDMI or via an
> > LSPCON DP->HDMI converter) you may also need LSPCON support in the Nouveau
> > driver, not sure if it exists.
>
> How would that be handled? For now I have tried to rely on reverse prime but
> it doesn't work because it makes X to crash :S
> xrandr --setprovideroutputsource nouveau modesetting
> xrandr --output HDMI-1-1 --auto --above eDP-1 => this causes the crashes
> and, per bash-completion, I can use DP-1 or HDMI-1-1 apart of eDP-1 as
> --above argument... but all fail in the same way (as gnome-control-center
> does when trying to use that HDMI output from it)
You'd need to use Nouveau as your primary driver, that is assigning that one to
your screen in your xorg.conf. You'd still need PRIME and specify
"--setprovideroutputsource Intel nouveau" to get eDP working in that
configuration, but even if this doesn't work, you could at least verify the
output routing.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20170524/932f3d18/attachment.html>
More information about the intel-gfx-bugs
mailing list