- This topic has 17 odgovora, 3 glasa, and was last updated 21 years, 3 months ranije by
.
-
Članci
-
Dakle digao slack 10.1, kde 3.4 medjutim mx700 nece da radi. Nadjoh negde na forumu da rc.hotplug blokira ps/2 iako je ovaj na usb i iskljucim ga i radi. (naravno kao neki obican pacov)
e sad u helpu sam video da kde 3.4 ima podrsku za logitechove miseve ali da mora u hotplug da se dodaju neki skriptovi …. nisam imao vremena da proucim to. Jel neko imao slicnih problema i da ih je resio?
Nisam dobijao nikakve errore. Posto imam i touchpad kde se startovao jedino kad sam /dev/mouse -> psaux promenio na mouse -> /dev/input/mouse
onda nije hteo da se podigneEvo ovo sam nasao u helpu ali iskren da budem nije mi bas jasno.
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:
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
Receiver for Cordless Presenter
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:#!/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 (http://linux-hotplug.sourceforge.net/)
#
# 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
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
fiThe 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 0x00000000That 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.
Meni MX310 sasvim lepo radi na slacku bilo da ga kacim kao USB ili sa PS/2 adapterom. Evo iz mog xorg.conf-a:
Identifier “Logitech MX310”
Driver “mouse”
Option “Protocol” “explorerps/2”
Option “Dev Name” “Logitech USB-PS/2 Optical Mouse”
Option “Device” “/dev/mouse”
Option “Buttons” “8”
Option “ZAxisMapping” “7 8”“Dev Name” ne moras da koristis, ali ako bas hoces nadji ga sa ‘less /proc/bus/input/devices’. ZAxisMapping mi je takav posto koristim imwheel da bih imao i tastere za levo/desno, tebi bi verovatno odgovaralo “4 5″
Sad, sto se onih skripti tice, one bi trebalo da omoguce obicnom useru da moze da podesava DPI misa, na kom kanalu radi bezicni, kao i da proverava status baterije, ali to kod mene jednostavno ne radi tako. TRebalo bi da daju write permission useru. Zato sam radio rucno, na silu. Mis jeste usb, ali posto je malo verovatno da ces svaki cas menjati port na koji je ukljucen, mozes pri bootu da mu podesis permissions na silu.
Samo odredi koji je device u pitanju sa ‘lsusb” evo, kod mene je ovakvo stanje:
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 002: ID 046d:c01b Logitech, Inc. MX310 Optical Mouse
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000Sto ce reci da mi je mis na /proc/bus/usb/003/002
Ja mu radim sledece pri bootu:
chown root.plugdev /proc/bus/usb/003/002
chmod 660 /proc/bus/usb/003/002Grupu plugdev koristim zato sto sam tu foru naucio od debiana, a onda svaki korisnik koji je u plugdev grupi moze da podesava misa po svom nahodjenju. Ako ti se ne dopada ta varijanta, uradi samo
chown root.users i svi useri ce moci da rade sta hoce.
A reci mi kako si podesio to sve za misa u xorg.conf. Ja se secam da je ranije bila komanda mouse ili tako nesto pa ti slack izbaci mouse config ali to sad nema. Kao sto rekoh kad mi je hotplug enablovan onda mi mis ne radi? Jel znas sto je to tako? Btw jel moze da mi radi usb stick ako je hotplug disaeblovan? Posto mi za mount /dev/sda1 prijavljuje unsupported block device ili tako nesto
P.C. Komanda se zove mouseconfig ali je ja nemam 🙂 a imao sam je prosli put kad sam instalirao linux 😀
Uspeo je nekako da proradi. Kao DevName pronasao je Logitech USB Receiver sto i koristim jer je mis bezicni 🙂 e sad lsusb mi ne daje nista.
E da jel znas mozda (ja pretpostavljam da je xorg.conf ali… ) zasto mi kad restartujem x ili idem na log of user konzola mi treperi sva i ne mogu nista da procitam?
Uspeo je nekako da proradi. Kao DevName pronasao je Logitech USB Receiver sto i koristim jer je mis bezicni 🙂 e sad lsusb mi ne daje nista.
E da jel znas mozda (ja pretpostavljam da je xorg.conf ali… ) zasto mi kad restartujem x ili idem na log of user konzola mi treperi sva i ne mogu nista da procitam?
P.S. Kao ZAxisMapping stavio sam “4 5” i skrol mi radi ali kako da namestim tumb buttons da rade alt+left i alt+right kao i da mi ono jedno dugme radi double click umesto sto to radi scroll klick?
Mnogo trazim znam 🙂
Nemam pojma za konzolu… Sta znam… baci svoj xorg.conf ovde pa da pogledamo… sta kazu logovi? Nadam se da ne koristis onaj kde-ov applet za screen resize and rotate. Mislim, mozes ti da ga korstis, ali ja vise volim da to podesim u xorg.conf, pa i gamma-u.
Moze da bude milion stvari.Sto se tice dugmica, znam samo kako naterati levo desno, a za to imas moj mini-howto u forumu tricks and tips.
Moraš biti prijavljen da bi postavio komentar u ovoj temi.