On Sat, 01 Sep 2001 16:32:56 +0000, [EMAIL PROTECTED] wrote:
> 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?
In DOS all is obvious to me. I got a new card. I got a new disk.
Disk has directory PKTDRVR. The packet driver is a binary.
What more do I need except to know that I have to load it ?
In Linux one gets the IMPRESSION that the system should know all.
After all, during bootup it tells me all these things about my
hardware that I might not have known, and am certainly surprised
when it describes my HD in terms that I have to go to MAXTOR to
find. But even then the impression is mixed. There is always
this stupid message re: creating 16 4meg Ramdisks. All distros
I have tried say this I think. I only have 16 megs of memory. :((
>> 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
No. Well, it may BE there, but I didn't LOOK there. <g>
I was trying to see what it might be considering on boot up.
>> 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.
I shall do that on Sunday.
No number. At least not on the box. It's something like XTFE or XFTE or...
Maybe it says something more numberlike on startup - I'll have to look in
my DOS inet.log. Thanks for jogging my thought processor on that. <g>
>> 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.
Don't know the answer to that. Didn't try the NE driver as I had a
proper one for this new PCI 10/100 card. Isn't the NE driver old ?
Or does 2000 refer to the year ?
I'm reluctant to try to run it with say a DE600 driver. I'd rather
just change the card. :(
> 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.
I know the address of my card. Are you saying I could do:
modprobe de io=0x320 and be done, OR is that just an option
for the FIRST line ?
In which case I add: insmod de io=0x320 (maybe) ?
Thanks, Steven.
- Clarence Verge
- Back to using Arachne V1.62 ....
