headers
Mark Sansome | 9 Sep 2007 10:22
Picon
Picon

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
(Continue reading)

Permalink | Reply |
headers
Pavel Roskin | 10 Sep 2007 05:13
Picon

Re: Problem with 2.6.22 kernel

On Sun, 2007-09-09 at 09:22 +0100, Mark Sansome wrote:

> > > 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... 

There is no loadable firmware with such version.  In fact, all versions
start with 0 or 1.  If the driver loads the firmware, it reads the
version from the firmware file, then loads the firmware, then reads the
firmware version from the device and compares two first numbers to make
sure that the firmware has been loaded successfully.

The original test would compare all numbers with 0, but I wanted to
strengthen the test.  On my hardware, the third number would mismatch,
but I assumes that the first two numbers would not.

I understand that either the firmware doesn't need to be loaded for your
hardware, or the version actually starts with "1", but the message was
corrupted.

> > 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
(Continue reading)

Permalink | Reply |
headers
Mark Sansome | 10 Sep 2007 10:31
Picon
Picon

Re: Problem with 2.6.22 kernel

On Sun, Sep 09, 2007 at 11:13:49PM -0400, Pavel Roskin wrote:
> On Sun, 2007-09-09 at 09:22 +0100, Mark Sansome wrote:

> > What else do I need to do to make it think that that wlan0 is eth1? (or
> > should I simply pursue the ifrename solution?)
> 
> Normally, Fedora and related systems would just rename the device if
> there is a configuration with matching HWADDR.  That is, if you have
> configuration for wlan0 and it includes HWADDR=MAC, and that MAC address
> is found on eth1, it would be renamed to wlan0.  It should be absolutely
> transparent, but it's not working for you.
> 
> Since I don't know why it's not working, I cannot be confident that any
> particular approach would help.
> 
> You could try running system-config-network, which is supposed to create
> all those files.

Actually this turned out to be easier than I thought. I discovered that my ifcfg-wlan0 file had a blank
HWADDR entry. Clearly this was not a problem with the previous version of the driver. Simply putting the
appropriate MAC address against this entry in the file meant that the driver now correctly associates
with wlan0, picks up all the relevant settings and "just works".

Many thanks for pointing me in the right direction here...

Once again, thanks for all your work with this driver. It's unfortunate that with this type of software the
only time anyone notices your efforts is when something goes wrong. I for one do appreciate what you do...

Thanks
(Continue reading)

Permalink | Reply |
headers
Pavel Roskin | 10 Sep 2007 12:59
Picon

Re: Problem with 2.6.22 kernel

Quoting Mark Sansome <msansome <at> troodos.demon.co.uk>:

> p.s. 2 cheeky additional questions:
> a) When (roughly) do you think the driver could be incorporated into  
>  the kernel?

I think it's too late for 2.6.24, but 2.6.25 is a realistic target.

> b) Any prospect of WPA support?

If mac80211 conversion succeeds, WPA will be supported automatically.

--

-- 
Regards,
Pavel Roskin
Permalink | Reply |
headers
Milan Plzik | 10 Sep 2007 17:56
Picon

Re: Problem with 2.6.22 kernel

On Po, 2007-09-10 at 06:59 -0400, Pavel Roskin wrote:
> Quoting Mark Sansome <msansome <at> troodos.demon.co.uk>:
> 
> > p.s. 2 cheeky additional questions:
> > a) When (roughly) do you think the driver could be incorporated into  
> >  the kernel?
> 
> I think it's too late for 2.6.24, but 2.6.25 is a realistic target.
> 
> > b) Any prospect of WPA support?
> 
> If mac80211 conversion succeeds, WPA will be supported automatically.
> 

  I'm not very sure, but is it really so? AFAIK WPA support requires 1.x
firmware releases, which are not (yet) supported at all. But I'm not
sure what does WPA support exactly mean (e.g. what everything changes).
I originally wanted to add support for WPA-enabled firmware to at76c503
driver as a part of my bachelor's work (or at least make an attempt to
do that), based on atmelwlandriver. However, if this can be done
otherwise, I can rather focus on some other topic. 

	Milan Plzik
Permalink | Reply |
headers
Pavel Roskin | 11 Sep 2007 03:42
Picon

Re: Problem with 2.6.22 kernel

Hello, Milan!

On Mon, 2007-09-10 at 17:56 +0200, Milan Plzik wrote:
> On Po, 2007-09-10 at 06:59 -0400, Pavel Roskin wrote:
> > Quoting Mark Sansome <msansome <at> troodos.demon.co.uk>:
> > 
> > > p.s. 2 cheeky additional questions:
> > > a) When (roughly) do you think the driver could be incorporated into  
> > >  the kernel?
> > 
> > I think it's too late for 2.6.24, but 2.6.25 is a realistic target.
> > 
> > > b) Any prospect of WPA support?
> > 
> > If mac80211 conversion succeeds, WPA will be supported automatically.
> > 
>   I'm not very sure, but is it really so?

It's hard to say until it's done.

>  AFAIK WPA support requires 1.x
> firmware releases, which are not (yet) supported at all.

You probably mean 1.103 firmware.  Indeed, it's not supported.  I think
it would be easier to add support for it once mac80211 conversion is
completed, as it would move some operations from the firmware to the
software, making firmware differences less relevant.

>  But I'm not
> sure what does WPA support exactly mean (e.g. what everything changes).
(Continue reading)

Permalink | Reply |

Gmane