Mouse stopped working

Lo, I did an update yesterday and since then my mouse stopped working.

/var/log/messages contains:

Mar 22 08:17:50 inspiron9400 su: (to root) aliB on /dev/pts/1
Mar 22 08:18:15 inspiron9400 kernel:   822.704445] usb 3-1: USB disconnect, address 4
Mar 22 08:18:18 inspiron9400 kernel:   825.453136] usb 3-1: new low speed USB device using uhci_hcd and address 5
Mar 22 08:18:18 inspiron9400 kernel:   825.620195] usb 3-1: New USB device found, idVendor=046d, idProduct=c521
Mar 22 08:18:18 inspiron9400 kernel:   825.620216] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Mar 22 08:18:18 inspiron9400 kernel:   825.620230] usb 3-1: Product: USB Receiver
Mar 22 08:18:18 inspiron9400 kernel:   825.620240] usb 3-1: Manufacturer: Logitech
Mar 22 08:18:18 inspiron9400 kernel:   825.620454] usb 3-1: configuration #1 chosen from 1 choice
Mar 22 08:18:18 inspiron9400 kernel:   825.646457] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0/input/input15
Mar 22 08:18:18 inspiron9400 kernel:   825.646614] generic-usb 0003:046D:C521.0007: input,hidraw0: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:1d.1-1/input0
Mar 22 08:18:18 inspiron9400 kernel:   825.676240] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.1/input/input16
Mar 22 08:18:18 inspiron9400 kernel:   825.676424] generic-usb 0003:046D:C521.0008: input,hiddev0,hidraw1: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:1d.1-1/input1

Obviously the mouse is recognized but still does not work.
I hope somebody has a hint.

Mine quit too. Both the touch pad and usb.

I will be watching this thread with interest.

Hi

First of all… we need more information. What are the list of repositories you have listed?

My bet would be that the xorg repo is enabled and you updated your x config. The xorg repo is bleeding edge and currently it makes your input devices not usable. (I know because I did update it two days ago to get newer ati drivers and mesa.)

Anyway… can you supply your repo list as this makes the first step to see what could have gone wrong?

I did this too - for ati & mesa drivers. How did you come by this info, and is there any news on it being fixed?

this happens to me every time I do a kernel update. I solve it by uninstalling my video drivers and resintalling them again, then configuring it on init 3 with sax2.

If you don’t have propietary drivers installed just go to init 3, and run “sax2 -r -m 0=radeonHD” or 0=mesa or any other driver you use. Believe me this solves it.

It would be nice if it did, but no, it does not solve it at all. As far as I can tell it is the autodetecting of input devices (kbd, mouse etc) that is currently broken.

Getting SaX to generate an xorg.conf with the input devices predefined works around it but does not fix it.

Hi verstraete_kenny,
my repos are

Education
Libdvdcss
Packman
devel:languages:misc
devel:languages:perl
nvidia
home:mrdocs
openSuse 11.2-0
openSuse 11.2:Contrib
openSuse 11.2-Non-Oss
openSuse 11.2-Update

Ok, got the mouse working.

As suggested, I switched to runlevel 3 and run sax2 once again.
This works but it is not a solution to run sax2 after every kernel-update.

@all: Big thx, for your help!

> it is not a solution to run sax2 after every
> kernel-update.

if running sax2 is too much trouble then, don’t update the kernel…
no police to forces you to update…

i’m running 2.6.22.19-0.4


palladium

i don’t know if this is the same issue, but just in case it is helpful, here is my thread:
System crippled (no input) - openSUSE Forums

Hmmm … a couple of thoughts on this, … why is it not a solution? The mouse does NOT stop working for most of us. I have 6 PCs running openSUSE, 5 of which are running 11.2 and I NEVER have had such a problem. Not once. Never.

This problem of the mouse not working only affects a few people, in which case is NOT having such a tool to fix this not so common problem (relative to the MAJORITY of users) a good idea?

2nd , kernel updates do not happen every day. Maybe 1/2 dozen times during a distributions lifetime.

3rd, unfortunately, sax2 is being depreciated and no longer supported, so you will in a way get your wish as there will no longer be such a tool in the future. >:(

Bit of an update, if anyone finds it helpful.

Since xorg-driver-input went to being version 7.5* (it was 7.4*) I can get input without using an xorg.conf

However it still reckons the touchpad is a mouse & loads the mouse driver rather than the synaptics driver.

Edit, the version change to 7.5 might not have been what ‘fixed’ it, but it is the change that I noticed & actually checked by removing my xorg.conf file.