Is this still your email

_______________________________________________
at76c503a-user mailing list
at76c503a-user <at> lists.berlios.de
https://lists.berlios.de/mailman/listinfo/at76c503a-user

Re: Hello at76c503a-user <at> lists.berlios.de

hey at76c503a-user <at> lists.berlios.de how have you been? i was under until i tried myself http://t.co/FCiY3n3Y

problem with linux-2.6.27

Hi!

First of all some feedback: I got Ubuntu 7.10, compiled at76-usb-0.17 for it, installed the firmware and
removed the old at76-usb-0.14 version which came with Ubuntu. Then it worked, nearly perfectly. WEP did,
WPA not; excellent performance!

Now I installed the new Ubuntu 8.10 and tried to do the same. The new Linux 2.6.27 had changed some interfaces
minorly - i adopted them and compiled the adopted at76-usb-0.17, installed the fw, removed the \"wrong\"
at76.ko-s from /lib/modules/..., depmod -aeq... -> Result: It worked with the same bad performance as
0.14 (unusable).

Does anyone has an idea what my mistake was or what had changed?

Claudio

Netg.MA101b user feedback

Hi at76c503a-developers!

We have got several computers at home and two of those devices:
  0864:4102 Netgear, Inc. MA101 802.11b Adapter
I have been using the atmelwlandriver[1] on Debian for a long time. Now
I have to get the wlan adapter running on a new Ubuntu installation. So
I took a look at your project.

Comparison of at76c503a and atmelwlandriver from my point of view:
 * atmelwlandriver is hard to set up (can cause frustration)
 * at76c503a is easy to set up (tremendously easy!)
 * atmelwlandriver works flawless, does scanning, never crashes
 * at76c503a (when used out-of-the-box) hardly holds contact to the
   access point, does not do scanning and "kills" kernel on device
   removal

Sadly I have to stay with the patched atmelwlandriver for now. I have
never done driver development so far, but I can help you by testing.

Claudio

[1]: sf.net/projects/atmelwlandriver (3.4.1.1) + self-made patch

field 'dwork_restart' has incomplete type

Hello Berlios List!

I am trying to get my Xterasys xn-2122b USB wireless
adapter to work on Debian etch, but when I try to
comiple the driver, 'make' gives me the error messages
shown below.

Please advise.

Thank you.

<begin insert>
make -C /usr/src/linux-headers-2.6.18-5-486
M=/mnt/bedlam/VAR/berlios/at76_usb-0.17
KERNELRELEASE=2.6.18-5-486 modules
make[1]: Entering directory
`/usr/src/linux-headers-2.6.18-5-486'
  CC [M] 
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.o
In file included from
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.c:41:
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.h:463:
error: field 'dwork_restart' has incomplete type
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.h:464:
error: field 'dwork_get_scan' has incomplete type
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.h:465:
error: field 'dwork_beacon' has incomplete type
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.h:466:
error: field 'dwork_auth' has incomplete type
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.h:467:
error: field 'dwork_assoc' has incomplete type
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.c: In
function 'at76_tx_callback':
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.c:1535:
warning: passing argument 6 of 'usb_fill_bulk_urb'
from incompatible pointer type
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.c: In
function 'at76_tx_mgmt':
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.c:1595:
warning: passing argument 6 of 'usb_fill_bulk_urb'
from incompatible pointer type
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.c: In
function 'at76_tx':
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.c:3213:
warning: passing argument 6 of 'usb_fill_bulk_urb'
from incompatible pointer type
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.c: In
function 'at76_submit_rx_urb':
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.c:3272:
warning: passing argument 6 of 'usb_fill_bulk_urb'
from incompatible pointer type
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.c: In
function 'at76_dwork_get_scan':
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.c:3695:
warning: type defaults to 'int' in declaration of
'__mptr'
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.c:3695:
warning: initialization from incompatible pointer type
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.c: In
function 'at76_dwork_beacon':
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.c:3763:
warning: type defaults to 'int' in declaration of
'__mptr'
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.c:3763:
warning: initialization from incompatible pointer type
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.c: In
function 'at76_dwork_auth':
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.c:3787:
warning: type defaults to 'int' in declaration of
'__mptr'
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.c:3787:
warning: initialization from incompatible pointer type
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.c: In
function 'at76_dwork_assoc':
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.c:3816:
warning: type defaults to 'int' in declaration of
'__mptr'
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.c:3816:
warning: initialization from incompatible pointer type
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.c: In
function 'at76_dwork_restart':
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.c:3997:
warning: type defaults to 'int' in declaration of
'__mptr'
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.c:3997:
warning: initialization from incompatible pointer type
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.c:5142:56:
error: macro "INIT_WORK" requires 3 arguments, but
only 2 given
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.c: In
function 'at76_alloc_new_device':
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.c:5142:
error: 'INIT_WORK' undeclared (first use in this
function)
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.c:5142:
error: (Each undeclared identifier is reported only
once
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.c:5142:
error: for each function it appears in.)
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.c:5143:44:
error: macro "INIT_WORK" requires 3 arguments, but
only 2 given
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.c:5144:50:
error: macro "INIT_WORK" requires 3 arguments, but
only 2 given
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.c:5145:56:
error: macro "INIT_WORK" requires 3 arguments, but
only 2 given
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.c:5146:58:
error: macro "INIT_WORK" requires 3 arguments, but
only 2 given
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.c:5147:54:
error: macro "INIT_WORK" requires 3 arguments, but
only 2 given
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.c:5148:
warning: implicit declaration of function
'INIT_DELAYED_WORK'
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.c: In
function 'at76_alloc_urbs':
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.c:5205:
warning: implicit declaration of function
'usb_endpoint_is_bulk_in'
/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.c:5208:
warning: implicit declaration of function
'usb_endpoint_is_bulk_out'
make[2]: ***
[/mnt/bedlam/VAR/berlios/at76_usb-0.17/at76_usb.o]
Error 1
make[1]: ***
[_module_/mnt/bedlam/VAR/berlios/at76_usb-0.17] Error
2
make[1]: Leaving directory
`/usr/src/linux-headers-2.6.18-5-486'
make: *** [modules] Error 2
</end insert>

      ____________________________________________________________________________________
Be a better sports nut!  Let your teams follow you 
with Yahoo Mobile. Try it now.  http://mobile.yahoo.com/sports;_ylt=At9_qDKvtAbMuh1G1SQtBI7ntAcJ

[ANNOUNCE] at76_usb 0.17 released

Hello!

Version 0.17 of the at76_usb driver has been released.

This is a stability release that includes only a handful of fixes.

- The default network device names will now start with "wlan", as in
  versions prior to 0.16.

- Fixed support for Belkin F5D6050.

- Added support for Corega Wireless LAN USB-11 mini and mini2.

- Improved messages in the kernel log.

- Packets captured in monitor mode use correct value for the protocol.

The driver is compatible with Linux 2.6.20 and newer, including the
forthcoming version 2.6.23.

--

-- 
Regards,
Pavel Roskin

wrong firmware version with Belkin F5D6050 and kernel 2.6.22.5

_______________________________________________
at76c503a-user mailing list
at76c503a-user <at> lists.berlios.de
https://lists.berlios.de/mailman/listinfo/at76c503a-user

Developer mailing list/code repository

  Hello,

  I tried to find some information on at76c503a page at berlios, but it
looks like it is quite out of date. Is there any mailing list for
developers? Is there any official repository holding the most recent
driver version? Accodring to commit logs, CVS is synced with some GIT
repository... . I would like to watch at76c503 development a bit. :)

	Milan

Re: Problem with 2.6.22 kernel

Hi Pavel,

On Sun, 2007-09-09 at 02:07 -0400, Pavel Roskin wrote:
> Hello, Mark!
> 
> On Wed, 2007-09-05 at 20:18 +0100, Mark Sansome wrote:

> As we can see, the device is called eth1, so problems with wlan0 are
> irrelevant to the driver.  I suspect wlan0 simply doesn't exist.
> 
Yes that's right.

> That's a clear sign that the only wireless device is called eth1.
> 
That's the conclusion I have come to...

> > eth1: firmware version 8.101.5-84
> 
> There is no firmware with major version 8.  I assumed that the first two
> numbers (major and minor version) would match the versions provided by
> Atmel in the text files from which the binary files are generated.
> 
I don't understand this bit... 
> 
> Since the version mismatch wasn't detected (at least it didn't prevent
> registering the interface), I assume that either you have a device that
> doesn't require firmware download, or you are not using version 0.16 as
> published on berlios.de, or the kernel messages got corrupted somewhere.
All I can tell you is that I have a Belkin F5D6050 and:
> >Atmel at76x USB Wireless LAN Driver 0.16 loading
that I got the latest driver from cvs

> 
> This change was made by Guido Guenther with the log message "remove
> netdev_name, names of network devices can be set via udev".  It's
> unfortunate that I didn't look at that commit.  Even though removing the
> parameter was justified, I don't think changing the default name was a
> good idea.
> 
> I guess the intention was to use names starting with "wlan" only for
> drivers based on mac80211 stack.  Since the mac80211 conversion is
> underway, the problem can be expected to be fixed in the next release.
When (roughly) might this be?

> > How do I correct this?
> 
> The answer is generally specific to the distribution.  It's possible to
> use ifrename that comes with wireless tools.  Fedora makes it possible
> to specify MAC address for the device, and if the device with that MAC
> address is named differently, it will be renamed.
> 
> Perhaps the easies approach would be just to accept that the device is
> called eth1 now.

I might need some help with this.

I'm looking into ifrename at the moment...

If I simply accept that wlan0->eth1 I will need to change some
configurations. In the following locations:
/etc/sysconfig/network-scripts/
/etc/sysconfig/networking/devices/
/etc/sysconfig/networking/profiles/default/
I have the files:
ifcfg-wlan0
keys-wlan0
route-wlan0
I have tried copying each of those to *-eth1 in all of the above
locations and rebooting but still the startup screen is full of "Device
not found" messages relating to wlan0 so I guess it is not as simple as
all that.

What else do I need to do to make it think that that wlan0 is eth1? (or
should I simply pursue the ifrename solution?)

Many thanks for your help and support so far.

Mark

_______________________________________________
at76c503a-user mailing list
at76c503a-user <at> lists.berlios.de
https://lists.berlios.de/mailman/listinfo/at76c503a-user

Problem with 2.6.22 kernel

Hello all,

I have been running the at76c503a driver quite successfully for a number
of years now (the latest being v.0.14dev on a  2.6.20 kernel) on Fedora
Core x (currently FC6).

Today a kernel update became available in the Fedora repository so I
upgraded. I now have the following : (uname -a)

2.6.22.1-32.fc6 #1 SMP Wed Aug 1 15:15:33 EDT 2007 i686 i686 i386
GNU/Linux

My current (0.14dev) at76 driver failed to build (I can post error
messages if required) but I was not concerned as I had seen the
announcement about 0.16 and thought it about time for an update anyway.

I downloaded 0.16 from cvs and it compiled without error. On rebooting
however wlan0 failed to load. I am unable to bring the interface up with
ifconfig wlan0 up or with iwlist wlan0 scan. There are no errors (as far
as I can tell) reported in dmesg. lsmod shows that at76_usb is loaded.

I have had to drop back to kernel v.2.6.20 (which is a pain because Yum
automatically upgraded my nvidia drivers to match the 2.6.22 kernel so
at the moment I don't have an X session!).

My question (1) :
Does anyone else have at76_usb working with a 2.6.22 kernel? (and
ideally anyone on FC6?)

My question (2) :
Do I require wireless-tools > wireless-tools-28-1.fc6?
If so this will be a non-trivial exercise on FC6 as when I tried to
update (using Yum) from the "development" repository (v.28 is the latest
available in "core") to wireless-tools-29-0.1.pre21.fc8 it wanted to
update Network Tools which wanted a whole new KDE which wanted ... just
about every package installed... - it eventually failed dependency
checks...

Thanks in advance for your help...

Mark

_______________________________________________
at76c503a-user mailing list
at76c503a-user <at> lists.berlios.de
https://lists.berlios.de/mailman/listinfo/at76c503a-user

[ANNOUNCE] at76_usb 0.16 released

Hello!

Version 0.16 of the at76_usb driver has been released.

The most important changes in this version may not be visible to the
ordinary users.  The code have been cleaned up, so that the driver can
be submitted for the Linux kernel inclusion.

This driver compiles for Linux 2.6.20 and newer, but it's impossible to
guarantee that it will compile for the future kernels.  Only submitting
the driver to the kernel would ensure that the driver stays up to date
with the kernel API.

Please don't complain that older versions are not supported.  A driver
to be submitted to Linux may not have any backward compatibility code.
It's already good that a way was found to support several kernels
without modifying the sources.

Two major bugs have been fixed.  Reloading the driver without unplugging
the device could cause kernel panic in older versions of the driver.
Running scan while the driver was in process of association could cause
kernel panic as well.

The driver now respects the channel in monitor mode.  While it can
capture beacons from neighboring channels, it won't capture packets from
all channels indiscriminately, as it was before.  Unfortunately, only
beacons are captured in monitor mode.  This appears to be a limitation
of the chipset.

It's now possible to read back all private parameters using the iwpriv
command.

The common event loop has been split into individual functions, which
may improve responsiveness of the system.  However, more work is needed
in this area.

If you want to reply to this announcement, please pick one list to podt
to, don't cross-post!

--

-- 
Regards,
Pavel Roskin