Joystick Conflicts

Foxsec

So I added that line to GRUB and ran the updater, and it didn't pick up the extra joystick, Did a total restart and now it doesn't pick any of the joysticks up, and neither the keyboard or mouse, so I can't do anything. :s

Halvhjearne

@Foxsec

sounds like you messed something up.
tbh i have no idea what you did, but you can most likely fix it by booting from a usb stick and reverse whatever you did wrong.

did you edit the vendor and product id?
yours should be:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbhid.quirks=0x0810:0xe001:0x040"

also, you are not adding a line to grub, you are editing a line that is already there and adding the usbhid quirks.
the rest should already be there by default.

Foxsec

@Halvhjearne

Hi again, I ended up having to do an entire fresh ubuntu install in the end

My line read as :

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbhid.quirks=0x0810:0xe001:0x040"

as the joystick is listed as Bus 001 Device 003: ID 0810:e001 ?

I then ran update-grub from /usr/bin and it just didn't work from there? was my quirks addition not right?

Edit: It looks like I had an extra 0? i will try it again with what you have suggested here.

Halvhjearne

@Foxsec

no, i made a mistake and the 0x is needed indeed.

not sure why it isnt working for you?

cat /sys/module/usbhid/parameters/quirks

if it is accepted, you should see it here or it will just return null
for me it returns this:

0x16c0:0x05e1:0x040,(null),(null),(null)

btw, it would be nice to know if the modprobe way didnt work for you.

Foxsec

Just redid it again, and it's come back as (null),(null),(null),(null)

Halvhjearne

@Foxsec

maybe you forgot to run update-grub?

either way, i suggest we take a few steps back ...

what is the actual make and model of this encoder (and is it a joystick or keyboard)?
and what happends when you run jstest?

Foxsec

@Halvhjearne

Deffo ran update-grub from /usr/sbin/, tried it again and the quirks are still null.

It's a joystick and buttons connected to a little encoder, not sure of the make or model because it isn't branded. I may just end up buying another one ;(

Halvhjearne

@Foxsec

not sure how it wouldnt work, except if you forgot to run update-grub or restart.

lsusb or usb-devices commands can usually give you a clue to the make and model name.

you didnt answer what happends when you run jstest?
on ubuntu you can get a version with gui called jstest-gtk

Foxsec

@Halvhjearne

Just lists it as twin usb joystick. I can copy and paste all of the info from it if that helps?

Did a jstest-gtk and it shows that the joysticks work but it picks up both players as player 1.

Halvhjearne

@Foxsec

not sure what you are doing wrong, the quirks should be added, even if the joystick is not connected.
it does sounds like its a clone of the xin-mo, so im guessing it should work.

mitu

You can check that the quirks have been added to the boot command line by running

cat /proc/cmdline

Can you copy the output of the command and post it here ? Alternatively, as @Halvhjearne mentioned, try using modprobe to apply the options from a command line:

rmmod usbhid && modprobe usbhid quirks=0x0810:0xe001:0x040

Foxsec

rmmod: ERROR: ../libkmod/libkmod-module.c:793 kmod_module_remove_module() could not remove 'usbhid': Operation not permitted
rmmod: ERROR: could not remove module usbhid: Operation not permitted

Is what I get when I run the rrmod command?

And I get the below when I type the cmdline in

BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic root=UUID=9c1664a3-6dc6-4ad4-afc8-334c7e46342b ro quiet splash vt.handoff=1

Think it's worth just getting another encoder so I'll have one for each joystick? seems like it just doesn't want to work, thanks a lot for you help btw guys, really appreciate it.

mitu

@Foxsec said in Joystick Conflicts:

rmmod: ERROR: ../libkmod/libkmod-module.c:793 kmod_module_remove_module() could not remove 'usbhid': Operation not permitted
rmmod: ERROR: could not remove module usbhid: Operation not permitted

Is what I get when I run the rrmod command?

Yeah, forgot about that. Prefix the commands with sudo:

sudo rmmod usbhid && sudo modprobe usbhid quirks=0x0810:0xe001:0x040

And I get the below when I type the cmdline in

BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic root=UUID=9c1664a3-6dc6-4ad4-afc8-334c7e46342b ro quiet splash vt.handoff=1

That means your Grub modifications have not added the usbquirks necessary for the joystick.

Think it's worth just getting another encoder so I'll have one for each joystick? seems like it just doesn't want to work, thanks a lot for you help btw guys, really appreciate it.

No, you're very close of making this one work, so there's no need to get another one.

Halvhjearne

@Foxsec said in Joystick Conflicts:

BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic root=UUID=9c1664a3-6dc6-4ad4-afc8-334c7e46342b ro quiet splash vt.handoff=1

are you sure you edited the line correctly in /etc/default/grub and ran update-grub?

perhaps show us the content of it

Foxsec

@Halvhjearne

I was writing down every step and making a code box for everything that came up and I tried that rmmod that Mitu suggested and i checked the quirks file after and it worked!

Both set of joysticks and buttons are now configured

Thanks so much for your help guys, really really appreciate it :)

Halvhjearne

@Foxsec said in Joystick Conflicts:

I was writing down every step and making a code box for everything that came up and I tried that rmmod that Mitu suggested and i checked the quirks file after and it worked!

Both set of joysticks and buttons are now configured

Thanks so much for your help guys, really really appreciate it :)

thats wierd, for me it would not work with modprobe and i remember reading somewhere that it was supposedly blocked, but whatever.

atleast it works for you now.