I need tutoring
Posted: Sat Jul 28, 2018 12:06 am
The Terminal command "ls /media/amigaone" lists four items on my X5000.
First, 0ff72520-8d43-468d-b4f8-6cbe7ea35f1f
This corresponds with a Desktop USB icon labeled "119 GB Volume." It contains a folder, "backupfolder," the target of MATE 16.04's scheduled backups, and "newSDCARD.png." I don't know what the latter is doing there, but it seems to be a window dump of Terminal when I was dd'ing, in two steps, "uboot.bin" from /dev/mmdblk0 to /dev/sdc. I have no memory of what that was all about, but I don't think it is a problem.
Second, 5913-1FA6
This corresponds to a small USB icon labeled "1.1 GB Volume," contents named "cyrus.dtb" and "uImage-4.18."
Third, 91dd8491-ac97-44c7-9611-dcabfec171a3
This is the media name of a red SD desktop icon, "2.9 GB Volume." Content that shows when it is clicked is cyrus-4.13.11-jm.config cyrus_5020.dtb installer.scr System.map Ubuntu-Mate_Installer_Uboot_Script.txt uImage-4.18 uImage-cyrus uRamdisk X5000_U-Boot_Commands.txt, plus according to a terminal ls command lost+found in blue letters.
I have no idea where to find "2.9 GB Volume" physically on my X5000! Where should I look?
Fourth, UBUNTU
This one corresponds to a full-size USB icon labeled "UBUNTU" with this stuff inside: cyrus-4.13.11-jm.config cyrus_5020.dtb cyrus.dtb installer.scr System.map Ubuntu-Mate_Installer_Uboot_Script.txt uImage-4.18 uImage-cyrus uRamdisk
Obviously I have more memory devices than I need to run Ubuntu, and at least two of the three contain some files that aren't relevant. But my real problem is this: Each of those three contains a copy of uImage-4.18. If I type "fatload usb 0:1 1000000 uImage-4.18" as a Uboot command, it succeeds quickly. But if I have set root to /dev/sdc2 first, then the fatload is rejected; it claims it can't read uImage-4.18.
I wonder which of the three uImage-4.18s listed above it is trying to read and why should having /dev/sdc2 as root have any effect on the matter?
First, 0ff72520-8d43-468d-b4f8-6cbe7ea35f1f
This corresponds with a Desktop USB icon labeled "119 GB Volume." It contains a folder, "backupfolder," the target of MATE 16.04's scheduled backups, and "newSDCARD.png." I don't know what the latter is doing there, but it seems to be a window dump of Terminal when I was dd'ing, in two steps, "uboot.bin" from /dev/mmdblk0 to /dev/sdc. I have no memory of what that was all about, but I don't think it is a problem.
Second, 5913-1FA6
This corresponds to a small USB icon labeled "1.1 GB Volume," contents named "cyrus.dtb" and "uImage-4.18."
Third, 91dd8491-ac97-44c7-9611-dcabfec171a3
This is the media name of a red SD desktop icon, "2.9 GB Volume." Content that shows when it is clicked is cyrus-4.13.11-jm.config cyrus_5020.dtb installer.scr System.map Ubuntu-Mate_Installer_Uboot_Script.txt uImage-4.18 uImage-cyrus uRamdisk X5000_U-Boot_Commands.txt, plus according to a terminal ls command lost+found in blue letters.
I have no idea where to find "2.9 GB Volume" physically on my X5000! Where should I look?
Fourth, UBUNTU
This one corresponds to a full-size USB icon labeled "UBUNTU" with this stuff inside: cyrus-4.13.11-jm.config cyrus_5020.dtb cyrus.dtb installer.scr System.map Ubuntu-Mate_Installer_Uboot_Script.txt uImage-4.18 uImage-cyrus uRamdisk
Obviously I have more memory devices than I need to run Ubuntu, and at least two of the three contain some files that aren't relevant. But my real problem is this: Each of those three contains a copy of uImage-4.18. If I type "fatload usb 0:1 1000000 uImage-4.18" as a Uboot command, it succeeds quickly. But if I have set root to /dev/sdc2 first, then the fatload is rejected; it claims it can't read uImage-4.18.
I wonder which of the three uImage-4.18s listed above it is trying to read and why should having /dev/sdc2 as root have any effect on the matter?