SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
As the title says, my network won't be able to work.
The installer autodetects de4x5. After I installed the PC and using netconfig to set up my network correctly (my router doesn't use a DHCP so I'd to set up it manually) it still doesn't work.
The light on my isn't burning, when using ifconfig I see that there are 20 errors
eth0 Link encap:Ethernet HWaddr 00:50:8B:4C:03:74
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:20 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:11 Base address:0x2000
(This is an error I found that's the same as mine except that I'm using the following configuration:
IP 192.168.2.3
Subnetmask 255.255.255.0
gateway 192.168.2.1
nameserver 192.168.2.1)
So I thought it might be the driver that's incorrect... I googled on the pc (a Compaq Presario 5686) And saw that I wasn't the only having problems. The PC is using a DS21143 NIC, and should use tulip (not de4x5),
so I configured /etc/rc.d/rc.modules, commented the area where it's searching what driver you had configured during install (in my case it was the de4x5) and decommented the line /???/modprobe tulip.
Then I rebooted the PC and still had errors when I looked at ifconfig.
route -n gives:
Dest gateway mask flags Iface use
192.168.2.0 0.0.0.0 255.255.255.0 U eth0 0
127.0.0.0 0.0.0.0 255.255.255.0 U lo 0
0.0.0.0 192.168.2.1 255.255.255.0 UG eth0 0
I can ping 192.168.2.3
I can't ping my router (or any other device thats in the network)
192.168.2.1 (my router) it's set up to reply to a ping... so that won't be the problem...
PING 192.168.2.1 (192.168.2.1) from 192.168.2.3 : 56(84) bytes of data.
>From 192.168.2.3: Destination Host Unreachable
>From 192.168.2.3: Destination Host Unreachable
Like i said... I think my NIC is the problem (It's working in win 98 so it isn't broken) not the configuration
Hmmm... According to the de4x5 documentation, that driver supports several chipsets including DC21143. Although yours was typed with an S, the similarity is striking... and since the driver was loaded automatically in the first place, I'd try those commands again with the original driver (de4x5) loaded instead of tulip.
I've configurated that one before... But when I found out that the de4x5 doesn't worked, I tried tulip (that also supports the DS21143 (You are talking about a DC don't know if it's a typo, b.c. I'm talking about a DS21143)) that supports this card (also?).
By the way, in installation (NETWORK command) if I skip the de4x5 It comes with tulip as working driver...
I also installed it 6 times (3 times with the de4x5 and 3 times with the tulip) but de4x5 AND tulip gives:
eth0 Link encap:Ethernet HWaddr 00:50:8B:4C:03:74
inet addr:192.168.2.3 Bcast:192.168.2.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:20 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:11 Base address:0x2000
I can't ping (except my own IP and 127.0.0.1) and my routers LED isn't burning (so there is no connection between my NIC and router)
Indeed, it looks like the connection between your NIC and the switch is not working. That could mean a faulty cable, or a handshake mismatch, or the network connector has burnt out... etc..
The eth0 interface itself seems to be functional. The problem appears not to be Slackware related.
LAN is working on windows 98... so I think there is nothing damaged on my NIC.
So I've tested it with an other LAN cable (cat 5 only 1 meter long... so that should not give any data losses). This cable is working on my other linux pc so should work.
Tested it with both drivers (de4x5 and tulip) both not working
ethtool eth0
Settings for eth0:
No data available
mii-tool:
eth0: no link
Edit:
The LAN Cable I used is also working... (checked it on an other PC)... I could ping my router without packet losses...
Command line arguments are now allowed, similar to passing arguments
through LILO. This will allow a per adapter board set up of full duplex
and media. The only lexical constraints are: the board name (dev->name)
appears in the list before its parameters. The list of parameters ends
either at the end of the parameter list or with another board name. The
following parameters are allowed:
fdx for full duplex
autosense to set the media/speed; with the following
sub-parameters:
TP, TP_NW, BNC, AUI, BNC_AUI, 100Mb, 10Mb, AUTO
Case sensitivity is important for the sub-parameters. They *must* be
upper case. Examples:
insmod de4x5 args='eth1:fdx autosense=BNC eth0:autosense=100Mb'.
So, you could try what happens if you force the driver to use 10Mbit by adding this to /etc/modules.conf (assuming you're using a 2.4 kernel:
Code:
options de4x5 args='eth0:fdx autosense=10Mb'
ans see if that helps. Try other mixes of driver arguments if the above line does not fix it.
options de4x5 args='eth0:fdx autosense=10Mb'
works
I'm sorry to resurrect an old thread, but this sounds like a solution for my predicament too (on the same model, Compaq Presario 5686). However, I'm using Puppy Linux 4.2.1, which uses kernel 2.6 and therefore modprobe.conf instead of modules.conf.
Just copying the "options" line above to /etc/modprobe.conf didn't work; instead, it prevented the Puppy Linux network wizard from detecting my network card. Could somebody please tell me how to make the equivalent change in modprobe.conf? Is there a way to test such settings without having to reboot the computer? Any help is greatly appreciated.
This is a Slackware forum. Please take your Puppy Linux question to the Puppy Linux forum and next time, do not resurrect a thread that has been dead for nearly four years.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.