Installed on actual hardware (Lenovo Thinkpad X1 Carbon 2021 with Intel graphics. Installed wayland version originally, experienced issues, found a command on this forum to change it to x11 and have logged in using x11 and still experienced the issue. After the laptop is shut down or asleep for a while, it doesn’t wake properly and the screen is just black and the keyboard doesn’t work. I don’t know if this next part is all the time, but I read a post somewhere that said it was just very dim, not off, and I held a flashlight up to the screen and saw that it was on the login screen, but the backlight was not on, and nothing worked so I couldn’t just type my password to log in. I also read a post where someone mentioned plugging in an external monitor and after 5 or 10 times plugging it in and alternating between the USB C ports, sometimes it changes to displaying correctly on the external monitor, then sometimes unplugging that monitor changes the laptop display to work properly, but not all the time. To confirm, I have looked on this forum and not found this exact issue. There were other posts about NVidia graphics, does not apply. This laptop has intel graphics. There were other posts about 2nd monitors, does not apply. This is about the built in laptop display. There were other posts about virtual machines, does not apply. This is on actual hardware. There were other posts about a black screen with a white cursor on the display, SOMEtimes this happens when plugging in an external monitor, but not all the time and this does not happen on the built in display. There were posts about wayland being a problem, does not apply as it happens on both wayland and x11. I have also completely wiped everything and done a fresh installation, the issue still happens.
Description of the issue (screenshots if relevant):
It is not a hardware issue because the laptop worked fine with Windows 11. Unless the claim is that OpenMandriva is not compatible with 4 year old Lenovo laptops?? If so, please let me know. I wanted to use OpenMandriva because I want to show support for the non-woke approach after learning how basically all the other distros and desktop environments hate anyone who disagrees with them, but it is very frustrating so far…
I write at the risk of having to admit that I missed the point in what you wrote. Apologies if I did.
Could you please narrow down the problem to a sentence or two at the most? The paragraph under " Desktop environment (KDE 6.3.4, LXQT 6.9):" says a lot but it seems to amount to “It’s broke”. We can’t fix it’s broke we need something more specific. The paragraph under " Description of the issue (screenshots if relevant):" does not seem to describe any issue. So if you could better help me understand that would be appreciated.
We will definitely need to know what intel graphics? The version matters. What is the output of inxi -G?
See if one of these existing topics fits your issue:
If none of those are relevant we need logs. Specifically we need logs from when you are having the problem. If you don’t know how to do this we can work it out once we get to a specific problem.
A guess. What kernel are you using? We have had users reporting problems with this kernel-rc-desktop-6.15.0-0.rc2.3 which got incorrectly installed due to a bug. If you have that could you boot into kernel-desktop-6.14.2-3 if that one does not work better, it has for most everyone.
Edit: If you do have the kernel-rc-desktop-6.15.0-0.rc2.3 we can correct that easily. But I thought it would be best to first see if we can get your graphics issue sorted.
I appreciate the assistance. I am not very familiar with linux, so I don’t really understand the terminology or the technologies underneath the desktop environment. If possible, I would be happy to share logs, but would need instructions on exporting them.
I am on kernel 6.14.2-desktop-3omv2590 (64-bit)
Unfortunately those other posts aren’t the issue I’m experiencing. The blinking cursor thing happens sometimes, but not all the time and that is only on the external monitor, not on the built in laptop display.
We are working on the issue with not supporting dual monitors. I think the work around is to wait till you are logged in to plug in the external monitor. Our devs are working on it.
Just clarifying that I am experiencing the problem on the built-in laptop display, not just on an external monitor. Plugging and unplugging an external monitor in 5 or 10 times is what sometimes randomly fixes the issue on the internal display temporarily.
You may find that there are a good number of problems reported with this hardware under Linux, not just with OpenMandriva. One solution I saw here suggested switching to ‘Performance’ power profile which you can do in SystemSettings>Power Management:
Ok, I have switched that setting to Performance on AC, battery, and low battery. To test, I will need to leave it off for a while as even before making that change it would rarely happen after immediate reboots. If the issue happens again, it may be a while before I can temporarily fix the issue to be able to use the computer and post an update here… But to verify I understand correctly, is the idea that 4 year old graphics are too new to be correctly supported in linux? Anything from 2021, 2022, 2023, 2024, or 2025 is incompatible? Or is it just this particular graphics setup from intel on that year only?
No, what I am reading suggests that intel has been working on a xe driver all these years and does not have one ready for LInux so users have to use the older i915 driver which seems to be a problem for this graphic card or device. That there should be an xe driver but till now there is not, which is on intel. If I understand correctly. AFAIK Intel does participate with kernel.org so I do not know what would be the reason for this.
This is a Linux Mint post about exactly this dated Dec. of 2024 so recent. Basically explaining how there should be an xe driver but users are stuck with the less than ideal for this hw i915 exactly as your are:
I do not like this and do not like not having a better answer for users. There may be better workarounds than any I have come up with. I do not have this hw so can not test either.
Another “next” thing to try is: We have seem some users get better results by using kernel-server-6.14.2-3 to install that:
Open terminal (Konsole) and type:
sudo dnf in kernel-server
When installed reboot and at grub2 menu go to the Advanced Options line and look for the first entry for kernel-server.
Lest anyone think we are trying to alibi our way out of a problem the code for any graphics normally comes from the company that makes the hardware, ie. AMD. Intel, or nVidia.
And I tried to find the XE driver for Linux at Intel but they clearly only have it for Windows. This just sucks.
Hello,
So the same thing happened after switching all power modes to Performance. But this time I did not need to plug in my external monitor for it to reactivate the built-in display. I plugged and unplugged the power cable a few times, and then just left the laptop open for a few minutes after trying to turn it on and then the login screen eventually appeared.
This is the output after entering that terminal command:
00:02.0 VGA compatible controller [0300]: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01)
I didn’t see “Fast Boot” as a BIOS option, but I will look for that. I did make sure Secure Boot was off though.
If the Fast Boot option is not present, I will try the kernel-server command. Is this just for testing to isolate the differences between the main Rock version and this alternate server version to see if there is a file that works better in the server version that can be replaced in the main Rock version? Or would I need to manually select the Advanced Options every time I restart my computer? This brings up a point that may help the diagnosis. The issue happens before grub2 even loads. It also happens before the lenovo boot splash screen. When it happens, the lack of backlight makes nothing visible. It isn’t a case where the manufacturer boot splash screen is normal then the backlight turns off in the middle of one of the boot or loading processes. Just wanted to clarify that in case it helps narrow anything down.
Update: I did not find a Fast Boot option in the BIOS. There was a Quick Boot or Diagnostic Boot option, but that seemed to just be regarding information displayed during the boot process. And Diagnostic Boot mode has been selected since day 2 or 3 of using this and that didn’t seem to change anything.
I have run the command to install the server kernel and selected that for this round of logging in. I will try shutting down for a while and seeing if that changes anything to eliminate the issue. Does that command make the server version the new default? If not and the issue keeps happening, then I won’t be able to manually go in and select that mode because it happens before the grub2 menu even comes up.
It might be best for now to just focus on getting graphic performance the best we can just on the laptop.
If you are referring to sudo dnf in kernel-server I just tested this in a Rock/6.0 system and it does become the default. Further you can check after booting in SystemSettings>System>About this System:
Use the up/down arrows on keyboard to highlight the one you want to boot. Note that each kernel version has 4 choices: default (graphical), console mode, fast but insecure mode, and recovery mode. It might be useful sometime to try them all so you can see how the work on your computer.
Console mode should boot to a terminal where you have a command prompt where you can login as user or root (administrator or super user) to repair a broken system.
If the kernel-server does not work I have 2 more things to try. They are both safe “won’t break users system” things.
Confirming that I did install the server version using the terminal command and that it did make that selection the new default that loads without having to be manually selected every time verified by checking the About system section. The issue did seem to happen after that though. I’m up for trying additional options.
Again, I really appreciate the efforts at trying to help me resolve this and try to get to a stable, good linux experience.
Let me write this next thing to try while it is on my mind. To try the experimental XE driver. We saw here that your hardware is the same as that used in the Arch Linux example.
To do that we add i915.force_probe=!9a49 xe.force_probe=9a49 as a kernel parameter to whatever kernel version we wish to test boot. How do you do that? At the grub2 menu we highlight the entry we wish to test boot,
Note that this edit applies only to the current boot so no permenent change to users system, if this actually helps we can make this permenent. To check that the XE driver is actually being used after booting type in terminal (Konsole) inxi -G. This is easier to do than it is to explain it, but do note that what you type must be exact.
Thanks, I appreciate your willingness to try these suggestions. This has to be a bit of a pain in the rear end…
This last thing I have to try is easy to do but is as much a guess as rolling the dice. We install the very latest kernel version. I have tested this in Rock/6.0 and the kernels work there as expected. You manually download the following .rpm’s, each is a different version of the latest Linux kernel from kernel.org as packaged by OpenMandriva. This assumes you are using x86_64 and not znver1:
That is 4 different versions or flavors of the latest kernel to try. To install and remove them using the last one in the list as an example:
Install: sudo dnf in kernel-server-gcc-6.15.0-1-omv2590.x86_64.rpm
Remove: sudo dnf rm kernel-server-gcc-6.15.0-1
At this point this a basically rolling the dice hoping for double 6’s and not snake eyes. But this is easy enough to do. Edit: But to be honest IMO the trial of the experimental XE driver was my last real hope for this. I am also asking OM developers to see if any of them have any suggestions.
Edit: If we were to find a solution to this it would help other people with this Intel hardware and that is not trivial. I can not test this as I only have one laptop which is AMD cpu and graphics.
First when you say shutdown to me that means power off. It is possible that with this hardware users should not use hibernate, sleep, or suspend at all. I wonder if this might apply to screen locking as well. This is unfortunate but users need to understand that we have manufactuers making hardware for the Windows and Apple where Linux, even if they claim to support it, is an afterthought. So users with this hardware using OMLx Plasma desktop may need to adjust settings in SystemSettings>System>Power Management to this:
When inactive: Do nothing
When laptop lid is closed: Do nothing
Dim automatically: Never
Maybe:
Turn off screen: Never
Another 2 maybe:
Under SystemSettings>Security and Privacy>Screen locking
Lock screen automatically: Never
And deselect "Lock after waking from sleep
I hate even making these suggestions but is seems possible that this is necessary for this Iris Xe Graphics hardware. I would prefer to be proved wrong about this…
