Gen too minimal install currently suffers from a bug where genkernel does not correctly generate initramfs with realtek.ko loaded before r8169.ko. This makes network and hence the whole install image unusable on these systems. Please see https://bugzilla.kernel.org/show_bug.cgi?id=204343
Which installcd is this? AFAIK this issue was fixed already by disabling loading of NET modules by default in genkernel-4. Even if net modules are to be loaded (for "dosshd" for example), this commit should have fixed realtek: https://gitweb.gentoo.org/proj/genkernel.git/commit/?id=63f7d255e2dc2956f293f1e7f5f7b4c503951fb0 If this is still failing on a brand new installcd, please share the dmesg output. (unloading & reloading r8169 can get you back online, to aid in sharing logs from the booted installcd)
I have just booted install-amd64-minimal-20200603T214508Z.iso and it does not load r8169 in initramfs
This was install-amd64-minimal-20200531T214503Z.iso However it gets a bit trickier than I thought. Originally this system had some version on arch on it in the past. When I tried using the above installcd it would be posting same error messages in dmesg and exhibiting same behaviour as described in the kernel bug referenced above. Reloading the module did not help. I had to resort to digging out an old install-amd64-minimal that I had lying around on an old laptop. Using this I compiled the r8169 and realtek in-kernel. When I tried booting install-amd64-minimal-20200531T214503Z.iso now, after successfully running with the in-kernel drivers, the installcd boots fine! Sorry, I didn't expect this twist. Feel free to close the bug as I can't prove it and you'd have to take my word for it.
I believe you that something happened and there was a failure. I do not believe that it was the same as the kernel.org bug or the same problem you think it is. I do not hold any of this against you, feel free to reopen the bug if you can reproduce this and provide logs =)
