Amiga.org
Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: skurk on August 28, 2007, 09:48:18 PM
-
Hi, folks. Bit of a ramble here, so try to keep up. The victim on the crime scene is a vanilla A600HD, kick 3.1. No other fancy stuff.
Just got a new (used) card, NetGear MA401, which should be supported by the prism2.device. Yes, it's on the list.
After installing prism2.device to devs:networks and HermesII in devs:firmware (just to be sure), I rebooted.
In the early startup menu, the network card is not reported in the Expansion Board Diagnostics. Should it be there? Nah, continuing.
Rebooted and started installing AmiTCP. Next up is that I can't choose the prism2.device from the list of available network adapters. "That's ok", I thought to myself, "I can edit AmiTCP:db/interfaces later."
Yada-yada, finished the installer, just like I did on the A4k/XSurf. Then I added the following line to the said file:
PRISM2 DEV=Devs:Networks/prism2.device UNIT=0
Tried to start AmiTCP:bin/startnet, but got the error message "AmiTCP couldn't be started!". Oookaay, so it wasn't as easy as the XSurf. Time to investigate.
So I tried to "online" the card manually:
3.sys:> amitcp:bin/online prism2
S2_ONLINE: Inappropriate state (Unit not configured)
Meeh. But the NetGear LED starts flashing immediately afterwards, so *something's* happening.
Oh, maybe it's because I haven't set the card defaults yet. Let's give it a go:
3.sys:> setprism2defaults SSID=wifinet NOKEY MANAGED CHANNEL=6
Tried to run startnet and online afterwards, same results. No go.
Rrghh. Tried with multiple reboots, tried unplugging and re-inserting the card after boot (a manual "cardreset") and even UNIT=1 in the interfaces file, just for the heck of it. Tried renaming the card from "prism2" to "en0", "eth0", no go.
Any ideas, folks? What did I miss here? The PCMCIA slot is working nicely, copied tons of files from the Mac using a Compact Flash adapter.
-
I think putting a number at the end of an inteface name might cause problems in AmiTCP. Try naming it prism.
-
No, I doubt that's it. The examples in AmiTCP:db/interfaces are all named like adriana0, ppp0, etc.
I will give it a try when I get home from work anyway.
-
The examples in AmiTCP:db/interfaces are all named like adriana0, ppp0, etc.
Yes, but they are all wrong resp. for an older version of AmiTCP.
For the current version of AmiTCP (3.6 IIRC) db/interfaces has to be
prism dev=devs/networks/prism2.device
And for ifconfig you use prism0 to get prism2.device unit 0. I needed some time to figure this out, too.
Have a look here: http://thomas-rapp.homepage.t-online.de/download/makenetboot
The script creates a bootable floppy disk with network access to a Samba or Windows share.
Bye,
Thomas
-
Gosh darn it, you guys were right.
AmiTCP:db/interfaces had to say
prism dev=devs:networks/prism2.device
...and ifconfig had to use prism0 for unit 0. But that wasn't all, though. My AmiTCP 4.1 wouldn't start, so I had to download 4.0-demo. It worked fine there, so I can live with that for a while.
Thanks again, guys!