Ethernet packet problems.
steve Shack
I've been having problems with getting networking to work correctly on
my minix box. The problem is that when I ping a host I get an error
dumped to the first console. It says that a packet was received with a
strange size (this size is always the same) I remember somone having
this same problem on the newsgroup but can't remember how it was fixed.
I have an (I believe) SMC8000 ethernet card which is detected by linux
as a 8013. I have correctly setup the port, irq and memory address and
have the memory size set to 2000 as I believe it has 4K of memory
(perhaps more I don't know). Does anyone have any ideas how to fix
this?
My feelings are that it is working correctly ( it obviously sends pings
out to my (linux) host and only has problems recieving them)
Will Rose
: Hello,
I had problems with 8013's under 2.0, tho' not the same problems; 2.0.2
fixed them all. You might try upgrading. The 8013's have 16K; your
best bet is to get the setup/test code from SMCs web site, and check out
the card settings and performance with that. (The version I have runs
under MSDOS). Finally, I've sometimes found that SMC cards need an
actual hard reset, not C-A-D, to come up in the right state.
steve Shack
>
> steve Shack <ssh...@cln.etc.bc.ca> wrote:
> : Hello,
> : I've been having problems with getting networking to work correctly on
> : my minix box. The problem is that when I ping a host I get an error
> : dumped to the first console. It says that a packet was received with a
> : strange size (this size is always the same) I remember somone having
> : this same problem on the newsgroup but can't remember how it was fixed.
> : I have an (I believe) SMC8000 ethernet card which is detected by linux
> : as a 8013. I have correctly setup the port, irq and memory address and
> : have the memory size set to 2000 as I believe it has 4K of memory
> : (perhaps more I don't know). Does anyone have any ideas how to fix
> : this?
>
> : My feelings are that it is working correctly ( it obviously sends pings
> : out to my (linux) host and only has problems recieving them)
>
> I had problems with 8013's under 2.0, tho' not the same problems; 2.0.2
> fixed them all. You might try upgrading. The 8013's have 16K; your
the details of the card on smcs website.
Badmuts
http://minix1.hampshire.edu/faq/strlnpaks.html
Steve Shack wrote in message <372F6754...@cln.etc.bc.ca>...
>> : I've been having problems with getting networking to work
correctly on
>> : my minix box. The problem is that when I ping a host I get an error
>> : dumped to the first console. It says that a packet was received with a
>> : strange size (this size is always the same...
Steve Shack
Really usefull especialy since I tracked down a 3c503 card and still
cant get minix tcp/ip working. After a little work i've found (from the
ethernet console dump) that packets are sent out but not received.
Stupid minix. or maybe stupid me. Anyway I checked the packets when they
get to my linux host ( a ip masq linux box connecting my computers to
the real internet) and they're getting there just fine.
Kees J Bot
Steve Shack <ssh...@cln.etc.bc.ca> wrote:
>
>Really usefull especialy since I tracked down a 3c503 card and still
>cant get minix tcp/ip working. After a little work i've found (from the
>ethernet console dump) that packets are sent out but not received.
>Stupid minix. or maybe stupid me. Anyway I checked the packets when they
>get to my linux host ( a ip masq linux box connecting my computers to
>the real internet) and they're getting there just fine.
This probably means that the IRQ is wrong. This shouldn't happen with a
3c503 though, because you tell the card what IRQ to use. (With WD8013
and NE2000 it is the other way around.)
Unless you've specified IRQ 2 on an AT. On an AT IRQ 2 is redirected to
IRQ 9, so you have to specify 9.
(If the IRQ is wrong Minix doesn't notice that packets are coming in.)
--
Kees J. Bot, Systems Programmer, Sciences dept., Vrije Universiteit Amsterdam
Albert S Woodhull
: .... After a little work i've found (from the
: ethernet console dump) that packets are sent out but not received.
: Stupid minix. or maybe stupid me. Anyway I checked the packets when they
: get to my linux host ( a ip masq linux box connecting my computers to
: the real internet) and they're getting there just fine.
This means you are using the wrong IRQ. Minix doesn't need to use
interrupts to send packets, but the driver tells the system it has
received a packet by generating an interrupt. You specify the interrupt
to use in the DPETH0 boot parameter, but the driver doesn't use this to
change the NIC's IRQ setting, nor can it determine whether the parameter
you have given it is correct.
Al
+-----------------------------------------------------------+
| Albert S. Woodhull -- PC Support Specialist |
| Office of Information Technology, PC Classroom Operations |
| University of Massachusetts, Amherst MA |
| phone: 413-545-1614 fax: 413-577-0749 |
| e-mail: wood...@oit.umass.edu |
| web page: http://www-unix.oit.umass.edu/~woodhull/ |
+-----------------------------------------------------------+
Steve Shack
>
> In article <37344AFC...@cln.etc.bc.ca>,
> Steve Shack <ssh...@cln.etc.bc.ca> wrote:
> >
> >Really usefull especialy since I tracked down a 3c503 card and still
> >ethernet console dump) that packets are sent out but not received.
> >Stupid minix. or maybe stupid me. Anyway I checked the packets when they
> >get to my linux host ( a ip masq linux box connecting my computers to
> >the real internet) and they're getting there just fine.
>
> 3c503 though, because you tell the card what IRQ to use. (With WD8013
> and NE2000 it is the other way around.)
>
> Unless you've specified IRQ 2 on an AT. On an AT IRQ 2 is redirected to
> IRQ 9, so you have to specify 9.
>
> (If the IRQ is wrong Minix doesn't notice that packets are coming in.)
> --
> Kees J. Bot, Systems Programmer, Sciences dept., Vrije Universiteit Amsterdam
After a little toying I solved the problem! The entire time I had the
minix network config setup correctly and the hardware setup correctly.
I went and played with the bios settings for shadow ram/rom and turned
off the shadow on that memory region. Bingo it works. and i'll have my
system up within a day or two. I'll let people know when that happens.
It'll be running a small bbs and mirror some of the minix sites.
Probably not actualy mirror but just copy it all of of others and put it
in a more sane file structure (rather than having 4 mirror dirs and
having to search through it all)