Hi all
On Wednesday 16 November 2011 08:21:26 Carsten Aulbert wrote:
Specifying eth0 will not help as the kernel arbitrarily changes the names
upon reboot. The machine I'm currently struggling with is choosing eth0 for
the first on-board NIC for ~50-60% of the time (no hard numbers on that
On 11/16/2011 08:21 AM, Carsten Aulbert wrote:
Hi
On Tuesday 15 November 2011 19:54:14 Sylvain Milot wrote:
# generated by fai-chboot for host james with IP 172.16.178.144
default fai-generated
label fai-generated
kernel vmlinuz-2.6.38-grml64
append initrd=initrd.img-2.6.38-grml64
On Wed, 16 Nov 2011 16:01:21 +0100, Carsten Aulbert
cars...@welcomes-you.com said:
I put 'set -x ' into the init function of the initrd to try to trace down
if
You do not need this. Just add the string debug to the kernel command
line, that will do the same trick.
The problem is, that
Hi
On Wednesday 16 November 2011 20:38:36 Thomas Lange wrote:
On Wed, 16 Nov 2011 16:01:21 +0100, Carsten Aulbert carsten@welcomes-
you.com said:
I put 'set -x ' into the init function of the initrd to try to trace
down if
You do not need this. Just add the string debug to the
Please any help oder ideas
Thanks
On 11/11/2011 12:27 PM, W Forum W wrote:
Hi,
Thanks
I tried this but it didn't solved my problem
Yes my server has multiple interfaces. I tried it also with a client
with only 1 interfaces
but the same issue.
Kind regards,
Wim
On 11/09/2011 04:13 PM,
Hi
On Tuesday 15 November 2011 11:50:04 W Forum W wrote:
Please any help oder ideas
Actually that is exactly my second problem (cf yesterday's email).
Does you server has multiples interfaces? If so use the kernel
arguments: live-netdev=eth0
This one does not always help, as device
Hello List,
comments below concerning multiple NICs ...
On Tue, 15 Nov 2011, W Forum W wrote:
Hi
On Tuesday 15 November 2011 11:50:04 W Forum W wrote:
Please any help oder ideas
Actually that is exactly my second problem (cf yesterday's email).
Does you server has multiples
Thanks but ...
I tried this but still no success
I tried it also with a client with 1 NIC but still no luck
Client still hangs after
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
In my dhcp log files I see for this client
dhcpd: DHCPREQUEST for 192.168.52.10 (192.168.52.133) from
On Tue, 15 Nov 2011, W Forum W wrote:
Thanks but ...
I tried this but still no success
I tried it also with a client with 1 NIC but still no luck
Client still hangs after
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
In my dhcp log files I see for this client
dhcpd: DHCPREQUEST for
On 11/15/2011 09:30 PM, Sylvain Milot wrote:
On Tue, 15 Nov 2011, W Forum W wrote:
Thanks but ...
I tried this but still no success
I tried it also with a client with 1 NIC but still no luck
Client still hangs after
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
In my dhcp log files I
Hi
On Tuesday 15 November 2011 19:54:14 Sylvain Milot wrote:
# generated by fai-chboot for host james with IP 172.16.178.144
default fai-generated
label fai-generated
kernel vmlinuz-2.6.38-grml64
append initrd=initrd.img-2.6.38-grml64 ethdevice=eth0
Hi,
Thanks
I tried this but it didn't solved my problem
Yes my server has multiple interfaces. I tried it also with a client
with only 1 interfaces
but the same issue.
Kind regards,
Wim
On 11/09/2011 04:13 PM, Jeremy MAURO wrote:
Hi,
Does you server has multiples interfaces? If so use the
We use
Ethernet controller: Intel Corporation 82545EM Gigabit Ethernet
Controller (Copper) (rev 01)
Ethernet controller: Intel Corporation 82557/8/9/0/1 Ethernet Pro 100
(rev 10)
To boot I use the 82545EM card
Regards
Wim
--
Wim De Geeter
| System Administrator
| Wegener Center for Climate
On 09/11/2011 16:10, W Forum W wrote:
Hi,
I have installed fai (v3.4.7) on a debian squeeze server.
We are install clients (nodes for a cluster) over PXE.
The client is getting all information from our DHCP server.
The boot process is like
PXELINUX 4.02 debian-20101014
...
My IP address seems
Am 09.11.2011 16:16 schrieb Vivien Bernet-Rollande:
eth0: link becomes ready
and then it hangs
anyone an idea??
I experienced this when a server with multiple NICs was booting and the nic
the dhcp server was connected was detected as eth1.
The initrd uses a dhcp client to configure the
15 matches
Mail list logo
