Ubuntu install not booting normally after live boot ejected

[charles-namibia]

Good day all.

New noob user. I have had the occasional run on Linux and so on but nothing major, I have ditched windows gotten sick of reboots and so on while recording videos and so on.
So, I now find myself trying to get my desktop to run Ubuntu 22.04.3, single OS no dual boot.

Hardware: (prebuilt)
Ran Win 11 22H2
Mobo: Asus ROG Strix-GL12CX
CPU: i7-9700K
RAM: 32Gb
VGA: Geforce RTX 2060
SSD: Kingston 470Gb

I tried using Rufus to create the Live boot USB with but it would not boot, I went over to use Ventoy and loaded the Ubuntu 22.04 64bit ISO.

Ventoy booted up and the install ran without a glitch, when I was asked to remove live boot and press enter (for the PC to reboot from the SSD) I did so, the PC rebooted and my screen went blank, keyboard and mouse LED's went off and remained off.
I had to manually power cycle the machine, I held down shift went to advanced and selected Ubuntu with recovery, Ubuntu booted into the GUI without any issues. I tried getting help on the ask Ubuntu forum, the guys had me use nomodeset and noveau.modeset=0 and I even tried noveau.modeset=1928x1080x32, none of these will let Ubuntu boot normally. I have to hold down shift while booting and enter advanced then boot with recovery to be able to boot into Ubuntu

I have done all the updates, and also installed the proprietary VGA driver.

Can someone help me please? As I said I am a noob.

Regards,
Charles

System report at link below:
https://pastebin.ubuntu.com/p/TdV7gF3CmG/

[MAFoElffen]

I see that you ran the script from an installed system, and have done some other things that would require yuo to be running from an installed system... So please describe how it does boot, what it does do, and not do.

Please post the results of these commands within CODE Tags:

apt list nvidia-driver-* --installed
nvidia-smi
ls -l $HOME

[charles-namibia]

@MAFoElffen

I'm sorry, I thought I did post what the matter was? Ubuntu does not boot on its own from power on...

I have to "make" it boot otherwise the PC does nothing.

This is the only PC (form of communication) I have and can not otherwise post here.

Action:
(1) Push power button, PC comes on, screen comes on, keyboard and mouse LED's Come on.

PC's "ROG" boot screen comes on, keyboard and mouse LED's go off and PC remains infinitely in this state..

(2)Push and hold power button till PC switches off......

Action:
(1) Push power button PC comes on,
(2) I depress and hold the "Shift" key on my keyboard till Grub comes up.

(3) I then select,

Advanced option for Ubuntu

next screen

(4) I then select,

Ubuntu, with Linux 6.2.0-37-generic

next screen

This brings me to the recovery menu,
(4) I then select,

resume

This boots into Ubuntu so that I am able to use it.
This is the ONLY way Ubuntu can be booted.

Code you asked me to run:

apt list nvidia-driver-* --installed
Listing... Done
nvidia-driver-535/jammy-updates,jammy-security,now 535.129.03-0ubuntu0.22.04.1 amd64 [installed]

nvidia-smi

Tue Dec 12 21:49:33 2023       +---------------------------------------------------------------------------------------+
| NVIDIA-SMI 535.129.03             Driver Version: 535.129.03   CUDA Version: 12.2     |
|-----------------------------------------+----------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |         Memory-Usage | GPU-Util  Compute M. |
|                                         |                      |               MIG M. |
|=========================================+======================+======================|
|   0  NVIDIA GeForce RTX 2060        Off | 00000000:01:00.0  On |                  N/A |
|  0%   53C    P8              13W / 170W |    263MiB /  6144MiB |     11%      Default |
|                                         |                      |                  N/A |
+-----------------------------------------+----------------------+----------------------+
                                                                                         
+---------------------------------------------------------------------------------------+
| Processes:                                                                            |
|  GPU   GI   CI        PID   Type   Process name                            GPU Memory |
|        ID   ID                                                             Usage      |
|=======================================================================================|
|    0   N/A  N/A      1302      G   /usr/lib/xorg/Xorg                           74MiB |
|    0   N/A  N/A      1597      G   /usr/bin/gnome-shell                         66MiB |
|    0   N/A  N/A      4706      G   ...irefox/3504/usr/lib/firefox/firefox      120MiB |
+---------------------------------------------------------------------------------------+

ls -l $HOME


total 56
drwxr-xr-x 2 charles charles  4096 Dec 12 13:49 Desktop
drwxr-xr-x 2 charles charles  4096 Dec 12 16:58 Documents
drwxr-xr-x 2 charles charles  4096 Dec 12 16:47 Downloads
drwxr-xr-x 2 charles charles  4096 Dec 12 13:49 Music
drwxr-xr-x 3 charles charles  4096 Dec 12 16:03 Pictures
drwxr-xr-x 2 charles charles  4096 Dec 12 13:49 Public
drwx------ 6 charles charles  4096 Dec 12 16:07 snap
-rw-rw-r-- 1 charles charles 17922 Dec 12 16:14 system-info.txt
drwxr-xr-x 2 charles charles  4096 Dec 12 13:49 Templates
drwxr-xr-x 2 charles charles  4096 Dec 12 13:49 Videos

I hope this helps?

Thank you for your time.

Regards
Charles

[oldfred]

If you have to press shift key to get grub menu, that would indicate a BIOS install. UEFI installs use escape key.
But Windows 11 would have been an UEFI install with gpt partitioning.

Post this:
sudo parted -l

UEFI systems have boot priority, usually UEFI first. But if you have it set for UEFI but actually have BIOS install, then you may have the issue you are seeing.
Query to check if UEFI or BIOS, run same commands, did, and you should get same results if UEFI.

fred@Z170-jammy:~$ [ -d /sys/firmware/efi ] && echo "EFI boot on HDD" || echo "Legacy boot on HDD"  
EFI boot on HDD 
fred@Z170-jammy:~$ if test -d /sys/firmware/efi; then echo efi; else echo bios; fi 
efi

[#&thj^%]

EDIT: See oldfred post above first.
Can you get rid of nVidia for a test login?
My method I use for every install that goes south:

sudo apt autoremove --purge nvidia*

After reboot, and Now can you Login normally?
I do see this from the report though:

Current boot mode:   UEFI Firmware mode
   --- SecureBoot Status from 'mokutil':
SecureBoot disabled

[MAFoElffen]

Yes. That had me a bit confused on what was going on.

Resume from recovery menu... That process differs from a normal boot process as primary from the Grub2 menu by that the Recovery mode grub menu entry with the following differences:

It has nomodeset boot option set
It emits recovery event instead of startup which does the following:
- starts services: hostname, console-setup, setvtrb
- emits mounted event for /run to trigger resolvconf and mounted-run

With resume from the recovery console the start event is emited and the normal boot is started. --> 'nomodeset' is still active as the kernel boot parameter.

So that would indicate that there is a problem with the installed NVidia driver. One is installed... But that has a problem o your hardware.

Boot that way, which will boot in "safe graphics" mode. Open a terminal session:

sudo apt remove --purge nvidia*
sudo ubuntu-drivers list

Look at that list. Install a version other than nvidia-drivers-535...

sudo apt install nvidia-driver-<version>

l

[grahammechanical]

When I used to run Ubuntu with an Nvidia video card I found that Advance Options>Recovery mode>Resume would load Ubuntu using an open source video driver called Nouveau. It can be just as good as the proprietary Nvida driver.

We can use commands to change video drivers. I was more comfortable using Software and Updates>Additional Drivers tab. When connected to the internet Additional Drivers tab would find appropriate Nvidia drivers which I could activate and de-activate to see what worked best. As my video card grew old the newest Nvidia drivers did not support my card so I had to select older drivers. Eventually, support dropped for my card completely. So, it was the open source video driver for me.

If we de-activate the proprietary driver Ubuntu will automatically use the open source driver.

After using Resume to load Ubuntu if the proprietary driver is not disabled then a reboot will try loading Ubuntu with the proprietary driver. That is why your problem continues.

Regards

[charles-namibia]

Good day everyone.

Thank you for all the comments and posts, I will answer all in this post in succession as I can.

1st: @oldfred

If you have to press shift key to get grub menu, that would indicate a BIOS install. UEFI installs use escape key.

I can use either the "shift" or "esc" keys both take me to the grub screen and from there i boot through the recovery screen.

You asked me to post this:

sudo parted -l

Model: ATA KINGSTON SA400S3 (scsi)
Disk /dev/sda: 480GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size   File system  Name                  Flags
 1      1049kB  538MB  537MB  fat32        EFI System Partition  boot, esp
 2      538MB   480GB  480GB  ext4

This is what I got.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

@1fallen

Can you get rid of nVidia for a test login?
My method I use for every install that goes south:

Unfortunately, No, this is the only VGA card I have and the Mobo does not have onboard graphics.

I will try your purge and reinstall and revert back to you.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

@MAFoElffen

Thank you you are saying much the same as @1fallen.
So I will go and do what you are both suggesting and then revert back to you.

Thank you all I will answer shortly.

Edit

So, I have tried ALL the suggestions you all gave me, including something else i found about enabling or disabling Wayland.
This also did not help, I am going to try and install Ubuntu 20.04 to see if this may help.

Regards
Charles

[MAFoElffen]

LOL.

You aree going to have the same result with 20.04. The version is not the problem. You are not understanding yet...

It is booting with "nomodeset" added to the boot line. What that kernel boot option does, is to turnoff the NVidia drivers.

So while booted, if you just did

sudo sed -i 's/quiet splash/quiet splash nomodeset/g'
sudo update-grub

Then that would be added permanently to your grub boot file and your system would use the nouveau opensourced graphics driver for your installation.

If you wanted better graphics, then follow the previous instructions. Those instructions would be the same for Ubuntu 20.04, 22.04, or 24.04 when it releases in a few months.

Alternate instruction would be to start "Software & Updates" > "Alternate Drivers" tab > Choose a driver... Remembering the precious instructions if that version of driver didn't work, to uninstall it and try another that does.

Whatever you do, going backwards in release version will end you up in a hole eventually right? You are going to need to get back to what is current sometime.

[charles-namibia]

Good day @MAFoElffen.

I understand yes, there are also posts saying to try other versions and other flavors which I am doing.

My findings so far, and also where I feel there could be a problem. (I am on my wifes PC now) windows 11.

I have found on this machine that I can use rufus to create the boot image or I can just open the ISO in windows (mount it) I can then copy the contents to a formated exFat or Fat32 memory stick and I can then boot from it and it'll work. I use another SSD though not the win11 SSD. On my PC ** I have to use Ventoy ** If I do not use Ventoy the Live boot will not boot, I think this is where the problem is. Ubuntu 22.04 is also the ** ONLY ** distro that will boot through recovery, none of the others do, and I mean none of them I have tried ALL of them in these past few days....... (20.04 through recovery gets to loading initial ramdisk and then stops dead in it's tracks, no further booting happens after that, none) Also, Ventoy gives me the ability to boot into normal grub or into grub2, grub2 does definitely NOT boot either.

The code you sent last night I ran, and it says sed: no input files? I even copied and pasted it to make sure I was not mistyping.

I do fear that I am running out of options and the only two are, use Ubuntu as it is now (boot through recovery) or go back to windows 11, which I am most certainly NOT looking forward to, most of the software I need to use bar one program now are supported on Linux or Ubuntu............ Rebooting or restarting is a no no for this PC so, I do not know what else to do....

Let me know your thoughts please, I am running out of time and work is piling up so I will have to make a decision very soon.

Regards.