ELSA AirLancer MC-11 wireless card and isoundd issues with Intimate

Hi there,

I am trying to get my Intimate iPAQ (modified rsync'd intimate-release
version with kernel 2.4.18-rmk3) to function as a wireless gateway/router
(eth0/usbf) for the rest of my little network but have run into a couple of
things that have me stumped.

Firstly, I realise that the pcmcia sleeve has to be initialised prior to the
pivot_root and 'booting' of the Intimate distro in order for the HD to be
used - does this affect the way that the pcmcia system works from a user POV
in Intimate. I ask as running a

/etc/init.d/pcmcia restart

in intimate gives an error (from memory) of 'rc.pcmcia does not contain PCIC
definition' (or something along those lines), which on checking, it does.
However, starting cardmgr from the cli works fine and I can insert/remove
cards with them being identified etc fine.

However, no messages regarding the cards show up in /var/log/messages or
stdout although modules etc are loaded fine, and the
/etc/pcmcia/<wireless/network/*.opts> scripts do not seem to run to bring up
the interface/configure etc.

The interface (eth0) is fine and can be brought up manually/ping over the
link/wireless tools work fine, so all that works, but I can't work out where
the difficulty lies within the pcmcia system preventing from all of this
being automated!

Also, after having the interface up for a few minutes (5-10), it seems to
spontaneously die on me despite the interfaces still being up according to
ifconfig.

(I have the iPAQ communicating with my laptop via another wireless card in
Ad-hoc mode that works fine and reliably in Familiar, so I am pretty sure
that the problem lies at the 'Intimate end' of things)

The link dropping doesn't seem to have anything to do with the iPAQ
suspending etc as it happens regardless of the state on the iPAQ. Again,
/var/log/messages doesn't say a thing!

Does anyone have any idea as to what might be the problem (it may all stem
from the pcmcia issue I mentioned first), any ideas welcome!

Finally (this has gone on a bit - sorry!), sound in Intimate. Is the
/dev/dsp device supposed to be a real file rather than a devfs 'dynamic'
filetype that is created at boot time (sorry for the terminology, I haven't
ventured into devfs etc before!)? Starting isoundd (at boot time or
manually) gives me an 'input/output error' message and I oticed that
/dev/dsp seems to be the only 'real' file remaining in the /dev/ dir when I
examine the fs without Intimate booted (aside from a couple of tty-related
symlinks IIRC). Any thoughts?

Sorry to go on, but I probably spent more time than was strictly good for me
playing with all this yesterday!

Regards,

Ben
Received on Mon Jul 15 10:50:15 2002