My pc does not boot Kubuntu .iso anymore.

[Gromm]

A strange situation here. I wanted to boot a Kubuntu 22.04 iso lately. The grub showed up in which I could choose what to do but after that a long time of black screen and a usb stick that was doing something (flickering light) but without result. This occurs only with iso's from the Ubuntu family (Ubuntu. Kubuntu, Ubuntu Studio.).
The same iso does start up on another machine. That one has a bios instead of an uefi.

On the uefi machine all other iso's like Debian KDE, Mx Linux, Mint, KDE neon and Manjaro KDE start up with no problems. I want however, to install Kubuntu on this machine. In the past that was simply possible with no problems whatsoever. What happened here and how to solve it?

[kc1di]

That is a strange one. For starters give us some info on the machine make, model, etc. And did you check the download to make sure it was correct? I am surprised that Mint would boot but ubuntu would not since the pretty much use the boot software. if you can get mint to boot go to a terminal and issue this command and post the results back here.

inxi -Fxxxzr

[Schwarzer Kater]

If e.g. the 22.04.3 ISO does not boot you could try another point release like the 22.04.2 or 22.04.1 ISO…

[Gromm]

That is a strange one. For starters give us some info on the machine make, model, etc. And did you check the download to make sure it was correct? I am surprised that Mint would boot but ubuntu would not since the pretty much use the boot software. if you can get mint to boot go to a terminal and issue this command and post the results back here.

inxi -Fxxxzr

Ok, here goes.

ystem:
Kernel: 5.15.0-92-generic x86_64 bits: 64 compiler: gcc v: 11.4.0
Desktop: Cinnamon 6.0.4 tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0
Distro: Linux Mint 21.3 Virginia base: Ubuntu 22.04 jammy
Machine:
Type: Desktop System: HP product: OMEN 25L Desktop GT12-0xxx v: N/A
serial: <superuser required> Chassis: type: 3 serial: <superuser required>
Mobo: HP model: 87C3 v: 00 serial: <superuser required> UEFI: AMI v: F.24
date: 07/11/2022
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M215 2nd Gen
serial: <filter> charge: 100% (should be ignored) rechargeable: yes
status: Discharging
CPU:
Info: 12-core model: AMD Ryzen 9 3900 bits: 64 type: MT MCP smt: enabled
arch: Zen 2 rev: 0 cache: L1: 768 KiB L2: 6 MiB L3: 64 MiB
Speed (MHz): avg: 2295 high: 3711 min/max: 2200/3100 boost: enabled
cores: 1: 2196 2: 2192 3: 2196 4: 2048 5: 3711 6: 2064 7: 2196 8: 2194
9: 2196 10: 2195 11: 2196 12: 2195 13: 2199 14: 2194 15: 2195 16: 2091
17: 3591 18: 2055 19: 2199 20: 2203 21: 2188 22: 2196 23: 2196 24: 2194
bogomips: 148521
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
Device-1: NVIDIA GA104 [GeForce RTX 3070] vendor: Hewlett-Packard
driver: nvidia v: 535.154.05 pcie: speed: 2.5 GT/s lanes: 16 ports:
active: none off: DP-1,HDMI-A-1 empty: DP-2,DP-3 bus-ID: 23:00.0
chip-ID: 10de:2484 class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: nvidia
unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia display-ID: :0
screens: 1
Screen-1: 0 s-res: 3600x1080 s-dpi: 101 s-size: 905x272mm (35.6x10.7")
s-diag: 945mm (37.2")
Monitor-1: DP-1 pos: primary,left res: 1680x1050 hz: 60 dpi: 90
size: 474x296mm (18.7x11.7") diag: 559mm (22")
Monitor-2: HDMI-0 pos: primary,right res: 1920x1080 hz: 60 dpi: 102
size: 476x268mm (18.7x10.6") diag: 546mm (21.5")
OpenGL: renderer: NVIDIA GeForce RTX 3070/PCIe/SSE2
v: 4.6.0 NVIDIA 535.154.05 direct render: Yes
Audio:
Device-1: NVIDIA GA104 High Definition Audio vendor: Hewlett-Packard
driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 16
bus-ID: 23:00.1 chip-ID: 10de:228b class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: Hewlett-Packard
driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
bus-ID: 25:00.4 chip-ID: 1022:1487 class-ID: 0403
Sound Server-1: ALSA v: k5.15.0-92-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: speed: 5 GT/s
lanes: 1 bus-ID: 21:00.0 chip-ID: 8086:2723 class-ID: 0280
IF: wlo1 state: down mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Hewlett-Packard driver: r8169 v: kernel pcie: speed: 2.5 GT/s
lanes: 1 port: f000 bus-ID: 22:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp34s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8
bus-ID: 1-10:4 chip-ID: 8087:0029 class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 0 state: down
bt-service: enabled,running rfk-block: hardware: no software: yes
address: <filter>
Drives:
Local Storage: total: 1.38 TiB used: 32.85 GiB (2.3%)
ID-1: /dev/nvme0n1 vendor: Western Digital
model: PC SN530 SDBPNPZ-512G-1006 size: 476.94 GiB speed: 31.6 Gb/s
lanes: 4 type: SSD serial: <filter> rev: HPS2 temp: 21.9 C scheme: GPT
ID-2: /dev/sda vendor: Seagate model: ST1000DM003-1SB102 size: 931.51 GiB
speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: HPH5 scheme: GPT
Partition:
ID-1: / size: 48.91 GiB used: 32.75 GiB (67.0%) fs: ext4
dev: /dev/nvme0n1p5
ID-2: /boot/efi size: 256 MiB used: 102.8 MiB (40.2%) fs: vfat
dev: /dev/nvme0n1p1
Swap:
ID-1: swap-1 type: partition size: 4 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/nvme0n1p7
Sensors:
System Temperatures: cpu: 38.0 C mobo: N/A gpu: nvidia temp: 23 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 33%
Repos:
Packages: apt: 2302
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
1: deb https://mintlinux.mirror.wearetriple.com/packages virginia main upstream import backport
2: deb http://ftp.tudelft.nl/archive.ubuntu.com jammy main restricted universe multiverse
3: deb http://ftp.tudelft.nl/archive.ubuntu.com jammy-updates main restricted universe multiverse
4: deb http://ftp.tudelft.nl/archive.ubuntu.com jammy-backports main restricted universe multiverse
5: deb http://security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
Info:
Processes: 459 Uptime: 3m wakeups: 2 Memory: 31.25 GiB used: 2 GiB (6.4%)
Init: systemd v: 249 runlevel: 5 Compilers: gcc: 11.4.0 alt: 11/12
Shell: Bash v: 5.1.16 running-in: gnome-terminal inxi: 3.3.13

In answer to more of your questions: All the tried iso's where checked, verified etc etc. Tested on other systems than this one. It is a strange problem indeed. Furthermore, in the past there where no such problems at all... It does not seem logical but it all occured after I installed and de-installed Manjaro KDE, that can never be connected one might think...
That Mint does boot and the Ubuntu's don't occured to me as strange as well already...But then: Debian and other direct debian based distros also do not give any problems and neither does an Arch based as Manjaro.

[Gromm]

If e.g. the 22.04.3 ISO does not boot you could try another point release like the 22.04.2 or 22.04.1 ISO…

I looked for those at Kubuntu.org. When I clicked on the 22.04.2 release, I was redirected to the .3 so I could not find those versions. No matter, first we'll see where things lead to.

[kc1di]

Thanks for the info. I would be suspicious of the Nvidia graphics card. You can try booting with "nomodeset" perimeter and see if that will allow it to boot. if it does after installation you will have to install the correct Nvidia driver for your card.
This page will tell you how to set that in the boot line. https://www.dell.com/support/kbdoc/e...-linux-booting
There are other possibilities also you may need a newer kernel. I would in bios /UEFI disable secure boot also.
Good luck.

[Gromm]

Thanks for the info. I would be suspicious of the Nvidia graphics card. You can try booting with "nomodeset" perimeter and see if that will allow it to boot. if it does after installation you will have to install the correct Nvidia driver for your card.
This page will tell you how to set that in the boot line. https://www.dell.com/support/kbdoc/e...-linux-booting
There are other possibilities also you may need a newer kernel. I would in bios /UEFI disable secure boot also.
Good luck.

Will try that "nomodeset" soon. But how can an Nvidia driver be the problem here? And where does that driver need to be installed then since usually a driver is installed in the operating system and this is a "pre-installation problem". This might be beyond my IT skils and knowledge. The secure-boot option is turned off already and legacy support is switched on standard. To be continued...

Bingo! The nomodeset-command did the trick. Next question: what exactly caused this problem if it related to the Nvidia GPU? And why does it occur now where it never caused any trouble before? And what about your suggestion of a newer kernel? Isn't a post-installation issue as well? Anyway, as we speak Ubuntu-Studio is just finished installing. Thank you for your golden tip, furthermore I would like to understand this all so if we just can continue with this thread a bit that might broaden my knowledge.

Update: although it did work, I could not boot the installed system afterwards without using the recovery mode. Now I am installing the updates to see what that does. No halleluja just yet! :P

[kc1di]

Yes your right about the drivers being installed in the system after install. But every distro handles Nvidia card in different ways. Some include nvidia drivers some do not.
ubuntu and Kubuntu usually use the nouveau open source driver. Which does not always work well with every nvidia card. Thus the need for nomodeset to get it going.
Here is a page about installing Nvidia Drivers after installing the system.
https://www.linuxcapable.com/install...-ubuntu-linux/
Problem is that most Nvidia drivers are propitiatory and not open source. Thought they are getting better with linux, they are not there completely yet.

[Gromm]

Will try that "nomodeset" soon. But how can an Nvidia driver be the problem here? And where does that driver need to be installed then since usually a driver is installed in the operating system and this is a "pre-installation problem". This might be beyond my IT skils and knowledge. The secure-boot option is turned off already and legacy support is switched on standard. To be continued...

Bingo! The nomodeset-command did the trick. Next question: what exactly caused this problem if it related to the Nvidia GPU? And why does it occur now where it never caused any trouble before? And what about your suggestion of a newer kernel? Isn't a post-installation issue as well? Anyway, as we speak Ubuntu-Studio is just finished installing. Thank you for your golden tip, furthermore I would like to understand this all so if we just can continue with this thread a bit that might broaden my knowledge.

Update: although it did work, I could not boot the installed system afterwards without using the recovery mode. Now I am installing the updates to see what that does. No halleluja just yet! :P

Update2: the updates seemed to do the trick. Ubuntu Studio is operational and running as of now. Although I fear the OS itself will be a bit buggy from time to time. Luckily I have a mint cinnamon partition as a safety precaution. (Sorry, you fanatic KDE users, I prefer KDE as well but with an NVidia card and KDE does not always seem to be a good match...)

[kc1di]

I'm sorry you have given up on Kubuntu I'm sure it can be made to work. But I understand maybe you'll come back to it soon. Good luck.

[Gromm]

Well, me thinks you misunderstood me. I haven't given up on Kubuntu/ KDE at all. (In case it is not known to you: Ubuntu studio is running on Plasma lately and the way I see it, it is Kubuntu with more pre-installed creative software.) I just have an extra installation of Mint as a precaution because of the trouble with kde and Nvidia from time to time. And no matter how much I prefer KDE/Kubuntu, Mint cinnamon gives much less problems. But I prefer KDE so I have a triple -boot now. Windows only for gaming.

The only thing I need to bring in order now is my wacom cintiq tablet. The thing is still offset, when I want to draw, the cursor is centimeters away from the tip of my pen. Anyway, thank you for your support. It took me days to figure out a possible solution and you come with someting that solves it instantly.

[kc1di]

I'm glad I was mistaken Hope everything will work out for you and my pleasure being of help.

[Gromm]

I'm glad I was mistaken Hope everything will work out for you and my pleasure being of help.

Now I hope to figure out why oh why this extra step you suggested was needed... I want to understand, although it might be stuff for an IT-expert which I am not.