[ltp] network/pcmcia problems

[Paul Barrett]

Peter Soderling writes:
 > A couple of questions:
 > 
 > did you supplement the pcmcia-cs-3.0.14 package with the driver from the
 > above site.  .  . or did you just use the 3.0.14 source unmodified? I
 > noticed that at the above site there is a line saying the the driver is now
 > integrated w/ 3.0.14.

I used the unmodified source in the 3.0.14 package.  A 'diff' of the
two shows that they're not significantly different.

 > I am using the 'make xconfig' command . . . so I am assuming that that above
 > option is the equivilent to saying 'no' to the 'configure network drivers'
 > (or something to that effect) option. If I'm wrong here . . . this may be my
 > problem . . . ?

Yes, that is correct.  I see no problem here.

 > and, for the pcmcia source, 'make dep', 'make all' & 'make install'

That's fine.

 > . . . and I get 'XIRCOM ini' . . . . freeze    ;-)

It sounds like your set-up is fine.  cardmgr is recognizing the
EtherJet card and installing it correctly, otherwise you wouldn't be
getting this far in the initialization process.

The following is from my /var/log/messages file showing the kernel
messages during EtherJet initialization.  I would think yours should
be very similar.

Aug 31 08:28:20 localhost cardmgr[396]: initializing socket 0
Aug 31 08:28:20 localhost cardmgr[396]: socket 0: IBM EtherJet 10/100
Aug 31 08:28:20 localhost cardmgr[396]: executing: 'insmod /lib/modules/2.2.5-22/pcmcia/cb_enabler.o'
Aug 31 08:28:20 localhost cardmgr[396]: executing: 'insmod /lib/modules/2.2.5-22/pcmcia/tulip_cb.o'
Aug 31 08:28:20 localhost kernel: cs: cb_config(bus 1): vendor 0x115d, device 0x0003 
Aug 31 08:28:20 localhost kernel:   fn 0 bar 1: io 0x280-0x2ff 
Aug 31 08:28:20 localhost kernel:   fn 0 bar 2: mem 0xa0011000-0xa00117ff 
Aug 31 08:28:20 localhost kernel:   fn 0 bar 3: mem 0xa0010000-0xa00107ff 
Aug 31 08:28:20 localhost kernel:   fn 0 rom: mem 0xa000c000-0xa000ffff 
Aug 31 08:28:20 localhost kernel: tulip_attach(bus 1, function 0) 
Aug 31 08:28:20 localhost kernel: tulip.c:v0.91 4/14/99 becker@cesdis.gsfc.nasa.gov (modified by danilo@cs.uni-magdeburg.de for XIRCOM CBE, fixed by Doug Ledford) 
Aug 31 08:28:20 localhost kernel: eth0: Xircom Cardbus Adapter (DEC 21143 compatible mode) rev 3 at 0x280, 00:06:29:90:47:C8, IRQ 3. 
Aug 31 08:28:20 localhost kernel: eth0:  MII transceiver #0 config 3100 status 7809 advertising 01e1. 
Aug 31 08:28:20 localhost kernel: XIRCOM init 
Aug 31 08:28:20 localhost cardmgr[396]: executing: './network start eth0'

Are you able to tell if cardmgr is executing the start network script
as shown above?  If so, then my guess is that you have a hardware
conflict, possibly with the sound card.  I have not been able to get
my sound card working in native mode.  It only works with the
SoundBlaster modules.  I seem to remember reading that someone else
noticed a conflict between his sound chip and the PCMCIA cards.

 > Finally . . . what about this option from your config.opts file . . .I
 > noticed it was commented out:
 > 
 > > # for IBM EtherJet Cardbus...
 > > #module "tulip_cb" opts "strict_csr6=1"

No, these lines aren't necessary.

 -- Paul