Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager

Bug #1882442 reported by David W Craig
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Fedora)
Unknown
Unknown
linux (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

output of lsb_release -rd:
Description: Ubuntu 20.04 LTS
Release: 20.04

I recently upgraded from 18.04 to 20.04 and was using MATE. When the upgrade was run my external
HDMI monitor was plugged in, after the update, when I reboot, the internal monitor shows the beginning of the boot process (I deactivated 'silent splash' by editing grub.cfg) then it switches to the HDMI monitor and the internal monitor goes dark. I can also get the tty consoles on the external monitor but not on the internal monitor.

In MATE it was a real problem because the panel is apparently still on the invisible part of the desktop; I used a tty to install gnome, then I could get the display settings by right-clicking on the desktop, and setting the monitors to mirror, so I can reach applications, etc.

Computer is a Dell Inspiron 3275 AIO with touch screen and Intel on-board video, I think.
I had no problems with Ubuntu 18.04 with MATE.

The problem seems to be similar to this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194
but sort of the reverse, in that the internal monitor is the problem.

Thank you for your help.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-33-generic 5.4.0-33.37
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: david 2012 F.... pulseaudio
 /dev/snd/controlC1: david 2012 F.... pulseaudio
 /dev/snd/controlC0: david 2012 F.... pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun 7 11:43:37 2020
HibernationDevice: RESUME=UUID=3b1a8a2e-1937-4785-b4bb-49f9a251b292
InstallationDate: Installed on 2020-03-07 (91 days ago)
InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Dell Inc. Inspiron 3275 AIO
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=95b8de7f-9de3-4cea-b947-e135a738948c ro
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-33-generic N/A
 linux-backports-modules-5.4.0-33-generic N/A
 linux-firmware 1.187
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2020-06-06 (1 days ago)
dmi.bios.date: 03/15/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.7.0
dmi.board.name: 04NJ6P
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 13
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 00
dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd03/15/2019:svnDellInc.:pnInspiron3275AIO:pvr1.7.0:rvnDellInc.:rn04NJ6P:rvrA02:cvnDellInc.:ct13:cvr00:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 3275 AIO
dmi.product.sku: 0855
dmi.product.version: 1.7.0
dmi.sys.vendor: Dell Inc.

Revision history for this message
David W Craig (davidwcraigx) wrote :
Revision history for this message
David W Craig (davidwcraigx) wrote :

I also went in the dconf editor and changed some settings for laptop lid behavior to 'nothing",
since the display settings show the internal monitor as a laptop monitor. No effect.

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
David W Craig (davidwcraigx) wrote :

If I shutdown and unplug the external HDMI monitor, then power on, the internal display only shows the initial UEFI message, the screen appears grey, then it goes dark. If I then plug in the HDMI (not changing the power state) I can get a tty with ctrl-alt-f1, login, and run startx. MATE then appears, but only the non-panel part of the display. Also the monitor arrangement is flipped, but I think that is a minor MATE problem I noticed in 18.04 after a cli startx.

Revision history for this message
David W Craig (davidwcraigx) wrote :

If the external HDMI is plugged in at power-on, a login window will show up on the HDMI, and then I can choose gnome or gnome classic for the session, log in, then right-click on the desktop, set the displays to mirror, and get to the main panels or activities menu.

Revision history for this message
David W Craig (davidwcraigx) wrote :

I left the machine on a while, and the internal monitor came on while I was gone for about an hour.
???

Revision history for this message
David W Craig (davidwcraigx) wrote :

This seems to be a kernel issue: when I switched back to kernel 4.15 in GRUB2, the problems seems to go away. Checking on it.

Revision history for this message
David W Craig (davidwcraigx) wrote :

PARTIAL FIX: downgrade the kernel. I can confirm that everything seems to return to normal if you use GRUB2 to select Linux 4.15.0-101-generic as the kernel.
I edited /etc/default/grub to
- give a boot menu with a reasonable timeout
- use the last selected kernel as default

description: updated
Revision history for this message
David W Craig (davidwcraigx) wrote :

I found a similar Fedora bug report, it is a kernel issue, and there is a workaround. See: https://bugzilla.redhat.com/show_bug.cgi?id=1594488

Need to add 'amdgpu.dc=0' to the kernel command line in grub.cfg:

GRUB_CMDLINE_LINUX="amdgpu.dc=0"
then run grub-update

reboot

after booting to a version 5 kernel, video on both monitors works, and a check of the proc cmdline shows:
$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=95b8de7f-9de3-4cea-b947-e135a738948c ro amdgpu.dc=0

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Please test latest mainline kernel without "amdgpu.dc=0":
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8-rc4/

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
David W Craig (davidwcraigx) wrote :
Download full text (4.6 KiB)

I got the files for the kernel and did this (many warnings, one error):

(base) david:new-kernel$ sudo dpkg -i *.deb
Selecting previously unselected package linux-headers-5.8.0-050800.
(Reading database ... 454198 files and directories currently installed.)
Preparing to unpack linux-headers-5.8.0-050800_5.8.0-050800.202007052030_all.deb ...
Unpacking linux-headers-5.8.0-050800 (5.8.0-050800.202007052030) ...
Preparing to unpack linux-headers-5.8.0-050800-generic_5.8.0-050800.202007052030_amd64.deb ...
Unpacking linux-headers-5.8.0-050800-generic (5.8.0-050800.202007052030) over (5.8.0-050800.202007052030) ...
Preparing to unpack linux-image-unsigned-5.8.0-050800-generic_5.8.0-050800.202007052030_amd64.deb ...
Unpacking linux-image-unsigned-5.8.0-050800-generic (5.8.0-050800.202007052030) over (5.8.0-050800.202007052030) ...
Selecting previously unselected package linux-modules-5.8.0-050800-generic.
Preparing to unpack linux-modules-5.8.0-050800-generic_5.8.0-050800.202007052030_amd64.deb ...
Unpacking linux-modules-5.8.0-050800-generic (5.8.0-050800.202007052030) ...
Setting up linux-headers-5.8.0-050800 (5.8.0-050800.202007052030) ...
Setting up linux-headers-5.8.0-050800-generic (5.8.0-050800.202007052030) ...
Setting up linux-modules-5.8.0-050800-generic (5.8.0-050800.202007052030) ...
Setting up linux-image-unsigned-5.8.0-050800-generic (5.8.0-050800.202007052030) ...
Processing triggers for linux-image-unsigned-5.8.0-050800-generic (5.8.0-050800.202007052030) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.8.0-050800-generic
modinfo: ERROR: could not get modinfo from 'da903x': No such file or directory
W: Possible missing firmware /lib/firmware/amdgpu/navi12_gpu_info.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_gpu_info.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_ta.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_asd.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_sos.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi12_ta.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi12_asd.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi12_sos.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi14_ta.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_ta.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi12_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi12_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi12_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi12_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi12_pfp.bin for module amdgpu
W: Pos...

Read more...

Revision history for this message
David W Craig (davidwcraigx) wrote :

The above did not work.
I edited grub to remove the amdgpu.dc=0 from the command line, ran update-grub and rebooted. Essentially the same behavior as before.
I did notice some 'Tell Plymouth to write out...(something) in the boot messages, but otherwise very similar.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Thanks for testing.

Did it work on 18.04?

Revision history for this message
David W Craig (davidwcraigx) wrote :

Yes, it worked on 18.04. The problem came with the upgrade to 20.04.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Can you please test kernel v4.15, which is used by 18.04:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.18/

Revision history for this message
David W Craig (davidwcraigx) wrote : Re: [Bug 1882442] Re: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager
Download full text (3.8 KiB)

I already tried that, it V4.1.5 worked with both Ubuntu 18.04 and 20.04. I
put in an earlier comment about this.

On Wed, Jul 8, 2020 at 10:40 AM Kai-Heng Feng <email address hidden>
wrote:

> Can you please test kernel v4.15, which is used by 18.04:
> https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.18/
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1882442
>
> Title:
> Upgrade from 18.04 to 20.04 deactivates internal monitor in display
> manager
>
> Status in linux package in Ubuntu:
> Incomplete
> Status in linux package in Fedora:
> Unknown
>
> Bug description:
> output of lsb_release -rd:
> Description: Ubuntu 20.04 LTS
> Release: 20.04
>
> I recently upgraded from 18.04 to 20.04 and was using MATE. When the
> upgrade was run my external
> HDMI monitor was plugged in, after the update, when I reboot, the
> internal monitor shows the beginning of the boot process (I deactivated
> 'silent splash' by editing grub.cfg) then it switches to the HDMI monitor
> and the internal monitor goes dark. I can also get the tty consoles on the
> external monitor but not on the internal monitor.
>
> In MATE it was a real problem because the panel is apparently still on
> the invisible part of the desktop; I used a tty to install gnome, then
> I could get the display settings by right-clicking on the desktop, and
> setting the monitors to mirror, so I can reach applications, etc.
>
> Computer is a Dell Inspiron 3275 AIO with touch screen and Intel
> on-board video, I think.
> I had no problems with Ubuntu 18.04 with MATE.
>
> The problem seems to be similar to this bug:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194
> but sort of the reverse, in that the internal monitor is the problem.
>
> Thank you for your help.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 20.04
> Package: linux-image-5.4.0-33-generic 5.4.0-33.37
> ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
> Uname: Linux 5.4.0-33-generic x86_64
> ApportVersion: 2.20.11-0ubuntu27.2
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC2: david 2012 F.... pulseaudio
> /dev/snd/controlC1: david 2012 F.... pulseaudio
> /dev/snd/controlC0: david 2012 F.... pulseaudio
> CasperMD5CheckResult: skip
> CurrentDesktop: ubuntu:GNOME
> Date: Sun Jun 7 11:43:37 2020
> HibernationDevice: RESUME=UUID=3b1a8a2e-1937-4785-b4bb-49f9a251b292
> InstallationDate: Installed on 2020-03-07 (91 days ago)
> InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release
> amd64 (20160719)
> MachineType: Dell Inc. Inspiron 3275 AIO
> ProcFB: 0 amdgpudrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic
> root=UUID=95b8de7f-9de3-4cea-b947-e135a738948c ro
> RelatedPackageVersions:
> linux-restricted-modules-5.4.0-33-generic N/A
> linux-backports-modules-5.4.0-33-generic N/A
> linux-firmware 1.187
> SourcePackage: linux
> UpgradeStatus: Upgraded to focal on 2020-06-06 (1 days ago)
> dmi.bios.date: 03/15/2019...

Read more...

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Would it be possible for you to do a kernel bisection?

First, find the last -rc kernel works and the first -rc kernel doesn’t work from http://kernel.ubuntu.com/~kernel-ppa/mainline/

Then,
$ sudo apt build-dep linux
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd linux
$ git bisect start
$ git bisect good $(the working version you found)
$ git bisect bad $(the non-working version found)
$ make localmodconfig
$ make -j`nproc` deb-pkg
Install the newly built kernel, then reboot with it.
If it still have the same issue,
$ git bisect bad
Otherwise,
$ git bisect good
Repeat to "make -j`nproc` deb-pkg" until you find the offending commit.

Revision history for this message
David W Craig (davidwcraigx) wrote :

I will have to read up on this, and I am in a situation where I have to rely on this as my only computer for a while.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.