Networking is Notworking
Forum: Networking
Topic: Networking is Notworking
started by: UnDude
Posted by UnDude on Aug. 22 2004,00:50
Greetings,I have recently installed DSL 0.7.3 on my HD at hdb7. All of my peripherals appear to be working except for my network interface card.
I am running a Cyrix P166 CPU (P1-compatible) on a Tyan Tomcat III mobo with 128 MB RAM, Trident 96XX video card, Avance Logic ALS-007 sound card, and 33.6k hardware modem (I am writing this from DSL/Dillo while playing an audio CD).
My NIC is a Realtek RTL-8019 10base-T ISA card in jumperless mode set to IRQ=10 and I/O=0x340h, which works fine in all versions of Windows which I currently have installed (Win95OSR2, Win2000Pro, WinNT3.51Wks).
If I run netcardconfig from the DSLpanel, all I get is "No supported network cards found".
I added the following to the append line in my /etc/lilo.conf file, then ran lilo and rebooted:
ether=10,0x340,0,0,eth0
but I still have no ethernet.
Running the dmesg command echos the ether portion of lilo.conf's append line, but no further mention of the NIC appears anywhere in the text.
The ifconfig command returns info on only lo (local loopback) and ppp0 (if I've dialed out to the Internet).
Any suggestions?
Oh yes, another question: Is there a Linux command that displays which IRQs and I/O addresses are being used by which devices? I'm thinking that the Plug'n'Pray sound card or video card may have possibly hijacked the NIC's IRQ.
Posted by ke4nt1 on Aug. 22 2004,01:43
If it is truly in a "jumperless mode". that may be a "plug & pray" option in the card.Can you hard jumper the options ?
Have you disabled plug & pray in your bios?
Do you have a utility on floppy to change/check the settings?
A Realtek 8019 should be easy to manage...
A very common card..
Did you try "insmod ne io=0x340 irq=10"
Does " lsmod " show anything in it about your card?
And congrats on getting your hda7 DSL install working..
Your about to have some real fun now..
Just when you get it real sweet... DSL 0.8 will be out
73
ke4nt
Posted by cbagger01 on Aug. 22 2004,12:13
Jumperless mode is the correct mode.Try editing the append line in your lilo to add "noisapnp" and see if it works.
Otherwise, try this:
< http://damnsmalllinux.org/cgi-bin....=ne2000 >
Posted by UnDude on Aug. 23 2004,19:53
| Quote (ke4nt1 @ Aug. 21 2004,21:43) |
| A Realtek 8019 should be easy to manage... A very common card.. And congrats on getting your hda7 DSL install working.. Your about to have some real fun now.. Just when you get it real sweet... DSL 0.8 will be out |
Thanks on the congrats. I'm actually having some fun playing with this. Yeah, just when I get this figgered out, they'll come out with a new version.
I recall that the Realtek 8019 was a pretty popular card available at the local computer shows several years ago when I bought them for $15 each. It *should* at least be recognized as an NE2000-compatible.
Okay, here's the latest:
The command insmod ne io=0x340 irq=10 returns:
(long_path)/ne.o: unresolved symbol ei_open, ethdev_init, ei_interrupt, NS8390_init, and ei_close (on 5 separate lines).
The lsmod command shows nothing about the network card.
The commands:
sudo su
ifdown -a
modprobe ne returns:
(long_path)/ne.o: init_module: No such device or address
Adding "noisapnp" to /etc/lilo.conf's "append" line made no difference.
Booting into the PC's BIOS, I changed the PnP setting for IRQ 10 from "PCI/ISA PnP" to "Legacy ISA". This also made no difference.
The network card can be switched between PnP and Jumperless modes by moving a physical jumper. In Jumperless mode, you boot a DOS floppy and run a config utility to view or set the irq and i/o locations. I did this and verified that the settings are correct.
dmesg still shows nothing about the NIC beyond echoing the "ether" statement in lilo.conf's append line.
I did notice on bootup (this doesn't show in dmesg) that immediately after /etc/fstab is set up with the hard drive's partitions, something like:
modprobe: modprobe: Can't locate module minix
or something to that effect is displayed. I don't know what it means, but it doesn't look good.
At any rate, I'm still stumped.
Posted by cbagger01 on Aug. 23 2004,21:49
It sounds like you are doing all of the right things.Change ISA settings.
Disable ISA PnP.
Manually load the driver.
I assume that your card still works after all of this tweaking and MS Windows is happy.
The "unresolved symbol" message troubles me.
Can you try and see if you can load the "ne" module in a different version of Linux like
Tom's Root Boot Floppy
Feather Linux
Knoppix (boot with "knoppix 2" to save memory)
At least you will have a better idea if the card can be run in Linux, as opposed to a problem that may be specific to only the DSL livecd and not other Linuxes (or is it spelled "Linuces"?).
Good Luck.
Posted by UnDude on Aug. 24 2004,03:46
| Quote (cbagger01 @ Aug. 23 2004,17:49) |
| Can you try and see if you can load the "ne" module in a different version of Linux like Tom's Root Boot Floppy Feather Linux Knoppix (boot with "knoppix 2" to save memory) At least you will have a better idea if the card can be run in Linux, as opposed to a problem that may be specific to only the DSL livecd and not other Linuxes (or is it spelled "Linuces"?). Good Luck. |
Yes, all peripherals work fine in Windows 95 OSR2, 2000 Pro, and NT 3.51 Workstation. Once upon a time, I *may* have had Mandrake 9 running on this PC before I started playing around with NT 3.51. If so, I seem to recall everything working fine on it.
I do currently have Mandrake 9 installed on another PC with a Tyan Tomcat IV mobo and an identical Realtek RTL-8019 network card, which works fine in it. All other peripheral cards are different, though.
I dug up tomsrtbt 2.0.103, booted DOS, made a floppy, then booted tomsrtbt and logged in as root. dmesg reveals:
NE*000 ethercard probe at 0x340: 00 4f 4c 04 aa 63
eth0: NE2000 found at 0x340, using IRQ 10.
So... tomsrtbt sees the NIC!
I didn't try loading the "ne" module in tomsrtbt yet (it's getting late, Zzzz...), but I'm sure it will work -- I'll try that tomorrow.
Hmmm... Should I try yanking the sound card and booting DSL?
Posted by cbagger01 on Aug. 24 2004,16:21
If tomsrtbt can see it AND USE IT (try a "ping" to another box) then you don't have any hardware conflicts after booting linux so I doubt that removing your sound card will help.After this is complete, the next step is to try a knoppix-like Linux (Feather Linux, or Knoppix itself) to see if the problem is embedded into knoppix (DSL is based on knoppix) or is a problem that is specific to DSL itself.
It is possible that during the transmogrify-knoppix-into-dsl process an important file was accidentally deleted that could be restored in the next version of DSL or at worst case be manually restored via a myDSL extension, for example.
Good Luck.
Posted by UnDude on Aug. 24 2004,17:40
| Quote (cbagger01 @ Aug. 24 2004,12:21) |
| If tomsrtbt can see it AND USE IT (try a "ping" to another box) then you don't have any hardware conflicts after booting linux so I doubt that removing your sound card will help. |
Come to think of it, this sound card might be another one of those jumperless option models, where you boot a DOS floppy and run a config util to nail down the IRQs and I/O addresses -- I'll have to dig out the docs. So PnP interfering with the NIC's settings may not be a problem here.
In tomsrtbt, the route command displays two lines, both referencing eth0. I could ping localhost, but I could not ping any other PCs on the network. The LED on my hub which corresponds to this PC flickers with each ping, but I'm getting no echoes back.
I noticed that the ne.o module does not appear to exist in tomsrtbt. Is there any other NIC configuration I need to do in tomsrtbt? Bear with me, I still consider myself a linux newbie, and I don't know too many of the console commands.
Posted by UnDude on Aug. 24 2004,21:33
Hey, I just got ping to work in tomsrtbt.My network uses IP addresses in the 192.168.0.x range, so I had to change my tomsrtbt machine's addy.
ifconfig -a
showed my eth0 setup, and
ifconfig eth0 inet 192.168.0.3 netmask 255.255.255.0
set my tomsrtbt PC's address.
Pinging other PCs on my network now works!
I tried to mount a Windows share with the command:
mount -t smbfs -o username=name,password=pwd //serverIP/share /localdir
but tomsrtbt's mount doesn't support smbfs (no samba, I presume).
So... I guess the next step is to download and try a different Knoppix-derived Linux. For now, I'm limiting my CD burning to 74-min. CD-RWs, and Knoppix itself is too big to fit, so I'll try Feather Linux.
Posted by cbagger01 on Aug. 25 2004,01:37
Tom's kernel is probably created with the compiled in "ne.o" networking support, so that could explain why there is no "ne.o" file kicking around.dsl/knoppix kernels take a modular approach to networking so they require the "ne.o" driver file.
It will be interesting to find out if Feather Linux works.
Posted by UnDude on Aug. 25 2004,03:30
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?
ifconfig -a now shows eth0 --> WooHoo!
Let's configure our IP address:
ifconfig eth0 inet 192.168.0.3 netmask 255.255.255.0
Pinging other PCs on the network now works!
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?
Posted by ke4nt1 on Aug. 25 2004,04:45
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
ke4nt
Posted by cbagger01 on Aug. 25 2004,17:15
congrats 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.
Posted by UnDude on Aug. 25 2004,17:20
| 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!
Cheers,
UnDude