missing patch for i915 in 4.15.0-33-generic => black screen on boot

[sh-dvl]

we must use i915 with modesetting, because else the hdmi-audio isn't available.

enabling modesetting, the monitor went black immediately after dmesg:

fb: switching to inteldrmfb from EFI VGA
Console: switching to colour dummy device 80x25
[drm] Replacing VGA console driver

for this bug at https://bugs.freedesktop.org/show_bug.cgi?id=105549 there seems to be a patch available which doesn't seem to be integrated in last available xenial-kernel 4.15.0-33-generic.

please integrate it in next kernel-update.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1792144

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[sh-dvl (sh-dvl)]

apport-collect ignores local proxy and hangs.
apport-bug doesn't show any relevant information and does not find any crash-reports (because there's noc crash, but only a dark screen)

all necessary info should be available in initial post.
if there is further detailled-information needed, give the command with textual output, which we'll add here, soon.

[Joseph Salisbury (jsalisbury)]

The upstream bug states that the following commit resolves this bug:

7306e32 drm/i915/bios: filter out invalid DDC pins from VBT child devices

That commit has been in Bionic since v4.15.0-23. Do you still see this bug with that kernel or newer?

[sh-dvl (sh-dvl)]

yes, unfortunately we still see this bug (else we haven't filed it here).

so, when the given patch is already added in -23 and we're using -33, it seems to be that that patch doesn't help for our problem, even the behaviour is really similar.

so. should we file a bug at freedesktop?

[sh-dvl (sh-dvl)]

we've just re-opened above mentioned bug at freedesktop

[redger (redgerhoo)]

I have the same bug on a similar motherboard - Asrock j4105-itx (j4105 CPU, asmedia asm1061, realtek rtl8111h)
After the boot sequence
KUbuntu 18.04 fully updated to Nov-19-2018
Bios 4.0.0.1245 Intel GOP 13.0.1011

I doubt this is the same as the freedesktop 105549 bug since the hardware is quite different (no lspcon chip on this motherboard)

Also note that the problem only arises when a disk is connected to one of the asmedia sata ports on this motherboard. If no disk on asmedia all is good. No HDMI or DVI screen if disk on asmedia port

Windows (8.1) does not experience this issue .... BUT does not have drivers for this chip at all (Vesa only)> I don't currently have access to Windows 10

When the VGA port is connected to a screen then BOTH the vga and hdmi / dvi screens are active ie. the hdmi / dvi output is live if vga simultaneously connected ... though vga is primary

May be spurious, but fwiw, under these conditions ... The system will not power down correctly (even if both VGA and hdmi / dvi connected). Powerdown seems to stop after a message about "ata3 SError" "failed command STANDBY IMMEDIATE" and then a manual power off is required

Any debug data I can provide ?