Le 15/06/2012 15:39, Michael Senizaiz a écrit :
If your kernel append lines only difference is that you are
referencing a different kernel and initrd with all the other bits the
same I would suggest adding the /lib/modules/`64 bit kernel` into the
initrd of the i386 and boot with that.
This portion of the boot isn't actually FAI specific, but just part of
the initrd boot up process. If your 64-bit kernel isn't a debian
style kernel with script/live etc. then it won't get all the variables
the same (or if it's using a different method for setting up the
network, the rootserver variable is actually set by the binary
/bin/ipconfig in the initrd)
It would be helpful if you posted your PXE boot config for both kernels.
Have a look here at what I found about the way networking is set up
with the initrd.
http://www.mail-archive.com/linux-fai@uni-koeln.de/msg04573.html
On Fri, Jun 15, 2012 at 3:13 AM, Nicolas Courtel <cour...@cena.fr
<mailto:cour...@cena.fr>> wrote:
Le 14/06/2012 19:00, Michael Senizaiz a écrit :
What kernel are you using? Are you using 'boot=live'? The
boot= tells it what script in scripts/ to run after init, and
only live and nfs will use the rootserver variable.
Yes, boot=live is added by fai-chboot; I'm pretty sure my config
is correct, as it used to work a couple of weeks ago, and is still
working on i386.
--
Nicolas
Well, I'm sure now that the problem is not related to FAI or to my
config : I just need to build the nfsroot with the 27th May Wheezy
snapshot to make my server work fine (of course the initrd only is relevant)
Between this snapshot and the current version, live-initramfs has not
changed, but the klibc-utils package has been upgraded from version
2.0~rc3-1 to 2.0-2, so I believe the change is in ipconfig.
--
Nicolas
