SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I can confirm the Slackware update Sat May 4 17:37:11 UTC 2024 and Multilib Sun, 5 May 2024 08:41:30 GMT resolved mostly issues.
The Chernobylite is crashing soon the launcher tries open the game, and is not showing anymore the windows which I posted in the GitHub, but I think this is related to Proton 9 been released this week, maybe is an incompatibility, I need check with Proton 8, but don't have time right now.
I can confirm the Slackware update Sat May 4 17:37:11 UTC 2024 and Multilib Sun, 5 May 2024 08:41:30 GMT resolved mostly issues.
The Chernobylite is crashing soon the launcher tries open the game, and is not showing anymore the windows which I posted in the GitHub, but I think this is related to Proton 9 been released this week, maybe is an incompatibility, I need check with Proton 8, but don't have time right now.
Tried No Man's Sky with proton 8.0-5, and it still crashed. My problem is that I'm not sure how much is ncurses and how much is not set up correctly.
Did you reinstall the various packages that get stomped on by nvidia? This may be outdated info, but if you were running nvidia then at the very least you need to completely reinstall xorg-server, mesa, and libdrm to make sure everything is properly reset.
Did you reinstall the various packages that get stomped on by nvidia? This may be outdated info, but if you were running nvidia then at the very least you need to completely reinstall xorg-server, mesa, and libdrm to make sure everything is properly reset.
I didn't need to. AFAIK, it doesn't clobber system mesa and the like anymore. My problem was this: https://gitlab.freedesktop.org/drm/amd/-/issues/3343 So hopefully that gets fixed for 6.6.31. ETA: looks like there's already a revert. not sure when it's happening, though?
Humm this link shows the problem I have trying to play Chernobylite with Proton 9, I was able to "bypass" if I change to Proton 6 and am able to enter in the game menu, but when I try to load/start/benchmark the game crash. For No Man Sky, since I use a Xeon 2697 v3, I needed to force the game only to use 14 cores(else it crash when trying to load/star new game), instead of 28, but Proton 9.0, in the changelog, say it is able to correct that, maybe for not all games...
I have installed back NMS only for check it since garpu was having problemas with it, but I will give a new try, didn't play it since 2021. :P
Humm this link shows the problem I have trying to play Chernobylite with Proton 9, I was able to "bypass" if I change to Proton 6 and am able to enter in the game menu, but when I try to load/start/benchmark the game crash. For No Man Sky, since I use a Xeon 2697 v3, I needed to force the game only to use 14 cores(else it crash when trying to load/star new game), instead of 28, but Proton 9.0, in the changelog, say it is able to correct that, maybe for not all games...
I have installed back NMS only for check it since garpu was having problemas with it, but I will give a new try, didn't play it since 2021. :P
Are you on an AMD card? Try the 6.6.29 kernel, if you're on 6.6.30.
I didn't need to. AFAIK, it doesn't clobber system mesa and the like anymore. My problem was this: https://gitlab.freedesktop.org/drm/amd/-/issues/3343 So hopefully that gets fixed for 6.6.31. ETA: looks like there's already a revert. not sure when it's happening, though?
On my system above 4g decoding is an option I can enable in the BIOS. Is this option not available on your hardware?
On my system above 4g decoding is an option I can enable in the BIOS. Is this option not available on your hardware?
Nope. mobo is asus prime b350, and it's b450 and above that supports it (that I can tell). Upgrading everything isn't in the cards, especially since I'd need a new audio device, too (currently an m audio delta 1010lt). While gaming is something I enjoy, it's not the main thing I do on a computer.
Are you on an AMD card? Try the 6.6.29 kernel, if you're on 6.6.30.
Well after I got some time I tried again NMS and the game screen was blinking green, It only didn't the first time I open steam and launch the game.
Then I rollback to 6.6.29, and it correct the problem which I didn't saw before, also now Chernobylite is working with Proton 9.
Yes I have a RX6800XT on my workstation and an RX6600XT on my server. Also I am using a Xeon 2697v3 on a Sabertooth X99, which have Above 4G Decoding and is turn on, but still I was getting the issue with 6.6.30 version.
I hope later version can fix, else I will need to blacklist kernel on slackbuidls from now.
Last edited by gbschenkel; 05-07-2024 at 02:53 PM.
Ah ok, I didn't know where the cutoff was for that feature. Learn something new every day
At least I think it doesn't...the motherboard may well support it, but I don't think my CPU (Ryzen 5 1600) does. Updating my bios further will have to wait to a time when they aren't doing rolling power blackouts for maintenance. But, yeah, Palworld and Guild Wars 2 look really nice now!
Yes I have a RX6800XT on my workstation and an RX6600XT on my server. Also I am using a Xeon 2697v7 on a Sabertooth X99, which have Above 4G Decoding and is turn on, but still I was getting the issue with 6.6.30 version.
I hope later version can fix, else I will need to blacklist kernel on slackbuidls from now.
That sounds like something useful they'd need to know. It's easily reproducible, if you've still got 6.6.29.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.