Hyperion Entertainment Message Boards

I purchased recently a 64GB Sandisk Cruzer Blade USB 2.0 stick, with the idea to collect all the Linux distros and kernelsI I use regularly on a single disk unit. But when trying to use it, I found a strange problem: Uboot does not recognize it as an USB storage device IF it is the only USB disk connected!?! (checked with "usb reset" + "usb storage/tree") The USB port used does not make any difference.

But if I have also an another USB stick (e.g. a similar Cruzer Blade but 32 GB) connected, and the 64GB one is in a port wich comes LATER in the USB port hierarchy, it is recognized normally. But if it is earlier in the hierarchy than the 32 GB one, it is not recognized.

What should I do to fix this problem? Starting from the bottom, what is the best way to prep (or low level format) a USB stick for Linux (both Fat32 and Ext parttions needed), so that it would work also with U-Boot? I already tried to create a new partioton table (MBR) using GParted, but it did not do any difference.

BTW, 32 GB Cruzer blades I have do not show this problem, but I cannot remember how I prepared them.

Hi Roland,

Have you seen any error messages? I also use Sandisk USB sticks but I haven’t had such problems yet. I usually create a small FAT16 partition on the USB stick. After that I copy the dtb file and the kernel to the stick. Then I create a big partition without a file system on the stick. Afterwards I copy a Linux img for example the MATE PowerPC Remix with dd to the second big partition. Then I increase it with Gparted.

Cheers,
Christian

@Roland

Download MATE PowerPC Remix 2017 0.9 img: http://forum.hyperion-entertainment.biz/viewtopic.php?f=58&t=3592&start=110#p44580

Installation instructions: http://forum.hyperion-entertainment.biz/viewtopic.php?f=58&t=3592&start=50#p41120

I've good luck with Sandisk Cruizer USB drives using an msdos partition table, a FAT32 partition (for dtb and kernel) and an ext4 partition (dd image onto partition, then correct partition size in gparted). However, I did have issues with a PNY USB drive that I was never able to get uboot to recognize.
---Casey

xeno74 wrote:Have you seen any error messages? I also use Sandisk USB sticks but I haven’t had such problems yet.

No, except those from U-Boot when you try to boot from a nonexistent disk. At OS level (both AmigaOS and Linux), after booting from some other unit, my Sandisk seems to work normally - partitions (both Fat and Ext) and files are accessible without problems.

Have you used also 64GB Cruzer Blades? The 32 GB ones has worked ok for me.

I usually create a small FAT16 partition on the USB stick. After that I copy the dtb file and the kernel to the stick. Then I create a big partition without a file system on the stick. Afterwards I copy a Linux img for example the MATE PowerPC Remix with dd to the second big partition. Then I increase it with Gparted.

I have used FAT32 for boot partition, but I tried now also FAT16. There was no difference... I also copied several partitions/distros from working USB disks to the 64GB Sandisk, but they did not have effect on U-boot behaviour. I have also already the Remix 0.9 image downloaded but have not tested it yet.

Roland,

I use very often a SanDisk Ultra Fit USB 3.0 Flash Drive.

Cheers,
Christian

caseycullen wrote:I've good luck with Sandisk Cruizer USB drives using an msdos partition table, a FAT32 partition (for dtb and kernel) and an ext4 partition (dd image onto partition, then correct partition size in gparted). However, I did have issues with a PNY USB drive that I was never able to get uboot to recognize.

Have you also used 64GB Sandisk Cruizers? This is the first USB stick I have of that size, so no experience from other units. In the smaller sizes I have had problems mostly with Kingston DT50 series. They worked slowly and unreliably with Linux, and they are also heating strongly when being just connected. I would recommend to avoid them....

32 GB Sandisk Cruzer Blades has worked best with Linux... Only two times the boot partition (FAT 32) has been corrupted for unknown reason (did not do any writing/deleting operations), but reformatting fixed it.

Roland wrote: Have you also used 64GB Sandisk Cruizers?

I have one with Debian PowerPCSPE for my Tabor board. It works without any problems.

— Christian

xeno74 wrote:

Roland wrote: Have you also used 64GB Sandisk Cruizers?

I have one with Debian PowerPCSPE for my Tabor board. It works without any problems.

Ok, thanks... What revision # does your Sandisk have? Mine has 1.00. If it the same, then the problem must be in the U-Boot of X5000. Unfortunately I do not have a Tabor to test it there .