Ubuntu-Mate 21.04 live does not boot

Ok, this is a strange one, I have a Ryzen 7 3700X and a EVGA 2080 Super graphics card.

I downloaded Ubuntu-Mate 21.04 and burned it with Etcher. I even tried using Gnome Disks. When I boot the stick I choose UEFI and select the top choice. I get the Mate symbol and the dots scrolling across.

Then the dots stop scrolling and I sat there for more than 10 mins and it never got past that screen. The Mate symbol with the dots just stayed there.

I tried booting and using the choice with nomodeset, and when the dots stop moving, the screen goes black and I sit there for 10 mins watching a black blank screen. I even tried changing nomodeset to nouveau.modeset=0 and get the same thing.

I burned XUbuntu 21.04 and when I boot up and pick the first option, I get the screen asking if I want to try or install. Clicking on try gets me the desktop. Not sure why XUbuntu live boots up, but Ubuntu-Mate will not.

I tried Mate 20.10 and the live iso boots to desktop, doesn't ask if I want to try or install, just went to desktop, but i'm having no luck with 21.04. I downloaded it 3 separate times and burned it to 2 different USB sticks. No luck.

I tried the Mate 21.04 on my brothers system that has a RX 5700 XT and it boots to the screen asking to try it live, or install, so it works on a Radeon graphics card, but will not work on a 2080 Super.

I'm at a loss as to why this is happening, all previous Mate live iso boot fine, just cannot boot 21.04. Any ideas on why and what I can do to try it?

Thank you.

2 Likes

@Cajun_Man0001 welcome. There is an almost identical post-Ubuntu-MATE 21.04 Installer Freezes on PC Install (not a VM). The user is on Ryzen 7 2700X and NVidia GeForce RTX 2070 GPU.

Can you check two things,

  1. When you see MATE logo and progress indicator dots, press 'Esc', that takes you to text mode. See if it gives any clue; where is has hung.
  2. The user in the linked post has posted 'auth.log'. It will be in your USB. Check if you see same error as Failed to activate service 'org.freedesktop.RealtimeKit1': timed out (service_start_timeout=25000ms). Or any other error(s).

I must have missed that post. I looked through before posting, could have sworn I didn't see anythink like this, but I guess I overlooked it. I was hoping there was a answer on his, but not yet.

Ok. When I get some time this week, I'll try again. I had reburned the stick so I'll have to burn it with 21.04 Mate again to try it.

I have it on a Ventoy stick, but I don't think that file gets put on it, but I'll look.

Thanks.

Blockquote
Apr 26 13:07:05 ubuntu-mate python3: pam_unix(su:session): session opened for user ubuntu-mate by (uid=0)
Apr 26 13:07:05 ubuntu-mate systemd-logind[2400]: New session c1 of user ubuntu-mate.
Apr 26 13:07:05 ubuntu-mate systemd: pam_unix(systemd-user:session): session opened for user ubuntu-mate by (uid=0)
Apr 26 13:07:31 ubuntu-mate dbus-daemon[2380]: [system] Failed to activate service 'org.freedesktop.RealtimeKit1': timed out (service_start_timeout=25000ms)
Apr 26 13:07:56 ubuntu-mate dbus-daemon[2380]: [system] Failed to activate service 'org.freedesktop.RealtimeKit1': timed out (service_start_timeout=25000ms)
Apr 26 13:08:21 ubuntu-mate dbus-daemon[2380]: [system] Failed to activate service 'org.freedesktop.RealtimeKit1': timed out (service_start_timeout=25000ms)
Apr 26 13:08:46 ubuntu-mate dbus-daemon[2380]: [system] Failed to activate service 'org.freedesktop.RealtimeKit1': timed out (service_start_timeout=25000ms)
Apr 26 13:09:11 ubuntu-mate dbus-daemon[2380]: [system] Failed to activate service 'org.freedesktop.RealtimeKit1': timed out (service_start_timeout=25000ms)
Apr 26 13:09:36 ubuntu-mate dbus-daemon[2380]: [system] Failed to activate service 'org.freedesktop.RealtimeKit1': timed out (service_start_timeout=25000ms)
Apr 26 13:10:01 ubuntu-mate dbus-daemon[2380]: [system] Failed to activate service 'org.freedesktop.RealtimeKit1': timed out (service_start_timeout=25000ms)
Apr 26 13:10:26 ubuntu-mate dbus-daemon[2380]: [system] Failed to activate service 'org.freedesktop.RealtimeKit1': timed out (service_start_timeout=25000ms)

The auth.log looks similar to his. I noticed when I hit ESC that something about a backup GPT wasn't found. went by so fast wasn't sure exactly what it said, but like I said 20.10 Mate live ISO booted fine.

Unfortunately there is no way to capture the text when ESC is pressed cause there was alot more lines then auth.log has.

Here is casper.log it shows the GPT message:

Blockquote
stdin: Invalid argument
stdin: Invalid argument
GPT PMBR size mismatch (5792251 != 60567551) will be corrected by write.
The backup GPT table is not on the end of the device.
GPT PMBR size mismatch (5792251 != 60567551) will be corrected by write.
The backup GPT table is not on the end of the device.
GPT PMBR size mismatch (5792251 != 60567551) will be corrected by write.
The backup GPT table is not on the end of the device. This problem will be corrected by write.
Partition #4 contains a ext4 signature.
16+0 records in
16+0 records out
passwd: password expiry information changed.
dbus-daemon[1100]: [session uid=999 pid=1100] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' (uid=999 pid=1101 comm="" label="unconfined")
dbus-daemon[1100]: [session uid=999 pid=1100] Successfully activated service 'org.gtk.vfs.Daemon'
dbus-daemon[1100]: [session uid=999 pid=1100] Activating service name='org.gtk.vfs.Metadata' requested by ':1.0' (uid=999 pid=1101 comm="" label="unconfined")
fuse: device not found, try 'modprobe fuse' first
dbus-daemon[1100]: [session uid=999 pid=1100] Successfully activated service 'org.gtk.vfs.Metadata'
A connection to the bus can't be made
Using CD-ROM mount point /cdrom/
Identifying... [fd0bcdc91f1278912c0661d3c1d29d9e-2]
Scanning disc for index files...
Found 4 package indexes, 0 source indexes, 0 translation indexes and 1 signatures
Found label 'Ubuntu-MATE 21.04 Hirsute Hippo - Release amd64 (20210420)'
This disc is called:
'Ubuntu-MATE 21.04 Hirsute Hippo - Release amd64 (20210420)'
Copying package lists...gpgv: Signature made Tue Apr 20 11:08:25 2021 UTC
gpgv: using RSA key 843938DF228D22F7B3742BC0D94AA3F0EFE21092
gpgv: Good signature from "Ubuntu CD Image Automatic Signing Key (2012) [email protected]"

Reading Package Indexes... 0%

Reading Package Indexes... Done
Writing new source list
Source list entries for this disc are:
deb cdrom:[Ubuntu-MATE 21.04 Hirsute Hippo - Release amd64 (20210420)]/ hirsute main multiverse restricted universe
Repeat this process for the rest of the CDs in your set.

Not sure about the GPT messages, it doesn't cause issues with any other iso I try to live boot, but when I get time I'll boot another live iso and use gparted to recreate a gpt drive on the drive I use and see if that makes a difference.

Looks like this post is getting some replies, so I'll go ahead and re-post my similar situation here.

The Ubuntu MATE 21.04 fails to "launch" when trying to do a clean install on my PC. The installer starts up and shows the green Ubuntu logo and the small circles cycle through for about 30 seconds and then the system hangs. I have tried this multiple times, on two different USB drives, and verified the checksums. I also wiped the drive clean once and downloaded the Ubuntu 21.04 (non-mate), but it on the same USB drive, and it boots up just fine.

My computer has been running Ubuntu MATE 20.10 without issues, and before that 20.04, 19.10, etc back to 18.04. No new hardware has been added to my computer.

My hardware specs are:

  • AMD Ryzen 7 2700X Eight-Core Processor
  • 32 GB RAM
  • ASUS ROG STRIX B450-F GAMING Motherboard
  • NVidia GeForce RTX 2070 GPU
  • Sabrent 1TB NVMe M.2 Boot drive
  • 1GB Ethernet port on the Motherboard

I also have a couple USB devices plugged in:

  • USB 3 Thumb Drive with Ubuntu-MATE 21.04 installer image (via BalenaEtcher)
  • USB KVM Switch (only used for keyboard and mouse; video directly plugged to monitor)
  • Logitech HD Pro Webcam C920
  • USB Microphone - BCMaster
  • Multi-card reader with NO external cards (CF, SD, etc...) plugged in
  • External LG USB Bluray/DVD/CD drive that is currently powered down for the install

I took a look at the installer logs written to the USB drive, and in the auth.log file it starts like this:

Apr 25 10:35:28 ubuntu-mate systemd-logind[2294]: New seat seat0.
Apr 25 10:35:28 ubuntu-mate systemd-logind[2294]: Watching system buttons on /dev/input/event1 (Power Button)
Apr 25 10:35:28 ubuntu-mate systemd-logind[2294]: Watching system buttons on /dev/input/event0 (Power Button)
Apr 25 10:35:28 ubuntu-mate systemd-logind[2294]: Watching system buttons on /dev/input/event5 (Logitech K800)
Apr 25 10:35:46 ubuntu-mate python3: pam_unix(su:session): session opened for user ubuntu-mate by (uid=0)
Apr 25 10:35:46 ubuntu-mate systemd-logind[2294]: New session c1 of user ubuntu-mate.
Apr 25 10:35:46 ubuntu-mate systemd: pam_unix(systemd-user:session): session opened for user ubuntu-mate by (uid=0)
Apr 25 10:36:11 ubuntu-mate dbus-daemon[2273]: [system] Failed to activate service 'org.freedesktop.RealtimeKit1': timed out (service_start_timeout=25000ms)
Apr 25 10:36:36 ubuntu-mate dbus-daemon[2273]: [system] Failed to activate service 'org.freedesktop.RealtimeKit1': timed out (service_start_timeout=25000ms)
Apr 25 10:37:01 ubuntu-mate dbus-daemon[2273]: [system] Failed to activate service 'org.freedesktop.RealtimeKit1': timed out (service_start_timeout=25000ms)
Apr 25 10:37:26 ubuntu-mate dbus-daemon[2273]: [system] Failed to activate service 'org.freedesktop.RealtimeKit1': timed out (service_start_timeout=25000ms)
Apr 25 10:37:51 ubuntu-mate dbus-daemon[2273]: [system] Failed to activate service 'org.freedesktop.RealtimeKit1': timed out (service_start_timeout=25000ms)
Apr 25 10:38:16 ubuntu-mate dbus-daemon[2273]: [system] Failed to activate service 'org.freedesktop.RealtimeKit1': timed out (service_start_timeout=25000ms)

The last message repeats for eternity every 30 seconds until I hard shutdown the PC.

To repeat, I am currently running Ubuntu Mate 20.10 on this hardware and it has been running Ubuntu Mate for a couple of years without issue. I have tried the installer on two different USB drives (16Gb) and end up with the same auth.log messages. I have never had an issue installing off of USB drives to this hardware before 21.04.

I have tried searching for a similar issue, but all I find about that issue are some references to a RHEL install.

All suggestions appreciated. I can look for items in other logs, but not sure what would be useful to post. Thanks a bunch in advance. I really want to perform a clean install of Ubuntu Mate 21.04 on my PC.

I reported the exact same issue here the other week, with no replies. Other flavours of Ubuntu 21.04 run fine.

21.04 Beta won't boot from Live USB on Intel NUC 11 systems - Support & Help Requests - Ubuntu MATE Community (ubuntu-mate.community)

EDIT: Interesting... just reflashed a USB, and MATE 21.04 works fine now. Only difference in my system is that the attached HDMI monitor is 4k (2160p), not 1440p. At a guess, something to do with Ubuntu's default switch to Wayland doing something with the display that X doesn't like? Fractional DPI scaling?

I have a similar issue: on booting after a clean install of Ubuntu Mate 21.04 I am stuck with a blank screen.
Three different attempts gave the same result, so I went back to 20.10. Computer works fine, no problem whatsoever.

I am running a 4k monitor, and it still does not boot for me. Like you said, I created USB installs for other Ubuntu flavors and they boot up just fine. It is just the Mate version of the installer that fails to boot. Frustrating.