The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.
--- Begin Message ---
Sorry for resubmitting this but yesterday I submitted without a subject...
I'm a CS student and I've used OpenWrt for years. I'm writing to this
mailing list because I'd like to contribute to the project by adding
support of the aformentioned device.
From what I can see, there's already an open PR
(https://github.com/openwrt/openwrt/pull/3762). I've merged the current
master into my fork (https://github.com/eutampieri/openwrt) and I've
built it. I can boot it from ramdisk but as soon as I flash the
sysupgrade I get this into the serial log:
>|Kernel panic - not syncing: No working init found. Try passing init=
option to kernel. See Linux Documentation/admin-guide/init.rst for
guidance.|
As far as I can tell, the init var isn't passed from the bootloader
(uboot), but how can I fix this?
Thanks to Benjamin Kallus we've found that the problem may lay here:
[ 0.433506] 0x000002280000-0x000003f40000 : "firmware"
[ 0.441125] 2 uimage-fw partitions found on MTD device firmware
[ 0.447182] Creating 2 MTD partitions on "firmware":
[ 0.452225] 0x000000000000-0x0000005c0000 : "kernel"
[ 0.458674] 0x0000005c0000-0x000001cc0000 : "rootfs"
[ 0.464437] mtd: device 12 (rootfs) set to be root filesystem
[ 0.471011] mtdsplit: no squashfs found in "rootfs"
When I download the mtdblock for rootfs, I get
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
0 0x0 JFFS2 filesystem, big endian
10223696 0x9C0050 Zlib compressed data, compressed
10224308 0x9C02B4 Zlib compressed data, compressed
10225004 0x9C056C Zlib compressed data, compressed
Regards,
Eugenio Tampieri
Il 25/02/22 14:23, Benjamin Kallus ha scritto:
That's right; the rootfs doesn't need specific offsets, you just need
to tell the kernel which partition to use as the rootfs on the kernel
command line. Good luck getting things working!
On Fri, Feb 25, 2022 at 1:15 PM Eugenio Tampieri
<euge...@eutampieri.eu> wrote:
First of all, thanks for your reply.
Second thing, sorry for the empty subject in my previous email. I
was caught off guard by the (totally sane and agreeable) rejection
of multipart HTML emails so I missed the subject.
About the rootfs: I already have the dumps, just not with me. I'll
try with different offsets. Does the rootfs partition need to have
a particular label (i.e. rootfs)? I thought that by pointing the
bootloader to it was enough.
Thanks again,
Eugenio Tampieri
--- End Message ---
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
