-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steven Friedrich wrote:
> [EMAIL PROTECTED] wrote:
Doing a descriptor dump, and posting the results to freebsd-usb@,
might find someone who knows how to get that particular device to
work.
>>> Ok, I'll bite. How do you do a descrip
[EMAIL PROTECTED] wrote:
Doing a descriptor dump, and posting the results to freebsd-usb@,
might find someone who knows how to get that particular device to
work.
Ok, I'll bite. How do you do a descriptor dump?
One way is to use sysutils/udesc_dump, from ports, as recommended here:
http://li
> > Doing a descriptor dump, and posting the results to freebsd-usb@,
> > might find someone who knows how to get that particular device to
> > work.
> >
> Ok, I'll bite. How do you do a descriptor dump?
One way is to use sysutils/udesc_dump, from ports, as recommended here:
http://lists.freebsd
[EMAIL PROTECTED] wrote:
I checked the FreeBSD 7.0-RELEASE Hardware Notes before I bought
this USB Ethernet device.
It should be supported by the rum driver, but it gets picked up
by ugen instead.
The Hardware Notes mentions version 3 and the box says ver 4000,
but I think it's probably actually
> I checked the FreeBSD 7.0-RELEASE Hardware Notes before I bought
> this USB Ethernet device.
> It should be supported by the rum driver, but it gets picked up
> by ugen instead.
> The Hardware Notes mentions version 3 and the box says ver 4000,
> but I think it's probably actually ver 4.
...
> Wh
I checked the FreeBSD 7.0-RELEASE Hardware Notes before I bought this
USB Ethernet device.
It should be supported by the rum driver, but it gets picked up by ugen
instead.
The Hardware Notes mentions version 3 and the box says ver 4000, but I
think it's probably actually ver 4.
I configure
