Clarence Verge wrote:
>
> dmesg | grep eth0 comes up blank.
Right. Your network card is not activated.
> How the heck I might know the module name
> for my card is beyond me.
--------------------------------------------
http://homepages.ihug.co.nz/~ichi/ether.html
--------------------------------------------
BTW, you would have exactly the same problem in DOS.
How the heck do you know which packetdriver to use
for your card?
> I browsed many files and finally found a list
> of possible modules that could be installed
> (I think I found it in sysinit or initsys)
/lib/modules/2.x.xx/net
> At any rate, I found a few Dlink numbers in there but they didn't
> seem to have mine so I went to the Dlink disk and glory be -
> a Linux subdir. Arrrggghhh. The damn thing is a SOURCE file.
It would help if you told us the number of your Dlink.
> Please don't tell me how nice it is that I can change the
> source - is it possible that someone could produce the binary
You should find a suitable module in /lib/modules/2.x.xx/net.
I would start with a DE one (if there is one that matches your
number). Otherwise, I would try ne. BTW does your Dlink work
with the ne2000 DOS packetdriver? If so, you could have made
things easier by mentioning that at the beginning. The DOS
packetdrivers and the Linux modules are pretty comparable.
To activate a NE2000-compatible network card:
------------------ --------------------
insmod 8390 == OR == modprobe ne io=0x320
insmod ne io=0x320 --------------------
------------------
0x320 is the address of my NE2000 card. Change it if
the address of your card is different.
Cheers,
Steven
