wifi is know to be stabler on 2.4

Quoting el8fr <[EMAIL PROTECTED]>:

> Hi,
>
> I'm having the same issued and like you I tested on 2.6.19... I really
> need wifi on my foxboard. Could someone recommend another usb stick ?
> Does someone has tested on 2.4.x kernel series ? (I prefer to ask
> before spending time for nothing).
>
> Regards.
>
>
> --- In [email protected], Marco Iora <[EMAIL PROTECTED]> wrote:
>>
>> I've done all these steps so I have a 2.6.19 kernel (sdk 2.10).
>> The problem continue to be the same, when some high rate data goes on
>> wireless the driver crashes.
>>
>> I've tried with rt73 official 1.0.4.0 drivers, and with the patched
>> ones from the subversion repository at acmesystems.
>>
>> The only difference with 2.6.15 (sdk 2.01) is the new kernel error
>> message ...
>> "crisv10_dma error: No urb for epid 31 in rx interrupt"
>>
>> I can't understand why there isn't the possibility to work with the
>> only wireless stick supported by acme...
>>
>> Please solve this early and let us know.
>> Best regards,
>> Marco Iora
>>
>> Il giorno 28/mag/07, alle ore 16:34, [EMAIL PROTECTED] ha scritto:
>>
>> > sure :-)
>> >
>> > you need to register on the axis developer site. then
>> > download sdk
>> > http://www.axis.com/products/dev_sdk/download.htm
>> >
>> > next you will need the spcax, wifi drivers, you can take
>> > them from the current sdk patch
>> > http://dev.acmesystems.it:8080/trac/browser/trunk/phrozen_patch/
>> > code/os/linux-2.6-tag--devboard-R2_01-1/drivers/usb/media
>> > http://dev.acmesystems.it:8080/trac/browser/trunk/phrozen_patch/
>> > code/os/linux-2.6-tag--devboard-R2_01-1/drivers/fox-normal/rt73usb
>> >
>> > you will need the wireless tools
>> > http://dev.acmesystems.it:8080/trac/browser/trunk/phrozen_patch/
>> > code/apps/wireless-tools
>> >
>> > finally setup the kernel to support the wireless driver
>> >
>> > john
>> >
>> >
>> > ----- Original Message -----
>> > From: [EMAIL PROTECTED]
>> > To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
>> > Subject: Re: FoxBoard and DWL G122 C1 problem
>> > Date: Mon, 28 May 2007 16:18:58 +0200 (CEST)
>> >
>> >> Great news!
>> >> Can you tell me more about the first option? Particularly
>> >> what version should I use to patch the wireless driver?
>> >>
>> >> Thanks,
>> >> Marco
>> >>
>> >>> Hi,
>> >>>
>> >>>
>> >>> yes this is a known problem
>> >>>
>> >>> you have 2 options,
>> >>> 1  update to the sdk2_10 from axis (and patch the
>> >>> wireless drivers yourself)
>> >>> 2  wait till i hav the new toolchain ready (which will
>> >>> take a few more weeks)
>> >>>
>> >>> unfortunatley the issue will not be resolved until we
>> >>> have 2.6.19
>> >>>
>> >>> John
>> >>>
>> >>>
>> >>> ----- Original Message -----
>> >>> From: [EMAIL PROTECTED]
>> >>> To: [EMAIL PROTECTED]
>> >>> Cc: [EMAIL PROTECTED]
>> >>> Subject: FoxBoard and DWL G122 C1 problem
>> >>> Date: Mon, 28 May 2007 16:06:54 +0200 (CEST)
>> >>>
>> >>>> Hi John,
>> >>>>     we are using a fox board for a robotic project at
>> >> our >> university.
>> >>>> Actually we need to stream webcam live captured data on
>> >> a >> wireless link. To do so we have modified vislib, an
>> >> open >> source v4l interface library developed by
>> >> MobileRobots, to >> send YUV captured data on a tcp
>> >> socket. All works great >> with our FoxBoard LX416 using
>> >> an ethernet link, but don't >> with the wireless adapter
>> >> (DWL G122 C1). >>
>> >>>> The interface rausb0 goes up without any problem, and
>> >> it >> get associated to the access point, but when we try
>> >> to >> send too much data through the wireless link it
>> >> crashes >> and a reboot is needed to get the interface up
>> >> again. >>
>> >>>> We think this behaviour is linked to usb bus matters,
>> >>>> perhaps some buffer get full and there is no control in
>> >>>> the driver to go around the problem?
>> >>>>
>> >>>> The only error message we get is this (from dmesg):
>> >>>> Jan  1 00:01:54 axis kernel: hc-crisv10 hc-crisv10.0:
>> >>>> Unlink after no-IRQ?  Controller is probably using the
>> >>>> wrong IRQ.
>> >>>>
>> >>>> To reproduce the problem you can do a remote "cat
>> >>>> /dev/zero" (by ssh for example) or transfer a big file
>> >>>> (4mb or so) using netcat, all wihout a ethernet cable
>> >>>> attached.
>> >>>>
>> >>>> We are using sdk revision 01, kernel 2.6.15.
>> >>>>
>> >>>> Thanks in advance.
>> >>>> Regards,
>> >>>> Marco Iora & Cristian Tosoni
>> >>>>
>> >>>
>> >>
>> >
>>
>
>
>



Reply via email to