I think the update broke dayz and my screwed with my monitor

Support
1 
[uriah@openmandriva-x8664 ~]$ sudo dnf clean all ; dnf clean all ; dnf repolist
0 files removed
0 files removed
repo id                                        repo name
brave-browser                                  Brave Browser
rolling-x86_64                                 OpenMandriva Rolling - x86_64
rolling-x86_64-non-free                        OpenMandriva Rolling - Non-free - x86_64
[uriah@openmandriva-x8664 ~]$ sudo dnf --refresh --allowerasing distro-sync 2>&1| tee dsync-log.txt
Brave Browser                                   142 kB/s |  47 kB     00:00    
OpenMandriva Rolling - x86_64                   2.4 MB/s | 5.4 MB     00:02    
OpenMandriva Rolling - Non-free - x86_64         47 kB/s |  30 kB     00:00    
Dependencies resolved.
Nothing to do.
Complete!
[uriah@openmandriva-x8664 ~]$ ^C

So it looks like my system is up to date and when I check out the drivers for the video card through OMWelcome it looks good also.

Brave Browser                                                                  13 kB/s | 2.0 kB     00:00    
OpenMandriva Rolling - x86_64                                                 5.4 kB/s | 2.4 kB     00:00    
OpenMandriva Rolling - Non-free - x86_64                                      7.9 kB/s | 2.4 kB     00:00    
Package nvidia-570.86.16-5.x86_64 is already installed.
Dependencies resolved.
Nothing to do.
Complete!
Press enter to close konsole

But, I no longer get 120 hz on my monitor, its stuck back down at 100hz now and DayZ is broken. It will load up just fine but it it locks up after just a minute or two. I know its probably not the fault of OM, DayZ is a jank ass game and you dont have any control over what nvidia does, but this was working Great, even better than on windows, two weeks ago.

Ive searched and searched and tried a lot of thing and even reinstalled the game but I am at a loss as to how to get this working again.

Any ideas?

Edited to add: I found the Crashed process viewer and the crashes look like this

           PID: 3873 (fossilize_repla)
           UID: 1001 (uriah)
           GID: 1007 (uriah)
        Signal: 6 (ABRT)
     Timestamp: Tue 2025-02-25 00:04:59 CST (2h 26min ago)
  Command Line: /home/uriah/.local/share/Steam/ubuntu12_32/../ubuntu12_64/fossilize_replay /home/uriah/.local/share/Steam/steamapps/shadercache/221100/fozpipelinesv6/steamapprun_pipeline_cache.904f69d2b1b44b65/steamapp_pipeline_cache.foz /home/uriah/.local/share/Steam/steamapps/shadercache/221100/fozpipelinesv6/steamapprun_pipeline_cache.904f69d2b1b44b65/steam_pipeline_cache.foz --master-process --quiet-slave --shmem-fd 158 --control-fd 163 --spirv-val --num-threads 11 --on-disk-validation-whitelist /home/uriah/.local/share/Steam/steamapps/shadercache/221100/fozpipelinesv6/steamapprun_pipeline_cache.904f69d2b1b44b65/steam_pipeline_cache_whitelist --replayer-cache /home/uriah/.local/share/Steam/steamapps/shadercache/221100/fozpipelinesv6/steamapprun_pipeline_cache.904f69d2b1b44b65/replay_cache --device-index 0 --timeout-seconds 10 --implicit-whitelist 0
    Executable: /home/uriah/.local/share/Steam/ubuntu12_64/fossilize_replay
 Control Group: /user.slice/user-1001.slice/user@1001.service/app.slice/app-steam@4272d5cab041458a9dcf1b110af9891b.service
          Unit: user@1001.service
     User Unit: app-steam@4272d5cab041458a9dcf1b110af9891b.service
         Slice: user-1001.slice
     Owner UID: 1001 (uriah)
       Boot ID: 1de4ebaac8144ee787520c944be1a824
    Machine ID: 42b2022e69254729bd9734dd397ba909
      Hostname: openmandriva-x8664
       Storage: /var/lib/systemd/coredump/core.fossilize_repla.1001.1de4ebaac8144ee787520c944be1a824.3873.1740463499000000.zst (present)
  Size on Disk: 19.5M
       Message: Process 3873 (fossilize_repla) of user 1001 dumped core.
                
                Stack trace of thread 3873:
                #0  0x00007f6866e79f50 abort (libc.so.6 + 0x28f50)
                #1  0x000055df603b0f0b n/a (n/a + 0x0)
                ELF object binary architecture: AMD x86-64

I dont know it it helps but I thought I should include it.

2

It looks like the flatpack for Dark Forces Jedi Knight broke too but reinstalling it worked it out. I even still have my save states.

3

This time it dumped a different log

         PID: 2553 (steamwebhelper)
           UID: 1001 (uriah)
           GID: 1007 (uriah)
        Signal: 5 (TRAP)
     Timestamp: Tue 2025-02-25 03:54:36 CST (1min 3s ago)
  Command Line: ./steamwebhelper -nocrashdialog -lang=en_US -cachedir=/home/uriah/.local/share/Steam/config/htmlcache -steampid=2323 -buildid=1738026274 -steamid=0 -logdir=/home/uriah/.local/share/Steam/logs -uimode=7 -startcount=0 -steamuniverse=Public -realm=Global -clientui=/home/uriah/.local/share/Steam/clientui -steampath=/home/uriah/.local/share/Steam/ubuntu12_32/steam -launcher=0 -use_xcomposite_workaround -no-restart-on-ui-mode-change --valve-enable-site-isolation --enable-smooth-scrolling --disable-gpu-compositing --disable-gpu --password-store=basic --log-file=/home/uriah/.local/share/Steam/logs/cef_log.txt --disable-quick-menu --disable-features=SpareRendererForSitePerProcess,DcheckIsFatal,ValveFFmpegAllowLowDelayHEVC
    Executable: /home/uriah/.local/share/Steam/ubuntu12_64/steamwebhelper
 Control Group: /user.slice/user-1001.slice/user@1001.service/app.slice/app-steam@09ca76e87e3b4df785f16901a9bd88e3.service
          Unit: user@1001.service
     User Unit: app-steam@09ca76e87e3b4df785f16901a9bd88e3.service
         Slice: user-1001.slice
     Owner UID: 1001 (uriah)
       Boot ID: 5f5d048a74a34ccc8936a10330c6c503
    Machine ID: 42b2022e69254729bd9734dd397ba909
      Hostname: openmandriva-x8664
       Storage: /var/lib/systemd/coredump/core.steamwebhelper.1001.5f5d048a74a34ccc8936a10330c6c503.2553.1740477276000000.zst (present)
  Size on Disk: 10.8M
       Message: Process 2553 (steamwebhelper) of user 1001 dumped core.
                
                Stack trace of thread 2553:
                #0  0x00007fa5d0acabcf n/a (n/a + 0x0)
                #1  0x00007fa5d0aca69b n/a (n/a + 0x0)
                #2  0x00007fa5d0acac49 n/a (n/a + 0x0)
                #3  0x00007fa5cf39e1f7 n/a (n/a + 0x0)
                #4  0x00007fa5cf39b646 n/a (n/a + 0x0)
                #5  0x00007fa5cf39a29b n/a (n/a + 0x0)
                #6  0x00007fa5cf3a5d68 n/a (n/a + 0x0)
                #7  0x00007fa5cf3a7167 n/a (n/a + 0x0)
                #8  0x00007fa5cf1c1b51 n/a (n/a + 0x0)
                #9  0x00007fa5cf225f7b n/a (n/a + 0x0)
                #10 0x00007fa5cf226191 n/a (n/a + 0x0)
                #11 0x00007fa5d0b1ac7f n/a (n/a + 0x0)
                #12 0x00007fa5d0b3bb96 n/a (n/a + 0x0)
                #13 0x00007fa5d0ba19de n/a (n/a + 0x0)
                #14 0x00007fa5c9f20e6b n/a (n/a + 0x0)
                ELF object binary architecture: AMD x86-64
4

Ya its borked and Im at my wits end. I even reinstalled steam and the game. I am about ready to reinstall the whole os from my usb installer and see if it work or fire up a windows hard drive.

5

I just reinstalled the other day, as you probably know. Sometimes, it is just less painful and a lot quicker than spending a week trying to troubleshoot. As long as you keep good backups, this is always an option. That is why I cannot stress enough the importance of good backups.

I also like to grab a copy of things like /etc/fstab and /etc/group /etc/hosts

6

If you do reinstall, grab the newest ISO that was posted today. I believe that is the one you use.

7

I was actually trying to get the old kernal and drivers back since I knew they worked but it seems to be forcing me to the latest update. I dont think the newest iso is gonna be what I need to get it running since eveything was up to date.

1 Like
8

So is rock still on the old nvidia drivers?

9

I don’t know what Rock is using, but if you want to grab that Rock 5 ISO, get it.

10

What kernel, and possibly what driver

11

The ones we had before rome just got updated. My system was up to date before I updated. The nvidia drive must have been .565 or .560

Is there a way to tell what I had?

12

Im going dark for a bit while i throw rock on this.

13

Do you have a log of the updates?

rpm -qa|grep kernel-desktop
should tell you the current and the older kernel/s
Then knowing the kernel version we may try to look for the relevant nvidia driver.

14

I do not have a log of the updates. Im sorry I jumped the gun. Dayz had an update and it was a mad rush to get stuff I just threw everything I had at it to get it working. I should have waited until someone was available to actually help. I had already reinstalled twice before your message so any logs are all gone.

Rock didnt work out for me. All I can say is you all have done an amazing job getting this stuff to work for noobs since them. Opening rock for the first time was like encountering aliens to me and I didnt want to start over learning a new system from scratch, especially having to do most of the work from command line. I didnt realize that the difference between rock and rome was like night and day. It shouldnt ever be recommended to a linnoob.

Im done for the night, I am worn out trying to make this work. Tomorrow Ill try and figure out how to do a dual boot and get DayZ running. But for now its whisky time.

1 Like
15

If anything I can install rome like a pro now, Ive had lots of practice lmao.

2 Likes
16

There is nothing wrong with whisky time. :grinning:

1 Like
17

My kid told me that maybe it was time to quit for the night. I told him that I didnt even have a working OS, it was time to go home to Rome. so here I am.

Im gonna hit you up on this backupping stuff. It would have come in handy right about now. Ive been good about keeping files backed up, I have stuff from 2010. Backing up an os is just a bit beyond me right now.

18

Expected, as it’s too old. Also it’s Plasma5, I would not suggest anyone to install it right now.

Something different if you are willing to try would be:
ROME upgrade started on 19 February,
this iso ROME plasma6.x11 x86_64 ID #3644 is:
Notified at February 07, 2025 11:57

I’d suggest to install this one, so to be able to start from something supposed working for you.
Once done, I suggest to do:
sudo sh -c "echo excludepkgs=kernel-desktop >> /etc/dnf/dnf.conf"
which should exclude the kernel-desktop from next updates, for now.
Then the tricky part is to find which nvidia driver version worked with that kernel, and if it’s still available somewhere.

19

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.