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

[sakaki]

How does one go about logging in as root or changing the demouser password? The passwd command asks for the current password which I don't have and a google search doesn't seem to pull up.

Check out the project's README - but in brief the root password is raspberrypi64

hth, sakaki

PS apt-get isn't going to work here (just like it won't in e.g. Arch Linux): gentoo has a different package manager, called Portage, and the cognate command to apt-get is emerge. For more details, see here.

[Gavinmc42]

Back on Buster at the moment, need to cleanup the desk to make room for the TV .

Code: Select all

 tvservice -v 2 -m DMT
Group DMT has 9 modes:
           mode 4: 640x480 @ 60Hz 4:3, clock:25MHz progressive 
           mode 6: 640x480 @ 75Hz 4:3, clock:31MHz progressive 
           mode 9: 800x600 @ 60Hz 4:3, clock:40MHz progressive 
           mode 11: 800x600 @ 75Hz 4:3, clock:49MHz progressive 
           mode 16: 1024x768 @ 60Hz 4:3, clock:65MHz progressive 
           mode 18: 1024x768 @ 75Hz 4:3, clock:78MHz progressive 
           mode 21: 1152x864 @ 75Hz 4:3, clock:108MHz progressive 
  (prefer) mode 35: 1280x1024 @ 60Hz 5:4, clock:108MHz progressive 
           mode 36: 1280x1024 @ 75Hz 5:4, clock:135MHz progressive 

Time to learn about monitors, again, last time was DOS era .
It just goes to show how well the Pi's have been supported that this has never been a problem for 7 years till now.
I should have been paying more attention to the messages the monitor displayed.

It has got me thinking about how well a 21:9 curved super-wide monitor would go on a Pi4.
And if Flightgear will compile on Gentoo64

[sakaki]

Gavinmc42,

based on that, group 2 (DMT) mode 35 (1280x1024 @ 60Hz) ought to work.
Please try setting it for HDMI1 as I suggested above; pretty sure you will get a usable display then.

Best,

sakaki

[bomblord]

Back on Buster at the moment, need to cleanup the desk to make room for the TV .

Code: Select all

 tvservice -v 2 -m DMT
Group DMT has 9 modes:
           mode 4: 640x480 @ 60Hz 4:3, clock:25MHz progressive 
           mode 6: 640x480 @ 75Hz 4:3, clock:31MHz progressive 
           mode 9: 800x600 @ 60Hz 4:3, clock:40MHz progressive 
           mode 11: 800x600 @ 75Hz 4:3, clock:49MHz progressive 
           mode 16: 1024x768 @ 60Hz 4:3, clock:65MHz progressive 
           mode 18: 1024x768 @ 75Hz 4:3, clock:78MHz progressive 
           mode 21: 1152x864 @ 75Hz 4:3, clock:108MHz progressive 
  (prefer) mode 35: 1280x1024 @ 60Hz 5:4, clock:108MHz progressive 
           mode 36: 1280x1024 @ 75Hz 5:4, clock:135MHz progressive 

Time to learn about monitors, again, last time was DOS era .
It just goes to show how well the Pi's have been supported that this has never been a problem for 7 years till now.
I should have been paying more attention to the messages the monitor displayed.

It has got me thinking about how well a 21:9 curved super-wide monitor would go on a Pi4.
And if Flightgear will compile on Gentoo64

Currently running Gentoo 64 on a pi4 at 21x9 and it looks amazing ^_^

How does one go about logging in as root or changing the demouser password? The passwd command asks for the current password which I don't have and a google search doesn't seem to pull up.

Check out the project's README - but in brief the root password is raspberrypi64

hth, sakaki

PS apt-get isn't going to work here (just like it won't in e.g. Arch Linux): gentoo has a different package manager, called Portage, and the cognate command to apt-get is emerge. For more details, see here.

I sincerely appreciate the assistance thank you!

[Gavinmc42]

Thanks Sakaki, it needed one more step, I'm using DVI monitors.

Code: Select all

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2

Broke some SD's by pulling power, will reburn, edit config.txt and it should all work then.
Next step(final) USB SSD's

Currently running Gentoo 64 on a pi4 at 21x9 and it looks amazing ^_^

Will add another jar for new monitor savings

[Gavinmc42]

[sakaki]

Glad it is working now ^-^
Have fun!
S

[bomblord]

So this seems to be reporting that it's using vc4 drivers (in the /etc/portage/make.conf)? I've tried a few different random games and none of them will get to the point where they render anything. Additionally it's showing some weird opengl info

Code: Select all

GLX version: 1.4
    Max core profile version: 0.0
    Max compat profile version: 2.1
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.0
OpenGL version string: 2.1 Mesa 19.1.4
OpenGL shading language version string: 1.20
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.1.4
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00

Opengles3 seems to be right but I'm unsure about everything else.

[sakaki]

bomblord,

hook up with jdonald on the Projects -> Gaming subforum here, he should be able to help you out.

Best, sakaki

[Gavinmc42]

bomblord, that looks about right.
Grab the mesa demos
https://github.com/freedesktop/mesa-demos
Unzip and rename to mesa-demos, open a terminal there.

Code: Select all

./autogen.sh
./configure
cmake .
make

This will get you a bunch of examples that mostly run these days.
I use these as my reference examples.
They now seem to be the first thing I install on any new Pi OS

I have tested lots of OpenGL games in the new Buster.
0AD needs the extra ram of the Pi4B2.
Many more just run now, how many run in Gentoo64?

[Gavinmc42]

Oh, goodie the 64bit Arm version works
https://hexler.net/products/kodelife#_
Just wish I knew how do shader coding, more learning

[Gavinmc42]

Going through these post and looking at old stuff

Gavinmc42 wrote:
Pi3B+ can get 300Mbs over Ethernet, is that faster than SD/USD drive speeds?
Network storage instead on local?
Hmm network swap file, nope probably better to go headless?

Funnily enough I did try swap over NFS onto an exported ramdisk of a PC on the same network. I actually had good success with this approach before, with another embedded board which had a (real) Gigabit Ethernet, but lousy on-board storage. It did create an additional point of failure and NFS wasn't perhaps the ideal transport, but I have to say it was pretty quick.

Will be interesting to revisit this with Pi4's now, faster USB3 and Network, can wait until I get a Pi4B4.

Rats, why did I choose the 16GB uSD card, just downloaded Arm's Compute Library Binary version and ran out of room to unzip it.
Time to get that 64GB uSD card running.
Will be interesting to check this precompiled version against a new A72 optimized version.
Double rats, Compute compile errors

[bomblord]

bomblord, that looks about right.
Grab the mesa demos
https://github.com/freedesktop/mesa-demos
Unzip and rename to mesa-demos, open a terminal there.

Code: Select all

./autogen.sh
./configure
cmake .
make

This will get you a bunch of examples that mostly run these days.
I use these as my reference examples.
They now seem to be the first thing I install on any new Pi OS

I have tested lots of OpenGL games in the new Buster.
0AD needs the extra ram of the Pi4B2.
Many more just run now, how many run in Gentoo64?

Might just be the games they seem to want a newer version of Open GL. Also note to self don't change fkms to kms for the graphics driver it makes the image unbootable until you change it again in the config.txt.

[jdonald]

Might just be the games they seem to want a newer version of Open GL.

The GPU driver supports up to OpenGL 2.1, but software rendering can do up to OpenGL 3.3. If you run into such a case you can test to see if it renders (slowly) by prefixing your command with LIBGL_ALWAYS_SOFTWARE=1. If the game still doesn't start, then your issue is probably something else.

To my knowledge it isn't (yet) common for Linux games to require OpenGL 3.0, even on x86. Dolphin is the exception, but hopefully everyone's on the same page now to run that with GLES 3.0 on the Pi 4:
* https://forums.dolphin-emu.org/Thread-d ... -4?page=10
* https://www.raspberrypi.org/forums/view ... 8&t=248950

[MamiyaOtaru]

screen was blank for me on a pi 4 connected via HDMI to a 2560x1440 screen. Edited all sorts of stuff in config.txt to force it to 1920x1080, be single screen only etc. No matter what, I would get the rainbow pattern, the four raspberries, a bunch of console output, then around when it looked like X would be starting the display went blank, and nothing would bring it back (no ctrl-alt-f1, nothing). HDMI safe mode worked, but being stuck at 640x480 wasn't cool

I managed to get it working by copying start4.elf and fixup4.dat from raspbian onto the gentoo card's boot partition. You may look into updating those?

[sakaki]

I managed to get it working by copying start4.elf and fixup4.dat from raspbian onto the gentoo card's boot partition. You may look into updating those?

Had you run rpi-update on the Raspbian image you copied these /boot files from? The image as shipped has the 20190718 boot firmware, which may or may not be better than the firmware shipped on the currently downloadable (20190710) Raspbian image (or the current 20190819 firmware).

Edit: if you just post the md5sums of these files, I can work out which version you have used. Thanks!

Best, sakaki

[Gavinmc42]

MamiyaOtaru, if it is working on Buster ok then run "tvservice -v 2 -m DMT"
Then edit the Gentoo64 config.txt with those values.
This solved my monitor issues.

[sakaki]

MamiyaOtaru, if it is working on Buster ok then run "tvservice -v 2 -m DMT"
Then edit the Gentoo64 config.txt with those values.
This solved my monitor issues.

It may be though, that an newer/older version of the /boot firmware (start4*.elf and fixup4*.dat) can fix the autodetection, which would be better than having to hack around with the config.txt file; so I'd still be interested to know what the timestamp on the "blessed" /boot files used was.

How is the image working for you so far otherwise, Gavinmc42?

Best, sakaki

[Gavinmc42]

How is the image working for you so far otherwise, Gavinmc42?

An easy way to change timezone and to US keyboard.

Just wondering if commenting "#hdmi_drive=2" might have been enough for DVI monitor detect to work?

Code: Select all

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2

Next to try is billw's USB drive cloner so I can boot from uSD and everything else is on USB SSD
https://github.com/billw2/rpi-clone

Been finding the USB hub in the Raspberry keyboard very handy.
Keyboard2 will have SDcard connectors I hope?

Gentoo64 SDcard burning/copying is next to get figured out.
One thing I loved on my Linux Mint box was two USB apps.
USB Image Writer and USB Stick Formatter.

Lots for software to get onto my Pi4/Gentoo64 boxes.
FreeCad, OpenScad, these have issues on Buster
Blender for Artist again, it works well on Buster now.
Probably Kicad for PCB design

Lazarus/FPC needs to be sorted, but a binary fpc version is working.
Optimizing all these for A72
Assort compilers and FPGA design tools.
3D software, slicer, printer, G-code, cnc…
Backup server.

Just the basic tools for a desktop dual screen hardware/software developer
Dual 21:9 screens?
It is looking very good for the average home hacker with Pi4's these days.

[Gavinmc42]

Yep, just by commenting the "#hdmi=2 line" things worked, don't need monitor settings.
I have the specific monitor settings commented out now.
Looks like forcing a DVI to be HDMI has been the issue?

You might want to consider putting a note about that somewhere or leave it commented out as default?

[sakaki]

Yep, just by commenting the "#hdmi=2 line" things worked, don't need monitor settings.
I have the specific monitor settings commented out now.
Looks like forcing a DVI to be HDMI has been the issue?

You might want to consider putting a note about that somewhere or leave it commented out as default?

Ah. I actually did change this option - it was commented out in 1.4.2. Looks like it is causing problems with some displays.

Would you mind trying a test? If you take a fresh, unbooted copy of the image, then only make the modification of commenting out the "hdmi_drive=2" line in /boot/config.txt, then boot it with your problematic monitor attached, does the image start up OK and display properly?

If so I'll probably look to release a minor bugfix release with this change reverted.

Thanks! sakaki

[derders]

for me too I had a black screen on my PI4 4GB via HDMI to TV 1080p

copied all start*.elf and fixup*.dat from my latest updated dietpi after reading it here

start4.elf has MD5 15FD86732474DCD39C902C7A804BD9DD
fixup4.dat has MD5 BDEA9BEFA5203A9D37FE9C16BCF59C3F

and I have a desktop

puh... after 2 hours of trying with some config.txt changes ...


time to get some sun and try it out later ...

[Gavinmc42]

Ah. I actually did change this option - it was commented out in 1.4.2. Looks like it is causing problems with some displays.

Would you mind trying a test? If you take a fresh, unbooted copy of the image, then only make the modification of commenting out the "hdmi_drive=2" line in /boot/config.txt, then boot it with your problematic monitor attached, does the image start up OK and display properly?

If so I'll probably look to release a minor bugfix release with this change reverted.

That explains why I had no luck with 1.42.
I did comment out the force HDMI, it worked three times on three uSD's.

To test with the rest of my 16GB cards I wanted to edit them in Gentoo64, hence file manager access to USB reader
USB access via Accessories- disk works, now it is just remembering where the hash symbol is on my non UK keyboard
Perhaps automount is not working?

The last thing is how to display temp on the panel, need that for stress test indicator when compiling the big stuff.

Now have 6 Pi's I can run Genoo64 on, going out to get a 1Gbs Ethernet Switch to connect them up.

I can see the advantage now of the ebuild system,
Warzon2100 3.3 beta compiled and ran A72 optimized.
Apart from some audio issues it runs better than Buster which has serious graphics issues..
Your Gentoo64 OpenGL is better than Buster's OpenGL
Or Buster deb is older?

[sakaki]

Thanks - opened an issue on GitHub to alert people about the hdmi_drive thing; it will be fixed in v1.5.1.

For a simple temperature monitor (not in a panel though) you can run:

Code: Select all

demouser@pi64 ~ $ watch vcgencmd measure_temp

Best, sakaki

[Gavinmc42]

Thanks Sakaki, i missed the obvious way to read temp

Been doing some serious emerges to get this working
https://www.raspberrypi.org/forums/view ... d#p1499505

I got this message from the FreeCAD build script after I had emerged sci-libs/opencascade.

Code: Select all

Could NOT find OCC (missing: OCC_INCLUDE_DIR) 
CMake Error at CMakeLists.txt:699 (message):
  ================================================================

  Neither OpenCASCADE Community Edition nor OpenCASCADE was found!

  ================================================================

Coin3d emerged ok, so some of the Buster issues don't seem to effect Gentoo64?
These big emerge do seem to work better on the 2GB Pi4,, trying this on a 1GB and there is not much free memory. Even with 2GB it is best not to have Chromium running with too many tabs;)

Not sure how long sci-libs/opencascade took, ran it overnight - 8+hours.
Can Distcc be used to speed this up?
Got a 5 port Gbs switch I'm going to mount Pi's on for a cluster.

Is there a wiki you can point me at for speeding up emerges/ebuilds.
Debian can make debs, what is the Gentoo equivalent and where do they hide when they are made.
I'm sure others might like FreeCAD without the pain of 3 days of building.