Why is my PCMCIA NIC not working?

[PiR]

I don't get it.

I've bought it this week. It is 3com EthernetIII, 562D/563D. And it should be handled by 3c589.device, acording to the manual.

I've installed AmiTCP 2.3, and 3c589.device and made a connection with crosslink cable to a PC.
Connection was established (LED), and my routing tables were configured (I could ping localhost, for example).

But, when I tried to ping the other site I could see NIC LED on PC blinking, but no reaction on Amiga side. The same results the opposite way.Then I've tried to install AmiTCP 3.0b2 and it went mad, it didn't set any routing, every ping was answered with 'no route to host', so I've returned to 2.3
For me it looks, like Amiga is able to send, but does not receive anything.

I've checked the cable on different NICs - it is ok.
I've checked the 3com on notebook - it is ok.

I have Amiga1200 with OS3.0 and BPPC'60.
Any help is very welcome and desired.  :-)

Thanks in advance.

[ncafferkey]

I have had one report of this model not working with 3c589.device. In that case it didn't seem to be giving interrupts to the Amiga. The owner of that card is going to lend it to me in the coming weeks, so maybe I 'll be able to make it work.

Has anybody else been able to use this card successfully with an Amiga?

[PiR]

Are you mayby the author of the stuff?
Hey, thanks!
Does it mean that we are doomed?
No interrupts means, well, no good.
Is active polling the only option? :-(
Or mayby it is possible that some initialization will help? But, on the other hand it was was working with PC.

I don't know if this maters, but my card is a combo: NIC+modem.

All the best with your usefull work.
 :-)

[ncafferkey]

PiR wrote:
Are you mayby the author of the stuff?
Hey, thanks!
Does it mean that we are doomed?
No interrupts means, well, no good.
Is active polling the only option? :-(
Or mayby it is possible that some initialization will help?

That's what I'm hoping, but it might be unlikely :-(

But, on the other hand it was was working with PC.

But then the A1200's PCMCIA slot isn't exactly standard.

I don't know if this maters, but my card is a combo: NIC+modem.

It shouldn't be a barrier to getting it to work, but it's possible the driver might need to be updated to handle this model. My own card is a combo too, although a different model.

All the best with your usefull work.
 :-)

Thanks.

[fragment]

One little thing. The 3c589 device doesn't support LED blinking.. yet  :-)

Is the card configured as a SANA-II driver and driver points to "networks/3c589.device" and unit 0? Try running "prepcard" from Tools. Does it give the productinfo?

I have 589D and have used it with AmiTCP 3.0, 4.22 and Miami without problems.

[PiR]

Hi

@ncafferkey
So, you're the guy!
Thanks again for this and for supporting source codes. Unluckilly It appeared that I don't have SANA-II headers...
But I have looked though the sources this weekend (both 3C589 and pccardserial) and found them quite simmilar. So why couldn't it be integrated for combo PCMCIAs? I mean, I've read that its not possible because of card.resource limitations, but I don't see the reason.
Ok, not possible to have two drivers, sure, but single driver to work both as 3c589 and pcserial - why not?
I was also looking through these sources - The initialisation checks if the card is serial-compatible device by PRODUCT_INFO. 3c589 does it also, but for different device (562 or 589, if I'm correct).
Can multile function card be identified as both then? I mean the same byte canot have two values at the same time. Does it mean I won't be able to use modem, as 3c589.device has recognized it?

One more small thingy - On initialisation function one FreeTupTagsList (I'm affraid I forgot exact word) is missing, for card identification (function from pccard.library). I'll mail you exact details.
Unluckilly without SANA headers I won't be able to compile it.
By the way - where do you have that info about EtherlinkIII from? It's so precise. Don't tell me it's just your intuition. ;-) The same for PCMCIA itself. The same for UART...

And by any chance the same person wrote also pcmcia.library itself. Pretty impresive activity. Really, and thanks again. If I can help you anyhow - let me know.

@fragment

The 3c589 device doesn't support LED blinking.. yet

I know. It was only PC that was blinking.  :-)

Is the card configured as a SANA-II driver and driver points to "networks/3c589.device" and unit 0?

Yes

Try running "prepcard" from Tools. Does it give the productinfo?

Well It does complain about it as memory card, so I think its not bad.
However the identification string looks good.

I could't make 3.0 installation working. I gave up till now.

[chris]

fragment wrote:
One little thing. The 3c589 device doesn't support LED blinking.. yet  :-)

The card I have doesn't have a blinking LED, even using the Windows drivers, it only lights up to show the link.

If it could be made to blink to show activity, that would be cool...

Chris

[PiR]

The card I have doesn't have a blinking LED, even using the Windows drivers, it only lights up to show the link.

Ok, I was unclear.
Mine was not blinking even, when inside PC.
When I had it on Amiga and tried to ping, the other side (PC) was blinking.

I don't think that it is possible to configure the card to blink on activity. I guess card just does not support it.

Cheers

[ncafferkey]

Thanks again for this and for supporting source codes. Unluckilly It appeared that I don't have SANA-II headers...

They're on the developer CD if you have it.

But I have looked though the sources this weekend (both 3C589 and pccardserial) and found them quite simmilar. So why couldn't it be integrated for combo PCMCIAs? I mean, I've read that its not possible because of card.resource limitations, but I don't see the reason.
Ok, not possible to have two drivers, sure, but single driver to work both as 3c589 and pcserial - why not?

It might be possible to have a combined driver, but IMO it'd be a messy solution. The only disadvantage of the current solution is that you can't use the modem and NIC at the same time. Also, there are NE2000-compatible combo cards, so you could end up with cnet.device mixed in too!

I was also looking through these sources - The initialisation checks if the card is serial-compatible device by PRODUCT_INFO. 3c589 does it also, but for different device (562 or 589, if I'm correct).
Can multile function card be identified as both then? I mean the same byte canot have two values at the same time. Does it mean I won't be able to use modem, as 3c589.device has recognized it?

Combo cards should have multiple tuple chains, but card.resource doesn't support examining them. So the easiest way to identify combo cards is to look at the manufacturer and product codes (and include the codes of compatible cards in the driver).

By the way - where do you have that info about EtherlinkIII from? It's so precise. Don't tell me it's just your intuition. ;-) The same for PCMCIA itself. The same for UART...

3Com has programmer docs for most of their cards on their website. Information on PC-type UARTS is available in a lot of places, including text books and manufacturers' data sheets.
[/quote]