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