Date: Tue, 1 Jan 2002 12:41:55 +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: Re: Fw: Logitech iFeel Optical USB Mouse cannot be attached. Message-ID: <001101c1927e$a4e266c0$ae35dacb@joannaraman> References: <Pine.BSF.4.33.0112302122590.57927-100000@resnet.uoregon.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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. > > 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 messages 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 > userland and kernel? I had performed the upgrade on about Dec 23. Both userland and kernel is in sync. Cheers, Raman _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?001101c1927e$a4e266c0$ae35dacb>