Bug 101163 - [drm:intel_modeset_init] *ERROR* LSPCON init failed on port B
Summary: [drm:intel_modeset_init] *ERROR* LSPCON init failed on port B
Status: CLOSED NOTOURBUG
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-24 09:16 UTC by Pacho Ramos
Modified: 2017-06-27 14:22 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
dmesg (58.44 KB, text/plain)
2017-05-24 09:16 UTC, Pacho Ramos
no flags Details
config.gz (24.52 KB, application/gzip)
2017-05-24 09:17 UTC, Pacho Ramos
no flags Details
dmesg with debug 14 (143.68 KB, text/plain)
2017-05-24 13:04 UTC, Pacho Ramos
no flags Details
dmesg with debug 14 and HDMI connected to a TV (180.95 KB, text/plain)
2017-05-24 14:03 UTC, Pacho Ramos
no flags Details

Description Pacho Ramos 2017-05-24 09:16:51 UTC
Created attachment 131461 [details]
dmesg

I see this in dmesg output:
[    0.984723] [drm:lspcon_init] *ERROR* Failed to probe lspcon
[    0.984727] [drm:intel_modeset_init] *ERROR* LSPCON init failed on port B
[    0.985898] [drm] GuC firmware load skipped
[    0.988260] [drm] Initialized i915 1.6.0 20170123 for 0000:00:02.0 on minor 0
[    0.988982] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[    0.989715] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input4
[    0.989728] ACPI: Video Device [PEGP] (multi-head: no  rom: yes  post: no)
[    0.989745] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:0a/LNXVIDEO:01/input/input5
[    0.989761] [drm] Initialized i915 1.6.0 20170123 for 0000:00:02.0 on minor 0

I am running kernel 4.11.2 on Gentoo, I will attach full dmesg output and .config

xorg-server-1.19.3 and
Comment 1 Pacho Ramos 2017-05-24 09:17:20 UTC
Created attachment 131462 [details]
config.gz
Comment 2 Imre Deak 2017-05-24 12:35:46 UTC
Could you add a dmesg log booting with drm.debug=14?
Comment 3 Pacho Ramos 2017-05-24 13:04:05 UTC
Created attachment 131466 [details]
dmesg with debug 14

Sure, this one is with that option :)
Comment 4 Imre Deak 2017-05-24 13:28:18 UTC
(In reply to Pacho Ramos from comment #3)
> Created attachment 131466 [details]
> dmesg with debug 14
> 
> Sure, this one is with that option :)

Thanks. Your VBT says that there is a DP->HDMI converter in your box, but the driver can't initialize it. I wonder if the converter is present at all and fails to answer, or if VBT is wrong. What external connectors do you have, DP or HDMI? Could you connect a monitor to it before booting?
Comment 5 Imre Deak 2017-05-24 13:30:44 UTC
(In reply to Imre Deak from comment #4)
> (In reply to Pacho Ramos from comment #3)
> > Created attachment 131466 [details]
> > dmesg with debug 14
> > 
> > Sure, this one is with that option :)
> 
> Thanks. Your VBT says that there is a DP->HDMI converter in your box, but
> the driver can't initialize it. I wonder if the converter is present at all
> and fails to answer, or if VBT is wrong. What external connectors do you
> have, DP or HDMI? Could you connect a monitor to it before booting?

... providing a log again.
Comment 6 Pacho Ramos 2017-05-24 13:49:52 UTC
It has a HDMI port... but it's not working. I thought it was due to it being connected to the nvidia card... but as my nvidia card is still not properly supported with nouveau (it should improve in 4.12...), I  couldn't test the port as xorg-server crashes when trying to rely on reverse PRIME to let it work :/

About the display port... that is interesting as my first try was to rely on that one. I own a far older Dell laptop with that port connected to Intel card while HDMI to nvidia... and that would make things easier for me... but, sadly, I cannot find that DP port at all when looking to my laptop (Dell Inc. Inspiron 15 7000 Gaming/065C71, BIOS 01.00.05 03/01/2017) :/
Comment 7 Pacho Ramos 2017-05-24 13:51:03 UTC
Should I reboot with the external monitor connected to HDMI even?
Comment 8 Pacho Ramos 2017-05-24 14:03:26 UTC
Created attachment 131467 [details]
dmesg with debug 14 and HDMI connected to a TV

This is the log anyway ;)
Comment 9 Imre Deak 2017-05-24 15:30:51 UTC
(In reply to Pacho Ramos from comment #8)
> Created attachment 131467 [details]
> dmesg with debug 14 and HDMI connected to a TV
> 
> This is the log anyway ;)

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.

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.
Comment 10 Pacho Ramos 2017-05-24 16:24:48 UTC
(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 :/

> 
> 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)
Comment 11 Imre Deak 2017-05-24 16:59:21 UTC
(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.
Comment 12 Pacho Ramos 2017-05-24 17:17:26 UTC
Let see if I am lucky :)
http://en.community.dell.com/support-forums/software-os/f/3525/t/20013117
Comment 13 Pacho Ramos 2017-05-26 14:43:14 UTC
No reply there :(

But I have confirmed that xrandr only reports the HDMI-1 port after running xrandr --setprovideroutputsource nouveau modesetting

then, it seems it's connected to nvidia card :/
Comment 14 Imre Deak 2017-05-29 08:26:26 UTC
(In reply to Pacho Ramos from comment #13)
> No reply there :(
> 
> But I have confirmed that xrandr only reports the HDMI-1 port after running
> xrandr --setprovideroutputsource nouveau modesetting
> then, it seems it's connected to nvidia card :/

Ok, so looks like the output needs to be enabled by the nouveau driver, either via PRIME or using nouveau as the primary driver. I'm closing this as based on the above it's not a problem in i915 output setup. Please open separate bugs for the PRIME problem you saw and - if you can't get HDMI working by using nouveau as your primary driver - another nouveau specific bug.

Thanks for the report.
Comment 15 Pacho Ramos 2017-05-29 08:44:44 UTC
OK, thanks a lot for your help :)


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.