Installing OpenMandriva Rome only leaves a black screen

I have been having a lot of issues with the installer since last night. A bunch of the installers launch with a completely black screen. The one that did work the longest only worked until I started doing system updates which led to the OS having a black screen with “_” visible. My latest installation actually launches into a black screen despite having done a successful fresh install with 24.12 Wayland.

Any ideas on how to solve this?

I’m afraid that what you write is not enough to understand what the issue is about.
Please provide more info, thanks.
One above all: how did you do the system upgrade?

PS> I move the topic to the proper place: Support.

systemd[1] : failed to start systemd-vconsole-setup.service - Virtual Console Set

I just noticed that this message flashed for a millisecond on my screen before turning into “_”. Used my phone to record it and write down the error message, since it was impossible to read any other way. The black screen provides no other useful error messages besides this one for the Wayland installation of Rome 24.12.

I am using Ventoy for my USB. Wasn’t an issue last night with 24.07 beyond that known issue, but the installer seems to degrade for some reason. The ISO version I used last night stopped working after having done a successful attempt, which then resulted in the system updates and/or Nvidia drivers to break OpenMandriva. I have no idea why it is breaking down besides the info I provided.

Agree with @rugyada we need more info. Also it is much easier to solve a problem than a shotgun list of problems.

That’s one problem with some installers but which ones?

This seems to be another problem which @rugyada answered,

One above all: how did you do the system upgrade?

And this seem to be a third problem. The first guess is that 24.12 Wayland is not working on your hardware for some reason so try 24.12 X11 and see if that works.

If possible could we focus on getting one thing, whatever is most important to you, to work? Edit: Also keep in mind that there is a big difference between an installer and an installed system it is important to be clear on that.

All of them besides the Wayland installer mentioned. The X11 installer refuses to launch into the desktop to start installing whether it is the 24.07 or 24.12 versions.

Most of the installers do not work for the same reason and the ones that do lead to the finished fresh install to launch into a black screen. Black screen from both ends.

Not trying to get in the way here, but Frozen_Death_Knight, can you state to the best of your ability what your hardware is?

1 Like

Well nothing I can not do without a specific example. Do you mean the installers you would have downloaded from SourceForge?
You need to tell us what hardware you are using?
Like do you have nVida graphics? That is one of the first suspects.

What we are seeing is most likely a hardware issue of some kind.

I test a lot of these isos and so do other OM contributors plus a lot of users do use them. So maybe I am being to persnikity but the issue is that the installer does not work for you, The most likely explanation is hardware, like nvidia,

It is exceeding unusual that Wayland would work and X11 does not, that really baffles me. And I honestly would like to find out why.

In some Linux systems you can get complete hardware info with inxi -f or to post here like this:

inxi -F > inxi.txt

That creates the file inxi.txt which you can then post here.

Ryzen 9 5950X CPU.

ROG Strix X570-E Gaming motherboard.

NVIDIA GeForce RTX 3060.

64 GB 4000 Mhz RAM (downclocked to 3600 Mhz for best performance with the other hardware).

System:
Host: Kernel: 6.8.0-51-generic arch: x86_64
bits: 64
Desktop: Cinnamon v: 6.2.9 Distro: Linux Mint 22 Wilma
Machine:
Type: Desktop Mobo: ASUSTeK model: ROG STRIX X570-E GAMING v: Rev X.0x
serial: UEFI: American Megatrends v: 4021
date: 08/09/2021
CPU:
Info: 16-core model: AMD Ryzen 9 5950X bits: 64 type: MT MCP cache:
L2: 8 MiB
Speed (MHz): avg: 3511 min/max: 2200/5382 cores: 1: 3600 2: 2200 3: 3600
4: 3600 5: 3599 6: 3600 7: 3600 8: 3600 9: 3591 10: 3601 11: 3598 12: 3600
13: 3600 14: 3598 15: 3599 16: 3598 17: 3599 18: 3593 19: 3600 20: 3613
21: 3600 22: 3600 23: 3598 24: 3599 25: 3592 26: 3601 27: 3598 28: 3600
29: 3598 30: 2200 31: 3595 32: 3600
Graphics:
Device-1: NVIDIA GA106 [GeForce RTX 3060] driver: nvidia v: 565.77
Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.6 driver: X:
loaded: nouveau unloaded: fbdev,modesetting,vesa failed: nvidia
gpu: nvidia,nvidia-nvswitch resolution: 1: 5120x1440~240Hz
2: 1920x1080~60Hz
API: EGL v: 1.5 drivers: kms_swrast,nvidia,swrast
platforms: gbm,x11,surfaceless,device
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 565.77
renderer: NVIDIA GeForce RTX 3060/PCIe/SSE2
Audio:
Device-1: NVIDIA GA106 High Definition Audio driver: snd_hda_intel
Device-2: AMD Starship/Matisse HD Audio driver: snd_hda_intel
Device-3: Roland UA-S10 driver: snd-usb-audio type: USB
API: ALSA v: k6.8.0-51-generic status: kernel-api
Server-1: PipeWire v: 1.0.5 status: active
Network:
Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi
IF: wlp5s0 state: up mac: b0:a4:60:32:52:c1
Device-2: Realtek RTL8125 2.5GbE driver: r8169
IF: enp6s0 state: down mac: fc:34:97:9e:1c:76
Device-3: Intel I211 Gigabit Network driver: igb
IF: enp7s0 state: down mac: fc:34:97:9e:1c:75
Bluetooth:
Device-1: Intel AX200 Bluetooth driver: btusb type: USB
Report: hciconfig ID: hci0 state: up address: B0:A4:60:32:52:C5 bt-v: 5.2
Drives:
Local Storage: total: 11.85 TiB used: 6.91 TiB (58.3%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 980 PRO 1TB size: 931.51 GiB
ID-2: /dev/nvme1n1 vendor: Kingston model: SFYRD2000G size: 1.82 TiB
ID-3: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB
ID-4: /dev/sdb vendor: Samsung model: SSD 870 EVO 500GB size: 465.76 GiB
ID-5: /dev/sdc vendor: Seagate model: BUP BK size: 3.64 TiB type: USB
ID-6: /dev/sdd vendor: Seagate model: Expansion HDD size: 4.55 TiB
type: USB
ID-7: /dev/sde vendor: SanDisk model: USB 3.2Gen1 size: 28.65 GiB
type: USB
Partition:
ID-1: / size: 1.79 TiB used: 1.65 TiB (92.4%) fs: ext4 dev: /dev/nvme1n1p2
Swap:
ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) file: /swapfile
Sensors:
System Temperatures: cpu: 48.0 C mobo: 44.0 C gpu: nvidia temp: 55 C
Fan Speeds (rpm): N/A gpu: nvidia fan: 0%
Info:
Memory: total: 64 GiB note: est. available: 62.7 GiB used: 15.57 GiB (24.8%)
Processes: 700 Uptime: 42m Shell: Bash inxi: 3.3.34

Hope that helps. The hard drive I installed it on (Samsung SSD 860) had a fully functional install of Mint 21.3, so the hard drive has been working just fine.

Need to sleep for now, so I’ll get back to this topic later when I get the time again.

It is most likely something to do with nVidia graphics which I am not the best person to help with. Plus it is late here. I’ll look some more tomorrow or maybe @zeroability or @bero will see this.

1 Like

It’s booting into a wayland session. Could you try the X11 ISO again?

Just did with 24.07. Black screen still. Been trying at least 6 different ISOs at this point and Wayland is the only one right now that even launches properly.

That is on boot up, or after logging into the desktop?

The desktop with the installer from the USB. I get a menu to choose options when launching the ISO. I pick the top option with the name of the distro version and instead of a desktop to try it I get a black screen with no error message.

It sounds almost like it’s trying to decide what graphics card or connection to use. By default, it should be booting with nouveau driver. You just have the nvidia card, right? Not an onboard or hybrid card like some laptops have?

I run a desktop PC with an Nvidia card. Not sure if the PC has an integrated GPU. I did not install one when I built this PC on my own.

I have a Wacom Cintiq 13 inch HD screen alongside my G9 Odyssey screen connected to the Nvidia card. Can that cause issues?

Probably not then. I would try a different DP or DVI and see if you can reproduce. I have seen silly stuff like that happen. Just to rule it out and it’s easy.

Edit:

It could possibly, yeah.

1 Like

How did you transfer the ISO you downloaded to the USB stick?

1 Like

Yes, that is also a possibility, should have thought of that. How isos are downloads might be a possibility as well.