User avatar
sakaki
Posts: 348
Joined: Sun Jul 16, 2017 1:11 pm

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

Fri Sep 06, 2019 11:47 am

Hi nersos,

so, it is possible to rebuild any package in Gentoo yourself with custom settings (in fact, ultimately that's kind of the point of using it ^-^), but to be fair, it's perhaps not the easiest distro to start out on if you want to go off-piste (you mentioned in your first post you were new to Linux). In case you are interested though, I have some notes on the process here.

In any event, streaming video sites are hardly my specialist area (I check the bundled browsers work against various YouTube streams as part of my pre-ship tests for the OS image, but that's about it) ><

You may have more luck if you post on the ARM and/or multimedia sections of the Gentoo forums (here and here), or even a query in the General discussion section of this site.

If https://www.stream4free.live/tf1-live-stream does require Flash (and I haven't looked in depth at it to check), please note that this is deprecated and on its way to being removed permanently in Chrome (and Chromium). There are some open source players available for Flash, but I haven't tried them.

As to Netflix, I think this requires the binary widevine DRM plugin to run. Unfortunately, the default Gentoo ebuilds for it (www-plugins/chrome-binary-plugins) are currently only keyworded for 64-bit Intel. I'm pretty sure there are aarch64 versions around somewhere (given Android phones etc), but this is quite far from my domain of expertise.

Also, other than (unavoidable) boot software and device firmware, I avoid shipping anything with gentoo-on-rpi-64bit that cannot be rebuilt by end-users from source, under an open-source license. So DRM binary blobs are not something I am comfortable working with.

Apologies therefore that I can't assist further with this ><

Best wishes, and I hope you find a solution. And thanks for trying Gentoo!

sakaki

nersos
Posts: 6
Joined: Thu Sep 05, 2019 4:58 am

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

Fri Sep 06, 2019 3:46 pm

Maybe im going to go to libelec or somenthing like this, you know if libelec you can use chrome? to go to another websites outside kodi? or maybe inside kodi by addons?

User avatar
sakaki
Posts: 348
Joined: Sun Jul 16, 2017 1:11 pm

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

Fri Sep 06, 2019 4:04 pm

nersos wrote:
Fri Sep 06, 2019 3:46 pm
Maybe im going to go to libelec or somenthing like this, you know if libelec you can use chrome? to go to another websites outside kodi? or maybe inside kodi by addons?
Pass, but if you post a short query in the General discussion forum here, I'm sure someone who does know about this stuff will be able to assist.

Best, sakaki

User avatar
Gavinmc42
Posts: 3736
Joined: Wed Aug 28, 2013 3:31 am

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

Sat Sep 07, 2019 11:30 am

Sakai, thanks for the PonyC ebuild it was no pain at all to install it this time ;)

USB stick insertion now pops up the file manager, so thanks for that too.

Let's see if QGIS will build :D
I'm dancing on Rainbows.
Raspberries are not Apples or Oranges

ejolson
Posts: 3575
Joined: Tue Mar 18, 2014 11:47 am

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

Sun Sep 08, 2019 5:27 am

sakaki wrote:
Fri Sep 06, 2019 4:04 pm
nersos wrote:
Fri Sep 06, 2019 3:46 pm
Maybe im going to go to libelec or somenthing like this, you know if libelec you can use chrome? to go to another websites outside kodi? or maybe inside kodi by addons?
Pass, but if you post a short query in the General discussion forum here, I'm sure someone who does know about this stuff will be able to assist.

Best, sakaki
I've been trying to install WireGuard on the 64-bit Gentoo image. After typing

Code: Select all

# emerge linux-headers
I'm still getting the error

Code: Select all

make[1]: *** /lib/modules/4.19.67-v8-174fcab91765-p4-bis+/build: No such file or directory.  Stop.
when I try to build from a wireguard source tarball. Then I tried

Code: Select all

# emerge wireguard
and Gentoo started downloading source to build a Linux 5.2 kernel. As I type, I expect it is about to self-destruct. What do I need to do to get WireGuard to build?

User avatar
sakaki
Posts: 348
Joined: Sun Jul 16, 2017 1:11 pm

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

Sun Sep 08, 2019 2:38 pm

ejolson wrote:
Sun Sep 08, 2019 5:27 am
What do I need to do to get WireGuard to build?
So, building out-of-tree kernel modules like this against a binary kernel is a little tricky at the moment (I need to tweak the weekly autobuilder to create a matching kernel-headers-... package for each of the provided kernels, basically, which I haven't done yet ><). By default the Gentoo in-tree ebuild for WireGuard will, as you have seen, pull in a stock kernel source tree, which is not what you want.

However, it can be done the old-school way for now. Begin by finding your kernel's release name:

Code: Select all

demouser@pi64 ~ $ uname -r
4.19.67-v8-174fcab91765-p4-bis+
Embedded in there is the short-form of the tip commit of the Raspberry Pi Linux source tree when the kernel was built (174fcab91765, in this case). Now, we could clone the full tree and then checkout this commit, but that'd take a long time. Instead, we can use a handy GitHub shortcut to download just a snapshot of how the source tree looked at that commit, as a zip file:

Code: Select all

demouser@pi64 ~ $ wget -c https://github.com/raspberrypi/linux/archive/174fcab91765.zip
Should be circa 200MiB.
I think GitHub may allow shallow clones with reachability now, so that'd be another way to do it...

Unpack it into the /usr/src directory, the standard location for these things to live:

Code: Select all

demouser@pi64 ~ $ sudo unzip -q 174fcab91765.zip -d /usr/src/
demouser@pi64 ~ $ ls -d /usr/src/linux-*
/usr/src/linux-174fcab91765ef8fe3562c9858fb62f1a471c2d6
You can see the unpacked directory name is using the long-form version of the tip commit.

Next, ensure the /usr/src/linux symlink points to this kernel source tree:

Code: Select all

demouser@pi64 ~ $ sudo eselect kernel set linux-174fcab91765ef8fe3562c9858fb62f1a471c2d6

OK, so now we can prepare the kernel tree for out-of-tree module builds, under the configuration used to build it originally. Let's work as root for this part, to keep things simple, and enter the kernel tree:

Code: Select all

demouser@pi64 ~ $ sudo su -
pi64 ~ # cd /usr/src/linux
The configuration of your running kernel can be found if you modprobe the configs module. We do so and zcat the resulting /proc entry to .config, where the Linux build system expects to find it:

Code: Select all

pi64 /usr/src/linux # modprobe configs
pi64 /usr/src/linux # zcat /proc/config.gz > .config
One wrinkle: you'll note (from "uname -r" above) that your actual kernel release name has a "+" on the end, indicating that it came from a version control system, and was modified wrt the specified commit (a dirty flag, basically). It happens because my kernel autobuilder changes the default config somewhat. Well, we aren't using a VCS here, so we have to synthetically add the "+" into the release name so it will match:

Code: Select all

pi64 /usr/src/linux # sed -i -e 's#-bis#-bis+#g' .config
Now we can prepare the kernel source tree (the following doesn't actually build the full kernel, just its in-tree modules), and should be a relatively quick operation on a Pi4:

Code: Select all

pi64 /usr/src/linux # make modules_prepare
pi64 /usr/src/linux # make -j4 modules
pi64 /usr/src/linux # logout
There are some advantages to actually doing a "make modules" here (specifically, creation of Module.symvers etc., which will ensure that the wireguard module pulls in its deps, when you modprobe it later).

OK, now fetch the latest source tarball for WireGuard, unpack it, and enter its source directory:

Code: Select all

demouser@pi64 ~ $ wget -c https://git.zx2c4.com/WireGuard/snapshot/WireGuard-0.0.20190905.tar.xz
demouser@pi64 ~ $ tar -xJf WireGuard-0.0.20190905.tar.xz
demouser@pi64 ~ $ cd WireGuard-0.0.20190905/src
Build the module and tools (won't take long):

Code: Select all

demouser@pi64 ~/WireGuard-0.0.20190905/src $ KERNELDIR=/usr/src/linux make
demouser@pi64 ~/WireGuard-0.0.20190905/src $ sudo KERNELDIR=/usr/src/linux make install
Update the module list:

Code: Select all

demouser@pi64 ~/WireGuard-0.0.20190905/src $ sudo depmod -a
And now you should be able to cleanly insert your newly built WireGuard module into the currently running kernel. Issue:

Code: Select all

demouser@pi64 ~/WireGuard-0.0.20190905/src $ sudo modprobe wireguard
Done!

hth,

sakaki

ejolson
Posts: 3575
Joined: Tue Mar 18, 2014 11:47 am

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

Tue Sep 10, 2019 6:19 pm

sakaki wrote:
Sun Sep 08, 2019 2:38 pm
ejolson wrote:
Sun Sep 08, 2019 5:27 am
What do I need to do to get WireGuard to build?
So, building out-of-tree kernel modules like this against a binary kernel is a little tricky at the moment (I need to tweak the weekly autobuilder to create a matching kernel-headers-... package for each of the provided kernels, basically, which I haven't done yet ><). By default the Gentoo in-tree ebuild for WireGuard will, as you have seen, pull in a stock kernel source tree, which is not what you want.

However, it can be done the old-school way for now.
The instructions worked flawlessly!

Possibly due to me using a cheap SD card, the module build for the kernel took 42 minutes. WireGuard is now up and running here on 64-bit Gentoo. It seems about 10% faster than with Raspbian.

More details are posted in this thread.

User avatar
Gavinmc42
Posts: 3736
Joined: Wed Aug 28, 2013 3:31 am

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

Thu Sep 19, 2019 12:30 pm

Finally noticed the Dolphin stuff and googled it :o
Wow , you guys have been busy.
And what a bunch of wet blankets on the Dolphin forums.
Sakaki has it in the repo so it was a quick emerge ;)

Don't have any GameCube or Wii games.
But I have some DOS games on floppies somewhere :lol:
And DosBox is one of the 59 emulators.
Plenty more for you guys to try emerging.

Mind you, Warzone2100 is my time waster these days.

Broke three Buster OS's in the last two days, not quite stable yet, unlike Gentoo64 :lol:
Not sure if I want to waste more time on Buster, so much still to learn about Gentoo.
4GB Pi4s were in stock today and my local supplier has shipped it :D
Attachments
Dosbox.png
Dosbox.png (233.06 KiB) Viewed 1052 times
I'm dancing on Rainbows.
Raspberries are not Apples or Oranges


User avatar
bomblord
Posts: 135
Joined: Sun Jul 14, 2019 2:54 am

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

Mon Sep 23, 2019 3:40 pm

Hey Sakaki, is it possible for https://github.com/raspberrypi/linux/pu ... rpi-update 4.19.74-v8+ be merged to Gentoo? It supposedly brings everything into OPENGLES 3.1 compliance and gets EXT_BUFFER_STORAGE working if my understanding of the discussion here is correct.

User avatar
sakaki
Posts: 348
Joined: Sun Jul 16, 2017 1:11 pm

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

Tue Sep 24, 2019 4:30 pm

Hi bomblord,

since your desired PR (#3203) was merged into rpi-4.19.y upstream, the weekly kernel autobuilds (here and here) which ran earlier today, will have picked it up automatically. To use the updated binary kernel packages thus created, you just need to unmask them locally, and then merge, so:

Code: Select all

demouser@pi64 ~ $ sudo emaint sync --repo genpi64
demouser@pi64 ~ $ echo "~sys-kernel/bcm2711-kernel-bis-bin-4.19.73.20190924" | sudo tee -a /etc/portage/package.unmask/bcm2711-kernel-bis-bin
demouser@pi64 ~ $ echo "~sys-kernel/bcmrpi3-kernel-bis-bin-4.19.73.20190924" | sudo tee -a /etc/portage/package.unmask/bcmrpi3-kernel-bis-bin
demouser@pi64 ~ $ sudo emerge -v1u bcm2711-kernel-bis-bin bcmrpi3-kernel-bis-bin
NB even if you are only working on an RPi4, you should still update both the RPi4 and RPi3 kernels, as shown above.
Once merged, reboot to start using your new kernel!

Note that the rpi-4.19.y kernel source tree (with PR#3203 included) is at still (at the time of writing) at sublevel 73; so while this PR won't aiui get pushed via the rpi-update route until the sublevel hits 74 (at some point in the near future), the above (20190924) build of the kernel should be good to use now on Gentoo.

If this kernel works for you, please let me know and I'll unmask it globally.

Best, sakaki

User avatar
bomblord
Posts: 135
Joined: Sun Jul 14, 2019 2:54 am

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

Tue Sep 24, 2019 7:26 pm

sakaki wrote:
Tue Sep 24, 2019 4:30 pm
Hi bomblord,

since your desired PR (#3203) was merged into rpi-4.19.y upstream, the weekly kernel autobuilds (here and here) which ran earlier today, will have picked it up automatically. To use the updated binary kernel packages thus created, you just need to unmask them locally, and then merge, so:

Code: Select all

demouser@pi64 ~ $ sudo emaint sync --repo genpi64
demouser@pi64 ~ $ echo "~sys-kernel/bcm2711-kernel-bis-bin-4.19.73.20190924" | sudo tee -a /etc/portage/package.unmask/bcm2711-kernel-bis-bin
demouser@pi64 ~ $ echo "~sys-kernel/bcmrpi3-kernel-bis-bin-4.19.73.20190924" | sudo tee -a /etc/portage/package.unmask/bcmrpi3-kernel-bis-bin
demouser@pi64 ~ $ sudo emerge -v1u bcm2711-kernel-bis-bin bcmrpi3-kernel-bis-bin
NB even if you are only working on an RPi4, you should still update both the RPi4 and RPi3 kernels, as shown above.
Once merged, reboot to start using your new kernel!

Note that the rpi-4.19.y kernel source tree (with PR#3203 included) is at still (at the time of writing) at sublevel 73; so while this PR won't aiui get pushed via the rpi-update route until the sublevel hits 74 (at some point in the near future), the above (20190924) build of the kernel should be good to use now on Gentoo.

If this kernel works for you, please let me know and I'll unmask it globally.

Best, sakaki
Thank you for the instructions I'll try it out when I get some free time.

jdonald
Posts: 413
Joined: Fri Nov 03, 2017 4:36 pm

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

Wed Sep 25, 2019 2:54 am

bomblord wrote:
Mon Sep 23, 2019 3:40 pm
It supposedly brings everything into OPENGLES 3.1 compliance and gets EXT_BUFFER_STORAGE working
The kernel update won't do that alone. You need Mesa built off that specific branch as well.

BRX7
Posts: 15
Joined: Sat Aug 31, 2019 11:07 pm

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

Wed Sep 25, 2019 8:57 am

I am trying to get openvpn running, originally was gonna use docker and run openvpn inside, but its too much of an issue with permissions messing up.

back to openvpn installation,
I have installed the new kernel and its fine, but it has no sources installed in usr/src and if i want to enable TUN
cat /usr/src/linux/.config | grep CONFIG_TUN doesnt find it.

what is a steps I need to take sepcific to gentoopi64 for openvpn and TUN option/flag.

thanks

PiUser10
Posts: 12
Joined: Mon Dec 30, 2013 9:20 am

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

Wed Sep 25, 2019 9:44 am

Love the gentoo 64-bit image, thanks for all the hard work.

Just one question if I may .... Is there a way to add a CPU temperature monitor to the top panel as per Raspbian ?
There does not appear to be one listed in the add to panel apps option.
I am used to using apt and have no real knowledge of emerge etc.

Keith

User avatar
Gavinmc42
Posts: 3736
Joined: Wed Aug 28, 2013 3:31 am

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

Wed Sep 25, 2019 11:00 am

Sakaki got me to run this in a terminal "watch vcgencmd measure_temp"
I shrink it down and put it in a corner.

But a temp display on the panel would be nice.
I got as far as googling it
https://wiki.gentoo.org/wiki/Xfce/Guide#Panel_plugins
I thought it would be interesting to learn how to do it myself, but I keep getting distracted by all the stuff that works now.
Something like this would be great to learn so we can add i2c or SPI or Uart sensor data like humidity etc.
https://goodies.xfce.org/projects/panel ... ors-plugin
I'm dancing on Rainbows.
Raspberries are not Apples or Oranges

geev03
Posts: 122
Joined: Thu Jun 07, 2012 12:40 pm
Location: London, UK

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

Fri Sep 27, 2019 10:35 am

sakaki wrote:
Tue Sep 24, 2019 4:30 pm
.......
......
If this kernel works for you, please let me know and I'll unmask it globally.

Best, sakaki
After the reboot, the programs are all working as before. Looking forward to using the gentoo ' rpi-4.19.74 kernel' soon and reading new articles in place of the gloomy ones likehttps://www.infoworld.com/article/31098 ... urity.html
Attachments
gentoo_kernel_4_19_73.jpg
gentoo_kernel_4_19_73.jpg (138.51 KiB) Viewed 598 times

BRX7
Posts: 15
Joined: Sat Aug 31, 2019 11:07 pm

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

Fri Sep 27, 2019 10:42 am

sakaki wrote:
Sun Sep 08, 2019 2:38 pm
ejolson wrote:
Sun Sep 08, 2019 5:27 am
What do I need to do to get WireGuard to build?
So, building out-of-tree kernel modules like this against a binary kernel is a little tricky at the moment (I need to tweak the weekly autobuilder to create a matching kernel-headers-... package for each of the provided kernels, basically, which I haven't done yet ><). By default the Gentoo in-tree ebuild for WireGuard will, as you have seen, pull in a stock kernel source tree, which is not what you want.

However, it can be done the old-school way for now. Begin by finding your kernel's release name:

Code: Select all

demouser@pi64 ~ $ uname -r
4.19.67-v8-174fcab91765-p4-bis+
Embedded in there is the short-form of the tip commit of the Raspberry Pi Linux source tree when the kernel was built (174fcab91765, in this case). Now, we could clone the full tree and then checkout this commit, but that'd take a long time. Instead, we can use a handy GitHub shortcut to download just a snapshot of how the source tree looked at that commit, as a zip file:

Code: Select all

demouser@pi64 ~ $ wget -c https://github.com/raspberrypi/linux/archive/174fcab91765.zip
Should be circa 200MiB.
I think GitHub may allow shallow clones with reachability now, so that'd be another way to do it...

Unpack it into the /usr/src directory, the standard location for these things to live:

Code: Select all

demouser@pi64 ~ $ sudo unzip -q 174fcab91765.zip -d /usr/src/
demouser@pi64 ~ $ ls -d /usr/src/linux-*
/usr/src/linux-174fcab91765ef8fe3562c9858fb62f1a471c2d6
You can see the unpacked directory name is using the long-form version of the tip commit.

Next, ensure the /usr/src/linux symlink points to this kernel source tree:

Code: Select all

demouser@pi64 ~ $ sudo eselect kernel set linux-174fcab91765ef8fe3562c9858fb62f1a471c2d6

OK, so now we can prepare the kernel tree for out-of-tree module builds, under the configuration used to build it originally. Let's work as root for this part, to keep things simple, and enter the kernel tree:

Code: Select all

demouser@pi64 ~ $ sudo su -
pi64 ~ # cd /usr/src/linux
The configuration of your running kernel can be found if you modprobe the configs module. We do so and zcat the resulting /proc entry to .config, where the Linux build system expects to find it:

Code: Select all

pi64 /usr/src/linux # modprobe configs
pi64 /usr/src/linux # zcat /proc/config.gz > .config
One wrinkle: you'll note (from "uname -r" above) that your actual kernel release name has a "+" on the end, indicating that it came from a version control system, and was modified wrt the specified commit (a dirty flag, basically). It happens because my kernel autobuilder changes the default config somewhat. Well, we aren't using a VCS here, so we have to synthetically add the "+" into the release name so it will match:

Code: Select all

pi64 /usr/src/linux # sed -i -e 's#-bis#-bis+#g' .config
Now we can prepare the kernel source tree (the following doesn't actually build the full kernel, just its in-tree modules), and should be a relatively quick operation on a Pi4:

Code: Select all

pi64 /usr/src/linux # make modules_prepare
pi64 /usr/src/linux # make -j4 modules
pi64 /usr/src/linux # logout
There are some advantages to actually doing a "make modules" here (specifically, creation of Module.symvers etc., which will ensure that the wireguard module pulls in its deps, when you modprobe it later).

OK, now fetch the latest source tarball for WireGuard, unpack it, and enter its source directory:

Code: Select all

demouser@pi64 ~ $ wget -c https://git.zx2c4.com/WireGuard/snapshot/WireGuard-0.0.20190905.tar.xz
demouser@pi64 ~ $ tar -xJf WireGuard-0.0.20190905.tar.xz
demouser@pi64 ~ $ cd WireGuard-0.0.20190905/src
Build the module and tools (won't take long):

Code: Select all

demouser@pi64 ~/WireGuard-0.0.20190905/src $ KERNELDIR=/usr/src/linux make
demouser@pi64 ~/WireGuard-0.0.20190905/src $ sudo KERNELDIR=/usr/src/linux make install
Update the module list:

Code: Select all

demouser@pi64 ~/WireGuard-0.0.20190905/src $ sudo depmod -a
And now you should be able to cleanly insert your newly built WireGuard module into the currently running kernel. Issue:

Code: Select all

demouser@pi64 ~/WireGuard-0.0.20190905/src $ sudo modprobe wireguard
Done!

hth,

sakaki
Ive followed this to setup wireguard for vpn use, however I am following this guide and it wants to me to install unbound,
https://grh.am/2018/wireguard-setup-guide-for-ios/

i have run emerge -v net-dns/unbound but i get this message

Local copy of remote index is up-to-date and will be used.
* Last emerge --sync was 34d 10h 2m 52s ago.

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild R ] dev-libs/openssl-1.0.2s-r1::gentoo USE="asm sslv3 tls-heartbeat zlib -bindist* -gmp -kerberos -rfc3779 -sctp -sslv2 -static-libs -test -vanilla" 5,236 KiB
[ebuild N ] net-dns/dnssec-root-20181220::gentoo 18 KiB
[ebuild N ] net-dns/unbound-1.9.2:0/8::gentoo USE="ecdsa -debug -dnscrypt -dnstap -ecs -gost -libressl -python -redis (-selinux) -static-libs -systemd -test -threads" PYTHON_SINGLE_TARGET="python3_6 -python2_7 -python3_5 -python3_7" PYTHON_TARGETS="python2_7 python3_5 python3_6 python3_7" 5,544 KiB

Total: 3 packages (2 new, 1 reinstall), Size of downloads: 10,797 KiB

The following USE changes are necessary to proceed:
(see "package.use" in the portage(5) man page for more details)
# required by net-dns/unbound-1.9.2::gentoo[-libressl,ecdsa]
# required by net-dns/unbound (argument)
>=dev-libs/openssl-1.0.2s-r1 -bindist

Use --autounmask-write to write changes to config files (honoring
CONFIG_PROTECT). Carefully examine the list of proposed changes,
paying special attention to mask or keyword changes that may expose
experimental or unstable packages

What should i do to correctly install unbound

BRX7
Posts: 15
Joined: Sat Aug 31, 2019 11:07 pm

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

Fri Sep 27, 2019 1:45 pm

OK,
I have dumped that instructions,
and followed this one, and its all working

https://www.reddit.com/r/pihole/comment ... pberry_pi/

lowfat
Posts: 11
Joined: Tue Sep 24, 2019 7:22 pm

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

Sat Sep 28, 2019 6:35 pm

sakaki wrote:
Sun Sep 01, 2019 4:13 pm
I've just posted a v1.5.1 bugfix release of my bootable 64-bit Gentoo image for the RPi4 B / RPi3 B & B+ on GitHub (here, includes full download instructions).
Hi Sakaki, is this a fully 64-bit Gentoo? I seem to recall a while ago there was a mixed 64- and 32-bit OS, where the 32-bit parts were required due to driver issues.

User avatar
sakaki
Posts: 348
Joined: Sun Jul 16, 2017 1:11 pm

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

Sun Sep 29, 2019 11:40 am

lowfat wrote:
Sat Sep 28, 2019 6:35 pm
Hi Sakaki, is this a fully 64-bit Gentoo? I seem to recall a while ago there was a mixed 64- and 32-bit OS, where the 32-bit parts were required due to driver issues.
Yes, it is fully (kernel+userland) 64-bit.
Best, sakaki

User avatar
sakaki
Posts: 348
Joined: Sun Jul 16, 2017 1:11 pm

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

Sun Sep 29, 2019 12:04 pm

PiUser10 wrote:
Wed Sep 25, 2019 9:44 am
Love the gentoo 64-bit image, thanks for all the hard work.

Just one question if I may .... Is there a way to add a CPU temperature monitor to the top panel as per Raspbian ?
There does not appear to be one listed in the add to panel apps option.
I am used to using apt and have no real knowledge of emerge etc.

Keith
The simplest thing is just to install the generic command plugin, and then use this to display the output of "vcgencmd measure_temp".
To do so, issue:

Code: Select all

demouser@pi64 ~ $ sudo emaint sync --repo genpi64
demouser@pi64 ~ $ sudo emerge -v xfce4-genmon-plugin
Once that builds (shouldn't take long), right-click in the top panel, and choose Panel -> Add New Items... from the drop-down menu. Click on "Generic Monitor" and press Add, then Close. It will show a rather ugly display "(genmon)XXX" initially. Right-click on the new item, and select Move, and move it where you want it. Then right-click on it again, and choose Properties.

A dialog box will open. Untick the Label box (this will remove the "(genmon)" string. Change the period to something relatively short, like 5.00 seconds. And, in the Command box, enter:

Code: Select all

vcgencmd measure_temp
And Close. You should now have a simple temperature monitor displaying! For a more condensed display, use something like the following Command instead:

Code: Select all

bash -c "vcgencmd measure_temp | cut -d= -f2 | tr -d \'"
You can make the output prettier by invoking a custom script, and using markup in the returned string; see e.g. these notes. You can also specify an icon, action to take on click, tooltip etc.

hth, sakaki

User avatar
sakaki
Posts: 348
Joined: Sun Jul 16, 2017 1:11 pm

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

Sun Sep 29, 2019 12:21 pm

BRX7 wrote:
Fri Sep 27, 2019 10:42 am
What should i do to correctly install unbound
Sounds like you've already got this working in Raspbian, but for the record, the issue is that the current net-dns/unbound ebuilds in the main Gentoo tree have the ecdsa USE flag on by default, which in turn requires dev-libs/openssl to be built without the bindist USE flag (since patent-encumbered code is included). This can be done (although it causes quite a lot of knock-on rebuilds) but actually, I'm not sure should be required here at all, since the current openssl in-tree builds contain the 'hobbled' elliptic-curve crypto patchset from Fedora 31 anyhow (allowing EC even with bindist set).

If I get a moment I'll investigate this a bit more and maybe file a bug report against it upstream.

Glad you found a solution to this through another route anyhow.

Best, sakaki

User avatar
sakaki
Posts: 348
Joined: Sun Jul 16, 2017 1:11 pm

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

Sun Sep 29, 2019 12:30 pm

geev03 wrote:
Fri Sep 27, 2019 10:35 am
After the reboot, the programs are all working as before.
Thanks! I've unmasked it globally now.
Best, sakaki

User avatar
sakaki
Posts: 348
Joined: Sun Jul 16, 2017 1:11 pm

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

Sun Sep 29, 2019 12:33 pm

jdonald wrote:
Wed Sep 25, 2019 2:54 am
bomblord wrote:
Mon Sep 23, 2019 3:40 pm
It supposedly brings everything into OPENGLES 3.1 compliance and gets EXT_BUFFER_STORAGE working
The kernel update won't do that alone. You need Mesa built off that specific branch as well.
OK apologies, haven't been following this particular thread that closely; is there a squashed patchset for these mesa changes around? If so I could apply it also under an appropriate USE flag.

Best, sakaki

Return to “Gentoo”