search

maxnet / berryboot

Berryboot -- Boot menu / OS installer
http://www.berryboot.com/
Other
799 stars 135 forks source link

Rasperry Pi 4 USB Boot With Latest Firmware #734

Open actraiser30 opened 2 years ago

actraiser30 commented 2 years ago

Hello I installed in my Raspberry Pi 4 the latest stable firmware 2022-01-25 and tried to install berryboot after in my 2.5 "HDD/SDD and it did not work installation finish successful but no boot,although the same procedure with the previous stable Firmware 2021-04-29 works flawless,apparently something was changed with the USB boot in the latest firmware Will a Berryboot Kernel/firmware update fix this issue??

Thanks

schmurian commented 2 years ago

+1

hupokoristik commented 1 year ago

(edited for clarity)

Oct 5, 2022 mini update

Berryboot (BB) working ok preliminarily. Running all from my 2.5-in. SSD (Samsung 250 GB). Never involved any microSD card.

►My process for SSD-Only and No-Micro-SD for Berryboot:

  1. Prepped SSD: deleted existing partitions, created one partition and formatted fat32.

  2. Attached SSD to desktop PC.

  3. Unzipped BB's boot files then copied to SSD.

  4. Detached SSD from desktop PC.

  5. Attached SSD to Rpi4-8gb (5.15.61-v8+ release; #1579 version).

  6. Booted Rpi4-8gb with BB for first time from SSD (with no other storage media attached).

  7. Once inside the BB loader (for the first time), I connected to network and pulled down just one of the older 'stock,' from-network IMGs. After first boot, I shut down Rpi4-8gb.

  8. Detached SSD from Rpi4-8gb.

  9. Attached SSD to a linux desktop.

  10. Reduced the size of the 'berryboot' ext4 partition using gparted from 232 GiB to 128 GiB, carefully keeping unchanged the smaller 127 MiB now-vfat 'boot' partition. Furthermore, from unallocated space, I created a new third partition of 72 GiB (ext4) on the SSD, electing not to allocate 100% of what was available. With hindsight, I possibly could have sized the primary partition to 128 GiB in prepping my SSD back in step 1. Probably most eupeptic is to avoid moving the start address of the ‘berryboot’ partition (left edge of the box in gparted).

  11. I copied IMG files to this new 72 GiB partition of the SSD. These IMG files should have already been downloaded and unzipped separately.(†††)

  12. Detached SSD from linux PC.

  13. Attached SSD to Rpi4-8gb.

  14. Booted Rpi4-8gb with BB for second time from SSD (again, with no other storage media attached).

  15. Inside the BB loader (for second time), I added several OSs via "Copy OS from USB stick" ---- which promptly detected the only other partition . . . specifically the SSD's 72 GiB partition chock full 'o unzipped IMGs.

(†††) Berryserver has present-vintage IMGs. Download from there. Use gzip -d command to decompress the ‘img.gz’ files; notably outside of WSL, powershell’s tar -xvzf gave me error: unrecognized archive format. A meaningful amount of time is required to download each OS img (depending on network config, your results may vary) and further time is required to perform each decompression. If you want to experiment with a fistful of new-to-you IMGs as well as gain time, then you might also want to dual-task and initiate downloads from berryserver prior to then in parallel with the steps above -- quite possibly using a second desktop PC.

►Added Considerations:

• SSD CONNECTION HARDWARE

My 2.5-in. SSD is attached via USB via a SATA cradle board with UASP, which in ways is an analogue of the one found in ArgonOne's m.2 Case. Preliminarily, most SATA-USB connectors/ enclosures/ docks/ bays/ daughter boards for m.2 and 2.5-in. SSD formats (with and without UASP) should work ok.

• POWER

I use a vrm-like 'power hat' (also made by Geekworm-SupTronics) that funnels a clean 5V to each of Rpi and SSD as well as powering my active cooling.

I use a 5A-rated PSU that feeds approx. 6V to the power hat.

►In Closing

On a preliminary basis, I continue testing my OSs; and thus far things with Berryboot are going ok, keeping fingers crossed. Whereas I am aware there are open issues submitted to these github pages. When I encounter issues, I shall as needed update this and post in issues.

Thanks.

Ever good luck and safe travels, friends and neighbors.

symbios24 commented 1 year ago

(edited for clarity)

Oct 5, 2022 mini update

Berryboot (BB) working ok preliminarily. Running all from my 2.5-in. SSD (Samsung 250 GB). Never involved any microSD card.

►My process for SSD-Only and No-Micro-SD for Berryboot:

  1. Prepped SSD: deleted existing partitions, created one partition and formatted fat32.
  2. Attached SSD to desktop PC.
  3. Unzipped BB's boot files then copied to SSD.
  4. Detached SSD from desktop PC.
  5. Attached SSD to Rpi4-8gb (5.15.61-v8+ release; #1579 version).
  6. Booted Rpi4-8gb with BB for first time from SSD (with no other storage media attached).
  7. Once inside the BB loader (for the first time), I connected to network and pulled down just one of the older 'stock,' from-network IMGs. After first boot, I shut down Rpi4-8gb.
  8. Detached SSD from Rpi4-8gb.
  9. Attached SSD to a linux desktop.
  10. Reduced the size of the 'berryboot' ext4 partition using gparted from 232 GiB to 128 GiB, carefully keeping unchanged the smaller 127 MiB now-vfat 'boot' partition. Furthermore, from unallocated space, I created a new third partition of 72 GiB (ext4) on the SSD, electing not to allocate 100% of what was available. With hindsight, I possibly could have sized the primary partition to 128 GiB in prepping my SSD back in step 1. Probably most eupeptic is to avoid moving the start address of the ‘berryboot’ partition (left edge of the box in gparted).
  11. I copied IMG files to this new 72 GiB partition of the SSD. These IMG files should have already been downloaded and unzipped separately.(†††)
  12. Detached SSD from linux PC.
  13. Attached SSD to Rpi4-8gb.
  14. Booted Rpi4-8gb with BB for second time from SSD (again, with no other storage media attached).
  15. Inside the BB loader (for second time), I added several OSs via "Copy OS from USB stick" ---- which promptly detected the only other partition . . . specifically the SSD's 72 GiB partition chock full 'o unzipped IMGs.

(†††) Berryserver has present-vintage IMGs. Download from there. Use gzip -d command to decompress the ‘img.gz’ files; notably outside of WSL, powershell’s tar -xvzf gave me error: unrecognized archive format. A meaningful amount of time is required to download each OS img (depending on network config, your results may vary) and further time is required to perform each decompression. If you want to experiment with a fistful of new-to-you IMGs as well as gain time, then you might also want to dual-task and initiate downloads from berryserver prior to then in parallel with the steps above -- quite possibly using a second desktop PC.

►Added Considerations:

• SSD CONNECTION HARDWARE

My 2.5-in. SSD is attached via USB via a SATA cradle board with UASP, which in ways is an analogue of the one found in ArgonOne's m.2 Case. Preliminarily, most SATA-USB connectors/ enclosures/ docks/ bays/ daughter boards for m.2 and 2.5-in. SSD formats (with and without UASP) should work ok.

• POWER

I use a vrm-like 'power hat' (also made by Geekworm-SupTronics) that funnels a clean 5V to each of Rpi and SSD as well as powering my active cooling.

I use a 5A-rated PSU that feeds approx. 6V to the power hat.

►In Closing

On a preliminary basis, I continue testing my OSs; and thus far things with Berryboot are going ok, keeping fingers crossed. Whereas I am aware there are open issues submitted to these github pages. When I encounter issues, I shall as needed update this and post in issues.

Thanks.

Ever good luck and safe travels, friends and neighbors.

Hello there any idea how to update berryboot to the latest kernel ??

Your quide is good but too complicated any easier way ???