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.
--
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/1882442
Title:
Upgrad
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 <1882...@bugs.launchpad.net>
wrote:
> Can you please test kernel v4.15, which is used by 18.04:
> https://kernel.ubuntu.com/~kernel-ppa/ma
Yes, it worked on 18.04. The problem came with the upgrade to 20.04.
--
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/1882442
Title:
Upgrade from 18.04 to 20.04 deactivates internal monito
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.
--
You received this bug n
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-
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 versio
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 cha
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.
--
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/1882442
Title:
I left the machine on a while, and the internal monitor came on while I was
gone for about an hour.
???
--
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/1882442
Title:
Upgrade from 18.04
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.
--
You received this bug noti
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 appea
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.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux i
Public bug reported:
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 b
13 matches
Mail list logo
