uvisor not creating ucom0

Alexandre "Sunny" Kovalenko Alex.Kovalenko at verizon.net
Fri Oct 15 19:30:08 PDT 2004

On Fri, 2004-10-15 at 22:15, Kent Hauser wrote:
> Hi,
> I'm having a problem getting -CURRENT to talk to my new USB palm (actually a 
> couple years old palm model).
> Without uvisor loaded, usbd reports it sees my palm & creates ugen0, ugen0.1, 
> and ugen0.2 entries in /dev. With uvisor loaded, no entries are reported.
> With uvisor loaded, I get the following output from usbd:
> ****
> usbd: driver-attach event cookie=3217024892 devname=ucom0
> usbd: device-attach event at 1097892732.945264000, Palm Handheld, Palm, Inc.:
>   vndr=0x0830 prdct=0x0001 rlse=0x0100 clss=0x0000 subclss=0x0000 prtcl=0x0000
>   device names: ucom0
> usbd: Found action 'USB device' for Palm Handheld, Palm, Inc. at ucom0
> ****
> ucom0 is mentioned, but no dev entry is created.
> I tried applying the patch from Axel Gonzales (8 Sep 04) for CLIE TH55 usb 
> syncing with no effect.
> Any thoughts?
> Thanks. Kent
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"

If you are running current, you should get /dev/cuaU0 and /dev/ttyU0
instead of /dev/ucom0. Do you?

I, personally, do not have much luck with using USB interface on my
CLIE, but ports are created ;)

Alexandre "Sunny" Kovalenko.

More information about the freebsd-current mailing list