Re: Problem with 2.6.22 kernel

--===============1112675538==
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-gDgiS3Sjb9ukyYjJwtP6"


--=-gDgiS3Sjb9ukyYjJwtP6
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Hi Pavel,

On Sun, 2007-09-09 at 02:07 -0400, Pavel Roskin wrote:
> Hello, Mark!
>=20
> 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.
>=20
Yes that's right.

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

> > eth1: firmware version 8.101.5-84
>=20
> 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.
>=20
I don't understand this bit...=20
>=20
> 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

>=20
> 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.
>=20
> 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?
>=20
> 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.
>=20
> 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


--=-gDgiS3Sjb9ukyYjJwtP6
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQBG461KdLsotyXZSYARAtChAJ9vLbQsC2dd9meweNxDhVhcldP+owCgtUyj
W3FATP3JigoppaZeZCT3t7I=
=ir+7
-----END PGP SIGNATURE-----

--=-gDgiS3Sjb9ukyYjJwtP6--



--===============1112675538==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
at76c503a-user mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/at76c503a-user

--===============1112675538==--