Linux wireless networking development ()

Mark Wallis | 30 Jan 23:24

Getting dscape running

Hi Jon,

> I have NetworkManager from CVS and the current version of
> wpa_supplicant running. Hardware is a rt2570 dongle using the dscape
> stack. OS is Ubuntu.

Have you confirmed you are able to connect using iwconfig manually instead 
of Network Manager ? Are you able to get associated ? 

I assume you are using the rt2500usb.ko driver, but can you confirm 
you are using a recent CVS tarball ?

Regards,
Mark Wallis
rt2x00 Project Admin
mwallis at serialmonkey.com

headers

Jon Smirl | 30 Jan 23:41

Getting dscape running

On 1/30/07, Mark Wallis <mwallis at serialmonkey.com> wrote:
> Hi Jon,
>
> > I have NetworkManager from CVS and the current version of
> > wpa_supplicant running. Hardware is a rt2570 dongle using the dscape
> > stack. OS is Ubuntu.
>
> Have you confirmed you are able to connect using iwconfig manually instead
> of Network Manager ? Are you able to get associated ?

check out my other post
>
> I assume you are using the rt2500usb.ko driver, but can you confirm
> you are using a recent CVS tarball ?

I'm using rt2500usb from the wireless-dev tree.
I'll pull from CVS and try your most recent code.

This is part of what makes working on wireless hard, the pieces are
scattered everywhere.

>
>
> Regards,
> Mark Wallis
> rt2x00 Project Admin
> mwallis at serialmonkey.com
>
>
>

(Continue reading)

headers

Mark Wallis | 31 Jan 00:01

Getting dscape running

> check out my other post

It would be helpful if you could provide a debug trace as well.

> This is part of what makes working on wireless hard, the pieces are
> scattered everywhere.

Probably best to move this discussion to rt2400-devel and let us check
if the problem still exists in our latest CVS. From there, if assoc
is working fine you can bounce over to the NetworkManager list and go
from there.

Regards,
Mark Wallis
rt2x00 Project Admin
mwallis at serialmonkey.com

headers

Jon Smirl | 31 Jan 00:48

Getting dscape running

On 1/30/07, Mark Wallis <mwallis at serialmonkey.com> wrote:
> > check out my other post
>
> It would be helpful if you could provide a debug trace as well.
>
> > This is part of what makes working on wireless hard, the pieces are
> > scattered everywhere.
>
> Probably best to move this discussion to rt2400-devel and let us check
> if the problem still exists in our latest CVS. From there, if assoc
> is working fine you can bounce over to the NetworkManager list and go
> from there.

ralink CVS won't build with the current wireless-dev tree.
It tool a little while to check since I had to rebuild my kernel and
turn debugfs on.
I'll try Pavel's suggestions next.

jonsmirl at jonsmirl:/extra/ralink/rt2x00$ make
  CC [M]  /extra/ralink/rt2x00/ieee80211/ieee80211.o
In file included from /extra/ralink/rt2x00/ieee80211/ieee80211.c:13:
include/linux/netdevice.h:406: error: duplicate member 'ax25_ptr'
/extra/ralink/rt2x00/ieee80211/ieee80211.c: In function 'ieee80211_tx_h_rts':
/extra/ralink/rt2x00/ieee80211/ieee80211.c:858: error:
'IEEE80211_HW_SOFTWARE_RTS' undeclared (first use in this function)
/extra/ralink/rt2x00/ieee80211/ieee80211.c:858: error: (Each
undeclared identifier is reported only once
/extra/ralink/rt2x00/ieee80211/ieee80211.c:858: error: for each
function it appears in.)
/extra/ralink/rt2x00/ieee80211/ieee80211.c: In function

(Continue reading)