networking issues

[Merith-TK]

Just a collection of issues ive noticed

1. To access anything outside of my LAN i have to run ip route add default via 192.168.0.1
2. mirror.archlinuxarm.org never responds... ever

[root@alarm ~]# pacman -Syu
:: Synchronizing package databases...
error: failed retrieving file 'core.db' from mirror.archlinuxarm.org : Resolving timed out after 10001 milliseconds

[Merith-TK]

--Note, i am unsure if the second one is related to how archarm is being ran, or not, but either way it does not have control over the host Networking--

It appears to have something to do with how networking is done on the steamlink itself. If we could disable the steamlinks desire to control networking, this probably would work

[coderobe]

the original steam link system shouldn't be doing anything anymore after the system has pivoted to the archlinux root, make sure you have a nameserver configured in resolvconf

[Merith-TK]

I am sure, I have even tried to use network manager, however, one the system pivots over, all steam link resources cannot be loaded by ini, Meaning the networking should not work without enabling it via arch-chroot or enabling a systemd service, Yet it does. Which means networking still occurs before the steam link hands itself over to run.sh,

…

On Fri, Aug 7, 2020, 11:46 AM Robin M. B. ***@***.***> wrote: the original steam link system shouldn't be doing anything anymore after the system has pivoted to the archlinux root, make sure you have a nameserver configured in resolvconf — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACPQOXVUX6BB4HVWW5MSEZ3R7RDWVANCNFSM4PSV2XYA> .

[fijam]

There are definitely issues with networking, see e,g,

[root@alarm /]# dhcpcd
dhcpcd-9.4.0 starting
sandbox unavailable: seccomp
dev: loaded udev
DUID 00:01:00:01:c7:92:bd:e5:e0:31:9e:2e:ef:e4
sandbox unavailable: seccomp
eth0: IAID 9e:2e:ef:e4
eth0: soliciting a DHCP lease
ps_bpf_start_bpf: bpf_open: Protocol not available
ps_root_recvmsg: Protocol not available
ps_sendpsmmsg: Connection refused
ps_root_recvmsgcb: failed to send message to pid 1643: Connection refused

[coderobe]

that's without kexec (i.e. what's currently in this repo)? in which case that sounds about right, but shouldn't be a problem after a kexec boot chain is setup

i planned to add instructions for that to this repo long ago, but haven't yet come around to doing that

[fijam]

Thanks for the reply, I have kexec setup working (https://heap.ovh/getting-linux-on-valve-steam-link.html) but the upstream kernel is missing some drivers (like NAND) and wifi is a bit wonky (e.g upstream firmware loses 5GHz).