Hi, have you gone into the pi400 firmware settings and changed the boot order so the usb-ssd is the first boot? Thanks
As part of the image install, the /etc/fstab and /boot/cmdline.txt are edited and the partition labels are changed to UUID numbers. So at boot up, the boot loader is looking for a particular partition UUID number instead of a partition label such as /dev/sda1, etc. So it should always find the device to boot from.
EDIT:
However, the uSD connector must be empty. If a uSD card is connected, it will receive priority and boot from the uSD.
Pudge
Okay so i have figured out the hardware problem why my SSD wonāt boot. Itās definitely the controller card in the external case that has a kingston ssd in it hooked to usb. So far i have it booting now on raspberry pi OS. I just have to figure out now how to edit the boot files on EOS image to do the same.
What you have to do and this should work for Pi 4 also is plug the drive into a working system and use lsub to find the Device values after ID for VID and PID. Then you need to add a kernel parameter to disable UASP for USB 3.0 because the controller isnāt supported. You need to edit the /boot/cmdline.txt file with nano.
sudo nano /boot/cmdline.txt
ADD
usb-storage.quirks=xxxx:xxx:u ( exchange x with VID and PID values from lsusb for the device)
Then it seems to boot okay. Now i have to figure out how to edit this file also on the image created from the arm installer.
2 Likes
arch-chroot
Iām not sure how to do this on ARM. I was going to try to edit it on a working system but Iām not sure i can since it hasnāt used the process to boot on the image that the installer creates and it isnā't actaully installed yet?
Edit: With rasberry PI OS i used the imager and i was able to edit the file on a working system that i imaged it on.
Use your 
install in an existing micro sd card on your Pi. Then attach the SSD with burnt image. arch-chroot and change the boot parameter. Now poweroff the Pi remove micro SD and try to boot from SSD
Couldnāt you just hook hook it up to your computer, mount the partition in your file manager and navigate to the file and edit it?
1 Like
This is much easier lol. Iām dumb
1 Like
Thatās what i did on Pi OS but not sure i can on EOS arm image that isnāt created yet. Does that file exist even on the image the installer creates before actually installing EOS Arm?
yes it does
1 Like
Yeah! Then it will be easy!
Edit: I did try KDE on the micro sd card but i found the cursor is not good. Xfce works great.
Iām going to try this very soon!
Donāt do this. For me KDE never worked on a micro SD.
1 Like
Go to your x86_64 machine, in a terminal create a Temporary folder off of home.
cd into that folder. Insert your USB SSD. Now
$ lsblk -f ( to find the device names of the SSD)
$ mkdir MP1 MP2
$ sudo mount /dev/sdX1 MP1
$ sudo mount /dev/sdX2 MP2
$ sudo nano MP2/etc/fstaB
FIX WHAT YOU NEED TO
$ sudo nano MP1/boot/cmdline.txt
fix what you need to
$ sudo umount MP1 MP2
$ rmdir MP1 MP2
Make sure to fully umount the USB SSD
Insert to RPi 400 and boot with an empty uSD slot
Pudge
Iām not sure how to do this for just a usb stick? Because they werenāt booting also? But it seems this issue is quite prevalent with certain drives and or enclosures that are usb 3.0 or higher. Itās a controller issue as far as i can tell from what Iām reading.
Edit: I also found that i donāt have to set it to boot from USB first as it has two settings. Either sd card or usb and if it isnāt present it looks for the other.
Edit2: Iām not 100% this is going to work yet just because it works on the Pi OS on the ssd. I was getting kernel panic on EOS Arm on the SSD also. 
@Pudge @sradjoker @pebcak
Just want to report this works like a charm on the ssd. It boots instantly and not like before taking forever and not completing and or giving a kernel panic etc. So the kernel parameter is the way to go for this issue. Now i can install to it because it has booted right up on the image.
Edit: Now i have Arm!
2 Likes
Welcome our fellow brother in ARMs!!
I tried kde again on the ssd and it has cursor issues. The cursor speed isnāt correct.
Edit: What i meant by this is the cursor acceleration is way off. Xfce works perfectly but on kde itās not for me anyway.
this was the first problem I had. Its like deja vu 
@Pudge should we make this the default.
usbhid.mousepoll=6
works for me all the time. It doesnāt add that much to the CPU load either
This is for KDE on RPi 4 only?
Pudge