It was already mentioned many times in this particular thread (and a few different approaches to it). Here is what I've done:
pepeEL wrote: ↑Fri Oct 11, 2019 11:36 am
Interesting (and accurate) set of instructions. I alwaysclicky wrote: ↑Fri Oct 11, 2019 11:43 amIt was already mentioned many times in this particular thread (and a few different approaches to it). Here is what I've done:
https://www.maketecheasier.com/boot-up- ... hard-disk/
Code: Select all
sudo su -
It'll be done when it's done. Constant pestering will not make it appear any faster. And in the general scheme of things, no, a lot of people are not waiting for it. We are making 100 of thousands of Pi4's a WEEK. Compare that with the number of people asking for USB boot......
Spot on.dickon wrote: ↑Fri Oct 11, 2019 11:25 amIt's quite a complicated thing. Much moreso than network, I would think. For network, you only need to write a driver for the hardware -- surprisingly simple in most cases; I did one for the DEC Tulip back in the day, and it wasn't much over about a 1000 lines of assembly, if that -- and enough of a UDP/IP stack (with trivial ARP, DHCP, and TFTP implementations; none of which is difficult) to load the next-stage.
For USB you've got to initialise the hardware, enumerate all the devices, handle hubs, ideally handle as many quirks as possible, and then you've got to have enough of a SCSI stack -- the USB mass-storage protocol is basically SCSI over USB -- to start probing the attached discs to read stuff from. After than you can hand it off to the partition and FAT parsers you've already got for the SD card mode, but there's still a lot of work to be done. All in, AIUI, about 32K of ROM space.
Not a simple job.
I have no problem with people waiting, quietly.
Would 'noatime' help with SSD and controller I have no idea if it implemented trim and such ("ostrich head in sand" is first association that came to me to describe my approach in this case)?dickon wrote: ↑Fri Oct 11, 2019 11:53 amInteresting (and accurate) set of instructions. I alwaysto get a full login shell, where PATH is setup correctly, and I'd recommend removing the 'noatime' from the root stanza in /etc/fstab as it's quite useful and doesn't have the same issues on a proper HD that it does on an SD card (basically, the extra write duty won't be an issue on a proper device, which it is on an SD card).
Code: Select all
sudo su -
All noatime does is stop the kernel writing atime datestamps when files are read from. These are mostly delayed until things are written to anyway, but they're worth disabling on something as limited as an SD card. Personally I find atimes quite useful and I wouldn't disable them on a proper disc.
Code: Select all
Still going through merging, should be up soon. See https://github.com/raspberrypi/rpi-eepr ... ot_beta.mdroyhenderson wrote: ↑Fri Oct 11, 2019 3:47 pmIs there any documentation available regarding network boot on RPi-4? I've trawled the board but most of what I've found looks to be a series of solutions to encountered problems …
I really don't understand this kind of comment. As has been stated many times in this thread (I guess it's my turn now) you can already boot with your rootfs on USB with only the initial boot files on an SD-card. There is really no speed nor reliability advantage against booting entirely from USB. The only advantage I see is that booting entirely from USB frees up the SD-card slot.
Exactly the opposite, in fact. The Pi 3B[+] for example will try to look for an SD card to boot from for a few seconds before it tries to boot from USB or network. So the start of the boot at least will take longer than just booting initially from SD card.
Q. Do you think we are stupid
This was quite unnecessary. Is it called 'feeding the troll''?jamesh wrote: ↑Mon Oct 21, 2019 8:50 amQ. Do you think we are stupid
A. No, we are not, and someone is working on it right now. You made a colossal mistake - that of think that just because YOU haven't seen any progress, that there hasn't been any progress. News for you, that's not how it works.
You clearly do not realise how complex it actually is to do this. Requires an entire open source (not GPL) USB 2/3stack to be found/developed, to cope with whatever can be plugged in. Plus a USB HW driver that works via the PCIe interface, so PCIe also needs to work. All in the bootloader! Huge amount of very complex work.
As for boot speed - already referenced above - quicker to use an SD card!!!!!
Reliability? Got any figures? I've had terrible reliability from SSD's and great reliability from SD cards...