well, the good news is: My Playstation Dualshock 2 works now, unlike with the previous Berryboot/Openelec version.
If the mouse had not worked at least to some degree, I would probably have given up already.
well, the good news is: My Playstation Dualshock 2 works now, unlike with the previous Berryboot/Openelec version.
If the mouse had not worked at least to some degree, I would probably have given up already.
Also, calling BS and 'ignorant' in your first post on this forum is not the preferred way of making friends here.
I care more about solutions than having 6 million "friends".
You seem to care more about your getting triggered than about me providing a solution to a problem that thousands of users seem to have.
Also, no need to get all triggered and hurt feels when I mention Berryboot and OpenELEC. I know it is "dead" that's why I am checking LibreELEC out now.
These answers are complete BS, ignorant and plain wrong.
I had same problem on my first Raspberry install and found the solution with some searching:
Add: usbhid.mousepoll=0 to /boot/cmdline.txt
fixed!
only problem I have now is that my first install was with Berryboot and not Noobs.
Berryboot mounts the /boot partition for easy access inside both Rasbian and OpenELEC.
Now I just installed via Noobs, and there's no /boot mounted.
Looks like Noobs or LibreELEC mount this partition as /flash, so:
Add: usbhid.mousepoll=0 to /flash/cmdline.txt
this would fix your mouse problem.
New Problem: LibreELEC mounts /flash as read-only, so you need to look which device and partition it is and remount it as writeable:
eg: df -h (to see mounted partitions), then:
mount -o remount,rw /dev/mmcblk0p8 /flash
(just chance the /dev/... to fit your local setup)
now you can do: nano /flash/cmdline.txt and fix your mouse lag problem...
PS. Yes, this topic was over 100 days old, but it was the first answer I got in DuckDuckGo when looking for a solution... so I added it here once I figured it out.