Re: Problem with 2.6.22 kernel

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


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

Firstly, apologies for taking so long to get back to you on this. I was
on holiday at the time you wrote and on my return discovered an
(unrelated) network problem which I wanted to eliminate before I dealt
with this:

On Fri, 2007-08-31 at 11:40 -0400, Pavel Roskin wrote:
> On Sat, 2007-08-11 at 18:48 +0100, Mark Sansome wrote:
> >=20
> > I have been running the at76c503a driver quite successfully for a numbe=
r
> > of years now (the latest being v.0.14dev on a  2.6.20 kernel) on Fedora
> > Core x (currently FC6).
> >=20
> > Today a kernel update became available in the Fedora repository so I
> > upgraded. I now have the following : (uname -a)
> >=20
> > 2.6.22.1-32.fc6 #1 SMP Wed Aug 1 15:15:33 EDT 2007 i686 i686 i386
> > GNU/Linux
> >=20
> > I downloaded 0.16 from cvs and it compiled without error. On rebooting
> > however wlan0 failed to load.
>=20
> That's unclear.  Does it mean that wlan0 doesn't exist?
>=20
Yes sorry, there are "device not found" messages on boot, but strangely
nothing similar in dmesg.

> > I am unable to bring the interface up with
> > ifconfig wlan0 up or with iwlist wlan0 scan.
>=20
> Again, it's unclear.  Are there any error messages from ifconfig, or the
> interface just stays down?

No, there are no error messages.

> >  There are no errors (as far
> > as I can tell) reported in dmesg. lsmod shows that at76_usb is loaded.
>=20
> Can you post the kernel messages?  What does iwconfig show?

Looking at this in more depth now it seems that as the system boots it
is trying to associate the driver with eth1 NOT with wlan0.

ifconfig shows nothing helpful: (Note: there IS an ethernet card -eth0-
in the PC which shares the connection out to another PC).

eth0      Link encap:Ethernet  HWaddr 00:20:ED:57:73:25 =20
          inet addr:192.168.124.2  Bcast:192.168.124.255
Mask:255.255.255.0
          inet6 addr: fe80::220:edff:fe57:7325/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:529 errors:0 dropped:0 overruns:0 frame:0
          TX packets:145 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000=20
          RX bytes:156060 (152.4 KiB)  TX bytes:23333 (22.7 KiB)
          Interrupt:18 Base address:0x6000=20

lo        Link encap:Local Loopback =20
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:117 errors:0 dropped:0 overruns:0 frame:0
          TX packets:117 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0=20
          RX bytes:12406 (12.1 KiB)  TX bytes:12406 (12.1 KiB)

iwconfig is more interesting:

eth1      IEEE 802.11b  ESSID:off/any =20
          Mode:Managed  Frequency:2.457 GHz  Access Point:
Not-Associated  =20
          Bit Rate:11 Mb/s   Tx-Power=3D15 dBm  =20
          Retry limit:8   RTS thr=3D1536 B   Fragment thr=3D1536 B  =20
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

Grepping dmesg for "eth" and for "Atmel" gives the following:
eth0: RealTek RTL8139 at 0xd8866000, 00:20:ed:57:73:25, IRQ 18
eth0:  Identified 8139 chip type 'RTL-8100B/8139D'
eth1: MAC address 00:30:f1:24:15:d7
eth1: firmware version 8.101.5-84
eth1: regulatory domain 0x30: ETSI (most of Europe)
eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
eth0: no IPv6 routers present
Atmel at76x USB Wireless LAN Driver 0.16 loading

Note: Grepping for wlan0 produced no output from dmesg.

So, if my assumptions are correct, why is it trying to associate the
driver with eth1 instead of wlan0 as it has always done in the past?

How do I correct this?

Many thanks and best regards

Mark

p.s.

I do appreciate all the work you put into this (and I'm looking forward
to the day it's included in the kernel!...)




--=-bOgh3X2QjxtnFuB7zRYt
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)

iD8DBQBG3wDzdLsotyXZSYARAmoDAKCGEtsp0PD/0QanfkwURr0e/kxY0gCgmUx4
lim1bUAlgdWzKBHX8s6CERk=
=lSWE
-----END PGP SIGNATURE-----

--=-bOgh3X2QjxtnFuB7zRYt--



--===============2098960036==
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

--===============2098960036==--