After the latest kernel update, on the updates repository, I couldn’t loging into X, I was greeted by a console screen and a blinking cursor. Im sort of used to this by now, so I immediately switched to init 3, removed my old fglrx drivers and tried to use the old familiar sax2 to reconfigure my video settings to default options. I was very surprised when sax2 didn’t work, in fact it seems not to be installed, uh ??!!!
Anyways, I decided to restore an old xorg.conf backup, one before I installed the proprietary ati divers… That did the trick. I was able to log back into my desktop.
This is when I noticed my mouse wasn’t working properly. Specifically it would work just fine, but when left alone for 2-3 seconds it would simply become unresponsive and the lights would turn off. To reactivate it was necessary to press any button, then the lights would turn back on and I could move the pointer again. Is the mouse hibernating!!!
I though it was an xorg.conf misconfiguration but after downloading and installing the latest ati drivers and running aticonfig --initial the problem persists. I did take a look at my xorg.conf file and I didn’t notice any “Device Mouse ” sections, not in the new or any of the old xorg.conf backups I had.
Is this a kernel bug, or is there something.else broken in my system??
I have a standard USB optical mouse.
I have booted into debian, sidux and windows after that and the mouse works just fine.
Does anybody have any idea about what can be causing this??
where ? =the bus number and the 2nd ? = the device number of the affected hardware. TO see a list of all current usb devices simply use the lsusb command.
In my case:
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 002: ID 0c45:5308 Microdia
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
so I wrote:
echo -1 > /sys/bus/usb/devices/5-1/power/autosuspend
that fixed it instantly!!!
To avoid doing this every time you reboot is useful to create a start up script in kde/autostart folder
note that the device number is always one number less than the one listed. If I wrote:
echo -1 > /sys/bus/usb/devices/5-2/power/autosuspend
it would return an error.
So I wrote:
echo -1 > /sys/bus/usb/devices/5-1/power/autosuspend
that fixed it instantly!!!
To avoid doing this every time you reboot is useful to create a start up script in kde/autostart folder
Yep. It’s even better to write that command in /etc/rc.d/boot.local.
script vs. udev rule
[ul]
[li]The first hack : Keyboard & mouse freezes
[/li][LIST]
[li]works instantly
[/li][li]works automatically (it’s a script which does exactly what you did)
[/li][li]is enabled at the very end of the init process
[/li][li]stops working when using a kvm switch or unpluging a device
[/li][/ul]
[li]The second solution: Keyboard & mouse freezes
[/li][ul]
[li]requires a reboot
[/li][li]requires some work (find out and add the vendor and product IDs of your devices in the sample udev rule)
[/li][li]is enabled at the beginning of the boot process
[/li][li]always works
[/li][/ul]
the udev rule I put together is buggy but works (2 bugs cancelling each other). Read the following posts for a cleaner version.
[li] and last but not least the third solution: Keyboard & mouse freezes
[/li]recompiling the kernel !
[/LIST]