Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
eth0 won't start during boot / starts fine after [solved]
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
airman
Tux's lil' helper
Tux's lil' helper


Joined: 06 Aug 2004
Posts: 82
Location: Utah, USA

PostPosted: Fri Apr 15, 2005 3:56 am    Post subject: eth0 won't start during boot / starts fine after [solved] Reply with quote

I've been running Gentoo on my box for about the last year with not too much of a problem. At least the problems that have cropped up I've been able to fix. This one, however, has me a bit puzzled...

When I boot my system, I get the following messages logged to the screen:

Code:
 * Bringing lo up...                           [ ok ]
 * Initializing random number generator...     [ ok ]
INIT: Entering runlevel: 3                     [ ok ]
 * Starting syslog-ng...                       [ ok ]
 * Bringing eth0 up (192.168.2.11)...
SIOCSIFADDR: No such device
eth0: unknown interface: No such device
SIOCSIFBRDADDR: No such device
eth0: unknown interface: No such device
SIOCSIFNETMASK: No such device                 [ !! ]

 * ERROR:  Problem starting needed services.
 *         "netmount" was not started.
 * ERROR:  Problem starting needed services.
 *         "sshd" was not started.
 * ERROR:  Problem starting needed services.
 *         "apache2" was not started.
 * Coldplugging input devices...               [ ok ]
 * Coldplugging isapnp devices...              [ ok ]
 * Coldplugging pci devices...                 [ ok ]
 * Coldplugging pnp devices...                 [ ok ]
 * Coldplugging usb devices...                 [ ok ]
 * Starting cups...                            [ ok ]
 * ERROR:  Problem starting needed services.
 *         "distccd" was not started.
 * Setting DNS domainname to xxxxxxxxxx.com... [ ok ]
 * ERROR:  Problem starting needed services.
 *         "gkrellmd" was not started.
 * Starting vixie-cron...                      [ ok ]
 * Starting xinetd...                          [ ok ]
 * Starting local...                           [ ok ]

login:


Once my system is booted and I log in as root, the following works just fine:

Code:
root # /etc/init.d/net.eth0 start
Bringing eth0 up (192.168.2.11)...        [ ok ]
Setting default gateway (192.168.2.1)...  [ ok ]
root #


...and the interface works fine after that. It's only during boot that /etc/init.d/net.eth0 won't start. After starting the interface, I can then start all of the services that couldn't start on bootup due to eth0 not being recognized.

I've read several threads here on the forums regarding incorrect modules being loaded, or rather NOT loaded into the kernel. But I don't see how this could be the case here, as I haven't changed the kernel or done system modifications for a long time. The only thing I may have done was to emerge new kernel sources. But that won't change my existing kernel/module setup.

Of note is the following:

(1) I have not made any changes to the kernel in the past year.
(2) The only changes I've made recently are to eth0, and that was merely modifying /etc/conf.d/net to assign a hard IP rather than use DHCP.
(3) I've undone my changes to /etc/conf.d/net and get the same error message on boot.

I'm puzzled... Any ideas?

Let me know if there are any other logs I could post to be helpful...


Last edited by airman on Fri Apr 15, 2005 1:06 pm; edited 1 time in total
Back to top
View user's profile Send private message
jruiz
Tux's lil' helper
Tux's lil' helper


Joined: 28 Apr 2004
Posts: 100
Location: Asturias

PostPosted: Fri Apr 15, 2005 7:01 am    Post subject: Reply with quote

Hi, did you try to just add your module to be loaded in /etc/modules.autoload.d/kernel-2.6 ??

You know, like "echo my_netcard_module >> /etc/modules.autoload.d/kernel-2.6"
Back to top
View user's profile Send private message
airman
Tux's lil' helper
Tux's lil' helper


Joined: 06 Aug 2004
Posts: 82
Location: Utah, USA

PostPosted: Fri Apr 15, 2005 12:42 pm    Post subject: Reply with quote

The module that my NIC uses is "natsemi". It appears that the module is already loaded. This 'lsmod' was run as the first command directly after a reboot...

Code:
root # lsmod
Module                  Size  Used by    Not tainted
sg                     29148   0  (autoclean) (unused)
st                     26712   0  (autoclean) (unused)
sr_mod                 14008   0  (autoclean) (unused)
sd_mod                 10956   0  (autoclean) (unused)
scsi_mod               89188   4  (autoclean) [sg st sr_mod sd_mod]
parport_pc             24584   1  (autoclean)
lp                      6792   0  (autoclean)
parport                22216   1  (autoclean) [parport_pc lp]
uhci                   23292   0  (unused)
natsemi                15264   0
usbcore                54988   1  [uhci]
root #


The eth0 interface starts after reboot without loading any additional modules...

Code:
root # /etc/init.d/net.eth0 start
 * Bringing eth0 up (192.168.2.11)...                                       [ ok ]
 *   Setting default gateway (192.168.2.1)...                               [ ok ]
root #


After starting the interface, we can see that the module is indeed now in use...

Code:
root # lsmod
Module                  Size  Used by    Not tainted
sg                     29148   0  (autoclean) (unused)
st                     26712   0  (autoclean) (unused)
sr_mod                 14008   0  (autoclean) (unused)
sd_mod                 10956   0  (autoclean) (unused)
scsi_mod               89188   4  (autoclean) [sg st sr_mod sd_mod]
parport_pc             24584   1  (autoclean)
lp                      6792   0  (autoclean)
parport                22216   1  (autoclean) [parport_pc lp]
uhci                   23292   0  (unused)
natsemi                15264   1
usbcore                54988   1  [uhci]
root #


The bizarre thing to me is why, since the module appears to be present, will eth0 NOT start during boot, but then start with no problems a few seconds later?

Still puzzled...
Back to top
View user's profile Send private message
airman
Tux's lil' helper
Tux's lil' helper


Joined: 06 Aug 2004
Posts: 82
Location: Utah, USA

PostPosted: Fri Apr 15, 2005 12:57 pm    Post subject: Reply with quote

Oh my goodness, adding 'natsemi' to /etc/modules.autoload.d/kernel-2.4 worked! No more error on bootup. :D

Thanks for the advice!

Any ideas why a module would suddenly stop loading on bootup when it has worked properly for so long? Could it be a matter maybe of WHEN it is automatically loaded on bootup? Maybe a hotplug or coldplug issue that we are covering over because of the now-manual load?

Happy to have it solved, but still wondering...
Back to top
View user's profile Send private message
jruiz
Tux's lil' helper
Tux's lil' helper


Joined: 28 Apr 2004
Posts: 100
Location: Asturias

PostPosted: Fri Apr 15, 2005 1:15 pm    Post subject: Reply with quote

I'm happy it helped, I see tho that I assumed you were using 2.6, and u use kernel 2.4, but u got it anyway :wink:

I'm not really sure, but I think that the init script for network loads the module (normally /etc/init.d/net.eth0 or similar), and not coldplug, dunno really why it stopped loading it for you when it was working well before, what I see it happends in your system is that coldplug loads the module correctly, but it comes after the network init scripts, and this is why after booting you see the module there...

Peace
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum