BenG83 has quit [Remote host closed the connection]
AneoX has joined #linux-sunxi
AneoX has quit [Client Quit]
parazyd has quit [Quit: leaving]
parazyd has joined #linux-sunxi
<ChriChri>
I have a file that starts with the magic 'sunxi-package'. It starts with sections named 'u-boot' (0x40), soc-cfg (0x1b0) and dtb (0x320). Size is 664kb. I suspect that it contains a u-boot and all the additional needed stuff to start a b288, but I can't find how to unpack it to get the single files. https://pastebin.com/8bz7Qkbp Any ideas or help?
hipboi has joined #linux-sunxi
hipboi has quit [Client Quit]
reinforce has quit [Quit: Leaving.]
florian has joined #linux-sunxi
MoeIcenowy has quit [Quit: ZNC 1.6.5+deb1+deb9u1 - http://znc.in]
MoeIcenowy has joined #linux-sunxi
elros1 has joined #linux-sunxi
elros1 has quit [Remote host closed the connection]
<ChriChri>
plaes: The board is a Pocketbook 740 aka Inkpad 3. Had a broken screen so I went into it ;-)...
<ChriChri>
About the sunxi-package: Got further and identified the start and length of the parts in the header. Now I have (for a start) a uboot.bin from that file.
BenG83 has quit [Ping timeout: 240 seconds]
megi has joined #linux-sunxi
<ChriChri>
I thought (naive) that I could just load it to the board by sunxi-fel, but it complains: "SPL: eGON header is not found". Well, I have an spl already, but I still don't know how to fit them together in one file...
florian_kc has joined #linux-sunxi
florian has quit [Ping timeout: 265 seconds]
tllim has quit [Read error: Connection reset by peer]
<kilobyte_ch>
Hello, I'm using legacy sunxy kernel with nand flash. I have multiple nand partitions which are formated with ext4. I always get ext4 fs errors after running devices with this configuration for a certain time. Is this a known issue?
<mru>
do not use ext4 on raw nand
<kilobyte_ch>
mru: ok, what's the solution? Using ubifs?
<mru>
yes, use ubifs
<kilobyte_ch>
mru: is this even possible with the old legacy kernel and these strange factory images you need to build?
<plaes>
kilobyte_ch: nope
<kilobyte_ch>
plaes: so what's the soltuon? throw away all legacy kernel allwinner nand boards? :)
<DuClare>
Install new kernel
<DuClare>
:)
<kilobyte_ch>
Unfortunately I need the TVIN. Thus I can't use the mainline Kernel.
<DonkeyHotei>
DuClare: last i checked, mainline still doesn't support nand
<DuClare>
Eh?
<DuClare>
Maybe there's a specific chip it doesn't support
<DuClare>
But nand in general should not be a problem
<DuClare>
Shows green or probably-green for most boards
<mru>
MLC nand isn't supported in mainline, at least not well
lkcl has joined #linux-sunxi
florian has joined #linux-sunxi
florian_kc has quit [Ping timeout: 265 seconds]
<DonkeyHotei>
mru: yes, that was what i meant
<mru>
does your board have mlc flash?
<DonkeyHotei>
it gets detected but can't be used
<DonkeyHotei>
i have one
<mru>
my usual advice is if you need more than ~512MB of storage, use eMCC
netlynx has quit [Quit: Ex-Chat]
<plaes>
eMMC :P
<mru>
it works
<plaes>
yup :)
<mru>
yes, you're at the mercy of its controller
<plaes>
can confirm.. I have 100+ sunxi devices with eMMC running 24/7
<mru>
but I have yet to encounter a problem caused by eMMC
<plaes>
I had occasional issues due to corrupt filesystem due to power interruptions, but I got past these after I added `fsck.repair=yes fsck.mode=force` to kernel args