Comment 59 for bug 1812359

Revision history for this message
Daniel van Vugt (vanvugt) wrote : Re: Cannot install Ubuntu 18.04 in Intel Atom D425 when an external monitor is connected

Comment #57 is an image. Please remember to attach a log instead :)

Also, I have been thinking that the Intel Atom D425 was a laptop. Not just because that's more common, but also because the log in comment #35 mentions it is trying to render to a laptop screen (LVDS) and a VGA monitor at the same time:

Jan 29 09:45:01 test /usr/lib/gdm3/gdm-x-session[656]: (II) intel(0): switch to mode 1366x768@60.4 on LVDS1 using pipe 1, position (0, 0), rotation normal, reflection none
Jan 29 09:45:02 test /usr/lib/gdm3/gdm-x-session[656]: (II) intel(0): switch to mode 1366x768@59.8 on VGA1 using pipe 0, position (1366, 0), rotation normal, reflection none

If the Atom D425 machine is not a laptop then I think this explains a lot...

If your Atom D425 machine only ever has one screen and that screen is the VGA monitor then the above log shows the main issue here -- Ubuntu thinks you have two screens when you only have one. And if it thinks you have two screens then it's likely trying to put the login screen on that LVDS display which doesn't exist --> bug 1760849.

But it's not just the above bugs you are experiencing. If your Atom D425 machine doesn't have a built-in laptop monitor (LVDS) then there is clearly a bug in the Intel Xorg driver for trying to drive that screen. It seems there is no EDID but (unsurprisingly) can't tell that there's really no screen there at all.

Jan 29 09:45:30 test gsd-color[1080]: unable to get EDID for xrandr-LVDS1: unable to get EDID for
output

IF it is true that the Atom D425 machine is not a laptop, and it does not have a built-in screen, then I think the next step is to find out if it is the kernel misdetecting the non-existent LVDS screen, or the Xorg driver.

Next, please run this command and send us the output:

  grep . /sys/class/drm/*/enabled

Also, the log in comment #41 seems to show the system isn't starting in that case because of a crash:

Jan 29 16:29:17 test org.gnome.Shell.desktop[672]: (EE)
Jan 29 16:29:17 test org.gnome.Shell.desktop[672]: Fatal server error:
Jan 29 16:29:17 test org.gnome.Shell.desktop[672]: (EE) wl_drm@4: error 0: authenicate failed
Jan 29 16:29:17 test org.gnome.Shell.desktop[672]: (EE)
Jan 29 16:29:18 test gnome-shell[672]: X Wayland crashed; exiting
Jan 29 16:29:18 test gnome-session[628]: gnome-session-binary[628]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Jan 29 16:29:18 test gnome-session-binary[628]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Jan 29 16:29:18 test gnome-session-binary[628]: Unrecoverable failure in required component org.gnome.Shell.desktop

That would be the same crash mentioned in comments #23 and #24. So we will need to debug that too. Please look in /var/crash for crash files and if found send them by running:

  ubuntu-bug YOURFILE.crash

Unfortunately I can't access bug 1731911 that you mentioned in comment #24. Was that a typo?