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)
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?
<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
<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)
<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>
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
<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?