| View previous topic :: View next topic |
| Author |
Message |
pschram
n00b
Joined: 04 Jan 2003
Posts: 44
|
 Posted: Mon Feb 24, 2003 10:03 pm Post subject: eth0 won't start at boot, but manually goes normal |
 |
|
I get error messages when starting eth0 at boot:
SIOCADDR exists
But when i fire up with:
| Code: | | /etc/init.d/net.eth0 start |
everything loads fine. I got my networkcard module loaded before the eth0 device tries to load in modules.autoload, so that's ok. Anybody any clues as to where to look for this? |
|
| Back to top |
|
 |
li1_getoo
l33t
Joined: 20 Oct 2002
Posts: 661
Location: Queens , NY
|
| Posted: Tue Feb 25, 2003 7:43 pm Post subject: |
|
|
| Code: | | rc-update add net.eth0 default |
should do the trick  |
|
| Back to top |
|
|
pschram
n00b
Joined: 04 Jan 2003
Posts: 44
|
| Posted: Tue Feb 25, 2003 8:46 pm Post subject: |
|
|
This doesn't solve it. When I type your suggestion I get:
| Code: | * net.eth0 already installed in runlevel default; skipping
|
|
|
| Back to top |
|
|
BradN
Advocate
Joined: 19 Apr 2002
Posts: 2391
Location: Wisconsin (USA)
|
| Posted: Wed Feb 26, 2003 12:48 am Post subject: |
|
|
| Is anything starting during startup after the interface tries to start that could be affecting it? nothing weird like pcmcia being required, or something like that right? |
|
| Back to top |
|
|
pschram
n00b
Joined: 04 Jan 2003
Posts: 44
|
| Posted: Wed Feb 26, 2003 9:41 am Post subject: |
|
|
| No, nothing like that. It's a regular pci 100Mbit networkcard. Also it has worked for like 2 months, but I probably wrecked something after an update of config files, but can't find what it is. Everything looks normal. I have what seems to be the right parameters in /etc/conf.d/net. Just a normal ip-adres of 192.168.0.1, so nothing special. |
|
| Back to top |
|
|
BradN
Advocate
Joined: 19 Apr 2002
Posts: 2391
Location: Wisconsin (USA)
|
| Posted: Wed Feb 26, 2003 8:59 pm Post subject: |
|
|
hmm...
you could try doing:
export CONFIG_PROTECT=""
emerge baselayout
in case one of your init scripts got hosed somehow. You would need to update any of the files you might have changed however.
Otherwise you could dig through the network init script and just troubleshoot it in general (try inserting a delay before when it tries to start the interface, such like that). |
|
| Back to top |
|
|
|
Kernel & Hardware
