chomick, > root@debian:/boot# package architecture (armel) > does not match system (armhf) > > is there anyway to fix this? Make sure you installing the MVEBU kernel linux-6.4.11-mvebu-tld-1-bodhi.tar.bz2. Sounds like you're installing the wrong kernel (i.e Kirkwood). If you meant "Debian package" then your apt source might be wrong.by bodhi - Debian
Billy, Reminder: if you have the mtd0 backup for this box, you can kwboot with the NSA325 u-boot (or the mtd0 backup file itself), and then flash the mtd0 backup in Debian. Also you can flash it in serial console (I can't recall if I've shown you how in this thread).by bodhi - Debian
Kernel linux-6.4.11-mvebu-370xp-tld-1 package has been uploaded. Please see 1st post for download link.by bodhi - Debian
The 6.4.11-kirkwood-tld-1 kernel download link problem has been fixed in the 1st post.by bodhi - Debian
The 6.4.11-mvebu-tld-1 kernel download link problem has been fixed in the 1st post.by bodhi - Debian
All, I've fixed the download links in the 2 kernel release threads. Please try again.by bodhi - Debian
OK it seems to have some problem for at least 2 users. Stay tuned on this thread.by bodhi - Debian
Hi Trond, QuoteIf you create a release for Netgear RN102 and RN104 too, I'll be eager to check it out. Sure I will.by bodhi - Debian
Is anybody having problem downloading the new 6.4.11 kernels? https://forum.doozan.com/read.php?2,32146 https://forum.doozan.com/read.php?2,12096 Dropbox seems to have changed their URL format. Please let me know.by bodhi - Debian
Billy, We went through this excercise before, somewhere in this thread. You can run kwboot and boot into Debian rootfs on USB.by bodhi - Debian
Kernel 6.4.11-mvebu-tld-1 package has been uploaded. See 1st post for download link. Please create a new thread for any installation problem or questions.by bodhi - Debian
Kernel linux-6.4.11-kirkwood-tld-1 package has been uploaded. See 1st post for download link. And please create a new thread for any installation problem or question.by bodhi - Debian
Did you create an Ext3 partition on the HDD and populate it with the rootfs tarball (the same way you did for the USB rootfs)?by bodhi - uBoot
superdm83, > It's not clear to me why should be reverse the > uImage to the original (it is in contrast with > point 4 of the installation procedure (here: > https://forum.doozan.com/read.php?2,12096) ? -NOT > SURE, I'm trying to understand ) That was because initially, you had created the rootfs to boot with stock u-boot. Quote4. (Stock u-boot only) Creaby bodhi - uBoot
nslick, > For the ds218j, the following works: > > dram: > > > +static struct mv_ddr_topology_map > board_topology_map = { > + DEBUG_LEVEL_TRACE, > + 0x1, /* active interfaces */ > + /* cs_mask, mirror, dqs_swap, ck_swap X > PUPs */ > + { { { {0x1, 0, 0, 0}, > + {0x1, 0, 0, 0}, > + {0x1, 0by bodhi - uBoot
> This box has Armada 380 SoC, so no need to compile > cryptodev. The driver used is armada-38x-crypto. > Also the rootfs > Debian-5.13.8-mvebu-tld-1-rootfs-bodhi.tar.bz2 is > armhf. So you have all necessary parts regarding > encryption tasks. I might need to check one more thing regarding encryption tasks for this box. I forgot whether the crypto SRAM definitions are nby bodhi - Debian
> Just to clarify... Are you using the samba > backports (v4.17.10) or the stock bullseye one > (v4.13.13)? I only seem to have slowdown issues > while using v4.17.10. The stock bullseye.by bodhi - Debian
superdm83, If you are not installing the new u-boot and its default envs image, but trying to boot Debian from kwboot first, then there are 2 methods: 1. kwboot with the 2017.07 image from the release thread: uboot.2017.07-tld-1.nsa325.mtd0.kwb (This older u-boot version has the correct internal envs) OR 2. kwboot with the uboot.2023.04-tld-1.nsa325.kwb using the instructionby bodhi - uBoot
Nuno, > As it stands, I am a bit weary of upgrading to > bookworm or installing other backports... I'm still on Debian bullseye for my GF Home boxes, which are my main NAS for streaming videos and music. And I have not noticed any slow down. For a closed home network environment, and with good hygiene (not using any thing from unknown sources), security is not much of a concern.by bodhi - Debian
Also, check your dmesg for armada-38x-crypto.by bodhi - Debian
Pachis, > After investigating I noticed a thing that could > be relevant and is that latest kernel lacks the > cryptodev module > (https://github.com/cryptodev-linux/cryptodev-linux), > you can check that /dev/crypto is non existant in > 6.3.8 kernel, but it exists in stock firmware > kernel. This box has Armada 380 SoC, so no need to compile cryptodev. The driverby bodhi - Debian
Rudy, > I'm wondering what additional steps will be > required after I follow the instructions here to > upgrade to the 'Bookworm' edition? The latest rootfs is Debian-5.13.8-mvebu-tld-1-rootfs-bodhi.tar.bz2. You can use that instead of the old rootfs (Debian-5.2.9-mvebu-tld-1-rootfs-bodhi.tar.bz2) stated in the installation instruction. And each of these releasby bodhi - Debian
Peter, Quite possible that either: 1. Since you had a few kernel panics and had to turn off power, the rootfs might have file system errors. Try mounting the USB rootfs on another Linux box and check for error. Assuming the USB drive is assigned /dev/sdb, e2fsck /dev/sdb1 OR 2. The rootfs was not created properly. QuoteInstallation: Installation can be done on any Linux boby bodhi - uBoot
Peter, Your rootfs uImage was set up to boot with the DTB embbeded (Step 4) Now you are running the new uboot 2017.07, so you also need to adjust your rootfs to boot with separated DTB. Mount your USB rootfs on another Linux box, and restore the original uImage. Assuming it is mounted at /media/sdb1 Reverse uImage to the original. cd /media/sdb1/boot cp -a uImage uImage.with_by bodhi - uBoot
Quote- ------------------------------------------------------------------------- Debian Security Advisory DSA-5477-1 security@debian.org https://www.debian.org/security/ Moritz Muehlenhoff August 14, 2023 https://www.debian.org/security/faq - ------------------------------------------------------------------------- Packageby bodhi - Debian
Peter, There are a few different possible reasons for this booting problem. Please post the entire serial boot log (from u-boot banner until the kernel panic).by bodhi - uBoot
Pachis, > No way to install debian on NAND?. This box NAND flash is too small for Debian rootfs. > Maybe the hdd would be an alternative, but I'm > worried about it not being able to sleep and spin > down. I would not worry about HDD not spinning down. However, if you really want to keep the HDD sleeping most of the time, you can run the rootfs on USB. Takeby bodhi - Debian
dhargens, > mkfs.ext3 -L rootfs -E lazy_itable_init=0 /dev/sda1 No need to have extra option.That should be: mkfs.ext3 -L rootfs /dev/sda1 sync > CE>> boot > Unknown command 'usb' - try 'help' > > ** Block device usb 0 not supported The error is because stock u-boot does not support USB commands. > Ok, so that doesn't workby bodhi - uBoot
Also, the 2Big2 u-boot is in mainline (with USB and SATA supports). https://github.com/u-boot/u-boot/tree/master/board/LaCie/net2big_v2 The 2Big2 u-boot should boot the 5Big2 with USB or SATA rootfs (at least one SATA port should work).by bodhi - Debian