Bugzilla – Bug 147268
USB mouse is recognized at boot but not at hotplug
Last modified: 2007-06-05 10:30:59 UTC
When I boot whith USB Mouse pluged, the mouse works. When I plug the Mouse after Booting, or unplug and reconnect it, I get the following messages in /var/log/messages: Jan 26 21:52:54 berlin kernel: usb 2-2: USB disconnect, address 2 Jan 26 21:52:54 berlin resmgr[4970]: set_facl() - ACL error on /dev/input/event4, acl_set_file: No such file or directory Jan 26 21:53:17 berlin kernel: hub 1-0:1.0: Cannot enable port 2. Maybe the USB cable is bad? Jan 26 21:53:19 berlin kernel: hub 1-0:1.0: Cannot enable port 2. Maybe the USB cable is bad?
try ftp://ftp.suse.com/pub/projects/kernel/kotd/i386/HEAD/kernel-default.i586.rpm
(In reply to comment #1) > I tryed it > but this does not help: with kernel 2.6.16 it is the same problem as with 2.6.13
can you attach the full hwinfo output? Did it ever work?
Created attachment 66485 [details] hwinfo The requested hwinfo
(In reply to comment #3) > Did it ever work? Yes, It worked on SUSE 9.3 (2.6.11.4-21.10-default) but with some Problems. I often needed up to about four trys of pluggig and unpluggig till the mouse worked. On 10.0 in never workes. Here is a /var/log/messages from 9.3: Feb 5 22:17:29 Berlin kernel: usb 1-2: USB disconnect, address 2 Feb 5 22:17:39 Berlin kernel: hub 1-0:1.0: Cannot enable port 2. Maybe the USB cable is bad? Feb 5 22:17:42 Berlin kernel: hub 1-0:1.0: Cannot enable port 2. Maybe the USB cable is bad? Feb 5 22:17:43 Berlin kernel: usb 1-2: new low speed USB device using uhci_hcd and address 5 Feb 5 22:17:44 Berlin kernel: input: USB HID v1.10 Mouse [PS/2+USB Mouse] on us b-0000:00:1d.0-2 Feb 5 22:18:09 Berlin kernel: usb 1-2: USB disconnect, address 5 Feb 5 22:18:17 Berlin kernel: usb 1-2: new low speed USB device using uhci_hcd and address 6 Feb 5 22:18:18 Berlin kernel: input: USB HID v1.10 Mouse [PS/2+USB Mouse] on usb-0000:00:1d.0-2 As you can see: there is also the "USB cable bad" message. But On 9.3 it disapears. On 10.0 is floods me messages file.
can you boot the 10.0 kernel with the 'apic' kernel cmdline option? does that make any difference?
No difference when bootimg with 'apic' what does: "Jan 26 21:52:54 berlin resmgr[4970]: set_facl() - ACL error on /dev/input/event4, acl_set_file: No such file or directory" mean?
I think thats the missing device node, unrelated and already fixed in 10.1.
are you able to compile your own kernel and see when it broke? I tend to think its bad hardware or BIOS.
can you try again with a 10.2 beta?
No reaction on this bug for a long time. Closing as CANTFIX.
Closed.