26 Oct
2007
26 Oct
'07
10:58 a.m.
Hello,
i builded a initrd for udpcast with cast'o matic and one with the command
line tool. With both initrd
linux trys to configure ip settings with bootp, but i have no bootp server
in the network. Can i deactivate it
or change it to dhcp? In config file the makeImage program is dhcp switched
to "yes"
I tryed also to change the dhcpd.conf with the two parameters:
allow bootp;
allow booting;
but no success.
Any Ideas?
kind regards,
Markus
27 Oct
27 Oct
9:13 a.m.
Hello all,
I had a quick look at Markus' problem yesterday.
The hardware we use contains two ethernet cards. One that is listed in
BIOS and can be configured for PXE-Boot (runs fine with the e100
driver) and one that can't be used for PXE.
We only connect the PXE capable card to our network.
As it turned out, the card that can't be used for PXE is detected as
eth0 and the other one is detected as eth1.
It seems that the initrd that is built with cast-o-matic as well as
the initrd that is built with the command line builder uses eth0 as
the standard network interface which leads to the phenomenon that has
been described by Markus.
So the question seems to be clear at the moment:
How can we configure the initrd to use eth1 as the standard network interface?
For starters it would be sufficient to have a quick hack on how to set
this for the initrd. On the other hand it would probably be a nice
feature to be able to set the network interface that will be used via
some dropdown menu in cast-o-matic as well as via some command line
switch for the command line tool.
Hopefully someone can shed some light on this issue.
I'm sorry for the inconvenience.
Kind regards,
Jens
30 Dec
30 Dec
1:22 a.m.
Jens Breuer wrote:
Hello all,
I had a quick look at Markus' problem yesterday.
The hardware we use contains two ethernet cards. One that is listed in
BIOS and can be configured for PXE-Boot (runs fine with the e100
driver) and one that can't be used for PXE.
We only connect the PXE capable card to our network.
As it turned out, the card that can't be used for PXE is detected as
eth0 and the other one is detected as eth1.
It seems that the initrd that is built with cast-o-matic as well as
the initrd that is built with the command line builder uses eth0 as
the standard network interface which leads to the phenomenon that has
been described by Markus.
So the question seems to be clear at the moment:
How can we configure the initrd to use eth1 as the standard network interface?
For starters it would be sufficient to have a quick hack on how to set
this for the initrd. On the other hand it would probably be a nice
feature to be able to set the network interface that will be used via
some dropdown menu in cast-o-matic as well as via some command line
switch for the command line tool.
Hopefully someone can shed some light on this issue.
I'm sorry for the inconvenience.
Kind regards,
Jens
I've aded probing of multiple interfaces in the new version (20071228).
Now, the boot system tries all network interfaces (except loopback)
until it finds one where it can get an address via DHCP.
Regards,
Alain
5297
days inactive
5362
days old
2 comments
3 participants
participants (3)
-
Alain Knaff -
Jens Breuer -
Markus Forster