**** BEGIN LOGGING AT Wed Mar 20 02:59:57 2019 Mar 20 09:26:08 jow: do you mind installing bzr on the buildbots? Mar 20 09:27:59 related to this issue https://github.com/openwrt/packages/issues/8210 Mar 20 10:41:15 hi! are there any openwrt devs on netdev 0x13 in prague? Mar 20 10:41:33 nbd: ^? Mar 20 14:05:04 ynezz: could you please test again Mar 20 14:07:06 Hauke: thanks, seems fixed Mar 20 14:15:00 aparcar[m]: I don't have access to all slaves and bzr is no build requirment of buildroot Mar 20 14:15:15 aparcar[m]: better switch to tarballs Mar 20 14:27:19 KanjiMonster: Please could you take a look at this one https://github.com/openwrt/openwrt/pull/750 ? Mar 20 14:28:44 ynezz: hrm, looks like I need to update my filters, that slipped by. will do so later Mar 20 14:54:21 blocktrron: https://github.com/openwrt/openwrt/pull/913 seems pretty much dead, what do you think? Mar 20 14:58:00 ynezz: yup, should go for ath79 at this point Mar 20 14:58:29 The motivation to port the sgmii workaround is another story. Mar 20 14:59:06 :) Mar 20 15:03:40 * gch981213 tries to build linux-next for mt7621 and got a 35MB vmlinux :( Mar 20 15:04:01 I assume I should do some kind of objcopy, right? Mar 20 15:11:13 * gch981213 found what he needed in include/kernel-defaults.mk Mar 20 15:15:33 gch981213: what for device you have? Currently NAND & I2c controller isn't in linux-next. Mar 20 15:19:23 Rene__: I need neither of them. My board uses SPI flash but I'll boot from USB stick. Mar 20 15:20:09 *I'll load kernel using tftp and use rootfs from USB stick Mar 20 15:22:51 ah, great Mar 20 18:06:23 ynezz: ping Mar 20 19:47:15 jow: pong Mar 20 23:52:41 Any guesses as to which 802.11 regulatory domain files Linksys labels at10k board data with "AH" belongs? Mar 20 23:53:17 (No obvious clues in the OEM firmware, AH is the output of a binary SKU decoder) Mar 21 00:18:40 Those files disable 52-64 and 100-144 if that helps Mar 21 00:48:07 -AH is Linksys SKU suffix for CN and probably a few more Mar 21 01:10:57 not sure if this belong to devel or the regular channel, but I was wondering if there was a reason why an image which is below the size limit doesn't boot Mar 21 01:11:23 Boot log? Mar 21 01:11:27 all I remember is that it's "too big", but why is that? and is there a way to know the limit Mar 21 01:12:06 let's say I build an image below the 8Mb, but it's too close to 8Mb, so it won't boot/work Mar 21 01:12:21 and I have to remove a few things so it can boot Mar 21 01:12:31 Boot, or save settings? Mar 21 01:12:38 boot Mar 21 01:12:44 is there a need for a certain amount of free space? Mar 21 01:13:12 let's say I build an image, flash it and it doesn't work/boot Mar 21 01:13:35 I don't really know how to phrase it differently Mar 21 01:13:46 just provide the log :) Mar 21 01:13:55 I don't have any log Mar 21 01:13:58 :+1: Mar 21 01:13:58 it's in general Mar 21 01:14:05 router doesn't really matter Mar 21 01:14:13 Nothing with embedded is "in general" ! Mar 21 01:14:22 the error does matter Mar 21 01:14:31 too big seems like image build error Mar 21 01:14:33 I've always heard that if the image gets too close to the flash memory limit, it won't work/boot Mar 21 01:15:03 If the image is too large, there won't be enough free blocks in the JFFS2 overlay, so it is unwritable. Mar 21 01:15:27 "work" and "boot" are entirely different things Mar 21 01:15:50 in this case, just boot I guess Mar 21 01:16:02 why would there need to be free blocks in JFFS2? the image is pretty much read-only Mar 21 01:17:12 configuration is already there I'd assume, so there is already enough to build Mar 21 01:17:24 Config is set "on the fly Mar 21 01:18:05 usually even the"corner case" of image still building (as in just enough space to generate the sized image) but just so full that there isn't any free space available for R/W, usually stuff still boots... if not, then at least to safe mode.. ofcourse non-workable in R/O state in normal boot, yeah... Mar 21 01:18:12 by scripts in /etc/uci-defaults Mar 21 01:19:14 Mister_X: because openwrt does use config files.. it essentially needs RW partition unless one builds highly specialised thing that has all settings ans such ready.. not the normal way an owrt image works Mar 21 01:20:01 ok Mar 21 01:20:19 openwrt buildroot should ofcourse not generate images that won't fit etc.. thus sometimes peoples wonder why no images built for certain device as they choose too many big packages to bake in... Mar 21 01:20:41 ie you never should have an image that will not actually fit Mar 21 01:28:01 so should yo ureally get image that isn't bootable at all would be very serious bug somewhere... which would need some logs or something.. impossible to even try guess what Mar 21 01:28:47 Even something as bizarre as a kernel too big to be able to uncompress itself isn't likely with 8 MB of flash and likely 32 MB or RAM or more Mar 21 01:30:59 well... there IS possibility of similar things like with tplink wdr4900 lately.. oem uboot crappyness that makes kernel crc fail if kernel over certain size.. which lately it is.. Mar 21 01:31:29 but.. again... can't know without logs... tough with similars one really needs TTL-serial connection and that way **** ENDING LOGGING AT Thu Mar 21 02:59:57 2019