On 4/30/09, Gustau Pérez <[email protected]> wrote: > >>> I think this is right place to post, if it is not, please let me know. >>> >> It is not usb fault, it is driver side fault. >> >> > Thank you. I thought it was not an usb fault, because with stable > (old usb stack) it shows the same behaviour. > > I posted here because I saw some posts this April related to rum and > because it was not current's fault. Perharps freebsd-net would be a > better place to post. > >> I use ndisgen(8) in such case(...), note that only CURRENT now have >> usb support for ndisulator. >> >> > Well, already tried (current csup'ed this week). No luck (no AP's > available, nothing), and removing the modules gave a nice panic :)
Please explain that in detail as much as possible and send bt from panic. On i386 ndisulator with usb works fine last time I tested it, I am aware of bugs on amd64 ... -- Paul _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "[email protected]"
