Updated 64-bit Gentoo Image for RPi3 Released (now also for RPi3B+ and RPi4B)

[sakaki]

1. chromium-ozone build does means ozone-wayland patch?
2. chromium is .121 now.

1. I think we're talking about the same thing: I mean the variant that has this commit and this one.
2. I'm just going by what's in the standard Gentoo tree for chromium, then trying to get those to build (to a (lawfully) binary distributable form, so no patent-encumbered software codecs etc). It's such a heavy load to test-build (8hrs or so on a binfmt_misc/QEMU chroot x86_64 server) I haven't really got the bandwidth to try creating my own ebuilds for other release points atm, unfortunately ><

Best, sakaki

[DougieLawson]

Apart from the glacially slow download from GitHub this is now booted on my 3B with the official RPF 7" display. I just need to fix it up for the US layout keyboard I'm using and get the screen rotated through 180 degrees.

Gentoo is still a mystery. I've used RedHat & SuSE with RPM. I've used DebIan, Ubuntu, Mint & Raspbian with apt. Gentoo has to have something different.

Sakaki-san thank you so much for your efforts and keep it up.

[cjan]

chromium .121, Security Fixes and Rewards: High CVE-2019-5786: Use-after-free in FileReader.

[sakaki]

<...> this is now booted on my 3B with the official RPF 7" display. I just need to fix it up for the US layout keyboard I'm using and get the screen rotated through 180 degrees.

Adding lcd_rotate=2 to /boot/config.txt and restarting will achieve the screen rotation efficiently. Apologies if you already knew that ^-^

Best, sakaki

[Gavinmc42]

Gentoo is still a mystery

Yep , there is a difference between know how something works and just using.
Sakaki knows what that is I just know it works better than any other 64bit Pi OS so I'm using it.

Going to try to break latest version this weekend by using it.
It's probably in one of Sakaki's wiki somewhere, do a "sudo porthole" in a terminal to get a gui version of Raspbians's "sudo apt-get install...."
It takes much longer to install things, that's just the way Gentoo works.

[sakaki]

chromium .121, Security Fixes and Rewards: High CVE-2019-5786: Use-after-free in FileReader.

Apologies cjan, I see now what you were getting at. That's quite a nasty bug, and has reportedly been expoited in the wild already, so needs addressing ><

Fortunately chromium-72.0.3626.121 (which has the fix) has hit the main Gentoo tree, so I've put together an modified ebuild with the necessary patches to build on arm64, built it, and pushed the resulting binary package to the binhost.

To upgrade, just open a terminal and issue:

Code: Select all

demouser@pi64 ~ $ sudo emaint sync --repo rpi3
demouser@pi64 ~ $ sudo emerge -vu www-client/chromium

As this is a binary package, the process should only take about 10 minutes or so.
The youtube playback issue is fixed in this version also. I'll put out a bugfix 1.4.1 release of the gentoo-on-rpi3-64bit image shortly with this updated chromium bundled by default; I don't feel comfortable with a vulnerable version being on there, in 1.4.0.

Thank you for pointing this out!

Best, sakaki

Update 10 March 2019: a new 1.4.1 release of the image is available, which fixes this issue; please see this post for more details.

[cjan]

sorry, didn't have p3 or p3+ so test in ALARM.
kernel-4.19.27 and build ffmpeg with patches plus -enable-v4l2-m2m and bcm2385_codec module loaded.
but didn't find /dev/video{10 11 12}, any idea?

[sakaki]

sorry, didn't have p3 or p3+ so test in ALARM.
kernel-4.19.27 and build ffmpeg with patches plus -enable-v4l2-m2m and bcm2385_codec module loaded.
but didn't find /dev/video{10 11 12}, any idea?

Apologies, not sure I quite follow: by "ALARM", do you mean ... a Pi booted with an archlinuxarm system? Or something else?

Which Pi model exactly are you using? And, what do you see output from dmesg?

Best, sakaki

[cjan]

O..p, Rpi2B and archlinuxarm kernel follow 'rpi-update'.
when ffplay -vcodec h264_v4l2m2m, say 'could not fine a valid device'.

in dmesg, does it matter?
vc4_hdmi 3f902000.hdmi: ASoC: can't open interface 3f902000.hdmi: -19

[sakaki]

Is this a v1.2 Pi2B, booted under a 64-bit kernel? Or <=v1.2 booted under a 32-bit kernel?

[cjan]

Is this a v1.2 Pi2B, booted under a 64-bit kernel? Or <=v1.2 booted under a 32-bit kernel?

Rip2b <1.2 32bit armv7 kernel.

[cjan]

in dmesg, does it matter?
vc4_hdmi 3f902000.hdmi: ASoC: can't open interface 3f902000.hdmi: -19

[sakaki]

Not sure, I've only booted 64-bit 4.19 kernels so far, and only on RPi3 B and B+ devices.

Perhaps post in this 4.19 thread instead (I see you have posted to it in the past)? There's example dmesg output there (although mostly on 3B+ devices), e.g. in this post, which shows the /dev/video{10,11,12} interfaces coming up OK under a 32-bit kernel; you may be able to compare that with what you're seeing.

Sorry, but I can't really help you further on this one ><

Best, sakaki

[cjan]

sorry, save your weekend time, im just test & play around, thanks.

[cjan]

found FULL vc4-kms driver cause the issue, FAKE driver have /dev/vidoe10.

[sakaki]

found FULL vc4-kms driver cause the issue, FAKE driver have /dev/vidoe10.

Works for me on both vc4-fkms-v3d and vc4-kms-v3d, on 64-bit (RPI3B and B+).

One thought, have you set at least "gpu_mem=96" in /boot/config.txt?

Because, if you use "gpu_mem=16", per 6by9 this will cause start_x.cd (=cut down) to be loaded, and as the name suggests not everything is supported when that happens:

...
The codecs are built into the standard start.elf and start_x.elf. They are NOT built into start_cd.elf (cutdown).

[*]I am current specifying "dtoverlay=vc4-kms-v3d,cma-256" and "gpu_mem=16" in /boot/config.txt; are those sensible settings? When the v4l2 camera or v4l2 m2m codecs interfaces are in use, does gpu_mem need to be increased or is this irrelevant?

"gpu_mem=16" will trigger the bootloader to load start_cd.elf, so no codecs.
...

It caught me out!

best, sakaki

[cjan]

gpu_mem=128, but another issue raise.
ffmpeg build with 3 patches, and -enable-libv4l2 & -enable-v4l2-m2m, but got error..

Code: Select all

[h264_v4l2m2m @ 0x58925490] driver 'bcm2835-codec' on card 'bcm2835-codec'
    Last message repeated 2 times
[h264_v4l2m2m @ 0x58925490] Using device /dev/video10
[h264_v4l2m2m @ 0x58925490] driver 'bcm2835-codec' on card 'bcm2835-codec'
[h264_v4l2m2m @ 0x58925490] no v4l2 output context's buffers
[h264_v4l2m2m @ 0x58925490] can't configure decoder                                                    
Failed to open file 'jellyfish-10-mbps-hd-h264.mkv' or configure filtergraph 

does build ffmpeg need extra option?

[sakaki]

Don't use all 3 of the patches 6by9 listed, just 2 of them: omit the 6d23e1aa79337d4f9468b8dadcebab824c01669b patch (I found it caused problems during the probe phase).

Best, sakaki

[cjan]

ok, rebuild with 2 patches only

Code: Select all

patching file libavcodec/v4l2_buffers.c
patching file libavcodec/v4l2_context.c
patching file libavcodec/v4l2_m2m_dec.c

same error

[sakaki]

Hmm, well may be a kernel issue or difference between 32/64 bit I suppose...

My (working) ffmpeg build-flags as follows:

Code: Select all

demouser@pi64 ~ $ ffmpeg
ffmpeg version 4.1.1 Copyright (c) 2000-2019 the FFmpeg developers
  built with gcc 8.2.0 (Gentoo 8.2.0-r6 p1.7)
  configuration: --prefix=/usr --libdir=/usr/lib64 --shlibdir=/usr/lib64 --docdir=/usr/share/doc/ffmpeg-4.1.1-r2/html --mandir=/usr/share/man --enable-shared --cc=aarch64-unknown-linux-gnu-gcc --cxx=aarch64-unknown-linux-gnu-g++ --ar=aarch64-unknown-linux-gnu-ar --optflags='-march=armv8-a+crc -mtune=cortex-a53 -O2 -pipe' --disable-static --enable-avfilter --enable-avresample --disable-stripping --disable-optimizations --disable-libcelt --enable-nonfree --disable-indev=oss --disable-indev=jack --disable-outdev=oss --enable-bzlib --disable-runtime-cpudetect --disable-debug --disable-gcrypt --disable-gnutls --disable-gmp --enable-gpl --enable-hardcoded-tables --enable-iconv --disable-libtls --disable-lzma --enable-network --disable-opencl --enable-openssl --enable-postproc --disable-libsmbclient --enable-ffplay --enable-sdl2 --disable-vaapi --disable-vdpau --enable-xlib --enable-libxcb --enable-libxcb-shm --enable-libxcb-xfixes --enable-zlib --disable-libcdio --disable-libiec61883 --disable-libdc1394 --disable-libcaca --disable-openal --enable-opengl --enable-libv4l2 --disable-libpulse --disable-libdrm --disable-libjack --disable-libopencore-amrwb --disable-libopencore-amrnb --disable-libcodec2 --disable-libfdk-aac --disable-libopenjpeg --disable-libbluray --disable-libgme --disable-libgsm --disable-mmal --disable-libmodplug --disable-libopus --disable-libilbc --disable-librtmp --disable-libssh --disable-libspeex --disable-libsrt --enable-librsvg --disable-ffnvcodec --enable-libvorbis --disable-libvpx --disable-libzvbi --disable-appkit --disable-libbs2b --disable-chromaprint --disable-libflite --disable-frei0r --disable-libfribidi --disable-fontconfig --disable-ladspa --disable-libass --disable-lv2 --enable-libfreetype --disable-librubberband --disable-libzmq --disable-libzimg --disable-libsoxr --enable-pthreads --disable-libvo-amrwbenc --enable-libmp3lame --disable-libkvazaar --disable-libaom --disable-libopenh264 --disable-libsnappy --enable-libtheora --disable-libtwolame --disable-libwavpack --disable-libwebp --enable-libx264 --disable-libx265 --enable-libxvid --disable-gnutls --disable-mipsdsp --disable-mipsdspr2 --disable-mipsfpu --disable-altivec --disable-amd3dnow --disable-amd3dnowext --disable-aesni --disable-avx --disable-avx2 --disable-fma3 --disable-fma4 --disable-mmx --disable-mmxext --disable-sse --disable-sse2 --disable-sse3 --disable-ssse3 --disable-sse4 --disable-sse42 --disable-xop --cpu=armv8-a+crc --disable-doc --disable-htmlpages --enable-manpages
  libavutil      56. 22.100 / 56. 22.100
  libavcodec     58. 35.100 / 58. 35.100
  libavformat    58. 20.100 / 58. 20.100
  libavdevice    58.  5.100 / 58.  5.100
  libavfilter     7. 40.101 /  7. 40.101
  libavresample   4.  0.  0 /  4.  0.  0
  libswscale      5.  3.100 /  5.  3.100
  libswresample   3.  3.100 /  3.  3.100
  libpostproc    55.  3.100 / 55.  3.100
Hyper fast Audio and Video encoder
usage: ffmpeg [options] [[infile options] -i infile]... {[outfile options] outfile}...

Best, sakaki

[sakaki]

Hello,

I've just posted a v1.4.1 bugfix release of my bootable 64-bit Gentoo image for the RPi3 (model B and B+) on GitHub (here, includes full download instructions).

For screenshots, and details of the major changes - including camera and hardware codec support - introduced in 1.4.0, please see my earlier post.

A changelog from the prior release image (with upgrade instructions) may be viewed here, but in summary:

• Upgraded the bundled chromium web browser, to www-client/chromium-72.0.3626.121-r1; this version fixes the serious CVE-2019-5786 bug (thanks to cjan for pointing this out), and also a problem that was preventing videos playing correctly on YouTube.
• Made the boot-time services rpi3-spidev and rpi3-i2cdev core dependencies of rpi3-64bit-meta, so they are always installed, and also modified the rpi3-i2cdev service, so it only loads the relevant kernel module if I2C is turned on in /boot/config.txt. Fixes an issue where turning on I2C in the pyconfig_gen application was not sufficient to have it enabled after reboot. Thanks to procount for reporting.
• Various minor ebuild tidy-ups.
• All packages brought up-to-date against the Gentoo tree, as of 19 February 2019 (with the exception of chromium, which has been backported to address a serious security concern; as noted above).

Users on the prior 1.4.0 release can simply run "sudo genup" in a terminal to upgrade to 1.4.1 (or wait for the weekly autoupdate to do it on your behalf). Manual upgrade instructions for users on older versions of the image are also provided, here.

Have fun ^-^

And, as always, any problems or comments, please post either in this thread, or in the project's (sticky) thread on the Gentoo forums (here).

sakaki

[sakaki]

For those who prefer a NOOBS-style installer, the v1.4.1 gentoo-on-rpi3-64bit images are now also available for install through PINN (called gentoo64 (=regular) and gentoo64pt (=pi-top) there).

Best, sakaki

PS: Many thanks to procount for helping me set up my own PINN repository (https://isshoni.org/pinn/os), and kindly linking it into the official set!

[sakaki]

chromium v73 (www-client/chromium-73.0.3683.86-r1) is now available on the binhost!

To get it immediately, issue:

Code: Select all

demouser@pi64 ~ $ sudo emaint sync --auto
demouser@pi64 ~ $ sudo emerge -vu www-client/chromium

Thanks to Khumarahn for pointing out the necessary aarch64 patches.

Best, sakaki

[sakaki]

I've just posted a short article on the gentoo-on-rpi3-64bit wiki, covering setup of an xrdp server on your RPi3 (here).

Brief instructions for creating a custom TLS keypair (and forcing its use) are also provided.

Example of connecting from Windows 10 (using its built-in remote desktop client):



(Instructions for connection via VNC may also be found on the wiki, here).

best, sakaki

[sakaki]

I've just posted a v1.4.2 update release of my bootable 64-bit Gentoo image for the RPi3 (model B and B+) on GitHub (here, includes full download instructions).

This release sees a number of significant version bumps to the bundled packages: for example, GCC from v8 to v9, Clang from v7 to v8, Chromium from v72 to v74, Firefox Quantum from v65 to v67 etc.

Here's a screenshot of the image running on an RPi3B+:



As always, you can burn the image (~1,511MiB compressed) to a microSD card (>=16GB), then boot your RPi3 from it directly (the root partition will be automatically resized to fill the card on first boot). Full instructions for download and use are provided on the project's GitHub page.

The image contains a complete (OpenRC-based) Gentoo system (including a full Portage tree, up-to-date as of 12 June 2019) - so you can run emerge operations immediately - and has a reasonably populated userland (see the screenshot above; all the apps shown, and many others, are bundled), so that you can get productive without having to compile or configure anything first (unless you want to, of course ^-^). Just download, xzcat to a microSD card (or use Etcher), and boot!

A changelog from the prior release image (with upgrade instructions) may be viewed here, but in summary:

• Kernel updated, to sys-kernel/bcmrpi3-kernel-bis-bin-4.19.49.20190611. Fixes some Bluetooth issues experienced with the prior 4.19 kernel, and adds POE fan and (built-in) btrfs support. Support for the RPi camera module (and leverage of the hw video codecs via v4l2) is retained.
• Per email request from @iugamarian, added the following applications to the image:
  • media-video/mpv;
  • net-p2p/transmission;
  • sys-fs/ncdu; and
  • app-misc/mc.
• Various minor ebuild tidy-ups.
• All packages brought up-to-date against the Gentoo tree, as of UTC EOD 12 June 2019 (which means e.g., www-client/firefox-67.0, www-client/chromium-74.0.3729.169-r1, app-office/libreoffice-6.2.4.2 etc. are bundled; a full list of installed packages may be found here).

As before, a variant image for the Pi-Top v1 (an RPi3-based DIY laptop) is also included. Manual upgrade instructions for users on older versions of the image are also provided, here.

Have fun ^-^

And, as always, any problems or comments, please post either in this thread, or in the project's (sticky) thread on the Gentoo forums (here).

Best,

sakaki

PS: I aim to release the PINN variant of this v1.4.2 image in a week or so, real-world commitments permitting ^-^