Date: Thu, 10 Jan 2002 07:57:09 +0800 From: "Raman Ng" <ramanng@yahoo.com> To: "Doug White" <dwhite@resnet.uoregon.edu> Cc: "Jon Parise" <jon@csh.rit.edu>, <stable@freebsd.org> Subject: (Resend) Re: Fw: Logitech iFeel Optical USB Mouse cannot be attached (file attached) Message-ID: <002b01c19969$5a6663c0$d13adacb@joannaraman>
next in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] > Odd. Well if it works :) > > Did you boot -v when you did this? Those uhci_* messages are kinda wacky. > Or did you compile with 'option USB_DEBUG'? Yes, I think it can help you all to solve the problem, I have also compile the kernel with UMS_DEBUG, UHCI_DEBUG and DIAGNOSTIC. > > > # usbdevs -v > > Controller /dev/usb0: > > addr 1: self powered, config 1, UHCI root hub(0x0000), VIA(0x0000), rev 0x0100 > > port 1 powered > > port 2 powered > > Controller /dev/usb1: > > addr 1: self powered, config 1, UHCI root hub(0x0000), VIA(0x0000), rev 0x0100 > > port 1 powered > > port 2 addr 2: self powered, config 1, product 0x9254(0x9254), Alcor Micro, Inc.(0x058f), rev 0x0100 > > > I'm guessing this is a hub. > > > port 1 powered > > port 2 addr 3: low speed, power 500 mA, config 1, iFeel Mouse(0xc030), Logitech, Inc.(0x046d), rev 0x0101 > > Well, there it is. According to your dmesg it is reporting as a HID > (Human Interface Device) so that's not it. > > Here's something to try.. > > 1. Do: > cd /dev > ./MAKEDEV usb usb0 uhid0 ums0 ulpt0 ugen0 usb1 > > This ensures the device nodes are in order. Done. > 2. Reboot. Don't plug the mouse in until the system has fully booted. > If that doesn't work, recompile your kernel with 'options UMS_DEBUG' then > try it again and paste any ums_attach messages you get. I can see only the following two messages for ums_attach, it is same as the one in dmesg. I have attached the file 'plug.txt' which contained all the essages shown when plug in the mouse. Dec 31 21:34:51 /kernel: device_probe_and_attach: ums0 attach returned 6 Dec 31 21:34:51 /kernel: device_probe_and_attach: ums0 attach returned 6 > I see only one place where the attach function can error without any > message and that's usbd_alloc_report_desc(). If the above didn't work, > I'd print the error code that that function is giving you. > > By the way, when you upgraded to 4.5-PRERELEASE, did you build both the userland and kernel? I had performed the upgrade on about Dec 23. Both userland and kernel is in sync. Cheers, Raman [-- Attachment #2 --] # Dec 31 21:34:36 /kernel: uhci_idone: error, addr=3, endpt=0x00, status 0x500000<BABBLE,STALLED> Dec 31 21:34:36 /kernel: uhci_idone: error, addr=3, endpt=0x00, status 0x500000<BABBLE,STALLED> Dec 31 21:34:41 /kernel: uhci_timeout: ii=0xc2c19840 Dec 31 21:34:41 /kernel: uhci_timeout: ii=0xc2c19840 Dec 31 21:34:41 /kernel: uhci_device_request: not done, ii=0xc2c19840 Dec 31 21:34:41 /kernel: uhci_device_request: not done, ii=0xc2c19840 Dec 31 21:34:46 /kernel: uhci_timeout: ii=0xc2c19840 Dec 31 21:34:46 /kernel: uhci_timeout: ii=0xc2c19840 Dec 31 21:34:46 /kernel: ums0: Logitech, Inc. iFeel Mouse, rev 1.00/1.01, addr 3, iclass 3/1 Dec 31 21:34:46 /kernel: ums0: Logitech, Inc. iFeel Mouse, rev 1.00/1.01, addr 3, iclass 3/1 Dec 31 21:34:46 /kernel: uhci_device_request: not done, ii=0xc2c19840 Dec 31 21:34:46 /kernel: uhci_device_request: not done, ii=0xc2c19840 Dec 31 21:34:51 /kernel: uhci_timeout: ii=0xc2c19840 Dec 31 21:34:51 /kernel: uhci_timeout: ii=0xc2c19840 Dec 31 21:34:51 /kernel: device_probe_and_attach: ums0 attach returned 6 Dec 31 21:34:51 /kernel: device_probe_and_attach: ums0 attach returned 6 Dec 31 21:34:51 /kernel: uhci_device_request: not done, ii=0xc2c19840 Dec 31 21:34:51 /kernel: uhci_device_request: not done, ii=0xc2c19840 Dec 31 21:34:56 /kernel: uhci_timeout: ii=0xc2c19840 Dec 31 21:34:56 /kernel: uhci_timeout: ii=0xc2c19840 Dec 31 21:34:56 /kernel: uhci_device_request: not done, ii=0xc2c19840 Dec 31 21:34:56 /kernel: uhci_device_request: not done, ii=0xc2c19840 Dec 31 21:35:01 /kernel: uhci_timeout: ii=0xc2c19840 Dec 31 21:35:01 /kernel: uhci_timeout: ii=0xc2c19840 Dec 31 21:35:06 /kernel: uhci_timeout: ii=0xc104f680 Dec 31 21:35:06 /kernel: uhci_timeout: ii=0xc104f680 Dec 31 21:35:06 /kernel: uhci_device_request: not done, ii=0xc104f680 Dec 31 21:35:06 /kernel: uhci_device_request: not done, ii=0xc104f680 Dec 31 21:35:11 /kernel: uhci_timeout: ii=0xc104f680 Dec 31 21:35:11 /kernel: uhci_timeout: ii=0xc104f680 Dec 31 21:35:11 /kernel: uhci_device_request: not done, ii=0xc104f680 Dec 31 21:35:11 /kernel: uhci_device_request: not done, ii=0xc104f680 Dec 31 21:35:16 /kernel: uhci_timeout: ii=0xc104f680 Dec 31 21:35:16 /kernel: uhci_timeout: ii=0xc104f680 Dec 31 21:35:16 /kernel: uhci_device_request: not done, ii=0xc104f680 Dec 31 21:35:16 /kernel: uhci_device_request: not done, ii=0xc104f680 Dec 31 21:35:21 /kernel: uhci_timeout: ii=0xc104f680 Dec 31 21:35:21 /kernel: uhci_timeout: ii=0xc104f680 Dec 31 21:35:21 /kernel: uhci_device_request: not done, ii=0xc104f680 Dec 31 21:35:21 /kernel: uhci_device_request: not done, ii=0xc104f680 Dec 31 21:35:26 /kernel: uhci_timeout: ii=0xc104f680 Dec 31 21:35:26 /kernel: uhci_timeout: ii=0xc104f680 Dec 31 21:35:26 /kernel: uhci_device_request: not done, ii=0xc104f680 Dec 31 21:35:26 /kernel: uhci_device_request: not done, ii=0xc104f680 Dec 31 21:35:31 /kernel: uhci_timeout: ii=0xc104f680 Dec 31 21:35:31 /kernel: uhci_timeout: ii=0xc104f680
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?002b01c19969$5a6663c0$d13adacb>