usb/106070: devd recognizes ucom, but ttyU is the device actually

Kay Abendroth kay.abendroth at
Thu Nov 30 07:41:11 PST 2006

>Number:         106070
>Category:       usb
>Synopsis:       devd recognizes ucom, but ttyU is the device actually
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-usb
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Nov 30 15:40:12 GMT 2006
>Originator:     Kay Abendroth
>Release:        6.2
FreeBSD halo 6.2-RC1 FreeBSD 6.2-RC1 #0: Thu Nov 16 22:50:15 CET 2006     root at halo:/usr/obj/usr/src/sys/HALO  i386
I was trying to sync my (USB) Palm Zire with FreeBSD, but had problems doing so. devd creates a ttyU[0-9]+ and cuaU[0-9]+ device but devd.conf-settings only work with devicename ucom[0-9]+, because devd's recognizing only ucom[0-9]+.

This should - at least - be mentioned elsewhere (man page of devd devd.conf) or changed to be more consistent with the real device-name(s).
1.) Add the following to your devd.conf:

attach 0 {
        device-name "ttyU[0-9]+";
        action "ln -s /dev/$device-name /dev/pilot";

2.) Start devd.
3.) HotSync your USB-Palm. No link will be created.

4.) Change your entry in devd.conf to the following instead:

attach 0 {
        device-name "ucom[0-9]+";
        action "ln -s /dev/ttyU0 /dev/pilot";

5.) Now everything works fine.


More information about the freebsd-usb mailing list