Re: eth0 hanging at boot

From: P Gentry (rdgentry1_at_cablelynx.com)
Date: 03/11/04


Date: 11 Mar 2004 12:49:14 -0800


"chloe" <Jon@freeserve.co.uk> wrote in message news:<c2pqhe$klg$1@titan.btinternet.com>...
> My RH9.0 indeed uses dhclient.
>
> My main question is why can I boot successfully with eth0 configuration set
> for "onboot=no", and subsequently I can activate/deactivate eth0 using RH's
> System Tools-Network Device Control application, without any problems
> whatsoever.
> However if I set "onboot=yes", then the boot hangs at activating eth0
> interface.

I misunderstood your last post -- thought after using the gui it was
booting OK. For possible reasons why not see below.

> Presumeably the process of obtaining an IP address from the ADSL router etc
> etc is somehow different depending on whether the activation takes place
> during boot or subsequently after using RH's GUI facility.

Not really different in nature, but different in timing -- the same
script gets called in either case.

> Is there any way of determining just what is being asked for during the
> boot? Presumeably something is being asked for during the boot process eth0
> activation stage, and is not forthcoming, thus the system hangs! Is that
> being too simplistic?

You're on the right track and not being "too simplistic" at all.
 
[snip]

If your box is _always_ hanging at boot (when "onboot=yes") then some
detective work is needed.

Since you're using a gui, Konsole (in KDE) makes it easy to copy
command line and output for pasting (assume same in Gnome, but I don't
use it any more).

We need output of following commands both before and after bringing up
eth0.
[user]$ /sbin/ifconfig <- interface setup
and
[user]$ /sbin/route -n <- main route table
and
[user]$ /sbin/route -C <- route cache

xDSL is a bit harder to figure out "long distance" because it can be
set up in several ways depending on hardware/provider.
-- do you have "always on" setup so long as the modem is powered up?
-- do you acquire a new "lease" each time the computer powers on?
-- are both your computer and the modem plugged into a power strip
that you use to power up/down your computer?
-- do you know for sure whether you're using PPPoE or PPPoA from the
modem to service provider?
-- should you be running a pppoe client? (doubtful)
-- if the modem provides light indicators, has the modem latched onto
a signal before Linux is loading/initializiing?

These questions are to make sure that there is a way out to the dhcp
server when Linux is booting -- that's what "onboot=yes" requires as
the script will contact the server for configuration info needed to
bring up eth0 properly. When "onboot=no" the script does not run till
you manually activate/bring up eth0.

Also muddying things is the possibilitiy that the modem itself is
acting as the dhcp server.

These multiple setup/configuration possibilities are best covered in
the dsl howto here:
http://www.tldp.org/HOWTO/DSL-HOWTO/

Another question:
When booting with "onboot=yes" does the system actually _hang_ and
refuse to go farther, requiring you to use rescue mode to change to
"onboot=no"? Or is it taking a long time before timing out and
proceeding?

If the first is true, then there is a basic setup problem -- seems
less likely since you can manually bring up eth0. Does the simple
command line work as well as the gui took? At a terminal (as root)
try to bring it up like this:
[root]# ifconfig eth0 up

If the second, the you _may_ be able to work around it, but how to do
so can depend on a number of things. It may be best to check here
first:
http://www.dslreports.com/
and try:
http://www.dslreports.com/forums/all

Since you can bring up your net connection manually, I think it's a
question of getting the script set up and running correctly at boot.

Get back with info above if you need help here.

hth,
prg
email above disabled



Relevant Pages

  • Re: Linux 2.6.29-rc1 MAJOR advisory
    ... boot the 2.6.29-rc1 I had built destroyed the MCP55 eth0 port, ... had to boot the patch -rc1 a second time. ... would only suggest a complete powerdown instead of only rebooting, ...
    (Linux-Kernel)
  • Re: How to trouble shoot eth0 FAILED?
    ... At this point ifplugd is trying to detect link status of eth0 and ... Ifplug is fetching network setup info for your computer. ... That's the error message you see at boot. ...
    (comp.os.linux)
  • Re: eth0 failure
    ... GRUB so dumped it and re-installed Mandrake V10 again. ... eth0 fails on boot. ... So re-edited the files in 5) above to standard and cold booted. ... But I am not that aware yet of the boot sequence on ...
    (comp.os.linux.networking)
  • Re: Various recent threads about networking issues
    ... so eth0 is wireless and eth0 is the lan. ... Is possible to make unloadable at boot a module? ... Is blacklist file in /etc/modules.d used to make modules unloadable ...
    (Fedora)
  • eth0 not starting on bootup
    ... on boot is eth0. ... the eth0 interface is now no longer starting when the ... To Unsubscribe Go To ABOVE URL or send a message to: ...
    (RedHat)