Date: Thu, 30 Apr 2009 12:24:04 +0200 From: "Paul B. Mahol" <onemda@gmail.com> To: =?ISO-8859-1?Q?Gustau_P=E9rez?= <gperez@entel.upc.edu> Cc: freebsd-usb@freebsd.org Subject: Re: Signal sensitivity problem with if_rum Message-ID: <3a142e750904300324n11458adaic8e656694ae95f24@mail.gmail.com> In-Reply-To: <49F9799F.7090601@entel.upc.edu> References: <49F4B018.1000703@entel.upc.edu> <3a142e750904300256w4218f71bwfee97cdd1eb8252f@mail.gmail.com> <49F9799F.7090601@entel.upc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/30/09, Gustau P=E9rez <gperez@entel.upc.edu> 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 ... --=20 Paul
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3a142e750904300324n11458adaic8e656694ae95f24>