046d:c50e LX5 cordless optical logitech mouse wrongly identified as MX1000 laser mouse

Bug #1087981 reported by dino99
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

oem@oem-desktop:~$ logitech_applet
003/002 046D/C50E M-RAG97 MX1000 Laser Mouse
   Channel 2 Battery: 5 Single channel No 800cpi support No Horiz Roller No Vert Roller 2 butt.

oem@oem-desktop:~$ dmesg | grep mouse
[ 0.761534] mousedev: PS/2 mouse device common for all mice

oem@oem-desktop:~$ dmesg | grep usb
[ 0.153470] ACPI: bus type usb registered
[ 0.153470] usbcore: registered new interface driver usbfs
[ 0.153470] usbcore: registered new interface driver hub
[ 0.153470] usbcore: registered new device driver usb
[ 0.760041] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 0.760043] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.760046] usb usb1: Product: EHCI Host Controller
[ 0.760048] usb usb1: Manufacturer: Linux 3.7.0-5-generic ehci_hcd
[ 0.760050] usb usb1: SerialNumber: 0000:00:1d.7
[ 0.760348] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
[ 0.760350] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.760352] usb usb2: Product: UHCI Host Controller
[ 0.760354] usb usb2: Manufacturer: Linux 3.7.0-5-generic uhci_hcd
[ 0.760357] usb usb2: SerialNumber: 0000:00:1d.0
[ 0.760585] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
[ 0.760588] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.760590] usb usb3: Product: UHCI Host Controller
[ 0.760592] usb usb3: Manufacturer: Linux 3.7.0-5-generic uhci_hcd
[ 0.760595] usb usb3: SerialNumber: 0000:00:1d.1
[ 1.256015] usb 3-1: new low-speed USB device number 2 using uhci_hcd
[ 1.430589] usb 3-1: New USB device found, idVendor=046d, idProduct=c50e
[ 1.430592] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1.430594] usb 3-1: Product: USB RECEIVER
[ 1.430597] usb 3-1: Manufacturer: Logitech
[ 1.540191] usbcore: registered new interface driver usbhid
[ 1.540193] usbhid: USB HID core driver
[ 1.572331] input: Logitech USB RECEIVER as /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0/input/input3
[ 1.572882] hid-generic 0003:046D:C50E.0001: input,hidraw0: USB HID v1.11 Mouse [Logitech USB RECEIVER] on usb-0000:00:1d.1-1/input0

Related report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1006145

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.7.0-5-generic 3.7.0-5.13
ProcVersionSignature: Ubuntu 3.7.0-5.13-generic 3.7.0-rc8
Uname: Linux 3.7.0-5-generic i686
ApportVersion: 2.6.3-0ubuntu4
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: oem 3259 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Date: Sat Dec 8 14:29:36 2012
HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.

 eth1 no wireless extensions.
Lsusb:
 Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
MarkForUpload: True
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-5-generic root=UUID=9e61e83e-bca9-43cf-aa90-5a68892213fa ro crashkernel=384M-2G:64M,2G-:128M quiet
RelatedPackageVersions:
 linux-restricted-modules-3.7.0-5-generic N/A
 linux-backports-modules-3.7.0-5-generic N/A
 linux-firmware 1.98
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
WpaSupplicantLog:

dmi.bios.date: 07/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3002
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5W DH Deluxe
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5W DH Deluxe
dmi.product.version: System Version
dmi.sys.vendor: ASUSTEK COMPUTER INC

Revision history for this message
dino99 (9d9) wrote :
summary: - LX5 corless optical logitech mouse wrongly identified as MX1000 laser
+ LX5 cordless optical logitech mouse wrongly identified as MX1000 laser
mouse
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Re: LX5 cordless optical logitech mouse wrongly identified as MX1000 laser mouse

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.7 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7-raring/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
dino99 (9d9) wrote :

this system is using the latest available kernel

tags: added: bot-stop-naging
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: kernel-bug-exists-upstream
removed: bot-stop-naging i386 raring
Revision history for this message
dino99 (9d9) wrote :

Feedback with kernel 3.8.0.17

/dev/input : all the mouse0/mice/event(x) are 0 bytes "unknown"
/dev/input/by-id : usb-Logitech_USB-RECEIVER-mouse 0 bytes "Link to unknown"
/dev/input/by-id : usb-Logitech-USB-RECEIVER-event-mouse 0 bytes "Link to unknown"

(its the same "Link to unknown" with 0 bytes into /dev/input/by-path)

with the same mouse, now the identification is:

cat /proc/bus/input/devices:
....
I: Bus=0003 Vendor=046d Product=c50e Version=0111
N: Name="Logitech USB RECEIVER"
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/input3
U: uniq=
H: Handlers=mouse0 event3
B: PROP=0
B: EV=20017
B: KEY=ffff0000 0 0 0 0 0 0 0 0
B: REL=143
B: MSC=10
B: LED=ff00

Thats always the same issues: grab & drag is quite impossible, selecting a block of cells or a group of words is also impossible.

Revision history for this message
dino99 (9d9) wrote :

oem@oem-desktop:~$ dmesg | grep Logitech
[ 1.539189] usb 2-2: Manufacturer: Logitech
[ 1.585900] input: Logitech USB RECEIVER as /devices/pci0000:00/0000:00:1d.0/usb2/2-2/2-2:1.0/input/input3
[ 1.586106] hid-generic 0003:046D:C50E.0001: input,hidraw0: USB HID v1.11 Mouse [Logitech USB RECEIVER] on usb-0000:00:1d.0-2/input0
[ 38.387619] input: Logitech USB RECEIVER as /devices/pci0000:00/0000:00:1d.0/usb2/2-2/2-2:1.0/input/input4
[ 38.387783] hid-generic 0003:046D:C50E.0002: input,hidraw0: USB HID v1.11 Mouse [Logitech USB RECEIVER] on usb-0000:00:1d.0-2/input0

Revision history for this message
dino99 (9d9) wrote :

i've installed the latest 3.9 rc6 kernel, and get the same issue

Revision history for this message
dino99 (9d9) wrote :

Now using the 3.8.0.19 kernel + nvidia-313-updates

but looking at the latest xorg.0.log, xserver-xorg-input-evdev (2.7.3-0ubuntu2b2) is very confused and set bad config for that 2buttons+1wheel mouse (like the 20 buttons found !!!!).
So i wonder if xserver-xorg-input-evdev might be blamed instead of the kernel itself.

tags: added: i386 raring
dino99 (9d9)
affects: linux → evdev
dino99 (9d9)
tags: added: saucy
Revision history for this message
dino99 (9d9) wrote :
Revision history for this message
dino99 (9d9) wrote :

Following the report comments from #9 above, i've installed ltunify.
But ltunify list cant find a receiver; which should mean that the builtin hid-logitech-dj kernel module or mousedev is confusing the system.

penalvch (penalvch)
tags: added: bios-outdated-3002 needs-upstream-testing regression-potential
penalvch (penalvch)
summary: - LX5 cordless optical logitech mouse wrongly identified as MX1000 laser
- mouse
+ 046d:c50e LX5 cordless optical logitech mouse wrongly identified as
+ MX1000 laser mouse
Revision history for this message
dino99 (9d9) wrote :

hi Christopher,

im copying back here what you have not seen into the report details:

dmi.bios.date: 07/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3002

the bios 3002 is the latest version for that mobo, and have been flashed 3 years back to support the q9550 proc. That said, the main issues have started with the kernel serie 3 when gnome3 have been also used (gnome2 was easier to set the hardware config; and xorg.conf was also able to deal with special settings for mouse for example, which now can conflict with the kernel hardware monitoring):

- the System Settings Mouse and/or dconf cant handle the mouse sensitivity: the single mouse click should work but doesn't, a second click is mostly needed each time
- selecting a words block is often a nightmare: sometimes it works, sometimes not after a while: like if a buffer was not refreshed or locked. This is irritating when you want to select then copy/paste a sentence ..... with writer or calc; or when you want to grab & drop cards when playing with aisleriot for example.

I have tested with a stock system (either precise/raring or now saucy i386) and/or with the gnome3-team ppa enabled: i cant see any difference. Also checked the different logs, but nothing usefull about that issue.
I know that the Logitech hardware is not the best supported, and affect a bunch of users seen across the forums; but there was no trouble before when using the 2.6 kernel & gnome2.
Some packages related to Logitech have also been tested but with no luck : locomo, libgii* ; maybe libgii-cibles should be added to the ubuntu archives.

Revision history for this message
dino99 (9d9) wrote :

Also note that the latest saucy kernel 3.11.0.1 have the same issue.

Revision history for this message
penalvch (penalvch) wrote :

dino99, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc4

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

tags: added: latest-bios-3002
removed: bios-outdated-3002
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
dino99 (9d9) wrote :

Have tested both 3.11-rc4 & rc5 and have got the same issues like with the ubuntu kernels.

tags: added: kernel-bug-exists-upstream-v3.11-rc5
removed: needs-upstream-testing
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

dino99, did this problem not occur in a release prior to Raring?

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
dino99 (9d9) wrote :

As reported on top, lp:1006145 #15 + give more details and trace back the history of that problem. Please refer to it.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

dino99, please don't make people dumpster dive through another report, just answer the question as asked for your hardware and personal experiences. Hence, did you personally experience this with your hardware on releases prior to Raring?

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
dino99 (9d9) wrote :

These issues are observed from 12.04 i386 with its stock kernel to 13.10 with the latest kernel upstream also.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
penalvch (penalvch)
tags: added: precise
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
dino99 (9d9) wrote :

That mouse was working fine prior to Precise; but i cant say if it was well identified (lx5 cordless optical) or not. What have changed then ? (hal dropped, maybe some way to detect hardware ids, some kernel support dropped ?) or actual kernels using some external outputs like dmidecode/lsusb ?

Revision history for this message
penalvch (penalvch) wrote :

dino99, which release specifically prior to Precise did it work in?

Revision history for this message
dino99 (9d9) wrote :

there was no such issue with the 3.2 kernel

tags: added: kernel-bug-exists-upstream-v3.16.0.18 utopic
removed: kernel-bug-exists-upstream-v3.11-rc5 latest-bios-3002 raring regression-potential saucy
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

dino99, please do not remove, nor change kernel tags when simply testing a new Ubuntu release. The default Ubuntu kernel is not an upstream kernel.

Despite this, this next step is to test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-rc6-utopic/ , and advise if this is reproducible.

tags: added: kernel-bug-exists-upstream-v3.11-rc5 latest-bios-3002 needs-upstream-testing raring regression-release saucy
removed: kernel-bug-exists-upstream kernel-bug-exists-upstream-v3.16.0.18
tags: added: needs-bisect
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
no longer affects: linux (Ubuntu)
affects: evdev → linux (Ubuntu)
Changed in linux (Ubuntu):
status: New → Incomplete
importance: Undecided → Medium
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.