[Prism54-users] Cardservices and Prism54

[Stefan U. Hegner (Mobil)]

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

Hi Bradley,

somewhere in your email I picked up some notes of anger or frustration
... possibly because I'm still not getting this right.

Anyway, despite this your mail was very helpful and after another 3
hours I got at least something that's working for me.

@mcgrof: I'm not shure about other newbies problems. - But some
reference to what hotplug does (besides uploading firmware) and how an
ifcfg-ethX file could look like that ifup can configure the interface
might be a helpful addition to the README.

Am Die, 2003-12-02 um 17.59 schrieb Bradley Chapman:=20
> > After reading more docs I am pretty certain, that my problem is the
> > integration of Prism54 into PCMCIA Cardservices.
>=20
> Maybe not. Card Services handles PCMCIA cards. Hotplug handles Cardbus ca=
rds,
> since Cardbus is a 32bit bus and is similar to PCI.

OK. But that suggests that I don't need pcmcia-cardservices at all.
However in the README there is still a reference to pcmcia-cs (though
related to Debian).

To spell this out it means=20
- the "old" ISL3890 uses pcmcia-cs and is configured by wireless.opts
- the "new" prism54 uses hotplug and needs to be configured differently

> You don't. You need to play with the stuff in /etc/hotplug instead.

(This is how things work on my Mandrake 9.1)
In the /etc/hotplug/net.agent ifplugd is called for bringing up
interfaces on Mandrake systems. The latter in turn calls ifup.

I've now tried a series of things:

a.) modified /etc/hotplug/net.agent in order to call iwconfig before
calling ifplugd.=20

        case $INTERFACE in
          eth1)
            mesg calling iwconfig for $INTERFACE ...
            /sbin/iwconfig $INTERFACE mode managed essid myessid
          ;;
        esac

This is not really elegant - but it works, since eth1 is on my machine
my Primsm54 Adaptor.

The reason for this was my syslog showing me:

ifplugd(eth1)[3277]: Using interface eth1/00:00:00:00:00:00
ifplugd(eth1)[3277]: Using detection mode: wireless extension
ifplugd(eth1)[3277]: ifplugd 0.15 successfully initialized, link beat
not detected.

In order to get a link beat detection, I needed to tell the card somehow
mode and essid ... then I got a little further down the log:

ifplugd(eth1)[2285]: Link beat detected.
ifplugd(eth1)[2285]: Executing '/etc/ifplugd/ifplugd.action eth1 up'.
ifplugd(eth1)[2285]: Program executed successfully.

But this didn't bring me any further.

b.) created /etc/sysconfig/networking-scripts/ifcfg-eth1 (eth0 is a
wired interface) with the following:

DEVICE=3Deth1
BOOTPROTO=3Ddhcp
ONBOOT=3Dyes
WIRELESS_MODE=3Dmanaged
WIRELESS_ESSID=3Dmyessid

Now my card comes up on insertion and gets an address via dhcp. This
works for me ... but I wonder, whether there is a better solution than
my "rude" way to use iwconfig from hotplug.

Finally, there are still this tons of "jiffi" messages in my syslog
like:

kernel: islpci_mgt_response(): entry in queue not found yet, retrying
(jiffies left =3D X
kernel: islpci_mgt_response(): queue empty, retrying (jiffies left =3D X

Where the "jiffies left =3D" varies between 100 and 0. - Does this have to
mean anything to me? I seem to get these messages only when the Prism54
card is not yet set-up properly. - So I assume I can ignore this.

However, I'm still curious to know what "jiffies" are ...

Thanks again.

Stefan.


--=20
/ Stefan Ulrich Hegner aka "Hegi" - Loehne/ Westfalen - Germany \
| mobil@hegner-online.de - primary Email stefan@hegner-online.de|
\ GPG-Fprint D9DB 51BD 2DA6 9B3A 41CB  0287 05A1 8D11 38BA CE91 /

--=-k7vCIY5dDdmJKqPemteR
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: Dies ist ein digital signierter Nachrichtenteil

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

iD8DBQA/zPucBaGNETi6zpERAnh/AJ4rz5Zf0oFS8C1Pda+ofFHgu0c6gwCdHoJT
7B7jxOgUEHOe5i1GqAQKtVI=
=f/Ua
-----END PGP SIGNATURE-----

--=-k7vCIY5dDdmJKqPemteR--