<slh>
Tapper: e.g. RPI4 + USB3 ethernet card (retaining the r7800 as managed switch and AP), nanopi r4s + r7800 as AP/ switch (availability and prices are going into the wrong direction at the moment) - or betting on wifi6 with the Belkin rt3200 (fully supported) or Xiaomi AX3600 (not quite supported yet)
<slh>
...either may profit from a cheap second hand rtl838x based (OpenWrt supported) switch ;)
<Tapper>
slh yeah you have a point.
<Tapper>
That m300 would have to be put in a place where you could not here it to mutch.
<slh>
yep
<slh>
all of the examples above are fanless and silent
<Tapper>
I did look at the Belkin rt3200 but the cost was to high
<slh>
with the larger switches above 16 ports you need to get the right model (some are fanless, others aren't)
<slh>
prices have risen from ~95 EUR to ~155 EUR over the last two weeks
<Tapper>
What about putting a pasave heat sink on the m300?
Rentong has joined #openwrt-devel
<slh>
Tapper: not an option, it's basically built like a small 1U rack server, active server PSU, small active fan in the back - you could probably run the board fanless in an open case, but not the PSU
<Tapper>
O rite.
<slh>
pretty much like an x86_64 mainboard sitting inside the case (with quite a few empty space around it)
<slh>
Tapper: if you're patient and persistent, you can often get a 24 port (passively cooled) smart-managed L2 switch under 45 EUR in good/ used condition, even 15-20 EUR for an 8 port one
<slh>
rtl838x based
Rentong has quit [Ping timeout: 480 seconds]
<Tusker>
rtl838x based to can run openwrt potentially ?
<Tusker>
s/to/so/
<slh>
Tusker: there are quite a few rtl838x based devices that aren't supported by OpenWrt, but would probably be relatively easy to get supported
<slh>
e.g the whole ZyXEL gs1900 model range (only the gs1900-48 is rtl839x based, there is proof of concept code for that SOC, but it's not merged yet)
<Tusker>
should probably replace my cisco 3560 at some stage
<Tapper>
I just had my wife look to see what the m300 looks like and tell me. lol she just said no! hahahah it's brite red.
<slh>
https://biot.com/switches/models those are the known ones so far, not all of them are supported yet - some probably never will be (not enough flash/ RAM), some will be very difficult (vendor locked down u-boot, hello HPE, TP-Link) - but most of them /could/ be supported
<Tapper>
It would defo have to be put in a cupboard
<Tusker>
slh: ah cool, good list to create an alert
<slh>
the NanoPi r4s is an interesting device (form-factor/ design wise it appears to be nicer than the RPi4 solution, although the RPi4 should be slightly faster), but availability and prices aren't good at the moment
rua has joined #openwrt-devel
goliath has quit [Quit: SIGSEGV]
Tapper has quit [Ping timeout: 480 seconds]
wulfy23 has joined #openwrt-devel
<wulfy23>
possible sluggish logd or similar regression recent master post procd -init- for a few seconds
wulfy23 has quit [Remote host closed the connection]
wulfy23 has joined #openwrt-devel
<wulfy23>
not seen on reboot... likely false alarm (again)
wulfy23 has quit []
philipp64|work has quit [Quit: philipp64|work]
<enyc>
digitalcircuit: given what you say, and page you linked, disabling l2 cache sorts it, .... definitely I would try either slightly increaed volts or certainly if this is an onboard physical separate buck-converter I'd certainly try adding a bit more low-ESR filter capacitance across the output reservoir on that buck-cnverter ...
<enyc>
digitalcircuit: the point being external PSU (may) be nothing so much to do with it, it may be a "loaded within inch of its life" internal buck converter (voltage dropping) supply ...
dedeckeh has quit [Remote host closed the connection]
dedeckeh has joined #openwrt-devel
goliath has joined #openwrt-devel
<digitalcircuit>
To clarify, I'm not entirely disabling L2 cache, just the highest frequency, but what you've said makes sense.
<digitalcircuit>
enyc: Noted, thank you!
<digitalcircuit>
I don't know if the NBG6817 has an accessible internal buck converter; the voltage level is controlled via software so I'm (naively) guessing it's a surface mount component somewhere. Even so, your point on why the external PSU would not affect it as a result seems plausible too.
decke has joined #openwrt-devel
rua has quit [Ping timeout: 480 seconds]
rua has joined #openwrt-devel
rua has quit [Remote host closed the connection]
rua has joined #openwrt-devel
Acinonyx_ is now known as Acinonyx
clef_ has joined #openwrt-devel
clef has quit [Read error: Connection reset by peer]
robin_ has quit [Ping timeout: 480 seconds]
robin_ has joined #openwrt-devel
clef_ has quit [Read error: Connection reset by peer]
clef has joined #openwrt-devel
nitroshift has quit [Quit: Gone that way --->]
nitroshift has joined #openwrt-devel
rua has quit [Ping timeout: 480 seconds]
goliath has quit [Quit: SIGSEGV]
rua has joined #openwrt-devel
danitool has joined #openwrt-devel
gladiac is now known as Guest4478
gladiac has joined #openwrt-devel
Guest4478 has quit [Read error: No route to host]
danitool has quit []
noltari has quit [Quit: Bye ~ Happy Hacking!]
goliath has joined #openwrt-devel
noltari has joined #openwrt-devel
gladiac has quit [Quit: Ping timeout (120 seconds)]
gladiac has joined #openwrt-devel
gladiac is now known as Guest4481
gladiac has joined #openwrt-devel
Guest4481 has quit [Read error: No route to host]
danitool has joined #openwrt-devel
Tapper has joined #openwrt-devel
<mrkiko>
enyc: are you the guy experimenting with voltate and ipq8xxx?
gladiac has quit [Read error: No route to host]
gladiac has joined #openwrt-devel
<enyc>
mrkiko: no
clef has quit [Ping timeout: 480 seconds]
Tapper has quit [Ping timeout: 480 seconds]
Tapper has joined #openwrt-devel
dangole has joined #openwrt-devel
danitool has quit [Quit: Cubum autem in duos cubos, aut quadratoquadratum in duos quadratoquadratos]
Tapper has quit [Read error: Connection reset by peer]
Tapper has joined #openwrt-devel
rejoicetreat has joined #openwrt-devel
Rentong has joined #openwrt-devel
Rentong has quit [Remote host closed the connection]
<abiliomarques>
what do you mean? I was wondering why not using something like musl 1.2.2
<PaulFertser>
abiliomarques: oh, I was too fast reading, just assumed you mentioned a version where it was fixed.
<abiliomarques>
musl 1.2.1 included a new malloc (mallocng) that in theory does not use floating point
<abiliomarques>
most of the MIPS I have don't have a FPU
<zx2c4>
stintel: rsalvaterra: ive never heard of any of this about random port changes. Would have been nice to get a real bug report about that. On the otherhand, the fact that you witnessed a bug, didnt report it or do anything with it, and then just moved on elsewhere doesn't give me much motivation to chase down something youre seeing but others arent. If you'd like this fixed, though, please get in touch with real details; you
<stintel>
probably not super useful, but that's why I found in my IRC history this year
<zx2c4>
Weird bug, no idea. Seems like a openwrt script issue?
<zx2c4>
Might be useful to open a GitHub report?
<stintel>
could be, never got any useful responses, so wasn't sure if openwrt or wg problem
LiCeUser4 has quit [Read error: Connection reset by peer]
<stintel>
hence not reported upstream, etc
LiCeUser4 has joined #openwrt-devel
<zx2c4>
Sun Mar 14 15:21:41 2021 daemon.err netifd[2253]: proto_shell_handler(231): run setup for interface 'wg0'Sun Mar 14 15:21:42 2021 daemon.err netifd[2253]: interface_set_available(465): Interface 'wg0', available=0Sun Mar 14 15:21:42 2021 daemon.err netifd[2253]: proto_shell_handler(231): run teardown for interface 'wg0'
<stintel>
and netifd being the black box that it is doesn't help
<zx2c4>
Upstream or downstream, a good bug report helps, and also i help maintain the downstream package
<zx2c4>
Those three lines seem to indicate the trouble beginning -- something happens during setup, and then it backs out
<mrkiko>
Hello! I am still in the process of trying to port R6100 to ath79. I am at the point where I am able to exchange ICMP replies with the device and obtain replies only for packets of about 40 bytes in size
LiCeUser4 has quit [Read error: Connection reset by peer]
<mrkiko>
I set the pll values for ar9344
LiCeUser4 has joined #openwrt-devel
<mrkiko>
but I guess I'm failing to tell the builtin switch to go to analog mode or something
<mrkiko>
Tapper: u-boot is very nice on that device. It's opne-source, you can customize it to be more accessible
Tapper has quit [Ping timeout: 480 seconds]
LiCeUser4 has quit [Quit: Time wasted on IRC: 15 hours 46 minutes 41 seconds]
<Slimey>
:p
rejoicetreat has quit [Ping timeout: 480 seconds]
dangole has quit [Ping timeout: 480 seconds]
decke has quit [Quit: Leaving.]
goliath has quit [Quit: SIGSEGV]
Rentong has joined #openwrt-devel
Rentong has quit [Remote host closed the connection]
Tapper has joined #openwrt-devel
tohojo has joined #openwrt-devel
rejoicetreat has joined #openwrt-devel
dannyAAM has quit [Quit: znc.saru.moe : ZNC 1.6.2 - http://znc.in]
dannyAAM has joined #openwrt-devel
Tapper has quit [Read error: Connection reset by peer]
Tapper has joined #openwrt-devel
rejoicetreat has quit [Remote host closed the connection]
rejoicetreat has joined #openwrt-devel
goliath has joined #openwrt-devel
dangole has joined #openwrt-devel
Borromini has joined #openwrt-devel
rua has quit [Ping timeout: 480 seconds]
rua has joined #openwrt-devel
jlsalvador has quit [Remote host closed the connection]
Borromini has quit [Ping timeout: 480 seconds]
jlsalvador has joined #openwrt-devel
rua has quit [Ping timeout: 480 seconds]
abiliomarques has quit [Ping timeout: 480 seconds]
<stintel>
that's what I hoped to reach eventually, but kicking off already with my commit from a couple of weeks ago
<dangole>
stintel: yes, funny, I also wasn't aware of that one. and yes, i do believe this is a good idea because the amount of duplication and arbitrariness hurts.
<dangole>
stintel: and then, once we gave that vfat partition a uniform size, we can try to get rid of it altogether ;)
<dangole>
stintel: I
<stintel>
dangole: at least it's somewhat back on some radars ;)
<stintel>
I've actively commented on that PR, but I guess 3 years is too long to remember :P
<stintel>
wooot, odroid booting again
<stintel>
downgraded from 5.10 to 5.4 and is fine now
<stintel>
went from 4.19 -> 5.10
<stintel>
maybe did something wrong there
<stintel>
at least I now have a working interim step
<mangix>
stintel: since your build environment is special, do you build with CONFIG_ALL ?
<stintel>
mangix: only when doing big changes like gcc10
goliath has quit [Quit: SIGSEGV]
rua has quit [Remote host closed the connection]
rua has joined #openwrt-devel
Rentong has joined #openwrt-devel
Rentong has quit [Remote host closed the connection]
shibboleth has quit [Quit: shibboleth]
dangole has quit [Remote host closed the connection]
dangole has joined #openwrt-devel
jlsalvador has quit [Read error: No route to host]
jlsalvador has joined #openwrt-devel
philipp64 has quit [Quit: philipp64]
<stintel>
hmmm, the odroid c2 config had gcc 7, could it be that kernel 5.10 didn't boot because of too old gcc?