Well, guess what? I finally got ethernet working in DSL.
While waiting for Feather Linux to download, I thought I'd try something by booting DSL 0.7.3 from CD instead of from the HD. dmesg now shows two interesting lines which do not appear when booting DSL from hdb7:
kmod: failed to exec /sbin/modprobe -s -k nls_iso8859-1, errorno = 2 ne.c: You must supply "io=0xNNN" value(s) for ISA cards.
Hmmm...
modprobe -c shows: alias eth0 off
Let's try this: modprobe ne io=0x340
No error messages were returned, so maybe this activated the network card?
Next, I booted DSL from the HD, entered the same modprobe and ifconfig commands, and -- lo and behold -- pinging works again.
So... it looks like this command is the key: modprobe ne io=0xNNN
Where would be the best place to put this command so that it is automatically run on bootup? Also, is there a config file that can automatically set my IP address and netmask?I thought we had suggested that solution earlier in this thread?
Place your modprobe line in your bootlocal.sh file Save it, for your HDInstall,
or make sure the bootlocal.sh file is in your filetool.lst for your LiveCD backup..
Good Work!
73 ke4ntcongrats on getting networking to work.
Take ke4nt's advice. Put the commands in your bootlocal.sh file (I think it's in /opt/ directory) and save the file for your hd install disk.
For your livecd use, you can use the standard livecd backup/restore method that involves the filetool.lst editing. Check out the DSL getting started and howtos for more details.
Also, check out the link that I posted at the beginning of the thread. It refers to command and to a network configuration script called "netcardconfig". Once you have your card driver loaded up and your ifconfig running, netcardconfig can be used to configure the IP address and other related stuff.
Quote (ke4nt1 @ Aug. 25 2004,00:45)
I thought we had suggested that solution earlier in this thread?
Hmmm, I had tried these two previously suggested commands:
insmod ne io=0x340 irq=10 and modprobe ne
neither of which worked.
But now, after rereading the alternate thread referenced by cbagger01, I see the command:
modprobe ne irq=10 io=0x300
For some reason, I apparently missed that one the first time through.
Oh well, maybe it's time for some new eyeglasses.
At any rate, I'm happy to have it working now, and I'd like to thank you guys for all your help!
