Next-in-Thread Next Message

None wvlan_cs fails on startup with "Resource temporarily unavailable" 

Forum: PCMCIA Wireless Network Adapter Issues
Date: 2000, Jul 21
From: Bob Cook bcook

My configuration includes the WaveLAN in an ISA adapter plus two ethernet cards (eth0 and eth1) and I expect the WaveLAN card to become 'eth2'. So far I've had no luck with either wvlan_cs or wavelan2_cs for drivers.

Note that this is a brand-new card and I don't really have another way to test if its good or not.

 kernel: Linux PCMCIA Card Services 3.1.17
 kernel:   kernel build: 2.2.12-20 #3 Fri Feb 25 23:42:22 PST 2000
 kernel:   options:  [pci] [cardbus]
 kernel: Intel PCIC probe:
 kernel:   Vadem VG-469 rev 00 ISA-to-PCMCIA at port 0x3e0 ofs 0x00
 kernel:     host opts [0]: none
 kernel:     host opts [1]: none
 kernel:     ISA irqs (scanned) = 3,4,5,7,11,15 status change on irq 15
 cardmgr[9171]: starting, version is 3.1.17 cardmgr[9171]: watching 2 sockets 
 kernel: cs: IO port probe 0x0c00-0x0cff: clean.
 kernel: cs: IO port probe 0x0800-0x08ff: clean.
 kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x3b8-0x3e7
 cardmgr[9171]: initializing socket 0
 kernel: cs: memory probe 0x0d0000-0x0dffff: clean.
 cardmgr[9171]: socket 0: Lucent Technologies WaveLAN/IEEE
 cardmgr[9171]: executing: 'modprobe wvlan_cs port_type=3 eth=1' 
 kernel: wvlan_cs: WaveLAN/IEEE PCMCIA driver v1.0.4
 kernel: wvlan_cs: (c) Andreas Neuhaus <andy@fasta.fh-dortmund.de>
 cardmgr[9171]: get dev info on socket 0 failed: Resource temporarily unavailable 

Thanks for any hints or suggestions.

Next-in-Thread Next Message

Messages Inline: 0 1

More does HCF_ERR_NO_NIC mean bad hardware?

Re: None wvlan_cs fails on startup with "Resource temporarily unavailable" (Bob Cook)
Date: 2000, Jul 26
From: Bob Cook bcook

Thanks to Dave Hind for the suggestion for my previous problem (I had conflicting information in my config files). That change now allows me to get the wvlan_cs driver started although it still won't initialize properly.

In wvlan_hcfio.c, the hcfio_string() function, on line ~346 there is a test of memory. Specifically there is a test at the ioport+0x28 for the bytes 0x7d37.

This test fails on my setup. It finds either 0xFFFF (on the first attempt) or 0x0000 on successive attempts.

I'm suspicious of believing the pcmcia card is faulty because I've gotten it to successfully initialize under Win98 and in a Mac. I don't have a way to verify my ISA bridge, but it seems to function ok because the card insertion is detected and recognizied.

By the way, I should mention that I'm running this on an old 486 box. This shouldn't make any difference but I wonder about bus speeds (its an AT bus) or something. I don't know enough about this sort of thing to be knowledgable but I'm certain I'm not the first to try this sort of thing and I can't seem to find references of anyone else having such problems.

TIA for any assistance or suggestions.

None A shot in the dark

Re: More does HCF_ERR_NO_NIC mean bad hardware? (Bob Cook)
Date: 2000, Jul 26
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I don't have experience with this specific card, but I'd try bumping
it to another IO port range (exclude 0x100-0x13f in your config.opts
file) just in case this is a conflict with some other device.

-- Dave

Feedback No luck... Where can I get details about the WaveLAN?

Re: None A shot in the dark (David Hinds)
Date: 2000, Jul 28
From: Bob Cook bcook

I've tried fiddling around with various ioport and interrupt combinations and nothing seems to help this problem.

I definitely can see that the driver is unable to read data from the wavelan card although it appears that the ISA->PCMCIA bridge is working (card identity is known, insert/remove events are registering). This is probably some sort of issue with bus timings on my crappy old h/w; of course I know nothing about this sort of stuff but I guess I'll get my hands dirty as I go (advice appreciated).

This theory is sort of confirmed via my earlier attempts at using the Lucent binary driver (wavelan2_cs). It would complain about events not occuring within a specific time. Unfortunately I don't have the exact error message text and since its only a binary driver (and I can't hack on it very easily) its hard to want to spend any more time with it.

I need to get a data sheet or other docs that describes programming the WaveLAN IEEE. I've been unable to find one but I'm *sure* there must be one available.

I'll also need some information about how the ISA->PCMCIA bridge works; I guess this is wrapped up in the i82365.c file somewhere?

Is there anyone else having similar problems with the WaveLAN IEEE card using an ISA->PCMCIA bridge? Maybe we can pool information to figure out why it works for everyone else but us... :^)

Any hints on hacking the wvlan_cs driver? Don't be shy, please pass them along.

More On Andy's page...

Re: Feedback No luck... Where can I get details about the WaveLAN? (Bob Cook)
Date: 2000, Jul 29
From: Jean Tourrilhes jt

  Hi,

  I can understand your frustration. It seem that the Pcmcia adapter from Lucent are a big source of trouble, we have many instance of them not working the way they should under Linux or Windows.
  For the spec of Pcmcia, I would start in the Pcmcia Howto.

  For the spec of the Wavelan, Lucent has published a very short document. It's almost useless, and looking in the driver is uselly more useful, anyway it's on Andy's page :
http://www.fasta.fh-dortmund.de/users/andy/wvlan/

  Now, if you are hacking the driver, you may want to synchronise with the others doing it, in particular Harald and Benjamin. Check details on my web page :
http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Wavelan-IEEE.html

  Good luck !

  Jean

Question Some questions about your message

Re: More On Andy's page... (Jean Tourrilhes)
Date: 2000, Jul 29
From: Bob Cook bcook

> I can understand your frustration. It seem that the
> Pcmcia adapter from Lucent are a big source of trouble,
> we have many instance of them not working the way they
> should under Linux or Windows.

Do you mean to say that the ISA->PCMCIA boards are faulty? Or did you mean that the current versions of the driver(s) have difficulty with these boards?

Can you recommend a better ISA->PCMICA board? This one was not very expensive and I'd be happy to spend money for one that would work...

> Now, if you are hacking the driver, you may want to
> synchronise with the others doing it, in particular
> Harald and Benjamin. Check details on my web page :
> ttp://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/
> Wavelan-IEEE.html

Will do. Thanks for putting together a very good web page on this subject!

> Good luck !

Thanks, looks like I'll need it. :^)

Sad Hum...

Re: Question Some questions about your message (Bob Cook)
Date: 2000, Jul 31
From: Jean Tourrilhes jt

  The Pcmcia package doesn't interact well with those adapters and the machine BIOS. I think you can't pin-point the blame on one, but usually the software is supposed to work around the hardware...

  Jean

None The PCI->PCMCIA adapters are the tricky ones

Re: Question Some questions about your message (Bob Cook)
Date: 2000, Jul 31
From: David Hinds <dhinds@pcmcia.sourceforge.org>

On Fri, Jul 28, 2000 at 10:43:14PM -0700, Bob Cook wrote:

> Do you mean to say that the ISA->PCMCIA boards are faulty? Or did you
> mean that the current versions of the driver(s) have difficulty with
> these boards?

The ISA->PCMCIA boards are not troublesome; the PCI->PCMCIA boards are
troublesome.

-- Dave
wvlan_cs fails on startup with "Resource temporarily unavailable"


Add Message to: "wvlan_cs fails on startup with "Resource temporarily unavailable""

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