On Thu, 2015-01-29 at 16:27 +0100, Patrick Ohly wrote:
> On Fri, 2015-01-23 at 16:07 +0100, Patrick Ohly wrote:
> > On Fri, 2015-01-23 at 21:22 +0800, LIYONG wrote:
> > > Hi Patrick,
> > >
> > > I am using the latest "source ./tizen-common-init-build-env" command to
> > > build the core minimal image.
> > > Using the mkefidisk.sh script in the yocto project to create the
> > > bootable u-disk. The host OS is Ubuntu 14.04
> >
> > Sorry, I am not familiar with mkefidisk.sh. So far, only the method of
> > manually creating an USB image as described in the Wiki page has been
> > tested.
> >
> > The strace output indicates problems with copying xattr attributes.
> > Perhaps that gives someone an idea.
>
> I tried it myself and can reproduce the issue. I used
> http://dominion.thruhere.net/koen/angstrom/minnow/mkefidisk.sh as linked
> to by http://www.elinux.org/Installing_Angstrom_on_a_Hard_Disk
>
> The image was a "Tizen on Yocto" image that I just created myself.
>
> In my case, the error is:
>
> Copying ROOTFS files...
> cp: 'mkefidisk-wKZ/hddimg_rootfs/var/volatile/log': Invalid argument
> Preparing boot partition...
> Installation complete.
This problem no longer occurs in the current tizen-distro. I replaced
config-image.bb + postinst with a modified base-files.bb + manifest. I
also got rid of this unnecessary /var/volatile. Now none of the rootfs
files have these problematic system.posix_acl_default xattr.
However, something in the meta-tizen layers breaks grub or gummiboot as
EFI boot loader. They build, but then hang before showing the boot menu.
This prevents using the tizen-distro/contrib/mkefidisk.sh script without
further changes: to work around that issue, use the script, then mount
the boot partition and replace EFI/BOOT/boot*.efi with the corresponding
file built in a bitbake build config without the meta-tizen layers
("bitbake grub-efi").
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
