Questions[nomodeset](ubuntu)

So, I changed the resolution of grub by editing the GRUB_GFXMODE line in /etc/default/grub. I also added nomodeset to GRUB_CMDLINE_LINUX_DEFAULT.

Now the problem is, that whenever I boot into Ubuntu, the resolution of grub (800x600) remains. That's not the case when I boot into Windows with grub. I also changed GRUB_GFXPAYLOAD_LINUX, but that doesn't affect my problem in any way.

Eventually I figured out that without nomodeset this problem doesn't occur. Unfortunately I need that flag, as otherwise my PC will boot into a black screen sometimes, with the only way to exit is by killing my PC off.

Any suggestions what could be the problem? I have a AMD RADEON VEGA 10 (Integrated Chip), if that's of any interest.

Information:
OS is Ubuntu MATE 20.04
The AMD Driver is the open source amdgpu. It came out of the box with Ubuntu
The GFXMODE line looks as follows: GRUB_GFXMODE=800x600
When that line is commented out the grub menu has a resolution of 1920x1080, thus making it very slow

I have been having difficulties with my Ubuntu installation.

It will no longer boot and shows a frozen cursor in the top left corner, I have checked many websites and have tried stuff like nomodeset, and I am able to access the console by typing Ctrl+Alt+F2. So I can apply terminal related fixes. I have lost my Ubuntu install USB so that is not an option. I have even tried changing session/display managers. Nothing has worked.

I am using Nvidia graphics cards. Ubuntu has been installed for two months and was working fine until now. This is on Ubuntu 19.10 with dev builds.

I was just installing nvidux or however it's spelled to attempt to overclock my PC's gpu. On reboot it is doing this now.

I have tried many other posts and none of the methods I could do worked. Nomodeset was attempted and failed. I tried changing display managers, failed, and I tried clearing displays from xorg or whatever that was called. Failed, tried many others but forgot what they were. They all changed nothing

I only have access to console so I can't attempt the boot repair tool or anything like that

Booting from another kernel version gets stuck at "Started process error reports when automatic reporting is enabled" and then freezes. Power button works to turn off though

I have an image of it the cursor in the top left, but I can't post due to low reputation.

I have recently installed Ubuntu but could not load it. By searching on Interned I found a solution which works for me but I do not understand it. The solution is taken from here.

In more detail, while I load Ubuntu, I get into a menu which asks me what I want to do. At this point I press e. After that I get a screen with some text where I replace quiet splash by nomodeset and then I press F10. After that Ubuntu loads.

Now, my questions are:

1. What exactly am I doing? Why does it help?
2. Can I do something to avoid doing these steps each time I when I wont to load Ubuntu?

Since installing Ubuntu 12.10 I have been playing around trying to get my Radeon HD 5450 gpu to work with the proprietary driver, as from the start installing the driver meant losing unity.

I won't list the steps I took as it is not a requirement to answering this question.

After taking one measure and then installing fglrx-updates, upon reboot the system hung at the purple screen. So I decided to boot using nomodeset

I edited

quiet splash $vt_handoff

to look like this

quiet splash nomodeset

Making this change I am then able to log in with Unity and the proprietary driver installed and performing well. I would go as far as to say it performs better than it did in 12.04

fglrxinfo reads

display: :0  screen: 0
OpenGL vendor string: Advanced Micro Devices, Inc.
OpenGL renderer string: ATI Mobility Radeon HD 5000 Series
OpenGL version string: 4.2.11903 Compatibility Profile Context

Please note the way I have added nomodeset It had been a while since I have had to do this so it was done from memory. When looking for an answer to this question I came across this and discovered that my edit was supposed to go from

quiet splash $vt_handoff

to

nomodeset $vt_handoff

What has my nomodeset edit done? The only thing wrong that I have noticed is that I don't get the plymouth Ubuntu logo screen when booting.

If that is the only trade-off I am happy to make the edit permanant.

Okay, so I had a dual boot of Tango Studio (based on Ubuntu 10.04) and Windows XP.

Yesterday I downloaded the .iso for Ubuntu 11.10 and attempted to install from a USB (my BIOS won't normally boot from USB but I had PLOP boot manager on a CD). I booted up Ubuntu from the USB and then from there formatted the partition with Tango on and installed Ubuntu 11.10. On booting up I came into Grub rescue mode. So I booted up from the USB again and used boot-repair to reinstall Grub.

After this I would see the normal Grub menu, but on choosing Ubuntu I would come to a black screen. On choosing recovery mode it would begin starting normally with no obvious errors but instead of coming to a cli I would just get a blank screen with a flashing cursor on the top left, not accepting any input.

I have since reformatted and reinstalled from a CD rather than USB and had the exact same problem. I used boot-repair again and the result is the same. Output of the most recent boot-repair is at http://paste.ubuntu.com/869805/

I have also tried editing the ubuntu grub entry and replacing quiet with text nomodeset as I saw in an answer to another question. This got me a bit further - I saw the purple ubuntu loading screen but still came to a blank screen after that. Anyway, in most of the other questions in which that is brought up the user is still able to boot into recovery, while I am not.

Can anyone help? Thanks in advance, let me know if there's any more info I need to provide!

EDIT FOR MORE INFO:

I read something saying it's quiet splash that should be replaced with nomodeset. Earlier I had left splash in the line. So i tried it this way and it froze after displaying the following text:

fsck from util-linux 2.19.1
mountall: Plymouth command failed
mountall: Disconnected from Plymouth
/dev/sda5:clean, 139359/1741488 files, 745830/6961125 blocks

From a bit of googling it doesn't look like plymouth is essential, but I've checked and I do have the most current versions of mountall and plymouth installed so I don't know why there's a problem

EDIT FOR MORE INFO AGAIN:

I used dkpg --reconfigure plymouth cause I saw it mentioned in another forum and it still says plymouth command failed on boot

FOLLOW UP - JULY

Unfortunately I was not able to get this working. I needed it working and switched distribution before anyone commented or answered this question, so am unable to try out any suggestions posted here

I'm thinking of giving this another go sometime soon, if I do then I'll report back.