Recently I dipped my toes in sim racing and I could run dirt 2.0 and AC fairly easily with a controller. A few weeks ago I bought a G920 and so far the only game that works with it proper is Dirt 2.0. AC and rF2 are a nightmare. AC shakes the wheel or doesn’t recognize it, rF2 just keeps steering on it’s own (even when the car is stationary, with autosteer off). I also tried RSF RBR, which runs, but after the first launch it doesn’t detect the wheel anymore.

DKMS is not supported on bazzite, I couldn’t get new-lg4ff to work. Oversteer works, but is sort of useless without the driver. I’m a little bit disheartened at this point. Since I bought the wheel, I spent way more time troubleshooting than racing.

Does anyone have any experience running these games on bazzite with a G920? Is there an easy fix to all of these issues that I’m overlooking?

I’m way too settled into bazzite to distrohop now and I really wouldn’t like to have MS in my household.

My main priority would be to get RSF RBR running and then AC or rF2 to have something other than rally.

Thanks in advance for any input

  • tal@lemmy.todayEnglish
    8·
    1 month ago

    DKMS is not supported on bazzite.

    I mean, not having DKMS sounds like it’d be obnoxious for gaming to me.

    But if all you need is a kernel module, you shouldn’t have to have it built via DKMS.

    I don’t use Bazzite, but the driver project has instructions for a non-DKMS build:

    https://github.com/berarma/new-lg4ff

    Manual method

    Use only if DKMS doesn’t work.

    You’re going to need to manually do a new build and install if you update your kernel, though, since otherwise the new kernel won’t have that driver (well, unless the Bazzite people include it in the new kernel).

    EDIT:

    I was under the impression that new-lg4ff cannot be installed due to the immutable nature of the system.

    I haven’t used an immutable distro, but if it’s a problem, I’m sure that there’s a way to defeat the immutability. If it just mounts the root filesystem read-only, then

    # mount -o remount,rw /

    Will probably do it.

    I’m also pretty sure that you can use a non-standard directory with modprobe and if you want to manually load the module out of some other directory. Looking at the modprobe(8) man page, looks like it takes a -d flag and an alternate module root directory.

    EDIT2: Hmm. insmod might be simpler than modprobe, since then you don’t have to worry about dependent modules, especially if new-lg4ff is just a single module. It’s been ages since I’ve insmodded something, but if it can take a path to a kernel module file, then one doesn’t need to worry about having modprobe see both new-lg4ff and any modules that it depends on.

    • Logh@lemmy.mlOPEnglish
      4·
      1 month ago

      I think you might’ve just saved me there. Will give modprobe a try in the afternoon. Thanks a lot!

      • tal@lemmy.todayEnglish
        3·
        1 month ago

        I just added one other followup – you might want to try insmod instead of modprobe, since modprobe expects more than just the single module, expects to have the other modules that that new-lg4ff might depend on visible to it…you might need to go set up a “duplicate module root” to make modprobe happy, but with insmod just be able to insert the module file without any other mucking around.

    • BlackEco@lemmy.blackeco.comEnglish
      1·
      1 month ago

      I haven’t used an immutable distro, but if it’s a problem, I’m sure that there’s a way to defeat the immutability. If it just mounts the root filesystem read-only, then

      # mount -o remount,rw /

      Will probably do it.

      It will work until the next reboot (and I believe it won’t work on Fedora 42 as it now uses composefs), on Fedora Atomic Desktops you have to use layers to add additional packages using rpm-ostree

      (Edit: formatting)

  • BlackEco@lemmy.blackeco.comEnglish
    2·
    1 month ago

    There’s an issue on Bazzite’s repo asking for new-lg4ff and other kernel modules to be added. While the issue is still open, it describes a workaround[1][2] but it requires building the DKMS module and layering it on top of Bazzite on every kernel update.

    Edit: re-reading your post and Oversteer’s README your wheel should be supported by the default kernel, I’m not sure new-lg4ff will fix your issue (and the latter does not list the G920). The issue must be somewhere else. I wish I could help you, but I have yet to try Assetto Corsa and Dirt Rally with my Driving Force GT on Bazzite.

    1. https://github.com/ublue-os/bazzite/issues/901#issuecomment-2054077901 ↩︎

    2. https://github.com/ublue-os/bazzite/issues/901#issuecomment-2395749374 ↩︎

  • DesolateMood@lemm.eeEnglish
    2·
    1 month ago

    So, I’m far from knowledgeable enough to help you fully, but it seems like something is wrong with the games rather than with your wheel. If DR2.0 and oversteer both work (I’m assuming you mean with proper ffb) then that means that the wheel is being detected by your computer and that the driver, which for the g920 is already built into the kernel according to new-lg4ff, is working.

    Like I said, I unfortunately can’t help you other than suggesting reinstalling the games or using a different proton version, but hopefully this is enough to help you find a proper answer

  • terraborra@lemmy.nzEnglish
    26·
    1 month ago

    A different distro isn’t going to help. It’s an issue of game telemetry and hardware not being supported. Unfortunately Simracing really requires dual-booting windows.

    • Logh@lemmy.mlOPEnglish
      2·
      1 month ago

      I was under the impression that new-lg4ff cannot be installed due to the immutable nature of the system. What I don’t understand is that dirt 2.0 works beautifully and from what I read on forums and protondb simracing is doable on linux, but all the positive stories came from people running traditional distros. I’m leaning on dual booting though, it just feels yucky.