Code: Select all
sudo nano /boot/cmdline.txt
Code: Select all
sudo nano /boot/cmdline.txt
They're now available in 4.4.47+ and 4.4.47-v7+ kernels/bootcode which you'll get with sudo rpi-config. They are not yet in the main-stream apt-get kernel package.anderml1955 wrote:Are the new boot options now in the mainstream kernel and bootloader? If so can we "unhold" then and revert to the normal apt-get updates.
Follow-up - did this with two new USB sticks; one Sandisk USB3 and a cheap PNY USB2, both from Wal-mart. The USB3 resulted in similar performance to the microSD card, the USB2 card was extremely slow - similar to the performance noted in previous post. I assume this must be a "USB2 stick quality" issue and not a USB2 v USB3 issue, since the Pi3 doesn't have USB3 ports. At some point I may try a more expensive USB2 stick and see how it performs.kwalk wrote:Thanks, Sudhir. I'll try a new USB this weekend. Was this USB spec related or a bad (slow) USB that didn't meet specs to begin with? My initial effort was with a brand new PNY USB 2.0 stick I bought from Office Max. I don't remember the specs on it, but could probably look them up from their website. RPi3 has only USB 2.0, so USB 3.0 stick won't necessarily be any faster, is that correct?
Thanks,
Keith
It looks good, but I have not read it from start to finish (TL:DR being a good thing in this case).paulv wrote:I have updated the header of the original post somewhat to bring it more in line with the UUID vs /dev/sd* changes for the filesystem identifiers, now that the Foundation changed to the more robust method since the 2017-04-10 version. I also updated the link to the Model 3 description for booting from a USB drive.
At a later date, when the new method is more established and most users will have migrated, I will remove the "simple" method.
Enjoy!
paulv
As expected this "just works"PeterO wrote: Have you covered the case where you can just "dd" the new raspbian image file onto a blank HDD ? I believe this works and will create a small boot partition and use the rest of the drive for the root file system (which may not be an ideal situation IMO).
I'll be trying it in the next few days when I but a new HDD to replace the one I dropped the other day![]()
Is using the more reliable /dev/sda method going to break something? I regularly have to fix debian/ubuntu systems that by default use uuids to identify drives to switch to the more reliable /dev/sdx method. It is more reliable, because I make drive backups using image copies of the drive and when you swap to a different drive, the uuid will change and the system won't boot. Using /dev/sdx, either drive boots fine.paulv wrote:This procedure will allow you to run Debian from a USB connected drive, instead of the SD card.
Starting with the 2017-04-10 kernel version, the Foundation changed to a more reliable way of using drive identifiers. This post still shows both methods, but note that using /dev/sd* for the filesystem is no longer recommended. Please implement the procedure for "Multiple Drives" further down. to stay compatible.
Paul
If you look at the very first post, there is a note about booting directly from a disk for the RPi Model 3.dvaitman wrote:Hi there,
If I want to boot from a USB with a RPi3, how would the process change?
Users browsing this forum: No registered users and 10 guests