search

z3ntu / RazerGenie

Qt application for configuring your Razer devices under GNU/Linux.
GNU General Public License v3.0
374 stars 35 forks source link

Two devices of the same model #154

Closed dsdante closed 1 year ago

dsdante commented 1 year ago
  1. Run RazerGenie.
  2. Connect mouse 1.
  3. Wait until it's recognized.
  4. Connect mouse 2 of the same model (tested on Abyssus Essential).

Expected result: mouse 2 is recognized and appeared in the device list.

Actual result: mouse 2 is not recognized, and the settings for the mouse 1 don't affect mouse 2.

z3ntu commented 1 year ago

Does the same behavior also exist when you reopen RazerGenie when both mice are already connected?

dsdante commented 1 year ago

Yes, RazerGenie only recognizes the mouse I connect first.

z3ntu commented 1 year ago

Did you check another GUI like polychromatic if that handles it correctly? To be honest I'm not even sure that OpenRazer handles it 100% correct if you have two basically-identical devices since it's normally not really a use case.

dsdante commented 1 year ago

No, I only tried RazerGenie.

Anyway, it's up to you what to do with this information. :) Not that it bothers me much.

z3ntu commented 1 year ago

image

So with our fake driver setup I cannot reproduce this. Here I have two devices of the same model with just a different serial number and everything works as expected.

Can you run this and send the output? python3 -c "from openrazer.client import DeviceManager; a = DeviceManager(); print(a.devices)"

dsdante commented 1 year ago

It returns the serial number of the first connected mouse. Here are the steps I tried:

  1. Connect mouse 1, run the command. [<RazerMouse PM1935H08501368>]
  2. Connect mouse 2, run the command. [<RazerMouse PM1935H08501368>]
  3. Disconnect mouse 1, run the command. []
  4. Disconnect mouse 2 and connect it again, run the command. [<RazerMouse PM2003H08501419>]
z3ntu commented 1 year ago

Then the problem is on OpenRazer side at least, and not the GUI. Not sure if that's easier to fix though then :wink:

When both mice are connected can you post both ls -al /sys/bus/hid/drivers/razermouse/0*/ and the output of openrazer-daemon -Fv (after e.g. systemctl --user stop openrazer-daemon.service)

dsdante commented 1 year ago

Sorry, I've taken mouse 2 to my work already; the testing session is over for me. :)

z3ntu commented 1 year ago

Okay, closing this then because in any case it's an OpenRazer issue that can't be solved in this repo.