Le 28/05/2015 16:54, Alexander Graf a écrit :
On 28.05.15 16:36, Guillaume Gardet wrote:
Le 28/05/2015 16:27, Marcus Schäfer a écrit :
Hi,
now, u-boot lists all bootable partitions to look for boot scripts.
If no partition has a bootflag, it falls back to 1st partition. This
break Chromebook (and maybe Raspberry Pi?) images, since 1st
partition is hidden and we use partition 2 for our boot script,
kernel and initrd.
Could we add the boot flag to partition number 2 when vboot is used?
I can look into this, could you send me the current partition layout
parted <device> unit s print
On raw files I get:
********************************************************************************
Model: (file)
Disk
/home/guillaume/perso/Libre/images/factory/openSUSE-Tumbleweed-ARM-JeOS-chromebook.armv7l-1.12.1-Build308.2.raw:
2566144s
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 2048s 411651s 409604s U-BOOT
2 413696s 827395s 413700s ext3 lxboot
3 829440s 2566016s 1736577s ext4 lxroot
********************************************************************************
Boot flag is for #2 : lxboot.
Plase also keep in mind that we're manually creating a hybrid GPT with
an MBR reflecting most of the layout. I don't know which label type
u-boot prefers in such a case - Linux will use the GPT.
u-boot too, I think.
The reason this is important is that the hybrid GPT bits are in our
scripts, not kiwi.
Alex
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
