MorphOS PowerUP and PCMCIA network adapters

[humppa]

I finally managed to get hold of a 90 degree PCMCIA adapter for my towered A1200.

Is anybody of you using a PCMCIA network adapter (LAN or WLAN) with MorphOS Powerup? What are your experiences, which one should I get?
Is there any problem in using the 68k-drivers? Or are there even PPC-native PCMCIA-drivers available?

[Piru]

carddisk.resource is PPC native, and there's a PPC native cnet.device included.

68k drivers should work fine, aswell.

[humppa]

Thanks, I was first planning to get a 3Com Etherlink III, but I suppose that the 589-driver is only available as a 68k-version, so I would prefer your PPC-native cnet.device instead.

Is there a compatibility-list somewhere or does basically every NE2000-based card work?

[Piru]

The driver included should support the cards listed in the compatibility file inside my old(er) m68k version of cnet.device.

[humppa]

Hmm, finally got some time to install MOSnet 1.2 and plug in a 3com Etherlink III PCMCIA card, although I might later look for a NE2000/Cnet card. I used the 3c589-driver available on Aminet (68k-version).

I then configured MOSnet according to the Mosnet-guide with static IP settings.
Unfortunately, I get these errors when starting MOSnet:

"Fatal error in NetDB file interfaces at line 77, col 86
Memory exhausted
MOSnet will quit"

and

"Fatal error in NetDB file DH1:Internet/MOSnet/db/netdb at line 15, col 25
Memory exhausted
MOSnet will quit"

From Snoopium, I can see that MOSnet fails to open card.resource and bsdsocket.library, so there seems to be already a problem in recognizing my PCMCIA-card.

Did anybody ever successfully managed to run a 3Com PCMCIA-card with MOS PUP?
The 3c359-driver installs 3c589.device and pccard.library. Does the latter maybe conflict with card.resource?
Should I first check if the PCMCIA-card is properly recognized under OS3.9?

[Crumb]

Should I first check if the PCMCIA-card is properly recognized under OS3.9?

of course! :-)

[humppa]

Crumb wrote:

Should I first check if the PCMCIA-card is properly recognized under OS3.9?

of course! :-)

Hehe, ok, I just checked my 3Com PCMCIA-card with OS3.9 and it works absolutely fine (after setting the Mediator to 4MB memory window and putting a Cardreset-patch in the Blizkick-line).

But under MOS Powerup, MOSnet still fails to access the card or maybe even the whole PCMCIA-slot.

With Snoopium, I get
-OpenLib of bsdsocket.library Failed
-OpenDev DEVS:Networks/3c589.device Unit 0 Failed
and
-OpenRes card.resource Failed
-(OpenLib pccard.library Ver1 is OK)

So how should I proceed now? Is there any way to check if the PCMCIA-port has been properly initialised? I read somewhere that a Cardpatch (for the A1200 PCMCIA-bug) is not needed for Morphos.

In db/interfaces I use the following line:
eth0 DEV=DEVS:Networks/3c589.device UNIT=0 IP=192.168.178.10 NETMASK=255.255.255.0 UP

Any ideas?

[humppa]

 :bump:

So I still got these errors:

"Fatal error in NetDB file interfaces at line 77, col 86
Memory exhausted
MOSnet will quit"
"Fatal error in NetDB file DH1:Internet/MOSnet/db/netdb at line 15, col 25
Memory exhausted
MOSnet will quit"

Then I commented out the lines in "netdb" and the MOSnet gui finally came up.
However, I still can't ping my router although bsdsocket.library can finally be opened (Snoopium shows that V0 fails, but V3 of bsdsocket.library is "OK").

Any ideas?

[ncafferkey]

It seems a bit weird that card.resource can't be opened. card.resource has a function called (I think) OwnCard() that can fail if there's a problem with the PCMCIA slot or card, but the resource itself should always open. Can you check with some monitor program if the resource is present?

[humppa]

It seems a bit weird that card.resource can't be opened. card.resource has a function called (I think) OwnCard() that can fail if there's a problem with the PCMCIA slot or card, but the resource itself should always open. Can you check with some monitor program if the resource is present?

I just had a look with "Scout": Card.resource is NOT listed under the category "resources". However, the PCMCIA-slot IS working in AOS3.9 and card resource 40.4 IS listed under "resources".

This makes me wonder why the PCMCIA-slot is not properly initialised in MorphOS?

There might be just one "speciality" of my system: I still have a Mediator 1200 LT4 installed in it. However, I switched to the 4MB memory window to prevent a conflict with the PCMCIA-slot.
Until now, Morphos has been working flawlessly with the Mediator still installed (but not used).

But with this card.resource not showing up, it wouldn't even  make any sense to try it with a cnet.device compatible PCMCIA card.

Maybe I'll try to install the PCMCIA-patches in Morphos (although others have already stated that MOS already does this).
Another possibility would be to try using a Realtek 8029 with the Mediator (!) in MOS, since I remember that somebody here in the forums claimed that he got it running (not FastEthernet.device though, since it uses DMA).

Any ideas?

[itix]

But with this card.resource not showing up, it wouldn't even make any sense to try it with a cnet.device compatible PCMCIA card.

cnet.device always worked for me but it was three years ago.

Maybe I'll try to install the PCMCIA-patches in Morphos (although others have already stated that MOS already does this).

PCMCIA patches only fix reset bug in AOS.

[humppa]

itix wrote:

But with this card.resource not showing up, it wouldn't even make any sense to try it with a cnet.device compatible PCMCIA card.

cnet.device always worked for me but it was three years ago.

Ok, but would it work even when there is apparently no card.resource?
The next thing I might try is to completely unplug the Mediator, just to see if there is any conflict.

[Piru]

I just had a look with "Scout": Card.resource is NOT listed under the category "resources".

While you're playing with Scout, check Residents list. Is card.resource listed there? (it should be)

The only condition shutting down the card.resource is memory appearing overlapping the PCMCIA port.

[humppa]

While you're playing with Scout, check Residents list. Is card.resource listed there? (it should be)

Yep, it's listed there:
cardresppc 50.4 (11.5.02) by some guy called "Harry Sintonen".;-)  
There is also carddisk.device 40.1 (12.2.93).

MOSNet first fails at opening bsdsocket.library Ver 0, but then later succeeds at opening "Ver 3" of that library. Weird.

OpenDev 3c589.device and
OpenRes card.resource are both a failure - I tried both MOSNet and MiamiDX.

Do I have to edit anything in the "netdb" file of MOSNet? When I don't comment out the "I" entry (interface) I get the earlier mentioned "Error in column x line y".

Just as a guess - do you think it's rather a problem of the 3c589-driver or a real hardware-problem (e.g. conflict with Mediator)? Would it be worthwhile getting a cnet-based PCMCIA-card?

Anyway, thanks for the suggestions so far.

[itix]

Just as a guess - do you think it's rather a problem of the 3c589-driver or a real hardware-problem (e.g. conflict with Mediator)? Would it be worthwhile getting a cnet-based PCMCIA-card?

You are not the only having problem with 3c589 driver in MorphOS. It just fails to work. I once tried to look into driver source code but without having a hardware it is next to impossible to do anything about it.