KGB-2 has quit [Remote host closed the connection]
KGB-2 has joined #openwrt-devel
danitool has quit [Quit: Cubum autem in duos cubos, aut quadratoquadratum in duos quadratoquadratos]
gromero_ has quit [Remote host closed the connection]
eluks has quit [Remote host closed the connection]
eluks has joined #openwrt-devel
gromero has joined #openwrt-devel
valku has quit [Quit: valku]
sorinello has joined #openwrt-devel
sorinello has quit []
caskd has joined #openwrt-devel
caskd has quit [Remote host closed the connection]
caskd has joined #openwrt-devel
caskd_ has joined #openwrt-devel
goliath has joined #openwrt-devel
caskd has quit [Ping timeout: 480 seconds]
caskd_ has quit [Ping timeout: 480 seconds]
sorinello has joined #openwrt-devel
danitool has joined #openwrt-devel
<dpawlik>
robimarko: hey, definitely there is somewhere an issue. Normally, there are no kmods packages available to install. Normally I was thinking that it is fine, but I remember that earlier kmods were available. I was thinking to make a dependency relation when r8152-firmware is installed it will also install kmod-usb-net-rtl8152, but after a while -
<dpawlik>
kindly ping ynezz - maybe you will know where to search for that bug ^^
<dpawlik>
I can create an issue with better description. In short, kmods- packages are not available after switch to apk
<KanjiMonster>
dpawlik: selfbuilt or snapshot?
<dpawlik>
I'm using own build, but mko was using image from firmware selector. Both get same issue: r8152-firmware is available, but the missing puzzle kmod-usb-net-rtl8152 is not available
Mangix has quit [Read error: Connection reset by peer]
<dhewg>
blogic: mesh doesn't come up with CONFIG_WIFI_SCRIPTS_UCODE due to IR and missing cc. quick and dirty hack to make it work: https://paste.debian.net/plainh/60ec7e3a
Ycarus has quit [Remote host closed the connection]
<dhewg>
blogic: now beacon_int got added, but the cc is still missing
<dhewg>
it's a wifi-device option here, not a wifi-iface one. is that still correct?
<blogic>
ah ofcourse
<blogic>
hang on
<blogic>
dhewg: can you PM me the UCI you are using ?
robimarko_ has joined #openwrt-devel
<dhewg>
sure, it's a very basic one, fresh openwrt one device with a iface config taken from another mesh node, so there might be something in there that's old and invalid by now? https://paste.debian.net/plainh/974ca2d5
vincejv has quit [Read error: Connection reset by peer]
mark22k has joined #openwrt-devel
mark22k has quit []
mark22k has joined #openwrt-devel
n3ph has joined #openwrt-devel
<robimarko_>
Any poor soul that had an issue with net-snmp not seeing a custom MIB?
<russell-->
i've had snmpd just stop responding to queries, restart fixes
<robimarko_>
My issue is that once I fix the error in MIB and try snmpwalking it, well it just refuses to walk the MIB
<robimarko_>
And snmptranslate still thinks its just enterprise OID
<dpawlik>
ynezz thanks for checking. So it is correct that the firmware does not require kmod and the kmod is not available via luci or apk search kmod-usb-net-rtl ? How user will know that on installing r8152-firmware they need to install kmod-usb-net-rtl8152 ?
<dpawlik>
ynezz so even when the package is available in firmware selector or in the repository, it is not so obvious that kmod needs to be installed.
<KanjiMonster>
dpawlik: the default assumption is that users know to install a kmod to get support for a device, and firmware gets pulled in as a dependency of that kmod
caskd has quit [Ping timeout: 480 seconds]
<efahl>
dpawlik: check the contents of /etc/apk/repositories.d/distfeeds.list It should have 8 line, the third of which is 'kmods'
<KanjiMonster>
the kmods one only exists though for CONFIG_BUILDBOT=y AFAICT
<KanjiMonster>
which is =y for the imagebuilder from downloads.openwrt.org, but is not enabled by default when building yourself
<efahl>
right, I suspect dpawlik's build is "broken" and his distfeeds isn't listing all the feeds, hence the confusion
<ynezz>
we've mostly tested everything provided by buildbot, so it might be the case, that custom builds might still need some fine tunning
<ynezz>
dpawlik: simply file the bug report, thanks
<ynezz>
dpawlik: the dependency is OK, you're usually supposed to install the kmod and if it needs firmware then its being pulled in as dependency, not vice versa
skynet2 has joined #openwrt-devel
<ynezz>
dpawlik: is it something related to the opkg -> apk switch? like it was working differently before?
<ynezz>
dpawlik: I'm quite lost here where/how it started to be seen as an issue :)
<dpawlik>
maybe I just don't understand something :) Let's wait and see what @mko says . Thanks for explanation
skynet2_ has joined #openwrt-devel
skynet2 has quit [Ping timeout: 480 seconds]
<ynezz>
lastlog mko
<ynezz>
oopsie
skynet2_ has quit []
<ynezz>
dpawlik: for you everything works, right?
minimal has joined #openwrt-devel
<KanjiMonster>
ynezz: somewhere around the apk switch we stopped adding the kmods to targets/<target>/packages/ and only have them now in targets/<target>/kmods/<kernel-version>
<dpawlik>
ah, I'm building images by my own, I can add the firmware and kmod to the .config. Mko is building via firmware selector - he just need to remember to add the kmod to customize image. Fiding that package was not so obvious as I thought
<KanjiMonster>
if you build an image, the default for opkg/apk is to only add targets/<target>/packages, but not targets/<target>/kmods, so kmods stopped being reachable
<KanjiMonster>
the firmware selector though should have proper feed config; if it doesn't there is a bug
<dpawlik>
can not focus now on the chat. Hope tomorrow will come back mko from the PTO and he will explain better ;)
vincejv has joined #openwrt-devel
n3ph has quit [Ping timeout: 480 seconds]
Rondom has joined #openwrt-devel
<ynezz>
KanjiMonster: yep, suspecting something along these lines
<KanjiMonster>
ynezz: I just downloaded builds from 24.02-rc2 and main for openwrt one, both had the correct feeds (according to the rootfs)
<KanjiMonster>
so we probably need some exact config for reproduction
<ynezz>
its from buildbots, so should be OK
valku has joined #openwrt-devel
<robimarko_>
firmware selector uses the buildbot generated image builders so it must have kmod feed as well present
robimarko_ is now known as robimarko
<aparcar[m]>
ynezz: did you read my message regarding codeberg?
butter has joined #openwrt-devel
blcok has joined #openwrt-devel
<butter>
which paket do i need for a mediatek MT7613BEN?
<butter>
Short explaination, I've got an archer c20 v6, and the "only difference" is the WIFI chip it seems
<butter>
so I'm gambling atm, and just in case, I've already a set of connectors soldered to the tx rx and gnd
<butter>
plan is to use the u-boot from the original firmware, stick it on and see if something happens.
<butter>
Does a sysupgrade .bin contain the kernel with the new modifications I've done in the firmware selector "installed packages", or does it only contain the original packets and the rest of it is in the squashfs partition?
<butter>
Because that would mean I'd need to recreate a full kernel, and that's gonna be interesting
<schmars[m]>
mt76/mt7615 are kernel modules that would be included in the squashfs, yeah
<butter>
okay, so I cannot simply walk into mordor here - like, just tell the website to include those modules, get the bin and wish it a great day during first-time installation
goliath has joined #openwrt-devel
<butter>
because all I've planned to do so far is take the c20 v5 and just change the packets to get a "c20 v6 kernel"
<butter>
but what I'm currently seeing is that I need to download the git, add a new hardware type, and recompile it for testing
<butter>
so that I can get an actual kernel with (hopefully) the right hardware drivers
blcok has quit [Ping timeout: 480 seconds]
Sawzall has quit [Read error: Connection reset by peer]
Rondom has quit [Remote host closed the connection]
butter has quit [Quit: Konversation terminated!]
Sawzall has joined #openwrt-devel
<blogic>
I spent the morning browsing PRs on GH
<blogic>
imho there is a ton that is good for a merge
<blogic>
lots of PRs had review from devs and then went stale and then OP popped up weeks/months later and fixed it
<blogic>
there are like 15-20 filogic boards that look good to go
<blogic>
pile of PRs that just need minor manual tweaks
<blogic>
so while building the GPL tar ball for the One and having SFC verify it, they actually asked about the warnings
<blogic>
I just built a really ugly for `grep | cut`; do grep| awk; done cmd and I am not able to spt any board using policycoreutils
<ynezz>
its for selinux
<blogic>
same for package/utils/audit/Makefile
<blogic>
yes
<mko>
Hey, just catching up on things. So first of all, I am not building myself, I use firmware builder. Then, apk update DOES SHOW pulling "snapshots/targets/mediatek/filogic/kmods/6.6.63-1-5ee6b854ff92f1a1f463f8234bb06825/packages.adb"
<blogic>
ynezz: any board includes it by default ?
<blogic>
same as lldp
<ynezz>
nope, thats why we wanted to move those into packages feed, since 2019...
<blogic>
so move audit, lldpd, policycoreutils, kexec-tools to packages
<blogic>
and import libpam
<ynezz>
+ define what should be in the core, so its clear
<blogic>
not sure about the force_link patch but the rest looks legit
<ynezz>
well, simply just approve the PR if you're not going to merge it yourself = you're fine with that
<blogic>
might be feasible to allow_list options within ucidef_set_system() but that might be very academic
<ynezz>
then anyone else will eventually merge it, because already having 2 devs in favor, it really helps a lot
<blogic>
ynezz: ok, if anyone complains I'll send them your way as you gave the Acked-by ;P
skynet2 has joined #openwrt-devel
skynet2_ has joined #openwrt-devel
skynet2_ has quit []
skynet2 has quit [Ping timeout: 480 seconds]
goliath has quit [Quit: SIGSEGV]
<schmars[m]>
given the surge of various new x86_64 mini pcs and appliances, is openwrt open for more specific models in the x86/64 target? for stuff like watchdog, serial console, leds, sensors, network config mirroring labels on the case, etc.
<efahl>
I'd like to see more user-configurable stuff to support those
<Habbie>
they don't need to go into a dts anyway
<efahl>
Specifically, I did an experimental hack in /etc/board.d/99-default_network to look for a 'ports' section in /etc/config/network
<efahl>
So I could say 'wan eth0', 'lan eth1 eth2 eth3' and have that magically appear in my board.json
<efahl>
It's different for every minipc, so I figure a uci-based way to do it was best
<schmars[m]>
that doesn'
<schmars[m]>
:)
<schmars[m]>
that doesn't work if you also wanted to rename ports, right? preinit is faster then ports from e.g. kmod-igc or kmod-i40e
<schmars[m]>
and i'd also want to pass grub options, for serial console
<efahl>
right, just assigns them to wan/lan using existing interface names
<efahl>
which in and of itself is a major leap forward from the default