|cdce%d: no union descriptor||The driver could not fetch an interface descriptor from the USB device. For a manually added USB vendor/product, the CDCE_NO_UNION flag can be tried to work around the missing descriptor.|
| cdce%d: no data interface
cdce%d: could not read endpoint descriptor
cdce%d: unexpected endpoint
cdce%d: could not find data bulk in/out
|For a manually added USB vendor/product, these errors indicate that the bridge is not compatible with the driver.|
|cdce%d: watchdog timeout||A packet was queued for transmission and a transmit command was issued, however the device failed to acknowledge the transmission before a timeout expired.|
|cdce%d: no memory for rx list -- packet dropped!||Memory allocation through MGETHDR or MCLGET failed, the system is running low on mbufs.|
| cdce%d: abort/close rx/tx pipe failed
cdce%d: rx/tx list init failed
cdce%d: open rx/tx pipe failed
cdce%d: usb error on rx/tx
arp(4), intro(4), ipheth(4), netintro(4), urndis(4), usb(4), ifconfig(8)
.Rs Universal Serial Bus Class Definitions for Communication Devices
.Rs Data sheet Prolific PL-2501 Host-to-Host Bridge/Network Controller
The cdce device driver first appeared in
.Ox 3.6 ,
.Nx 3.0 and
.Fx 6.0 .
.An -nosplit The cdce driver was written by
.An Craig Boston Aq firstname.lastname@example.org based on the aue(4) driver written by
.An Bill Paul Aq email@example.com and ported to
.An Daniel Hartmeier Aq firstname.lastname@example.org .
Many USB devices notoriously fail to report their class and interfaces correctly. Undetected products might work flawlessly when their vendor and product IDs are added to the driver manually.