Skip to contentSkip to conversation

disabling nics using boot options.

Linux-ia64 Bill Nottingham 2 participants 4 messages Jan 9, 2003

lore
Share & tools
lore

Bill Nottingham

author
#0 lore raw
Quoted 4 lines · Roy Dragseth

Further investigation shows that if I connect the Gbit interface to a 10Mbs hub everything works ok, e.g. using the ksdevice=eth2 boot option works as expected.

Quoted 8 lines

I have narrowed this down to the following problem: When the init process tries to configure the eth2 with dhcp it fail, but if I logon as root and run

/etc/init.d/network start

everything works ok. Subsequent reboots also works ok because now the information is cached in /etc/dhcpc/. If I remove the cached info the problem turn up again.

So, it works post-install, but not in the installer? Hm. The dhcp client code is different in the two cases, but not in a way that should significantly affect this case.

Bill

#1 lore raw
Quoted 3 lines · Bill Nottingham

So, it works post-install, but not in the installer? Hm. The dhcp client code is different in the two cases, but not in a way that should significantly affect this case.

Well, it doesn't work during a normal bootup either. If I remove the cached info in /etc/dhcpc/ and reboots, the network initialization fails:

Setting network parameters:  [  OK  ]
Bringing up interface lo:  [  OK  ]
Bringing up interface eth2:  dhcpcd[536]: timed out waiting for a valid DHCP

server response
Determining IP information for eth2... failed. [FAILED]

If I log in and run /etc/init.d/network start everything works ok:

root@compute-1-1 root]# /etc/init.d/network start

Setting network parameters:  [  OK  ]
Bringing up interface lo:  [  OK  ]
Bringing up interface eth2:  [  OK  ]

I cannot see what it is different when init starts the network from when root is doing it.

r.

Signature · 4 lines
  The Computer Center, University of Tromsø, N-9037 TROMSØ, Norway.
	      phone:+47 77 64 41 07, fax:+47 77 64 41 00
     Roy Dragseth, High Performance Computing System Administrator
	 Direct call: +47 77 64 62 56. email: [email protected]
author
#2 lore raw
In reply to Bill Nottingham
Quoted 12 lines · Roy Dragseth

Well, it doesn't work during a normal bootup either. If I remove the cached info in /etc/dhcpc/ and reboots, the network initialization fails:

Setting network parameters:  [  OK  ]
Bringing up interface lo:  [  OK  ]
Bringing up interface eth2:  dhcpcd[536]: timed out waiting for a valid DHCP

server response
Determining IP information for eth2... failed. [FAILED]

If I log in and run /etc/init.d/network start everything works ok:

Quoted 7 lines

root@compute-1-1 root]# /etc/init.d/network start

Setting network parameters:  [  OK  ]
Bringing up interface lo:  [  OK  ]
Bringing up interface eth2:  [  OK  ]

I cannot see what it is different when init starts the network from when root is doing it.

How quickly does it time out (after 30 seconds to a minute?)

Bill

#3 lore raw
In reply to Bill Nottingham
Quoted 1 line · Bill Nottingham

How quickly does it time out (after 30 seconds to a minute?)

I clocked it in to exactly one minute.

r.

Signature · 4 lines
  The Computer Center, University of Tromsø, N-9037 TROMSØ, Norway.
	      phone:+47 77 64 41 07, fax:+47 77 64 41 00
     Roy Dragseth, High Performance Computing System Administrator
	 Direct call: +47 77 64 62 56. email: [email protected]