no kernel installed on client so it refuses booting ... a little more

[Nicolas Triantafillou]

scripts/DEFAULT/S01 has:

fcopy /etc/kernel-img.conf

this should be happening by itself? check out your files/etc/kernel-img.conf

the hook shouldn't be needed.

Nick.

Holger Levsen wrote:
> Hi Gerald, hi all,
> 
> I use a hook before the packages get installed to set /etc/kernel-img.conf - 
> but I'm also wondering how other people do it as I don't think this is a 
> really elegant solution.
> 
> FAI_CONFIGDIR/files/instsoft.NEWWORLD consists of this lines:
> -----------------------------------------------------
> #! /bin/sh
> 
> # kernel-image-2.6.8-powerpc.deb requieres this :(
> echo "do_initrd = Yes" >> $target/etc/kernel-img.conf
> -----------------------------------------------------
> 
> "NEWWORLD" is the name of the class which installs the kernel. (via 
> package_config/NEWWORLD)
> 
> 
> regards,
>  Holger
> 
> On Friday 08 October 2004 15:34, Gerald Houart wrote:
> 
>>a little more about the problem:
>>grub works fine but without kernel installed it makes kernel panic message
>>
>>looking log files of FAI installation (especially rcS.log and shell.log) i
>>found : ====rcS.log =====================================================
>>.
>>.
>>Unpacking kernel-image-2.6.8-1-686 (from
>>.../kernel-image-2.6.8-1-686_2.6.8-3_i386.deb) .. .
>>
>>
>>You are attempting to install an initrd kernel image (version 2.6.8-1-686)
>>This will not work unless you have configured your boot loader to use
>>initrd. (An initrd image is a kernel image that expects to use an INITial
>>Ram Disk to mount a minimal root file system into RAM and use that for
>>booting).
>>
>>   As a reminder, in order to configure LILO, you need
>>   to add an 'initrd=/initrd.img' to the image=/vmlinuz
>>   stanza of your /etc/lilo.conf
>>
>>I repeat, You need to configure your boot loader -- please read your
>>bootloader documentation for details on how to add initrd images.
>>
>>If you have already done so, and you wish to get rid of this message,
>>please put
>>  "do_initrd = Yes"
>>in /etc/kernel-img.conf. Note that this is optional, but if you do not,
>>you will continue to see this message whenever you install a kernel
>>image using initrd.
>>Do you want to stop now? [Y/n]Ok, Aborting
>>dpkg: error processing
>>/var/cache/apt/archives/kernel-image-2.6.8-1-686_2.6. 8-3_i386.deb (
>>--unpack):
>> subprocess pre-installation script returned error exit status 1
>>.
>>.
>>====rcS.log =====================================================
>>
>>and
>>
>>====shell.log =====================================================
>>.
>>.
>>Get:1 ftp://ftp.de.debian.org sarge/main kernel-image-2.4.27-1-686 2.4.27-2
>>[12.3MB] Fetched 12.3MB in 34s (355kB/s)
>>(Reading database ... 10001 files and directories currently installed.)
>>Unpacking kernel-image-2.4.27-1-686 (from
>>.../kernel-image-2.4.27-1-686_2.4. 27-2_i386.deb)
>> ...
>>Setting up kernel-image-2.4.27-1-686 (2.4.27-2) ...
>>/initrd.img does not exist. Installing from scratch, eh?
>>Or maybe you don't want a symbolic link here. Hmm? Lets See.
>>.
>>.
>>====shell.log =====================================================
>>
>>
>>i putted "do_initrd = Yes" in fai/files/etc/kernel-img.conf/DEFAULT but
>>without results
>>
>>after install i can install kernel manually in a shell with
>>  chroot /tmp/target mount -t proc none proc
>>  chroot /tmp/target apt-get install kernel-image...
>>  chroot /tmp/target update-grub
>>
>>and so it boots !!!
>>
>>any other suggestions are welcome
>>
>>best regards
>>
>>Gerald HOUART
>>
>>
>>>>>>>>On Fri, 08 Oct 2004 09:40:17 +0200, Gerald Houart
>>>>>>>><ghouart at ulb.ac.be> said:
>>>>>>>>
>>>
>>>   > i use fai installed with sarge ... and everything based on the
>>>   > example "simple"
>>>   > but after all the process of installation, grub refuses to boot
>>>   > linux and in fact in /boot there is no kernel !!!
>>>   >
>>>   > any suggestion to resolve this probably stupid problem (but so
>>>   > stupid that i can't see where it is !)
>>>
>>>Read the the log files!!!
>>>
>>>I think you did not define the classes MBR and GRUB or no kernel is
>>>installed at all. Have a special look at shell.log.
>>>
>>>--
>>>regards Thomas
>>
>>*********************************************
>>Gérald HOUART
>>Support informatique du bâtiment NO
>>Universite Libre de Bruxelles
>>ext 5604 / bureau 2.o8.216
>>*********************************************
> 
> 
>