Re: Thank you Ronald, for step by step directions to boot Raspberry Pi 5.

Ronald Klop <[email protected]>
Newsgroups gmane.os.freebsd.devel.arm
Message-ID <858113745.221622.1761470176660@localhost>
 
Van: Fred Finster <[email protected]>
Datum: zaterdag, 25 oktober 2025 20:04
Aan: Ronald Klop <[email protected]>
CC: [email protected]
Onderwerp: Thank you Ronald, for step by step directions to boot Raspberry Pi 5.
> 
> I will follow your directions to boot on the Raspberry   Pi 500 keyboard model, ( which is based on the Raspberry Pi5 with a heat sink.   I am still puttering around.  I have the Ras Pi 500 booting Debian Raspberry Pi Linux Operating system.  Yes it is a D0 stepping of the BCM2712 D0.  I need to connect a 3.3V USB serial port to capture the boot messages output from the Raspberry Pi 5.
> 
> https://wiki.freebsd.org/RonaldKlop/Raspberry%20Pi%205%2016GB  Ronald Klop booting Raspberry Pi 5 16GB
> 
> Are you able to run a command:  'md5deep -zltr *' to audit the files and share the results?  I have placed my 'md5deep -zltr  *'  results here in a blog post here  
> 
> https://ghostbsd-arm64.blogspot.com/2025/10/freebsd-143-booting-freebsd-on.html
> 
> https://github.com/NumberOneGit/rpi5-uefi/releases   D0 stepping Raspi 5 software
> 
> https://download.freebsd.org/releases/VM-IMAGES/14.3-RELEASE/aarch64/Latest/  Virtual Memory images
> 
> https://download.freebsd.org/releases/VM-IMAGES/14.3-RELEASE/aarch64/Latest/FreeBSD-14.3-RELEASE-arm64-aarch64-zfs.raw.xz   Image that Ronald Klop used to create his Raspberry Pi 5 boot image
> 
> I connected a USB ethernet dongle.  Which Make and  Model.  What are the USB Vendor ID and Product ID for this USB ethernet dongle, Ronald?    I have available a Nintendo model.
> 
>   Thanks again for your help,  Ronald Klop.
> 
> Fred Louis Finster
> 
> https://ghostbsd-arm64.blogspot.com   Place I post Raspberry Pi   FreeBSD Aarch64 blog posts. ( and GhostBSD-Arm64 builds)
> 


Have fun setting it up. Here the info you requested.
# md5sum * overlays/*
d033812243c150e88afd9a32f3677f69  RPI_EFI.fd
1be945bb8ed0d95f8a99de45f3d85f28  bcm2712-d-rpi-5-b.dtb
27b07dc2ccc6a4d9defdfa7e6da1e9d2  bcm2712-rpi-5-b.dtb
870fa76dacf722d12f01d56e9f8d65f6  bcm2712-rpi-500.dtb
cd9ec5de2f83efa0f80ce16dab964440  bcm2712-rpi-cm5-cm4io.dtb
40be2399c9ec7dbeb848738208a86403  bcm2712-rpi-cm5-cm5io.dtb
362c22e6a82545d4315edd0bad4c31d2  bcm2712-rpi-cm5l-cm4io.dtb
9e8624d1862fac39410259315a1b9302  bcm2712-rpi-cm5l-cm5io.dtb
602679b2e6cdbe96bb75eafb6b683ab2  bcm2712d0-rpi-5-b.dtb
7bfe92010349bec31f95f78c70df2334  config.txt
md5sum: overlays: Is a directory
9957d90ac6c4f2d2c16aba9cc1cef5d6  overlays/bcm2712d0.dtbo
Why do we have different RPI_EFI.fd hashes?
# usbconfig -d ugen1.2 -v
ugen1.2: <USB 10/100/1G/2.5G LAN Realtek Semiconductor Corp.> at usbus1, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=ON (64mA)
ugen1.2.0: ure0: <Realtek USB 10/100/1G/2.5G LAN, class 0/0, rev 3.20/31.04, addr 1>

  bLength = 0x0012 
  bDescriptorType = 0x0001 
  bcdUSB = 0x0320 
  bDeviceClass = 0x0000  <Probed by interface class>
  bDeviceSubClass = 0x0000 
  bDeviceProtocol = 0x0000 
  bMaxPacketSize0 = 0x0009 
  idVendor = 0x0bda 
  idProduct = 0x8156 
  bcdDevice = 0x3104 
  iManufacturer = 0x0001  <Realtek>
  iProduct = 0x0002  <USB 10/100/1G/2.5G LAN>
  iSerialNumber = 0x0006  <4013000001>
  bNumConfigurations = 0x0003
[...] 
Regards,
Ronald.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.