[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#785343: linux-image-4.0.0-1-686-pae: "/@/initrd.img" not found, due to the symlink /initrd.img having an absolute target



On Fri, 15 May 2015 at 13:47:59 +0100, Ben Hutchings wrote:
> On Fri, 2015-05-15 at 05:24 +0200, Guilhem Moulin wrote:
>> On Fri, 15 May 2015 at 03:57:35 +0100, Ben Hutchings wrote:
>>> GRUB knows how to do this properly, so you're just making things
>>> difficult for yourself.
>> 
>> Since there is always a risk of bricking the board when flashing the
>> BIOS chip, I don't want to add a hook add flash it whenever I upgrade
>> the kernel.
> [...]
> 
> Why would you need to flash the whole chip?  Isn't the configuration in
> its own flash partition?

Not that I know of.  At the moment the format doesn't allow “support
multiple CBFSes per firmware image” [0].  My current way of upgrading
the grub.cf is to replace the grub.cfg in the ROM, then flash the whole
chip [1]:

    cbfstool libreboot.rom remove -n grub.cfg
    cbfstool libreboot.rom add -t raw -n grub.cfg -f grub.cfg
    flashrom -p internal -w libreboot.rom

And using flashrom on the go makes me sweaty ;-)  As the coreboot wiki
says: “Disadvantages: more risky if you have no way to recover ”.

-- 
Guilhem.

[0] http://www.coreboot.org/CBFS#FMAP
[1] http://www.coreboot.org/GRUB2#combining_with_coreboot

Attachment: signature.asc
Description: Digital signature


Reply to: