http://qa.mandrakesoft.com/show_bug.cgi?id=2248
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |WORKSFORME
------- Additional Comments From [EMAIL PROTECTED] 2003-03-13 22:31 -------
Looks OK for now. If I see it again, I'll reopen.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: RESOLVED
creation_date:
description:
During installation, the USB mouse was OK. So it was after the first couple of
reboots. But then, it stopped working - it seems like the USB subsystem did not
initialize properly. USBview shows nothing and says "cannot open
/proc/bus/usb/devices".
The following is taken from the output of dmesg:
---------------
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
PCI: Enabling device 02:07.0 (0000 -> 0002)
PCI: Setting latency timer of device 02:07.0 to 64
usb-ohci.c: USB OHCI at membase 0xe49f8000, IRQ 19
usb-ohci.c: usb-02:07.0, OPTi Inc. 82C861
usb-ohci.c: USB HC TakeOver failed!
Trying to vfree() nonexistent vm area (e49f8000)
PCI: Enabling device 02:07.1 (0000 -> 0002)
PCI: Setting latency timer of device 02:07.1 to 64
usb-ohci.c: USB OHCI at membase 0xe49f8000, IRQ 16
usb-ohci.c: usb-02:07.1, OPTi Inc. 82C861 (#2)
usb-ohci.c: USB HC TakeOver failed!
Trying to vfree() nonexistent vm area (e49f8000)
usb.c: deregistering driver usbdevfs
usb.c: deregistering driver hub
---------------
