3

I have always used windows and recently decided to make the switch to linux, electing to test it on my laptop before installing it on my main desktop PC.

I downloaded ubuntu 18.04.02 LTS ISO file and mounted it to a USB thumb drive using rufus, booted to from the USB drive, installed ubuntu and upon restarting I am just left with a black screen displaying

/dev/nvme0n1p2: clean, XXXX/XXXX files, XXXX/XXXX blocks

The numbers on this screen do not move and even after leaving it running for the 8 hours I was at work it did not get any further. I have tried re-installing ubuntu twice even remounting the ISO again but I am met with the same result each time.

I am able to boot the laptop in recovery mode and from here I can access the desktop but I wouldn't know where to begin to look for ways to fix the issue from here.

UPDATE 04/07/19: Just to collate all the information that has come out in the comments below for anyone else looking to help.

The full specs of the laptop are:
CPU: AMD Ryzen 5 3550H
RAM: 8 GB DDR4
GPU: AMD Radeon RX 560X 4 GB,
I am installing Ubuntu on an NVMe SSD.

In BIOS I have disabled Secure boot & Fast boot settings and enabled UEFI sata config. There are no visible options for RAID settings in my BIOS for this laptop, so I am working under the assumption it is disabled.

I have verified the MD5 checksum of the ISO file for installation and it is a match. When writing the ISO to the USB I followed the Official Tutorial and used Rufus and all the settings from the tutorial, I have also tried using Etcher as well and still the same issue. I have not yet been able to verify if the USB device itself is faulty or not as I have no other devices that can hold enough space for the ISO file (I also am unable to write to DVD as this laptop does not have a DVD drive and I do not have an external one).

I am unable to boot to the live USB desktop. When doing so I met with a few errors that flash past too fast to read and then the following appears:

[OK] started session cX of user gdm. Starting user manager for UID 121. 
[OK] Started user manager for UID 121. Stopping user manager for UID 121

which repeats increasing the value of cX until it reaches a point where it just stops

I have tried changing a few boot settings from the grub menu on both the current install and on the live USB.

Tried the following: Remove quiet splash and added nomodest text loglevel=0 and again with loglevel=7 instead of 0

All times this was attempted, the boot started with less error messages and more initializing various features, but eventually went to the same gdm... UID 121 messages, only this time with the final error message at the end:

[FAILED] Failed to start user manager for UID 121. See 'systemctl status user@121.service' for details
Gryu
  • 8,002
  • 9
  • 37
  • 53
serendipity0
  • 31

3 Answers3

0

Stealing from the comment chain above:

i ran into this same problem and was able to make this work properly by disabling secure boot and ensuring UEFI boot mode was enabled

Mr. Cat
  • 1
0

Disable hibernate in Windows, disable fast boot, then go in to grub, choose kernal, press e, then at the end of the Linux boot instructions type "nvme_core.default_ps_max_latency_us=5500" "idle=nomwait"

SDW_1980
  • 172
  • 3
  • 13
0

This question is 8 months old, but I found a documented answer after I had a problem for a while myself, and want to share it with whoever finds this question. Ubuntu 18 and 19 had some problems with rufus versions under 3.7 because of a bug. Reference

This problem may occure when organizations or private users usually do not refresh their toolbox with new rufus versions.

Version 3.7 fixed ubuntu 19.10, yet 18.04 is still bugged in that version.

Overall this is less of a problem now, since latest rufus update fixed both versions and now stands at version 3.9.

Official online tools and downloads can be found here

Pizza
  • 1,512