jamesh
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 20295
Joined: Sat Jul 30, 2011 7:41 pm

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

Wed Jul 11, 2018 11:03 am

Gavinmc42 wrote:
Wed Jul 11, 2018 2:42 am
The old Pi2 uses the BCM2836 SoC, the newer Pi2 uses the BCM2837.
Old 32bit only, new 32/64bit.
So this should work on the new Pi2, but I don't have any.

Gentoo32?
I have only found DIY build instructions, no ready to go image?
Not all Pi2 manufacture uses the bcm2837, some are still made with the bcm2836.
Principal Software Engineer at Raspberry Pi (Trading) Ltd.
Please direct all questions to the forum, I do not do support via PM.

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

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

Wed Jul 11, 2018 12:57 pm

Not all Pi2 manufacture uses the bcm2837, some are still made with the bcm2836.
Hmm that could be confusing if I needed a lower power WiFi-less 64bit Pi ;)
BCM2836 rev 1.1 , BCM2837 rev 1.2?
I'm dancing on Rainbows.
Raspberries are not Apples or Oranges

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

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

Wed Jul 11, 2018 1:24 pm

Hey, which is the lower power Pi2?
32ibt 2836 or 64bit 2837?

I suppose just for Ethernet gadgets the Pi2 rev 1.2 would be better than Pi3B or 3B+.
Is there a Pi2 rev1.3 with the metal top 2837 clocking at 1.4GHz?
Probably not, need a PCB redesign to get the heat out, 1.3GHz?
But old lan chip, so not as network fast as a 3B+ :(

Hmm Pi2B+ in the works?
Rhetorical question - no answer expected :D
I'm dancing on Rainbows.
Raspberries are not Apples or Oranges

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

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

Thu Jul 12, 2018 2:06 pm

Gavinmc42 wrote:
Wed Jul 11, 2018 12:57 pm
Not all Pi2 manufacture uses the bcm2837, some are still made with the bcm2836.
Hmm that could be confusing if I needed a lower power WiFi-less 64bit Pi ;)
BCM2836 rev 1.1 , BCM2837 rev 1.2?
Yes, afaik the rev 1.2 RPi2 has a 64-bit-capable SoC, whereas the earlier revs do not.

I have been informed by a user that the gentoo-on-rpi3-64bit image will boot on a rev 1.2 Pi2 board, provided that an appropriate dtb is present in /boot, by e.g. mounting the first partition of the image on a pc, at /mnt/piboot say, then doing.:

Code: Select all

# cp /mnt/piboot/bcm2710-rpi-3-b.dtb /mnt/piboot/bcm2709-rpi-2-b.dtb
Unfortunately I don't have a Pi2 to test this out.
cjan wrote:
Wed Jul 11, 2018 12:10 am
do we have 32bit for Rip2 ?
A bootable 32-bit Gentoo image with integrated desktop etc. would definitely be possible but it's not on my todo list. There are of course the usual stage 3s etc available if you want to roll your own.

hth, sakaki

Solid924
Posts: 1
Joined: Mon Jul 23, 2018 7:02 pm

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

Mon Jul 23, 2018 7:04 pm

Hello,

I tried to install Team viewer on Gentoo but it doesn't work. What's the correct command to install it? Sudo emerge teamviewer does NOT work.

Thanks!!

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

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

Sun Jul 29, 2018 12:58 pm

Solid924,

Apologies for the delay in replying, I am currently travelling with only very intermittent internet access, and will respond on my return (last week of August).

In the meantime, please post a topic on the ARM subforum of the Gentoo board for support.

Best,

Sakaki

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

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

Tue Aug 28, 2018 1:06 pm

Solid924,

I saw you posted an issue about this in the Gentoo forums. Did it get resolved to your satisfaction? Note that if can run 32-bit Raspbian apps from within 64-bit Gentoo if you need to: see for example my notes here.

Best,

sakaki

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

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

Tue Aug 28, 2018 1:14 pm

All -

an apology - there is a bug (introduced by me) in porthash-1.0.6, that in turn is causing genup to fail. I've put a fix into porthash-1.0.7, and posted a news article via the rpi3-overlay, and a GitHub issue with the resolution, also copied below. ><

Diagnostics

Look near the end of your /var/log/latest-genup-run.log file to see if the issue affects you; if it does, you'll see something similar to the below:

Code: Select all

=== Sync completed for gentoo
q: Updating ebuild cache for /usr/portage ...
q: Finished xxx entries in yyy seconds
Checking master signature on gentoo repo...
porthash: Using public key 09F2FF455D90CAF4
porthash: Entering /usr/portage...
porthash: Verifying existing hashfile...
porthash: Hashfile signature and format valid
porthash: Computing master hash of /usr/portage, may take some time...
porthash: error: Hashfile and computed hashes DIFFER
Killing parent process... 

Fixing the Issue

To address the issue, open a terminal and issue the following commands, as the root user, on your rpi3:
(if running as demouser, prefix the following commands with sudo):

Code: Select all

pi64 ~ # emaint sync --repo sakaki-tools
pi64 ~ # emerge --update --oneshot --verbose app-portage/porthash
This should upgrade porthash to >= 1.0.7. Once this is done, your automatic weekly genup run should start working again.

That's it!

Background to the Issue (Optional Reading)

The porthash utility creates, or by default checks, the validity of a repository master hash (repo.hash) and counterpart digital signature (repo.hash.asc), to allow verification of a Portage tree distributed over an unauthenticated channel such as rsync. There was no such 'official' facility in Gentoo when the tool was originally deployed.

However, when Gentoo started rolling out its official app-portage/gemato manifest verification tool, porthash was modified (at v1.0.6) to migrate the location of the repo.hash{,.asc} files, from the top level /usr/portage/ directory (where they would clash with gemato) to /usr/portage/local/, which gemato ignores.

Unfortunately, during an rsync process of the Portage tree with the isshoni.org binhost, this local directory is not synced by default, but since (due to faulty logic; my bad) porthash-1.0.6 checks this location first when looking for the repo.hash{,.asc} files, the next time the tree is synced after the files have been migrated, the old (stale) /usr/portage/local/repo.hash{,.asc} files will be checked (not the fresh /usr/portage/repo.hash{,.asc} versions), and accordingly the signature verification will fail, and genup will halt with an error. (example)

This error is addressed in >=porthash-1.0.7, so upgrading this single package is sufficient to fix the problem.

Thanks to orion777 and ericbish for reporting this issue, and apologies again to all users for any inconvenience caused

Return to “Gentoo”

Who is online

Users browsing this forum: No registered users and 1 guest