<SnarlingFox>
I've got the build system ready to build an image, at the `make menuconfig` stage and unsurprisingly there's no specific device available, what are the steps for adding a new device?
<PaulFertser>
SnarlingFox: usually you take a look at existing commits adding new devices. There you see amendments to target/linux/../image/Makefile , that's where the device list is generated from.
Danct12 has quit [Remote host closed the connection]
<PaulFertser>
SnarlingFox: to force regeneration you can just delete tmp/
<SnarlingFox>
Thanks Paul, I'll take a look into that now, just testing a ipq40xx-generic-zyxel_nbg6617 build now with a couple of extra drivers to see if that solves the missing wireless adaptors (there's 3 radios on this board, two 2x2 for 2.4 Ghz and 5 GHz built into the SoC, and a secondary 4x4 one for backhaul, none of which appeared on the original nbg6617 image)
<SnarlingFox>
Hah, so on your recommendation I found https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=82618062cf7ed6b40d2c52c6f6b96364888ffda6 - and lo and behold it covers the steps I've already worked out by hand myself XD oh well, I know I'm on the right track at least
<PaulFertser>
For wireless you need proper partitioning specified in DT so that the drivers could get their calibration data. Also often times you need to amend the shell script that extracts some part of those. Depending on the target.
<SnarlingFox>
Yeah that's the point I fall flat on my face.
<rsalvaterra>
Hey, guys! Quick question about the BPi R3: is the optional fan PWM-controlled, or does it run at fixed speed?
<rsalvaterra>
(Depending on the temperature, should have made that clear.)
<SnarlingFox>
Jumping in half-cocked here rsalvaterra, if the Banana Pi R3 fan control is software-controlled, it's unlikely OpenWrt is doing that for you now (unless you can find a specific package for it in opkg). You might need to cook something up yourself (and share it with the world whilst you're at it ;))
<rsalvaterra>
Heh. I surely hope you're wrong, but I'm not keeping my hopes up. :)
<SnarlingFox>
You likely just need to know the GPIO the fan is connected to :)
<PaulFertser>
PWM isn't available on just any GPIO.
<rsalvaterra>
Actually, I haven't asked the most important question… how hot does it get in real world usage?
* rsalvaterra
is thinking of getting one for his girlfriend's home, hence the questions.
<rsalvaterra>
I thought of waiting for the BPi R4, but dangole told me it runs *blazing hot*, and that's a big no-no.
* SnarlingFox
pastes "Picard shocked face"
<SnarlingFox>
You're sneaking OpenWrt into your girlfriends place? :O
<stintel>
friends don't let friends run OEM firmware
<stintel>
it's almost always a security hazard
<SnarlingFox>
stintel: XD
<robimarko>
stintel: Nah, OpenSSL 0.9.8 is perfectly fine in 2023
<stintel>
robimarko: ;)
<ukleinek>
Easy solution: Don't have friends :-)
<SnarlingFox>
Well I get that, my partner was like "Why the heck do we need this stupid router you've built?" - it's a fanless Celeron box with OpenWrt on it :D
<stintel>
lol if a fanless celeron was the only thing I have to "explain"
<robimarko>
I am scared to even summarize the value of random AP-s laying around because of OpenWRt
<SnarlingFox>
Oh I'm forever having to "excuse" myself, part of the reason I'm messing with these WSQ50's is they've become a "relationship arguing point" because they keep fucking up
<stintel>
I've a 20U full-depth rack that is almost completely full :P
<SnarlingFox>
robimarko: Be proud, make a fort out of them akin to a pillow fort :D
<SnarlingFox>
Puts a whole new meaning in "security product"
<stintel>
and then there's my office 😂
<robimarko>
SnarlingFox: If you have the WIP code somewhere I can take a look and leave comments
<SnarlingFox>
(The offending modded WSQ50 being the white blob)
<PaulFertser>
SnarlingFox: do you have a specific question about the calibration data?
<stintel>
heh you call that tidy o_O
<SnarlingFox>
robimarko: There's no WIP yet, I'm just trying my first build of OpenWrt firmware _ever_ - fun stuff.
<SnarlingFox>
PaulFertser: Truthfully, I have no idea what I need or how to get it from the original WSQ50 firmware to successfully port it all to OpenWrt. I can stick the tarball of the Linux filesystem on Dropbox alongside the mmcblk dumps though.
<SnarlingFox>
I could also potentially make the serial console remotely accessible as well - but I fear that may be a security risk (appreciate everyone, trust no one, right?)
<PaulFertser>
SnarlingFox: basically, you look at vendor boot log to extract the list of partitions. And there should be one named ART or factory or calibration or something. And you should look inside with hexdump -C or something to see if what looks like ath10k calibration data is at the right offset there. It's likely to match what other vendors using the same SoC used.
<SnarlingFox>
I'm happy to delve deeper into that but I find IRC quite challenging for this kinda thing.
<SnarlingFox>
Off topic: May I ask if there's been discussion over migrating to something like Discord and why people opted to stay with IRC?
<SnarlingFox>
(I could have quite happily shared my screen for example)
<SnarlingFox>
I'm actually scared to hit ctrl+v in IRC because of that very reason :D
* SnarlingFox
has been kicked for ~~flooding~~ being a pleb
<stintel>
discord is proprietary
<stintel>
and is horrible on resource usage
<stintel>
just like any other hipster IRC clone
<SnarlingFox>
stintel: You mean you _too_ don't have 256 GB RAM on your daily driver? :D
<stintel>
I do, actually
<PaulFertser>
And also discord actively abuses their userbase. There're known instances where they banned free software developers "for violating ToS", and yes, their ToS actually prohibit using their service with anything but their own proprietary shit.
<SnarlingFox>
Okay now you're just swinging it around stintel XD
paintenzero has joined #openwrt-devel
<SnarlingFox>
PaulFertser: Ahh okay I didn't relise that, kinda shooting themselves in the foot, they've got a real easy to use platform with lots of handy features so that's a waste :/
<stintel>
on a workstation it's not a big problem, but laptops that are actually portable still max out at 32GB last time I looked
<SnarlingFox>
So what do devs do then when they need to do stuff like pairing up? Zoom or something?
<stintel>
jitsi!
<stintel>
my discord tab is using 243MB RAM
<stintel>
I wonder how much worse it would be if you run the app
<robimarko>
At work we use Google suite, so Meet is often used
<robimarko>
Its still propriatery but at least it just works in a browser
<robimarko>
Had to use Zoom, that thing is utter crap
<stintel>
yeah, it's the one causing the least problems on a linux desktop, in my experience
<stintel>
zoom is absolute garbage
<robimarko>
Teams are somewhat better than Zoom as at least it has web version
<SnarlingFox>
stintel: Currently using the Windows desktop app, circa 400 MB (on a 64 GB RAM system), I've seen it use up to 1.7 GB RAM before when I've been heavily using it but I think it's mainly caches that can be expunged when required
<robimarko>
I like Jitsi though, some clients use it and its great
<stintel>
the client I worked for when covid started was acquired by a german firm, they kinda pushed zoom and holy crap
<stintel>
I had to do a Windows VM with USB PT for the webcam to be able to use it
<stintel>
absolute nightmare
<SnarlingFox>
We use Zoom a lot at work.. it's forever "installing updates" right when you're late to a meeting :D
<robimarko>
I have a no webcam policy so it mostly worked, but then they would release a new version and boom now it wont load in Fedora
<stintel>
ah we did "cafe quarantaine" every friday after work
<stintel>
basically get drunk with colleagues in front of webcam 😂
<stintel>
good times!
<robimarko>
Thats one way to keep spirits high
<tomn>
there is a special place in hell for orgs that disable the web interface for zoom (which works absolutely fine, if it's enabled)
<robimarko>
Well, that is the issue
<robimarko>
It has to be enabled
<stintel>
it didn't use to work fine on a linux desktop, but last I tried is 2y ago or so
<SnarlingFox>
Oh we just did that in our afternoon meetings, half the staff would just have a glass of wine or beer in hand on a Friday :D
<robimarko>
Since 99% of them just use Windows and happily install whatever, "it just works TM"
<SnarlingFox>
(If only to make a point being coerced into turning their webcams on)
<SnarlingFox>
"You want to see me, you get to see _all_ of me, warts and all"
<PaulFertser>
Why not use Telegram? It sucks and server side is proprietary but at least the client is free software and GNU/Linux distros ship it. I'm using it for job but I'm not participating in video calls so no idea if it's stable for that.
<SnarlingFox>
Wouldn't really call Telegram a professional tool although it does fill a need. Same for WhatsApp.
<stintel>
I wish Signal had a non-electron desktop client
<PaulFertser>
What's bad about telegram compared to zoom?
<robimarko>
Same, though Flatpak version has been working great for me
<SnarlingFox>
Zoom, despite its warts, does at least allow me to share desktops with others, I've used it for escorting access to production servers for our developers
<SnarlingFox>
And as much as I find Zoom to be.. "quirky".. it's better than Skype!
<stintel>
ugh, we didn't mention teams yet
<PaulFertser>
SnarlingFox: you can use OBS to stream to twitch or something , it doesn't need to be the same tool you use while calling :)
<stintel>
probably the worst of them all :P
<robimarko>
Luckily it still has web app
<SnarlingFox>
I haven't used Teams yet, I don't ever plan to, our internal IT team trolled everyone on April Fools saying they were swapping everyone from Slack to Teams and some colleagues bought it and kicked up a stink XD
<stintel>
oof, harsh
<SnarlingFox>
I bought the guy in IT a beer, it was hilarious :D
<SnarlingFox>
Okay, firmware and calibration data, how do I do this? :D
<stintel>
hah I started using the discord tab and we went to 370MB
<PaulFertser>
SnarlingFox: 0:ART partition
<PaulFertser>
SnarlingFox: probably just add your device to compex,wpj428
<SnarlingFox>
I'm sorry I don't understand either of those two lines you've posted
<PaulFertser>
SnarlingFox: on line 269 I see vendor firmware defines a partition https://pastebin.com/evng9mx9 . And same partition name is referred to for this set of devices: https://git.openwrt.org/?p=openwrt/openwrt.git;a=blob;f=target/linux/ipq40xx/base-files/etc/hotplug.d/firmware/11-ath10k-caldata;h=1d4fd9cd8f9a3983ac3323ce72153c1dcc17a69a;hb=82618062cf7ed6b40d2c52c6f6b96364888ffda6#l180
<SnarlingFox>
Ahh good, yeah the SPI device I haven't touched yet, I'm guessing we _don't_ touch that and pull that in for the new image
<SnarlingFox>
Sorry, to be clear, we don't touch SPI, we _do_ modify the case statement for that device
<PaulFertser>
SnarlingFox: the calibration data is on SPI NOR flash so you need to touch it to read out from it.
<PaulFertser>
SnarlingFox: define the corresponding sections in the DT.
<SnarlingFox>
There's multiple $FIRMWARE case statements in there though, I don't yet know which would be for mine, would I just append the conditional on the $board case statements for all of them?
<SnarlingFox>
(Not quite sure where $FIRMWARE is defined yet)
<SnarlingFox>
On the original firmware, there's a load of files in /lib/firmware/ that relate to the specific wireless chips (IPQ4019, QCA9984) if relevant
<SnarlingFox>
"define the corresponding sections in the DT" - sorry, how do I go about doing that? Just edit target/linux/ipq40xx/base-files/etc/hotplug.d/firmware/11-ath10k-caldata ?
<PaulFertser>
SnarlingFox: for a new board you need to prepare a new DTS file of course. Describing all the hardware of the target.
<PaulFertser>
like https://git.openwrt.org/?p=openwrt/openwrt.git;a=blob;f=target/linux/ipq40xx/files-4.14/arch/arm/boot/dts/qcom-ipq4018-nbg6617.dts;h=d7f8c5955caee15d373a342b75c8c1947f5b8022;hb=82618062cf7ed6b40d2c52c6f6b96364888ffda6
<SnarlingFox>
Yep, that was touched on yesterday by robimarko and a couple of others but no idea on how to achieve it, checking that link now though
<PaulFertser>
(of course use the current version of the most recently added board for inspiration)
<PaulFertser>
SnarlingFox: that link is what you sent, it's from commit adding support for that Zyxel :)
<SnarlingFox>
That NBG6617 does boot but doesn't mean it's accurate, I think the hope was I could potentially export or generate one somehow from the existing firmware
<SnarlingFox>
Getting into u-boot for example isn't a problem and there's some content in /proc/device-tree/
<PaulFertser>
SnarlingFox: you're supposed to write a new file on your own using other good upstream files for inspiration.
<SnarlingFox>
Ahh okay, wing it basically
<robimarko>
Its making educated guesses, nobody here can tell you what to do exactly to get your board properly described
<SnarlingFox>
Fair, okay I'll take a look at that, I've gotta run some errands now though (recycling run and shopping), thanks both
<SnarlingFox>
One quick note though, the "generic" image I tried to build on the side failed with the following error:
<SnarlingFox>
make -r world: build failed. Please re-run make with -j1 V=s or V=sc for a higher verbosity level to see what's going on
floof58 has quit [reticulum.oftc.net liquid.oftc.net]
enyc has quit [reticulum.oftc.net liquid.oftc.net]
GNUmoon has quit [reticulum.oftc.net liquid.oftc.net]
xback has quit [reticulum.oftc.net liquid.oftc.net]
filimonic has quit [reticulum.oftc.net liquid.oftc.net]
aiyion has quit [reticulum.oftc.net liquid.oftc.net]
rmilecki has quit [reticulum.oftc.net liquid.oftc.net]
schmars[m] has quit [reticulum.oftc.net liquid.oftc.net]
takimata has quit [reticulum.oftc.net liquid.oftc.net]
lucenera has quit [reticulum.oftc.net liquid.oftc.net]
vulpes2[m] has quit [reticulum.oftc.net liquid.oftc.net]
KGB-2 has quit [reticulum.oftc.net liquid.oftc.net]
lemmi has quit [reticulum.oftc.net liquid.oftc.net]
mrkiko has quit [reticulum.oftc.net liquid.oftc.net]
stintel has quit [reticulum.oftc.net liquid.oftc.net]
owrt-images-builds has quit [reticulum.oftc.net liquid.oftc.net]
tmn505 has quit [reticulum.oftc.net liquid.oftc.net]
dhewg has quit [reticulum.oftc.net liquid.oftc.net]
swegener has quit [reticulum.oftc.net liquid.oftc.net]
hauke has quit [reticulum.oftc.net liquid.oftc.net]
blocktrron has quit [reticulum.oftc.net liquid.oftc.net]
nbd has quit [reticulum.oftc.net liquid.oftc.net]
Sagi has quit [reticulum.oftc.net liquid.oftc.net]
Habbie has quit [reticulum.oftc.net liquid.oftc.net]
mirko has quit [reticulum.oftc.net liquid.oftc.net]
rmilecki has joined #openwrt-devel
vulpes2[m] has joined #openwrt-devel
enyc has joined #openwrt-devel
GNUmoon has joined #openwrt-devel
stintel has joined #openwrt-devel
nbd has joined #openwrt-devel
swegener has joined #openwrt-devel
hauke has joined #openwrt-devel
blocktrron has joined #openwrt-devel
Habbie has joined #openwrt-devel
Sagi has joined #openwrt-devel
mirko has joined #openwrt-devel
aiyion has joined #openwrt-devel
floof58 has joined #openwrt-devel
xback has joined #openwrt-devel
filimonic has joined #openwrt-devel
takimata has joined #openwrt-devel
schmars[m] has joined #openwrt-devel
lucenera has joined #openwrt-devel
lemmi has joined #openwrt-devel
KGB-2 has joined #openwrt-devel
mrkiko has joined #openwrt-devel
tmn505 has joined #openwrt-devel
owrt-images-builds has joined #openwrt-devel
dhewg has joined #openwrt-devel
SnarlingFox has quit [reticulum.oftc.net kinetic.oftc.net]
rua has quit [reticulum.oftc.net kinetic.oftc.net]
parazyd has quit [reticulum.oftc.net kinetic.oftc.net]
Shados has quit [reticulum.oftc.net kinetic.oftc.net]
Znevna has quit [reticulum.oftc.net kinetic.oftc.net]
ahf has quit [reticulum.oftc.net kinetic.oftc.net]
\x has quit [reticulum.oftc.net kinetic.oftc.net]
JiiPee has quit [reticulum.oftc.net kinetic.oftc.net]
tom- has quit [reticulum.oftc.net kinetic.oftc.net]
FLD has quit [reticulum.oftc.net kinetic.oftc.net]
Emantor has quit [reticulum.oftc.net kinetic.oftc.net]
Ansuel has quit [reticulum.oftc.net kinetic.oftc.net]
sandberm has quit [reticulum.oftc.net kinetic.oftc.net]
PaulFertser has quit [reticulum.oftc.net kinetic.oftc.net]
slh has quit [reticulum.oftc.net kinetic.oftc.net]
noltari has quit [reticulum.oftc.net kinetic.oftc.net]
rotanid has quit [reticulum.oftc.net kinetic.oftc.net]
djfe has quit [reticulum.oftc.net kinetic.oftc.net]
KanjiMonster has quit [reticulum.oftc.net kinetic.oftc.net]
neocturne has quit [reticulum.oftc.net kinetic.oftc.net]
jow has quit [reticulum.oftc.net kinetic.oftc.net]
rua has joined #openwrt-devel
parazyd has joined #openwrt-devel
FLD has joined #openwrt-devel
Shados has joined #openwrt-devel
Emantor has joined #openwrt-devel
Ansuel has joined #openwrt-devel
PaulFertser has joined #openwrt-devel
sandberm has joined #openwrt-devel
slh has joined #openwrt-devel
noltari has joined #openwrt-devel
ahf has joined #openwrt-devel
\x has joined #openwrt-devel
Znevna has joined #openwrt-devel
rotanid has joined #openwrt-devel
KanjiMonster has joined #openwrt-devel
djfe has joined #openwrt-devel
tom- has joined #openwrt-devel
JiiPee has joined #openwrt-devel
neocturne has joined #openwrt-devel
jow has joined #openwrt-devel
SnarlingFox has joined #openwrt-devel
rsalvaterra has quit [reticulum.oftc.net coulomb.oftc.net]
hitech95 has quit [reticulum.oftc.net coulomb.oftc.net]
f00b4r0 has quit [reticulum.oftc.net coulomb.oftc.net]
robimarko has quit [reticulum.oftc.net coulomb.oftc.net]
EqUaTe has quit [reticulum.oftc.net coulomb.oftc.net]
nixuser has quit [reticulum.oftc.net coulomb.oftc.net]
shoragan has quit [reticulum.oftc.net coulomb.oftc.net]
wille-io has quit [reticulum.oftc.net coulomb.oftc.net]
Obi-Wan has quit [reticulum.oftc.net coulomb.oftc.net]
tomn has quit [reticulum.oftc.net coulomb.oftc.net]
bbezak has quit [reticulum.oftc.net coulomb.oftc.net]
KGB has quit [reticulum.oftc.net coulomb.oftc.net]
slh64 has quit [reticulum.oftc.net coulomb.oftc.net]
mark22k has quit [reticulum.oftc.net coulomb.oftc.net]
xdarklight_ has quit [reticulum.oftc.net coulomb.oftc.net]
quinq has quit [reticulum.oftc.net coulomb.oftc.net]
ldir has quit [reticulum.oftc.net coulomb.oftc.net]
SirLouen has quit [reticulum.oftc.net coulomb.oftc.net]
colo has quit [reticulum.oftc.net coulomb.oftc.net]
_lore_ has quit [reticulum.oftc.net coulomb.oftc.net]
bookworm has quit [reticulum.oftc.net coulomb.oftc.net]
lu_zero has quit [reticulum.oftc.net coulomb.oftc.net]
kabel has quit [reticulum.oftc.net coulomb.oftc.net]
larsc has quit [reticulum.oftc.net coulomb.oftc.net]
SwedeMike has quit [reticulum.oftc.net coulomb.oftc.net]
ukleinek has quit [reticulum.oftc.net coulomb.oftc.net]
ynezz has quit [reticulum.oftc.net coulomb.oftc.net]
embargo has quit [reticulum.oftc.net coulomb.oftc.net]
karlp has quit [reticulum.oftc.net coulomb.oftc.net]
clandmeter has quit [reticulum.oftc.net coulomb.oftc.net]
robimarko has joined #openwrt-devel
hitech95 has joined #openwrt-devel
wille-io has joined #openwrt-devel
bbezak has joined #openwrt-devel
xdarklight_ has joined #openwrt-devel
quinq has joined #openwrt-devel
_lore_ has joined #openwrt-devel
colo has joined #openwrt-devel
clandmeter has joined #openwrt-devel
lu_zero has joined #openwrt-devel
bookworm has joined #openwrt-devel
embargo has joined #openwrt-devel
ukleinek has joined #openwrt-devel
karlp has joined #openwrt-devel
ynezz has joined #openwrt-devel
kabel has joined #openwrt-devel
SwedeMike has joined #openwrt-devel
larsc has joined #openwrt-devel
rsalvaterra has joined #openwrt-devel
f00b4r0 has joined #openwrt-devel
nixuser has joined #openwrt-devel
shoragan has joined #openwrt-devel
EqUaTe has joined #openwrt-devel
tomn has joined #openwrt-devel
mark22k has joined #openwrt-devel
SirLouen has joined #openwrt-devel
KGB has joined #openwrt-devel
Obi-Wan has joined #openwrt-devel
ldir has joined #openwrt-devel
slh64 has joined #openwrt-devel
schmars[m] has quit [Ping timeout: 480 seconds]
<PaulFertser>
SnarlingFox: you need to produce a single threaded log to see the error.
lu_zero has quit [reticulum.oftc.net coulomb.oftc.net]
hitech95 has quit [reticulum.oftc.net coulomb.oftc.net]
SwedeMike has quit [reticulum.oftc.net coulomb.oftc.net]
larsc has quit [reticulum.oftc.net coulomb.oftc.net]
SirLouen has quit [reticulum.oftc.net coulomb.oftc.net]
EqUaTe has quit [reticulum.oftc.net coulomb.oftc.net]
ldir has quit [reticulum.oftc.net coulomb.oftc.net]
tomn has quit [reticulum.oftc.net coulomb.oftc.net]
kabel has quit [reticulum.oftc.net coulomb.oftc.net]
Obi-Wan has quit [reticulum.oftc.net coulomb.oftc.net]
f00b4r0 has quit [reticulum.oftc.net coulomb.oftc.net]
robimarko has quit [reticulum.oftc.net coulomb.oftc.net]
rsalvaterra has quit [reticulum.oftc.net coulomb.oftc.net]
nixuser has quit [reticulum.oftc.net coulomb.oftc.net]
karlp has quit [reticulum.oftc.net coulomb.oftc.net]
wille-io has quit [reticulum.oftc.net coulomb.oftc.net]
clandmeter has quit [reticulum.oftc.net coulomb.oftc.net]
ukleinek has quit [reticulum.oftc.net coulomb.oftc.net]
xdarklight_ has quit [reticulum.oftc.net coulomb.oftc.net]
ynezz has quit [reticulum.oftc.net coulomb.oftc.net]
bookworm has quit [reticulum.oftc.net coulomb.oftc.net]
mark22k has quit [reticulum.oftc.net coulomb.oftc.net]
embargo has quit [reticulum.oftc.net coulomb.oftc.net]
colo has quit [reticulum.oftc.net coulomb.oftc.net]
bbezak has quit [reticulum.oftc.net coulomb.oftc.net]
_lore_ has quit [reticulum.oftc.net coulomb.oftc.net]
slh64 has quit [reticulum.oftc.net coulomb.oftc.net]
KGB has quit [reticulum.oftc.net coulomb.oftc.net]
shoragan has quit [reticulum.oftc.net coulomb.oftc.net]
quinq has quit [reticulum.oftc.net coulomb.oftc.net]
hitech95 has joined #openwrt-devel
EqUaTe has joined #openwrt-devel
wille-io has joined #openwrt-devel
Obi-Wan has joined #openwrt-devel
tomn has joined #openwrt-devel
bbezak has joined #openwrt-devel
slh64 has joined #openwrt-devel
KGB has joined #openwrt-devel
xdarklight_ has joined #openwrt-devel
mark22k has joined #openwrt-devel
SirLouen has joined #openwrt-devel
quinq has joined #openwrt-devel
ldir has joined #openwrt-devel
colo has joined #openwrt-devel
_lore_ has joined #openwrt-devel
bookworm has joined #openwrt-devel
clandmeter has joined #openwrt-devel
embargo has joined #openwrt-devel
lu_zero has joined #openwrt-devel
karlp has joined #openwrt-devel
ukleinek has joined #openwrt-devel
kabel has joined #openwrt-devel
ynezz has joined #openwrt-devel
larsc has joined #openwrt-devel
SwedeMike has joined #openwrt-devel
rsalvaterra has joined #openwrt-devel
f00b4r0 has joined #openwrt-devel
robimarko has joined #openwrt-devel
nixuser has joined #openwrt-devel
shoragan has joined #openwrt-devel
Obi-Wan has quit [synthon.oftc.net reticulum.oftc.net]
lu_zero has quit [synthon.oftc.net reticulum.oftc.net]
f00b4r0 has quit [synthon.oftc.net reticulum.oftc.net]
hitech95 has quit [synthon.oftc.net reticulum.oftc.net]
robimarko has quit [synthon.oftc.net reticulum.oftc.net]
SwedeMike has quit [synthon.oftc.net reticulum.oftc.net]
larsc has quit [synthon.oftc.net reticulum.oftc.net]
SirLouen has quit [synthon.oftc.net reticulum.oftc.net]
tomn has quit [synthon.oftc.net reticulum.oftc.net]
EqUaTe has quit [synthon.oftc.net reticulum.oftc.net]
ldir has quit [synthon.oftc.net reticulum.oftc.net]
kabel has quit [synthon.oftc.net reticulum.oftc.net]
rsalvaterra has quit [synthon.oftc.net reticulum.oftc.net]
nixuser has quit [synthon.oftc.net reticulum.oftc.net]
karlp has quit [synthon.oftc.net reticulum.oftc.net]
wille-io has quit [synthon.oftc.net reticulum.oftc.net]
clandmeter has quit [synthon.oftc.net reticulum.oftc.net]
ukleinek has quit [synthon.oftc.net reticulum.oftc.net]
xdarklight_ has quit [synthon.oftc.net reticulum.oftc.net]
ynezz has quit [synthon.oftc.net reticulum.oftc.net]
bookworm has quit [synthon.oftc.net reticulum.oftc.net]
mark22k has quit [synthon.oftc.net reticulum.oftc.net]
embargo has quit [synthon.oftc.net reticulum.oftc.net]
colo has quit [synthon.oftc.net reticulum.oftc.net]
quinq has quit [synthon.oftc.net reticulum.oftc.net]
bbezak has quit [synthon.oftc.net reticulum.oftc.net]
_lore_ has quit [synthon.oftc.net reticulum.oftc.net]
slh64 has quit [synthon.oftc.net reticulum.oftc.net]
KGB has quit [synthon.oftc.net reticulum.oftc.net]
shoragan has quit [synthon.oftc.net reticulum.oftc.net]
djfe has quit [synthon.oftc.net reticulum.oftc.net]
KanjiMonster has quit [synthon.oftc.net reticulum.oftc.net]
sandberm has quit [synthon.oftc.net reticulum.oftc.net]
parazyd has quit [synthon.oftc.net reticulum.oftc.net]
\x has quit [synthon.oftc.net reticulum.oftc.net]
neocturne has quit [synthon.oftc.net reticulum.oftc.net]
jow has quit [synthon.oftc.net reticulum.oftc.net]
rotanid has quit [synthon.oftc.net reticulum.oftc.net]
noltari has quit [synthon.oftc.net reticulum.oftc.net]
Ansuel has quit [synthon.oftc.net reticulum.oftc.net]
PaulFertser has quit [synthon.oftc.net reticulum.oftc.net]
Emantor has quit [synthon.oftc.net reticulum.oftc.net]
FLD has quit [synthon.oftc.net reticulum.oftc.net]
rua has quit [synthon.oftc.net reticulum.oftc.net]
tom- has quit [synthon.oftc.net reticulum.oftc.net]
Shados has quit [synthon.oftc.net reticulum.oftc.net]
Znevna has quit [synthon.oftc.net reticulum.oftc.net]
slh has quit [synthon.oftc.net reticulum.oftc.net]
ahf has quit [synthon.oftc.net reticulum.oftc.net]
owrt-images-builds has quit [synthon.oftc.net reticulum.oftc.net]
vulpes2[m] has quit [synthon.oftc.net reticulum.oftc.net]
JiiPee has quit [synthon.oftc.net reticulum.oftc.net]
SnarlingFox has quit [synthon.oftc.net reticulum.oftc.net]
dhewg has quit [synthon.oftc.net reticulum.oftc.net]
tmn505 has quit [synthon.oftc.net reticulum.oftc.net]
mrkiko has quit [synthon.oftc.net reticulum.oftc.net]
lucenera has quit [synthon.oftc.net reticulum.oftc.net]
takimata has quit [synthon.oftc.net reticulum.oftc.net]
filimonic has quit [synthon.oftc.net reticulum.oftc.net]
xback has quit [synthon.oftc.net reticulum.oftc.net]
aiyion has quit [synthon.oftc.net reticulum.oftc.net]
rmilecki has quit [synthon.oftc.net reticulum.oftc.net]
floof58 has quit [synthon.oftc.net reticulum.oftc.net]
swegener has quit [synthon.oftc.net reticulum.oftc.net]
hauke has quit [synthon.oftc.net reticulum.oftc.net]
blocktrron has quit [synthon.oftc.net reticulum.oftc.net]
nbd has quit [synthon.oftc.net reticulum.oftc.net]
Sagi has quit [synthon.oftc.net reticulum.oftc.net]
enyc has quit [synthon.oftc.net reticulum.oftc.net]
Habbie has quit [synthon.oftc.net reticulum.oftc.net]
mirko has quit [synthon.oftc.net reticulum.oftc.net]
lemmi has quit [synthon.oftc.net reticulum.oftc.net]
GNUmoon has quit [synthon.oftc.net reticulum.oftc.net]
stintel has quit [synthon.oftc.net reticulum.oftc.net]
KGB-2 has quit [synthon.oftc.net reticulum.oftc.net]
SwedeMike has joined #openwrt-devel
xdarklight_ has joined #openwrt-devel
djfe has joined #openwrt-devel
SirLouen has joined #openwrt-devel
larsc has joined #openwrt-devel
kabel has joined #openwrt-devel
ynezz has joined #openwrt-devel
ukleinek has joined #openwrt-devel
lu_zero has joined #openwrt-devel
karlp has joined #openwrt-devel
clandmeter has joined #openwrt-devel
embargo has joined #openwrt-devel
bookworm has joined #openwrt-devel
ldir has joined #openwrt-devel
colo has joined #openwrt-devel
_lore_ has joined #openwrt-devel
quinq has joined #openwrt-devel
mark22k has joined #openwrt-devel
slh64 has joined #openwrt-devel
bbezak has joined #openwrt-devel
KGB has joined #openwrt-devel
tomn has joined #openwrt-devel
Obi-Wan has joined #openwrt-devel
rotanid has joined #openwrt-devel
KanjiMonster has joined #openwrt-devel
noltari has joined #openwrt-devel
slh has joined #openwrt-devel
sandberm has joined #openwrt-devel
Ansuel has joined #openwrt-devel
PaulFertser has joined #openwrt-devel
Emantor has joined #openwrt-devel
FLD has joined #openwrt-devel
\x has joined #openwrt-devel
JiiPee has joined #openwrt-devel
tom- has joined #openwrt-devel
ahf has joined #openwrt-devel
Shados has joined #openwrt-devel
Znevna has joined #openwrt-devel
rua has joined #openwrt-devel
parazyd has joined #openwrt-devel
SnarlingFox has joined #openwrt-devel
Habbie has joined #openwrt-devel
mirko has joined #openwrt-devel
Sagi has joined #openwrt-devel
hauke has joined #openwrt-devel
blocktrron has joined #openwrt-devel
dhewg has joined #openwrt-devel
nbd has joined #openwrt-devel
stintel has joined #openwrt-devel
swegener has joined #openwrt-devel
lemmi has joined #openwrt-devel
vulpes2[m] has joined #openwrt-devel
KGB-2 has joined #openwrt-devel
rmilecki has joined #openwrt-devel
owrt-images-builds has joined #openwrt-devel
GNUmoon has joined #openwrt-devel
takimata has joined #openwrt-devel
mrkiko has joined #openwrt-devel
aiyion has joined #openwrt-devel
lucenera has joined #openwrt-devel
xback has joined #openwrt-devel
tmn505 has joined #openwrt-devel
filimonic has joined #openwrt-devel
neocturne has joined #openwrt-devel
hitech95 has joined #openwrt-devel
rsalvaterra has joined #openwrt-devel
robimarko has joined #openwrt-devel
f00b4r0 has joined #openwrt-devel
EqUaTe has joined #openwrt-devel
shoragan has joined #openwrt-devel
nixuser has joined #openwrt-devel
wille-io has joined #openwrt-devel
enyc has joined #openwrt-devel
floof58 has joined #openwrt-devel
jow has joined #openwrt-devel
vulpes2[m] has quit [Ping timeout: 480 seconds]
goliath has joined #openwrt-devel
Daanct12 has quit [Quit: WeeChat 4.1.1]
Danct12 has joined #openwrt-devel
paintenzero is now known as Guest6410
paintenzero has joined #openwrt-devel
grid has joined #openwrt-devel
minimal has joined #openwrt-devel
<paintenzero>
Hello, Chat! We are developing our own board based on HLK7621 (module with MT7621a). We ran OpenWRT 22.03.5 without issue on it. Now I built OpenWRT 23.05.0 and PCIe buses stopped working. I found patches with increasing PERST reset delay. It didn't help. As a reset pin only #19 is used so no need to patch for using 8 and 7. What am I missing here? The same configuration works
<paintenzero>
fine in OpenWRT 22.03.
<paintenzero>
I get "mt7621-pci 1e140000.pcie: pcie0 no card, disable it (RST & CLK)" for all three lanes in OpenWRT 23.05
<stintel>
I recall some issues about that on github, I'd try to find those and read the comments, might contain helpful info
<SnarlingFox>
Holy crap those are some netsplits, I forgot that about IRC :D
<SnarlingFox>
PaulFertser: Cheers, checking now
<paintenzero>
stintel: they are talking about the same patch to increase PERST reset delay. I tried all values incrementing by 100 from 100 to 600. It doesn't help me for whatever reason :(
<stintel>
paintenzero: there are some references to other PRs there with changes to DTS also
<stintel>
I don't know anything about the specifics, I just remember those issues blocking bumping ramips to 5.15 back then, so that's the best I can do
<paintenzero>
stintel: thank you! Will check again other PRs in case I missed something
<stintel>
good luck finding the issue!
<Ansuel>
consider that original fw sometimes doesn't reset periperal... things that is 99% done on upstream kernel and resetting them remove all kind of tweak a bootloader may apply... so check also if uboot is doing something special and the special reg is missing upstream
<paintenzero>
Ansuel: u-boot is the same in my case. I didn't change or flash it while trying 22.03 and 23.05.
<Ansuel>
mhhh right could be a regression in some rework... pcie code likes to change a lot LOL
<Slimey>
hmm
<Slimey>
Machine: Qualcomm Technologies, Inc. IPQ807x/AP-HK07
<Slimey>
Linux version 4.4.60 (root@blueserver-virtual-machine) (gcc version 5.2.0 (OpenWrt GCC 5.2.0 unknown) ) #11 SMP PREEMPT Tue Nov 7 13:41:24 IST 2023 Boot CPU: AArch64 Processor [410fd034]
<SnarlingFox>
Ahh here we go PaulFertser: "Package kmod-ath10k wants to install file... But that file is already provided by package * kmod-ath10k-ct" - DERP
<PaulFertser>
SnarlingFox: you should just select either of those two.
<SnarlingFox>
Yep I figured, just menuconfig'ing away the sins now
<PaulFertser>
SnarlingFox: -ct is for the CandelaTech custom firmware, it used to be more stable on most OpenWrt targets.
<SnarlingFox>
"Used" to be?
<SnarlingFox>
I'm unclear which I should be using for this device, was gonna try the non-CT first
<PaulFertser>
Well, not sure about the current status, few people were reporting better results after trying the pure upstream.
<PaulFertser>
I'd try -ct (both kmod and firmware) first.
<SnarlingFox>
Oh okay
<SnarlingFox>
Right, trying another build
f00b4r0 has quit [Ping timeout: 480 seconds]
<SnarlingFox>
Huh, turns out building it with 24 threads is surprisingly quick
* SnarlingFox
Fry Suspicious gif
<stintel>
first build always takes much longer because you need to build tools, toolchain, etc
FinboySlick has joined #openwrt-devel
<SnarlingFox>
Ah that may explain it :D
<SnarlingFox>
So what you're saying is, I can never wipe this virtual machine? :)
<Znevna>
who said that?
<SnarlingFox>
:D
<SnarlingFox>
Right, even though it's got a lot to be changed, lets see if this WSQ50 will boot from tftp from this initramfs image
<FinboySlick>
Before I start looking into it further, anyone here knows why freeradius3 doesn't appear to be in 23.05.0? I see in git that it's still being updated.
<stintel>
FinboySlick: could be related due to the move to libpcre2 although I'm not sure that was pre or post 23.05
<FinboySlick>
OK, but it will eventually come back, right?
<stintel>
it should
<Ansuel>
stintel yes... there is a pending pr to fix it
<stintel>
I personally added --disable-pcre in my build branch to make it build
<SnarlingFox>
Well, the WSQ50 boots, but errrs like "[ 8.915830] ath10k_ahb a000000.wifi: failed to fetch board-2.bin or board.bin from ath10k/QCA4019/hw1.0" are to be seen... not surprising for a first attempt :)
<Ansuel>
for some reason there was some confusion in checking the freeradius source and it was think there was support for pcre2
<Ansuel>
reality is that big nope
paintenzero has joined #openwrt-devel
<paintenzero>
Also we made a board with MT7621a and MT7915E. On OpenWRT 22.03.5 two PCIe devices are detected and can be configured. However they behave like antennas are not connected (which obviously not true). So there is no signal from the MT7915E. On dmesg the only error I see is "eeprom load fail, use default bin". Does anybody know how to fix it?
<SnarlingFox>
PaulFertser: Is there a preferred way to name multiple near identical products that have the same hardware?
<SnarlingFox>
Just spotted that both the WSQ50 and WSQ60 have identical hardware, it's only the software (and a vertical stand that comes with the 60) that separates them
<SnarlingFox>
Should I call it something like "zyxel,wsqx0" in any patches?
<SnarlingFox>
Or just call it "zyxel,wsq50" for now?
<jakllsch>
probably wsq50, imo
<PaulFertser>
SnarlingFox: I agree with jakllsch
<SnarlingFox>
I decided to put them both in but as separate lines: "zyxel,wsq50 | zyxel,wsq60)" (split onto 2 lines with a backslash)
<SnarlingFox>
Just trying to identify what "ubootenv_add_uci_config "/dev/mtd6" "0x0" "0x10000" "0x10000"" is and what and why it needs to be set
<dwfreed>
if the hardware is identical, differentiating between them is not useful
<dwfreed>
for an existing example of this, see the linksys e8450 and belkin rt-ax3200
<SnarlingFox>
Although the WSQ50 and WSQ60 are identical, they have yet to be brought into the OpenWrt fold properly (despite a bastardized install from the manufacturer that's a few years old now)
<SnarlingFox>
I booted up from an initramfs image from a nbg6617 and the device booted up fine and had access to ethernet, but not to any of the numerous wireless radios on these puppies
filimonic has quit [Read error: Connection reset by peer]
filimonic has joined #openwrt-devel
<SnarlingFox>
When booting up from that same image, if I `cat /proc/mtd` it's empty
<SnarlingFox>
Well, it has a header, but no lines after the header
<SnarlingFox>
(It's likely that's because it's booted from initramfs over tftp)
<mrkiko>
SnarlingFox: mhm, I guess you do not have content in /proc/mtd because the DTS you are using doesn't define partitions in flash
<PaulFertser>
SnarlingFox: ubootenv is only needed if you need to modify any u-boot env variables from within OpenWrt. Omit that for now.
<SnarlingFox>
Based on the partition sizes, gut feel is that "env" aka mtd2 is the correct one, the larger one could actually be the ubootloader itself
<PaulFertser>
SnarlingFox: most probably env is the u-boot env, yes.
FinboySlick has left #openwrt-devel [#openwrt-devel]
hurricos has joined #openwrt-devel
Borromini has joined #openwrt-devel
<Borromini>
Ansuel: i think there's an owrt-23.05-ax880 tree that got accidentally pushed
<Borromini>
it's showing up in heads
<Mangix>
oh lovely
<Mangix>
build breaks on Fedora 3i9
<Ansuel>
yes
<Ansuel>
Borromini yes waiting jow for deletion :(
<Ansuel>
my fault for doing 3 things at the same time...
<robimarko>
Mangix: I constantly build on Fedora 39
<robimarko>
And it works
<Mangix>
robimarko: then i guess 40. or w/e the latest is
<Mangix>
recent update broke it
<Mangix>
prereq-build.mk needs an update
<robimarko>
Mangix: Latest is 39, I have been running it since beta
<Mangix>
wipe your build/staging_dir and see it fail
<Mangix>
I had to manually fix symlinks
<robimarko>
Oh that
<robimarko>
Yeah, all of the symlinks were broken after the update
<Ansuel>
i mean... if the problem is really a problem of things not linked it should not be that problematic to implement... plenty of way from notifier to other solution
<Ansuel>
thing is that i can't understand how pxa is the only device broken???
<robimarko>
Its probably not
<robimarko>
at91 I2C had the same issue and the same "fix" in the original recovery model
<Ansuel>
at91 and imx should also be broken in theory
<robimarko>
Its been broken since 5.10 or even before
<robimarko>
Nope
<robimarko>
5.15
<Ansuel>
problem is that i assume reverting it is a no go?
<robimarko>
Why not, that is what Linus suggested
<robimarko>
Even the patchset converting it says that we can always go back if its broken
<Ansuel>
anyway from what i'm seeing it's not even a notifier thing... but it's really an additional function or something to toggle for this o.O i assume the recovery thing can be generilized as well... just missing in the generic code
<SnarlingFox>
Huh, in stepping through this DTS file I noticed there's a USB 3.0 port definition... sure enough there's an unpopulated header on the PCB, score!
<aveng3r>
Hi there, I'm trying to run some docker containers that talk to each other using ubus, I share the /var/run/ubus/ubus.sock volume between them. Everything works but if I try to register an object on a process running as normal user (non-root) I get UBUS_STATUS_INVALID_ARGUMENT from the ubusd.
<aveng3r>
I've tried to create an acl file and run ubusd -A acl.json, but that didn't work
<aveng3r>
If anyone knows how to workaround this problem, or how to write a proper acl file to ubusd please let me know, thanks!