Talk:Raspberry Pi/Quick Install Guide

From Gentoo Wiki
Jump to:navigation Jump to:search
Note
Before creating a discussion or leaving a comment, please read about using talk pages. In particular, sign comments using ~~~~ and add new discussions at the bottom of the page. New discussions should be made visible with {{Talk|date = 2024-05-19}}.
== Discussion title ==

{{Talk|date = 2024-05-13}}

A comment [[User:Larry|Larry]] 13:52, 13 May 2024 (UTC)
: A reply [[User:Sally|Sally]] 11:29, 14 May 2024 (UTC)
:: Another reply [[User:Larry|Larry]] 09:15, 19 May 2024 (UTC)
:: Your reply ~~~~

Navigate to first:

Changed downloadable tarball http address for Raspberry Pi B+

Talk status
This discussion is done as of 2023-09-07.

The right link is: http://gentoo.osuosl.org/releases/arm/autobuilds/current-stage3-armv6j_hardfp/stage3-armv6j-20160326.tar.bz2 --Best, Pál (talk) 18:48, 3 October 2016 (UTC)

Already changed so closing.
Immolo (talk) 10:15, 7 September 2023 (UTC)

Keeping ntp-client command in install guide

Talk status
This discussion is done as of 15 July 2022.

The command "rc-update add ntp-client default" has been removed and replaced with a link to the relevant ntp config page, which is fair enough. However for the typical installed, especially a beginner, this command is pretty much essential. Otherwise you end up with the magical 1 January 1970. I know for 99% of the Gentoo RPi that I install will need this service. Any objections? Baldy (talk) 19:52, 10 February 2013 (UTC)

A fix was provided (Special:Diff/13277). --Blacki (talk) 03:13, 15 July 2022 (UTC)

Moving "Cross building" to its own page

Talk status
This discussion is done as of 15 July 2022.

We now have a very comprehensive section on distcc and cross building, I think it needs its own page.

  • People may already have gentoo running on there RPi and just looking to setup distcc
  • Not everyone will want to setup distcc, its not essential.

Of course we can leave a description of it and link to the page. Baldy (talk) 19:52, 10 February 2013 (UTC)

A fix was provided (Special:Diff/13385). --Blacki (talk) 03:47, 15 July 2022 (UTC)

Root password reset

Talk status
This discussion is still ongoing.

Just tried this howto, everything went fine except the root reset password by editing /etc/shadow, I fixed it by copying the shadow password for root from my laptop. mamac (talk) 23:23, 16 April 2013 (UTC +2)

naming of the network interface

Talk status
This discussion is done.

Isn't eth0 still valid ? — The preceding unsigned comment was added by Toralf (talkcontribs) 13:59, 28 August 2013‎

The name of a network interface can change. Recent udev versions have different name schema. YMMV. --Grknight (talk) 19:55, 8 November 2018 (UTC)

Why not merge this page to Raspberry Pi

Talk status
This discussion is done as of 2023-09-07.

Both seem on the same topic, about the gentoo installation on raspberry pi. Why not merge them? AleiPhoenix (talk) 15:24, 5 September 2013 (UTC)

Different ways to do the same task so worth keeping both.
Immolo (talk) 10:18, 7 September 2023 (UTC)

Installing gentoo headless

Talk status
This discussion is still ongoing.

I installed gentoo on my raspberry pi without a display and input devices. I had to bring forward some steps before unmounting the SD:

  • Add net.eth0 to default runlevel
  • Add sshd to default runlevel
  • set root password

Should something like this be added? Should it be under notes or an extra point? jo77ah 14:40 13 July 2015 (UTC +2)

Raspberry Pi 2 B Changes

Talk status
This discussion is still ongoing.

With regard to Raspberry Pi 2 B there are some changes that should be put into the documentation, some of them related only to RPi2B and some also affect current installation:

  • it is Cortex-A7 which is arm7a arch
  • raspberrypi/firmware/boot now contains kernel.img and kernel7.img (idk if kernel7.img is picked up automatically or it must be specified in config.txt, i did not test that)
  • raspberrypi/modules now contains two directories, at this moment these are 4.1.15+ and 4.1.15-v7+
  • overclocking information is missing for armv7 (good information can be found for example in this article and the discussion below: http://haydenjames.io/raspberry-pi-2-overclock/)

— The preceding unsigned comment was added by Fordfrog (talkcontribs) 2 January 2016

New OpenSSH And Remote root Login Problem

Talk status
This discussion is still ongoing.

With new OpenSSH one of the default configuration parameters prevents being able to log in as root to the box: PermitRootLogin prohibit-password It should be changed to "yes" instead, at least for the first remote root login.

— The preceding unsigned comment was added by Fordfrog (talkcontribs) 2 January 2016

Using force_turbo=1 Might Void Warranty

Talk status
This discussion is done as of 15 July 2022.

According to this article http://haydenjames.io/raspberry-pi-2-overclock/ using force_turbo=1 might void warranty. In the discussion there is written that it voids the warranty when combined with overclocking. — The preceding unsigned comment was added by Fordfrog (talkcontribs) 2 January 2016

force_turbo=1 is the same as using the performance CPU governor. Its the overclocking/overvolting that sets the warranty bit.
--NeddySeagoon (talk) 11:07, 8 March 2017 (UTC)
A fix was provided (Special:Diff/856625). --Blacki (talk) 05:08, 15 July 2022 (UTC)

Splitting Memory

Talk status
This discussion is still ongoing.

It should mention that for graphical environments gpu_mem should be higher (on RPi2B 256+?) and on headless it can go down to 16. — The preceding unsigned comment was added by Fordfrog (talkcontribs) 2 January 2016

This is not simple any more. The gpu_mem is only used by the original graphics driver. The open source vc4 driver uses the CMA provided by the kernel. Setting a high gpu_mem when the vc4 driver is in use reserves RAM for the GPU that it will never use.
--NeddySeagoon (talk) 11:07, 8 March 2017 (UTC)

Raspberry Pi's firmware: config file of the kernel?

Talk status
This discussion is done.

So, one can get the precompiled kernel binaries from: git://github.com/raspberrypi/firmware/

and just copy it to /boot/ directory on microSD card.

But, what if one want to know what are the included options for this kernel? There is no config file at all, right? Where can one find this config file? --Best, Pál (talk) 18:58, 9 May 2016 (UTC)

The config is included as a loadable module.
modprobe configs
Then /proc/config.gz appears
--NeddySeagoon (talk) 11:07, 8 March 2017 (UTC)

CPU Governor

Talk status
This discussion is done as of 15 July 2022.

Under install kernel and modules should the page describe how to change the CPU Governor. As distributed, it defaults to powersave. Thats not good for build performance. On the basis that this is a quick install guide. It could just be a note to users.

There are thermal implications of using ondemand or performance.

--NeddySeagoon (talk) 11:07, 8 March 2017 (UTC)

The article already explained how to change the CPU governor in Raspberry_Pi/Quick_Install_Guide#Optional_cpupower. --Blacki (talk) 05:35, 15 July 2022 (UTC)

WiFi Setup (chroot)

Talk status
This discussion is still ongoing.

For PiZeroW1 and PiZero2, getting networking up requires some work, since the SoC only has WiFi. Borrowing from the AMD64 instructions, this requires a chroot operation. After step 3.5 (clear password), enter a chroot as follows:

  1. Create a /mnt/gentoo/lib/firmware directory when prepping the SD card
  2. Download wifi-firmware tarball from https://github.com/RPi-Distro/firmware-nonfree
  3. Extract bcrm firmware: tar -xzvf rpi-brcm-bullseye.tar.gz -C /mnt/gentoo/lib/firmware --strip-components=4 firmware-nonfree-bullseye/debian/config/brcm80211/brcm
  4. Extract cypress firmware: tar -xzvf rpi-brcm-bullseye.tar.gz -C /mnt/gentoo/lib/firmware --strip-components=4 firmware-nonfree-bullseye/debian/config/brcm80211/cypress
  5. Copy the DNS info over, following step 1.2 in the AMD64 instructions
  6. Set mountpoints for /dev,/proc,/sys,/tmp, and /run following step 1.3 in the AMD64 instructions
  7. Enter chroot following step 1.4 in the AMD64 instructions
  8. Sync emerge in chroot (~40min): emerge --sync --quiet
  9. Select your emerge profile using eselect profile list and eselect profile set ...
  10. Move to protage distdir directory: cd $(portageq distdir)
  11. Find the required URLs for wpa_supplicant tarballs: emerge --fetchonly --pretend wpa_supplicant
  12. Use wget to download the tarballs: wget <http://url1> <http://url2> <http://url3>
  13. Exit chroot, shutdown the host OS, and boot your new Gentoo SD

Then once booted into Stage3 bring up wlan0

  1. Set the local date/time: date --set="YYYYMMDD HH:MM"
  2. Install wpa_supplicant with emerge wpa_supplicant
  3. Configure wpa_supplicant as described in step 2 of the AMD64 instructions
  4. Continue with step 4 of the ARM instructions taking care to replace references to eth0 with wlan0

BriandDK (talk) 21:39, 9 November 2023 (UTC)

Select Profile require a previous emerge sync

Talk status
This discussion is still ongoing.

Step 4.3 (select profile) fails since no previous emerge --sync operation has not yet been performed. An emerge --sync operation needs to be done previously, either in a chroot, before booting Stage3, or immediately after bringing the network up.

BriandDK (talk) 22:20, 9 November 2023 (UTC)

Missing bcm2708-rng

Talk status
This discussion is still ongoing.

Step 7.2 (load bcm2708-rng) fails since bcm2708-rng doesn't appear to be in either the RPi firmware repo or the Stage3 tarball

BriandDK (talk) 02:17, 10 November 2023 (UTC)