Networking :: Networking is Notworking



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?
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.
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.
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.
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.
Next Page...
original here.