Bootable 64-bit RPi3/Pi4 Gentoo image (OpenRC/Xfce/VC4) Pt 2

Message

Post by **NeddySeagoon** » Mon Dec 07, 2020 12:22 pm

Jarodiv,

media-libs/raspberrypi-userland is upstreamed.

# eix media-libs/raspberrypi-userland
[I] media-libs/raspberrypi-userland
     Available versions:  *0_pre20160424 (~)0_pre20201022 (~)1.20200520*l{tbz2}[1] (~)1.20201102*l{tbz2}[1] **9999*l **9999*l[1] {examples wayland}
     Installed versions:  1.20201102*l{tbz2}[1](12:39:56 11/29/20)
     Homepage:            https://github.com/raspberrypi/userland
     Description:         Raspberry Pi userspace tools and libraries

as is media-sound/pulseaudio

Code: Select all

# eix media-sound/pulseaudio
[I] media-sound/pulseaudio
     Available versions:  (~)12.2-r3[1] 13.0^t{tbz2} (~)13.0-r1^t 13.0-r2^t{tbz2}[1] {+X +alsa +alsa-plugin +asyncns bluetooth +caps dbus doc elogind equalizer gconf +gdbm +glib gtk ipv6 jack libressl libsamplerate lirc native-headset neon ofono-headset +orc oss pi4-workaround qt5 realtime rpi-deglitch selinux sox ssl system-wide systemd tcpd test +udev +webrtc-aec zeroconf ABI_MIPS="n32 n64 o32" ABI_S390="32 64" ABI_X86="32 64 x32" CPU_FLAGS_ARM="neon" KERNEL="linux"}
     Installed versions:  13.0-r2^t{tbz2}[1](20:37:55 12/01/20)(X alsa alsa-plugin asyncns bluetooth caps dbus doc elogind gdbm glib gtk ipv6 qt5 ssl tcpd udev -equalizer -gconf -jack -libressl -libsamplerate -lirc -native-headset -ofono-headset -orc -oss -pi4-workaround -realtime -rpi-deglitch -selinux -sox -system-wide -systemd -test -webrtc-aec -zeroconf ABI_MIPS="-n32 -n64 -o32" ABI_S390="-32 -64" ABI_X86="-32 -64 -x32" CPU_FLAGS_ARM="-neon" KERNEL="linux")
     Homepage:            https://www.freedesktop.org/wiki/Software/PulseAudio/
     Description:         A networked sound server with an advanced plugin system

It is indeed possible to use only the ~arm64 ::gentoo repo on a 64 bit Pi now but in one or two areas, particularly multimedia, it remains sub optimal.

Jarodiv · Post by **Jarodiv** » Tue Dec 08, 2020 11:25 pm

Those pesky date based version numbers. I've read the 20201022 as 20200122 and thus thought it quite old and older than what is available in the genpi64 overlay. Guess I'll replace this package too. Pulseaudio still is an older version than in the overlay, so not sure if the upstream version contains all fixes. Guess I will keep it for now. But still, down to one package from the overlay, thanks!

Strange · Post by **Strange** » Wed Dec 16, 2020 1:17 pm

Finally I successfully installed Gentoo on my pi4b, basically follow the "Raspberry Pi4 64 Bit Install" document and use sakaki's image as bootstrap for build new kernel. cheers.

flysideways · Post by **flysideways** » Wed Dec 16, 2020 5:23 pm

I have done multiple installs following different paths.

Currently I am working on one using limited resources as would be expected for someone with a Pi but new to Gentoo. (right now it is updating from the lagging snapshot, 66 packages)

An overview:

Using the Raspberry Pi Imager to do the firmware update, per their instructions, for the USB mass storage boot.
Using the Raspberry Pi Imager to burn genpi64.img.xz
Following steps in the amd64 handbook, modified for the arm64, using steps from Neddy's RPI64 wiki entries and the Chroot wiki entry to build entirely from the Pi.
I have been through it once using git pulls for the needed parts and am doing it again trying out the Gentoo repository in place of git.

I have a bunch of notes and will post them up after I get them in a clear and concise form.

This is exciting. Someone with any desktop or laptop can use the Pi tools and genpi64 to get a first start into Gentoo on a Pi 4. It is a whole lot more than my Athlon 1200 was, and doesn't idle at 130 watts.

flysideways · Post by **flysideways** » Thu Dec 17, 2020 2:00 am

post moved to Native RPi4B 64bit Gentoo Install Instructions

spork_kitty · Post by **spork_kitty** » Sun Dec 20, 2020 5:51 pm

For the experienced, what all is really necessary to migrate from genpi to Gentoo if you're on a standard SD card install? Seems like you need to move some packages from ::genpi to ::gentoo, re-emerge, get your own kernel toolchain together, build, and go... does that about cover it?

lperkins2 · Post by **lperkins2** » Wed Dec 23, 2020 11:08 pm

spork_kitty wrote:For the experienced, what all is really necessary to migrate from genpi to Gentoo if you're on a standard SD card install? Seems like you need to move some packages from ::genpi to ::gentoo, re-emerge, get your own kernel toolchain together, build, and go... does that about cover it?

Pretty much. Also a good idea to get distcc up and running if you have a computer that can assist.

If you want to reduce the pain marginally, you can also use https://packages.genpi64.com as a binpkg provider. It's not really ready for prime-time yet, but the packages which are there *should* work (as usual with this sort of thing, if it breaks, you get to keep the pieces).

flysideways · Post by **flysideways** » Mon Dec 28, 2020 7:49 pm

https://wiki.gentoo.org/wiki/FAQ wrote:By default in Gentoo the entire system is built from source code, ...

samip537 · Post by **samip537** » Tue Dec 29, 2020 4:27 am

Hi,

I don't know if people are aware here, but we are working on with some people on getting a Gentoo for Raspberry Pi going again, with help from Sakaki's work.
Help and ideas would be much appreciated, like what default packages to include, default kernel and things like that. Please see the Github issues for those.

Our Github repository: https://github.com/GenPi64/gentoo-on-rpi-64bit
Our binhost: https://packages.genpi64.com

flysideways · Post by **flysideways** » Tue Dec 29, 2020 8:03 am

Sakaki might appreciate her email being removed from the forked project, unless you have her approval.

It is in the Feedback Welcome! section at the bottom of the page.

Strange · Post by **Strange** » Tue Dec 29, 2020 10:00 am

I think it may help that to have an equivalent .img of Gentoo minimal install iso.

samip537 · Post by **samip537** » Tue Dec 29, 2020 10:34 pm

flysideways wrote:Sakaki might appreciate her email being removed from the forked project, unless you have her approval.

It is in the Feedback Welcome! section at the bottom of the page.

That was totally forgotten to remove, but now it has been removed.

Strange wrote:I think it may help that to have an equivalent .img of Gentoo minimal install iso.

There is stage3 already, so it would only need kernel and should be bootable.

lperkins2 · Post by **lperkins2** » Wed Dec 30, 2020 9:15 am

flysideways wrote:Sakaki might appreciate her email being removed from the forked project, unless you have her approval.

It is in the Feedback Welcome! section at the bottom of the page.

Thank you for pointing that out. I've combed over most of the code once already, examining the output of

Code: Select all

grep -R -i sakaki

, but it can't all by blindly removed as her copyright notices and authorship information needs to stay. I am unsurprised something got missed. If you spot anything else, please point it out.

flysideways · Post by **flysideways** » Wed Dec 30, 2020 1:31 pm

I was just pointing out the email being in a section soliciting feedback, of course the copyright attribution must remain.

ShorTie · Post by **ShorTie** » Sun Feb 28, 2021 10:30 am

Ok, I know like nuffin about Desktop's, lol.
I'm creating a piGentoo image maker.

Everyone raves' about this.
Everyone want to update it.
Basically Every One Wants it, it seems.

But what is I ask ????

So......
I found this
https://github.com/sakaki-/gentoo-on-rp ... l-packages
Sortta looked like this thing to me.

So now I'm really cornfused, lol.
Way to much gibberish for me.
Me like a KISS method.

So I took a Day and turned it into a 1 liner emerge.
https://dpaste.org/0u9C
Now I worked thru my 1 liner, took another day or so.
And came up with that, still needs some tweeking.

I see 156 packages she had to maintian on her own because of keyworking issues alone.
I do not work in the ~ world.
I filed a bug, https://bugs.gentoo.org/773319, but jstein killed it.

So, So, Sorry, Guess my work is done here untill some keywording issue's are fixed for me.

Post by **NeddySeagoon** » Sun Feb 28, 2021 11:46 am

ShorTie,

You misunderstand the entire process of stabilisation and you started from a baseline that was known to be about six months out of date.
Everything I know about that has not been added to ::gentoo already is still in my genpi64 fork. It needs some TLC as its not been touched for some time.

The stuff that has been added to ::gentoo can be stabilised following normal Gentoo processes.
If someone (maybe you?) wants to do the work it can happen faster.

-- edit --

A quick scan down your packages list shows you included hard masked stuff that is about to removed from ::gentoo for assorted reasons.
Mostly dead upstream and no support for python3.

-- edit --

Genpi64 is alive and well on github.
Its open source. Feel free to join in the fun.

ShorTie · Post by **ShorTie** » Sun Feb 28, 2021 12:35 pm

Guess you Do Not get the ~ thing !!
Is about all I can say.
Stuff that should not be marked ~ imho.
Like maybe dev-python/parsedatetime-2.6::gentoo (masked by: ~arm64 keyword)
But, Hey!
What do I know, lol.
Get overlay out of your head Pleaze.
Thank You, Jeff.

Post by **NeddySeagoon** » Sun Feb 28, 2021 1:20 pm

ShorTie,

So do the work to stable dev-python/parsedatetime-2.6. Submit a bug or a PR with your testing evidence.
Its already stable on amd64, so that should be a nice easy one to start with ... maybe.

The workflow is documented on the Wiki.

ShorTie · Post by **ShorTie** » Mon Mar 01, 2021 11:44 am

NeddySeagoon the biggest problem is arm64 has been neglected for too many years.

I said she had to maintain 156 packages and sam_ like went off on me.

ShorTie: She didn't actually maintain any of those packages though
she just had a big list of package.accept_keywords

Well having to write some thing to package.accept_keywords is maintenance to me.
It still took like human help.

Peeps are just use to sticking every thing in package.accept_keywords, it's a way of like.
Or , like you I do believe, they just run ~ from the git go, to bypass all the keyword crap.
Much easier then doing the whole bug route, imho.

I'd say, everything in her package.accept_keywords has been tested out the ying-yang.
And should be just stabilize Period.
Not like she just wrote this yesterday, lol.

And truely, Why should I do

So do the work to stable dev-python/parsedatetime-2.6. Submit a bug or a PR with your testing evidence.
Its already stable on amd64, so that should be a nice easy one to start with ... maybe.

No ones gonna believe me .. :/~
Has it not been "tested" enough already ??
Probably been tested in more ways and forms then your gonna, imho.
Bigga waste of my time

If it Twas Me sam, for a quick catch up, I'd search all the packages.
If it is stabile on arm, make it stabile on arm64.
Then let bug wrangler sort things out.

But that is Me and the easy way.
So it will never happen.
Let the old folks roll and dedicate your testing time to the new and improved versions only.

Post by **NeddySeagoon** » Mon Mar 01, 2021 1:19 pm

ShorTie,

You are confusing the two separate steps.

To go from no keyword at all to a testing keyword is one step.
There is no route from no keyword at all directly to stable.

Its two separate steps with 30 days bug free between.

Sakakis list of keywords are no repoman clean. They worked for building a binary distro with a fixed set of USE flags. That was Sakakis objective.
It worked for that.

When you add the keyword to many packages repoman identifies other packages, hidden behind USE flags, that also need te be keyworded.
That leave two choices ...
1. Trace the packages to be keyworded recursively and keyword them all.
2. Mask the USE flags that pull in other things.

1. is the right way to do it.
2. is a temporary measure, while a dependency won't build or fails tests. File a bug and cite it in the mask comment.

In short, Sakakis work was good enough for the her binary distro and it was a useful place to start keywording from. Its incomplete for keywording for the ::gentoo repo.
The easy stuff has been done.

As sam said in #gentoo-arm. See https://bugs.gentoo.org/773172 as a worked example of a stable or keyword request.
Its one request per bug, along with all the dependencies.
Its good to go when the bot says

NATTkA bot gentoo-dev 2021-02-28 21:44:56 UTC

All sanity-check issues have been resolved

Do it right or don't do it at all.

lperkins2 · Post by **lperkins2** » Fri Mar 19, 2021 5:39 pm

Aside from the procedural problem, there is another problem with asserting testing within genpi64 is sufficient to conclude all the genpi64 packages are stable. arm/aarch64 ::gentoo is for all arm/aarch64 systems: pinebooks, chromebooks, raspberry pis, gentoo prefixes inside termux, and so on. The genpi64 project only supports and tests packages on the Raspberry Pi 3 and 4. There are essentially 2 variations of the hardware, which is why a gentoo-binary-distro is actually viable with them. That doesn't mean the packages will work with other aarch64 systems, which means they very much still need testing (or at least, we can't just categorically say they've been tested).

CrazyTerabyte · Post by **CrazyTerabyte** » Wed Jun 30, 2021 8:53 pm

Hello, is the forked GenPi64 usable? Are there instructions on how to migrate an installation from sakaki to the forked GenPi64?

Out of my head, I imagine I need to change PORTAGE_BINHOST, /etc/portage/repos.conf/{genpi64,sakaki-tools}.conf, and possibly update the make.profile link. But what should I update each of those to? Is there anything else needed?

I've been neglecting the Gentoo installation on my RPi4 for several months, now I wish to make sure it will be in a healthy state.

5UrNkC27BJ · Post by **5UrNkC27BJ** » Mon Dec 12, 2022 7:06 pm

NeddySeagoon wrote:lperkins2,

I for one, will not use discord. Their terms of service are offensive to me.
Also, I'm a superannuated canine and I don't want to lean any novel manoeuvrers.

I encourage you and other genpi64 followers to join #gentoo-arm on freenode and join in with the existing gentoo arm and arm64 teams.

still on freenode?

Post by **NeddySeagoon** » Mon Dec 12, 2022 8:08 pm

5UrNkC27BJ,

When freenode imploded gentoo moved to Libera.

Or are you just teasing me for the being

a superannuated canine and I don't want to lean any novel manoeuvrers.

:)