Help with EtherNEC Mint, Magxnet, or Sting

[Crash]

I'm rusty, but still finding the process of getting Ethernet working to be extremely difficult. I'm using an EtherNEC adapter and card. My computer is an Atari Falcon030 with a CT60 accelerator.

The closest I could get to functioning was with Sting, where I could ping within my network router, but apparently could not communicate with the gateway or resolve. I could login to a local FTP server, but couldn't get any directory listings.

Because I could ping some machines and login to ftp, I assume that the card and cabling are working ok.

Magxnet shows no sign of being functional, and I can't determine any way to troubleshoot. I've followed the instructions that I can find, but it doesn't do anything I can detect.

Mint is what I'm working on right now, and have installed the Easymint distribution. The problem is that the device driver is probably not installed or configured correctly.

During configuration, I get prompted for the name of the interface, and it has ne0 entered. Other configuration files refer to both en0 and ne0, and I am guessing that only one of these are correct.

How can I verify that the network adapter is configured correctly?

The installation process prompted for the NIC driver, but didn't seem to do anything. I manually copied the driver to the /boot/modules/net directory, made it executable, and verified that is is listed with the drivers -a command.

I've entered a series of commands in the startup scripting with the ifconfig commands:

ifconfig en0 addr 192.168.1.3 netmask 255.255.255.0 up
route add 192.168.1.0
route add default en0 gw 192.168.1.1

I'm referring to the following document for guidance:

http://assemsoft.atari.org/rtl8139/files/lan_doc.txt

I have tried re-installing the entire Easymint package several times, while setting all of the references to the ethernet card to either ne0 or en0 - neither seems to work.

The enec3.xif driver that I am using has the string en0 inside it, so I assume this is the correct way to refer to this driver (as opposed to ne0, rtk0, etc...)

I still can't ping or anything else in Mint.

I would be thankful if anyone can recommend Mint compatible internet tools (ping, tracert, resolve, etc) that are not command line oriented. I do not wish to use command line software if I can use GEM driven programs instead.

It seems that each method of internet access (Sting, Magxnet, Mint(net) uses its own internet tools; is it correct that these cannot be used interchangeably with others (such as Sting Tracert with Mint)?

Does anyone have a working Ethernec?

Any suggestions or links would be greatly appreciated,

Crash

[FujiMan]

Hi,

Maybe check your DNS entries.

Is there some sort of DHCP for MiNT and TOS?

Should it be on a EasyMiNT installation?

This would probably fix about 90-95% of issues setting up a Atari on a network.

At this point, this stuff should just work...

FujiMan

I'm rusty, but still finding the process of getting Ethernet working to be extremely difficult. I'm using an EtherNEC adapter and card. My computer is an Atari Falcon030 with a CT60 accelerator.

The closest I could get to functioning was with Sting, where I could ping within my network router, but apparently could not communicate with the gateway or resolve. I could login to a local FTP server, but couldn't get any directory listings.

Because I could ping some machines and login to ftp, I assume that the card and cabling are working ok.

Magxnet shows no sign of being functional, and I can't determine any way to troubleshoot. I've followed the instructions that I can find, but it doesn't do anything I can detect.

Mint is what I'm working on right now, and have installed the Easymint distribution. The problem is that the device driver is probably not installed or configured correctly.

During configuration, I get prompted for the name of the interface, and it has ne0 entered. Other configuration files refer to both en0 and ne0, and I am guessing that only one of these are correct.

How can I verify that the network adapter is configured correctly?

The installation process prompted for the NIC driver, but didn't seem to do anything. I manually copied the driver to the /boot/modules/net directory, made it executable, and verified that is is listed with the drivers -a command.

I've entered a series of commands in the startup scripting with the ifconfig commands:

ifconfig en0 addr 192.168.1.3 netmask 255.255.255.0 up
route add 192.168.1.0
route add default en0 gw 192.168.1.1

I'm referring to the following document for guidance:

http://assemsoft.atari.org/rtl8139/files/lan_doc.txt

I have tried re-installing the entire Easymint package several times, while setting all of the references to the ethernet card to either ne0 or en0 - neither seems to work.

The enec3.xif driver that I am using has the string en0 inside it, so I assume this is the correct way to refer to this driver (as opposed to ne0, rtk0, etc...)

I still can't ping or anything else in Mint.

I would be thankful if anyone can recommend Mint compatible internet tools (ping, tracert, resolve, etc) that are not command line oriented. I do not wish to use command line software if I can use GEM driven programs instead.

It seems that each method of internet access (Sting, Magxnet, Mint(net) uses its own internet tools; is it correct that these cannot be used interchangeably with others (such as Sting Tracert with Mint)?

Does anyone have a working Ethernec?

Any suggestions or links would be greatly appreciated,

Crash

[Crash]

Part of my problem was that I was trying to use the wrong driver, which was causing it to work but with errors. Aside from this, I tried several of the ways to install Easymint, but it seems that this can cause confusion.

I'm currently using Xaaes, Teradesk, and Easymint 1.16 kernel and full installation. I would like to figure out how Xaaes is launched and try MyAES, but so far I can't figure this one out. It's not in the Mint.cnf where I would expect.

Both Sting and Mint(net) are working now, so I'm quite pleased.

Cheers!

[christos]

Well,
To install MyAES you need to give up login and start with init. It's all described here

[Crash]

Greetings,

I am sorry to say that I don't know what you mean.

I don't know how to give up login.

My Mint.cnf has the line INIT=u:\sbin\init

Is this correct?

I tried to follow the instructions on that page, although they do not correspond with the Myaes distribution I am using. Maybe this refers to an old distribution?

For example, the instructions say that gemsys directory and install.txt file need to be copied to the gemsys/myaes folder, but there is no install.txt and no Gemsys folder in the MyAes archive.

--
After depacking you get a folder named myaes, there you will find a folder gemsys and two files, 'install.txt' and 'myaes2.tos'. Copy the content of the gemsys folder to C:\GEMSYS and copy the file 'myaes2.tos' to C:\GEMSYS\MYAES. After that you have to edit the C:\GEMSYS\MYAES\MYAES.CNF and change it to your needs.
For starting MyAES automatically after rebooting, edit the file /etc/ttytab and create a new line under the block with the 'console' lines, or copy one of the 'console' lines and put it to the end of the block. The line should look like this:

console "/c/gemsys/myaes/myaes2.tos" stv52 on secure

After commenting out the old active 'console' line, configuration is finished. After a reboot MyAES should start automagically.
--

I made the changes that I could, but now Mint stops during the boot process. Any suggestions would be greatly appreciated.

Crash