Talk:Hetzner Cloud (ARM64)

From Gentoo Wiki
Jump to:navigation Jump to:search
Note
This is a Talk page - please see the documentation about using talk pages. Add newer comments below older ones, sign comments using four tildes (~~~~), and indent successive comments with colons (:). Add new sections at the bottom of the page, under a heading (== ==). Please remember to mark sections as "open for discussion" using {{talk|open}}, so they will show up in the list of open discussions.

feedback

Talk status
This discussion is still ongoing.

I found this article and I realized that I also installed gentoo on the hetzner cloud on one of these 2 core arm64 vservers. --Alexander-n8hgeg5e (talk) 05:28, 2 March 2024 (UTC)

Feel free to complete the page. Did you use IPv4 or genkernel? Is jitterentropy not working either (I think I misconfigured the kernel)? --Lars Hint (talk) 07:14, 2 March 2024 (UTC)
Or did I misunderstand something and you installed Gentoo on something else and the installation process was the same? :) --Lars Hint (talk) 11:32, 2 March 2024 (UTC)
No you understood me correctly, I'm just a bit unresponsive sometimes. I installed it on one of these new arm64 v-servers, the small one with 4G ram.
Usually I use my self made kernel ebuild but this time I tried genkernel. I don't remember whether I used a config from /proc/config.gz as a base.
It seems I did something completely different and I can only assume that the file
in /etc/kernels/kernel-config-6.6.13-gentoo-arm64 is my kernel config.
Jitterentropy is a module in my config, but not loaded.
CONFIG_CRYPTO_JITTERENTROPY=m
If I load it with (is this the right one?): modprobe jitterentropy_rng
Then:
modprobe: ERROR: could not insert 'jitterentropy_rng': Bad address
For the network I configured both IPV4 and IPV6.
The network setting was the part that I initially had no clue about how to do it.
Then I found the network settings on the preinstalled system and discovered that they are mostly static.
I configured IPv4 and IPv6. Essentially only the first 2 lines differ from your config:
modules="dhclient"
config_enp1s0="dhcp
2a01:4f8:_:_::1/64"
routes_enp1s0="default via fe80::1"
dns_servers_enp1s0="2a01:4ff:ff00::add:1 2a01:4ff:ff00::add:2"
Then I installed wireguard on the system.
Alexander-n8hgeg5e (talk) 20:19, 6 March 2024 (UTC)