Talk:Raspberry Pi Install Guide

From Gentoo Wiki
Jump to:navigation Jump to:search
This is a Talk page - please see the documentation about using talk pages. Add newer comments below older ones, sign comments using four tildes (~~~~), and indent successive comments with colons (:). Add new sections at the bottom of the page, under a heading (== ==). Please remember to mark sections as "open for discussion" using {{talk|open}}, so they will show up in the list of open discussions.

Pi Zero 2 W

Talk status
This discussion is still ongoing.

The creation of the partitions in this new guide does not appear to work for the Raspberry Pi Zero 2 W. I faithfully followed the partition creation and while my final disk works fine on a Raspberry 4B, the same disk will not book on a Raspberry Pi Zero 2 W. This is because the Raspberry Pi Zero 2 W requires a bootable first partition. I then created another disk following the guidance of and I was able to get postings... however, I ended up with a kernel panic relating to Broadcom. I'll document what I did differently to create the bootable SD HC, and, more importantly, how I overcame the kernel problem (which I am hopeful to accomplish in the future). Note I am using kernel 6.6 or 6.7 as I wanted something at 6.2 or above in order to pick up some Realtek wifi modules. Let this comment serve as a warning that treatment for the Raspberry Pi Zero 2 W will be slightly different. I had been using the GenPi64 images and found I could use the same card either on a Raspberry Pi 4B or Zero 2 W. What I ended up doing was building out my Gentoo image on the Rpi4B and then using the card on the Pi Zero 2 W to run my data gathering without needed a lot of RAM. I decided to break away from the GenPi64 project and try this guide which averts the very long build time that the GenPi64 project takes (it builds everything to assure a working image) (there also was a personality clash). I'll update more with my findings. I logged a topic on the Raspberry Pi Forum

Update 3/28/24: I have posted a long explanation on the Raspberry Pi Forum on the topic just referenced about the importance of not using a GUID Partition Table if you card is to be used on a Raspberry Pi Zero 2 W.

Jlpoole (talk) 05:01, 15 February 2024 (UTC)

This used to be true with older GPU code. Only MSDOS partition tables were supported and the bootable flag had to be set.
How old is the GPU firware?
--NeddySeagoon (talk) 18:34, 15 February 2024 (UTC)
What does GPU stand for? I regret that I have difficulty keeping track of acronyms.
--Jlpoole (talk) 03:01, 20 March 2024 (UTC)

Firmware Instructions apparently out of date

Talk status
This discussion is still ongoing.

Recent changes to the raspberrypi/firmware repo appear to invalidate the firmware installation instructions. Following the instructions printed here as of this date yields this error in the rpi firmware bootloader:

Trying partition: 0
type: 16 lba: 2048 'mkfs.fat' ' V       ^ ' clusters 62429 (16)
Read config.txt bytes      359 hnd 0x200f
usb_max_current_enable default 0 max-current 5000
Device-tree file "bcm2712-rpi-5-b.dtb" not found.

The installed operating system (OS) does not indicate support for RaspberryPi 5
Update the OS or set os_check=0 in config.txt to skip this check.

I was able to boot by rsyncing the boot partition from a previous gentoo installation, into which I had compiled the kernel from raspberrypi/linux, version 6.7.4-v8-16k+. I might suggest that the instructions be updated to include cross-compilation instructions from x86, straight from the downstream repo.

Device-tree file "bcm2712-rpi-5-b.dtb" not found. is odd. The Pi has found the /boot partition, read config.txt but cannot find bcm2712-rpi-5-b.dtb so the kernel is missing the addresses of the hardware.
In my view the main page of this guide is too big already and it should be split into a number of sub pages. Cross compiling the kernel could then be included as a sub page or as a reference to a separate page. It's a common practice for embedded systems, not just Pi's. A common shared page may help to reduce the clutter and maintenance.
--NeddySeagoon (talk) 18:45, 15 February 2024 (UTC)

Rpi5 Wifi & Bluetooth

In the instruction prior to the section 4.3.4 "Raspberry Pi 5 WiFi/Bluetooth Firmware" ("WifiBluetooth"), you have the reader stationed under /mnt/gentoo/home. In WifiBluetooth, the command line example shows just "#root" with no directory path prefixing the prompt. I think for sake of consistency, the current directory should appear presumably as "/mnt/gentoo/home #". Or, is the user suppose to change directories? I am assuming the user is supposed to be under /mnt/gentoo/home and then performs a "git clone" to create the directory "firmware-nonfree".

--Jlpoole (talk) 02:51, 20 March 2024 (UTC)

6.3 [/etc/]fstab

I am referencing this wiki for an installation of Gentoo on an NVMe on a Raspberry Pi 5. I have a Raspberry 4 running off of a USB drive, /dev/sda, and just realized for NVMe, things might be different. I'm just making note here that consideration for an NVMe install should not be overlooked/forgotten. I'm reading Jeff Geerling's blog NVMe SSD boot with the Raspberry Pi 5 now. My Pimoroni NVME with a Crucial 500 GB P3 Plus, PCIe 4.0 NVME M.2 SSD shows up within Raspberry's latest release (Bookworm?) as /dev/nvme0n1 which I have divided into 4 partitions: boot, swap, home, & root as directed by this guide. I don't expect problems at this time, but saw the reference re: /dev/sda and thought mention of NVMe would be appropriate. Update: no problems, just have to reference /dev/nvme0n1 which I think is hard-coded by the lower firmware/system files if an NVMe is active.

Jlpoole (talk) 23:14, 27 March 2024 (UTC)

WiFi/Bluetooth Firmware

There is a section Raspberry Pi 5 WiFi/Bluetooth Firmware which ostensibly was created to help people get Rpi5 installed. Nontheless, we must not forget the other models. This is an area where roads may diverge meaning what model of Raspberry Pi you are preparing for will determine which files to copy over. For instance, I'm on a Rpi 5 building a master build directory to copy images for Rpi4 and Pi Zero 2 W, so the possible divergence what firmware may be needed become crucial.

Here is a colorized listing in HTML of the Raspberry Pi Foundation's tree showing the relation of files to soft links for various Rpi models: [Edit added:] Likewise, here is a colorized HTML listing of the Bluetooth tree:

While the colored tree above will help me determine what I need, I'm not sure how working with the file listing should be articulated and look forward to some suggestions.

Jlpoole (talk) 23:14, 27 March 2024 (UTC)