Basically I was able to play Cyberpunk on my Nobara setup (N37, KDE, Nvidia 10180ti, Intel i5 CPU) but everything went sideways when I upgraded from kernel version 6.2.14-300 to 6.3.5-201 (and still have issues despite several upgrades since then and now on 6.3.12 I think).
If I switched back to 6.2.14-300 I was able to play but since there has been a few upgrades since, I no longer have 6.2.15-300 as an option at start up.
The game launches but it stays on a black screen, no audio, no visuals just the cursor. I’ve reinstalled the game and nothing. Switched from X11 to wayland and nothing.
I can’t remember which nvidia driver version I have right now but it’s the latest in the Nobara repos.
Game was installed through Lutris and worked great prior to the upgrade.
You must log in or register to comment.
Any reason why You don’t update to N38? Which proton build are You using?
I installed the game through Lutris and the current runner is Wine (WineHQ Staging 8.11). I do have the ability to install just about any Proton version with the ProtonUP-QT application just don’t know which one since the installers through Lutris only offer Wine runners. As far as the upgrade goes, well no particular reason honestly, I thought they were still waiting on some packages upstream.
I upgraded to n38 without issues, there is an install guide on discord. You can try to download latest wine-ge-proton from protonup and use it instead of wine-staging. I remember having issues with worms siege not working with wine-staging.
See my comment below regarding the n38 upgrade. If I get the system back up then I’ll try this.
Why do you need Discord to upgrade Nobara?
You don’t. There are specific instructions on how to do this in one of the channels but it’s also on their website.
Thanks. Really riles me up that people constantly direct you to a bloated proprietary chat software that requires registration for some basic information, especially when the same info is freely available on a website.
I had some issues with cyberpunk using proton 8 or higher recently, I think 7.0.4 is working fine, and any GE proton 7 works too.
See my comment about the n38 upgrade.
Well tried upgrading to n38 last night, now it’s not booting up all the way. I followed the guide on Nobara’s website.
Currently stuck at “Failed to start systemctl-user db.service”
I can do an ALT + F3 and it takes me to the terminal where I can log in just fine but that’s about all I can do. No GUI, No KDE. Did I search on Google and Nobara’s discord but nothing useful. Would really rather not have to reinstall clean. Any ideas?
Have you tried reinstalling kde. Sounds like it might have been wiped?
Just tried. No dice. Ran a few commands.
dnf group list --available *desktop - this did not list KDE as an option at all.
dnf groupinstall “KDE Plasma Workspaces” - this said that nothing was found as if the package was not available
dnf install @kde-desktop-environment - seems to have installed KDE but after reboot, no DE, just back to the terminal.
I also ran disabling gdm and enabling ssdm commands but I can’t remember exactly what I ran.
No dice.
If I run dnf list installed | grep kde it shows nothing.
Darn. I had a similar experience with gnome getting deleted during an update and just had to reinstall the DE.
It’s starting to sound like I need to reinstall the OS.
Shouldn’t have dnf groupinstall “KDE Plasma Workspace” installed everything I needed if the DE was corrupted or deleted during upgrade? Do I need to run any other commands?
deleted by creator
Ran a dnf list installed | grep nvidia and got nothing in return so in the process of doing a clean install of n38 unfortunately
Can you even do Wayland on Nvidia? My only Nvidia card is used in a server for testing self hosted stuff that uses cuda but it’s still a removed to deal with.
I mean not very well, its very glitchy and lots of artifacts but I mentioned it just in case.
Starting with Kernel 6.3 when my pc starts it freezes forever complaining about waiting for CPU 7. Disabling SMT fixed it but then you have no SMT :( I suspect 6.3 introduced a scheduler bug.
