Closed leotada closed 4 years ago
Did you rmmod hid-logitech
the old driver and loaded the new one (modprobe hid-logitech
)? Check with lsmod
, which shows the new drivers as hid_logitech_new
, whereas the old one doesn't have the new
suffix.
I don't know much about kernel modules, I used only the command on the readme: sudo dkms install /usr/src/new-lg4ff I hadn't installed any version yet. This command will build and load the module, right?
Yes, dkms install
builds and installs the module but doesn't load or unload the module.
Alternatively, cou can also just restart afterwards to have the new module loaded.
I restarted the computer thinking this, but didn't load the new driver module automatically, it didn't work, for some reason.
I restarted the computer thinking this, but didn't load the new driver module automatically, it didn't work, for some reason.
This will only work when installing the module using DKMS. It should install the driver and update the iniramfs image with the new module. Pasting the output of the dkms install command could help determine what's happening.
$ sudo dkms install /usr/src/new-lg4ff
Creating symlink /var/lib/dkms/new-lg4ff/0.3/source ->
/usr/src/new-lg4ff-0.3
DKMS: add completed.
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area...
make -j16 KERNELRELEASE=5.4.17-200.fc31.x86_64 KVERSION=5.4.17-200.fc31.x86_64...
cleaning build area...
DKMS: build completed.
hid-logitech.ko.xz:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/5.4.17-200.fc31.x86_64/extra/
Adding any weak-modules
depmod....
Backing up initramfs-5.4.17-200.fc31.x86_64.img to /boot/initramfs-5.4.17-200.fc31.x86_64.img.old-dkms
Making new initramfs-5.4.17-200.fc31.x86_64.img
(If next boot fails, revert to initramfs-5.4.17-200.fc31.x86_64.img.old-dkms image)
dracut.........
DKMS: install completed.
That looks good. Could you attach the output of the dmesg command after rebooting?
That looks good. Could you attach the output of the dmesg command after rebooting?
$ sudo dmesg | grep logitech [sudo] senha para leonardo: [ 159.603595] logitech 0003:046D:C294.0006: fixing up Logitech Driving Force report descriptor [ 159.604004] logitech 0003:046D:C294.0006: input,hidraw5: USB HID v1.00 Joystick [G27 Racing Wheel] on usb-0000:01:00.0-4/input0 [ 160.415189] logitech 0003:046D:C29B.0007: input,hidraw5: USB HID v1.11 Joystick [G27 Racing Wheel] on usb-0000:01:00.0-4/input0 [ 160.415293] logitech 0003:046D:C29B.0007: Force feedback support for Logitech Gaming Wheels
Could it be the complete output of the dmesg command after a reboot? We're trying to find something that has gone wrong and I need more information about your system. Are you sure you're running the same kernel that has the newly installed kernel?
The DKMS installation process seems to go well but the module is not found at reboot. We aren't doing anything weird on purpose. This module should load like any other DKMS module. Could you ask in some Fedora support forum? They may have some ideas as to why it doesn't work.
I'm having the same issue on Fedora 31. I haven't spent much time figuring out why because I was so eager to try this so I followed the steps under manual method and that works.
On 12/2/20 10:52 am, Bernat wrote:
The DKMS installation process seems to go well but the module is not found at reboot. We aren't doing anything weird on purpose. This module should load like any other DKMS module. Could you ask in some Fedora support forum? They may have some ideas as to why it doesn't work.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/berarma/new-lg4ff/issues/25?email_source=notifications&email_token=AIKKGFD65OLJJNIDUPNXL5TRCM25TA5CNFSM4KR63UVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELOTYNI#issuecomment-584924213, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIKKGFG33IFFZBGJT2QGT53RCM25TANCNFSM4KR63UVA.
I'm having the same issue on Fedora 31. I haven't spent much time figuring out why because I was so eager to try this so I followed the steps under manual method and that works.
Thanks for reporting. I've never used Fedora and I'm no expert on DKMS. Any external help is welcomed. Some Fedora users may know better than me.
I've done a search for "fedora 31 dkms" and I got this result: https://github.com/zfsonlinux/zfs/issues/9868
That leads me to: https://bugzilla.redhat.com/show_bug.cgi?id=1753044
I'm not sure that it's the same exact issue but seems very related. Installing the grubby package might be worth a try.
@berarma I'm running Fedora 31, thanks a lot for the link to that issue. That issue is now resolved with a new dkms release which has been pushed to Fedora 31. With that update the dkms procedure for installing lg4ff-new is indeed working now.
PS: Thanks a lot for your work here!
@jp7677 Thanks for the confirmation!
I tried to install using DKMS on Fedora 31 (5.4.17-200.fc31.x86_64) and DKMS status show this:
but on dmesg command do not show any change, and only work like the old kernel driver. Using the manual installations works and show the 0.3 version on dmesg.