[ Next-in-Thread ]  [ Next Message ] 

Problems with Vadem VG-469 isa bridge 

Forum: PCMCIA Installation and Configuration Issues
Date: 1999, Nov 02
From: Steve Kann stevek

I've been having a heck of a time trying to get a Lucent Wavelan IEEE -compatible (actually a cabletron roamabout DS) working on a linux PC.

I think that it is some kind of hardware conflict or something like that, because I've gotten it working on two other machines (one a laptop, and another desktop machine), using the exact same methodologies, with no problems.

The PC card comes with a PCMCIA->ISA bridge card. What happens is this: After a clean boot, the first time I load the PCMCIA modules, they will properly detect an insertion and load the correct card service module. The module doesn't work, though -- the wavelan2_cs module loads and identifies the card, but it can't communicate properly with it. I've tried blocking out different io port ranges to get the card onto either 0x100, 0x300, or 0x400 (+40), all of which seem to be free on my machine. I've tried different interrupts also, including 3 and 7 (com2 and lpt1, both disabled in my bios), and no difference.

The next symptom, is that after stopping and restarting the pcmcia subsystem, after inserting a card, I always get the message "socket timed out during reset".

I am using kernel 2.2.13, and have tried both the 3.0.14 and 3.1.3 PCMCIA releases, as well as both the lucent wavelan2 4.00 and Andreas Neuhaus' wvlan_cs 1.0.1 package. Both seem to have similar problems.

I have enabled debugging via PCMCIA_DEBUG, and various pc_debug settings. The results of that can be found at http://www.stevek.com/debug

I've tried changing all kinds of different parameters, including most of the timing parameters for pcmcia_core reset stuff, using async_clock for the i82365, etc. Nothing seems to have any affect other than changing how long it takes for the pcmcia driver to give up resetting the socket.

TIA for any advice!

[ Next-in-Thread ]  [ Next Message ] 

Messages Inline: [ 0 ]  [ All ]  Outline: [ 1 ]  [ 2 ]  [ All ] 

No good ideas, unfortunately

Re: Problems with Vadem VG-469 isa bridge (Steve Kann)
Date: 1999, Nov 30
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Can you maybe try swapping the Wavelan card and/or the ISA-to-PCMCIA
bridge card with one of the other systems you say you've set up
successfully?  That would help to rule out some possible hardware
failures.

Otherwise, nothing jumps out at me.

-- Dave

Ok: Older version(s) seems to work.

Re: Problems with Vadem VG-469 isa bridge (Steve Kann)
Date: 1999, Dec 15
From: Dan dan

My symptoms :

kernel - 2.0.34
pcmcia - 3.1.x
card - lucent ISA to pcmcia, single slot, based on vadem 469 chip
computer - old 486-s 33/66/100 ...

default setup/boot hung-up on cardmgr - I went to 'by-hand' mode...

insmod of 'pcmcia_core' (no opts) worked
insmod of 'i82365' (no opts) hangs, but machine OK, <CR> ok, ^C-s nogo
(try many timing options consider debugging - nogo)

lsmod at this point (from another window...) shows i82365 there, but not initialized.

reboot...(often)


My solution :

peruse web and see many using this card OK, others not OK.
try three different ISA motherboard machines, all same.
try late 2.x.x release of pcmcia_cs from archives - my client drivers need 3.x.x (ug)
try 3.0.13 pcmcia - wa-la - works so far...

Thoughts from web notes (from others):

somewhere between vadem support enabled and the current 3.x releases that some 'feature' was added (for 2.2.x+ kernels?) that busts the initialization of the vadem chip in this case.

Thanks to all for help and advice. I hope this will save some others as much time as you all have saved me!

Thanks for a great tool-kit Dave!

--danno
Problems with Vadem VG-469 isa bridge


[ Add Message ]  to: "Problems with Vadem VG-469 isa bridge"

[ Members ]  [ Subscribe ]  [ Admin Mode ] 
[ Show Frames ]  [ Help for HyperNews at pcmcia-cs.sourceforge.net 1.10 ]