05:00 <Jookia> Good(?) news, I think my NAND issues come from hardware faults

05:32 <veremitz> :/

05:32 <veremitz> good that its an answer :)

05:32 <veremitz> or explanation I s'pose

13:14 <apritzel> warpme: junari: is there any news on the LPDDR4 front? Does the code work reliably on the OrangePi Zero 3 now? And problems are just with other boards?

13:37 <warpme> apritzel : from my side: last state is: it works but unstable. I compared dram controller registers between stable xulong code and non-stable code and there are differences. I recall Junari is working on this issue.

13:39 <apritzel> OK, thanks, and that was on your OrangePi Zero3?

13:39 <warpme> yes

13:39 <warpme> and zero2w

13:40 <apritzel> alright, thanks. I was thinking about merging some code now, so we still get that in the next release

13:41 <apritzel> we would still have till the end of the year to apply fixes

13:41 <warpme> i just got Eth board for zero2w and interesting is that using Eth makes hard hangs for me. Switching to wifi (by only reconfig what intf is used by dhcp) works stable. very strange....

13:42 <apritzel> the LPDDR4 patches would unblock people that want to play with those new H618 boards, that mostly seem to ship with LPDDR4

13:42 <warpme> exactly!

13:43 <warpme> I was trying to play with dram clk (decreasing) - but this not helps....

13:43 <apritzel> junari: when you read this: is there any chance you could post some "best state so far" LPDDR4 patch on the list?

13:48 <warpme> good thing is that we have xulong code (based on uboot 2021.07) which seems to work well with lpddr4. Maybe it is worth to try to adjust CONFIG_DRAM_SUN50I_H616_* para in defconfig to values resulting with exact the same dram controller registers values like stable xulong code does?

13:49 <apritzel> yeah, I tried before to correlate the Xulong code, but then Junari came up with his version, so I dropped that

13:49 <apritzel> I can have a look again

22:07 <DonkeyHotei> Hi, all. I'm revisiting this old Armbian-xenial system, and it seems to have this weird issue where ping fails with EPERM and setcap does not fix it, with another symptom being that DNS fails within Chromium while still working fine in other contexts

22:07 <DonkeyHotei> EPERM even as rooy, I meant

22:07 <DonkeyHotei> *root

22:13 <DonkeyHotei> What else could cause that?

22:15 <DonkeyHotei> I ask here on the assumption that I'm not the only one here who has seen such a thing happen

22:19 <bauen1> DonkeyHotei: something like SELinux, Apparmor, SECCOMP / eBPF filters / sandbox ?

22:20 <bauen1> DonkeyHotei: oh and user namespaces also

22:20 <bauen1> DonkeyHotei: but these are just general ideas, nothing specific to your system

22:20 <gnarface> the only bell it rang for me was also something about virtualization

22:21 <gnarface> a side effect of using a tun/tap network device as the primary or something like that

22:21 <gnarface> i forget exactly

22:21 <DonkeyHotei> gnarface: This is on bare metal

22:21 <gnarface> it involved virtualization, but the network device in question was technically the host's

22:22 <DonkeyHotei> bauen1: User namespaces seems the most likely explanation here. Got any link with info?

22:24 <Jookia> technically it would be network namespaces

22:25 <DonkeyHotei> Jookia: Regardless of the semantics, got any URL?

22:25 <Jookia> if 'root' means your actual root user then this shouldn't be happening

22:25 <Jookia> how are you running ping?

22:26 <Jookia> EPERM can also mean linux firewall rules

22:27 <bauen1> DonkeyHotei: the manpage for unshare I guess ? Basically user (/ network) namespaces could mess with the capability required by ping

22:27 <DonkeyHotei> Jookia: If "su -" counts as the actual root user, then it *is* happening

22:28 <Jookia> try logging in at a root prompt over serial

22:28 <Jookia> or tty

22:28 <DonkeyHotei> I believe I tried that before, but I'll try again

22:28 <Jookia> do you have any specific firewall rules

22:31 <DonkeyHotei> None

22:40 <DonkeyHotei> Jookia: Logged in as root via serial, still EPERM from ping

22:49 <Jookia> huh, weird

22:50 <DonkeyHotei> Well , "weird" was the very word I used for this in the first line of this convo

23:07 <DonkeyHotei> "ip netns list" just returns EOF

23:24 <DonkeyHotei> Well! Given your [plural] clues, I found the cause: https://askubuntu.com/questions/868590/ping-socket-permission-denied

23:25 <DonkeyHotei> Now ping works, but only as root. However, the DNS side of it is still not solved, because "host google.com" also works only as root

23:32 <DonkeyHotei> Aaaaand, adding non-root users to those groups fixes that. Problem solved.

23:32 <DonkeyHotei> Thank you!