Re: usb moused no longer starts

> From marcus at marcuscom.com wrote on Sat Mar 20 07:12:07 2004
>>> julian at elischer.org wrote on Sat Mar 20 06:08:47 2004
>>> there were small changes to usb_subr.c
>> > can you see what happens if you back that file back 2 days
> > Reverting back to 1.59 fixes the problem.
>
> To add to this, it looks like moused is started before the mouse
> attachment actually completes.  This is what I see when I unplug then
> plug back in my mouse:
>
> ums0: at uhub1 port 1 (addr 2) disconnected
> ums0: detached
> moused: unable to open /dev/ums0: No such file or directory
> ums0: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM), rev
> 1.10/3.00, addr 2, iclass 3/1
> ums0: 5 buttons and Z dir.

>From /var/log/console I see for 1.61:

Mar 19 23:03:26 k9 kernel: Fri Mar 19 23:03:26 EST 2004
Mar 19 23:05:47 k9 kernel: Mar 19 23:05:47 k9 moused: unable to open /dev/ums0: 
No such file or directory
Mar 19 23:14:27 k9 kernel: Mar 19 23:14:27 k9 moused: unable to open /dev/ums0: 
No such file or directory
Mar 19 23:19:29 k9 kernel: Mar 19 23:19:29 k9 moused: unable to open /dev/ums0: 
No such file or directory
Mar 19 23:29:51 k9 kernel: Mar 19 23:22:03 k9 moused: unable to open /dev/ums0: 
No such file or directory

>From /var/log/console for 1.59:

Mar 20 06:46:07 k9 kernel: Starting usbd.
Mar 20 06:46:08 k9 kernel: moused: 
Mar 20 06:46:08 k9 kernel: unable to open /dev/ums0: Device busy
Mar 20 06:46:08 k9 kernel: 
Mar 20 06:46:08 k9 kernel: usbd: '/usr/sbin/moused -p /dev/${DEVNAME} -m2=4 -I /var/run/moused.${DEVNAME}.pid' returned 1
Mar 20 06:46:08 k9 kernel: Starting local daemons:

And from /var/log/messages for 1.59:

Mar 20 06:46:07 k9 kernel: Mounting root from ufs:/dev/ad0s2a
Mar 20 06:46:07 k9 kernel: ums0: Logitech USB-PS/2 Mouse M-BA47, rev 1.00/1.20, addr 2, iclass 3/1
Mar 20 06:46:07 k9 kernel: ums0: 4 buttons and Z dir.

which from memory is what I normally see and mouse works correctly.

--
tonym