headers
Rich B | 1 Nov 2003 12:56
Picon
Favicon

Probems with MA101 and Redhat 9 and Ibm r40 :)

Hi,

Ive managed to get a fair bit further with the Berlios driver than the 
sourceforge one. However Ive still got some problems. I think Ive figured 
whats wrong, basically I cant obtain a MAC address from my Lan's server. Ive 
tried changing specific settings with iwconfig, e.g channel, frequency, 
ssid, ive also tried to force it with a specific mac address but the command 
wasnt available or something around those lines. Ive done a dmesg to see if 
theres any problems and i got these 2 lines :( (ive separated them so you 
can see)

##start dmesg##

hub.c: new USB device 00:1d.1-2, assigned address 2
usb.c: USB device 2 (vend/prod 0x864/0x4102) is not claimed by any active 
driver.
usbdfu.c: USB Device Firmware Upgrade (DFU) handler v0.11beta5
usb.c: registered new driver usbdfu
at76c503.c: Generic Atmel at76c503/at76c505 routines v0.11beta5
at76c503-rfmd.c: Atmel at76c503 (RFMD) Wireless LAN Driver v0.11beta5
usbdfu.c: Downloading firmware for USB device 2...
usb.c: registered new driver at76c503-rfmd
usb-uhci.c: interrupt, status 2, frame# 835

usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 18 ret -84
usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 18 ret -84

usb.c: USB disconnect on device 00:1d.1-2 address 2
hub.c: new USB device 00:1d.1-2, assigned address 3
at76c503.c: $Id: at76c503.c,v 1.35 2003/07/30 06:31:51 jal2 Exp $ compiled
(Continue reading)

Permalink | Reply | 0 comments |
headers
Fred Sonnenwald | 1 Nov 2003 13:04

RE: Probems with MA101 and Redhat 9 and Ibm r40 :)

First, I think your slightly mistaken about MAC addresses. A MAC address is a universially unique
identifier that is part of your ethernet adapter. I think you want to be obtaining an IP address, but there
may something else I don't see. I'm not an expert with this driver.

"Rich B" <rb_52 <at> hotmail.com> wrote:

>Hi,
>
>Ive managed to get a fair bit further with the Berlios driver than the 
>sourceforge one. However Ive still got some problems. I think Ive figured 
>whats wrong, basically I cant obtain a MAC address from my Lan's server. Ive 
>tried changing specific settings with iwconfig, e.g channel, frequency, 
>ssid, ive also tried to force it with a specific mac address but the command 
>wasnt available or something around those lines. Ive done a dmesg to see if 
>theres any problems and i got these 2 lines :( (ive separated them so you 
>can see)
>
>##start dmesg##
>
>hub.c: new USB device 00:1d.1-2, assigned address 2
>usb.c: USB device 2 (vend/prod 0x864/0x4102) is not claimed by any active 
>driver.
>usbdfu.c: USB Device Firmware Upgrade (DFU) handler v0.11beta5
>usb.c: registered new driver usbdfu
>at76c503.c: Generic Atmel at76c503/at76c505 routines v0.11beta5
>at76c503-rfmd.c: Atmel at76c503 (RFMD) Wireless LAN Driver v0.11beta5
>usbdfu.c: Downloading firmware for USB device 2...
>usb.c: registered new driver at76c503-rfmd
>usb-uhci.c: interrupt, status 2, frame# 835
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Rich B | 1 Nov 2003 13:18
Picon
Favicon

Probems with MA101 and Redhat 9 and Ibm r40 :)

Hi,

Ive managed to get a fair bit further with the Berlios driver than the 
sourceforge one. However Ive still got some problems. I think Ive figured 
whats wrong, basically I cant obtain a MAC address from my Lan's server. Ive 
tried changing specific settings with iwconfig, e.g channel, frequency, 
ssid, ive also tried to force it with a specific mac address but the command 
wasnt available or something around those lines. Ive done a dmesg to see if 
theres any problems and i got these 2 lines :( (ive separated them so you 
can see)

##start dmesg##

hub.c: new USB device 00:1d.1-2, assigned address 2
usb.c: USB device 2 (vend/prod 0x864/0x4102) is not claimed by any active 
driver.
usbdfu.c: USB Device Firmware Upgrade (DFU) handler v0.11beta5
usb.c: registered new driver usbdfu
at76c503.c: Generic Atmel at76c503/at76c505 routines v0.11beta5
at76c503-rfmd.c: Atmel at76c503 (RFMD) Wireless LAN Driver v0.11beta5
usbdfu.c: Downloading firmware for USB device 2...
usb.c: registered new driver at76c503-rfmd
usb-uhci.c: interrupt, status 2, frame# 835

usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 18 ret -84
usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 18 ret -84

usb.c: USB disconnect on device 00:1d.1-2 address 2
hub.c: new USB device 00:1d.1-2, assigned address 3
at76c503.c: $Id: at76c503.c,v 1.35 2003/07/30 06:31:51 jal2 Exp $ compiled
(Continue reading)

Permalink | Reply | 2 comments |
headers
Tim Small | 1 Nov 2003 17:16

Re: Probems with MA101 and Redhat 9 and Ibm r40 :)

Mmm, you seem confused about some stuff (e.g. MAC address vs. IP).  Not 
really clear if you are trying to do this, but you need to set the 
interface up after loading the driver

e.g.

iwconfig wlan0 mode managed (if you are using an access point - use 
'ad-hoc' otherwise).
iwconfig wlan0 essid any (or your actual ssid)
ip link set wlan0 up

then either manually configure an IP address e.g. like this:

ip addr add 192.168.1.78/24 dev wlan0

or use a dhcp client (pump, dhclient, dhcp or whatever your system uses) 
e.g.:

dhclient wlan0

If you were using Debian, you would set this stuff up permanently in 
/etc/network/interfaces - I think Redhat still uses a mess of scripts 
and config files under /etc/sysconfig/

if it still isn't working then there may be a problem with the wireless 
driver or USB hub driver - try using the other USB hub driver (e.g. uhci 
vs. usb-uhci).

Tim.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Stuart Walsh | 1 Nov 2003 22:12
Picon

Another technical question

Hi folks,

Got another annoying question for the developers.. In case you've forgotten me, I'm developing a FreeBSD driver.

The problem I'm having now is that in adhoc mode, after creating an IBSS, no other devices scanning can seem
to find it.  When they scan, the LED on the device blinks, so it is receiving the scan packet, but it's not
getting passed down to my driver.  I assume this means that the device handles scan requests in hardware or
something.  Is there something I'm missing in setting up the device perhaps?  The driver works perfectly
connecting to Access Points and connecting to other adhoc nodes when that node creates the ibss, just not
when it creates it itself.

Any help would be much appreciated, and if I havent explained anything particularly well, please let me know.

Regards,

Stuart
Permalink | Reply | 6 comments |
headers
Joerg Albert | 1 Nov 2003 23:20
Picon
Picon

Re: Another technical question

Hi,

On Sat, 1 Nov 2003, Stuart Walsh wrote:

> Got another annoying question for the developers.. In case you've forgotten me,
> I'm developing a FreeBSD driver.
>
> The problem I'm having now is that in adhoc mode, after creating an IBSS,
> no other devices scanning can seem to find it.  When they scan, the LED
> on the device blinks, so it is receiving the scan packet, but it's not
> getting passed down to my driver.  I assume this means that the device
> handles scan requests in hardware or something.  Is there something I'm
> missing in setting up the device perhaps?  The driver works perfectly
> connecting to Access Points and connecting to other adhoc nodes when
> that node creates the ibss, just not when it creates it itself.

guess scan packets == ProbeRequests, i.e. the other device is using active
scanning (opposite to passive, where it only listens on all channels).
Yes, ProbeRequests are handled by the firmware of the USB adapter, the
driver doesn't get them.

Which "other device" did you use and how can you be sure that they haven't
received any answer from the USB adapter to their ProbeRequests?

IMHO the best way to test is to use a third Prism2 or Orinoco based device
to trace all packets on the channel used.
Have you ever tried to trace the beacons of the Atmel USB device? Maybe
there are wrong for some reasons.

/Jörg
(Continue reading)

Permalink | Reply | 5 comments |
headers
Joerg Albert | 1 Nov 2003 23:29
Picon
Picon

Re: Probems with MA101 and Redhat 9 and Ibm r40 :)

Hi Rich,

On Sat, 1 Nov 2003, Rich B wrote:

> Hi,
>
> Ive managed to get a fair bit further with the Berlios driver than the
> sourceforge one. However Ive still got some problems. I think Ive figured
> whats wrong, basically I cant obtain a MAC address from my Lan's server. Ive
> tried changing specific settings with iwconfig, e.g channel, frequency,
> ssid, ive also tried to force it with a specific mac address but the command
> wasnt available or something around those lines. Ive done a dmesg to see if
> theres any problems and i got these 2 lines :( (ive separated them so you
> can see)
>
> ...
> usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 18 ret -84
> usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 18 ret -84

You may easily ignore these lines if you see the device's MAC
address below as in your case (i.e. the driver start + firmware download
was successful). AFAIK hotplug caused them accessing usbdevfs.

>  ...
> Is this a bug with you're drivers or is it a problem with my laptop/hardware
> config? Ive tried drivers .9 .10 and the latest tarball. All create the same
> errors. Will this be responsible for the wireless not connecting to any mac
> address? It can see my mac address (according to dmesg) but it just cant
> locate the servers. By the way i have an onboard eth0 intel network card but
> its not been upgraded to wireless as i havent purchased the hardware.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jackie Huen | 1 Nov 2003 01:32

Arescom USB Adaptor


Here is one more vendor:

Brand: Arescom
Model: WL-210
FCCID: 07J-GL2411USB
VID: 0x0d8e
PID: 0x7110
MAC: AT76C503A
Radio: 3861
Binary Driver Verified: NO
GPL Driver Verified: NO
AT76C503 USB Driver Verified: YES (need to add VID/PID to source)
Vendor: Driver: NO
Chipset Verified: YES

I hope the next release will contain this VID/PID in the source
Permalink | Reply | 1 comment |
headers
Stuart Walsh | 2 Nov 2003 00:38
Picon

Re: Another technical question

On Sat, 1 Nov 2003 23:20:24 +0100 (CET)
Joerg Albert <joerg.albert <at> gmx.de> wrote:

> Hi,
> 
> On Sat, 1 Nov 2003, Stuart Walsh wrote:
> 
> > Got another annoying question for the developers.. In case you've forgotten me,
> > I'm developing a FreeBSD driver.
> >
> > The problem I'm having now is that in adhoc mode, after creating an IBSS,
> > no other devices scanning can seem to find it.  When they scan, the LED
> > on the device blinks, so it is receiving the scan packet, but it's not
> > getting passed down to my driver.  I assume this means that the device
> > handles scan requests in hardware or something.  Is there something I'm
> > missing in setting up the device perhaps?  The driver works perfectly
> > connecting to Access Points and connecting to other adhoc nodes when
> > that node creates the ibss, just not when it creates it itself.
> 
> guess scan packets == ProbeRequests, i.e. the other device is using active
> scanning (opposite to passive, where it only listens on all channels).
> Yes, ProbeRequests are handled by the firmware of the USB adapter, the
> driver doesn't get them.

Probe requests, right.

> Which "other device" did you use and how can you be sure that they haven't
> received any answer from the USB adapter to their ProbeRequests?
>
(Continue reading)

Permalink | Reply | 4 comments |
headers
Joerg Albert | 2 Nov 2003 01:14
Picon
Picon

Re: Another technical question


On Sat, 1 Nov 2003, Stuart Walsh wrote:

> Unfortuneatly the only other device I have to test with is a
> pcmcia atmel chipset card.  The other way around it works just fine.  My
> driver sees the ProbeResponse from the pcmcia card if it has created the
> IBSS.

Does the Atmel PCMCIA driver usually gets ProbeResponses from the firmware
and you miss them now or do you only see that it does not join the
IBSS?

> > IMHO the best way to test is to use a third Prism2 or Orinoco based device
> > to trace all packets on the channel used.
> > Have you ever tried to trace the beacons of the Atmel USB device? Maybe
> > there are wrong for some reasons.
>
> Yeah I could probably use one of those for testing.. just to see
> what's going on exactly.  Everything looks fine to me, but obviously
> something is wrong somewhere.  My thinking was that perhaps I have
> missed a setting somewhere and so the firmware is ignoring proberequests
> for some reason.

I haven't seen such a setting yet. AFAIR you may make the beacon content
inconsistent (reported channel != used channel) by fiddling with some MIB
content, but I don't remember which.
You don't have two USB adapters either?

/Jörg
(Continue reading)

Permalink | Reply | 3 comments |

Gmane