Jestem w trakcie konfiguracji Debiana do swoich potrzeb i nadszedł właśnie czas na "ogarnięcie" myszki. Dokładnie to myszka laserowa Logitech MX 1000.
Standardowymi suwakami regulującymi myszkę nie da się ustawić tak aby chodziła jak w Windowsie (osoby które posiadają laserowe myszki chyba wiedzą o czym mówię), chodzi głównie o toporność ruchu, ociężałość i brak precyzji.
Po instalacji KDE4 i "wyklikaniu" zakładek ustawień systemowych natrafiłem na bardzo interesująca rzecz. Poniżej umieszczam zrzut z tego okna.
Postąpiłem według zaleceń i zajrzałem do podręcznika KDE - dział myszka. Z tego co zrozumiałem muszę napisać jakiś skrypt aby nadać sobie uprawienia.
Poniżej wklejam tekst z podręcznika, z góry przepraszam za brak formatowania . Tekst się trochę rozjechał. Postaram się wkleić czytelniejsza wersję.
W związku z tym czy ktoś mógłby mi naświetlić temat pisania tego skryptu?Logitech Support
Some Logitech USB mice support special features, such as switching to a higher resolution, or providing cordless status. If KDE was built with libusb support, then you will get an additional tab for each supported mouse that is plugged in.
The supported devices are:Receiver for Cordless PresenterKod: Zaznacz cały
Wheel Mouse Optical MouseMan Traveler MouseMan Dual Optical MX310 Optical Mouse MX510 Optical Mouse MX300 Optical Mouse MX500 Optical Mouse iFeel Mouse Mouse Receiver Dual Receiver Cordless Freedom Optical Cordless Elite Duo MX700 Optical Mouse Cordless Optical Trackman Cordless MX Duo Receiver MX100 Laser Mouse
Not all devices support all capabilities (typically cordless devices do not provide resolution switching, and of course only cordless devices support cordless status reporting), so some parts of the tab will not be enabled for some mouse types.
If the mouse supports resolution switching, the Sensor Resolution radio button group will be enabled, and you can switch from 400 counts per inch to 800 counts per inch and back. If you use 800 counts per inch, the same physical movement of the mouse will cause a greater (roughly double) amount of motion of the cursor. This tends to be popular amongst gamers.
If the mouse supports cordless reporting, the Battery Level and RF Channel widgets will be enabled. You can only change the RF Channel if your mouse has two channel support.
Fixing permission problems on Logitech mice
Because of the way USB devices work, the code that accesses the current status on Logitech mice needs to be able to write to the mouse. This should be handled by your distribution, but if not, you may need to do some configuration yourself.
On a Linux system, you should use the hotplug system to change the ownership and permissions on the mouse entry in /proc/bus/usb. One way to do this is to create a short script (/etc/hotplug/usb/consoleUserPerms) that changes the ownership and permissions, as shown below:That should be all that is needed on Linux - just copy the files into /etc/hotplug/usb/, and when the mouse is plugged in, the ownership and permissions should be changed so that the user at the console can access the mouse.Kod: Zaznacz cały
#!/bin/bash # # /etc/hotplug/usb/consoleUserPerms # # Sets up newly plugged in USB device so that the user who owns # the console according to pam_console can access it from user space # # Note that for this script to work, you'll need all of the following: # a) a line in the file /etc/hotplug/usb.usermap or another usermap file # in /etc/hotplug/usb/ that corresponds to the device you are using. # b) a setup using pam_console creates the respective lock files # containing the name of the respective user. You can check for that # by executing "echo `cat /var/{run,lock}/console.lock`" and # verifying the appropriate user is mentioned somewhere there. # c) a Linux kernel supporting hotplug and usbdevfs # d) the hotplug package ([url]http://linux-hotplug.sourceforge.net/[/url]) # # In the usermap file, the first field "usb module" should be named # "consoleUserPerms" to invoke this script. # if [ "${ACTION}" = "add" ] && [ -f "${DEVICE}" ] then # New code, using lock files instead of copying /dev/console permissions # This also works with non-kdm logins (e.g. on a virtual terminal) # Idea and code from Nalin Dahyabhai <nalin@redhat.com> if [ -f /var/run/console.lock ] then CONSOLEOWNER=`cat /var/run/console.lock` elif [ -f /var/lock/console.lock ] then CONSOLEOWNER=`cat /var/lock/console.lock` else CONSOLEOWNER= fi if [ -n "$CONSOLEOWNER" ] then chmod 0000 "${DEVICE}" chown "$CONSOLEOWNER" "${DEVICE}" chmod 0600 "${DEVICE}" fi fi The usermap file that goes with this is /etc/hotplug/usb/logitechmouse.usermap, as shown below: # script match_flags idVendor idProduct bcdDevice_lo bcdDevice_hi bDeviceClass bDeviceSubClass bDeviceProtocol bInterfaceClass bInterfaceSubClass bInterfaceProtocol driver_info # Wheel Mouse Optical consoleUserPerms 0x0003 0x046d 0xc00e 0x0000 0xffff 0x00 0x00 0x00 0x00 0x00 0x00 0x00000000 # MouseMan Traveler consoleUserPerms 0x0003 0x046d 0xc00f 0x0000 0xffff 0x00 0x00 0x00 0x00 0x00 0x00 0x00000000 # MouseMan Dual Optical consoleUserPerms 0x0003 0x046d 0xc012 0x0000 0xffff 0x00 0x00 0x00 0x00 0x00 0x00 0x00000000 # MX310 Optical Mouse consoleUserPerms 0x0003 0x046d 0xc01b 0x0000 0xffff 0x00 0x00 0x00 0x00 0x00 0x00 0x00000000 # MX510 Optical Mouse consoleUserPerms 0x0003 0x046d 0xc01d 0x0000 0xffff 0x00 0x00 0x00 0x00 0x00 0x00 0x00000000 # MX300 Optical Mouse consoleUserPerms 0x0003 0x046d 0xc024 0x0000 0xffff 0x00 0x00 0x00 0x00 0x00 0x00 0x00000000 # MX500 Optical Mouse consoleUserPerms 0x0003 0x046d 0xc025 0x0000 0xffff 0x00 0x00 0x00 0x00 0x00 0x00 0x00000000 # iFeel Mouse consoleUserPerms 0x0003 0x046d 0xc031 0x0000 0xffff 0x00 0x00 0x00 0x00 0x00 0x00 0x00000000 # Mouse Receiver consoleUserPerms 0x0003 0x046d 0xc501 0x0000 0xffff 0x00 0x00 0x00 0x00 0x00 0x00 0x00000000 # Dual Receiver consoleUserPerms 0x0003 0x046d 0xc502 0x0000 0xffff 0x00 0x00 0x00 0x00 0x00 0x00 0x00000000 # Cordless Freedom Optical consoleUserPerms 0x0003 0x046d 0xc504 0x0000 0xffff 0x00 0x00 0x00 0x00 0x00 0x00 0x00000000 # Cordless Elite Duo consoleUserPerms 0x0003 0x046d 0xc505 0x0000 0xffff 0x00 0x00 0x00 0x00 0x00 0x00 0x00000000 # MX700 Optical Mouse consoleUserPerms 0x0003 0x046d 0xc506 0x0000 0xffff 0x00 0x00 0x00 0x00 0x00 0x00 0x00000000 # Cordless Optical Trackman consoleUserPerms 0x0003 0x046d 0xc508 0x0000 0xffff 0x00 0x00 0x00 0x00 0x00 0x00 0x00000000 # Cordless MX Duo Receiver consoleUserPerms 0x0003 0x046d 0xc50b 0x0000 0xffff 0x00 0x00 0x00 0x00 0x00 0x00 0x00000000 # MX100 Laser Mouse consoleUserPerms 0x0003 0x046d 0xc50e 0x0000 0xffff 0x00 0x00 0x00 0x00 0x00 0x00 0x00000000 # Receiver for Cordless Presenter consoleUserPerms 0x0003 0x046d 0xc702 0x0000 0xffff 0x00 0x00 0x00 0x00 0x00 0x00 0x00000000
A tak na sam koniec - wygoglałem trochę opisów edycji plików konfiguracyjnych aby dostosować MX1000, jednak najpierw chcę spróbować odblokować tą zakładkę.
Z góry dziękuje za pomoc.