Qt5 Image Errors

Technical Support
, , ,
1

I could copy the Qt5 image Colibri_T20_LinuxImageV2.6.1_20161124.tar.bz2 to an XD card on a laptop PC, then I wanted to expand it on the same card; according to “Flashing Embedded Linux to Tegra Modules” extraction must have root permissions.

venturi@linux-rs:/var/run/media/venturi/550B-8282> sudo tar xpvf Colibri_T20_LinuxImageV2.6.1_20161124.tar.bz2

However this process leads to mess of errors…

Colibri_T20_LinuxImageV2.6.1/
Colibri_T20_LinuxImageV2.6.1/rootfs/
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/sed
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/chattr
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/systemd-tmpfiles
tar: Colibri_T20_LinuxImageV2.6.1/rootfs/bin/systemd-tmpfiles: Cannot change ownership to uid 0, gid 0: Operation not permitted
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/umount
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/zcat
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/touch
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/journalctl
tar: Colibri_T20_LinuxImageV2.6.1/rootfs/bin/journalctl: Cannot change ownership to uid 0, gid 0: Operation not permitted
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/systemd-ask-password
tar: Colibri_T20_LinuxImageV2.6.1/rootfs/bin/systemd-ask-password: Cannot change ownership to uid 0, gid 0: Operation not permitted
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/loginctl
tar: Colibri_T20_LinuxImageV2.6.1/rootfs/bin/loginctl: Cannot change ownership to uid 0, gid 0: Operation not permitted
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/more
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/rmdir
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/mknod
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/ls
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/busybox.suid
tar: Colibri_T20_LinuxImageV2.6.1/rootfs/bin/busybox.suid: Cannot change ownership to uid 0, gid 0: Operation not permitted
tar: Colibri_T20_LinuxImageV2.6.1/rootfs/bin/busybox.suid: Cannot change mode to rwsr-xr-x: Operation not permitted
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/gzip
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/cpio
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/run-parts
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/systemd-hwdb
tar: Colibri_T20_LinuxImageV2.6.1/rootfs/bin/systemd-hwdb: Cannot change ownership to uid 0, gid 0: Operation not permitted
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/systemd-machine-id-setup
tar: Colibri_T20_LinuxImageV2.6.1/rootfs/bin/systemd-machine-id-setup: Cannot change ownership to uid 0, gid 0: Operation not permitted
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/tar
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/ps
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/fatattr
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/busybox.nosuid
tar: Colibri_T20_LinuxImageV2.6.1/rootfs/bin/busybox.nosuid: Cannot change ownership to uid 0, gid 0: Operation not permitted
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/sh
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/kill
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/umount.util-linux
tar: Colibri_T20_LinuxImageV2.6.1/rootfs/bin/umount.util-linux: Cannot change ownership to uid 0, gid 0: Operation not permitted
tar: Colibri_T20_LinuxImageV2.6.1/rootfs/bin/umount.util-linux: Cannot change mode to rwsr-xr-x: Operation not permitted
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/ping
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/netstat
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/systemd-firstboot
tar: Colibri_T20_LinuxImageV2.6.1/rootfs/bin/systemd-firstboot: Cannot change ownership to uid 0, gid 0: Operation not permitted
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/ln
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/systemd-inhibit
tar: Colibri_T20_LinuxImageV2.6.1/rootfs/bin/systemd-inhibit: Cannot change ownership to uid 0, gid 0: Operation not permitted
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/pidof
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/dmesg
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/pidof.procps
tar: Colibri_T20_LinuxImageV2.6.1/rootfs/bin/pidof.procps: Cannot change ownership to uid 0, gid 0: Operation not permitted
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/su.shadow
tar: Colibri_T20_LinuxImageV2.6.1/rootfs/bin/su.shadow: Cannot change ownership to uid 0, gid 0: Operation not permitted
tar: Colibri_T20_LinuxImageV2.6.1/rootfs/bin/su.shadow: Cannot change mode to rwsr-xr-x: Operation not permitted
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/uname
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/login.shadow
tar: Colibri_T20_LinuxImageV2.6.1/rootfs/bin/login.shadow: Cannot change ownership to uid 0, gid 0: Operation not permitted
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/systemctl
tar: Colibri_T20_LinuxImageV2.6.1/rootfs/bin/systemctl: Cannot change ownership to uid 0, gid 0: Operation not permitted
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/egrep.grep
tar: Colibri_T20_LinuxImageV2.6.1/rootfs/bin/egrep.grep: Cannot change ownership to uid 0, gid 0: Operation not permitted
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/pwd
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/udevadm
tar: Colibri_T20_LinuxImageV2.6.1/rootfs/bin/udevadm: Cannot change ownership to uid 0, gid 0: Operation not permitted
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/getopt
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/egrep
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/chgrp
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/fgrep
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/true
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/hostname
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/dd
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/sleep
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/dumpkmap
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/mv
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/grep
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/kill.procps
tar: Colibri_T20_LinuxImageV2.6.1/rootfs/bin/kill.procps: Cannot change ownership to uid 0, gid 0: Operation not permitted
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/machinectl
tar: Colibri_T20_LinuxImageV2.6.1/rootfs/bin/machinectl: Cannot change ownership to uid 0, gid 0: Operation not permitted
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/kmod
tar: Colibri_T20_LinuxImageV2.6.1/rootfs/bin/kmod: Cannot change ownership to uid 0, gid 0: Operation not permitted
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/mount.util-linux
tar: Colibri_T20_LinuxImageV2.6.1/rootfs/bin/mount.util-linux: Cannot change ownership to uid 0, gid 0: Operation not permitted
tar: Colibri_T20_LinuxImageV2.6.1/rootfs/bin/mount.util-linux: Cannot change mode to rwsr-xr-x: Operation not permitted
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/mktemp
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/usleep
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/vi
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/gunzip
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/df
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/grep.grep
tar: Colibri_T20_LinuxImageV2.6.1/rootfs/bin/grep.grep: Cannot change ownership to uid 0, gid 0: Operation not permitted
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/systemd-tty-ask-password-agent
tar: Colibri_T20_LinuxImageV2.6.1/rootfs/bin/systemd-tty-ask-password-agent: Cannot change ownership to uid 0, gid 0: Operation not permitted
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/systemd-escape
tar: Colibri_T20_LinuxImageV2.6.1/rootfs/bin/systemd-escape: Cannot change ownership to uid 0, gid 0: Operation not permitted
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/busybox
tar: Colibri_T20_LinuxImageV2.6.1/rootfs/bin/busybox: Cannot create symlink to `busybox.nosuid': Operation not permitted
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/su
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/login
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/ping6
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/chattr.e2fsprogs
tar: Colibri_T20_LinuxImageV2.6.1/rootfs/bin/chattr.e2fsprogs: Cannot change ownership to uid 0, gid 0: Operation not permitted
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/cp
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/watch
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/echo
Colibri_T20_LinuxImageV2.6.1/rootfs/bin/date

…

Surely I am doing something wrong, but I cannot guess what.

Any help is warmly welcomed.

Thank you for your attention.

Miguelon.

2

The idea would be for that extraction to be done not on the SD card but rather a sane (e.g. ext4) host file system. Only in the later ./update.sh -o step would the resp. flashing images be written to your SD card which may be fat32 formatted as well.

3

Thanks for your attention.

I believe that this misunderstanding could be avoided if the script name was say ‘setsdcard.sh’,
and not ‘update.sh’, which suggests a target operation to be made with a SDCARD duly set up
through a copy operation from the EXT4 partition where it was extracted.

The ‘update.sh’ scripts works correctly from EXT4.

Miguelon.