![]() Some of the OpenGL related files (including OpenGL ES) probably have the non-accelerated original Ubuntu files in need of replacement. It is ok to overwrite those files so long as they are in the sample rootfs or at the root of the actual Jetson which has L4T R21.1 installed. Just to be clear, these commands should be run at the root of the sample rootfs (which should be a subdirectory to where flash.sh is). The “file exists” would tend to mean that either you’ve already unpacked these files once, or a file of the same name already exists in the subdirectory from where you ran the command. Sorry, to be explicit the above errors were created whilst using sudo, I also tried sudo -s This is one of the biggest causes of help messages for new users…either failure of using sudo or failure of an underlying file system not supporting the full range of linux files. Another cause would be if the underlying file system cannot contain device special files (e.g., a windows partition can’t handle specialized linux files). An obvious example is that only root can create device special files in /dev. So yes, operation not permitted occurs sometimes because of lack of sudo. Being in sudo -s removes all those individual sudo commands. I tend to pipe and redirect a lot because it gives me fine control, and so one would need sudo in each part of a compound command like “bunzip2 < 2 | tar -list”. ![]() This stays continuously in a root su shell, and does not exit after the first command. ![]() Tar: usr/lib/arm-linux-gnueabihf/tegra-egl: Cannot utime: Operation not permitted Tar: usr/lib/arm-linux-gnueabihf/tegra-egl/libGLESv1_CM.so.1: Cannot open: File exists Tar: usr/lib/arm-linux-gnueabihf/tegra/libnvmmlite_image.so: Cannot open: File exists It looks like the inability to set the timestamp of a file is something mtp speciffic.Is sudo needed: bunzip2 < …/nv_tegra/nvidia_drivers.tbz2 | tar xv The timestamps of the unpacked files have been restored correctly. I pulled it out of the phone, plugged it in another computer (Ubuntu 14.04) and was able to unpack another tarball without any errors. It turned out that the MicroSD card itself has been formatted using vfat filesystem without any encryption. Is the problem related to me using encryption? Is there any mount option or other magic that will allow setting the files' timestamps on a mounted mtp filesystem? I normally wouldn't worry about it but there are files under Android/data that belong to applications that might be timestamp sensitive. This is confirmed by ls -l - it shows the current date and time. Telling me that tar is unable to restore the original timestamp of the files. Tar: 00001.vcf: Cannot utime: Operation not supported The files got restored but for each one I got an error message like: 00001.vcf Then replaced the card, formatted the new one and tried to restore my files: I replaced the MicroSD card in my mobile (Samsung Galaxy S4 Mini running CyanogenMod 11 with encryption) with a bigger one.īefore I pulled the old one out I backed up its content into a tar file:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |