FWIW, see the thread round about:

http://mail-index.netbsd.org/current-users/2002/06/05/0008.html
http://mail-index.netbsd.org/current-users/2002/06/12/0006.html

I don't know if things have gotten better since then...

On 2/12/03 1:15 PM, "Ed Gould" <ed@left.wing.org> wrote:

> I have a Diamond USB modem that gets attached as a ugen device,
> not as a umodem (both with the 1.5.2 kernel I'm running and with
> -current as of the most recent snapshot).  Is getting this device
> recognized as a umodem just a matter of adding the right information
> to some table somewhere, or is it really a usb-connected winmodem
> or some other such ugliness?
> 
> The related dmesg entries are:
> 
> uhci0 at pci0 dev 7 function 2: Intel 82371SB USB Host Controller (PIIX3)
> (rev. 0x01)
> uhci0: interrupting at irq 10
> usb0 at uhci0: USB revision 1.0
> uhub0 at usb0
> uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
> uhub0: 2 ports with 2 removable, self powered
> ugen0 at uhub0 port 1
> ugen0: Diamond Multimedia Systems Inc Diamond SupraMax 56K USB Modem, rev
> 1.00/0.01, addr 2
> 
> Thanks.
> 
> --Ed
> 
> 
>