-   Slackware (
-   -   Slackware ethernet card error (

punchagan 05-13-2007 11:55 PM

Slackware ethernet card error
I am a newb using Slackware 11 for about 2 months now. It was working great until one day i encountered these errors in the boot up:

/etc/rc.d/rc.inet1:line1:eth_up: command not found
/etc/rc.d/rc.inet1:line2:eth_up: command not found
/etc/rc.d/rc.inet1:line255:eth_up: command not found

Now, I am unable to activate my ethernet card. I cannot connect to the network. Also, the boot is taking very long with long waits for starting sendmail daemon.

What could be the possible reason for this?
I suspect a burn-out of my network card. Is this possible? Any other causes?

[I tried Knoppix (live) to connect to the internet, but that failed too.]

MS3FGX 05-14-2007 12:47 AM

It appears that your boot scripts have been modified somehow. "eth_up" does not appear anywhere in the default rc.inet1 script, though it was used in Slackware 10.1 and previous, as I recall. Somehow you have it being referenced in your Slackware 11 system, which simply will not work.

You will likely want to reinstall the tcpip package from the Slackware CD (or from a mirror online) to replace the file with the correct version.

ak-87 05-14-2007 03:44 AM

Yes, somehow your rc.inet1 was modified. I've checked now my rc.inet1 and there is no eth_up in the whole file. If you are not using sendmail, simply turn that service off -

#chmod -x /etc/rc.d/rc.sendmail
. Maybe the best solution is to check if there is any backup file left in your /etc/rc.d (i.e. rc.inet1~) or to reinstall network packages.

Also try this:

#ifconfig eth0 up

david_ross 05-15-2007 12:11 PM

Moved: This thread is more suitable in Slackware and has been moved accordingly to help your thread/question get the exposure it deserves.

I would suggest reinstalling the tcpip package to reset your rc.inet scripts.

Alien_Hominid 05-15-2007 03:26 PM

Stop. I believe you don't need to reinstall.
Firstly run netconfig (you should run as root from terminal). I had these errors earlier in Slack 10.2 until I heavily modified my system. However I don't know which thing caused them. But they didn't break my network connection so they shouldnt have broken yours.

Sendmail hangs up because it waits until it gets response that connection to outside world is available.

MS3FGX 05-16-2007 08:19 AM

There really isn't any reason not to just reinstall the tcpip package if he is getting errors with his boot scripts. Assuming he has not modified them (and apparently he has not) it isn't like there is anything he will lose.

Michielvw 05-16-2007 08:47 AM

Might just be me, but why people are going on about sendmail ;) But I think his rc.inet1 is pretty screwed up. Have a look at the errors it reports.

My rc.inet1 just begins with
1: #! /bin/sh
2:# /etc/rc.d/rc.inet1

So, I am leaning towards the fact that something really did screw up his rc.inet1.

Alien_Hominid 05-16-2007 10:10 AM

I have had these same errors in the same lines. They didn't do anything else except these errors.

MS3FGX 05-16-2007 02:55 PM

I'm not sure what that is supposed to mean, really. You aren't supposed to have any errors with your operating system (well, unless you are using Windows), anything that can be fixed should be fixed.

Alien_Hominid 05-17-2007 03:55 AM

I know, you're right. But this error is similar to the wrong placed echo.
I've searched for it, but haven't found and somehow later it was gone.

Talking about errors, you can always press alt+ctrl+f1 and check how many errors KDE or Gnome gives.

All times are GMT -5. The time now is 10:52 AM.