Home / user-852189

coolcatco888's questions

Martin Hope
coolcatco888
Asked: 2021-04-10 21:17:46 +0800 CST
  • 0

Note I experimenting with liquorix kernel but that ultimately was not the cause of my boot hangs

Original Issue:

After installing the liquorix kernel to improve gaming performance, I noticed system stability issues like frequently failing to boot or crashing when playing a game like Cyberpunk.

Here's how I installed liquorix:

sudo add-apt-repository ppa:damentz/liquorix && sudo apt-get update
sudo apt-get install linux-image-liquorix-amd64 linux-headers-liquorix-amd64

It was fine at first but I started running into thes stability issues after:

  1. Updating Mesa GL using Ubuntu Software Updater
  2. Removing unused kernel files from linux-image-5.4.0-64-generic (as recommended by the ubuntu software updater) <-- This seems to have triggered the stability issues

I even tried booting into my previous kernel (5.4.0-70-generic) however the problems still persisted. I decided to remove the liquorix kernel using these instructions:

Still the problems persisted, I even tried:

  1. sudo apt-get autoremove
  2. Removing all old kernels with Ubuntu Cleaner
  3. Reinstalling my current kernel

Unfortunately Ubuntu hangs on boot/reboot about 50% of the time. I am not sure why my system is so unstable after reverting back to the previous kernel and purging the old kernel. Not sure exactly what caused this, was it:

  1. Installing the liquorix kernel
  2. Updating Mesa GL after installing the liquorix kernel
  3. Removing the old kernel files

Also here is my Mesa version:

OpenGL version string: 4.6 (Compatibility Profile) Mesa 21.0.2 - kisak-mesa PPA

When it fails to boot, sometimes it hangs on my Motherboard logo. Othertimes I see a list of errors like this:

0.316293] do_IRQ: 1.55 No irq handler for vector
0.316293] do_IRQ: 2.55 No irq handler for vector
0.316293] do_IRQ: 3.55 No irq handler for vector
0.316293] do_IRQ: 4.55 No irq handler for vector
0.316293] do_IRQ: 5.55 No irq handler for vector
0.316293] do_IRQ: 6.55 No irq handler for vector
0.316293] do_IRQ: 7.55 No irq handler for vector
0.316293] do_IRQ: 8.55 No irq handler for vector
0.316293] do_IRQ: 9.55 No irq handler for vector
0.316293] do_IRQ: 10.55 No irq handler for vector

Update 1 It seems like the No irq handler is a red herring. It sometimes boots with that message.

When I boot without "quiet splash" I see this when it freezes

fb: switching to amdgpudrmfb from EFI VGA

Note that when it succeeds to boot it also displays these same messages for a split second as well. I am not sure why it sometimes succeeds and sometimes fails. Boot Freeze Message

Update 2 I managed to find a log of what was installed that caused this in the first place:

2021-04-09 15:21:50 install linux-headers-liquorix-amd64:amd64 <none> 5.11-26ubuntu1~focal
2021-04-09 15:21:50 install linux-image-liquorix-amd64:amd64 <none> 5.11-26ubuntu1~focal

2021-04-09 15:27:15 upgrade libdrm-common:all 2.4.102-1ubuntu1kisak1~f 2.4.103-1ubuntu1~f~mesarc0
2021-04-09 15:27:15 upgrade libdrm2:i386 2.4.102-1ubuntu1kisak1~f 2.4.103-1ubuntu1~f~mesarc0
2021-04-09 15:27:16 upgrade libdrm2:amd64 2.4.102-1ubuntu1kisak1~f 2.4.103-1ubuntu1~f~mesarc0
2021-04-09 15:27:16 upgrade libdrm-amdgpu1:amd64 2.4.102-1ubuntu1kisak1~f 2.4.103-1ubuntu1~f~mesarc0
2021-04-09 15:27:16 upgrade libdrm-amdgpu1:i386 2.4.102-1ubuntu1kisak1~f 2.4.103-1ubuntu1~f~mesarc0
2021-04-09 15:27:16 upgrade libdrm-intel1:i386 2.4.102-1ubuntu1kisak1~f 2.4.103-1ubuntu1~f~mesarc0
2021-04-09 15:27:16 upgrade libdrm-intel1:amd64 2.4.102-1ubuntu1kisak1~f 2.4.103-1ubuntu1~f~mesarc0
2021-04-09 15:27:16 upgrade libdrm-nouveau2:amd64 2.4.102-1ubuntu1kisak1~f 2.4.103-1ubuntu1~f~mesarc0
2021-04-09 15:27:16 upgrade libdrm-nouveau2:i386 2.4.102-1ubuntu1kisak1~f 2.4.103-1ubuntu1~f~mesarc0
2021-04-09 15:27:16 upgrade libdrm-radeon1:amd64 2.4.102-1ubuntu1kisak1~f 2.4.103-1ubuntu1~f~mesarc0
2021-04-09 15:27:16 upgrade libdrm-radeon1:i386 2.4.102-1ubuntu1kisak1~f 2.4.103-1ubuntu1~f~mesarc0
2021-04-09 15:27:16 upgrade libegl-mesa0:amd64 21.0.1~kisak1~f 21.0.2~kisak1~f
2021-04-09 15:27:16 upgrade libgbm1:amd64 21.0.1~kisak1~f 21.0.2~kisak1~f
2021-04-09 15:27:17 upgrade libgl1-mesa-dri:i386 21.0.1~kisak1~f 21.0.2~kisak1~f
2021-04-09 15:27:17 upgrade libgl1-mesa-dri:amd64 21.0.1~kisak1~f 21.0.2~kisak1~f
2021-04-09 15:27:18 upgrade libosmesa6:i386 21.0.1~kisak1~f 21.0.2~kisak1~f
2021-04-09 15:27:18 upgrade libosmesa6:amd64 21.0.1~kisak1~f 21.0.2~kisak1~f
2021-04-09 15:27:19 upgrade libglx-mesa0:i386 21.0.1~kisak1~f 21.0.2~kisak1~f
2021-04-09 15:27:19 upgrade libglx-mesa0:amd64 21.0.1~kisak1~f 21.0.2~kisak1~f
2021-04-09 15:27:19 upgrade libglapi-mesa:amd64 21.0.1~kisak1~f 21.0.2~kisak1~f
2021-04-09 15:27:19 upgrade libglapi-mesa:i386 21.0.1~kisak1~f 21.0.2~kisak1~f
2021-04-09 15:27:19 upgrade libegl1-mesa:amd64 21.0.1~kisak1~f 21.0.2~kisak1~f
2021-04-09 15:27:19 upgrade libegl1-mesa-dev:amd64 21.0.1~kisak1~f 21.0.2~kisak1~f
2021-04-09 15:27:19 upgrade libgl1-mesa-dev:amd64 21.0.1~kisak1~f 21.0.2~kisak1~f
2021-04-09 15:27:19 upgrade libgl1-mesa-glx:amd64 21.0.1~kisak1~f 21.0.2~kisak1~f
2021-04-09 15:27:19 upgrade libxatracker2:amd64 21.0.1~kisak1~f 21.0.2~kisak1~f
2021-04-09 15:27:19 upgrade linux-firmware:all 1.187.10 1.190.2~mesarc0
2021-04-09 15:27:25 upgrade mesa-va-drivers:amd64 21.0.1~kisak1~f 21.0.2~kisak1~f
2021-04-09 15:27:26 upgrade mesa-vdpau-drivers:i386 21.0.1~kisak1~f 21.0.2~kisak1~f
2021-04-09 15:27:26 upgrade mesa-vdpau-drivers:amd64 21.0.1~kisak1~f 21.0.2~kisak1~f
2021-04-09 15:27:26 upgrade mesa-vulkan-drivers:i386 21.0.1~kisak1~f 21.0.2~kisak1~f
2021-04-09 15:27:27 upgrade mesa-vulkan-drivers:amd64 21.0.1~kisak1~f 21.0.2~kisak1~f
2021-04-09 15:27:27 upgrade xserver-xorg-video-amdgpu:amd64 19.1.0-1 19.1.0+git2102021245.6ed4863~f~mesarc0

2021-04-09 15:59:01 remove linux-headers-5.4.0-66-generic:amd64 5.4.0-66.74 <none>
2021-04-09 15:59:01 remove linux-headers-5.4.0-66:all 5.4.0-66.74 <none>
2021-04-09 15:59:02 remove linux-modules-extra-5.4.0-66-generic:amd64 5.4.0-66.74 <none>
2021-04-09 15:59:03 remove linux-image-5.4.0-66-generic:amd64 5.4.0-66.74 <none>
2021-04-09 15:59:07 remove linux-modules-5.4.0-66-generic:amd64 5.4.0-66.74 <none>

I've looked up various sources and it seems like the amdgpu firmware might be the culprit. I've reinstalled my current kernel and also reinstalled the firmware, even going so far as to delete the /lib/firmware/amdgpu and forcing a reinstallation. The problem is still there and I am not sure what else to do at this point.

Any ideas?

boot
Martin Hope
coolcatco888
Asked: 2020-11-06 18:20:11 +0800 CST
  • 0

I recently upgraded from Ubuntu 18.04 LTS to 20.04 LTS.

I noticed that whenever I play a game, like Hitman 2 using proton or something, it will freeze after 30mins to 1hr. This never happened on 18.04 LTS.

I noticed packages were not upgradable including libsane1, libsane-common and seem to be stuck in the 18.04 LTS versions. (see screenshots below) If I try to update it, it wants to remove ubuntu-desktop and other ubuntu core packages.

I also noticed that libgl1-mesa-glx (and other libraries that I installed to play games) were still on 20.2.1~kisak1~b which according to this is a bionic 18.04 LTS release. https://launchpad.net/~kisak/+archive/ubuntu/kisak-mesa/+build/20149684

I suspect some packages were not upgraded to 20.04 LTS during the upgrade and I am not sure how to fix it.

libsane1 and libsane-common are still in 18.04 LTS versions

I can't upgrade without removing core ubuntu packages

libgl1-mesa-glx is still on 18.04 LTS version and says it's up to date

here is my journalctl -b -e output

Nov 05 18:28:43 hackintosh tracker-store[3289]: OK
Nov 05 18:28:43 hackintosh systemd[1677]: tracker-store.service: Succeeded.
Nov 05 18:28:53 hackintosh nm-applet[2502]: gtk_widget_destroy: assertion 'GTK_>
Nov 05 18:28:53 hackintosh nm-applet[2502]: gtk_widget_destroy: assertion 'GTK_>
Nov 05 18:28:53 hackintosh nm-applet[2488]: gtk_widget_destroy: assertion 'GTK_>
Nov 05 18:28:53 hackintosh nm-applet[2488]: gtk_widget_destroy: assertion 'GTK_>
Nov 05 18:28:53 hackintosh nm-applet[2502]: Can't set a parent on widget which >
Nov 05 18:28:53 hackintosh nm-applet[2488]: Can't set a parent on widget which >
Nov 05 18:28:56 hackintosh systemd-resolved[912]: Server returned error NXDOMAI>
Nov 05 18:29:11 hackintosh dbus-daemon[1720]: [session uid=1000 pid=1720] Activ>
Nov 05 18:29:11 hackintosh systemd[1677]: Created slice apps.slice.
Nov 05 18:29:11 hackintosh systemd[1677]: Created slice apps-org.gnome.Terminal>
Nov 05 18:29:11 hackintosh systemd[1677]: Starting GNOME Terminal Server...
Nov 05 18:29:11 hackintosh dbus-daemon[1720]: [session uid=1000 pid=1720] Succe>
Nov 05 18:29:11 hackintosh systemd[1677]: Started GNOME Terminal Server.
Nov 05 18:29:11 hackintosh gnome-terminal-server[3781]: Fontconfig warning: "/e>
Nov 05 18:29:11 hackintosh gnome-terminal-server[3781]: Fontconfig warning: "/e>
Nov 05 18:29:11 hackintosh systemd[1677]: Started VTE child process 3789 launch>
Nov 05 18:29:27 hackintosh systemd-resolved[912]: Server returned error NXDOMAI>
Nov 05 18:29:29 hackintosh sudo[3823]: pam_unix(sudo:auth): Couldn't open /etc/>
Nov 05 18:29:31 hackintosh sudo[3823]: pam_unix(sudo:auth): Couldn't open /etc/>
Nov 05 18:29:31 hackintosh sudo[3823]:     cley : TTY=pts/1 ; PWD=/home/cley ; >
Nov 05 18:29:31 hackintosh sudo[3823]: pam_unix(sudo:session): session opened f>
lines 979-1001/1001 (END)
Nov 05 18:28:43 hackintosh tracker-store[3289]: OK
Nov 05 18:28:43 hackintosh systemd[1677]: tracker-store.service: Succeeded.
Nov 05 18:28:53 hackintosh nm-applet[2502]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
Nov 05 18:28:53 hackintosh nm-applet[2502]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
Nov 05 18:28:53 hackintosh nm-applet[2488]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
Nov 05 18:28:53 hackintosh nm-applet[2488]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
Nov 05 18:28:53 hackintosh nm-applet[2502]: Can't set a parent on widget which has a parent
Nov 05 18:28:53 hackintosh nm-applet[2488]: Can't set a parent on widget which has a parent
Nov 05 18:28:56 hackintosh systemd-resolved[912]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Nov 05 18:29:11 hackintosh dbus-daemon[1720]: [session uid=1000 pid=1720] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.118' (uid=1000 pid=3778 >
Nov 05 18:29:11 hackintosh systemd[1677]: Created slice apps.slice.
Nov 05 18:29:11 hackintosh systemd[1677]: Created slice apps-org.gnome.Terminal.slice.
Nov 05 18:29:11 hackintosh systemd[1677]: Starting GNOME Terminal Server...
Nov 05 18:29:11 hackintosh dbus-daemon[1720]: [session uid=1000 pid=1720] Successfully activated service 'org.gnome.Terminal'
Nov 05 18:29:11 hackintosh systemd[1677]: Started GNOME Terminal Server.
Nov 05 18:29:11 hackintosh gnome-terminal-server[3781]: Fontconfig warning: "/etc/fonts/conf.avail/65-ttf-droid-sans-fonts.conf", line 61: Having multiple values in  isn't supported and may not work as ex>
Nov 05 18:29:11 hackintosh gnome-terminal-server[3781]: Fontconfig warning: "/etc/fonts/conf.avail/65-ttf-droid-sans-fonts.conf", line 96: Having multiple values in  isn't supported and may not work as ex>
Nov 05 18:29:11 hackintosh systemd[1677]: Started VTE child process 3789 launched by gnome-terminal-server process 3781.
Nov 05 18:29:27 hackintosh systemd-resolved[912]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Nov 05 18:29:29 hackintosh sudo[3823]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory
Nov 05 18:29:31 hackintosh sudo[3823]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory
Nov 05 18:29:31 hackintosh sudo[3823]:     cley : TTY=pts/1 ; PWD=/home/cley ; USER=root ; COMMAND=/bin/journalctl -b -e
Nov 05 18:29:31 hackintosh sudo[3823]: pam_unix(sudo:session): session opened for user root by (uid=0)

***EDIT

I noticed that my distro upgrade might be broken enter image description here enter image description here enter image description here

Here is my apt.log

Log time: 2020-11-05 18:37:31.210246
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) libsensors-config:amd64  1:3.6.0-2ubuntu1 @in uN Ib >
Broken libsensors-config:amd64 Conflicts on libsensors4:amd64 
  Considering libsensors4:amd64 6 as a solution to libsensors-config:amd64 0
  Holding Back libsensors-config:amd64 rather than change libsensors4:amd64
Investigating (1) libsensors5:amd64  1:3.6.0-2ubuntu1 @un uN Ib >
Broken libsensors5:amd64 Depends on libsensors-config:amd64 
  Considering libsensors-config:amd64 0 as a solution to libsensors5:amd64 0
  Holding Back libsensors5:amd64 rather than change libsensors-config:amd64
Investigating (2) libsnmp35:amd64  5.8+dfsg-2ubuntu2.3 @un uN Ib >
Broken libsnmp35:amd64 Depends on libsensors5:amd64  (>= 1:3.5.0)
  Considering libsensors5:amd64 0 as a solution to libsnmp35:amd64 3
  Holding Back libsnmp35:amd64 rather than change libsensors5:amd64
Investigating (3) libsane:amd64  1.0.29-0ubuntu5.2 @un uN Ib >
Broken libsane:amd64 Depends on libsnmp35:amd64  (>= 5.8+dfsg)
  Considering libsnmp35:amd64 3 as a solution to libsane:amd64 10
  Holding Back libsane:amd64 rather than change libsnmp35:amd64
Investigating (3) sane-utils:amd64  1.0.29-0ubuntu5.2 @un uN Ib >
Broken sane-utils:amd64 Depends on libsane:amd64  (>= 1.0.27)
  Considering libsane:amd64 10 as a solution to sane-utils:amd64 3
  Holding Back sane-utils:amd64 rather than change libsane:amd64
Investigating (3) libsane1:amd64  1.0.29-0ubuntu5.2 @ii umU NPb Ib >
Broken libsane1:amd64 Depends on libsane:amd64  (>= 1.0.29-0ubuntu5.2)
  Considering libsane:amd64 10 as a solution to libsane1:amd64 0
  Removing libsane1:amd64 rather than change libsane:amd64
Investigating (4) colord:amd64 
Broken colord:amd64 Depends on libsane:amd64  (>= 1.0.24)
  Considering libsane:amd64 10 as a solution to colord:amd64 42
  Added libsane:amd64 to the remove list
  Fixing colord:amd64 via keep of libsane:amd64
Investigating (5) colord:amd64 
Broken colord:amd64 Depends on libsane:amd64  (>= 1.0.24)
  Considering libsane:amd64 42 as a solution to colord:amd64 42
  Removing colord:amd64 rather than change libsane:amd64
Investigating (6) gnome-control-center:amd64 
Broken gnome-control-center:amd64 Depends on colord:amd64  (>= 0.1.30)
  Considering colord:amd64 42 as a solution to gnome-control-center:amd64 54
  Added colord:amd64 to the remove list
  Fixing gnome-control-center:amd64 via keep of colord:amd64
Investigating (6) colord:amd64 
Broken colord:amd64 Depends on libsane:amd64  (>= 1.0.24)
  Considering libsane:amd64 42 as a solution to colord:amd64 54
  Added libsane:amd64 to the remove list
  Fixing colord:amd64 via keep of libsane:amd64
Investigating (7) colord:amd64 
Broken colord:amd64 Depends on libsane:amd64  (>= 1.0.24)
  Considering libsane:amd64 54 as a solution to colord:amd64 54
  Removing colord:amd64 rather than change libsane:amd64
Investigating (8) gnome-control-center:amd64 
Broken gnome-control-center:amd64 Depends on colord:amd64  (>= 0.1.30)
  Considering colord:amd64 54 as a solution to gnome-control-center:amd64 54
  Removing gnome-control-center:amd64 rather than change colord:amd64
Investigating (8) ubuntu-desktop-minimal:amd64 
Broken ubuntu-desktop-minimal:amd64 Depends on gnome-control-center:amd64 
  Considering gnome-control-center:amd64 54 as a solution to ubuntu-desktop-minimal:amd64 1
  Removing ubuntu-desktop-minimal:amd64 rather than change gnome-control-center:amd64
Investigating (8) ubuntu-desktop:amd64 
Broken ubuntu-desktop:amd64 Depends on gnome-control-center:amd64 
  Considering gnome-control-center:amd64 54 as a solution to ubuntu-desktop:amd64 0
  Removing ubuntu-desktop:amd64 rather than change gnome-control-center:amd64
Done
ERROR:root:Package brscan4 has no priority set
ERROR:root:Package mfcj480dwlpr:i386 has no priority set
ERROR:root:Package minecraft-launcher has no priority set
ERROR:root:NvidiaDetection returned a error: invalid literal for int() with base 10: 'server'
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) ubuntu-desktop:amd64 
Broken ubuntu-desktop:amd64 Depends on gnome-control-center:amd64 
  Considering gnome-control-center:amd64 7 as a solution to ubuntu-desktop:amd64 10000
  Added gnome-control-center:amd64 to the remove list
Broken ubuntu-desktop:amd64 Depends on ubuntu-desktop-minimal:amd64 
  Considering ubuntu-desktop-minimal:amd64 1 as a solution to ubuntu-desktop:amd64 10000
  Added ubuntu-desktop-minimal:amd64 to the remove list
  Fixing ubuntu-desktop:amd64 via keep of gnome-control-center:amd64
  Fixing ubuntu-desktop:amd64 via keep of ubuntu-desktop-minimal:amd64
Investigating (0) gnome-control-center:amd64 
Broken gnome-control-center:amd64 Depends on colord:amd64  (>= 0.1.30)
  Considering colord:amd64 5 as a solution to gnome-control-center:amd64 7
  Added colord:amd64 to the remove list
  Fixing gnome-control-center:amd64 via keep of colord:amd64
Investigating (0) colord:amd64 
Broken colord:amd64 Depends on libsane:amd64  (>= 1.0.24)
  Considering libsane:amd64 0 as a solution to colord:amd64 5
  Added libsane:amd64 to the remove list
  Fixing colord:amd64 via keep of libsane:amd64
Investigating (1) colord:amd64 
Broken colord:amd64 Depends on libsane:amd64  (>= 1.0.24)
  Considering libsane:amd64 0 as a solution to colord:amd64 5
  Added libsane:amd64 to the remove list
  Fixing colord:amd64 via keep of libsane:amd64
Investigating (2) colord:amd64 
Broken colord:amd64 Depends on libsane:amd64  (>= 1.0.24)
  Considering libsane:amd64 0 as a solution to colord:amd64 5
  Added libsane:amd64 to the remove list
  Fixing colord:amd64 via keep of libsane:amd64
Investigating (3) colord:amd64 
Broken colord:amd64 Depends on libsane:amd64  (>= 1.0.24)
  Considering libsane:amd64 5 as a solution to colord:amd64 5
  Removing colord:amd64 rather than change libsane:amd64
Investigating (4) gnome-control-center:amd64 
Broken gnome-control-center:amd64 Depends on colord:amd64  (>= 0.1.30)
  Considering colord:amd64 5 as a solution to gnome-control-center:amd64 7
  Added colord:amd64 to the remove list
  Fixing gnome-control-center:amd64 via keep of colord:amd64
Investigating (4) colord:amd64 
Broken colord:amd64 Depends on libsane:amd64  (>= 1.0.24)
  Considering libsane:amd64 5 as a solution to colord:amd64 7
  Added libsane:amd64 to the remove list
  Fixing colord:amd64 via keep of libsane:amd64
Investigating (5) colord:amd64 
Broken colord:amd64 Depends on libsane:amd64  (>= 1.0.24)
  Considering libsane:amd64 7 as a solution to colord:amd64 7
  Removing colord:amd64 rather than change libsane:amd64
Investigating (6) gnome-control-center:amd64 
Broken gnome-control-center:amd64 Depends on colord:amd64  (>= 0.1.30)
  Considering colord:amd64 7 as a solution to gnome-control-center:amd64 7
  Removing gnome-control-center:amd64 rather than change colord:amd64
Investigating (6) ubuntu-desktop-minimal:amd64 
Broken ubuntu-desktop-minimal:amd64 Depends on gnome-control-center:amd64 
  Considering gnome-control-center:amd64 7 as a solution to ubuntu-desktop-minimal:amd64 1
  Removing ubuntu-desktop-minimal:amd64 rather than change gnome-control-center:amd64
Investigating (7) ubuntu-desktop:amd64 
Broken ubuntu-desktop:amd64 Depends on gnome-control-center:amd64 
  Considering gnome-control-center:amd64 7 as a solution to ubuntu-desktop:amd64 10000
  Added gnome-control-center:amd64 to the remove list
Broken ubuntu-desktop:amd64 Depends on ubuntu-desktop-minimal:amd64 
  Considering ubuntu-desktop-minimal:amd64 7 as a solution to ubuntu-desktop:amd64 10000
  Added ubuntu-desktop-minimal:amd64 to the remove list
  Fixing ubuntu-desktop:amd64 via keep of gnome-control-center:amd64
  Fixing ubuntu-desktop:amd64 via keep of ubuntu-desktop-minimal:amd64
Investigating (7) gnome-control-center:amd64 
Broken gnome-control-center:amd64 Depends on colord:amd64  (>= 0.1.30)
  Considering colord:amd64 7 as a solution to gnome-control-center:amd64 10000
  Added colord:amd64 to the remove list
  Fixing gnome-control-center:amd64 via keep of colord:amd64
Investigating (7) colord:amd64 
Broken colord:amd64 Depends on libsane:amd64  (>= 1.0.24)
  Considering libsane:amd64 7 as a solution to colord:amd64 10000
  Added libsane:amd64 to the remove list
  Fixing colord:amd64 via keep of libsane:amd64
Investigating (8) colord:amd64 
Broken colord:amd64 Depends on libsane:amd64  (>= 1.0.24)
  Considering libsane:amd64 10000 as a solution to colord:amd64 10000
  Removing colord:amd64 rather than change libsane:amd64
Investigating (9) gnome-control-center:amd64 
Broken gnome-control-center:amd64 Depends on colord:amd64  (>= 0.1.30)
  Considering colord:amd64 10000 as a solution to gnome-control-center:amd64 10000
  Removing gnome-control-center:amd64 rather than change colord:amd64
Investigating (9) ubuntu-desktop-minimal:amd64 
Broken ubuntu-desktop-minimal:amd64 Depends on gnome-control-center:amd64 
  Considering gnome-control-center:amd64 10000 as a solution to ubuntu-desktop-minimal:amd64 10000
  Removing ubuntu-desktop-minimal:amd64 rather than change gnome-control-center:amd64
Done
ERROR:root:failed to mark 'ubuntu-desktop' for install (E:Unable to correct problems, you have held broken packages.)
upgrade mesa 18.04 20.04
Martin Hope
coolcatco888
Asked: 2020-04-30 10:43:34 +0800 CST
  • 0

I have a Jelly Comb wireless keyboard and mouse combo that uses a single USB receiver.

I have no problems using this keyboard and mouse when I boot up into Ubuntu 18.04 LTS. The problem is, if I unplug the USB receiver dongle and re-plug it in, it does not work.

It seems I can plug in a regular wired keyboard and mouse no problem but doing this with a wireless keyboard and mouse receiver does not work.

I couldn't find any answers to my specific problem. Can anyone help?

Thanks!

keyboard mouse usb
Martin Hope
coolcatco888
Asked: 2018-09-17 11:24:01 +0800 CST
  • 0

I noticed that whenever I try to select "Windows 10" from the grub boot screen, it turns black and then returns to Grub.

This happened after I upgraded Ubuntu 16.04 LTS to 18.04 LTS. I should note that I triple boot with Mac OSX High Sierra and chainload Clover from Grub. I also noticed that Clover does not detect Windows 10 as a bootable option anymore.

Does anyone have any ideas as to what is going on?

I have tried:

  1. sudo update-grub
  2. boot-repair

Nothing seemed to work. Any ideas?

Here is my boot-repair pastebin http://paste.ubuntu.com/p/jrzcMYk9WG/

Thanks!

grub2 boot upgrade dual-boot
Martin Hope
coolcatco888
Asked: 2018-07-22 17:58:09 +0800 CST
  • 5

I was wondering how to safely convert a Hybrid GPT/MBR to a pure GPT partition scheme? (Without Reformatting)

The reason why I ask is, I currently triple-boot with Ubuntu 16.04 LTS, Windows 10 and Mac OSX Lion.

Originally I needed to format my drive with a Hybrid partition scheme to install Windows 7 but I have since upgraded to Windows 10.

I know now that Windows 10 supports booting from GPT partitions and I would like to covert everything to a pure GPT partition scheme without reformatting.

If I can do this, I would be able to reformat my HFS+ partition to an APFS partition and install High Sierra.

So the questions are:

  1. How do I convert my Hybrid MBR to a pure GPT?
  2. Will it break booting into any of my OSes if I do? (Windows 10, Linux, MacOSX)

Here is my gdisk output:

GPT fdisk (gdisk) version 1.0.1

Partition table scan:
  MBR: hybrid
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with hybrid MBR; using GPT.

Command (? for help): p
Disk /dev/sda: 3907029168 sectors, 1.8 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): CBC86EEB-C878-4C46-9963-120433EB0BED
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 3907029134
Partitions will be aligned on 8-sector boundaries
Total free space is 269477 sectors (131.6 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1              40          409639   200.0 MiB   EF02  EFI System Partition
   2          409640       293378391   139.7 GiB   AF00  Mac OSX
   3       293642240       684265471   186.3 GiB   0700  WINDOWS 7
   4       684265472      1075085311   186.4 GiB   0700  LINUX
   5      1075085865      1087375589   5.9 GiB     8200  
   6      1087375590      3907024064   1.3 TiB     0700
partitioning mbr gpt