It just straight up just makes my mouse stop working #32
Comments
|
Similar thing is happening to me. The update seemed to be working fine until I turned on my computer this morning. With leetmouse uninstalled my mouse works fine. Edit: Preemptively hit enter |
|
This is really strange. The fact, that you say "about 2 minutes" at "Reloading device manager configuration" speaks for this: Pacman triggers a udev update, then these rules kick in that trigger leetmouse_bind. That script waits 120s for the kernel module to become ready. (This will change eventually in the future, since udev should never call/run blocking code. But I did not implement it yet) If building the kernel module was successful, modprobing the kernel module should work and the script continues. Apparently, modprobing the module did not work for you so the script keeps on hanging. In any case: Uninstall leetmouse, pull the latest changes and reinstall from scratch. There were some issues regarding compiling the kernel module after recent changes in |
|
Can you both please also try to run |
Pulling the latest changes yielded the same result |
|
Building the module works flawless how it looks like. Judging on that you still see issues, please tell me about the return value of modinfo. E.g. in bash, type |
|
The result of modinfo leetmouse: |
|
sudo dkms build --force leetmouse-driver/0.9.0 ✔ Building module: this is all it gave me |
it returned 0
|
|
also sorry for not responding for a while had a very full everything but im more avalible now, also i would like to thank you for all the work you do in this project for us mouse accell linux gamers, you are quite litteraly our only option and its a good one. thank you <3 if there is a option to donate you a small thing to show my greatfullness tell me |
Please repeat running |
|
I had absolutely the the same issue. And I've also tried Based on that, I thought that my |
This error looks unrelated to the issue, since @VirtualLusamine and @DontStarve72 seem to have issues with the bind script while their kernelmodule seems to compile properly. But I am glad that you were able to troubleshoot your problems! |
|
In my case, the bind script was hanging during |
I see. It is very closely related but the core issue is different. Thank you for your feedback! |
|
It seems that this error only occurs with razer mice and is linked to this pull request When testing with only a logitech mouse connected there are no problems with the installation, but when connecting a razer mouse the following error occurs after executing And the output of After changing the constant NUM_USAGES to 90 in utils.c the error in the installation of the package continues, but now the mouse responds after finishing the installation. Unfortunately I can't find the root cause of the error as I don't have C knowledge let alone Linux drivers, but I hope this helps. All this was tested on kernel 6.3.1 on arch with a Logitech superlight x and a Razer viper v2 pro. |
|
Good catch! Increasing this value might do the trick. I will need to take a closer look, if increasing this value can break anything or not. Thank you for your valuable feedback! |
|
for all my course and internship in programming taught me, i cant explain to you how some things work. Coding sometimes leads us to mental breakdowns and mental anguish, puts us into a depressive state and debbugging the same error for days makes you go mentally unwell. But one of the things that makes me cry with joy is somehow, for some reason. you found something that makes it work, and as i dont need to analize this code or develop it as far as i know. im happy. thank you so much. you have a keen eye. ill still offer assistance in debugging and testing the driver in my computer. also can you tell me what the NUM_USAGES value controlls. im curious and could help lead to a solution |
|
It returns 0 for me as well. Can confirm that I'm also attempting to use a Razer Viper V2 Pro |
|
In util.c
Changing return -1 to 0/1 allows it to build on razer devices, no clue why I just saw it and thought it should be 1 or 0 instead of -1 tried to build it and it worked. Tried when it was -1 it would just freeze my mouse |
|
No clue if it has to do with maybe another daemon getting in the way that uses dkms I.E. OpenRazer causing it to completely fail. If the 0/1 value is supposed to be a -1, I'll completely uninstall OpenRazer and attempt to build without it installed. |
I would be careful here. Parsing the mouses USB descriptor failed on your device for some reason. By changing the return of Increasing the value of NUM_USAGES looks more ideal to me at first glance. |
Ah yeah it was indeed working for me fine but it continuously loading does sound like it would be pretty bad in the long run as it would just build up
This happens to be the problem OpenRazer was interfering with the building of the driver, for me at least, no clue how we could manage to get both of them to interface without throwing that udev error people have been getting as well. I can live without having customized RBG on my mouse as well as changing the response time but others might not. |
|
Same issue (or same symptoms) but without openrazer installed. It's never been on my system. Still a razer mouse though, build appears to succeed with no errors but the mouse simply doesn't work at all. It's definitely the bind and unbind scripts, neither works correctly. It's like the script takes ownership of the mouse away from the normal driver but doesn't give it to leetmouse. Only way to make my mouse work again is to uninstall the driver and relaunch the x server. Is there a way to make some kind of verbose output from those bind/unbind scripts? That'd help a lot with tracking down what's causing this. |
|
Issue persists with Razer Naga X. Changing NUM_USAGE to 90 did not change anything. Breaks system, making every package install/update hang at "Reloading Device Manager Config". Returns to normal when uninstalled. |
|
I have the same issue but with a corsair katar pro. |
|
Those who are having problems with hanging at install, try the fixed point branch instead thats what i used for a while and it worked with my mice when it was hanging (naga and deathadder). Recently got a model o wireless and have had no issues since |
|
Having the same issue the past few days while on arch, kernel 6.8.5. Reinstalling results in the same hang mentioned earlier at
Does not work at all with the driver installed. Only works again after uninstalling, unplugging the mouse and plugging it back in. Tried setting NUM_USAGES to 90 but no dice. Using a finalmouse ulx. |
|
Tried the steps in Manual compile, insmod, bind which work fine, the driver shows up in lsmod, but when manually binding the leetmouse driver it fails: Unbinding/binding to usbhid always works. Is the leetmouse driver missing a reference somewhere? |
|
similar issue, trackball will stop working for around 2 minutes after a reboot, then works with no acceleration. running sudo dkms build --force leetmouse-driver/0.9.0 returns ` ign command: /usr/lib/modules/6.6.31-1-lts/build/scripts/sign-file Building module: EDIT: not sure what was broken myself, i just uninstalled everything and started over. still hangs on a similar section of the install but functions now |
i lost 3 days trying to fix my mouse not working untill i realized it was some update you made, can i get a previous version that used dkms and not depmod or something or you updating so it works, it said a error in the command: dmesg | tail
that it wasnt working and had a exit code of -1 so it just didnt work and didnt let my mouse work either. i cant really play without mouse accel so id really need help here.
my mouse is Razer Lancehead Turnament Edition and i have open razer installed too.
i hope you can help me
The text was updated successfully, but these errors were encountered: