[From nobody Thu Jun 25 05:55:05 2020 Received: from mail-yw1-xc32.google.com ([2607:f8b0:4864:20::c32]) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1h2zWD-0004oE-Ut for openwrt-devel@lists.openwrt.org; Sun, 10 Mar 2019 14:33:40 +0000 Received: by mail-yw1-xc32.google.com with SMTP id a199so936112ywa.0 for <openwrt-devel@lists.openwrt.org>; Sun, 10 Mar 2019 07:33:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=olmari.fi; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=LN6qS7npNprLG3bU0kZTXNJHKNhvEzLbkTxpM7DtCrQ=; b=WoAQkbjbuTCNFCSYV9ozHfhhkc7DDrxRwu0kzg9KxDW5TX/83ZciIalmLtHIQlkTVe SMS2Fd0lP4L8udcPJMCLWLDtzVBbrqTf59/cMT/pm1e4zWWm32hNevOjZMyuLQsdIZaE RWEHw3SGqSoGoi1wrnNU+f4WwUpmx2U3LStXViBvvekhgpCLONlg+XZopYwfsOgsVMeZ W2rDV/gdvAgQEbiR2kkizgs/OnIDARKrBmRRZfR0f8ZCb58TmuD45zNdmJGNcyEwSe/N odHwE8swmwtMx3X+dSlA+2aZgpnsZPG7m49ufpuln1FcIRtZ0Z/sFMmR/ypAZ9a3tRFN BguQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=LN6qS7npNprLG3bU0kZTXNJHKNhvEzLbkTxpM7DtCrQ=; b=Q0ssuLv83s63gkqxFLjET1YyZEQAr8pG6qKZWkNMoL5MIcnsyW9bwT/Dae4JqnP+XE bghd8csl2ZEGau7v4rvhJhBT0Gfg1beqRr1xKtGXEr5SHyiqO8RE7sOIq0xcmPmN6xGK X1kes7ig+juNlI+iPRuHrEiv0YjqtH5O7rfaxwQPtwM/OQ6ERtMRQVWIYwgkw5znG+sW i9i/YQT2PmVv4/PfQj7rMDR4Yxkj8rkQJ86jQCP3fdnDG+zFBJWp3+pT02cDbHmXWuT9 RW1NuwC+3QeX+JBB2JMrGmp1xMIVlmlWS/JCQb+mhOCmaknAARSb9lcP4XKVTe33um4O SBBg== X-Gm-Message-State: APjAAAVLkHQCFUxui7gA1OHRNhY/aiqO29zwvIBHVkD3my8Vblu3UQ6v FU7vwP56Pfof64suCLblJ3AdY5zUg0eR6uC4YFLmWA== X-Google-Smtp-Source: APXvYqxOCrd1FmrDd6pp+MR5Ic0EtBduZosCRl+ZfJ7C6smh5sejXthCkrV3jn6AN6KrAqqKA/4kBKgYLWRu9GlR3Ks= X-Received: by 2002:a25:d656:: with SMTP id n83mr22636864ybg.423.1552228415581; Sun, 10 Mar 2019 07:33:35 -0700 (PDT) MIME-Version: 1.0 References: <mailman.25981.1552219601.2376.openwrt-devel@lists.openwrt.org> <mailman.25989.1552224733.2376.openwrt-devel@lists.openwrt.org> <79c2718f-7910-9cd6-8fc7-9597629d9c58@gmail.com> In-Reply-To: <79c2718f-7910-9cd6-8fc7-9597629d9c58@gmail.com> From: Sami Olmari <sami@olmari.fi> Date: Sun, 10 Mar 2019 16:33:21 +0200 Message-ID: <CAENOc+zH-gbmgrqUv+tBSJdKa+m3wXbXb1SFy2BQjtAuox=T2w@mail.gmail.com> Subject: Re: [OpenWrt-Devel] Trunk tl wdr4900 v1 boot fails on bootloader CRC check To: Alberto Bursi <bobafetthotmail@gmail.com> Cc: openwrt-devel <openwrt-devel@lists.openwrt.org>, Christian Lamparter <chunkeey@gmail.com> Content-Type: multipart/alternative; boundary="0000000000005251d60583be5729" X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190310_073338_161776_CE49BD83 X-CRM114-Status: GOOD ( 13.26 ) X-Spam-Score: -0.2 (/) X-Spam-Report: SpamAssassin version 3.4.2 on bombadil.infradead.org summary: Content analysis details: (-0.2 points) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at https://www.dnswl.org/, no trust [2607:f8b0:4864:20:0:0:0:c32 listed in] [list.dnswl.org] -0.0 SPF_PASS SPF: sender matches SPF record 0.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain -0.1 DKIM_VALID_EF Message has a valid DKIM or DK signature from envelope-from domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature --0000000000005251d60583be5729 Content-Type: text/plain; charset="UTF-8" On Sun, Mar 10, 2019 at 4:20 PM Alberto Bursi <bobafetthotmail@gmail.com> wrote: > > On 10/03/19 21:32, Sami Olmari via openwrt-devel wrote: > > Okay it wasn't > > > https://github.com/openwrt/openwrt/commit/576c69938bb38c7edfa23f220eb30cb5c1d0a726 > > nor the immediately next one > > > https://github.com/openwrt/openwrt/commit/0fbd3d23aadee0d95beef4f077a866dae7f4841a > > so it's still unclear what commit really breaks this... but I'll try > > to keep looking.. :) > > > > -- > > Sami Olmari > > _______________________________________________ > > openwrt-devel mailing list > > openwrt-devel@lists.openwrt.org > > https://lists.openwrt.org/mailman/listinfo/openwrt-devel > > > The issue isn't a specific commit. > > The issue is the kernel is too big. > > The bootloader of this device only reads 0x29F000 bytes in hex or > > 2748416 bytes, around 2.6Mb in decimal. > > > In the Github PR (1) they see they can only work around this by > > making an u-boot bootloader that can be loaded instead of the kernel. > > Then this u-boot will load the kernel with no limitations. > > > -Alberto > > > [1] https://github.com/openwrt/openwrt/pull/1773 > Shouldn't this alleviate that? https://github.com/openwrt/openwrt/commit/576c69938bb38c7edfa23f220eb30cb5c1d0a726 " Currently, the image creation process for the TP-Link tl-wdr4900-v1 needs a fixed sized kernel and places the rootfs partition at a fixed offset. With the upcoming move to 4.19 the kernel will no longer fit into the existing allocated space for the kernel partition. This patch converts the device to utilize the established tplink,firmware mtdsplitter, which can deal with a dynamic kernel/rootfs size. " Not that I really know too good, I'm still just eager user more than developer... Anyway, All I can then hope a fix is introduced... I am more than willing to alpha/betatest :) -- Sami Olmari --0000000000005251d60583be5729 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr"><br><div class=3D"gmail_quote"><div dir= =3D"ltr" class=3D"gmail_attr">On Sun, Mar 10, 2019 at 4:20 PM Alberto Bursi= <<a href=3D"mailto:bobafetthotmail@gmail.com">bobafetthotmail@gmail.com= </a>> wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:= 0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">= <br> On 10/03/19 21:32, Sami Olmari via openwrt-devel wrote:<br> > Okay it wasn't <br> > <a href=3D"https://github.com/openwrt/openwrt/commit/576c69938bb38c7ed= fa23f220eb30cb5c1d0a726" rel=3D"noreferrer" target=3D"_blank">https://githu= b.com/openwrt/openwrt/commit/576c69938bb38c7edfa23f220eb30cb5c1d0a726</a> <= br> > nor the immediately next one <br> > <a href=3D"https://github.com/openwrt/openwrt/commit/0fbd3d23aadee0d95= beef4f077a866dae7f4841a" rel=3D"noreferrer" target=3D"_blank">https://githu= b.com/openwrt/openwrt/commit/0fbd3d23aadee0d95beef4f077a866dae7f4841a</a> <= br> > so it's still unclear what commit really breaks this... but I'= ll try <br> > to keep looking.. :)<br> ><br> > -- <br> > =C2=A0Sami Olmari<br> > _______________________________________________<br> > openwrt-devel mailing list<br> > <a href=3D"mailto:openwrt-devel@lists.openwrt.org" target=3D"_blank">o= penwrt-devel@lists.openwrt.org</a><br> > <a href=3D"https://lists.openwrt.org/mailman/listinfo/openwrt-devel" r= el=3D"noreferrer" target=3D"_blank">https://lists.openwrt.org/mailman/listi= nfo/openwrt-devel</a><br> <br> <br> The issue isn't a specific commit.<br> <br> The issue is the kernel is too big.<br> <br> The bootloader of this device only reads 0x29F000 bytes in hex or<br> <br> 2748416 bytes, around 2.6Mb in decimal.<br> <br> <br> In the Github PR (1) they see they can only work around this by<br> <br> making an u-boot bootloader that can be loaded instead of the kernel.<br> <br> Then this u-boot will load the kernel with no limitations.<br> <br> <br> -Alberto<br> <br> <br> [1] <a href=3D"https://github.com/openwrt/openwrt/pull/1773" rel=3D"norefer= rer" target=3D"_blank">https://github.com/openwrt/openwrt/pull/1773</a><br> =C2=A0</blockquote><div><br></div><div><br></div><div>Shouldn't this al= leviate that? <a href=3D"https://github.com/openwrt/openwrt/commit/576c6993= 8bb38c7edfa23f220eb30cb5c1d0a726">https://github.com/openwrt/openwrt/commit= /576c69938bb38c7edfa23f220eb30cb5c1d0a726</a></div><div><br></div><div>&quo= t;<br><pre>Currently, the image creation process for the TP-Link tl-wdr4900= -v1 needs a fixed sized kernel and places the rootfs partition at a fixed offset. With the upcoming move to 4.19 the kernel will no longer fit into the existing allocated space for the kernel partition. This patch converts the device to utilize the established tplink,firmware mtdsplitter, which can deal with a dynamic kernel/rootfs size.<br><br>"<br><br></pre><pre>Not that I really know = too good, I'm still just eager user more than developer... Anyway, All = I can then hope a fix is introduced... I am more than willing to alpha/beta= test :)<br><br>-- <br></pre><pre> Sami Olmari<br></pre></div></div></div></= div> --0000000000005251d60583be5729-- ]