00:28 <owrt-images-builds> Build [#17](https://buildbot.openwrt.org/images/#/builders/208/builds/17) of `main_bcm47xx/legacy` completed successfully.

02:36 <owrt-images-builds> Build [#16](https://buildbot.openwrt.org/images/#/builders/252/builds/16) of `main_malta/be64` completed successfully.

04:22 <owrt-images-builds> Build [#16](https://buildbot.openwrt.org/images/#/builders/254/builds/16) of `main_kirkwood/generic` completed successfully.

04:50 <owrt-images-builds> Build [#16](https://buildbot.openwrt.org/images/#/builders/88/builds/16) of `main_ramips/rt288x` failed.

06:02 <owrt-images-builds> Build [#16](https://buildbot.openwrt.org/images/#/builders/218/builds/16) of `main_ipq40xx/generic` failed.

08:45 <svanheule> mirko: the channel is #rtl83xx on libera.chat

08:46 <svanheule> mirko: the user who reported it is kobubs, but no updates since

09:23 <owrt-images-builds> Build [#16](https://buildbot.openwrt.org/images/#/builders/26/builds/16) of `main_qualcommax/ipq807x` completed successfully.

09:24 <owrt-images-builds> Build [#17](https://buildbot.openwrt.org/images/#/builders/91/builds/17) of `main_bmips/bcm63268` failed.

10:36 <owrt-images-builds> Build [#16](https://buildbot.openwrt.org/images/#/builders/162/builds/16) of `main_ipq806x/generic` completed successfully.

11:14 <stintel> geez, that Cudy AP3000 Outdoor is huge

11:32 <stintel> I'm so going to mess up the neighbors non-AX networks by putting an outdoor AX AP :P

11:32 <stintel> BSS coloring ftw

11:35 <stintel> "Apply Cudy Intermediate OpenWrt image for AP3000 Outdoor V1" from google drive feels extremely dodgy though

11:35 <stintel> how was this even accepted

11:40 <schmars[m]> ah there's an intermediate image now, cool

11:41 <schmars[m]> i had to flash mine over serial with xmodem, early bird

11:41 <schmars[m]> check if your port negotiates 1g/2.5g correctly, in snapshot a month ago i had an issue there

11:41 <stintel> if I read the specs it's just GE ?

11:42 <stintel> Speed : 1000, Loopback: NONE

11:42 <stintel> is what le switch says

11:42 <schmars[m]> yoooo the specs used to say 2.5g

11:42 <schmars[m]> very sure

11:42 <schmars[m]> so they really fucked up that ethernet port properly i guess

11:43 <schmars[m]> their factory u-boot has broken ethernet too, that's why no tftp

11:43 <stintel> ah, after the intermediate flash, thing disappeared from netowkr

11:43 <schmars[m]> (oh no wait the broken ethernet is on the indoor variant, sorry)

11:44 <stintel> hmm maybe the intermediate image is OpenWrt and has 192.168.1.1

11:44 <schmars[m]> waiiit your right about 1g port. they "2.5g" in all marketing material is about the wifi hahaha

11:44 <schmars[m]> nevermind me, all good, but still curious how the device works for you

11:45 <stintel> nope, SOL

11:46 <stintel> yeah really, requiring a binary intermediate as part of the OpenWrt installation procedure is really unacceptable imo

11:48 <schmars[m]> yeah not ideal but seems pragmatic to me compared to the hassle that some other vendors are

11:48 <schmars[m]> writing the image over serial also works, without the intermediate image

11:49 <stintel> would have been nice if that was documented in the commit message

11:50 <schmars[m]> there's a chance for rectification with the indoor veriant :-)

11:50 <stintel> I just returned them

11:50 <stintel> TP-Link EAP683-LR/UR will be my AP of choice for intodor

11:50 <stintel> indoor*

11:51 <stintel> although risky, as you and f00b4r0 seem to have unfixed issues with the mtk 802,11ax stuff

11:51 <stintel> and focus already shifted to wifi 7

11:52 <stintel> and fixing wifi6 issues seems not important

11:52 <schmars[m]> for me the few seconds downtime during recovery are fine. actually we had to tear down that site where it occured daily. i'm basically not affected by that crash anymore

11:52 <stintel> few seconds is unacceptable to me

11:53 <schmars[m]> that's understandable

11:54 <schmars[m]> will tp-link make an outdoor variant similar to the old eap225-outdoor?

11:55 <stintel> fingers crossed ¯\_(ツ)_/¯

11:55 <stintel> so that intermediate image ... fail to reach it

11:56 <schmars[m]> i need something with external rp-sma, so we can do 11ax sector antennas. not a lot of options in that area unfortunately. basically the cudy, and the zyxel

11:56 <stintel> exactly why we don't want binary intermediate shite

15:57 <dviola> the TL-WR802N v2 uses the same CPU as my TL-WR840N v2 as is still supported in openwrt git, same RAM/flash size and all, I was wondering whether I could use the same dtsi as the older version and make it work

15:57 <dviola> I mean, before I throw it away

15:58 <dviola> any chances that would work?

16:14 <robimarko_> DTS is irrelevant for resource usage

16:15 <robimarko_> It might exist in the tree, but it was marked as 4MB device then it has not had images generated for a long long time for it

16:15 <robimarko_> Just forget about 32MB RAM devices

16:16 <dviola> it's the only device I have right now

16:18 <robimarko_> I understand, its just not feasible to run OpenWrt on it anymore

16:19 <f00b4r0> unless you want to run something ancient such as 19.07 which should work

16:20 <robimarko_> I have been poking at the seccomp getting selected issue

16:21 <robimarko_> It seems to be the same issue that nbd pushed the initial fix for

16:22 <robimarko_> Its like getting evaluated before the value is even set

16:43 <dviola> f00b4r0: it's been running ancient versions just fine but I still want some of the newer ones, I can compile openwrt and do everything from the CLI, I'm just curious about the dts/dtsi at this point

16:43 <dviola> and I will get a new router, just haven't decided which one yet

16:50 <dviola> I don't care if I run into OOM, if it boots that's all I care about, I'm also trying to learn about openwrt here

17:23 <dviola> also, there are no images for 19.07 and I can't compile it anymore, my compiler is too new, and python 2.x isn't easily available on distros anymore

17:24 <dviola> therefore I would like to try a newer version, even if that means it would suck... but this dtsi stuff is kind of stopping me

17:33 <dviola> seems device specific and I don't have all the info it needs

18:10 <robimarko_> If it was supported in ar71xx then you should have enough information

18:12 <dviola> yeah, I'll into that, thanks

18:17 <dviola> would be neat if I could just reuse the dtsi from the previous model, then fill in the bits here and there

18:17 <dviola> if needed

18:21 <dviola> https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=7e513136c63108bf55b38be4d2b65aa00b0d2b26

18:53 <dviola> I wonder how ar71xx dealt with the partitions {} stuff

18:58 <tmn505> Mostly by specifying partitions in kernel command line. Check /proc/cmdline of Your device.

19:01 <dviola> I mean the reg = <0x000000 0x020000>; and such

19:04 <dviola> pretty sure I'll brick my device if I get this wrong, might need to get another router first

19:05 <tmn505> exactly as I said, but tp-link devices probably used tplink-safeloader or whatever they came up with.

19:06 <tmn505> check this https://github.com/openwrt/openwrt/blob/openwrt-19.07/target/linux/ar71xx/image/common-tp-link.mk

19:07 <totkeks> is there a general way to deal with packages that want to store data in /var/lib? Because that is mapped on /tmp/ it is gone after reboot and the package, stubby again, doesn't work properly. My thought was to just put some lines in the init script that make sure the folder is there and has the right permissions. Is that the way or is there another way/api?

19:07 <dviola> tmn505: ah, I misunderstood that

19:08 <dviola> makes sense now, thanks

19:39 <dviola> this seems to be what I was looking for: https://openwrt.org/docs/techref/flash.layout#discovery_how_to_find_out

19:39 <dviola> looks like I have all the info now

19:56 <dviola> still worried about flashing this one, I assume it'll boot even if the other values are incorrect, as long as the partitions are fine

22:05 <mrkiko> auto-answer to myself: no, there is no real problem with nfs root support. It's me, thatdidn't enable the correct option in openwrt build system