Raspberry pi 5 status

SHA512 is correct.
I used dd command and it looks success.

Hmm, not sure if sha512 is totally correct though. Is this "improperly formatted" message normal?
% sha512sum -c CHECKSUM.SHA512-FreeBSD-14.2-RELEASE-arm64-aarch64-RPI FreeBSD-14.2-RELEASE-arm64-aarch64-RPI.img.xz
FreeBSD-14.2-RELEASE-arm64-aarch64-RPI.img.xz: OK
sha512sum: WARNING: 2984186 lines are improperly formatted
 
I don't know if this is normal, i've never used sha512sum with the -c parameter.

Try without it and copy the resulting hash into your clipboard, and use the search function of your browser to compare the hash with the one in my previous post.
 
I don't know if this is normal, i've never used sha512sum with the -c parameter.

Try without it and copy the resulting hash into your clipboard, and use the search function of your browser to compare the hash with the one in my previous post.
1740045974543.png


I'm convinced the hash code of the downloaded image file is correct.
 
Hmm, not sure if sha512 is totally correct though. Is this "improperly formatted" message normal?
I've just downloaded the image and the checksum file, put them together in a direction, run the command and didn't receive any error message.
Code:
iso $ sha512sum -c CHECKSUM.SHA512-FreeBSD-14.2-RELEASE-arm64-aarch64-RPI
FreeBSD-14.2-RELEASE-arm64-aarch64-RPI.img.xz: OK
iso $

"improperly formatted" I saw this message a lot in the past when I was on Linux, it's a common error, but is not relevant if the hash is the same, it's not difficult to verify just run the command sha512sum without any option and compare with the checksum file using your eyes only, not fun but it works ;)
 
this is what i do when i need to verify checksum of a file when there is no checksum file provided by but a hash instead.

1. Calculate hash of downloaded file.
sha256sum file-x-y-z > checksum
2. Copy the original hash and replace current file hash with the original one
$EDITOR checksum
Code:
## current file hash
c9b25de21a3b1934187476d7f6d79d724b73355a01046b059264ed4fa72fc2bc  file-x-y-z
## replace current hash with original hash
2fa9906bcfa80ca875807baafc3a53dc14ad08c0d2774a2ad9af9478e3870b3c  file-x-y-z
3. Run checksum control with -c flag to verify hash from a file.
Code:
sha256sum -c checksum
file-x-y-z: OK
 
After multiple downloads and burns using different tools (raspberry imager, dd and win32diskimager) and under different systems(raspberry, FBSD and windows), i believe the image file I download is correct, even the sha512 checksum gives me "improperly formatted" message. Followed the instructions downloaded RPi5_UEFI_Release_v0.3.zip and copied the 3 files to the root of EFI partition of SD card. The problem is when I try to boot the system it stops the half way. See attached picture.
 

Attachments

  • IMG_7438.JPEG
    IMG_7438.JPEG
    1.1 MB · Views: 12
Can you write same image to a USB flash drive stick and boot from a USB flash drive stick on your Raspberry Pi 5? The last 3 lines in your photo detail the problem as being a bad file system 'inode' that the FreeBSD boot sequence can not read the /bin/sh file to execute that file that does not exsist. A solution write image to a USB Flash drive, then fsck the UFS file system on the USB flash drive stick in an unmounted condition. Correct the filesystem error in the UFS filesystem. Mount Then make an image of the corrected filesystem USB flash drive stick. Write this corrected image to your SD card to boot with. Tell us how it goes for you. Sorry for complicated instructions, for a bad image file. Other may suggest other methods to fix problems, or try a 14.1 image in place of a 14.2 image?
https://download.freebsd.org/ftp/releases/ISO-IMAGES/14.1/
https://download.freebsd.org/ftp/releases/ISO-IMAGES/14.2/
 
Back
Top