Networking :: linksys card not working



The tulip command should be successful.
If it fails, the next command (netcardconfig) will also not work.

Try doing this.  Post the output of these commands:

sudo su
lsmod
lspci -v
ok here we go

lsmod gets me

soundcore           3428         0  (autoclean)
mousedev           3832         0  (unused)
hid                      22372        0  (unused)
input                    3168        0   [mousedev hid]
af_packet          13544        0  (autoclean)
nls_iso8859-1    2844         0  (autoclean)
nls_cp437           4348        0  (autoclean)
agpgart               42660      0  (unused)
tulip                     38848      0
crc32                    2816      0  [tulip]
serial                   52100     0  (autoclean)
pcmia_core         39840     0
rtc                        7036      0  (autoclean)
cloop                    8740      2
ieee1394            183076   0
usb-storage       61696      0  (unused)
usb-uhci             21644     0  (unused)
usbcore             57600      1  [hid usb-storage usb-uhci]
ataraid                 6180      0
ide-cd                 28512     0
ide-scsi                8816     1

and for lspci -v the list was to long to write it all down so i just got the part about the nic

0000:00:0b.0   Ethernet controller :Linksys NC100 network everywhere fast ethernet   10/100  (rev 11)
        subsystem: linksys: unknown device 0574
        flags: bus master, medium devsel, latency 64, IRQ9
        I/O ports at 1400 [size = 256]
        memory at f4020000  (32-bit, non-prefetchable) [size=1k]
        expansion ROM at <unassigned>[disabled][size=128k]
        capabilities: [c0] Power management version 2
Hmm...

Looks like DSL already detected your card and installed the tulip driver for you, which explains why the modprobe command failed when we tried to load the driver a second time.

How about getting the output of:

sudo su

ifconfig -a
well i get

eth0   Link encap:ethernet HWaddr  00:03:6D:1D:34:EO
         broadcast multicast mtu:1500 metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:0 errors:12 dropped:0 overruns:0 carrier:24
         collisions:0 txqueuelen:1000
         RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
         interrupt:9 Base address: 0x1400

lo       link encap:Local loopback
         inet addr: 127.0.0.1  Mask: 255.0.0.0
         UP LOOPBACK RUNNING MTU: 16436 metric:1
         RX packets:2 errors:0 dropped:0 overrunns:0 frame:0
         TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:100 (100.0 B)  TX bytes:100 (100.0 B)
This means your network interface is present and accounted for.  You need the "eth0" in order to configure your networking.

So it appears that all of your hardware detection is correct, but your network settings or physical connection is wrong.

Are you sure that your network cables are good and they are plugged firmly into the sockets?

Are there any bent terminal wires inside the sockets?  They should all line up nicely just like a telephone jack socket.

Finally, do you know if networking works for other operating systems like Windows on this exact same computer?

If so, you will need to learn your Windows networking configuration so that you can copy it and use it with the DSL linux network settings.
Next Page...
original here.