Running Slackware 10.1, SOYO KT-880 Dragon2 V2.0 motherboard, using the
onboard ethernet device, connected to a Linksys BEFW1154 router, then to a
Westell DSL modem. Sometimes, but not always, after a fresh boot up, eth0
is not always up. But then, if I run "# /etc/rc.d/rc.inet1 start" eth0
comes up okay. Currently, rc.inet1 is called from the rc.M startup script.
I was just wondering, is there maybe a better place to call rc.inet1 from,
so that eth0 will always come up?

Does anybody else have this problem?


Thanks

jevb wrote:
> Running Slackware 10.1, SOYO KT-880 Dragon2 V2.0 motherboard, using the
> onboard ethernet device, connected to a Linksys BEFW1154 router, then to a
> Westell DSL modem. Sometimes, but not always, after a fresh boot up, eth0
> is not always up. But then, if I run "# /etc/rc.d/rc.inet1 start" eth0
> comes up okay. Currently, rc.inet1 is called from the rc.M startup script.
> I was just wondering, is there maybe a better place to call rc.inet1 from,
> so that eth0 will always come up?
>
> Does anybody else have this problem?
>
>
> Thanks
I think you could put it in:
/etc/rc.d/rc.local
Then it would save you having to ad it later in a terminal.

--
Leo in Canada:
They said "everyone uses microsoft" and so like the lemmings they marched into
the sea.
< running Linux >

Just a thought from a Slack amatuer:

The reason I like slack is because rc.local can do just about anything for
you. I would put something like this in:
ifconfig eth0 down --Make sure the sucker is down
ifconfig eth0 up (Parameters)

It will be there 100 percent of the time I bet.

Just an idea.

Josh Beck

"jevb" <jevb@bluebottle.com> wrote in message
news:1123996014.db0b4510eced859f0ed095452e2a98ab@t eranews...
> Running Slackware 10.1, SOYO KT-880 Dragon2 V2.0 motherboard, using the
> onboard ethernet device, connected to a Linksys BEFW1154 router, then to a
> Westell DSL modem. Sometimes, but not always, after a fresh boot up, eth0
> is not always up. But then, if I run "# /etc/rc.d/rc.inet1 start" eth0
> comes up okay. Currently, rc.inet1 is called from the rc.M startup script.
> I was just wondering, is there maybe a better place to call rc.inet1 from,
> so that eth0 will always come up?
>
> Does anybody else have this problem?
>
>
> Thanks

Leo (Bing) Whiteway wrote:

> jevb wrote:
>> Running Slackware 10.1, SOYO KT-880 Dragon2 V2.0 motherboard, using the
>> onboard ethernet device, connected to a Linksys BEFW1154 router, then to
>> a Westell DSL modem. Sometimes, but not always, after a fresh boot up,
>> eth0 is not always up. But then, if I run "# /etc/rc.d/rc.inet1 start"
>> eth0 comes up okay. Currently, rc.inet1 is called from the rc.M startup
>> script. I was just wondering, is there maybe a better place to call
>> rc.inet1 from, so that eth0 will always come up?
>>
>> Does anybody else have this problem?
>>
>>
>> Thanks
> I think you could put it in:
> /etc/rc.d/rc.local
> Then it would save you having to ad it later in a terminal.
>
If I do put it in rc.local, should I then disable it in rc.M? I guess I
should, that makes sense. I'll try it and see what happens. I'll let you
know what happens.

On Mon, 15 Aug 2005 04:24:13 +0000, Josh wrote:

> The reason I like slack is because rc.local can do just about anything for
> you. I would put something like this in:

Just to clarify something, rc.local is not unique to Slackware. Any other
distro that I've ever seen also has this...

I guess you'll need to find another reason to like Slack.

--
If you're not on the edge, you're taking up too much space.
Linux Registered User #327951

In alt.os.linux.slackware, jevb dared to utter,
> Running Slackware 10.1, SOYO KT-880 Dragon2 V2.0 motherboard, using the
> onboard ethernet device, connected to a Linksys BEFW1154 router, then to a
> Westell DSL modem. Sometimes, but not always, after a fresh boot up, eth0
> is not always up. But then, if I run "# /etc/rc.d/rc.inet1 start" eth0
> comes up okay.

You're going to have to give us a little more to go on. Is eth0
configured statically? Dynamically? Do you do any ppp? There could
be any number of reasons it doesn't come up. If it's dynamic, try
increasing the timeout in rc.inet1. I do not usually recommend doing
net startup in rc.local as others have, because this can slowdown
certain services that do DNS lookups on startup (sendmail comes to
mind).

--
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5

+Alan Hicks+ wrote:

> In alt.os.linux.slackware, jevb dared to utter,
>> Running Slackware 10.1, SOYO KT-880 Dragon2 V2.0 motherboard, using the
>> onboard ethernet device, connected to a Linksys BEFW1154 router, then to
>> a Westell DSL modem. Sometimes, but not always, after a fresh boot up,
>> eth0 is not always up. But then, if I run "# /etc/rc.d/rc.inet1 start"
>> eth0 comes up okay.
>
> You're going to have to give us a little more to go on. Is eth0
> configured statically? Dynamically? Do you do any ppp? There could
> be any number of reasons it doesn't come up. If it's dynamic, try
> increasing the timeout in rc.inet1. I do not usually recommend doing
> net startup in rc.local as others have, because this can slowdown
> certain services that do DNS lookups on startup (sendmail comes to
> mind).
>

Hummm, thanks for your reply Alan. Unfortunately I don't know the answers to
your questions. Do you mean do I have a static IP, or a dynamic IP? If
that's the question, then I *think* it's dynamic. I use DHCP in my router
(see above), and the router assigns the IP to my computer. I have two other
Win machines connected to the router also. I always do a soft shutdown, so
that I only have to do a Left_Click on the mouse to start it up. Like I
said, *sometimes* eth0 doesn't come up, and *sometimes* it does. Let me
know if you have any more questions.

jerry

jevb wrote:

> I use DHCP in my router
> Like I said, *sometimes* eth0 doesn't come up, and *sometimes* it
> does.

I've found that default rc.inet1 sometimes has problems for a simple reason:
the default timeout for dhcp client [dhcpcd] is 10 seconds. Some networking
equipment can have delays, etc. Try this as a test:

edit /etc/rc.d/rc.inet1 and edit the line that calls 'dhcpcd'. Change the
'-t 10' to '-t 60' [that will be a safe value]

See if this helps.

In alt.os.linux.slackware, jevb dared to utter,
> Do you mean do I have a static IP, or a dynamic IP? If
> that's the question, then I *think* it's dynamic. I use DHCP in my router
> (see above), and the router assigns the IP to my computer.

In this case it's a dynamic IP. If you look in /etc/rc.d/rc.inet1.conf
you will see something like this:

# Primary network interface card (eth0)
IPADDR[0]=""
NETMASK[0]=""
USE_DHCP[0]=""
DHCP_HOSTNAME[0]=""

If USE_DHCP[0]="yes" you're using dhcp. If not, then you should see an
ip address and netmask listed for IPADDR[0] and NETMASK[0].

> I always do a soft shutdown, so
> that I only have to do a Left_Click on the mouse to start it up.

Ok, I'm having trouble resolving this statement with:

>>> Sometimes, but not always, after a fresh boot up,
>>> eth0 is not always up.

Do you mean you are using software suspend and the interface doesn't
come back up after a software resume, or are you talking about a cold
boot, such as power off to power on.

--
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5

On 2005-08-15, +Alan Hicks+ <alan@lizella.netWORK> wrote:


> come back up after a software resume, or are you talking about a cold
> boot, such as power off to power on.

I suspect a cold boot.

I've noticed this happens to me occasionally, also. But, I shut down
so seldom I usually forget all about it till it happens again. I
increased the -t setting in rc.inet1 as suggested in another post and
it seems to have solved the problem.

nb