Gentoo Forums

• Updated the uploadable firmware file /lib/firmware/brcmfmac43455-sdio.bin (for the RPi3B+/4B's CYW43455 WiFi/BT chip) to match that provided by the Raspbian distribution (by adding their newer version of this file to the sys-firmware/brcm43430-firmware package, controlled by the 43455-fix USE flag, removing it from sys-kernel/linux-firmware, basis the same USE flag, and adding the 43455-fix USE flag to the default profile). This change will (hopefully) improve WiFi performance / stability meaningfully, particularly on the RPi4B (where, for some APs, the older driver was preventing association entirely). Thanks to haaldemir for reporting.
• Bumped media-libs/raspberrypi-userland, as 6by9's pointer-wrangling PR#586 (64-bit userland MMAL) has now been tidied up and merged into raspberrypi-userland upstream.
• Upgraded the shipped kernels, to bcm{rpi3,2711}-kernel-bis-bin-4.19.89.20191217.
• Various minor ebuild tidy-ups.
• All packages brought up-to-date against the Gentoo tree, as of 14 December 2019 (so e.g., sys-devel/clang is now at 9.0.1_rc2).

spork_kitty wrote:So, I was lucky and received a Pi4 for the holidays! I have an existing install of genpi on my pi3, though, that I'd like to preserve in my hardware upgrade. What are the big things I should be paying attention to during my migration? Is a kernel upgrade/rebuild all I really need?

(EDIT: Backing up the entire SD card right now, as step 0. )

demouser@pi64 ~ $ eix rpi-64bit-meta

demouser@pi64 ~ $ eix rpi3-64bit-meta

Sakaki wrote:

spork_kitty wrote:So, I was lucky and received a Pi4 for the holidays! I have an existing install of genpi on my pi3, though, that I'd like to preserve in my hardware upgrade. What are the big things I should be paying attention to during my migration? Is a kernel upgrade/rebuild all I really need?

(EDIT: Backing up the entire SD card right now, as step 0. )

If you started with a modern version of the gentoo-on-rpi-64bit image (>=1.5.0), it should "just work" (i.e., you should be able to move the same card between your 3B/B+ and 4B RPis at will).
[snip]

If in doubt, write the current (v1.5.3) image to a fresh card, and boot that; then you can use its filesystem (and installed package set + configs) as a reference. But, what you want to do is definitely possible ^-^

orion777 wrote:What about the video capturing over the camera? Is it done via built-in codec or it is done by using CPU resources? Because the CPU load is about 2.6 with live preview, tested over remote desktop.. (all 4 kernels are loaded about 60%)

demouser@pi64 ~ $ ffmpeg -f video4linux2 -input_format h264 \
  -video_size 1280x720 -framerate 30 -i /dev/video0 \
  -vcodec copy -an -f matroska test.mkv

UK locale settings, keyboard mapping, timezone and WiFi regulatory domain; however, these are easily changed if desired. See the Gentoo Handbook (here and here) for details on the first three;

 /etc/X11/xorg.conf.d/00-keyboard.conf

section "InputClass"
        Identifier "system-keyboard"
        MatchIsKeyboard "on"
        Option "XkbLayout" "us"
EndSection

/etc/default/keyboard

XKBMODEL=“pc78”
XKBLAYOUT=“us” 

ian.au wrote:Sakaki,
Locale, Timezone and Wifi domain are all straightforward, but changing the keymaps variable per the wiki (in my case from "gb" to "us") doesn't successfully remap the system keyboard, to do that requires editing in

Code: Select all

 /etc/X11/xorg.conf.d/00-keyboard.conf

Sakaki wrote:Hi Ian,

not sure what is causing the screen blanking issue you experienced, not something I've seen here (and I have RPi4s that have been running this image since it was released). I do recall there was one earlier issue with screensaver blanking, that had an autostart service added to fix it; this may be conflicting with anything you are trying to do. Please see:

https://github.com/sakaki-/genpi64-over ... -r3.ebuild

One other thing you could try would be to select Applications -> Settings ->RPi Config Tool, select "Force HDMI output, even if no display detected", and save (rebooting when prompted, and electing to keep your settings on reboot).

As to the X screensaver issue, the simplest way around that is probably to issue:

Code: Select all

demouser@pi64 ~ $ sudo emaint sync --repo genpi64
demouser@pi64 ~ $ sudo emerge -v xfce-extra/xfce4-xkb-plugin

and once this completes, right-click in an empty part of the top (grey) panel bar, and select Panel -> Add New Items... from the drop-down. Then click on the "Keyboard Layouts" entry (you may have to scroll through the list to find it) and click the Add button.

You should now see a flag on your panel bar. Right-click on this and choose Properties from the drop-down. Under "Behavior" choose Manage layout: "globally" (from the menu there) and then click Close.

Then select Applications -> Settings -> Keyboard, Layout tab, and uncheck "Use system defaults". Remove all keyboards from the list, then add your own layout (you can add multiple if you like; if you do so, you can then click on the flag icon to switch between them, and/or set a hotkey to do that in the Applications -> Settings -> Keyboard, Layout dialog).

You should now find that the X screensaver works fine (and your /etc/X11/xorg.conf.d/00-keyboard.conf entry will be ignored).

You may need to re-login once to get everything to "take".

I'm going to aim to ship future releases with this plugin installed - makes setting up the keyboard much easier (not sure how I missed it initially! ><)

Sakaki wrote:Thanks Neddy ^-^

Speaking of h/w video decoding, although the gentoo-on-rpi-64bit image now supports access to the RPi's built-in h/w video codecs via both V4L2-M2M and MMAL endpoints (and ships with a custom version of ffmpeg that can utilise both), neither firefox nor chromium currently exploit these out of the box (see e.g. this post and this thread), although I think Raspbian's 32-bit custom Chromium build can use MMAL codecs, so it may be possible to adopt some of their patches (not something I've looked at yet). PRs on this topic welcome!

Biker wrote:Was wondering if it would make sense to remove the distcc-pump from the (commented) FEATURES= in make.conf as provided in a fresh installation?

And also if it should still be recommended in https://github.com/sakaki-/gentoo-on-rp ... tcc-Client to have distcc-pump in the FEATURES ?

nvertigo wrote:I've a serious issue when using sys-boot/rpi3-64bit-firmware-1.20200114:

The boot process stops after checking the fses (since it's at that point, when the screen blanks for a split second, I guess it happens when the gpu fw should be loaded).

This doesn't happen if I use sys-boot/rpi3-64bit-firmware-1.20190925.

It doesn't matter if I use my own kernel build or your prebuild kernel.

Sakaki wrote: Ack. I've seen this myself also, in recent testing.

ara ~ # alias emerge
alias emerge='FEATURES="-userpriv" /usr/bin/pump /usr/bin/emerge'

adler ~ # ls -la /usr/local/bin/aarch64-unknown-linux-gnu-clang*
-rwxr-xr-x 1 root root 65 Jan 18 09:36 /usr/local/bin/aarch64-unknown-linux-gnu-clang
-rwxr-xr-x 1 root root 67 Jan 18 09:36 /usr/local/bin/aarch64-unknown-linux-gnu-clang++
-rwxr-xr-x 1 root root 69 Jan 18 09:31 /usr/local/bin/aarch64-unknown-linux-gnu-clang++-9
-rwxr-xr-x 1 root root 67 Jan 18 09:34 /usr/local/bin/aarch64-unknown-linux-gnu-clang-9
adler ~ # cat /usr/local/bin/aarch64-unknown-linux-gnu-clang
#!/bin/bash
exec /usr/lib/llvm/9/bin/clang --target=aarch64 "$@"
adler ~ # cat /usr/local/bin/aarch64-unknown-linux-gnu-clang++
#!/bin/bash
exec /usr/lib/llvm/9/bin/clang++ --target=aarch64 "$@"
adler ~ # cat /usr/local/bin/aarch64-unknown-linux-gnu-clang++-9
#!/bin/bash
exec /usr/lib/llvm/9/bin/clang++-9 --target=aarch64 "$@"
adler ~ # cat /usr/local/bin/aarch64-unknown-linux-gnu-clang-9
#!/bin/bash
exec /usr/lib/llvm/9/bin/clang-9 --target=aarch64 "$@"
adler ~ # ls -la /usr/lib/distcc/aarch64-unknown-linux-gnu-clang*
lrwxrwxrwx 1 root root 16 Jan 18 09:37 /usr/lib/distcc/aarch64-unknown-linux-gnu-clang -> /usr/bin/distccd
lrwxrwxrwx 1 root root 16 Jan 18 09:37 /usr/lib/distcc/aarch64-unknown-linux-gnu-clang++ -> /usr/bin/distccd
lrwxrwxrwx 1 root root 16 Jan 18 09:37 /usr/lib/distcc/aarch64-unknown-linux-gnu-clang++-9 -> /usr/bin/distccd
lrwxrwxrwx 1 root root 16 Jan 18 09:37 /usr/lib/distcc/aarch64-unknown-linux-gnu-clang-9 -> /usr/bin/distccd