- Не работает беспроводная мышь. на XP
- Rapoo 1620 не работает
- Related products
- M260 Silent
- M500 Silent
- M280 Silent
- M100 Silent
- User Manual
- General FAQ
- Frequently Asked Questions: 1620
- How to connect M100 to a MacBook/ PC/ Laptop via 2.4 GHz wireless transmission with a USB dongle?
- How to repair the 2.4 GHz wireless connection?
- I have lost/broken the USB receiver (dongle). Can I receive a new USB-receiver?
- I just bought it and cannot find the USB receiver. Where is it?
- The mouse arrow shakes, moves strangely or does not move at all. What can I do?
- The mouse shows irregular failures during usage?
- The mouse is suddenly not working. What can I do?
- My product is faulty. What can I do?
- Couldn’t find the answer in the FAQs?
- wireless мышь Rapoo 1620 сконфигурировалась как клавиатура и мышь — это правильно ?
Не работает беспроводная мышь. на XP
Помощь в написании контрольных, курсовых и дипломных работ здесь.
Беспроводная мышь
Доброго дня Всем. Столкнулся я с такой проблемой приобрел себе беспроводную мышь Rapoo T6.
Не работает беспроводная мышь
Купил недавно беспроводную мышь RoadMice Ford GT500 2,4hz USB . включаю на ноутбуке работает.
Не работает беспроводная мышь
Доброго времени суток! Перестала работать, на ноутбуке, беспроводная мышь. На стационарном.
Неправильно работает беспроводная мышь
Приветствую всех форумчан. Имеется аккумуляторная беспроводная мышка. Работала около года.
Беспроводная мышь LENTEL JY-WM33 не работает на SAMSUNG r410
Добрый день, уважаемые форумчане! Увидев заголовок вы наверное подумаете, что очередной чайник.
Мышь работает через раз, то есть запустил ОС — мышь не работает, перезагрузил — мышь работает
Установлена Windows 7 со всеми последними обновлениями. Все всегда замечательно работало. Но с.
Wi-FI и беспроводная мышь
Имеется ПК с USB адаптером Wi-Fi. Выявил проблему падения скорости
в 20 раз — работа беспроводной.
Беспроводная мышь
ТУт такая проблема была неработающая мышь я её починил,припаяв питание напрямую(не в.
Беспроводная мышь и Windows XP
Подскажите пожалуйста, уже все перепробовал и ничего. Дрова есть, мышка рабочая (проверял на другом.
Залипает беспроводная мышь.
Была беспроводная мышка Microsoft Wireless Optical Mouse 2000, взял A4Tech (G6-19) Silver Grey.
Источник
Rapoo 1620 не работает
€ 9.99 recommended retail price
Related products
Multi-mode Wireless Silent Optical Mouse
M260 Silent
Multi-mode Wireless Silent Optical Mouse
M500 Silent
Multi-mode Wireless Silent Optical Mouse
M280 Silent
Multi-mode Wireless Silent Optical Mouse
M100 Silent
User Manual
Download the Quick Start Guide for this product
General FAQ
Check commonly asked questions for further information
Frequently Asked Questions: 1620
Please check our FAQs to find answers and solutions to common questions.
How to connect M100 to a MacBook/ PC/ Laptop via 2.4 GHz wireless transmission with a USB dongle?
1. Take out the receiver from the mouse.
2. Place the receiver into a PC or laptop USB port.
How to repair the 2.4 GHz wireless connection?
After you unplug and replug the USB receiver, within 30 seconds, turn off the mouse and then turn it on with the left key pressed.
I have lost/broken the USB receiver (dongle). Can I receive a new USB-receiver?
It is not possible to provide a replacement receiver for this product.
This is because during production the product and the Nano USB receiver (dongle) are assigned a unique code, so the product can only communicate with the bundled original receiver. This production process is also performed for security reasons.
I just bought it and cannot find the USB receiver. Where is it?
The USB receiver is stored inside the battery compartment of the mouse. The special receiver storage compartment is located there so you can always store the dongle safely when not in use to prevent damage or loss.
The mouse arrow shakes, moves strangely or does not move at all. What can I do?
1. Use a mousepad or a piece of paper to check if the surface may be the reason.
2. Try using the mouse on a different surface.
3. Clean the sensor on the bottom of the mouse with a dry cloth.
The mouse shows irregular failures during usage?
1. Move other active wireless devices away from the mouse and the USB receiver.
2. The PC can not respond immediately because the CPU is under full load.
3. Try changing the battery.
The mouse is suddenly not working. What can I do?
1. Make sure the device is turned on.
2. Make sure the USB receiver is plugged into the PC/ laptop’s USB port.
3. If the PC/ laptop cannot initially recognize the USB receiver, please replug the receiver.
4. Check if the battery is installed correctly.
5. In case of a low battery, please try changing the battery.
6. Move other working wireless devices away from the mouse and the USB receiver.
7. Please keep away from walls or big objects because this may reduce the range.
My product is faulty. What can I do?
We offer a ‘return to the retailer’ warranty on our products. In case of a defect, please return the product to your retailer with a clear description of the problem, proof of purchase, and all accessories. During the warranty period, you will receive a replacement product from the retailer if available.
Couldn’t find the answer in the FAQs?
Contact us and fill out the form with as much information as possible.
One of our support staff will help you as soon as possible.
Источник
wireless мышь Rapoo 1620 сконфигурировалась как клавиатура и мышь — это правильно ?
debian sid xfce4
kernel 3.2.0
xorg.conf нет в системе — работаем с evdev
не знаю, это нормально или нет, но в логах вижу как моя wireless мышь Rapoo 1620 сконфигурировалась как мышь и как клава одновременно. Прошу прояснить — это нормально или нет.
1.908031] usb 2-1: new full-speed USB device number 2 using uhci_hcd
[ 2.064201] usb 2-1: New USB device found, idVendor=24ae, idProduct=2000
[ 2.064256] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2.064312] usb 2-1: Product: RAPOO 2.4G Wireless Device
[ 2.064360] usb 2-1: Manufacturer: RAPOO
[ 2.077883] input: RAPOO RAPOO 2.4G Wireless Device as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0/input/input0
[ 2.078258] generic-usb 0003:24AE:2000.0001: input,hidraw0: USB HID v1.01 Keyboard [RAPOO RAPOO 2.4G Wireless Device] on usb-0000:00:1d.0-1/input0
[ 2.082826] input: RAPOO RAPOO 2.4G Wireless Device as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.1/input/input1
[ 2.083636] generic-usb 0003:24AE:2000.0002: input,hiddev0,hidraw1: USB HID v1.01 Mouse [RAPOO RAPOO 2.4G Wireless Device] on usb-0000:00:1d.0-1/input1
[ 2.083733] usbcore: registered new interface driver usbhid
[ 2.083780] usbhid: USB HID core driver
[ 2.304025] usb 3-2: new low-speed USB device number 2 using uhci_hcd
[ 2.481798] usb 3-2: New USB device found, idVendor=04f2, idProduct=0833
[ 2.481847] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2.481890] usb 3-2: Product: USB Keyboard
[ 2.481929] usb 3-2: Manufacturer: CHICONY
[ 2.498264] input: CHICONY USB Keyboard as /devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2:1.0/input/input2
[ 2.498543] generic-usb 0003:04F2:0833.0003: input,hidraw2: USB HID v1.11 Keyboard [CHICONY USB Keyboard] on usb-0000:00:1d.1-2/input0
[ 2.535910] input: CHICONY USB Keyboard as /devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2:1.1/input/input3
[ 2.536236] generic-usb 0003:04F2:0833.0004: input,hiddev0,hidraw3: USB HID v1.11 Device [CHICONY USB Keyboard] on usb-0000:00:1d.1-2/input1
[ 3.457691] kjournald starting. Commit interval 5 seconds
41.388] (II) LoadModule: «evdev»
[ 41.388] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 41.407] (II) Module evdev: vendor=«X.Org Foundation»
[ 41.407] compiled for 1.12.1, module version = 2.7.0
[ 41.407] Module class: X.Org XInput Driver
[ 41.407] ABI class: X.Org XInput driver, version 16.0
[ 41.407] (II) Using input driver ‘evdev’ for ‘Power Button’
[ 41.407] (**) Power Button: always reports core events
[ 41.407] (**) evdev: Power Button: Device: «/dev/input/event5»
[ 41.407] (—) evdev: Power Button: Vendor 0 Product 0x1
[ 41.407] (—) evdev: Power Button: Found keys
[ 41.407] (II) evdev: Power Button: Configuring as keyboard
[ 41.407] (**) Option «config_info» «udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input5/event5»
[ 41.407] (II) XINPUT: Adding extended input device «Power Button» (type: KEYBOARD, id 6)
[ 41.407] (**) Option «xkb_rules» «evdev»
[ 41.407] (**) Option «xkb_model» «pc104»
[ 41.407] (**) Option «xkb_layout» «us,ru»
[ 41.407] (**) Option «xkb_variant» «winkeys»
[ 41.407] (**) Option «xkb_options» «grp:rctrl_toggle,terminate:ctrl_alt_bksp,grp_led:scroll»
[ 41.484] (II) config/udev: Adding input device Power Button (/dev/input/event4)
[ 41.484] (**) Power Button: Applying InputClass «evdev keyboard catchall»
[ 41.484] (**) Power Button: Applying InputClass «evdev keyboard catchall»
[ 41.484] (II) Using input driver ‘evdev’ for ‘Power Button’
[ 41.484] (**) Power Button: always reports core events
[ 41.484] (**) evdev: Power Button: Device: «/dev/input/event4»
[ 41.484] (—) evdev: Power Button: Vendor 0 Product 0x1
[ 41.484] (—) evdev: Power Button: Found keys
[ 41.484] (II) evdev: Power Button: Configuring as keyboard
[ 41.484] (**) Option «config_info» «udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input4/event4»
[ 41.484] (II) XINPUT: Adding extended input device «Power Button» (type: KEYBOARD, id 7)
[ 41.484] (**) Option «xkb_rules» «evdev»
[ 41.484] (**) Option «xkb_model» «pc104»
[ 41.484] (**) Option «xkb_layout» «us,ru»
[ 41.484] (**) Option «xkb_variant» «winkeys»
[ 41.485] (**) Option «xkb_options» «grp:rctrl_toggle,terminate:ctrl_alt_bksp,grp_led:scroll»
[ 41.485] (II) config/udev: Adding input device RAPOO RAPOO 2.4G Wireless Device (/dev/input/event0)
[ 41.485] (**) RAPOO RAPOO 2.4G Wireless Device: Applying InputClass «evdev keyboard catchall»
[ 41.486] (**) RAPOO RAPOO 2.4G Wireless Device: Applying InputClass «evdev keyboard catchall»
[ 41.486] (II) Using input driver ‘evdev’ for ‘RAPOO RAPOO 2.4G Wireless Device’
[ 41.486] (**) RAPOO RAPOO 2.4G Wireless Device: always reports core events
[ 41.486] (**) evdev: RAPOO RAPOO 2.4G Wireless Device: Device: «/dev/input/event0»
[ 41.486] (—) evdev: RAPOO RAPOO 2.4G Wireless Device: Vendor 0x24ae Product 0x2000
[ 41.486] (—) evdev: RAPOO RAPOO 2.4G Wireless Device: Found keys
[ 41.486] (II) evdev: RAPOO RAPOO 2.4G Wireless Device: Configuring as keyboard
[ 41.486] (**) Option «config_info» «udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0/input/input0/event0»
[ 41.486] (II) XINPUT: Adding extended input device «RAPOO RAPOO 2.4G Wireless Device» (type: KEYBOARD, id 8)
[ 41.486] (**) Option «xkb_rules» «evdev»
[ 41.486] (**) Option «xkb_model» «pc104»
[ 41.486] (**) Option «xkb_layout» «us,ru»
[ 41.486] (**) Option «xkb_variant» «winkeys»
[ 41.486] (**) Option «xkb_options» «grp:rctrl_toggle,terminate:ctrl_alt_bksp,grp_led:scroll»
[ 41.487] (II) config/udev: Adding input device RAPOO RAPOO 2.4G Wireless Device (/dev/input/event1)
[ 41.487] (**) RAPOO RAPOO 2.4G Wireless Device: Applying InputClass «evdev pointer catchall»
[ 41.487] (**) RAPOO RAPOO 2.4G Wireless Device: Applying InputClass «evdev keyboard catchall»
[ 41.487] (**) RAPOO RAPOO 2.4G Wireless Device: Applying InputClass «evdev pointer catchall»
[ 41.487] (**) RAPOO RAPOO 2.4G Wireless Device: Applying InputClass «evdev keyboard catchall»
[ 41.487] (II) Using input driver ‘evdev’ for ‘RAPOO RAPOO 2.4G Wireless Device’
[ 41.487] (**) RAPOO RAPOO 2.4G Wireless Device: always reports core events
[ 41.487] (**) evdev: RAPOO RAPOO 2.4G Wireless Device: Device: «/dev/input/event1»
[ 41.487] (—) evdev: RAPOO RAPOO 2.4G Wireless Device: Vendor 0x24ae Product 0x2000
[ 41.487] (—) evdev: RAPOO RAPOO 2.4G Wireless Device: Found 9 mouse buttons
[ 41.487] (—) evdev: RAPOO RAPOO 2.4G Wireless Device: Found scroll wheel(s)
[ 41.487] (—) evdev: RAPOO RAPOO 2.4G Wireless Device: Found relative axes
[ 41.487] (—) evdev: RAPOO RAPOO 2.4G Wireless Device: Found x and y relative axes
[ 41.487] (—) evdev: RAPOO RAPOO 2.4G Wireless Device: Found absolute axes
[ 41.487] (II) evdev: RAPOO RAPOO 2.4G Wireless Device: Forcing absolute x/y axes to exist.
[ 41.487] (—) evdev: RAPOO RAPOO 2.4G Wireless Device: Found keys
[ 41.487] (II) evdev: RAPOO RAPOO 2.4G Wireless Device: Configuring as mouse
[ 41.487] (II) evdev: RAPOO RAPOO 2.4G Wireless Device: Configuring as keyboard
[ 41.487] (II) evdev: RAPOO RAPOO 2.4G Wireless Device: Adding scrollwheel support
[ 41.487] (**) evdev: RAPOO RAPOO 2.4G Wireless Device: YAxisMapping: buttons 4 and 5
[ 41.487] (**) evdev: RAPOO RAPOO 2.4G Wireless Device: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 41.487] (**) Option «config_info» «udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.1/input/input1/event1»
[ 41.487] (II) XINPUT: Adding extended input device «RAPOO RAPOO 2.4G Wireless Device» (type: KEYBOARD, id 9)
[ 41.487] (**) Option «xkb_rules» «evdev»
[ 41.487] (**) Option «xkb_model» «pc104»
[ 41.487] (**) Option «xkb_layout» «us,ru»
[ 41.487] (**) Option «xkb_variant» «winkeys»
[ 41.488] (**) Option «xkb_options» «grp:rctrl_toggle,terminate:ctrl_alt_bksp,grp_led:scroll»
[ 41.488] (II) evdev: RAPOO RAPOO 2.4G Wireless Device: initialized for relative axes.
[ 41.488] (WW) evdev: RAPOO RAPOO 2.4G Wireless Device: ignoring absolute axes.
[ 41.488] (**) RAPOO RAPOO 2.4G Wireless Device: (accel) keeping acceleration scheme 1
[ 41.488] (**) RAPOO RAPOO 2.4G Wireless Device: (accel) acceleration profile 0
[ 41.488] (**) RAPOO RAPOO 2.4G Wireless Device: (accel) acceleration factor: 2.000
[ 41.488] (**) RAPOO RAPOO 2.4G Wireless Device: (accel) acceleration threshold: 4
[ 41.489] (II) config/udev: Adding input device RAPOO RAPOO 2.4G Wireless Device (/dev/input/mouse0)
[ 41.489] (II) No input driver specified, ignoring this device.
[ 41.489] (II) This device may have been added with another device file.
соответственно в /proc/bus/input вижу и клаву и мышь для Rapoo + для моей usb CHICONY клавы вижу 2 записи — это правильно ?
/proc/bus/input# cat devices
I: Bus=0003 Vendor=24ae Product=2000 Version=0101
N: Name=«RAPOO RAPOO 2.4G Wireless Device»
P: Phys=usb-0000:00:1d.0-1/input0
S: Sysfs=/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0/input/input0
U: Uniq=
H: Handlers=sysrq kbd event0
B: PROP=0
B: EV=120013
B: KEY=10000 7 ff9f207a c14057ff febeffdf ffefffff ffffffff fffffffe
B: MSC=10
B: LED=1f
I: Bus=0003 Vendor=24ae Product=2000 Version=0101
N: Name=«RAPOO RAPOO 2.4G Wireless Device»
P: Phys=usb-0000:00:1d.0-1/input1
S: Sysfs=/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.1/input/input1
U: Uniq=
H: Handlers=kbd mouse0 event1
B: PROP=0
B: EV=1f
B: KEY=4837fff 72ff32d bf544446 0 0 1f0001 20f90 8b17c000 677bfa d941dfed 9ed680 4400 0 10000002
B: REL=1c3
B: ABS=1 0
B: MSC=10
I: Bus=0003 Vendor=04f2 Product=0833 Version=0111
N: Name=«CHICONY USB Keyboard»
P: Phys=usb-0000:00:1d.1-2/input0
S: Sysfs=/devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2:1.0/input/input2
U: Uniq=
H: Handlers=sysrq kbd event2
B: PROP=0
B: EV=120013
B: KEY=10000 7 ff800000 7ff febeffdf f3cfffff ffffffff fffffffe
B: MSC=10
B: LED=7
I: Bus=0003 Vendor=04f2 Product=0833 Version=0111
N: Name=«CHICONY USB Keyboard»
P: Phys=usb-0000:00:1d.1-2/input1
S: Sysfs=/devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2:1.1/input/input3
U: Uniq=
H: Handlers=kbd event3
B: PROP=0
B: EV=13
B: KEY=ff0000 0 0 0 0 0 0 0 0 2000000 387a d801d001 1e0000 0 0 0
B: MSC=10
I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name=«Power Button»
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input4
U: Uniq=
H: Handlers=kbd event4
B: PROP=0
B: EV=3
B: KEY=100000 0 0 0
I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name=«Power Button»
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input5
U: Uniq=
H: Handlers=kbd event5
B: PROP=0
B: EV=3
B: KEY=100000 0 0 0
I: Bus=0010 Vendor=001f Product=0001 Version=0100
N: Name=«PC Speaker»
P: Phys=isa0061/input0
S: Sysfs=/devices/platform/pcspkr/input/input6
U: Uniq=
H: Handlers=kbd event6
B: PROP=0
B: EV=40001
B: SND=6
в /dev/input вижу 2 устройства для мыши
by-id by-path event0 event1 event2 event3 event4 event5 event6 mice mouse0
Дело в том, что не понятно по каким причинам, но мышь отваливается — совершенно не вижу никакой закономерности. Как правило после того, как мышь отвалилась, она сама потом и подключается, но иногда приходится передергивать usb приемник, чтобы восстановить работу мыши. Autosuspend запрещен
Источник