jlsalvador has quit [Quit: jlsalvador]
jlsalvador has joined #openwrt-devel
rua has quit [Ping timeout: 480 seconds]
rua has joined #openwrt-devel
nlowe has joined #openwrt-devel
nlowe has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
goliath has quit [Quit: SIGSEGV]
rua has quit [Ping timeout: 480 seconds]
rua has joined #openwrt-devel
<dangole> stintel: pushed 2500base-t support for unifi6lr to master, would be glad if you can do some testing too
fda- has joined #openwrt-devel
fda has quit [Ping timeout: 480 seconds]
rua has quit [Ping timeout: 480 seconds]
rua has joined #openwrt-devel
mangix_ has joined #openwrt-devel
mangix has quit [Ping timeout: 480 seconds]
dangole has quit [Ping timeout: 480 seconds]
lucenera has quit [Quit: The Lounge - https://thelounge.chat]
lucenera has joined #openwrt-devel
<mangix_> rsalvaterra: pretty sure there are other ones that openwrt does not carry
mangix_ has quit []
mangix has joined #openwrt-devel
<mangix> anyway, finally got the ax router
<mangix> goodbye ath10k
<Slimey> hehe
pmelange has joined #openwrt-devel
pmelange has left #openwrt-devel [#openwrt-devel]
valku has quit [Quit: valku]
jlsalvador has quit [Quit: jlsalvador]
jlsalvador has joined #openwrt-devel
nitroshift has joined #openwrt-devel
<neggles> I have shifted all of my openwrt build dirs etc. over to 4x250GB SATA SSDs in a striped zfs pool, and, definitely should've done that sooner
<neggles> everything builds *so much faster* (probably half because the build_dir fits entirely in ARC)
danitool has joined #openwrt-devel
danitool has quit []
rmilecki has joined #openwrt-devel
nlowe has joined #openwrt-devel
Acinonyx has joined #openwrt-devel
<Pepes> mangix: Which one? You don't need to buy a new router each time for new WiFi standards, when you can swap miniPCIe cards in Turris.
nlowe has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
nlowe has joined #openwrt-devel
danitool has joined #openwrt-devel
felix has quit [Remote host closed the connection]
felix has joined #openwrt-devel
goliath has joined #openwrt-devel
ecloud has quit [Ping timeout: 480 seconds]
ecloud has joined #openwrt-devel
cptn3m0 has joined #openwrt-devel
nlowe has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Acinonyx_ has joined #openwrt-devel
nlowe has joined #openwrt-devel
<f00b4r0> is there a preferred way to preset root password with image builder?
Acinonyx has quit [Ping timeout: 480 seconds]
aleksander has joined #openwrt-devel
cptn3m0 has quit [Quit: Page closed]
<mangix> Pepes: ax cards are not cheap
<rsalvaterra> mangix: This is interesting… the generic kconfig disables CONFIG_DEVTMPFS_MOUNT by default. However, some targets enable it (layerscape/{armv7,armv8_64b}, mediatek/mt7622, oxnas, rockchip/armv8).
<rsalvaterra> I wonder if these targets need it at all…
<mangix> and actually in the context of the Omnia, I'd need those duplexer things. 2 antennas to one. I broke both of the originals
<mangix> rsalvaterra: no
<mangix> at least not in the context of openwrt
<Pepes> mangix: Hmm, card itself is not expensive, but the shipping, VAT from the China could be, but there was some bulk order on Turris forum, which could save you some pennies. But in large quantity, it makes sense
<rsalvaterra> In that case, according to the original commit message, the backport shouldn't be needed. We should just disable that kconfig.
<Pepes> mangix: Regarding diplexer, I think I might be able to help you or at least figure out something for you
<stintel> [ 16.883111] mtk_soc_eth 1b100000.ethernet eth0: Link is Up - 2.5Gbps/Full - flow control off
<stintel> U6LR ^
<rsalvaterra> stintel: \o/
<mangix> stintel: nice
<stintel> credit to dangole
<rsalvaterra> Yep, I saw the patches. :)
<stintel> but that thing is so annoying, sysupgrade takes ages due to large NOR flash
<mangix> stintel: slow SPI speed maybe?
<rsalvaterra> Heh. That's actually good, NOR is more durable than NAND. :P
<stintel> [ 15.962776] jffs2_build_filesystem(): erasing all blocks after the end marker...
<stintel> [ 145.023272] done.
<mangix> Pepes: that would be great
<rsalvaterra> stintel: Just two minutes. :P
<stintel> that
<stintel> that's additional to the sysupgrade time
<stintel> in total it's like 5 minutes
<stintel> which is extreme
<mangix> these fancy /dev things are not done by openwrt
<stintel> anyway, now to decide where to put the U6LR with 5GHz enabled only (I have 2.4g AX from 2x EAP615-Wall)
<stintel> probably close to / aimed at the bedroom as that's where I mostly use my laptop :P
<mangix> IIRC it maxes out at 80
<mangix> or 75
<mangix> well, for ramips. I have no idea about mediatek
<rsalvaterra> Maybe it could be increased…?
<mangix> for ramips, the max is a function of the clock
<mangix> 880/10 MHz or something
<mangix> hmmm I think the divisor is higher
nlowe has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<nitroshift> mangix, if / when you have time to revisit transmission please let me know
<nitroshift> morning
nlowe has joined #openwrt-devel
<mangix> MediaTek PHYs (MEDIATEK_GE_PHY) [N/m/y/?] (NEW)
<mangix> someone broke something
pmelange has joined #openwrt-devel
pmelange has left #openwrt-devel [#openwrt-devel]
\x has quit [Ping timeout: 480 seconds]
<stintel> context?
<stintel> I'm not seeing that symbol in openwrt.git and not in linux.git
<stintel> someone is playing with 5.15 :)
<mangix> stintel: I'm not actually
<mangix> oh I see
<stintel> well that symbol is not in openwrt.git so there is no patch adding it, and linux.git doesn't contain it
<mangix> local patch
<stintel> in the 5.10 branch
<mangix> yeah it's a backport
<rsalvaterra> mangix: I'm not going to backport the CONFIG_DEVTMPFS_MOUNT patch. Rather, I'm fixing procd in order to mount /dev noexec, since procd creates/populates /dev for us.
<mangix> cool
<mangix> no
<nitroshift> ok, thanks
<mangix> nitroshift: surprising
<nitroshift> mangix, what's surprising?
<mangix> crashed
<nitroshift> same error as mine last days?
<mangix> yeah
<nitroshift> mangix, i tried with latest wolfssl 5.10, error persists
rua has quit [Quit: Leaving.]
<mangix> I'd try reverting wolfssl
<nitroshift> back to 4.8 stable? tried that too
castiel652 has joined #openwrt-devel
<mangix> extremely strange
<f00b4r0> hmm. [ -n "$undefined" ] triggers a busybox shell error when $undefined is undefined, but [ -z "$undefined" ] works in both cases. wth?
<mangix> transmission uses libcurl which uses wolfSSL as well. Maybe the latter introduced the issue
<nitroshift> mangix, if you come up with a fix please let me know, i will test it immediately
<mangix> nitroshift: open up an issue in the packages feed and ping @kareem-wolfssl . Include logread stuff. Also mention https://github.com/openwrt/packages/commit/6786e35ff87c4f72ec5343a9f3815842367b3c84#diff-d1290258a553f20590b337cf6bd6446879e65e6c070b661bd82e17a5d220ed95
<nitroshift> mangix, will do
<nitroshift> thanks
<mangix> that commit was tested with 4.8.1
<mangix> strange
<neggles> what is the purpose of the "pinctrl-names" property anyway
<neggles> i've never seen it set to something other than "default"
<f00b4r0> is it expected that one cannot rename a network device using "config device; option ifname 'eth0'; option name 'myname'"?
<mangix> fun question: how do you forward ipv6 with luci?
<mangix> *port forward
<stintel> tell your ISP to stop being schmuks and demand PD, then you don't need port forwarding ¯\_(ツ)_/¯
<f00b4r0> god the lack of documentation for config/network or netifd is killing me
<Habbie> the netifd design document is good but way too short
<f00b4r0> it doesn't tell me anything I need to know to _use_ the thing ;P
<Habbie> true :)
<f00b4r0> mangix: custom rule, luci won't help you there
<Habbie> i usually mess around in luci to see what it does in uci
<f00b4r0> Habbie: heh. There's apparently no option to rename devices in luci, so I suspect that's a clue it can't be done
<Habbie> luci doesn't expose all
<Habbie> oh you just said that too
rua has joined #openwrt-devel
dangole has joined #openwrt-devel
mirko has quit [Ping timeout: 480 seconds]
<rsalvaterra> I wonder if this would allow us to remove split-gso from cake…
<neggles> f00b4r0: that should be how that works
<f00b4r0> neggles: network device rename?
yrrips- has joined #openwrt-devel
<neggles> f00b4r0: yeah
<neggles> though what are you trying to achieve
<f00b4r0> renaming eth0 to some other name
<neggles> eth0 will always be there and always be eth0
<f00b4r0> ah. bummer.
<neggles> you can change the name of `lan` or `wan` or `some_vlan_number` on it
<neggles> and you could technically rename it via some Shenanigans that would require a custom image
<f00b4r0> it's easy to rename netdevs on "standard" linux, so I guessed it could be done here too.
<f00b4r0> s/guessed/hoped/ :)
<neggles> systemd udev does make it rather easy
<f00b4r0> exactly
<neggles> i am not sure what we use? but it is not that
<neggles> because systemd has no place in a friggin' router
<f00b4r0> sure not
<f00b4r0> though you don't need systemd to do device renames
<f00b4r0> anyway, thanks, now I know it's a dead end
<neggles> give it six months and you'll need systemd to use udev...
<neggles> why do you want to rename it?
<f00b4r0> neggles: sure hope not ;P
<rsalvaterra> neggles: I'd say that depends on the size of the router… not in an embedded system, for sure. :)
<neggles> rsalvaterra: okay, no place in a router running openwrt :P
<rsalvaterra> Fair enough. ;)
<neggles> f00b4r0: oh no that's not doom and gloom, it's facts :(
<stintel> SD card on my M300 has plenty of space for systemd ¯\_(ツ)_/¯
* stintel hides
<neggles> you could always create a bridge/lan device and add a single port to it
<f00b4r0> for particular shenanigans. Making different hardware present an "homogenous" view to sysadmin
<f00b4r0> neggles: i figured that too, but that seems rather overkill
<neggles> stintel: just because you *can* doesn't mean you *should*
<rsalvaterra> stintel: Just install Ubuntu on it, then. :P
* rsalvaterra runs
<f00b4r0> and I'm not sure the overhead is desirable either :P
<f00b4r0> stintel: lol
<neggles> I don't know that there would be much overhead on a single-port bridge
<stintel> rsalvaterra: you're the worst, systemd I can live with, but ubuntu, really?
<neggles> *distant snapd noises*
<stintel> *puke*
* neggles screams and brandishes a cross
<rsalvaterra> I use Ubuntu (MATE). Works For Me™. :)
yrrips has quit [Ping timeout: 480 seconds]
<neggles> I use ubuntu more than I use any other linux distro for all the usual reasons ("I can google things and someone else has probably already fixed it") - but my cloud-init has a script that obliterates every last remnant of snapd, apt-mark holds it, and installs a pin file setting it to -999
<rsalvaterra> With Compiz. And wobbly windows. Because of course. xD
<neggles> aaaaand tbh i've started just installing straight debian instead
<stintel> oh dear
<stintel> OpenWrt on embedded, Gentoo on anything else
<neggles> ^ not just gentoo, musl gentoo
<stintel> because everything else is getting much like macOS: outdated soft/libs, and the OS decides how you do things
<f00b4r0> devuan ftw :
<f00b4r0> :)
<rsalvaterra> I used Gentoo for about 7 years, or so… before Ubuntu. I like Debian, but the UI needs tons of polish (which Ubuntu does).
<stintel> hardened musl gentoo on servers/hypervisors/VMs, glibc gentoo on workstation / laptop
<stintel> and on my HiFive Unmatched because no musl support for RISC-V
<neggles> if I had to use a linux desktop as my primary i'd probably end up on kde neon or something approximating that on arch
<neggles> but my dayjob involves far too much windows
<stintel> I'm about to "order" a Thinkpad T14s with corp managed Fedora to replace the piece of shit macbook/macOS combo
* rsalvaterra 's dayjob involves too much macOS.
<neggles> my dayjob also involves too much macos because i am the only guy in the company (small company) that knows how anything mac works
<neggles> so definitely do not have time to be screwing around with gentoo or even arch :P
<stintel> and when I'm doing OpenWrt related stuff for day job I'm using my own gentoo workstation anyway
<rsalvaterra> neggles: I only know how to use macOS when I open the terminal. The rest is a mystery. :P
<mangix> rsalvaterra: you seen the compiz style gnome extensions?
<rsalvaterra> mangix: Gnome died for me after 2.x. It's horribly bloated.
<neggles> rsalvaterra: 1. `brew update`; 2. wait 5-57 minutes
<stintel> brew ... another total piece of crap
<f00b4r0> holy cow. busybox shell is driving me nuts
<neggles> yeah i should say, i use ubuntu on most of my linux boxen, but none of them have a gui
<f00b4r0> now it errors on '[ "$var" ]' with $var unset
<neggles> f00b4r0: ash is a fickle beast at times
<f00b4r0> that's a polite way to say it's a piece of s***
<neggles> hey be nice
<neggles> it's very smol
<f00b4r0> true
<neggles> you would want `[ -z "$var" ]`
<stintel> good idea to use path where lots of installers also drop their crap (ok, macOS doesn't need an installer, but unfortunately every other software company ignores that), then does not recommend to change the path
<rsalvaterra> neggles: Even my parents use Ubuntu. There hasn't been a machine running Windows here since about 10 years ago. :)
<karlp> which is what you _should_ be doing anyway, even in bash :)
<f00b4r0> neggles: I initially used `[ -n "$var" ]` but that didn't work either
<stintel> ugh, I'm gonna close this window for a while because ranting about OSes will kill my producitivty
<neggles> hehe
<neggles> fair
<rsalvaterra> xD
<neggles> lets go back to complaining about ash then
<f00b4r0> but it doesn't always fail
<neggles> f00b4r0: context?
<f00b4r0> which is completely crazy
<rsalvaterra> Should be 100 % POSIX, no?
<f00b4r0> $LANMAC may be unset
<f00b4r0> line 13 fails randomly
<neggles> [ -z "$macaddr" ] || uci set ...
<f00b4r0> as I said, i first used [ -n "$macaddr" ] && uci set
<neggles> yeah
<f00b4r0> that worked/failed randomly
<neggles> -n is not a logical NOT on -z
<f00b4r0> ha
<neggles> except, that's what i thought, if you quote it then -z won't return 1
<neggles> hm
<neggles> wait no i'm stupid
<f00b4r0> no it works
<f00b4r0> let's see how long it does ;)
<neggles> `VAR=; [ -z "$VAR" ] || echo butts` = no "butts"
<f00b4r0> it baffles me why -n or just [ "$var" ] does not (always)
<rsalvaterra> mangix: Nice, but doesn't change the fact that it's GNOME 3.x… :P
<neggles> f00b4r0: -n will return true on an empty string
<f00b4r0> neggles: just to be clear
<neggles> or
\x has joined #openwrt-devel
<neggles> gah! this stuff always messes up my head
<f00b4r0> the problem I'm facing here is I'm running my script set -e
<f00b4r0> and _randomly_ (apparently); the _test itself_ is exiting with an error
<neggles> then you'll want to do an if [] so it doesn't trip the -e
<f00b4r0> yeah but it shouldn't trip in the first place, due to being a friggin test ;P
<neggles> a test is still a command
<f00b4r0> the command is valid though
<neggles> if the line as a whole doesn't return 0
<neggles> it'll fail out
<neggles> but there's some weird quirk -n has in posix sh that i can't remember
<f00b4r0> -z seems to work more reliably
<f00b4r0> I wish I understood why
<neggles> yeah, `[ -z "$var" ] && echo "Empty" || echo "Not empty"`
<neggles> i think -n doesn't like being fed <null> rather than ""
yrrips- is now known as yrrips
<f00b4r0> which is exactly why I'm quoting the variable
<neggles> f00b4r0: okay so from my own brief check just now
<neggles> `[ -n "$UNSET_VAR" ] && echo true || echo false` will succeed / return 0 because of the "echo false" at the end succeeding
<neggles> but if you pull the `|| echo false` off the end, it returns 1
<f00b4r0> oh
<f00b4r0> oh of course
<neggles> but when you do it with `[ -z "$UNSET_VAR"] || do_thing_if_not_null`
<f00b4r0> doh. Now I feel stupid :)
<f00b4r0> yeah I get it
<neggles> either the test returns 0, or the do_thing does
<f00b4r0> yup
dangole has quit [Remote host closed the connection]
<neggles> that's the annoying gotcha and why everyone uses -z
dangole has joined #openwrt-devel
<f00b4r0> got it now. Well, lesson learnt for sure!
<f00b4r0> thanks :)
<neggles> ain't `sh` grand
<f00b4r0> it's mighty :)
<neggles> it would be nice if busybox supported [[]]
<f00b4r0> indeed
<neggles> ugh
<neggles> I cannot get the UART on this ipq8064 AP to work
robimarko has joined #openwrt-devel
<robimarko> neggles: which one?
<neggles> that was eerie
<neggles> robimarko: heh it's not supported yet
<neggles> sophos APX530, it's got a few Weird things going on in the OEM DT
<robimarko> So, like UART doesnt work at all or?
<neggles> it took me a while to work out which gsbi uart it was actually using, but it's gsbi4
<neggles> on standard pins
<neggles> but yeah, i get Starting kernel ... then nothing
<robimarko> You gotta utilize earlyprintk then
<robimarko> Luckily the MSM serial is supported, you just gotta set the correct adress
<neggles> heh, it looks like I didn't actually try the latest rev of the dtb i've bolted together oop
<neggles> the one in this image is pointed at gsbi2 which is where the bluetooth uart is
<neggles> console is at 0x16340000
<robimarko> Then you can enable early printk in the kernel and bake the cmdline
<robimarko> Cause it could be hanging way before the kernel usually probes the MSM serial driver
<neggles> I think I have earlyprintk turned on
<robimarko> If you are using OpenWrt then you gotta enable it in openwrt menuconfig kernel build options
<robimarko> As it will disable the kernel_menuconfig set symbol
<neggles> right
<neggles> that makes sense. CONFIG_KERNEL_EARLY_PRINTK=y it is
<robimarko> But you also gotta select the debug UART adapter and set the psysical and virtual adress of the port
<robimarko> And then set the earlycon= in the cmdline as well
<neggles> well if nothing else this should let me work out why/where/how it's hanging
<neggles> [ 7.010786] 16340000.serial: ttyMSM0 at MMIO 0x16340000 (irq = 184, base_baud = 115200) is a MSM
<neggles> ^ from oem firmware
<robimarko> Yeah, earlycon=msm_serial_dm,<addr> in the cmdline is required
<neggles> ok, easy
<robimarko> And set the kernel to use the built-in cmdline
<neggles> (or set the cmdline in u-boot?)
<robimarko> I wouldnt rely on that
<stintel> oh new stable kernel releases have landed apparently
<stintel> kernel.org not updated yet
<robimarko> As usually the bootipq or whatever cmd usually sets the default bootargs which you cant change
<neggles> it's using a FIT image and passing the `bootargs=`
<neggles> just boots with `bootm 0x44000000#config@2`
<neggles> very civilized of them really
<neggles> is the debug adapter stuff in kernel_menuconfig or openwrt?
<robimarko> kernel_menuconfig
<neggles> thought so, thanks :)
<neggles> and apparently changing CONFIG_KERNEL_EARLY_PRINTK to y in openwrt menuconfig requires a musl rebuild
<neggles> ah, right, kernel headers.
jlsalvador has quit [Quit: jlsalvador]
jlsalvador has joined #openwrt-devel
<neggles> hm.
<rsalvaterra> stintel: On it. For 5.10. :)
<owrt-snap-builds> Build [#409](https://buildbot.openwrt.org/master/images/#builders/48/builds/409) of `bcm47xx/generic` failed.
<neggles> robimarko: ah so, if my ttyMSM0 is at 0x16340000, i'd pass `earlycon=msm_serial_dm,0x16340000` in cmdline?
<neggles> I found the phys/virt addrs for ipq8064 easily enough, though I don't know if those change depending on how the uart/pinctrl is wired
<robimarko> Yeah
<robimarko> The phys/virt also need to match the UART adapter used
<robimarko> So phys for it would be 0x16340000 as well
<neggles> oh interesting
<robimarko> You also need to pass the earlycon=ttyMSM0,115200
<robimarko> Virt address needs to be calculated, I dont know whats it mapped on IPQ8064
<neggles> ah
<robimarko> On IPQ4019 it was just 0xf and then phys
<neggles> I found a pair of addresses that are supposedly accurate for the ipq8064 dev boards, which seem to also use gsbi4 serial
<neggles> most of these things do
<neggles> so `ubi.mtd=rootfs loglevel=8 console=ttyMSM0,115200 earlycon=msm_serial_dm,0x16340000 earlycon=ttyMSM0,115200` ?
<robimarko> GSBI4 is the most common for sure
<robimarko> Yeah, that should work
<robimarko> Nope
<robimarko> Actually, the earlycon=ttyMSM0,115200 needs to be earlyprink=ttyMSM0,115200
<neggles> ah
<neggles> robimarko: Success!
<neggles> ...well sort of
<neggles> ah wait yeah alright heh
<neggles> it helps when you point the serial port at the right address in the dtb
<neggles> earlycon worked then I lost it at regular console :P
<robimarko> Yeah, it can break the regular console
<robimarko> As it avoids the driver init basically
<neggles> yeah, this is my fault though
<neggles> 12490000.serial: ttyMSM0 at MMIO 0x12490000
<robimarko> Haha, so wrong stdout
<neggles> ttyMSM0 should be at 0x16340000
<robimarko> Or alias
<neggles> h-uh, device tree alias is pointing to the right spot
<neggles> oh
<neggles> right, the bluetooth UART on gsbi2 is getting probed before the console one
<neggles> that explains why the oem firmware uses the "qcom,msm-hsuart-v13" for the BT uart
<neggles> driver gets probed later
<robimarko> But that shouldnt matter at all
<robimarko> Is the bootloader maybe passing the wront console=?
<robimarko> Cause I dont know what has higher priority, DT or cmdline
<neggles> robimarko: bootloader cmdline is identical to dt one
<neggles> and i have serial0 pointed at gsbi4_serial which is the console dev
<neggles> oh wait
<neggles> console=ttyMSM0,115200
<neggles> and ttyMSM0 is gsbi2
<neggles> do I need to pass console=ttyMSM1?
<robimarko> Looks like it
<robimarko> Looks like kernel uses cmdline if available
<neggles> hmm... can i use a devicetree alias in console=?
<neggles> i suspect no
<robimarko> Dont know what has higher priority
nlowe has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
nlowe has joined #openwrt-devel
fda- has quit [Ping timeout: 480 seconds]
<neggles> robimarko: okay so it's apparently just decided that whatever the first msm_serial device it probes is, that one's the console
<neggles> which is problematic when it probes gsbi2_serial first, *then* gsbi4_serial
<neggles> so i think for now I will just turn off the bluetooth uart
<robimarko> Hmm, that is not supposed to happen really
<neggles> yeah, something's not right
<neggles> there's two different uart drivers in the OEM fw, gsbi2_serial is using the other one which comes up as ttyHS0 and gets probed about 0.25s after msm_serial
<neggles> i wonder if this is why
<neggles> robimarko: disabling it worked :D
<neggles> until it hung after mounting the ubifs https://www.toptal.com/developers/hastebin/lowemuqiqo but eh details
<neggles> and i'm missing a bunch of other stuff but
fda has joined #openwrt-devel
rua has quit [Quit: Leaving.]
rua has joined #openwrt-devel
<robimarko> The HS UART is supposed to be 4 wire as far as I know, and it has quite a lot of bandwith
<robimarko> So they usually use it for bluetooth
fda- has joined #openwrt-devel
fda has quit [Ping timeout: 480 seconds]
robimarko has quit [Quit: Page closed]
KB1SPH has quit [Ping timeout: 480 seconds]
fda has joined #openwrt-devel
KB1SPH has joined #openwrt-devel
fda- has quit [Ping timeout: 480 seconds]
nitroshift has quit [Quit: Gone that way --->]
nlowe has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
rua1 has joined #openwrt-devel
rua has quit [Quit: Leaving.]
<rmilecki> ok, guys, I spent last 2 hours debugging boot process
<rmilecki> what the hell starts /sbin/mount_root ?
<rmilecki> i thought it's /etc/rc.d/S10boot
<rmilecki> but it actually gets executed EARLIER than S10boot
<stintel> package/base-files/files/lib/preinit/80_mount_root: mount_root
<rmilecki> oh
<rmilecki> ...
<rmilecki> great
<rmilecki> thank you stintel
<stintel> yw :)
minimal has joined #openwrt-devel
valku has joined #openwrt-devel
Forst has quit [Quit: Goodbye]
Forst has joined #openwrt-devel
Forst has quit [Quit: Goodbye]
Forst has joined #openwrt-devel
fda- has joined #openwrt-devel
<rsalvaterra> Done. :)
fda has quit [Ping timeout: 480 seconds]
<hurricos> oh man, I missed the whole OS fight
<stintel> round 2: fight!
mattytap_ has joined #openwrt-devel
mattytap has quit [Ping timeout: 480 seconds]
<hurricos> S
<hurricos> ... so, for what it's worth: I've moved to Fedora for both server and desktop use
<stintel> nice
<hurricos> a combination of bleeding-edge and stable has always sat well with me. I also support a community of non-technical users and am starting to play around with Fedora Kinoite
<hurricos> it also helps that I need to know Red Hat for work :^)
<rsalvaterra> hurricos: Well, we can start another one, say… vim vs emacs? :P
<hurricos> and while RHEL8 has dropped support for LSI2008
* rsalvaterra uses nano and doesn't care.
<hurricos> Fedora 35 still supports it
<hurricos> I use $EDITOR
<hurricos> I'm an emacs guy except when I already know where the file I'm editing is
nlowe has joined #openwrt-devel
aleksander has quit [Quit: Leaving]
<stintel> cool
<stintel> but I'm way past silent :D
<svanheule> :P
castiel652 has quit [Read error: Connection reset by peer]
<svanheule> it has a Realtek SoC though, so maybe it will run OpenWrt one day
fda has joined #openwrt-devel
fda- has quit [Ping timeout: 480 seconds]
fda- has joined #openwrt-devel
Larhzu has quit [Quit: leaving]
fda has quit [Ping timeout: 480 seconds]
Larhzu has joined #openwrt-devel
fda has joined #openwrt-devel
fda- has quit [Ping timeout: 480 seconds]
<Slimey> lol
<Slimey> yeah never trust those plastic junk anchors, adtran supplies the metal ones shown but bigger since those waps weight a ton and are basically a giant heat sink
<Slimey> but i try to avoid walking under them just in case ;)
<rmilecki> nbd: i've rootfs_data on bcm4908 almost fully working, but I'm dealing with one last issue
<rmilecki> I use /lib/preinit/75_rootfs_prepare to call "ubimkvol /dev/ubi0 -n 20 -N rootfs_data" (if it doesn't exist yet)
<rmilecki> the problem is: [ 43.563490] mount_root: failed to mount -t ubifs /dev/ubi0_20 /tmp/overlay: Invalid argument
<rmilecki> it's cuased by missing /dev/ubi0_20 (it doesn't seem to get created automatically that early)
<rmilecki> nbd: if I reboot, then /dev/ubi0_20 exists and mount_root works fine
jlsalvador has quit [Quit: jlsalvador]
<rmilecki> I use /lib/preinit/75_rootfs_prepare as "rootfs_data" UBI volume needs to exist before "mount_root" kicks in
<rmilecki> (validation can happen after "mount_root" mounts it)
<rmilecki> is there a trick to create /dev/ubi0_20 that early manually? without procd which (as I believe) handles it later
jlsalvador has joined #openwrt-devel
<jow> rmilecki: mknod?
<rmilecki> ah, i was looking for "mkdev" command
<jow> or try if you can use /etc/hotplug.d/hotplug-preinit.json
stintel[m] has left #openwrt-devel [#openwrt-devel]
<stintel> LOL
<stintel> I gave that leave command more than 24h ago
stintel[m] has joined #openwrt-devel
<jow> unsuccessfully, it appears
<stintel> no no, I joined again
<stintel> I couldn't speak
<stintel> and I still can't 😂
<rmilecki> i've a working rootfs!!! =)
<rmilecki> thanks jow!
rua1 has quit [Ping timeout: 480 seconds]
rua has joined #openwrt-devel
minimal has quit []
nlowe has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<f00b4r0> Slimey: these anchors are definitely not suitable for drywall. Anyone knowing their left from their right hand should know that ;)
<Slimey> lol
pmelange has joined #openwrt-devel
Borromini has joined #openwrt-devel
mattytap has joined #openwrt-devel
mattytap_ has quit [Ping timeout: 480 seconds]
mrkiko has joined #openwrt-devel
<mrkiko> Hello all! Does anyone know if the MVEBU GL-MV1000 has kernel size limits? rsalvaterra ?
srslypascal is now known as Guest10411
srslypascal has joined #openwrt-devel
<rsalvaterra> No idea… :/
bluew has joined #openwrt-devel
Guest10411 has quit [Ping timeout: 480 seconds]
<rsalvaterra> WTF, cake has diffserv*8*? o_O
<hurricos> yeah :D
<rsalvaterra> I was casually reading the code and stumbled on the diffserv8 matrix. :P
<mrkiko> rsalvaterra: thanks
<Habbie> lol https://www.youtube.com/watch?v=U6ppbNUzSlY - TP Link Archer AXE200 turning antennas Video 1
zatwai has quit [Quit: ZNC 1.8.2+deb2+b1 - https://znc.in]
zatwai has joined #openwrt-devel
<Habbie> (pretty cool really)
swegener has quit [Remote host closed the connection]
swegener has joined #openwrt-devel
<dwfreed> would be interesting to see the patches for that functionality
<Habbie> yep
<dwfreed> presumably it operates on some kind of RSSI triangulation based on individual antenna reception
<Habbie> could they get away with keeping this closed?
<Habbie> i suspect they could
<dwfreed> what's hostapd's license
<slh> the first question would probably be if that's actually doing anything functional - or if it's more for show to its gamer audience
<Habbie> slh, i did get the impression antenna orientation can matter
<Habbie> slh, which doesn't mean this is useful, of course
<dwfreed> slh: right, if the antenna is just a vertical and all that is moving is the plastic, it's probably useless
<slh> dwfreed: BSD
<hauke> it only has 4 antennas so more low end
<dwfreed> slh: oof
<hauke> or it has multiple other internal antennas in addition
<dwfreed> then yeah, probably won't get this in a GPL dump
<hauke> doing beamforming is probably less expensive compared to haveing motors
<hauke> <ou can adjust the beam with beamforming much faster
<hauke> but it does not look so cool
<Habbie> ack
<dwfreed> Habbie: antanna orientation matters insofar as radiation pattern and and polarization are optimal for your environment
<rsalvaterra> It looks cool, but I can't imagine it not being noisy and distracting.
<slh> and propne to breaking down the line
<Habbie> rsalvaterra, you mean entertaining and cool
<Habbie> needs more RGB though
<rsalvaterra> Habbie: You already have lolcat. :P
<Habbie> :)
<dwfreed> Habbie: north of 10m frequencies, radiators are generally vertical wires, which results in an omnidirectional donut-shaped radiation pattern; beamforming basically uses principles of constructive and destructive interference, and the ability to adjust the phase of the produced signal to convert the omnidirectional radiation into a more directional "beam" which can have greater strength than the
<dwfreed> original radiations on their own
<mangix> rsalvaterra: nvim
<Habbie> dwfreed, ack
<Habbie> dwfreed, i knew like 15% of that :)
<Habbie> but, wouldn't these motors move those vertical wires?
<dwfreed> it seems like they're just rotating the plastic side to side
<Habbie> i got the impression it had two elbows
<dwfreed> if it's angling up and down, yeah, that can help
<dwfreed> but the side to side is definitely not providing any value
<Habbie> got it
<slh> I just wonder how long the pigtails will survive that rotating, I mean rf signals are difficult to beging with
<dwfreed> well, the side to side kind of helps when you're not straight vertical
<philipp64> no one else is seeing CI/CD failures that are unrelated to their PR's?
<Pepes> philipp64: I do sometimes. Usually it is about cryptodev in x64
<philipp64> Pepes: mine was for various failures (x86_64, i386_pentium-mmx, aarch64_cortex-a53) and seems to be a packager issue:
<philipp64> * pkg_run_script: Internal error: perlbase-i18n has a NULL tmp_unpack_dir.
<philipp64> which I don't understand...
<philipp64> Oh, also arm_cortex-a15_neon-vfpv4...
<philipp64> Anyone out there running an IP-PBX on their Openwrt firewall?
pmelange1 has joined #openwrt-devel
pmelange has quit [Ping timeout: 480 seconds]
pmelange has joined #openwrt-devel
<owrt-snap-builds> Build [#404](https://buildbot.openwrt.org/master/images/#builders/32/builds/404) of `omap/generic` failed.
<Pepes> philipp64: Yep, I noticed them too sometimes while updating git package. It is weird, but I noticed that only on CI, so it is not a big issue for me, though.
<philipp64> It would be nice if CI/CD didn't have FP/FN's, but... I've yet to encounter one that didn't. So I should ignore them?
pmelange1 has quit [Ping timeout: 480 seconds]
<philipp64> Who owns CI/CD these days?
rmilecki has quit [Ping timeout: 480 seconds]
dangole has quit [Remote host closed the connection]
Tapper has joined #openwrt-devel
dangole has joined #openwrt-devel
pmelange has left #openwrt-devel [#openwrt-devel]
Borromini has quit [Quit: Lost terminal]
rsalvaterra has quit [Quit: rsalvaterra]
Tapper has quit [Read error: No route to host]
rsalvaterra has joined #openwrt-devel
Tapper has joined #openwrt-devel
<neggles> ahh okay, the HS UART is 4-pin, so i do actually need to use that
<neggles> not sure it's got mainline drivers hmm