embargo has joined #openwrt-devel
valku has quit [Quit: valku]
megabro has quit [Remote host closed the connection]
* russell-- recalls when someone (maybe ubiquiti) gave him u-boot source that left out the source file or function that did the critical thing
Tusker has joined #openwrt-devel
dangole has quit [Quit: Leaving]
<blocktrron> stintel: not sure what this is about, but i have this older source provided: https://github.com/blocktrron/u6-lr-gpl
<blocktrron> Most of the interesting stuff is contained inside their "ubntapp" blob, which is not included in the GPL tarball
<neggles> it's a bit rude of them to literally just dump `build_dir` and call it good
<neggles> not surprising, but rude
minimal has quit []
Slimey has quit [Read error: Connection reset by peer]
Slimey has joined #openwrt-devel
fda- has joined #openwrt-devel
fda has quit [Ping timeout: 480 seconds]
indy has quit []
Slimey has quit [Read error: Connection reset by peer]
indy has joined #openwrt-devel
indy has quit [Ping timeout: 480 seconds]
indy_ has joined #openwrt-devel
victhor has quit [Ping timeout: 480 seconds]
strobo has joined #openwrt-devel
strobo_ has quit [Ping timeout: 480 seconds]
fda has joined #openwrt-devel
fda- has quit [Ping timeout: 480 seconds]
Tapper has joined #openwrt-devel
Andi_ has quit [Ping timeout: 480 seconds]
Andi_ has joined #openwrt-devel
fda- has joined #openwrt-devel
<Tapper> Her's a blog post I found.
<Tapper> my thoughts concerning the recently aborted OpenSSL 3 migration, the future of the OpenSSL project
<Tapper> I post this because I spotted a email on the ML about it.
fda has quit [Ping timeout: 480 seconds]
danitool has quit [Ping timeout: 480 seconds]
Tapper has quit [Quit: Tapper]
nitroshift has joined #openwrt-devel
rmilecki has joined #openwrt-devel
dedeckeh has joined #openwrt-devel
castiel652 has joined #openwrt-devel
goliath has joined #openwrt-devel
indy_ is now known as indy
Tapper has joined #openwrt-devel
<Tapper> qosify is crasshing again
<Tapper> Tue Nov 9 07:39:43 2021 daemon.info procd: Instance qosify::instance1 s in a crash loop 6 crashes,
<Tapper> Tue Nov 9 07:10:03 2021 daemon.notice procd: /etc/rc.d/S19qosify: Command failed: Request timed out
<Tapper> This is with latest master
<mangix> Tapper: the libressl thing is interesting, but not relevant to OpenWrt.
<mangix> The latter will stay on 1.1.1 for as long as possible AFAIK
<Tapper> mangix OK mate I was just posting because some was asking to make the change on the ML. I don't know mutch about the dif between them TBH
<mangix> both are terrible. just in different ways
<Tapper> lol
<mangix> libressl is less terrible though
Grommish has joined #openwrt-devel
pmelange has joined #openwrt-devel
danitool has joined #openwrt-devel
pmelange has left #openwrt-devel [#openwrt-devel]
<dhewg> the recent libre/openssl talk was just about the build host library, and not the target library
pmelange has joined #openwrt-devel
pmelange has left #openwrt-devel [#openwrt-devel]
owrt-2102-builds has quit [Quit: buildmaster reconfigured: bot disconnecting]
owrt-2102-builds has joined #openwrt-devel
owrt-1907-builds has quit [Quit: buildmaster reconfigured: bot disconnecting]
owrt-1907-builds has joined #openwrt-devel
owrt-snap-builds has quit [Quit: buildmaster reconfigured: bot disconnecting]
owrt-snap-builds has joined #openwrt-devel
<owrt-snap-builds> Build [#336](https://buildbot.openwrt.org/master/images/#builders/63/builds/336) of `ath79/tiny` failed.
<owrt-snap-builds> Build [#340](https://buildbot.openwrt.org/master/images/#builders/59/builds/340) of `x86/geode` failed.
<dhewg> Tapper: thanks for that link, interesting read
<Tapper> NP
* enyc meeps
userx has quit [Remote host closed the connection]
<stintel> blocktrron: hoping to get the 2.5GbE PHY to actually do 2.5GbE :)
<neggles> stintel: the U6-LR has a 2.5G PHY?!
<stintel> yes
<stintel> the only reason I bought one is to be help in testing that, I have a multigigabit PoE switch
victhor has joined #openwrt-devel
<SwedeMike> stintel: really? https://store.ui.com/products/unifi-6-long-range-access-point says "(1) GbE RJ45 port"
<SwedeMike> stintel: so this is just something ubnt doesn't enable?
<SwedeMike> stintel: because I have two of those, and a 1/2.5GbE switch, but I haven't even tried them in 2.5GbE ports because of the data sheet
<neggles> why on earth...
<neggles> but yeah it's a marvell 2.5GbE PHY
<neggles> the magnetics are only 1G rated, but that's probably not an issue on short cable runs
<SwedeMike> I'll try it out now (their software)
<neggles> SwedeMike: it almost certainly won't work with the OEM firmware
<neggles> it'll be configuring the PHY for 1G max speed
<SwedeMike> ah
<SwedeMike> ok, then no matter :)
<SwedeMike> neggles: what do you mean by "magnetics"?
<PaulFertser> SwedeMike: Ethernet transformer
<neggles> ethernet transformer yeah
<SwedeMike> a component between the port and the PHY IC?
<neggles> yes
<SwedeMike> is this the PoE part?
<neggles> its job is twofold
<PaulFertser> Sometimes it's integrated in the socket ("magjack"), sometimes it's a distinct (usually black) thing nearby.
<neggles> 1. it maintains isolation between the PHY and the ethernet cable so you don't get weird ground loops and voltages
<PaulFertser> Needed for all Ethernet devices, not just PoE.
<neggles> 2. PoE power comes from the center taps of the transformers
<neggles> paul mostly beat me to it :P
<SwedeMike> ah, I think I've seen these on block diagram, just didn't know what it was called.
<neggles> blob:https://imgur.com/813334b2-96dd-416a-b474-140b45e2ce40
<neggles> oop
<neggles> big black blob bottom right
<SwedeMike> interesting that they didn't make it support 2.5GbE all the way, considering the specs it kind of screams for 2.5GbE support
<neggles> suspect they were just planning to use the same PHY chip on U6-LR/U6-Pro/U6-Mesh initially
<neggles> then the MTK-based U6-Pro/U6-Mesh got canned because, well, they sucked, and didn't have 2.5G either
<neggles> AIUI they're being reworked with QCA SoCs
<SwedeMike> I never did understand the differentiation between U6-LR, U6-Pro etc, it seems very confusing market segmentation
<SwedeMike> and they're selling 2.5GbE switches but barely have any 2.5GbE client devices at all
<neggles> U6-LR and U6-Lite's dirty little secret is the same as all the other MT7622 WiFi 6 devices' - no 802.11ax on 2.4Ghz
<SwedeMike> I remember the U6-LR early access hw being different frmo the U6-LR actual shipping hw. Friend of mine bought the EA and it had a different radio, from what I remember
<neggles> yeah, that was a more minor redesign
<SwedeMike> does the MT7622 even have forwarding performance to do 2.5GbE even if it has such a phy?
<neggles> yeah, dual-core A53, it'd be fine
<neggles> U6-Pro was just U6-LR with 2x2 802.11ax on 2.4GHz, iirc
Andi_ has quit [Ping timeout: 480 seconds]
Andi_ has joined #openwrt-devel
<SwedeMike> ok, I only have had experience with MT7621, and without accelerator it was anemic forwarding speed
<neggles> they are worlds apart. mt7621 is an old, slow, dual-core quad-thread 800MHz MIPS
<SwedeMike> ah
<neggles> would be nice if mediatek hadn't made the model numbers so close.
<neggles> from what i've heard, the respun U6-Pro will be a quad-core IPQsomethingoranother with 4x4:4 802.11ax on both bands and 2.5G - but take that with a *huge* grain of salt
<stintel> even if it doesn't do full 2.5, I'm sure it can do more than 1GbE
<neggles> throughtput-wise, yeah
robimarko has joined #openwrt-devel
<SwedeMike> I'm looking at the MT7622A block diagram and it does seem to be quite powerful indeed
<robimarko> stintel: Whats the Aquantia PHY model inside of the LR?
<SwedeMike> nice assortment of ports
<neggles> just a damn shame it's only 802.11n 2.4GHz
<stintel> neggles: aye
<neggles> SwedeMike: AQR112
<neggles> er, robimarko:, rather
owrt-2102-builds has quit [Quit: buildmaster reconfigured: bot disconnecting]
owrt-2102-builds has joined #openwrt-devel
owrt-1907-builds has quit [Quit: buildmaster reconfigured: bot disconnecting]
owrt-1907-builds has joined #openwrt-devel
owrt-snap-builds has quit [Quit: buildmaster reconfigured: bot disconnecting]
owrt-snap-builds has joined #openwrt-devel
<stintel> lol, I have some shortcuts for some sites, bugs.gentoo.org = bgo, that works funny with openwrt things ... bugs.openwrt.org = boo, forum = foo, git = goo :D
<robimarko> neggles: Does it show up on the MDIO bus?
<neggles> not a clue, I only know which PHY it is from the DTS in the tree :P
<stintel> the first problem is that the mtk eth driver doesn't do c45 mdio
<robimarko> Well, you can get away with that
<stintel> see https://git.openwrt.org/?p=openwrt/staging/dangole.git;a=summary
<robimarko> Use the GPIO MDIO instead
<stintel> unfortunately with those changes the mdio doesn't respond anymore
<stintel> robimarko: any example code for that ? :P
<stintel> this stuff is seriously over my head but I'm willing to learn
<robimarko> Nothing special needed, its just the GPIO bitbanging MDIO driver
<robimarko> Its part of the kernel, just follow the bindings
<robimarko> And put the MDIO pins in GPIO pinctrl
<robimarko> It should be able to do C45 that way
<robimarko> You can also drop the C45 compatible, for me whenever I used it the kernel couldnt probe the PHY at all on IPQ SoC-s which has HW C45
<robimarko> I assume that the FW for AQR is uploaded by the bootloader here?
<nbd> Tapper: which openwrt version did you use when qosify crashed?
dangole has joined #openwrt-devel
rua has quit [Quit: Leaving.]
<neggles> it appears that u-boot has AQR112 support
Andi_ has quit [Read error: Connection reset by peer]
<robimarko> Yeah, U-boot has a lot of AQR PHY-s
<robimarko> Mostly due to vendors using it to upload the FW instead of in Linux
<Namidairo> SwedeMike: nobody runs the A version though, that's more of a multimedia chipset
<Namidairo> or rather general purpose
<neggles> wellllll
<Namidairo> don't typically need audio
<neggles> i found explicit references to configuring the U6LR AQR and
<neggles> '// for U6LR aqr112c' - it is a 112C, apparently
<Namidairo> they probably want the BT
<neggles> well that's naughty. the MDIO driver has a reference to "ubnt_mt7622_part.h" which is *not* present in this tree
<neggles> UBNT up to their usual """GPL compliance"""
<robimarko> Classic UBNT, all of the important stuff somehow gets left out
Ironalchemy has joined #openwrt-devel
<robimarko> The 112C should be SW compatible, as far as I know its the cost reduced model
Ironalchemy has quit [Remote host closed the connection]
<neggles> compact, it's smaller and has less interface options
<robimarko> Dont have the datasheet though, requested most of the AQR datasheets but havent got them yet
<neggles> psst, ubiquiti, GPL compliance requires you to provide code *that actually compiles*
<neggles> yeah. marvell are gigantic dicks about handing over datasheets.
<robimarko> Got the AQR113/4/5 datasheets for whatever reason
<robimarko> They are annoying as you gotta request everything, I mean I have an NDA
<neggles> I've been trying to get a copy of whatever the latest-and-presumably-last version of the octeon II/III SDK is
<robimarko> Got the FW errata as well, but no FW images
Ironalchemy has joined #openwrt-devel
Ironalchemy has quit [Remote host closed the connection]
<robimarko> I think they gave up on the Octeon MIPS line as soon as they bought Cavium
<neggles> they did, but they *also* took down the SDKs
<neggles> so all i've got is the old one hurricos dug up
<neggles> which is ver 5.1 - ver 5.4 would be nice since that's what ubiq use to build EdgeOS ~2.0.9
<Habbie> aparcar[m] merged my metadata generation patch for the packages CI yesterday; a user noticed a problem in it in https://github.com/openwrt/packages/pull/17103
<neggles> happy to sign an NDA if they want... c'mon, guys, MIPS octeon is a dead product line, why are you being so cagey
<Habbie> can somebody have a look and merge it, so the user in 17103 can get on with their work? :)
<robimarko> neggles: Yeah, all they provide now is a toolchain
<robimarko> And 4.14 kernel tree
<neggles> the most annoying part is the toolchain was updated semi-recently, so the SDK must have been as well
<neggles> ...i'd been misreading that as 4.4, which is what EdgeOS is on - 4.4.79 - 4.14 is more useful
dangole has quit [Remote host closed the connection]
<robimarko> Its 4.14
userx has joined #openwrt-devel
<neggles> yeah i've been to the repo quiite a few times and misread it every time... woops
<Tapper> nbd latest master. SNAPSHOT r18061
<robimarko> stintel: Do you have any info on the U6-Pro? Cause its cheaper then the LR
<nbd> Tapper: what platform are you using?
Borromini has joined #openwrt-devel
<stintel> robimarko: I do not
<robimarko> I looked at the FCC pictures and they are terrible
<robimarko> There is 2 and from like a meter with terrible resolution
<robimarko> I see that more and more vendors are doing it that way now so you cant know whats inside
<stintel> robimarko: as I mentioned earlier, only got the U6-LR to do 2.5GbE testing
<robimarko> Thats what I am also interested, whether it has the AQR PHY as well
Borromini has quit []
<userx> Hello, how can I install package (add files) to staging_dir/target-<arch>_musl/usr? I need it for build dependencies since I see that this path is used in PYTHONPATH variable.
<userx> In particular I'm interested in staging_dir/target-x86_64_musl/usr/lib/python3.9/site-packages. For example, I took python-twisted. I see this package installed to staging_dir/target-x86_64_musl/root-x86/usr/lib/python3.9/site-packages
* stintel prints a label for the U6LR TTL pinout
<stintel> gonna be less annoying next time :)
<karlp> yah, I'm putting a label printer on the christmas wishing list I think :)
<stintel> I already label all my power bricks and even most cables that come with devices
<karlp> little concerned about thermal printer durability though,
<neggles> robimarko: the U6-Pro that has been in the EA store / thru early FCC approval is not what will actually make it out to retail.
<robimarko> So they are playing that game again
<neggles> not playing any games really, they just realized that another MT7622-based device wasn't going to cut it
<neggles> qualcomm stuff inbound instead
<neggles> it got some *really bad* feedback from testers, so it has been yeeted out the window
<stintel> booo qca
<stintel> not buying anything qca based anymore
<neggles> you're not wrong, but mediatek don't have a quad-core with dual 4x4 AX radios (let alone an 8x8 radio and 4x4 radio), soooo...
<Tapper> nbd ipq806x
<neggles> you can expect the U6-Pro to be essentially the same hardware as a TP-Link EAP660 HD
<stintel> 8x8 was coming I believe
<robimarko> So its gonna be using IPQ807x then
<neggles> most likely, yes
<robimarko> Well, its the only SoC that has dual band AX
<neggles> unless you use PCIe radios
<neggles> but, $$$
<stintel> I have this amazing ipq807x based device with 10GbE 802.3bt uplink
<robimarko> Yeah, that costs way more
<stintel> but try getting sources from Huawei
<robimarko> Yeah, I just ignore anything made by Huawei
<stintel> it has 8x8 5G and 4x4 2.4G
<neggles> that'll be the IPQ8074
<robimarko> So it uses the most beefy radios
<neggles> which will probably show up in the U6-HD
<neggles> assuming that happens
<stintel> know of any other device with those specs? 10GbE 802.3.bt 8x8/4x4 rj45 console port?
<robimarko> Not with BT for sure
<stintel> 802.3at is ok too
<neggles> i mean you only need 802.3bt if you're pulling north of 25W, but
<robimarko> QCA made the IPQ807x series really modular
<robimarko> You just select the actual radios per the specs you want
<stintel> but 8x8 + 4x4 only makes sense with 10GbE uplink imo
<robimarko> Whats the Huawei model?
<neggles> cisco C9130AXI-Z has all that and 5GbE
<stintel> AP7060DN
<neggles> I don't think the move from 5GbE to 10GbE serves any real purpose for any wifi AP
<robimarko> Cause, I am messing with Xiaomi which shares the GPL in the same fashion as Huawei
<stintel> are there u-boot sources for ipq807x ?
<robimarko> But its dirt cheap, hence why I tolerate it
<robimarko> Yeah
<stintel> in that case I can probably just build u-boot and flash it via clamp on the SPI NOR
<robimarko> Yeah, its under the codeaurora
<robimarko> If you know the reference desing they are using then it should be really easy
<neggles> oh and the meraki MR56 which is just a merakified version of the C9130
<stintel> I see, that might be helpful, thanks
<stintel> heeeh nice price that cisco :D
<stintel> the Huawei wasn't cheap either but not *that* expensive
<neggles> they cost about 40% of list price to actually buy.
<nbd> Tapper: please replace your /etc/init.d/qosify on the router with http://nbd.name/qosify
<neggles> no public cisco pricing is real.
<nbd> (this will turn on coredumps)
<nbd> Tapper: then restart qosify
<nbd> Tapper: it should create a .core file in /tmp on the next crash
<robimarko> stintel: For that price it has no competition really
<nbd> Tapper: afterwards, please send me that file
<robimarko> stintel: Cisco/Meraki have their usual pricing, so they will be usefull once the license runs out and you can get them used
<neggles> e.g. sticker price on the C9130AXI-Z here (australia) is $4617AU
<neggles> but I can buy one for $1953, and if I send a single email to our distributor, they'll knock another $500 off
<neggles> (still not worth the money)
<robimarko> Thats still like 3 times the max the HW is worth
<stintel> robimarko: does https://gist.github.com/stintel/c9a010d4f4dcad02479dd7364360abce learn you the reference design? probably not
<neggles> nah, there's a *shitload* of hardware in those ciscos
<Tapper> nbd OK
<neggles> it's a lot more than just an AP
<neggles> but yes, no *person* should buy cisco/aruba wifi APs brand new, you buy them in 3 years once businesses start refreshing them for a tax break
<neggles> with the notable exception of the aruba instant-ON stuff, which is actually reasonably priced and quite good.
<neggles> no licenses either
<robimarko> stintel: Unfortunatelly not as unlike every other vendor, they are not just putting the reference desing in the FIT config
<robimarko> And since they disable kernel bootlog that is out of the question as well
<stintel> got the ap7060dn for EUR540 new 1.5y ago
<stintel> I'd say that beats the Cisco price :)
<neggles> well yeah, but, huawei
<robimarko> But if you can pull the DTB it shouldnt be hard
<neggles> spi_flash_programmer_clip.jpg
<robimarko> neggles: Its not like Cisco is nicer
<robimarko> Just look at the MR33 trap
<Namidairo> the blowing away of efuses
<Namidairo> lol
<robimarko> They will actually trip the secure boot fuse in the newer bootloader
<neggles> hey don't think i'm defending cisco here
<robimarko> If you try to load an unsigned FW
<neggles> it forcibly turns on secure boot *after* you try to load an unsigned firmware?
<neggles> WHY?!
<Namidairo> spite
<neggles> just turn it on from the get-go you assholes
<robimarko> Because "security"
<robimarko> And because Cisco
<robimarko> So, its a d*ck move
<neggles> why would they not just... turn on secure boot?
<neggles> that's just mean
<robimarko> Because its not worth it
<robimarko> Just complicates the production
<robimarko> And they sign their FW anyway
<neggles> if they sign their FW anyway it doesn't complicate production at all
<Namidairo> i wonder what key is loaded in there
<neggles> i am 100% sure cisco could be just using secure boot by default
<Namidairo> or rather, if they are even doing it properly
<neggles> heh
<neggles> maybe it's all zeroes
<Namidairo> ^
<neggles> probably just stuffing it with random bits if they're solely using it as a f&@$-you
<robimarko> I mean, here is the whole saga
<robimarko> If they wanted to do it properly, they would have enabled secure boot and signed the bootloader
<neggles> yeah i vaguely remember being glad i'd left my MR33 in a closet for a year and a half
<robimarko> But it looks like they didnt
<robimarko> And now they are just being mean
<stintel> robimarko: so I just build u-boot for all ipq807x variants, clamp flash trial and error style? :P
Tapper has quit [Read error: Connection reset by peer]
<neggles> stintel: dump the existing flash and go binwalking for DTBs :P
<stintel> oh I have a dump
<robimarko> stintel: You need to figure the reference design firt
<robimarko> And then it should be really hard to build for that reference design
<neggles> if there's an FDT in there somewhere it's easy to rip it out and turn it back into text
<robimarko> And if its NOR you can always easily recover
<neggles> assuming it's not encrypted
<robimarko> Yeah, just pull the DTB
Tapper has joined #openwrt-devel
<stintel> binwalk says there are 56 DTBs :P
<neggles> classic
<neggles> are most of them some ludicrous length?
<stintel> ~5000 bytes
<neggles> well.
<neggles> binwalk --dd='.*' --include='device tree' <image>
<Namidairo> that would be mean, padding with the DTB signature
<neggles> then see which ones `file` reports as being actual dtbs
<nitroshift> _lore_, ping
<neggles> its late here so i better go, but, good luck :P
<neggles> (...and now i want one of those huawei APs...)
<Namidairo> what, the refreshed ax6 pro?
<stintel> ipq807x-hk01
<Namidairo> *ax3 pro
<neggles> nah, AP7060DN
<stintel> and the next says hk02 :P
<neggles> give! me! 8x8!
<stintel> ok so they really made it hard :P
<neggles> stintel: sounds like region code specific DTBs maybe
<stintel> neggles: friend of mine got one off ebay for ~EUR300 iirc
<Namidairo> aren't those the reference board names
<neggles> maybe!
<stintel> I tried to get one too for that price but I think they noticed their mistake
<neggles> stintel: i am in australia so i don't get to have nice things :(
<stintel> otoh, it lacked a bunch of labels compared to mine
<Namidairo> ^
<neggles> any chance i could grab a copy of that flash dump though? i am curious
<stintel> so maybe it was an early model not yet certified for Europe
<Namidairo> e8450's didn't get released here
<stintel> neggles: sure
<neggles> yay!
<robimarko> stintel: Well, HK01 is the most abused model
Tusker has quit [Quit: Time wasted on IRC: 12 hours 32 minutes 58 seconds]
<robimarko> Its the top of the range reference board
<robimarko> But it can be in like 20 configurations
<robimarko> I wonder how the bootloader picks one as it just uses config@1
<robimarko> Usually they will need to pass the actual node
<neggles> probably an fdt command in the bootcmd
<neggles> i've got an ADVA/MRV FSP150-XG304 (marvell bobcat/prestera) that runs an FDT command to disable the front USB port in its bootcmd
<Namidairo> so do ddns-scripts just assume that whomever is configuring them isn't trying to inject commands into uci?
<robimarko> stintel: Any place to get the AP7060DN?
<neggles> taobao probably :P
<robimarko> If they are decently priced, I can horass the boss into buying one for scientific purposes
<stintel> robimarko: got it from a supplier in Belgium
<stintel> might have been a friendly price because I did a project for them once
<robimarko> stintel: I tried googling but there is like only one EU offer
<robimarko> And thats 720 EUR
<stintel> yeah on ebay 728 :/
<Namidairo> because I was looking at a vendor firmware yesterday and they wrote their own ddns ui instead of forking luci-app-ddns
<Namidairo> ...and made the same mistake
<stintel> neggles: pm'd you the nor dump
<Tapper> nbd I did as you said but there is no file and no sing of a crash in the log now. It is not running tho.
<neggles> stintel: got it, thanks :D
<stintel> yw
<Tapper> sign*
<nbd> Tapper: did you restart qosify?
<Tapper> yeah
<nbd> and /etc/init.d/qosify restart works fine without any error message?
<Tapper> root@TappersRouter:~# /etc/init.d/qosify restart
<Tapper> -ash: /etc/init.d/qosify: Permission denied
<neggles> ewwwwwwww this is VxWorks
<stintel> chmod +x it
<Tapper> nbd that mite be because I copped the file on to my router using winscp
<stintel> Tapper: chmod +x /etc/init.d/qosify
<stintel> unix 101 ;P
<neggles> okay so two of these DTBs are way bigger than the others and this has redundant bootloaders
<neggles> so
<Tapper> root@TappersRouter:~# /etc/init.d/qosify restart
<Tapper> Command failed: Request timed out
<Tapper> now for the core file
rua has joined #openwrt-devel
<Tapper> no file in /tmp
<nbd> Tapper: can you send me your build tree .config?
<Tapper> nbd I have my config.buildinfo is that the write one?
<nbd> that one works as well
<stintel> robimarko: does this look right for using gpio-mdio? https://gist.github.com/a09c384b1e3ce8b063c8ca4a8b8f428c
<Namidairo> oh I see what's happened with this vendor firmware
<Namidairo> they're literally one commit behind the one that would have actually sanitised the uci config options
<Namidairo> so close yet so far
<Tapper> nbd If you don't want to have it like that I can paste it for you.
<Tapper> It is a send server.
<Tapper> Same as the old firefox send
<nbd> Tapper: it's fine, i downloaded it
<Tapper> k
<stintel> ah I probably also need to set MDIO_MODE to 1 in GPIO_MODE0
danitool has quit [Quit: Cubum autem in duos cubos, aut quadratoquadratum in duos quadratoquadratos]
<robimarko> stintel: Yeah, you need to switch the pins to GPIO mode
<robimarko> And that should work
<stintel> I'm trying to find out how :P
<robimarko> I assume you need to move the mdc_mdio group
<robimarko> https://git.openwrt.org/?p=openwrt/staging/dangole.git;a=blob;f=target/linux/mediatek/dts/mt7622-ubnt-unifi-6-lr.dtsi;h=6a2941435b9e0f8006477ac8d78c0780be939068;hb=HEAD#l81
<robimarko> Try just removing the group
<nbd> Tapper: try this: /etc/init.d/qosify stop; ulimit -c unlimited; qosify & sleep 1; /etc/init.d/qosify reload
<Tapper> OK
<Tapper> nbd do you want me to paste that all at the same time?
swalker has quit [Ping timeout: 480 seconds]
<_lore_> nitroshift: pong
<nbd> Tapper: no need. just check if there is a .core file now, or if the messages end with "segmentation fault"
<nitroshift> _lore_, i was told to talk to you regarding irq balance for mv88e6xxx
<nitroshift> and / or mvneta
<Tapper> nbd no .core file
<Tapper> root@TappersRouter:~# /etc/init.d/qosify stop; ulimit -c unlimited; qosify & sle
<Tapper> libbpf: elf: section(5) .maps, size 256, link 0, flags 3, type=1
<Tapper> ep 1; /etc/init.d/qosify reload
<Tapper> libbpf: elf: section(4) license, size 4, link 0, flags 3, type=1
<Tapper> libbpf: license of /lib/bpf/qosify-bpf.o is GPL
<Tapper> libbpf: elf: section(6) .BTF, size 5974, link 0, flags 0, type=1
<Tapper> Command failed: Not found
<Tapper> [1]+ Done(2) qosify
<nitroshift> at the moment all interrupts sit on cpu0
<nitroshift> any chance it can use more than one cpu core?
<nitroshift> installing irqbalance package doesn't help either
<_lore_> nitroshift: it depends on the board I guess
<_lore_> e.g. espressobin has only one irq line
<nitroshift> _lore_, i'm talking about linksys wrt3200acm
<nitroshift> that's armada 385
<stintel> nitroshift: o/
<nitroshift> yo stintel o/
<_lore_> nitroshift: if (!pp->neta_armada3700) .. it should be supported
<nitroshift> well, cat /proc/interrupts: https://pastebin.com/nDgQ6hJV
<nitroshift> eth0 sits on cpu0 alone
<nbd> Tapper: is there anything relevant in the last lines of the output of logread?
<nbd> it's really weird that it just exits without any error messages or segfault
<stintel> robimarko: and drop the c45 compatible, use what instead?
<robimarko> You can try with it, and if that fails to probe the PHY just drop it
<_lore_> is the board loaded as neta_armada3700?
<stintel> it fails
<nitroshift> _lore_, no
<robimarko> Then just drop it
<Tapper> nbd no mate.
<robimarko> Kernel can figure if its C45 on its own
<stintel> also, using the mdio tool everything on the mdio-bus all phy-ids show 0x00000000
<_lore_> nitroshift: please check if there is the "marvell,armada-3700-neta" property in the dts
<stintel> which doesn't look good I'd sayu
<Tapper> nbd do you want me to paste all the files I have for qosify.
<robimarko> stintel: Maybe it has a reset GPIO
<robimarko> I wouldnt be surprised if that needs to be deasserted
<Tapper> nbd what paste bin site do you use. Paste bin wants me to log in.
<nbd> Tapper: you could run 'logread | nc termbin.com 9999' and send me the link that it prints
<nitroshift> _lore_, model = "Linksys WRT3200ACM";
<nitroshift> compatible = "linksys,rango", "linksys,armada385", "marvell,armada385",
<nitroshift> "marvell,armada380";
<Tapper> nbd ok
<nitroshift> _lore_, also, the mdio section says compatible = "marvell,mv88e6085";
<robimarko> stintel: Is the PHY visible if you use the HW MDIO but drop the compatible so it will probe it as C22
<robimarko> Just to see the ID
<nitroshift> there's no mention of armada-3700-neta
<_lore_> nitroshift: it seems it should be supported in this case
swalker has joined #openwrt-devel
<nitroshift> _lore_, digging deeped in dts includes, i found marvell,armada-370-neta mentioned in a few places in armada-38x.dtsi
<nitroshift> no armada-3700-neta though
<nbd> Tapper: nothing relevant in there. still no idea why it just quits
<nitroshift> *deeped / deeper
<nbd> Tapper: please run qosify -o; echo $?
<stintel> robimarko: apparently not
<robimarko> Then it really smells like a reset not deasserted
<_lore_> nitroshift: I'll look more into it
<stintel> robimarko: 0x8 has non-zero bmsr and bmcr thouh
<nitroshift> _lore_, thanks
<robimarko> Whats the ID?
<stintel> ID(0x02/0x03): 00000000
<robimarko> Hm, I meant the AQR still has to have the 0x2/0x3 ID populated
<robimarko> Whats in reg 0x1?
<nbd> Tapper: to paste the result, you can also do ( qosify -o; echo $? ) 2>&1 | nc termbin.com 9999
swalker has quit [Ping timeout: 480 seconds]
<stintel> robimarko: how would I check that?
<robimarko> You can use mdio tools for that
<robimarko> Like you did before
<stintel> hmmm
<robimarko> Just add the 0x1 after the PHY address
<robimarko> So phy_addr 0x1
<stintel> wasn't immediately clear from the help text
<robimarko> Yeah, the help text is a mess
<robimarko> Still havent managed to read a MMD using that
<stintel> ahh
<stintel> 0x6148
<stintel> it's displayed in the pastebin
<stintel> 0x1 = BMSR(0x01): 0x6148
<nbd> Tapper: now we're getting somewhere
<Tapper> nbd OK cool. lol
<nbd> Tapper: i'll let you know when i have something to test
<Tapper> nbd what did I fuck up?
<Tapper> OK cool
<stintel> might it be helpful to document those qosify troubleshooting steps ?
<nbd> Tapper: doesn't look like a mistake on your part
<Tapper> mbd O cool. I feel better now lol
<robimarko> stintel: Well, it might a be a ethernet PHY at all
<robimarko> Most of the bits make sense
<robimarko> Though its advertising that it doesnt have extended capability
<robimarko> Ok, if its similar to AQR113 then it doesnt use Clause 22 at all
<robimarko> According to it, all of the standard Clause 22 stuff is actually in MMD1
swalker has joined #openwrt-devel
<stintel> so I switched back to gpio-mdio and have the same result when reading
<stintel> I assume that means the gpio-mdio is working properly
<nbd> Tapper: what llvm version is on your host?
<robimarko> stintel: unfortunatelly I dont have the register docs
<robimarko> As they are a separate doc
<stintel> for the aqr112 ?
<robimarko> I was looking at AQR113 as I had the datasheet for that
<robimarko> Nothing for AQR unfortunately
<robimarko> But they have got to be really similar
<robimarko> And indeed the PHY ID and everything is in MMD1
<robimarko> It says that the device ID is in MMD1.3
<Tapper> llvm is already the newest version (1:10.0-50~exp1).
<robimarko> Vendor ID is in MMD1.2
Slimey has joined #openwrt-devel
<Tapper> nbd does that help?
<nbd> Tapper: ah, i guess that one is too old
<nbd> you can download https://downloads.openwrt.org/snapshots/targets/ipq806x/generic/llvm-bpf-13.0.0.tar.xz and unpack it into your build tree
<Tapper> How to update I am using ubuntu wsl2
<nbd> and change the bpf toolchain option to "Use prebuilt LLVM toolchain"
<Tapper> nbd let me see if i can get a newer build of it in my ubuntu
<nbd> no need to update llvm on your system then
<Tapper> nbd I will get back to you.
<Tapper> nbd thanks
swalker has quit [Remote host closed the connection]
swalker has joined #openwrt-devel
minimal has joined #openwrt-devel
<stintel> oooh
<stintel> > I will be happy to provide you with the GPL files. We can provide you with the software version for which the appliances last held a valid License, if you can provide me with a company name or SN of the appliances I can check what that version was.
aleksander has joined #openwrt-devel
nitroshift has quit [Quit: Gone that way --->]
<Habbie> stintel, remember two weeks ago when i asked you about saving license keys :D
<nbd> i will add a minimum llvm version check soon
<nbd> so that it bails out at build time
<stintel> Habbie: :P
<nbd> instead of producing weird runtime errors
pmelange has joined #openwrt-devel
<stintel> robimarko: I'm lost :P
<stintel> ahh
<stintel> mdio mdio-bus mmd ... seems to return the same stuff as before
<stintel> when not using mmd
<ldir> nbd: Can you tell me what llvm toolchain you're using on macos and where you installed it from please?
castiel652 has quit [Quit: Page closed]
Tapper has quit [Ping timeout: 480 seconds]
<nbd> ldir: i think i installed llvm 13 using brew
<nbd> but the apple toolchain might work as well, not sure
<ldir> ok - it's just that apple's clang can produce ebpf... I did it once... can't remember how?
Tapper has joined #openwrt-devel
<nbd> ldir: took me a while to figure out how to compile kernel ebpf properly. the result is in include/bpf.mk
<ldir> nbd: I'm sure it did! :-) I'll just brew install llvm
<nbd> i think the apple toolchain should behave in the same way as upstream llvm
<nbd> if it supports ebpf properly
<nbd> so you probably don't have to brew install llvm
KGB-0 has joined #openwrt-devel
hexa- has quit [Quit: WeeChat 3.1]
<PaulFertser> Hey ldir. I'm told you are taking care about dnsmasq configuration in OpenWrt. Could you please review my patch? https://patchwork.ozlabs.org/project/openwrt/patch/20210923072845.22602-1-fercerpav@gmail.com/
<Tapper> nbd In Ubuntu I going to try llvm 12
<Tapper> sudo apt install clang-12 --install-suggests
hexa- has joined #openwrt-devel
pmelange has left #openwrt-devel [#openwrt-devel]
Tapper has quit [Read error: Connection reset by peer]
Tapper has joined #openwrt-devel
<Tapper> nbd that's working now.
<nbd> great
<Tapper> nbd I think you should put this in the wiki. I would do it, but my spelling and gramer would not be a good look for openwrt.
<Tapper> lol
<robimarko> stintel: Well I am out of ideas
<stintel> same :)
goliath has quit [Quit: SIGSEGV]
<ldir> PaulFertser: not looked at dnsmasq stuff for a while, however reading the dnsmasq man page (owww my head hurtz) and looking at your change, all looks good to me.
<ldir> if I can remember how to a apply a patch from patchwork I'll apply it :-)
<PaulFertser> ldir: thank you! I'll add the documentation for the option to the wiki.
<PaulFertser> ldir: btw, that man page I improved a bit already https://www.mail-archive.com/dnsmasq-discuss@lists.thekelleys.org.uk/msg15520.html (was merged but no new release was made since then, so the web site shows older variant)
<ldir> PaulFertser: yes, I'm running 2.87test4 + the filter patch - Simon has gone 'off grid' for a bit.
dedeckeh has quit [Remote host closed the connection]
<stintel> ldir: git pw patch apply #
robimarko has quit [Quit: Page closed]
<hurricos> Is there anything similar to `wireless.wifi-device.path` for /etc/config/network?
<hurricos> I'm almost certain "no" from the wiki pages for each
Tapper has quit [Ping timeout: 480 seconds]
<owrt-snap-builds> Build [#300](https://buildbot.openwrt.org/master/images/#builders/71/builds/300) of `bcm4908/generic` failed.
mangix has quit [Remote host closed the connection]
mangix has joined #openwrt-devel
stintel has quit [Ping timeout: 480 seconds]
stintel has joined #openwrt-devel
jlsalvador has quit [Remote host closed the connection]
jlsalvador has joined #openwrt-devel
minimal has quit []
Borromini has joined #openwrt-devel
jlsalvador has quit [Quit: jlsalvador]
jlsalvador has joined #openwrt-devel
<stintel> can'
<stintel> can't repro the issue with Pi Zero 2 on Raspberry Pi OS :(
<stintel> checksums for the 3 firmware files are the same
niyawe has quit [Quit: niyawe]
<dwfreed> stintel: what were you trying to repro? I have a 4 8 GB sitting next to me
<dwfreed> It is still on Pi OS buster, but I could replace it with bullseye easily, as I haven't done anything with it yet
KGB-0 has quit []
KGB-0 has joined #openwrt-devel
dedeckeh has joined #openwrt-devel
dedeckeh has quit [Remote host closed the connection]
arifre has quit [Remote host closed the connection]
userx has quit [Remote host closed the connection]
lmore377 has quit [Quit: No Ping reply in 180 seconds.]
<stintel> dwfreed: Zero 2 locks up on OpenWrt
lmore377 has joined #openwrt-devel
<stintel> it's a new device, not supported yet
<dwfreed> ah, bummer
<dwfreed> I hate how much of raspberry pi is still closed source
<dwfreed> it's better in bullseye, but still not great
goliath has joined #openwrt-devel
<stintel> bummer indeed
<stintel> I'd hoped to replace the zero w that I use as security cam with the zero 2
<stintel> the zero w is at 100% CPU all the time (motion)
<Habbie> the zero 2 really hits a lot of sweet spots
<rsalvaterra> dwfreed: How much of the RPi is actually closed, these days? I thought the last remaining pieces were the GPU and hardware video decode drivers…?
<rsalvaterra> Oh, I remember, that horrible VideoCore blob…
<Slimey> heh
<rsalvaterra> … which basically boots the whole system and kicks the "main" CPU…
<Habbie> is that really different from the closed source BIOS on the average PC or server?
<Habbie> other than it having a separate CPU
<rsalvaterra> Habbie: Yes, completely different.
<rsalvaterra> The BIOS run on the CPU.
<PaulFertser> Current computers no longer have BIOS.
<PaulFertser> Unfortunately, most UEFI implementations are just as shitty.
<PaulFertser> If we consider current Intel CPUs then it's even worse than any videocore code because you can run unsigned code on VC while you can't run unsigned code on the ME (a dedicated CPU in PCH).
<rsalvaterra> s/BIOS/UEFI. Only the smell differs. :P
<PaulFertser> rsalvaterra: not really, BIOS was supposed to be running all the time (DOS syscalling it to do many jobs). While UEFI itself is no longer active once the kernel boots.
<PaulFertser> And Linux was calling into BIOS too (remember APM for power management?) but not often, agreed.
<rsalvaterra> PaulFertser: Uh… what about UEFI Runtime Services…?
<PaulFertser> rsalvaterra: they're no longer active after GRUB transfers control to Linux. IIRC it's called "shutdown services" even.
<PaulFertser> rsalvaterra: I think the only part that gets used is to read/write "nvram variables", probably via SMM handlers.
<rsalvaterra> Hm… good to know. But there's still a bigger elephant in the room in x86…
<rsalvaterra> … SMM.
<PaulFertser> rsalvaterra: I think ME is the biggest.
<rsalvaterra> Hard to choose… ME or SMM…? :)
<PaulFertser> rsalvaterra: you control all of the SMM code and can change it.
<rsalvaterra> Theoretically…
<rsalvaterra> … becuse in practice, that code is part of the firmware.
<rsalvaterra> So, unless you're engineering a computer from scratch…
<PaulFertser> rsalvaterra: I have to admit, I had ExitBootServices() in mind. Runtime services is different thing and it's indeed used for nvram variables modification. But I do not think they normally run in the background.
<PaulFertser> rsalvaterra: coreboot was ported to many COTS devices
<rsalvaterra> Sure, but not yet any of the devices I own, unfortunately. :)
<PaulFertser> And if the board is based on reference design it's probably supported by TianoCore edkII directly. E.g. our Tioga Pass server seems to be booting vanilla "Purley" edkII, and probably not much tweaking is needed to make everything work fully.
<PaulFertser> I understand this all is unhelpful in most cases. Fuck Intel and the others. Only Pine seems to be really caring about the ordinary end users.
<rsalvaterra> It's the reason I drool over the Talos POWER9 machines…
<rsalvaterra> … but they're way out of my budget.
<stintel> if only someone would build them in EU
<rsalvaterra> stintel: Preach it, brother! :)
<stintel> the shipping costs are what is killing it for me
<stintel> and customs fee, import tax
<rsalvaterra> stintel: Lucky you, I get thoroughly trounced by the price of the hardware already. :P
<stintel> well becoming an economic refugee helped my finances :P
<rsalvaterra> When you can get a dual socket EPYC for the same price, you start thinking twice about openness vs performance…
* stintel reverts mac80211 to 5.10 and tries that on the Zero 2
<stintel> I want that thing to work so I can replace the Zero security cam and have an excuse to order another Zero 2 😂
<rsalvaterra> stintel: What's the Wi-Fi hardware on the thingy?
danitool has joined #openwrt-devel
<stintel> another variation of bcm43430
Borromini has quit [Quit: leaving]
<stintel> ooh
<stintel> it's not hanging now
<stintel> not working either, but not hanging is an improvement
<stintel> ow
<stintel> it's working
<stintel> yay
<owrt-snap-builds> Build [#337](https://buildbot.openwrt.org/master/images/#builders/63/builds/337) of `ath79/tiny` completed successfully.
Tapper has joined #openwrt-devel
<owrt-snap-builds> Build [#341](https://buildbot.openwrt.org/master/images/#builders/59/builds/341) of `x86/geode` completed successfully.
owrt-1907-builds has quit [Remote host closed the connection]
owrt-snap-builds has quit [Remote host closed the connection]
owrt-2102-builds has quit [Remote host closed the connection]
owrt-2102-builds has joined #openwrt-devel
owrt-snap-builds has joined #openwrt-devel
owrt-1907-builds has joined #openwrt-devel
<nbd> Tapper: no need to add a wiki entry. the build will now fail with a useful error message if clang is too old
<Tapper> nbd OK good to know.
<Tapper> I just found this script to install the latest clang.
<Tapper> bash -c "$(wget -O - https://apt.llvm.org/llvm.sh)"
<nbd> there's really no need to install a package onto the system. you can simply download the tarball from openwrt.org and unpack it into your build directory
<nbd> that way you get the same version that the snapshot builds use
<Tapper> cant OpenWrt auto do that with out checking for a llvm on the host?
<nbd> well, it only works on linux/x86_64 hosts
<Grommish> stintel: Not ready to tackle this memleak yet? :D
<nbd> but i guess at some point i'll add a script to scripts/
<stintel> Grommish: that's over my head
<Grommish> stintel: *sigh* Mine too, which is why i was pinning my hopes on you :D
<stintel> Grommish: but you should probably have added all maintainers returned by the get_maintainers.pl script and also the ML
<Grommish> stintel: Also beyond me.. I don't expect to hear back from the single, and I'm not on the mailing list.. Meh
Tusker has joined #openwrt-devel
<Grommish> Well, does that mean Octeon targets are going away?
<Grommish> Since none of them can seem to handle 5.10
<stintel> it's just a bug that needs to be fixed ..
<Grommish> Well, yeah :) But aren't they all? You know how slim the dev pool is for the target, and I have nothing practical to offer except obstinance
<Grommish> Anyway, if you think there is anything I can help with, hit me up. I don't mind putting in an OWRT bug report (not that it's needed) but upstream I wouldn't have any idea how, or the knowledge to answer them if they answered
<stintel> try the ML returned by the get_maintainer script
<Grommish> Ok.. CC you again?
<slh> Grommish: Ansuel has been working on kernel v5.15 for ipq806x (WIP PR on github), might be worth looking at for octeon, maybe it's fixed there already
<stintel> Grommish: yes, I'd like to get a response if anyone sends one
<Grommish> slh: Ok.. I'll look, thanks
<stintel> I have not revived the box yet where I have my octeon cards in so can't even test anything myself
<Grommish> Does the ERLite have USB3?
<stintel> Grommish: no idea - I don't own ERlite anymore :P
<Grommish> Ah, i thought you were the one who sounded the original memleak on it :D Apologies!
<stintel> I am
<stintel> but I retired them and gave them away
<stintel> too slow for my uplink
<stintel> I had apu2 main erlite backup router
<stintel> the m300 replaced the apu2 as main router and the apu2 is now the backup
<Grommish> Ah, gotcha
<stintel> so didn't need the ERLs anymore
<stintel> but I have a couple of SNIC10s
<stintel> so I do still have octeon devices, just can't use them atm
goliath has quit [Quit: SIGSEGV]
pmelange has joined #openwrt-devel
pmelange has left #openwrt-devel [#openwrt-devel]
<stintel> ok, mac80211 5.12 seems to break on the Pi Zero 2
<stintel> and my Zero W are all still on a build with mac80211 5.10
<stintel> so good chance they will also break
<stintel> oh dear, that looks painful to bisec
<hauke> stintel: I think someone in the forum reported the same problem
<hauke> there are not many changes in brcmfmac between 5.11 and 5.12
<hauke> stintel: could you try mac80211 5.12 with brcmfmac 5.11?
<hauke> or the otehr way around
valku has joined #openwrt-devel
niyawe has joined #openwrt-devel
<stintel> hauke: how would I do that?
<hauke> stintel: this diff from the kernel should apply more or less: git diff v5.12.19 v5.11.22 -- drivers/net/wireless/broadcom/brcm80211/
lmore377 has quit [Quit: No Ping reply in 180 seconds.]
lmore377 has joined #openwrt-devel
<fda-> dangole: after update avm7320 to uorrent version i noticed some "random: ubusd: uninitialized urandom read (4 bytes read)" and "urandom-seed: Seed file not found (/etc/urandom.seed)". are the messages okay and should be ignored?
dansan has quit [Quit: The C preprocessor is a pathway to many abilities some consider to be unnatural.]
dansan has joined #openwrt-devel
aiyion_ has joined #openwrt-devel
aiyion has quit [Ping timeout: 480 seconds]
<neggles> Grommish: definitely does not have USB3 no
<stintel> forums suck
<stintel> impossible to find anything
<neggles> bad search implementations suck
<neggles> and most forum search implementations are bad
bookworm_ has quit []
bookworm has joined #openwrt-devel
<Tapper> I go back to google and sirch for what I want with the words openwrt forums after it lol
rmilecki has quit [Ping timeout: 480 seconds]
goliath has joined #openwrt-devel
<Grommish> neggles: I didn't think so.. Wonder if it'll have any impact on the ERL if it's enabled, other than just taking up space
<neggles> Grommish: doubt it, there's no XHCI controller in the octeon chip they used, way way way too old
<neggles> it predates USB3 by at least 3 years
<Grommish> neggles: Yeah. there is a PR that wants to enable it by default.. Any good with memleaks? :D
<stintel> that PR is for a way newer Edgerouter than the ELR ?
<stintel> the supported octeon devices have plenty of storage, so enabling things in the kernel config rather than adding a kmod-package to default_packages is the usual way things are done
<neggles> *distant sad SNIC10e noises*
slh has quit [Ping timeout: 480 seconds]
<neggles> my kingdom for a 3mb (compressed, LZMA is fine even iirc) octeon kernel+initrd
<stintel> :D
<stintel> you live in a fantasy world :P
slh64 has quit [Ping timeout: 480 seconds]
<neggles> I will settle for a 3mb kernel image that has *just barely enough features* to mount a ubifs volume on NAND and kexec() into it
<neggles> which... is pretty much the cavium stage1+stage2 setup...
<stintel> gahhh bloody brcmfmac
<neggles> ah yeah, that PR *is* for a much newer ER, the ER-6P
<neggles> which uses a CN7130