Issues with installing hid-fanatecff
Hello, i'm trying to setup the Force Feedback for my Fanatec GT DD Pro Wheel, but i get this message as i want to make it. How can i get this to work? I use this github repo: https://github.com/gotzl/hid-fanatecff
GitHub
GitHub - gotzl/hid-fanatecff: Driver to support FANATEC input devic...
Driver to support FANATEC input devices, in particular ForceFeedback of various wheel-bases - gotzl/hid-fanatecff
23 Replies
Have you tried layering it? https://copr.fedorainfracloud.org/coprs/sigonze/hid-fanatecff-kmod/
i'm new to fedora, how do i layer it?
Just follow those instructions
Just this I think
sudo dnf copr enable sigonze/hid-fanatecff-kmod
sudo dnf install hid-fanatecff
Although it says it not adapted to ostree
Try with dnf see what happens
Afaik dnf is an alias to ostree so you can try an follow the ostree method
It it says is borked, worth a try anyway
thanks
Ahh sucks, maybe some fedora atomic gurus can chime in
I'm interested too, would like to get a fanatec device
on my arch install it worked out for me
oh well time to learn fedora more i suppose
copr enable sigonze/hid-fanatecff-kmod
rpm-ostree install hid-fanatecff
should have worked, issue with the copr maybe? I don't have a non-Atomic Fedora to test
forgot about distrobox lol, worked on fedora 40 distrobox
so rpm-ostree is not working for that, I'm don't much about it too probably someone else can understand it
Does the driver work on distrobox?
I'm not sure if it works if you install the drivers and oversteer in the same distrobox, then export oversteer
I don't have the hardware to test, oversteer with G29 works great for me
Ovesteeer is included in bazzite I think?
It may be interesting to request fanatec hid to be included if it isn't? Maybe worth pinging kyle
can't use dkms in distrobox
open an issue in https://github.com/ublue-os/akmods
GitHub
GitHub - ublue-os/akmods: A caching layer for pre-built Fedora akmo...
A caching layer for pre-built Fedora akmod RPMs. Contribute to ublue-os/akmods development by creating an account on GitHub.
and we can look into add this driver
with which words should i open the issue? Oh, i remember now that i don't have a github account
Hello! I am also having the same issue and ended up here. I notice there is a bazzite-specific issue here: https://github.com/ublue-os/bazzite/issues/901
Though should there be another issue created on Akmods if we hope to get this implemented? None exist yet.
GitHub
Add kernel driver modules for steering wheels (hid-tmff2 in particu...
Describe the package First of all, thank you for including a simple one-click method to install oversteer! Unfortunately though that's not sufficient to use my steering wheel (a Thrustmaster T3...
So I was able to get the driver to work with a couple of tweaks
I pulled hid-fanatecff to my /home folder and created a "wheel-driver.sh" as suggest by napaalm on the issue thread I posted; but with a few less commands
Then, in the makefile you have to make some tweaks
I assume you have installed "kernel-headers-matched", and have done a full reboot since then.
As of current, due to package availability on COPR, you do have to be on the testing branch right now
Make the following changes to the makefile
I'm unsure if there is any real change here.... but this is what I've set it to be. I think /usr/src/kernels is different.
Now for the commands. I have ld.bfd installed, which is installed with binutils-devel. I'm certain you can also use ld.gold. Regardless, within the hid-fanatecff folder, run
and then
the makefile only needs to be ran once every time your kernel version changes; but the ./wheel-driver.sh needs to be ran every single boot.
For me I was able to find my device under /dev/input/event9
No matter what though, oversteer would refuse to cooperate with this. It might be an issue with my wheel. Despite this, forcefeedback worked properly in all the applications I tried so far.
You should be seeeing your device being detected and setup properly in
If you get an error, try a USB 2.0 port.
Hopefully that helps. Though could we get some confirmation on if this driver will be considered in an official capacity at any point in the future? Do we need to move that issue back over to akmods?
Updated issue with a better organized version of what was said here.