Black screen after switching to a new keyboard

[dev0null]

Hello, new OM user here coming(escaping) from debian!

yapping

Everything worked so well I didn’t even notice the installation process. I was looking around the live iso then I hit the install button and not even 5 minutes later I booted into the new system, huh? With debian I would have sat there for at least 20 minutes . Good job!

Requirements:
I have Searched the forum for my issue and found nothing related or helpful
I have checked the Resources category (Resources Index)
I have reviewed the Wiki for relevant information
I have read the the Release Notes and Errata

OpenMandriva Lx version:
OpenMandriva Lx release 6.0 (Vanadium) Rock for x86_64

Desktop environment (KDE, LXQT…):

• Plasma 6
• X11
• Nouveau

Description of the issue (screenshots if relevant):
The system boot into a black screen, it gets past the initrd. The issue started happening after I switched the keyboard with a new one while the PC was on and in user space; everything seemed to be working fine until I restarted the system.

This only happens (100% reproducible) when the keyboard plugged in is not the one with which OMLx was installed. I tried 3 different keyboards in total.

I have been looking for xorg and sddm logs, a config file or some sort of device id stored somewhere but could not get ahead of myself.

Also, at line 669 of the xorg log file seems that my external sound card is recognized as keyboard:

event4  - BurrBrown from Texas Instruments USB AUDIO  CODEC: is tagged by udev as: Keyboard

---

Relevant informations (hardware involved, software version, logs or output…):

• The logitech G413 is the keyboard used during the installation of OMLx

  input: Logitech G413 Carbon Mechanical Gaming Keyboard as /devices/pci0000:00/0000:00:07.1/0000:0a:00.3/usb3/3-1/3-1:1.1/0003:046D:C33A.0006/input/input20
  input: Keychron Keychron K10 Max Keyboard as /devices/pci0000:00/0000:00:07.1/0000:0a:00.3/usb3/3-2/3-2:1.2/0003:3434:0AA1.0009/input/input27
  

• The sddm.conf is the default one and the theme is breeze
• Xorg log: xorg.log.txt (73.8 KB)

[grafi]

I looked through your xorg.log.txt. The black screen is not caused by the new keyboard — it’s a graphics driver issue. Here’s what stands out:

• Your GPU is NVIDIA (10de:2484), but Xorg is only loading the modesetting driver, not the proprietary NVIDIA driver.
• Errors:
  • xf86EnableIO: failed to enable I/O ports (Operation not permitted)
  • open /dev/fb0: No such file or directory
• Xorg is falling back to fbdev/vesa/modesetting instead of using NVIDIA’s driver.

That usually leads to a black screen right after boot/login.

Try to install proprietary drivers from repo or the nvidia side.

Yet I must add one thing and I’m sorry for being blunt here. Change GPU to radeon or change a distro.

I recently faced the same choice.
I chose to change cards.
But that’s me.

I don’t know what you’ll do.

Anyway here is the post about one of my issues

Nvidia RTX 3060 display issues

Hello, Requirements: I have Searched the forum for my issue and found nothing related or helpful I have checked the Resources category (Resources Index) I have reviewed the Wiki for relevant information I have read the the Release Notes and Errata **OpenMandriva Lx version:6 Desktop environment (KDE 6, ): Description of the issue (screenshots if relevant): Issues A lot of weird, little strange and random behaviors hard to document catch and categorize Resolution issues One moni…

here is why it happened
Openmandriva impossible to install on rtx 3060:

@zeroability

I would like to reiterate something important that is not quite being understood by many.

We do not “support” packages from the non-free repository. No distro does in their equivalent repositories. This is because the source is proprietary. Every single distro makes their best effort to offer it as a convenience for the

Just read a full post by @zeroability

[dev0null]

Thank you for your help and your time.

@grafi

it’s a graphics driver issue

Yes I have seen the error you mentioned. Perhaps I need to clarify the situation.

I installed OpenMandriva 3 days ago, everything worked so well I didn’t feel the need to install Nvidia drivers since the DE experience was really smooth even with a dual monitor setup (this has been a major issue for me on Gnome-X11 where everything felt buggy and stuttery).

The system boot process completes successfully when the G413 keyboard is connected. The problem is triggered specifically by the use of a different keyboard.

It sounds really weird. I searched online a lot and even put the AI to work to find the same issue (not specifically on OpenMandriva) to no avail.

@grafi

I don’t know what you’ll do.

As of right know I’m not doing anything that requires proprietary drivers so I’m totally fine with the Nouveau driver.

[grafi]

I can only echoing what developers told me, when I asked similar question.

If you still use dual monitors, try to switch cables or “hdmi” sockets 1 -2 with 2-1 unplug one of the monitors. If the error will be resistant, then you have two options, proprietary driver or card change.

If you have any onboard gpu you may install proprietary drivers by this metod

If you fressh Install OM and have something Like nvidia 810 840M or other stone age nvidia gpu. Read this

Your GUI get carazy? hangs, blinks, freezes, drops in to usless cosole, drops dead come back alive, and drops ded again over and over. Do this At Grub2 Menu go to Advanced Options>Console Mode that should boot to a login prompt login with your user name login to the system Only bold text repo is mandatory sudo dnf config-manager --enable rock-x86_64-non-free rock-updates-x86_64-non-free sudo dnf config-manager --enable rock-x86_64-restricted rock-updates-x86_64-restricted sudo dnf che…

That’s probably the best way to install this driver smoothly.

If that doesn’t help then I’m clueless as you are now.

Only think I’m quite sure that NVIDIA is absolutely unpredictable on OM.
One day they work and another they don’t for no apparent reason

The main problem with them is they are closed source for the most part

[LeeTalbert]

Can you boot to a TTY with console mode? If so, can you get to a desktop with startx ?

[rugyada]

@dev0null

[dev0null]

@LeeTalbert

Can you boot to a TTY with console mode? If so, can you get to a desktop with startx ?

Not consistently, usually the system become unresponsive but I think a couple of time I was able to log in on TTY2 and started a X session but it was broken, it erased my kde wallet and reset some of the DE configurations.
Also I tried to restart sddm before starting an X session but didn’t work at all and systemctl status reported it working correctly with no errors.

@rugyada

Thank you!

[LeeTalbert]

At the grub menu go into advanced options and select the console mode to boot. This goes straight into a TTY without you needing to do Ctrl+alt+F#. If you can boot into this then the problem is most likely the graphics driver. I can’t imagine why a keyboard would have any impact on booting.

What GPU do you have?

[dev0null]

My GPU is an RTX 3070.

I confirm I can boot in console mode (with the new keyboard too). I tried starting sddm and it went unresponsive again.

I know must be a graphics driver issue but I swear this keyboard took over my pc hahaha. Currently the only way to log in to a graphical session is to use the old one.

Should I try tinkering with udev rules? Should I install nvidia drivers?

[grafi]

I would go NVIDIA drivers from repo

[LeeTalbert]

Does startx from console mode give you a stable desktop?

So far it sounds like something with nvidia and sddm not cooperating

[dev0null]

Yes, booting in console mode (or disabling sddm) then manually starting an X session gives a stable desktop; my bad the first time I tried to do it, when the kde wallet dialog popped up I just closed it and that led to the overwrite of some configs.

For now I’ll just ditch display managers and login from console.