Show all posts by user

Re: 2023.04 U-Boot MVEBU -- Armada 38x - Yesterday

Brian, Yes, this u-boot is a bit old for the new DS116 boot.scr. Try creating the script like you did here https://forum.doozan.com/read.php?3,133945,140004#msg-140004 And boot automatically.

by bodhi - uBoot

Re: 2023.04 U-Boot MVEBU -- Armada 38x - Yesterday

Strange, it looks like it should work Scanning usb 0:1... Found U-Boot script /boot/boot.scr 1146 bytes read in 2 ms (559.6 KiB/s) ## Executing script at 01800000 Booting with N2350 distro boot script loading uImage from usb 0:1 ... 5173840 bytes read in 73 ms (67.6 MiB/s) loading uInitrd from usb 0:1 ... 5268566 bytes read in 69 ms (72.8 MiB/s) loading DTB file from usb 0:1 ... Fa

by bodhi - uBoot

Re: Debian on Synology DS215j - Yesterday

ZooMoo, > To build the ancient and modified Synology kernel > you need to use their chroot'ed build > environment. > Amazingly it boots, but it fails with the > following errors and drops down to a initramfs > prompt. > > > [ 71.628934] Archive bit cmd:7ec67b40 not > implement. > [ 71.633909] Archive bit cmd:7ec67b08 not > implement.

by bodhi - Debian

Re: 2023.04 U-Boot MVEBU -- Armada 38x - 2 days ago

Brian, Let me write the flashing instruction (in the next few days or weeks if I can). It will save you some headache :) there is an established procedure what to do when you flash new u-boot and envs image. You could also post what you think you need to do next and I'll comment on it. But now that you know you can recover the box with kwboot, you could experiment. > Maybe we al

by bodhi - uBoot

Re: 2023.04 U-Boot MVEBU -- Armada 38x - 2 days ago

Hi Brian, > Using your boot.scr, kwboot booted the USB rootfs > all the way to debian login prompt successfully. Cool! > > The only problem seems to be the ethernet mac > address not quite right. I'm going to hard-code it > in debian network config for the moment. Yes, it is a random local MAC address when you kwboot this way. So that's the best way to

by bodhi - uBoot

Re: 2023.04 U-Boot MVEBU -- Armada 38x - 2 days ago

Brian, Download the attached uboot.2025.07-rc5-tld-1.ds116.boot.scr and copy it to your rootfs /boot. I also attached the boot.cmd used to create the boot.scr. cd /boot cp -a uboot.2025.07-rc5-tld-1.ds116.boot.scr boot.scr sync and run kwboot, reboot the box.

by bodhi - uBoot

Re: 2023.04 U-Boot MVEBU -- Armada 38x - 2 days ago

Brian, > Cannot read environment, using default > Cannot read default environment from file > <13>Jul 8 08:58:40 root[2206]: Cannot read u-boot > env ethaddr The default envs image has not been flashed. So atm you can't see the envs in Debian yet. The error above is OK. Check the MAC address in dmesg, you'll see it is mvneta f1070000.ethernet eth0: Us

by bodhi - uBoot

Re: 2023.04 U-Boot MVEBU -- Armada 38x - 2 days ago

This post is in the Wiki: How to create a u-boot boot script on USB rootfs https://forum.doozan.com/read.php?2,136786,136978#msg-136978 After you'v created the boot script, I'll come back and show you how to boot that automatically (no manual interaction) after kwboot started.

by bodhi - uBoot

Re: 2023.04 U-Boot MVEBU -- Armada 38x - 3 days ago

Brian, > I got the ds116, hooked up serial. > > Tried tftp boot with stock uboot to usb rootfs > (following the relevant part of ds116 usb rootfs > installation), success. > Tried kwboot uboot.2025.07.07-rc5 next with the > same usb rootfs (with uImage reverted to the > original), success. The boot log looks flawless! > > I don't know how to s

by bodhi - uBoot

Booting Kirkwood SoC NAS with stock u-boot - 4 days ago

Boot Kirkwood rootfs with stock u-boot Check this u-boot release thread to see if there is new u-boot support for your box. If not then this is the instruction for how to boot Debian. There are 3 methods. Pick one that your stock u-boot supports. Method 1 is the preferred procedure. 1. Booting with stock u-boot that supports usb, ext2load, and run commands 2. Booting with stock u-boot

by bodhi - Debian

Re: Boot Kirkwood rootfs with stock u-boot - 4 days ago

KodexMedia, > it sounded like there may have been some kind of > IDE to SATA thing going on on this motherboard, or > at least there was 2 SATA controllers which was > why many has trouble getting all 4 drive bays to > work. Yes. I actually saved the post where this box was booted off USB rootfs, and then in Debian all 4 drives were spun up by the kernel. Tested by Co

by bodhi - Debian

Re: Zyxel NSA310 - questions after Debian install - 4 days ago

tmcatalin, > Regarding `printenv' I am attaching the output of > 'fw_printenv'. BTW, is any difference between > them? > Only if you have modifed the envs after installation. Otherwise, with the default envs, it will try to boot USB and then if failed, it will automatically try SATA. I like to see how the box boots with u-boot and then the kernel booting. I

by bodhi - Debian

Re: Zyxel NSA310 - questions after Debian install - 5 days ago

tmcatalin, > 1. ethernet MAC address is `00:00:00:00:00:30` > despite the fact it is set in setenv: > root@nsa310:~# fw_printenv ethaddr > ethaddr=50:67:XX:YY:ZZ:XY So this box behaves like other MVEBU boxes. You can set the correct MAC address 2 different ways: a. Use the attached script to set it to ethaddr after it booted. Put this set_persistent_mac_address scrip

by bodhi - Debian

Re: Boot Kirkwood rootfs with stock u-boot - 6 days ago

KodexMedia, I'm assuming you are referring to this instruction (I should have moved it out to its own thread): Boot Kirkwood rootfs with stock u-boot https://forum.doozan.com/read.php?2,102054,105374#msg-105374 1. Booting with stock u-boot that supports usb, ext2load, and run commands 2. Booting with stock u-boot that does not supports usb, ext2load, and run commands 3. Booting

by bodhi - Debian

Re: Help unbricking IOmega ix4-200d - 9 days ago

Rodrigo, > Hi again, do you know why the > Debian-6.5.7-kirkwood-tld-1-rootfs-bodhi.tar.bz2 > didn't work.. just curiosity. This stock u-boot might have some limitation regarding the size of the kernel. You are booting using a set of envs that are not from my recommendation. See here: Boot Kirkwood rootfs with stock u-boot: https://forum.doozan.com/read.php?2,102054,

by bodhi - uBoot

Re: 2023.04 U-Boot MVEBU -- Armada 38x - 10 days ago

Attached is the latest uboot for DS116. It's only a few days before the mainline u-boot 2025.07 will be released, so I'd expect there will be no significant change upstream. uboot.2025.07-rc5-tld-1.ds116.kwb sha256: a161d56317ee9f0cb8e883ed81b61e4796f6a82ee114c7f276d24b15389ff760

by bodhi - uBoot

Re: Using 2015.10 U-Boot for Pogoplug V3 (OXNAS OX820) with AKiTio MyCloud Mini - 10 days ago

tiramisu376, > After flashing the U-Boot with > ‘CONFIG_SYS_NAND_5_ADDR_CYCLE’ enabled, the > NAND version of the 2015.10 U-Boot now boots > successfully. Nice! Let me move this thread to U-Boot subforum.

by bodhi - uBoot

Re: 2023.04 U-Boot MVEBU -- Armada 38x - 10 days ago

Here is the default envs for Synology DS116.

by bodhi - uBoot

Re: 2023.04 U-Boot MVEBU -- Armada 38x - 10 days ago

eno789, > Question, on DS116/DS216/RS816, if this release > candidate U-Boot tests okay, we no longer need to > flash uImage to mtd for USB rootfs boot, or write > uImage/uInitrd to raw sectors for SATA rootfs > boot, right? Exactly, it is a full feature u-boot. There is no limitation as how you want to boot the box. You can boot straight from USB or HDD rootfs. I'

by bodhi - uBoot

Re: Help unbricking IOmega ix4-200d - 11 days ago

> Update, i try with > Debian-5.13.6-kirkwood-tld-1-rootfs-bodhi.tar.bz2 > and start.. so far, I must change some parts > beacuse dont find the roorfs, I must put a label > to the partition on the usbstick Yes, the instruction: Quote1. Format a new USB drive with a single Ext3 partition, and label it rootfs. This step should be done at Linux command line using fdisk, mkfs

by bodhi - uBoot

Re: GTI Mirabox, Netgear RN102/RN104, Netgear RN2120 Installation & Kernel Upgrade (Linux-6.15.2) - 14 days ago

adrien60, Thanks for the feedback!

by bodhi - Debian

Re: Debian on Synology DS112 v10j - 15 days ago

BayPanard, > Do you need me to boot debian using stock uboot > with tftp boot? or using your uboot with esata > booting? It's really the same in Debian (everything should be working with either boot method). But please do eSATA booting with new u-boot.

by bodhi - Debian

Re: GTI Mirabox, Netgear RN102/RN104, Netgear RN2120 Installation & Kernel Upgrade (Linux-6.15.2) - 15 days ago

Kernel linux-6.15.2-mvebu-370xp-tld-1-bodhi.tar.bz2 package has been uploaded. Please see 1st post for download link.

by bodhi - Debian

Re: Linux Kernel 6.12.6 MVEBU package and Debian armhf rootfs - 15 days ago

Kernel 6.15.2-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

Re: Linux Kernel 6.11.6 Kirkwood package and Debian rootfs - 15 days ago

Kernel linux-6.15.2-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

Re: Debian on Synology DS112 v10j - 18 days ago

BayPanard , Log into Debian and lspci lspci -vvv Please post the output here.

by bodhi - Debian

Re: Synology DS214+ - 18 days ago

eno789, Looks for Synology NAS with Armada 385 or 388 SoC. They have a lot more support, therefore quite stable. I'd avoid Armada 375 and XP because the potential problems (some are working fine, some seeing PCI SATA problem).

by bodhi - Off-Topic

Re: Debian on Synology DS112 v10j - 18 days ago

BayPanard, > Okay seems like having a working modern uboot on > this box is not an easy task, You can boot with eSATA rootfs in the mean time.

by bodhi - Debian

Re: Synology DS214+ - 18 days ago

Sorry, I have bad news! this box PCI bus has some issues in Linux.

by bodhi - Off-Topic

Re: Debian on Synology DS112 v10j - 19 days ago

BayPanard, Thanks! looks like I need to rebase this u-boot to 2025.07-x to make sure we don't miss other indirect bugs. The good thing is what we found out about "unable to assign mbus window for io" error is a real bug and I will send that patch to U-Boot. The difficulty is the Linux driver for MVEBU PCI is quite different from the U-Boot version. So even though we know it&#

by bodhi - Debian