Description of problem:
The https://fedoraproject.org/wiki/Common_F27_bugs#aarch64-nonetwork-pine64 says
When booting the AArch64 disk images on the Pine 64 you will not
have a network connection. To correct this issue create a symlink
named 'dtb' pointing to the installed kernel dtb directory
(dtb-4.13.9-300.fc27.aarch64) and reboot the system.
cd /boot; ln -sf dtb-4.13.9-300.fc27.aarch64 dtb
On my Banana Pi M64, I had to make the same symlink to make network (eth0) work. Assuming network is something people want, so either the page on the fedoraproject.org should be amended, or the fedora-arm-installer should be changed to add that symlink.
Version-Release number of selected component (if applicable):
Documentation as of today.
Steps to Reproduce:
1. sudo fedora-arm-image-installer --image=/tmp/Fedora-Minimal-27-1.6.aarch64.raw.xz --target=bananapi_m64 --media=/dev/mmcblk0 --selinux=ON --addconsole --norootpass -y
2. Put the SD card to the Banana Pi M64 board SD slot and boot with ethernet connection.
It does not appear to get IP via DHCP (and due to lack of console it virtually not accessible).
Ethernet works and the board gets DHCP and is accessible via sshd.
it's definitely more than just the Pine 64 listed on the wiki that need the fix.
The wiki page should also mention to keep that dtb symlink in sync with the kernel version after kernel updates, even if for me the kernel update renders networking not working even with the dtb symlink updated -- bug 1528593.
Same problem for Pine64
It's a known problem, I know the logic needed to fix it, I just need time to code it up and test the fix
(In reply to Jan Pazdziora from comment #2)
> The wiki page should also mention to keep that dtb symlink in sync with the
> kernel version after kernel updates, even if for me the kernel update
> renders networking not working even with the dtb symlink updated -- bug
That's a bug, I just need to get the time to work out the exact logic, I know what needs to be done, I just need the time to finish up the fix.