I ended up on KDE-NEON(Ubuntu based) with the nvidia repo drivers…works great. Maybe its just my hardware combo.
1 Like
That’s possible. We try to debloat as much as we can, and we truthfully don’t have the resources (time, hardware, money, interest, etc…) to support closed source software. We can only make our best effort to build it and hope for the best.
I would be more than happy to test/validate since IIRC I read where most of the devs/packagers don’ have nvidia hardware to test against. I just could not get the darn thing up and going enough even for that. The last time I tried this hard to use a distro was 25 years ago when I inherited a whole bunch of burnt cd’s from my late friend and there happened to be some Slackware discs in there.
Still a valid distro, but you will work for it. Probably harder than here lol.
The first thing I would do is make sure your BIOS is up to date. We use newer kernels than most distros do. Remove as many extra devices as you can related to the issue you are having. Start with X11 (which I think you eventually got to), one monitor (no touch screens or writing tablets) especially on a notebook. Look at the “how to get help” post on the forum. It may seem abrupt and abrasive, but we want this distro to give people freedom to make the system their own, not to just use an out of the box experience that caters to anyone but the user. Go into the OpenMandriva and Cooker rooms on Matrix[dot]org to share any things you are trying in real time. There will be people that may have already tried some things in there to get it to work, or just to rule out other things you may find will fix the issue specific to your system.
I hope you will give us another chance, but I understand how frustrating it can be when you want something that just works.
1 Like
yeah, bios update might be in order…I’m old school and don’t update that unless I have to. No hard feelings its just how it goes sometimes. If it makes you feel any better I was having most of the same issues in Devuan Excalibur as well.
1 Like
I remember the old days with failed updates for AMI and Phoenix. It makes you never want to risk it again. Now they have consistency checks and usually more than one slot on the BIOS so the board will revert to the old image and still boot. Now, the need to update is greater because of microcode changes and other feature additions. If a buggy feature is phased out, it can be in an update in the BIOS based on how it communicated with the CPU before the microcode update. You are certainly welcome to keep your own things as you would like them. Just know that you are going to hit a wall someday.
The bios version I was on was from 2022…anyway updated it to the 2nd most recent (I usually stay one back just in case I need somewhere to go forward). Anyway, live wayland USB loads up fine, do the install, aaaaaand barf to black screen. I guess OM just hates my hardware 
1 Like
As a possible workaround you may boot to console mode and see if the desktop starts by skipping the sddm screen:
at the console prompt, login with your user/password than do
startx /usr/bin/startplasm + TAB (because I don’t remember the plasma wayland executable)
If that should work you may try to install lightdm to replace sddm.
1 Like
Hi, I am contacting you after Ben79 suggested to do so.
I downloaded and installed the latest ISO Wayland and I noticed that it has serious problems in systems equipped with Nvidia video card.
Issues affect the whole system in different ways, in particular web browsers (Chromium won’t work and Firefox messes up the screen with WebGL-based 3D applications).
If one tries and install nvidia official drivers the system won’t boot and one can recover it only from live ISO.
Please let me know if I can help you testing Rome system with nvidia drivers in some ways.
You will need to read this thread over carefully, as well as the links provided to other topics where this was already discussed:
With the latest nvidia proprietary driver, support for cards older than the GTX 1650 will no longer be supported from nvidia. Thus, we cannot continue supporting them.
They will not backport fixes into drivers prior to the 59x beta driver we are using on their way to releasing 6xx driver version. They will not support older kernels.
If you are using nouveau and not getting 3D support on your applications, then you would need to review their card support matrix for 3D acceleration support:
Going forward, we will only be able to offer the open driver from Nvidia and the nouveau driver from FDO. If your card is not supported on either, there isn’t much we can do.
Thank you for your explanation.
My system has a GeForce GTX 1060 on, so as far as I have understood, it won’t be supported anymore even if drivers are available on Nvidia official site.
Can you please tell me which options I have to fix graphics of my system without changing my video card? Now my system is working really bad, while times ago it was quite acceptable even without Nvidia drivers.
Should I install any particular package? I did not see any nouveau driver installed.
To clarify, if your card is older than the GTX 1650, it will no longer be supported by nvidia as of version 6xx. We are using version 59x (which is a beta) because our kernels tend to be newer, and nvidia does not always make the same versions of drivers available to all arches. For example, the current 58x the last time I checked was not available for aarch64. We split the difference by offering the newer driver with hopefully better support with newer kernels. Newer or older, we are still at their mercy because the driver is proprietary.
At this time, 58x is not legacy. We just won’t be packaging it. I realize that is frustrating, but I own two 560’s and one 960 that are completely useless in Linux, even though they work perfectly fine. If people want to use the 58x proprietary version, you should go over nvidia’s documentation about using their .run file to install it. You will probably need dkmsso the kmod can be rebuilt when you update the kernel. Even that will be on borrowed time, and we won’t be able to support it. You would have to report it on the nvidia forum (which should be happening with the proprietary driver, anyway).
First, don’t use Wayland. They and the entire FDO don’t care about older graphics cards for Wayland. My 960 ran like absolute trash with and without the proprietary nvidia driver. Your 1060 isn’t that much more powerful than the 960. Turn off compositing in Plasma or GNOME, or try a different desktop environment or window manager.
nouveau is the default driver loaded when the nvidia package is not installed and you have an nvidia card. You should only need to remove the nvidiapackage.
At the moment my problem is that only the Wayland ISO is working somehow without Nvidia drivers. The other one won’t even start. So there is something wrong in Nouveau driver because in the past my system could work even without nvidia.
Please don’t tell me I should change a Linux distribution that worked great until the last November massive updates
@ben79 has identified several issues with current ROME iso’s. If you can’t use X11 on ROME it might be due to a missing DDX. This thread is not about helping you with that, though. Please search through some of his recent findings to see if you are seeing any similarities, and open a specific Support topic to the issues you are having including filling out the template.
1 Like
Ok, thank you for your suggestions.
I do not know if I will be able to have a working system in short time, but at least now I know what is the basic issue which makes my system go wrong after installing Nvidia drivers.