<Znullptr>
anyone know offhand how to fix? i know several people have built this configuration ( ipq807x-5.15 ) recently
goliath has quit [Quit: SIGSEGV]
GNUmoon has quit [Remote host closed the connection]
GNUmoon has joined #openwrt-devel
<Znullptr>
this build system has a problem with multi core builds, it will continually fail for things that you wouldn't think would be affected by an asynchronous build elsewhere ... it goes further an now nss-eip-firmware /ifpp.bin is missing / fails a stat and it's stuck there, i've tried multiple times w/ -j1
Tapper has joined #openwrt-devel
srslypascal is now known as Guest2275
srslypascal has joined #openwrt-devel
Guest2275 has quit [Ping timeout: 480 seconds]
Tapper has quit [Ping timeout: 480 seconds]
guerby__ has quit [Read error: Connection reset by peer]
tizbac has quit [Remote host closed the connection]
tizbac has joined #openwrt-devel
<Grommish>
The x86_64 tree doesn't seem to enable gcc w/ PIE (CONFIG_GCC_DEFAULT_PIE) abilities by default.. Is this intentional?
<Grommish>
I enabled PIE on the x86_64 rust-lang toolchain because I assumed it was enabled, but it doesn't compile if gcc doesn't know what to do about it.
<Grommish>
So, do I disable PIE for the rust toolchain, or was this just never enabled by accident?
<Znullptr>
changed to another machine and distro , same problem
minimal has quit [Quit: Leaving]
mattytap__ has joined #openwrt-devel
mattytap_ has quit [Remote host closed the connection]
mattytap__ has quit [Read error: No route to host]
mattytap__ has joined #openwrt-devel
Strykar has quit [Remote host closed the connection]
Strykar has joined #openwrt-devel
gladiac has joined #openwrt-devel
valku has quit [Quit: valku]
mattytap has joined #openwrt-devel
mattytap__ has quit [Ping timeout: 480 seconds]
rua has quit [Quit: Leaving.]
cbeznea has joined #openwrt-devel
ekathva has joined #openwrt-devel
ekathva_ has joined #openwrt-devel
ekathva__ has joined #openwrt-devel
ekathva has quit [Ping timeout: 480 seconds]
ekathva_ has quit [Ping timeout: 480 seconds]
awgh_ has quit [Quit: eschaton immanetized.]
awgh has joined #openwrt-devel
ecloud has quit [Ping timeout: 480 seconds]
Misanthropos has joined #openwrt-devel
ecloud has joined #openwrt-devel
Tapper has joined #openwrt-devel
goliath has joined #openwrt-devel
robimarko has joined #openwrt-devel
<robimarko>
Znullptr: This is not the place for asking about out of tree stuff
<robimarko>
And no, NSS-DRV and ECM dont work on 5.15
<robimarko>
Thats being worked on
jlsalvador has quit [Quit: jlsalvador]
Misanthropos has quit [Ping timeout: 480 seconds]
danitool has joined #openwrt-devel
Tapper has quit [Ping timeout: 480 seconds]
ekathva_ has joined #openwrt-devel
danitool has quit [Quit: Cubum autem in duos cubos, aut quadratoquadratum in duos quadratoquadratos]
<f00b4r0>
"ubus call network.interface dump" does not report IP addresses set manually, is this expected?
ekathva__ has quit [Ping timeout: 480 seconds]
<dwfreed>
f00b4r0: I would imagine so, because you're asking for netifd's state
<f00b4r0>
ok, makes sense. Means I need to use something other than /lib/functions/network.sh for something generic then
rua has joined #openwrt-devel
ekathva__ has joined #openwrt-devel
ekathva_ has quit [Ping timeout: 480 seconds]
danitool has joined #openwrt-devel
rua has quit [Quit: Leaving.]
Tapper has joined #openwrt-devel
l-fy has joined #openwrt-devel
<l-fy>
Hello. I'm trying to build yate package out of the sources. And i will need a bit of help.
ekathva_ has joined #openwrt-devel
ekathva has joined #openwrt-devel
ekathva_ has quit [Read error: Connection reset by peer]
ekathva__ has quit [Ping timeout: 480 seconds]
Tapper has quit [Read error: Connection reset by peer]
Tapper has joined #openwrt-devel
ekathva_ has joined #openwrt-devel
rua has joined #openwrt-devel
ekathva has quit [Ping timeout: 480 seconds]
ekathva__ has joined #openwrt-devel
svanheule has quit [Quit: svanheule]
ekathva_ has quit [Ping timeout: 480 seconds]
svanheule has joined #openwrt-devel
ekathva_ has joined #openwrt-devel
ekathva__ has quit [Read error: Connection reset by peer]
ekathva__ has joined #openwrt-devel
rua has quit [Quit: Leaving.]
ekathva_ has quit [Ping timeout: 480 seconds]
Tapper1 has joined #openwrt-devel
Tapper has quit [Read error: Connection reset by peer]
ekathva_ has joined #openwrt-devel
ekathva__ has quit [Read error: Connection reset by peer]
rua has joined #openwrt-devel
rua has quit [Remote host closed the connection]
bluew has quit [Quit: Leaving]
rua has joined #openwrt-devel
Tapper1 has quit [Ping timeout: 480 seconds]
svanheule has quit [Quit: svanheule]
svanheule has joined #openwrt-devel
robimarko_ has joined #openwrt-devel
robimarko has quit [Ping timeout: 480 seconds]
T-Bone has joined #openwrt-devel
f00b4r0 has quit [Read error: Connection reset by peer]
rua has quit [Quit: Leaving.]
rua has joined #openwrt-devel
SamantazFox has quit [Remote host closed the connection]
SamantazFox has joined #openwrt-devel
cyrozap has quit [Quit: Client quit]
cyrozap has joined #openwrt-devel
valku has joined #openwrt-devel
rua has quit [Quit: Leaving.]
dangole has joined #openwrt-devel
Tapper has joined #openwrt-devel
al has quit [Ping timeout: 480 seconds]
<hanetzer>
stintel: yooooo, good job on getting the eap615-wall into the tree :)
<stintel>
thans
<stintel>
thanks*
<hanetzer>
I was just about to rebase my branch against master and had conflicts in the dts file, its what alerted me to the fact it happened :)
<hanetzer>
that said, how long until a new target shows up in the 'releases' section of downloads? another point release (so 21.02.3-ish)?
rua has joined #openwrt-devel
al has joined #openwrt-devel
<stintel>
probably
<hanetzer>
so, what's the protocol on packaging for devices with device specific firmwares? As in, they have an additional mcu or similar to control a dohickey with upgradable firmware (think like, some stm mcu to control fans or the like)
ekathva__ has joined #openwrt-devel
ekathva_ has quit [Ping timeout: 480 seconds]
<Znullptr>
robimarko_: I'd think most of the development is out-of-tree until it's not, where is the correct place?
ekathva__ has quit [Read error: Connection reset by peer]
ekathva__ has joined #openwrt-devel
mattytap_ has joined #openwrt-devel
mattytap has quit [Read error: Connection reset by peer]
jlsalvador has joined #openwrt-devel
<robimarko_>
Znullptr: Forum, but I see you already asked there
rua has quit [Quit: Leaving.]
mattytap__ has joined #openwrt-devel
<karlp>
hanetzer: just say it's for a "radio" then it's fine :)
<hanetzer>
karlp: lmao
<karlp>
"it's an externally accessible PUF device using broad spectrum EM emissions"
mattytap_ has quit [Read error: No route to host]
mattytap_ has joined #openwrt-devel
mattytap__ has quit [Read error: Connection reset by peer]
<jow>
hanetzer: make a firmware package and add it to the devices PACAKGES list
<jow>
make sure the firmware blobs you package have a license allowing redistribution
mattytap__ has joined #openwrt-devel
<hanetzer>
jow: yeah, not sure on that.
rua has joined #openwrt-devel
mattytap_ has quit [Ping timeout: 480 seconds]
Tapper has quit [Ping timeout: 480 seconds]
dangole has quit [Remote host closed the connection]
ekathva_ has quit [Remote host closed the connection]
ekathva__ has quit [Ping timeout: 480 seconds]
ekathva has quit [Quit: Leaving]
Tapper has joined #openwrt-devel
srslypascal is now known as Guest2343
srslypascal has joined #openwrt-devel
Guest2343 has quit [Ping timeout: 480 seconds]
srslypascal has quit [Remote host closed the connection]
srslypascal has joined #openwrt-devel
Misanthropos has joined #openwrt-devel
Strykar has quit [Ping timeout: 480 seconds]
dwfreed is now known as Guest2345
Guest2345 is now known as dwfreed
srslypascal is now known as Guest2346
srslypascal has joined #openwrt-devel
Guest2346 has quit [Ping timeout: 480 seconds]
srslypascal has quit [Quit: Leaving]
srslypascal has joined #openwrt-devel
hexa- has quit [Quit: WeeChat 3.3]
hexa- has joined #openwrt-devel
Ansuel has joined #openwrt-devel
<Ansuel>
robimarko: stupid question i never understood why a partition change would require uart flash or something like that. can't we create a compatible image and then use that image to flash the correct one ?
<dwfreed>
self-rewrites easily get messy
<Ansuel>
so we don't trust writing the firmware from a running system?
<slh>
the idea in this case would be a one-step/ (mostly-)one-way migration from the rather limited vendor partitioning to something using the vast amounts of unpartitioned flash left dormant by the vendor
<dwfreed>
slh: sounds like nbg6817
<slh>
dwfreed: Xiaomi ax3600
<slh>
and ax9000
<slh>
~19 MB, from a 256 MB NAND flash, of which the last 128 MB are left unused (as Xiaomi's redmi variants of the same devices only come with 128 MB NAND flash)
<robimarko_>
Ansuel: Well, off course you can have a "intermediate" image
<robimarko_>
But its not gonna be autogenerated by OpenWrt
<robimarko_>
And you gotta make sure to flash that into the first rootfs so that sysupgrade can be used
<robimarko_>
I just think that calling for trouble with people who have no idea what they are doing
<robimarko_>
You saw the amount of people who willingly flashed random QSDK builds and messed their partition layouts
<robimarko_>
Hm, though in theory you could flash the rootfs UBI like now
<robimarko_>
As long as it would fit in the first rootfs and then the rootfs_data would auto expand based on first OpenWrt boot to the full rootfs size
<robimarko_>
And buildbot images are always gonna fit
goliath has quit [Quit: SIGSEGV]
<robimarko_>
So thats a viable way of flashing from stock FW
<robimarko_>
Though, I dont think that UBI will like it since there would be an existing UBI with data, I dont think it would overwrite that
<Ansuel>
something to explore for sure...
<Ansuel>
this is only for ax9000 right ?
<robimarko_>
Nope
<robimarko_>
AX3600 as well
<robimarko_>
AX6 as well
<robimarko_>
They all use the same partition scheme
<robimarko_>
Where you have 2 rootfs partitions and one large overlay one
<robimarko_>
So kernel and squashfs go into the rootfs partitions but overlay will be used for the RW overlay
<robimarko_>
But since the dual-booting is not implemented in the bootloader
<robimarko_>
But rather they depend on the kernel changing the rootfs to boot from if it fails mounting
<robimarko_>
Then it makes no sense to be stuck with ~20MB of rootfs
robimarko_ has quit [Quit: Leaving]
robimarko has joined #openwrt-devel
GNUmoon has quit [Ping timeout: 480 seconds]
<Ansuel>
so in short we one way is a migration image or some hack with ubi or just user uart
<robimarko>
Yeah
<Ansuel>
my concern is that an user already has to follow ""tons"" of step to install openwrt so i think improving it is a good idea...
<Ansuel>
i mean we can totally create a dummy image one time and just make it part of the installation project
<slh>
the migration image is probably an easier approach, but to be honest, 19 MB isn't that little either <-- no urgency involved
<robimarko>
Ansuel: Well, the difficulty of installing on these devices is Xiaomis fault
<robimarko>
They are actively trying to prevent installing anythnig
<robimarko>
Not to mention that european AX9000-s appear to all come with secure boot
<robimarko>
How would a migration image even work?
<slh>
the Dynalink DL-WRX36 could be a nice alternative, but also secure boot enabled - and while you can tftpboot it from serial console, it's unclear if you can set an alternative boot command (as new default) for booting from NAND
<robimarko>
In theory you could add a step to sysupgrade to ubiformat the new rootfs+rootfs1+overlay partitions before it does its thing
<robimarko>
slh: Yeah, that one looks interesting due to its price
<robimarko>
But its still more expensive than AX6/3600
<robimarko>
And its US only
<slh>
yeah, 69 EUR and ipq8072a with 1 GB RAM...
srslypascal is now known as Guest2350
srslypascal has joined #openwrt-devel
<slh>
robimarko: it's also selling on ebay.de
<robimarko>
slh: AX6/3600 is IPQ8071A and 512MB of RAM
<robimarko>
Oh, there were none in EU last time I checked
<hurricos>
Ansuel: Usually the old firmware has no idea how to repartition for the new firmware. The one way I've dealt with this has been to add a copy-pastable script to the COMPAT_MESSAGE, which goes into the sysupgrade file
<hurricos>
err
<hurricos>
Yeah, what I said is still relevant. Conversation took a turn towards initial flashing process and I thought I was way off
<robimarko>
slh: Thanks, I might as well order one for that price
<robimarko>
It looks to be Askey rebrand
<robimarko>
hurricos: Yes, thats correct
<robimarko>
There is no way of dealing with changed partition table
<slh>
even cheaper than the going rate for an ax3600, I've been circling that offer for many weeks already - but the big question is about booting from NAND
<hurricos>
it's a little odd. I'd really love if we made a way to officially pack arbitrary executables into sysupgrade files, but for obvious reasons that isn't a great idea
<robimarko>
hurricos: Well, actually you could have a image with both the old partitions and the new one
<robimarko>
As they can overlap
<robimarko>
Then you can use sysupgrade
<robimarko>
In the same fashion that we remove custom UBI volumes from vendors
<robimarko>
But just use it to ubiformat and then it could sysupgrade like usual on the "new" partition
<robimarko>
slh: Yeah, especially since the one guy who asked about it on the forum newer replied if that works
<slh>
yep
Guest2350 has quit [Ping timeout: 480 seconds]
<robimarko>
The HW is unbeatable for that price
<robimarko>
IPQ8072A with 1G of RAM and even a 2.5G port
<robimarko>
In the US they are 99USD all the time
<slh>
btw. how close can ipq8072a/ ipq8074a (as in ax9000) get to routing 1 GBit/s (or beyond) wirespeed (without nss)? the ax3600/ ipq8071a get's around 600 MBit/s
<robimarko>
I havent actually tested
<robimarko>
But it should be around 700-ish
<robimarko>
Its mostly capped due to the shit networking driver
<slh>
yeah, the usual story with QCA... :(
<robimarko>
As it only has one queue and thus NAPI threaded doesnt help
<robimarko>
You are basically stuck due to one core being hogged with IRQ-s
<robimarko>
BTW, they are proudly still using QSDK 11.0, at least its CSU1 editin
<robimarko>
On the Dynalink I mean
<robimarko>
Its a pure Askey rebrand, the DoC is even issued by Askey
<slh>
not quite, rax120v2 is ipq8074a with 4x4 2.4 GHz and 8x8 5 GHz
goliath has joined #openwrt-devel
<robimarko>
Yeah, but for what price?
<slh>
a lot
<slh>
(and yes, 5 GBit/s WAN)
<robimarko>
That was my point, AX9000 was the only 200-ish EUR Hawkeye
<robimarko>
Qhora is also cool with 2x 10G
<robimarko>
Recently got it
<robimarko>
The Dynalink FCC pictures are great
<robimarko>
Lots of closeups
<robimarko>
Unlike some other vendors
<robimarko>
Even has a SPI-NOR for U-boot
<robimarko>
Looks to be very well built, decent heatsink
<slh>
wow, I've never seen that high-res FCC images
shibboleth has quit [Quit: shibboleth]
GNUmoon has joined #openwrt-devel
<russell-->
-ENOLINK
<russell-->
oh, nm, i see it
Borromini has quit [Quit: leaving]
robimarko has quit [Ping timeout: 480 seconds]
srslypascal has quit [Quit: Leaving]
<Ansuel>
im reading the askey discussion sad it has gone quite that quick...
srslypascal has joined #openwrt-devel
<slh>
yep, it's a damned interesting device
<Ansuel>
the scary part is the secure boot fuse... they are starting to use it
<Ansuel>
luckly they are not locking uboot access and you can just change the bootcommand to load custom image
<slh>
if I hadn't already bought the ax3600, I probably would have bought it already - it's still continuing to tempt
<Ansuel>
a be stuck...
<Ansuel>
encrypted firmware no way to get the wifi board data
<Ansuel>
unless we find a vulnerability
<Ansuel>
not something expected as it's not xiaomi crap
<mangix>
no E8450 love?
<Ansuel>
mangix news about ath79 dsa?
<mangix>
what news would there be?
<Ansuel>
no idea more ported devices, other testing
<mangix>
The PR is stalled currently. I don't see interest in it. I don't see it being merged. I think it's best if it's split in smaller chunks.
robimarko has joined #openwrt-devel
<slh>
mangix: if the e8450 had been available (on an approach to be supported) when I bought the ax3600 (October 2020), I would have gone with that one - but right now, as I already own the ax3600 (which at least from the on-paper specs is better than the e8450) and having to pay more than the UK customers... the upcoming filogic 830 with wifi6e and quad-core 2+ GHz cores might get dangerous to me, but
<slh>
until then...
<robimarko>
I mean, it all started with AX3600 being like 50-60 EUR
<robimarko>
And then they launched the even cheaper AX6
<robimarko>
There was no competition really
<robimarko>
E8450 came later and for a long time was unobtanium outside of UK
<slh>
QCA just came to market ~2 years earlier with 802.11ax than mediatek - and is still easier to get
cmonroe has joined #openwrt-devel
cmonroe_ has quit [Ping timeout: 480 seconds]
Misanthropos has quit [Ping timeout: 480 seconds]
robimarko has quit [Quit: Leaving]
Ansuel has quit [Quit: Probably my PC crashed or time to sleep.]