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 ?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1792144

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

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792144/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to