dangole_ has joined #openwrt-devel
aiyion_ has joined #openwrt-devel
aiyion has quit [Ping timeout: 480 seconds]
dangole has quit [Ping timeout: 480 seconds]
Backhand4630 has quit [Quit: Textual IRC Client: www.textualapp.com]
danitool has quit [Remote host closed the connection]
tSYS has quit [Quit: *squeak*]
tSYS has joined #openwrt-devel
<Namidairo> that can't be right, they're trying to remove bw160 from all mt7915
<Namidairo> too bad i'm allergic to mailing lists
nixuser has quit [Ping timeout: 480 seconds]
nixuser has joined #openwrt-devel
f0g has joined #openwrt-devel
dansan has quit [Ping timeout: 480 seconds]
<f0g> Hi all. I get my openwrt version from /etc/openwrt_version, which is a string as 'r0-65c3b472'. It looks like a commit, but I didn't find in openwrt git source. How can I know the exactly openwrt version?
<slh> f0g: ./scripts/getver.sh
<slh> it's supposed to get a monotonically increasing version number --> r21678-87b9825521 21678 commits since ee53a240ac902dc83209008a2671e7fdcf55957a (LEDE REBOOT), 87b9825521 the current git hash of HEAD. this obviously won't find the right offset for forked/ modified repos
<slh> then you get something like r0+xyz-hash (xyz number of additional, non-OpenWrt, commits)
<owrt-2102-builds> Build [#55](https://buildbot.openwrt.org/openwrt-21.02/images/#builders/44/builds/55) of `realtek/generic` completed successfully.
<f0g> slh: thanks. but it looks like my openwrt souce has been changed a lot, and I can't get any human readable version from the script.
<f0g> output is like: fatal: Invalid revision range xxxx..65c3b472...
<slh> quite possible
<slh> then you end up with r0-hash, as you got there
dansan has joined #openwrt-devel
dangole_ has quit [Ping timeout: 480 seconds]
tomn has quit [Remote host closed the connection]
tomn has joined #openwrt-devel
ptudor_ has quit [Quit: Strict-Transport-Security: max-age=48211200; preload]
ptudor has joined #openwrt-devel
minimal has quit [Quit: Leaving]
<mrkiko> No installation insturctions in commit 665c2154ef122d10dfffeca95538ebdff82653b5
<Tapper> Hi people any one know if the 5.15. kernel can run on r7800 yet? last time I tryed about 2 weeks agao it would reboot all the time.
valku has quit [Quit: valku]
<mrkiko> Hi Tapper! I don't have the answer to your question, still was happy to say hello!:D
<mrkiko> Tapper: Ansquel will now better for sure but he's not around, at least not yet
<Tapper> Hi mrkiko all good mate. How's your day going?
f0g has quit [Remote host closed the connection]
<mrkiko> Tapper: it just begun! :D and it's fine.
<Tapper> mrkiko same here mate. Going to the gym to lift wates soon then to see the kids off to school.
<mrkiko> Tapper: :D :D go ahead and anjoey
<Tapper> Then I don't know what i will be doing. Need to wait until my wife is awake.
<Tapper> Lifting waits is good for us blind people. I would love to play soka but.... never mind ded lifts it is.
<Tapper> Makes you feel good to.
Tapper has quit [Quit: Tapper]
<KGB-1> https://tests.reproducible-builds.org/openwrt/openwrt_ath79.html has been updated. (98.6% images and 99.6% packages reproducible in our current test framework.)
borek has joined #openwrt-devel
borek has quit [Quit: borek]
borek has joined #openwrt-devel
<mrkiko> tap:D :D
cbeznea has joined #openwrt-devel
hhasert has joined #openwrt-devel
SlimeyX has quit [Read error: Connection reset by peer]
robimarko has joined #openwrt-devel
SlimeyX has joined #openwrt-devel
danitool has joined #openwrt-devel
<Znevna> any ideea why "disable" wireless interfaces from LuCI works reliably only once?
<rmilecki> nick[m]12: sure, I can test bcm47xx next week
borek has quit [Read error: No route to host]
borek has joined #openwrt-devel
<nick[m]12> rmilecki: nice thanks!
<KGB-2> https://tests.reproducible-builds.org/openwrt/openwrt_sunxi.html has been updated. (0% images and 97.7% packages reproducible in our current test framework.)
vicencb has joined #openwrt-devel
ptudor has quit [Ping timeout: 480 seconds]
ptudor has joined #openwrt-devel
Misanthropos has quit [Quit: ZNC 1.8.2+deb2+b1 - https://znc.in]
dangole_ has joined #openwrt-devel
dangole has joined #openwrt-devel
dangole_ has quit [Remote host closed the connection]
<ukleinek> To run two instances of the same image in qemu I'd like to adapt the network config (e.g. lan ip network and ula prefix) based on the mac address. Is there a script that is run at first boot that would automate the reconfiguration necessary for each run?
<ukleinek> maybe package/base-files/files/bin/config_generate?
<nbd> you can put a script in /etc/uci-defaults
<nbd> it is run only once after upgrade (and then deleted)
<rmilecki> (and on the first image boot)
Acinonyx has quit [Quit: Peer reset by connector]
Acinonyx has joined #openwrt-devel
robimarko has quit [Remote host closed the connection]
robimarko has joined #openwrt-devel
borek has quit [Read error: Connection reset by peer]
borek has joined #openwrt-devel
<ukleinek> nbd, rmilecki: Sounds like what I need. Thanks
srslypascal is now known as Guest333
srslypascal has joined #openwrt-devel
Guest333 has quit [Ping timeout: 480 seconds]
goliath has joined #openwrt-devel
<KGB-2> https://tests.reproducible-builds.org/openwrt/openwrt_omap.html has been updated. (11.1% images and 99.5% packages reproducible in our current test framework.)
dangole has quit [Remote host closed the connection]
dangole has joined #openwrt-devel
danitool has quit [Quit: Cubum autem in duos cubos, aut quadratoquadratum in duos quadratoquadratos]
<damex> Znevna: i have many openwrt devices and i haven't had such problem with any of them
<Znevna> what devices?
<Znevna> any mediatek radios ? :)
<damex> Znevna: https://openwrt.org/toh/xiaomi/ax3200 does this one count?
<damex> i have two of them
<Znevna> ok
<Znevna> that one has wifi leds?
<Znevna> or better yet
<Znevna> disable the interfaces from luci, enable them again, and then try to disable them again :)
<Znevna> at the 2nd disable you should be stuck with broadcasting ssids and that's about it
<Znevna> disable > enable > restart > disable > works fine tho'
valku has joined #openwrt-devel
<aiyion_> Is everything alright with the devel-mailinglist?
aiyion_ is now known as aiyio
aiyio is now known as aiyion
<damex> Znevna: it does 'stuck' in some cache. in windows or ios it is the same. moment you successfully connect to other existing access point - it dissapear from the list
<aiyion> It often takes a few minutes for my mails to get through, but the current has been taking an hour now.
minimal has joined #openwrt-devel
Acinonyx has quit [Quit: Peer reset by connector]
Acinonyx has joined #openwrt-devel
<Znevna> that doesn't make sense
<Znevna> check the logs
Acinonyx has quit [Quit: Peer reset by connector]
Acinonyx has joined #openwrt-devel
gladiac has joined #openwrt-devel
<damex> Znevna: well, it does not get stuck. i don't see it 'broadcasting' seconds after i click disable second time
srslypascal is now known as Guest342
srslypascal has joined #openwrt-devel
<damex> i can check logs but testing shows different thing
borek has quit [Remote host closed the connection]
borek has joined #openwrt-devel
Guest342 has quit [Ping timeout: 480 seconds]
<Znevna> ok
<Znevna> easy reproducible on asus ax53u
<damex> Znevna: how long does it get stuck on ax53u? is there anything special saying that it is definitely stuck? i already did lots of enable/disable on that 2.4 interface before
<damex> and do you use snapshot or release?
<Znevna> snap
<Znevna> stuck? until next enable or restart
borek has quit [Ping timeout: 480 seconds]
<mrkiko> robimarko: and on ipq4xx/chromeOS, what's the reason for not being able to start secondary CPU(s)? Is it code in trusted firmware or something like that?
<damex> Znevna: so it broadcast indefinitely until you enable it back or restart router? how did make sure that it actually stuck?
<robimarko> mrkiko: It was outdated TZ FW AFAIK
<robimarko> They worked around that by reverting some upstream changes
<mrkiko> robimarko: wow :D
<mrkiko> Kernel taint, need to reboot...
mrkiko has quit [Quit: leaving]
mrkiko has joined #openwrt-devel
srslypascal is now known as Guest349
srslypascal has joined #openwrt-devel
<Znevna> damex: what do you mean? i see it broadcasting the SSID.
Guest349 has quit [Ping timeout: 480 seconds]
<robimarko> mrkiko: What is the issue you are having?
SlimeyX has quit [Ping timeout: 480 seconds]
SlimeyX has joined #openwrt-devel
<aiyion> Like really. Is the mailinglist broken? I've sent the patch three and a half hours ago.
<mrkiko> robimarko: just for fun, tried to load ovpn-dco, and it somehow failed, the kernel printed a backtrace and was tainted (maybe only for the fact the module was out of tree or something), so I rebooted the VPS just to avoid possible instability later
SlimeyX has quit [Ping timeout: 480 seconds]
Misanthropos has joined #openwrt-devel
lucenera has quit [Quit: The Lounge - https://thelounge.chat]
SlimeyX has joined #openwrt-devel
lucenera has joined #openwrt-devel
gladiac has quit [Quit: k thx bye]
Backhand4630 has joined #openwrt-devel
<Backhand4630> is there a way to compile an openwrt-image and use the official repository for opkg?
<Backhand4630> my device is not in the autobuild anymore, so i have to compile it myself, and the kernel-hash is different and therefor will not install any of the packages of the feed
<damex> Backhand4630: no, most likely not. you better build everything you want to have inside your package (that would also save some space)
<damex> inside your device image*
<KGB-2> https://tests.reproducible-builds.org/openwrt/openwrt_lantiq.html has been updated. (96.2% images and 99.6% packages reproducible in our current test framework.)
<Backhand4630> god that is one aspect of openWRT i really hate
<Backhand4630> if you are on the exact same kernel version but cant use the official repo. why is it built that way?
<ynezz> Backhand4630: crashing kernel or using supported device, choose one
<Backhand4630> crashing kernel please
<ynezz> IIRC you can force the installation
<Backhand4630> ahh yeah ... --force-depends did the trick. thanks mate
<ynezz> happy oopsies
<Backhand4630> wont happen
<Backhand4630> wouldn't the hash be the same if i build my image with defconfig?
borek has joined #openwrt-devel
gch981213 has quit [Quit: Ping timeout (120 seconds)]
gch981213 has joined #openwrt-devel
ynezz has quit [Ping timeout: 480 seconds]
Borromini has joined #openwrt-devel
borek has quit [Quit: borek]
ynezz has joined #openwrt-devel
ynezz is now known as Guest358
Guest358 is now known as ynezz
vicencb has quit [Quit: Leaving.]
lucenera has quit [Quit: The Lounge - https://thelounge.chat]
<ynezz> just build with `make LINUX_VERMAGIC=yourdesiredhash` if you like oopsies
lucenera has joined #openwrt-devel
<Backhand4630> thanks. like i said, i am using a supported device, there is even a dts for it but it was removed from autobuild because of NAND flash reasons. in my case it makes sense
<Backhand4630> thanks i didnt know this is possible
<robimarko> It really doesnt matter if device is supported
<Znevna> you're the mikrotik guy? :P
<Backhand4630> yeah :P
<Znevna> get a supported device
<Znevna> less headaches
<Backhand4630> i already have it, i am low on cash and its one device less in the landfill. makes sense for me to keep it :)
<ynezz> well, you should ideally build with the same config as our buildbots are using, you can find that in config.buildinfo files in the downloads
<ynezz> this way you can stay away from some issues
<Backhand4630> yeah i am doing that right now ---> wget -O .config -https://downloads.openwrt.org/releases/xx.xx.x/targets/ath79/mikrotik/config.buildinfo
danitool has joined #openwrt-devel
<Backhand4630> but when im building with that config how can i specify only my device?
<Backhand4630> cause when i do "make menuconfig" and target my device, then i would alter the config again, wouldnt i?
<ynezz> this kind of config changes should be probably harmless, kernel related configurations should be avoided
<ynezz> like disabling/enabling some kernel features/modules etc.
<Backhand4630> yes, i meant to get the same hash without the LINUX_VERMAGIC parameter
<ynezz> you wont
<Backhand4630> i see ... does it have changed since 2018/2019? because i found a thread in the forums where they do it: https://forum.openwrt.org/t/build-official-release-with-minimal-kernel-fix-kernel-vermagic-mismatch/18562/3
<Backhand4630> (and a blog post)
<Backhand4630> where they say the hash is made out of the configuration
<ynezz> grep '=[ym]' $(LINUX_DIR)/.config.set | LC_ALL=C sort | $(MKHASH) md5 > $(LINUX_DIR)/.vermagic
<ynezz> thats how its computed
<Backhand4630> mhh i see...
<Backhand4630> and would it be possible to alter de hash of a already flashed device?
cbeznea has quit [Quit: Leaving.]
<ynezz> yes, you can change it somewhere in the /usr/lib/opkg file(s)
rafelbev has joined #openwrt-devel
<Backhand4630> cool thanks. you're saving me a lot of time here. i will look into it
<rafelbev> hi, I would like to ask a question with regards to IMAGE_SIZE. I am currently preparing a patch/pull request for the Wavlink WL-WN583AX1. I already managed to get it functioning, and would like to ask what the IMAGE_SIZE variable is referring to. I'm basing my knowledge off another device that was defined, but I don't want to just copy blindly values only. Could you kindly hold my hand if I have a couple of questions please?
<Borromini> rafelbev: usually it's the maximum flash size an image can occupy
<Borromini> ie flash minus space needed for bootloader, calibration data and whatever OEM partitions are kept/contain relevant data
<ynezz> Backhand4630: thinking about it more, I was wrong, you should be able to get same version magic with the same configuration
danitool has quit [Quit: Cubum autem in duos cubos, aut quadratoquadratum in duos quadratoquadratos]
<Backhand4630> yenzz: okay cool. but how do i target my device then?
<Backhand4630> ynezz*
cbeznea has joined #openwrt-devel
<robimarko> buildbot config will build for all devices in that subtarget
<ynezz> I would first try to build with stock config.buildinfo
<rafelbev> Borromini: can I derive it from the size or layout of the mtd? it sounds indicative for the wiki? or is it actually used by the device during the flash/boot process?
<robimarko> rafelbev: its the largets image that can actually fit on the device
<ynezz> Backhand4630: I would first try to build with stock config.buildinfo, check the hash, save the .config.set, do make menuconfig and adjust the config only for your device, diff the new .config.set and adjust removed/missing kernel options/modules so .config.sets are same
<ynezz> IIRC ath79 was one of the targets with fully reproducible images
<Backhand4630> okay thank you very much! i'll give it a shot
<ynezz> https://tests.reproducible-builds.org/openwrt/openwrt_ath79.html "we could built 884 (98.6%) out of 896 images and 1539 (99.6%) out of 1544 packages reproducibly"
<ynezz> so same config should yield same result
<Borromini> rafelbev: it's used by the build process so you don't overwrite when flashing AFAIK. If the image size surpasses that limit the image won't be created.
<Borromini> Most of the time it's the same size as the OEM firmware partition
<rafelbev> Borromini: can I use the size of the bin file of the original firmware?
<Borromini> no.
<Borromini> i'm no expert on this, but I can tell you that binary might be compressed or contain extra data, it's no indication, you need to look at /proc/mtd to see which areas are occupied by the OEM firmware (kernel + userland stuff)
<Borromini> best practice is to build an image and boot it as a ramdisk as well, before you write to flash
danitool has joined #openwrt-devel
dangole has quit [Remote host closed the connection]
dangole has joined #openwrt-devel
<rafelbev> Borromini: should be this... 0x000000090000-0x000000e90000 : "firmware"
<rafelbev> further down in the bootlog i can see that it's made up of two partitions, kernel and rootfs
<Borromini> if they're both squeezed in there then yes that's your range
<rafelbev> yes: 0x000000090000-0x000000400000 : "kernel" and 0x000000400000-0x000000e90000 : "rootfs"
<rafelbev> what is the block size (multiplier) for that range? converted to decimal that is a size of 14,680,064. did I get the magic number? :D
<Borromini> that's above my paygrade sorry.
<rafelbev> btw the original firmware had this banner on startupDescription: MIPS OpenWrt Linux-4.4.198
<rafelbev> and I get a login prompt for MeshLink
<rafelbev> what links to pastebins are allowed so if anybody is interested in reading the original bootlog, they can grab it later?
<rafelbev> This is the log from the original firmware of the Wavlink WL_WN-583AX1: https://pastebin.com/raw/tbjXkB9E
Borromini has quit [Ping timeout: 480 seconds]
Borromini has joined #openwrt-devel
cbeznea has quit [Quit: Leaving.]
dangole has quit [Remote host closed the connection]
dangole has joined #openwrt-devel
Backhand4630 has quit [Quit: Textual IRC Client: www.textualapp.com]
<Znevna> hah another mt7915
<Borromini> are you still buying MT7621 stuff Znevna
<aiyion> :D
robimarko has quit [Quit: Leaving]
hhasert has quit [Quit: Leaving]
<aiyion> Znevna, your PR 11601, does that get a backport to 22.03?
<KGB-0> https://tests.reproducible-builds.org/openwrt/openwrt_bcm47xx.html has been updated. (100.0% images and 99.6% packages reproducible in our current test framework.)
<aiyion> ah just saw the mt76 PR. So that will need to happen first.
Backhand4630 has joined #openwrt-devel
Borromini has quit [Quit: Lost terminal]
srslypascal has quit [Ping timeout: 480 seconds]
srslypascal has joined #openwrt-devel
<Backhand4630> okay, any developer here? ... we have this git-commit in the ar71xx branch of the code.. can we port this to ath79?