Re: Logitech iFeel Optical USB Mouse cannot be attached.
> > > >I have found that the iFeel Mouse does indeed work with an OHCI controller >but not with a UHCI controller. I have only got one mainbord with an OHCI >controller so I cannot generalise this. > >Jos > The iFeel being talked about here is the 0x46d(Logitech) 0xc032(iFeel ...)? I've been playing with this mouse for a while and I've found that it doesn't work with two of the VIA south-bridges which i've owned. Does work with a Genuine Intel southbridge(IBM laptop). and does work with a generic OHCI controller. Troy To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Logitech iFeel Optical USB Mouse cannot be attached.
On Thu, Apr 04, 2002 at 01:51:27AM +0100, Andrew Boothman wrote: > Ian Logan wrote: > > I've got an iFeel at home, plugged directly into the machine. Gives the > > exact same error. At one point last summer I started trying to look into > > it, and from what I saw in the code and what I remember it looked like > > some sort of timeout was happening while trying to talk to the mouse. > > I'll see if I can find my notes on it, or reproduce it. > > Maybe that will help someone smarter than me figure it out, if not > > sorry for the "me too". > > Sorry for this second generation "me too", but I have an iFeel Mouseman > which works completely perfectly here. > > It plugs directly into an AMD-756 OHCI USB Controller Root Hub. I have found that the iFeel Mouse does indeed work with an OHCI controller but not with a UHCI controller. I have only got one mainbord with an OHCI controller so I cannot generalise this. Jos -- Jos Vissers Veldsestraat 5 6617 AA Bergharen The Netherlands +31 487 531 521 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Logitech iFeel Optical USB Mouse cannot be attached.
Ian Logan wrote: > Hello all, > I've got an iFeel at home, plugged directly into the machine. Gives the > exact same error. At one point last summer I started trying to look into > it, and from what I saw in the code and what I remember it looked like > some sort of timeout was happening while trying to talk to the mouse. > I'll see if I can find my notes on it, or reproduce it. > Maybe that will help someone smarter than me figure it out, if not > sorry for the "me too". Sorry for this second generation "me too", but I have an iFeel Mouseman which works completely perfectly here. It plugs directly into an AMD-756 OHCI USB Controller Root Hub. Andrew. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Logitech iFeel Optical USB Mouse cannot be attached.
Actually I did try using a USB/PS2 adapter once. It doesnt really work. I believe the PS/2 port wasnt supplying enough power to the mouse :-( You could see the mouse power-up but as soon as you tried to do anything with it it would lose power. And if I remember right, the machine locked up (but that could just be my imagination). Ian On Wed, Apr 03, 2002 at 01:02:54PM -0500, Scott Christopher Dodson wrote: > > If it helps any, the optical logitech wheel mouse I have works without a > hitch. I've got mind connected via USB, but have you tried using the > USB/PS2 adapter as a temporary fix? > > -- > scott > > > On Wed, 3 Apr 2002, Ian Logan wrote: > > > Hello all, > > I've got an iFeel at home, plugged directly into the machine. Gives the > > exact same error. At one point last summer I started trying to look into > > it, and from what I saw in the code and what I remember it looked like > > some sort of timeout was happening while trying to talk to the mouse. > > I'll see if I can find my notes on it, or reproduce it. > > Maybe that will help someone smarter than me figure it out, if not > > sorry for the "me too". > > Ian > > > > On Wed, Apr 03, 2002 at 12:55:54PM +0200, Nick Hibma wrote: > > > > > > This looks like an electrical problem. What happens if you connect the > > > mouse directly to the machine, without any hubs? > > > > > > Nick > > > > > > > > > > -- > > Ian Logan > > Computing & Networking > > New Mexico State University > > Email: [EMAIL PROTECTED] Phone: 505-646-6034 Fax: 505-646-4560 > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-stable" in the body of the message > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message -- Ian Logan Computing & Networking New Mexico State University Email: [EMAIL PROTECTED] Phone: 505-646-6034 Fax: 505-646-4560 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Logitech iFeel Optical USB Mouse cannot be attached.
If it helps any, the optical logitech wheel mouse I have works without a hitch. I've got mind connected via USB, but have you tried using the USB/PS2 adapter as a temporary fix? -- scott On Wed, 3 Apr 2002, Ian Logan wrote: > Hello all, > I've got an iFeel at home, plugged directly into the machine. Gives the > exact same error. At one point last summer I started trying to look into > it, and from what I saw in the code and what I remember it looked like > some sort of timeout was happening while trying to talk to the mouse. > I'll see if I can find my notes on it, or reproduce it. > Maybe that will help someone smarter than me figure it out, if not > sorry for the "me too". > Ian > > On Wed, Apr 03, 2002 at 12:55:54PM +0200, Nick Hibma wrote: > > > > This looks like an electrical problem. What happens if you connect the > > mouse directly to the machine, without any hubs? > > > > Nick > > > > > > -- > Ian Logan > Computing & Networking > New Mexico State University > Email: [EMAIL PROTECTED] Phone: 505-646-6034 Fax: 505-646-4560 > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Logitech iFeel Optical USB Mouse cannot be attached.
Hello all, I've got an iFeel at home, plugged directly into the machine. Gives the exact same error. At one point last summer I started trying to look into it, and from what I saw in the code and what I remember it looked like some sort of timeout was happening while trying to talk to the mouse. I'll see if I can find my notes on it, or reproduce it. Maybe that will help someone smarter than me figure it out, if not sorry for the "me too". Ian On Wed, Apr 03, 2002 at 12:55:54PM +0200, Nick Hibma wrote: > > This looks like an electrical problem. What happens if you connect the > mouse directly to the machine, without any hubs? > > Nick > > -- Ian Logan Computing & Networking New Mexico State University Email: [EMAIL PROTECTED] Phone: 505-646-6034 Fax: 505-646-4560 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Logitech iFeel Optical USB Mouse cannot be attached.
This looks like an electrical problem. What happens if you connect the mouse directly to the machine, without any hubs? Nick On Sun, 23 Dec 2001, Raman Ng wrote: > Hello all, > > I have already sent a mail about this problem before. > I am a newbie of > FreeBSD. This time I attached the dmesg output and > kernel configuration for > you all. > > I am using Asus A7V mb, Athlon 1.1 GHz CPU, 512 Mb > RAM. Whenever the kernel > boot up, the message device_probe_and_attach: ums0 > attach returned 6. > Details can refer to the attached detail.. This > problem is similar to PR > misc/30373 and there is no one handle it at all. I > have tried FreeBSD 4.4-RELEASE, 4.5-PRERELEASE and > 5.0-CURRENT (which is cvsup a month ago) and the > problem is still persisted. > > I can use this mouse without any problem with Windows > and Linux. Please give > me any clue if I can solve this problem. > > Thanks in advance. > > Regards, > Raman > > --- dmesg output --- > Copyright (c) 1992-2001 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, > 1991, 1992, 1993, 1994 > The Regents of the University of California. > All rights reserved. > FreeBSD 4.5-PRERELEASE #0: Sun Dec 23 01:55:47 HKT > 2001 > root@:/usr/obj/usr/src/sys/STABLE_DEBUG > Timecounter "i8254" frequency 1193182 Hz > CPU: AMD Athlon(tm) Processor (1109.89-MHz 686-class > CPU) > Origin = "AuthenticAMD" Id = 0x642 Stepping = 2 > > >Features=0x183f9ff > AMD Features=0xc044<,AMIE,DSP,3DNow!> > real memory = 536788992 (524208K bytes) > avail memory = 518246400 (506100K bytes) > Preloaded elf kernel "kernel" at 0xc0389000. > Pentium Pro MTRR support enabled > md0: Malloc disk > Using $PIR table, 9 entries at 0xc00f1750 > npx0: on motherboard > npx0: INT 16 interface > pcib0: on motherboard > pci0: on pcib0 > pcib1: > at device 1.0 on pci0 > pci1: on pcib1 > pci1: at 0.0 > irq 11 > isab0: at device 4.0 on > pci0 > isa0: on isab0 > atapci0: port > 0xd800-0xd80f at device 4.1 on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > uhci0: port 0xd400-0xd41f > irq 9 at device 4.2 on pci0 > uhci0: LegSup = 0x003b > uhci_run: setting run=0 > uhci_run: done cmd=0x80 sts=0x20 > uhci_run: setting run=1 > uhci_run: done cmd=0x81 sts=0x0 > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, > addr 1 > uhub0: 2 ports with 2 removable, self powered > uhci1: port 0xd000-0xd01f > irq 9 at device 4.3 on pci0 > uhci1: LegSup = 0x0010 > uhci_run: setting run=0 > uhci_run: done cmd=0x80 sts=0x20 > uhci_run: setting run=1 > uhci_run: done cmd=0x81 sts=0x0 > usb1: on uhci1 > usb1: USB revision 1.0 > uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, > addr 1 > uhub1: 2 ports with 2 removable, self powered > uhci_device_request: not done, ii=0xc104f680 > uhub2: ALCOR Generic USB Hub, class 9/0, rev > 1.10/1.00, addr 2 > uhub2: 4 ports with 4 removable, self powered > uhci_device_intr_transfer: not done, ii=0xc104f620 > uhci_waitintr: timeout > uhci_idone: error, addr=3, endpt=0x00, status > 0x50 > uhci_waitintr: timeout > usbd_transfer_cb: short transfer 0<1 > uhci_waitintr: timeout > usbd_transfer_cb: short transfer 0<1 > ums0: Logitech, Inc. iFeel Mouse, rev 1.00/1.01, addr > 3, iclass 3/1 > uhci_waitintr: timeout > usbd_transfer_cb: short transfer 0<74 > device_probe_and_attach: ums0 attach returned 6 > uhci_waitintr: timeout > usbd_transfer_cb: short transfer 0<1 > uhci_waitintr: timeout > usbd_transfer_cb: short transfer 0<1 > uhci_waitintr: timeout > usbd_transfer_cb: short transfer 0<4 > uhci_waitintr: timeout > usbd_transfer_cb: short transfer 0<4 > chip1: at device 4.4 on > pci0 > rl0: port 0xa400-0xa4ff > mem 0xd580-0xd58000ff irq 9 at device 9.0 on pci0 > rl0: Ethernet address: 00:50:ff:60:0b:b8 > miibus0: on rl0 > rlphy0: on miibus0 > rlphy0: 10baseT, 10baseT-FDX, 100baseTX, > 100baseTX-FDX, auto > pcm0: port 0xa000-0xa01f irq 5 at > device 10.0 on pci0 > pci0: (vendor=0x104c, dev=0x8020) at > 13.0 irq 9 > atapci1: port > 0x8000-0x803f,0x8400-0x8403,0x8800-0x8807,0x9000-0x9003,0x9400-0x9407 > mem 0xd400-0xd401 irq 10 at device 17.0 > on pci0 > ata2: at 0x9400 on atapci1 > ata3: at 0x8800 on atapci1 > orm0: at iomem > 0xc-0xcbfff,0xcc000-0xc,0xd-0xd27ff on > isa0 > fdc0: at port 0x3f0-0x3f5,0x3f7 > irq 6 drq 2 on isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > atkbdc0: at port > 0x60,0x64 on isa0 > atkbd0: flags 0x1 irq 1 on atkbdc0 > kbd0 at atkbd0 > psm0: irq 12 on atkbdc0 > psm0: model IntelliMouse, device ID 3 > vga0: at port 0x3c0-0x3df iomem > 0xa-0xb on isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > ppc0: at port 0x378-0x37f irq 7 on > isa0 > ppc0: SMC-like chipset (ECP/EPP/
Re: Logitech iFeel Optical USB Mouse cannot be attached.
> > The following is the output of usbdevs -v > > > > # usbdevs -v > > Controller /dev/usb0: > > addr 1: self powered, config 1, UHCI root hub(0x), VIA(0x), rev > > 0x0100 > > port 1 powered > > port 2 powered > > This is with the "mouse" attached? > > If it doesn't even show up, that would point towards faulty hardware... > The mouse has already attached when execute usbdevs and I can use this mouse in both Windows and Linux without any problem. With reference with the dmesg output attached, I guess the mouse is attached in usb1 but I cannot confirm if it is true since I am only a newbie. However, the usbdevs only list /dev/usb0 but no usb1. I found there is no device usb1 in /dev so I tried to create the device node usb1 but usbdevs still only list /dev/usb0 but no usb1. Regards, Raman Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.5-PRERELEASE #0: Sun Dec 23 01:55:47 HKT 2001 root@:/usr/obj/usr/src/sys/STABLE_DEBUG Timecounter "i8254" frequency 1193182 Hz CPU: AMD Athlon(tm) Processor (1109.89-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x642 Stepping = 2 Features=0x183f9ff AMD Features=0xc044<,AMIE,DSP,3DNow!> real memory = 536788992 (524208K bytes) avail memory = 518246400 (506100K bytes) Preloaded elf kernel "kernel" at 0xc0389000. Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 9 entries at 0xc00f1750 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 irq 11 isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xd800-0xd80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xd400-0xd41f irq 9 at device 4.2 on pci0 uhci0: LegSup = 0x003b uhci_run: setting run=0 uhci_run: done cmd=0x80 sts=0x20 uhci_run: setting run=1 uhci_run: done cmd=0x81 sts=0x0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xd000-0xd01f irq 9 at device 4.3 on pci0 uhci1: LegSup = 0x0010 uhci_run: setting run=0 uhci_run: done cmd=0x80 sts=0x20 uhci_run: setting run=1 uhci_run: done cmd=0x81 sts=0x0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci_device_request: not done, ii=0xc104f680 uhub2: ALCOR Generic USB Hub, class 9/0, rev 1.10/1.00, addr 2 uhub2: 4 ports with 4 removable, self powered uhci_device_intr_transfer: not done, ii=0xc104f620 uhci_waitintr: timeout uhci_idone: error, addr=3, endpt=0x00, status 0x50 uhci_waitintr: timeout usbd_transfer_cb: short transfer 0<1 uhci_waitintr: timeout usbd_transfer_cb: short transfer 0<1 ums0: Logitech, Inc. iFeel Mouse, rev 1.00/1.01, addr 3, iclass 3/1 uhci_waitintr: timeout usbd_transfer_cb: short transfer 0<74 device_probe_and_attach: ums0 attach returned 6 uhci_waitintr: timeout usbd_transfer_cb: short transfer 0<1 uhci_waitintr: timeout usbd_transfer_cb: short transfer 0<1 uhci_waitintr: timeout usbd_transfer_cb: short transfer 0<4 uhci_waitintr: timeout usbd_transfer_cb: short transfer 0<4 chip1: at device 4.4 on pci0 rl0: port 0xa400-0xa4ff mem 0xd580-0xd58000ff irq 9 at device 9.0 on pci0 rl0: Ethernet address: 00:50:ff:60:0b:b8 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pcm0: port 0xa000-0xa01f irq 5 at device 10.0 on pci0 pci0: (vendor=0x104c, dev=0x8020) at 13.0 irq 9 atapci1: port 0x8000-0x803f,0x8400-0x8403,0x8800-0x8807,0x9000-0x9003,0x9400-0x9407 mem 0xd400-0xd401 irq 10 at device 17.0 on pci0 ata2: at 0x9400 on atapci1 ata3: at 0x8800 on atapci1 orm0: at iomem 0xc-0xcbfff,0xcc000-0xc,0xd-0xd27ff on isa0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 plip0: on ppbus0 ad4: 43979MB [89355/16/63] at ata2-master UDMA100 ad6: 57241MB [116301/16/63] at ata3-master UDMA100 acd0: DVD-ROM at ata0-master using PIO4 acd1: CD-RW at ata1-master using PIO4 Mounting root from ufs:/dev/ad4s2a
Re: Logitech iFeel Optical USB Mouse cannot be attached.
On Mon, 24 Dec 2001, Raman Ng wrote: > The following is the output of usbdevs -v > > # usbdevs -v > Controller /dev/usb0: > addr 1: self powered, config 1, UHCI root hub(0x), VIA(0x), rev > 0x0100 > port 1 powered > port 2 powered This is with the "mouse" attached? If it doesn't even show up, that would point towards faulty hardware... Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Logitech iFeel Optical USB Mouse cannot be attached.
Doug White wrote: > > Dropping -stable crosspost. > > For those of you with this mouse -- we really need the output of 'usbdevs > -v' with the mouse attached. > > I'm betting that this isn't a standard USB mouse and requires a special, > proprietary driver. :( The very idea of a "winmouse" gives me the heebee-jeebees... -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Logitech iFeel Optical USB Mouse cannot be attached.
The following is the output of usbdevs -v # usbdevs -v Controller /dev/usb0: addr 1: self powered, config 1, UHCI root hub(0x), VIA(0x), rev 0x0100 port 1 powered port 2 powered Regards, Raman - Original Message - From: "Doug White" <[EMAIL PROTECTED]> To: "Jon Parise" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Monday, December 24, 2001 2:24 AM Subject: Re: Logitech iFeel Optical USB Mouse cannot be attached. > Dropping -stable crosspost. > > For those of you with this mouse -- we really need the output of 'usbdevs > -v' with the mouse attached. > > I'm betting that this isn't a standard USB mouse and requires a special, > proprietary driver. :( > > Doug White| FreeBSD: The Power to Serve > [EMAIL PROTECTED] | www.FreeBSD.org _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Logitech iFeel Optical USB Mouse cannot be attached.
Dropping -stable crosspost. For those of you with this mouse -- we really need the output of 'usbdevs -v' with the mouse attached. I'm betting that this isn't a standard USB mouse and requires a special, proprietary driver. :( Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Logitech iFeel Optical USB Mouse cannot be attached.
On Sun, Dec 23, 2001 at 04:43:55AM -0800, Raman Ng wrote: > I am using Asus A7V mb, Athlon 1.1 GHz CPU, 512 Mb > RAM. Whenever the kernel > boot up, the message device_probe_and_attach: ums0 > attach returned 6. > Details can refer to the attached detail.. This > problem is similar to PR > misc/30373 and there is no one handle it at all. I > have tried FreeBSD 4.4-RELEASE, 4.5-PRERELEASE and > 5.0-CURRENT (which is cvsup a month ago) and the > problem is still persisted. http://www.freebsd.org/cgi/query-pr.cgi?pr=misc/30373 -- Jon Parise ([EMAIL PROTECTED]) . Information Technology (2001) http://www.csh.rit.edu/~jon/ : Computer Science House Member To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
