> I tried everything - filesystems from ext2 till > ext4, and volume size from 32Gb till 4Gb. But it > didn't help. > > fdisk /dev/sdd > n > p > 1 > Enter > Enter > w We usually do the "O" command to wipe the disk partition(s) first. And this wipe resets the partition table. fdisk /dev/sdd o n p 1 Enter Enter w > Nowby bodhi - Debian
Nikola204, > Sooooo....I made it! Now I'm looking at the > Debian's console, but the problem was in USB > Drive! I changed USB 3 to USB 2 drive and did the > same steps according to the manual. And now > everything works! You must have some misstep somewhere. If I had set the env to use USB 3.0 then it did work for me. How did you create the partiton on theby bodhi - Debian
Sash, > but no, nothing new. OK. So it seems to be stuck in starting u-boot (i.e. some weird state in the strapping register was set). We need more debug configured in to hopefully see more info. Unfortunately, I'm out of time. If you want, check back here in a couple months, when I will be available with more free time.by bodhi - uBoot
Sash, > i tested the connection/cables to a ttl converter > and there it works. cables about 25cm. That what I meant. You need to use the USB ttl converter. Plug the USB converter into the good NSA325 (instead of the PHILAP0112), and run ARM kwboot on this box.by bodhi - uBoot
Ivan, > That's great, can I have btrfs support please? It will take a while. Not sure when. > > I also have an issue with a specific usb stick > that I want to use for swap, it doesn't get > recognized during uboot, nor kernel boot, but once > in Debian I just need to remove it and plug it > back in and it get's recognized. I have attached >by bodhi - uBoot
Sash, > root@PHILAP0112:# uname -a > Linux PHILAP0112 6.12.57+deb13-amd64 #1 SMP > PREEMPT_DYNAMIC Debian 6.12.57-1 (2025-11-05) > x86_64 GNU/Linux It is x86_64 box, so you can not use ARM binaries such as kwboot_2024.04-rc3 or or kwboot_static_2024.04-rc3. You have to use either the x86_64 binary kwboot_2025.01-rc1_x86-64, or one that comes with the distro on your PHILAP0112by bodhi - uBoot
Ivan, > The Seagate 465.7GB HDD was btrfs, so uboot was > not able to see it. I see. We do have btrfs support in u-boot. But of course, I did not turn it on for these u-boots. > I have formatted it to Ext4 > (there are no partitions), and with "finalized" > optiion: > > mkfs.ext4 -E lazy_itable_init=0 /dev/sdb > You should have at least 1 partiby bodhi - uBoot
Otto > unfortunately, the WakeUp script no longer working > since some kernel updates. > I starts the WOL from a Raspi via cron now. Yes, it's a good way to get around this rtc_wake problem. Last time I looked at the driver, mvebu suspend code seems to have a problem. Not sure if I want to try fixing it (not a simple task).by bodhi - Debian
Ivan, QuoteDS211> sata info Device 0: Model: ST3500418AS Firm: CC46 Ser#: 9VMRBDX5 Type: Hard Disk Supports 48-bit addressing Capacity: 476940.0 MB = 465.7 GB (976773168 x 512) Device 1: Model: WDC WD120EDAZ-11F3RA0 Firm: 81.00A81 Ser#: 5PK9RX2B Type: Hard Disk Supports 48-bit addressing Capacity:by bodhi - uBoot
AndreaCipcino, Have you tried what Otto did above? https://forum.doozan.com/read.php?2,137911,138165#msg-138165by bodhi - Debian
Joe, > I think it will be OK. I messed up the > environment and used > > setenv dtb_file /boot/dts/kirkwood-nsa320.dtb > boot > > to fix it, not sure After booting into Debian, you can do fw_printenv > current_envs.txt And then compare with the default envs Quotehttps://forum.doozan.com/read.php?3,12381 uboot.2016.05-tld-1.environment.img (the dby bodhi - uBoot
Joe, > Thanks again. I think the nandflash worked OK, I > was not able to do a few of the backup commands > such as fw_printenv > current_envs.txt It's OK. For first time installation, there is no envs to save, only relevant when you upgrade u-boot to newer version. > but it boots up and I can access it using ssh. > once again, thanks Cool!by bodhi - Debian
Hi Joe, The installation instruction is right below where you found the new u-boot image. It starts here: Quotehttps://forum.doozan.com/read.php?3,12381 A. Flashing Instruction: Installation is the same for each u-Boot image, the instruction below is written to include all boxes. So choose the platform name that you are installing for, and copy/paste the appropriate commands. Aby bodhi - Debian
joe, Since you are kwboot and booting with the new u-boot, you need to readjust the rootfs (you probably tried booting with stock u-boot before). Quotehttps://forum.doozan.com/read.php?2,140631,140631#msg-140631 4. (Stock u-boot only) Create uImage with embedded DTB for booting with older u-boots (2012 or earlier). Skip this step if you have installed the latest U-Boot for Kirkwood (orby bodhi - Debian
Attached here is the Dec 15 build. This build is to see if we can activate both SATA slots. uboot.2025.10-tld-1.ds211.bodhi.251215-2.tar sha256: 6d61b22d3342452763ea6fb48ecb193195de52b30d9f0b70da2448a4395e214f This tarball contains 5 files. Ony the image uboot.2025.10-tld-1.ds211.kwb is different from previous build. uboot.2025.10-tld-1.ds211.kwb uboot.2024.10-tld-1.ds211.environmenby bodhi - uBoot
Quote** Read outside partition 18446744057368543488 I must have missed something during rebase. Or I did not completely fix this bug :) UPDATE: The rebase was OK. My test HDD was 4TB. Perhaps there are more problem somewhere in the driver that I did not encounter, like with you did with your 12 TB HDD.by bodhi - uBoot
Attached here is the Nov 28 build. This build should fix the error "reading outside partition". The main interest is to test large HDDs > 2TB. But please do install the other HDD in the lower bay. It might not have the fix for 2 HDDs yet. I might need to revisit the code where the MPP and GPIOs are defined. uboot.2025.10-tld-1.ds211.bodhi.251215.tar sha256: 0712b1f1a81e06fby bodhi - uBoot
Ivan, Thanks! I will upload the newest version.by bodhi - uBoot
fgh, > I have an old NSA325 i bring out in daylight from > time to time. Plan now is to put it on 24/7-work > offsite for a while. So I returned back here for > some proper help and info. Ive just updated to > your latest kernel and Debian 12.12. Glad to hear!by bodhi - Debian
J1 serial port (right to left, outside looking in). 1. Square: Vcc 3.3V 2. TXD 3. RXD 4. GND Means after you open the case cover, you'll see the board is mounted perpendicular. Look at the right side of the board (outside looking in), J1 is at the lower left corner. The unpopulated header is 4 holes, horizontally ( in some other boards, the header is installed with 4 pins).by bodhi - Debian
Thecus N2350 Serial Console Header Pinouts Picture (working thread) https://forum.doozan.com/read.php?2,50829,54569#msg-54569 Pinouts: J1 serial port (right to left, outside looking in). 1. Square: Vcc 3.3V 2. TXD 3. RXD 4. GND Connect only TXD, RXD, and GND. Do not connect 3.3V. You could connect the wires temporarily to the 3 holes. No need to solder unless you want aby bodhi - Debian
Nikola204, > 2) I'm not so good at Linux and I don't understand > how this schema works. So I'd like to clarify, > does Debian works from USB drive? That's the idea. The installation make it possible to boot Debian rootfs on USB drive. > Does stock ROM affected? Yes and No. You will replace the boot loader (u-boot) on this box with a slightly newerby bodhi - Debian
> Oh yeah i did install it via an USB card reader, > it works great and with SD works well for me when > i boot from SD, Cool! > guessing i have to reflash the > nand with the new environment if i want it to boot > sd automaticly? No need to reflash the NAND image of the envs. Adjust it in Debian, fw_printenv If you see the envs listing is the same as in u-booby bodhi - uBoot
Nexus6, > devices=usb sata My bad. The env above should be devices=usb sata mmc So in serial console setenv devices 'usb sata mmc' And then boot boot Furthermore, see the rootfs release notes. https://forum.doozan.com/read.php?2,12096 QuoteUpdated 01 Nov 2023: Basic Debian bookworm Kirkwood rootfs for most Kirwood plugs: QuoteInstallation: Installaby bodhi - uBoot
Nexus6, > Hello there, i recently got a fully new Pogoplug > V4 from work and decided to install debian and > stuff, used my Pi1 for TTL and i manage to make it > work, only issue is that the SD didnt boot unless > i manually set the envs, noticed the 2023 uBoot > envs dosent have anything related to emmc booting > but the 2016 does, i havent tried to downgrade (ifby bodhi - uBoot
Try the normal ARM version kwboot_2024.04-rc3 (it's the same as the static version but load share libs dynamically). QuoteUpdate Feb 29, 2024 1 . If you are installing u-boot and Debian rootfs on Kirkwood boxes for the first time, you can use the latest flashing utilities on the rootfs itself. No need to download the binpack. But if you'd prefer to have a tool box just in case, tby bodhi - uBoot
Sash, Try using my kwboot build. It is more resilient in error recovery. U-Boot flashing utilities and kwboot binary QuoteUpdate Mar 02, 2024 1 . If you are installing u-boot and Debian rootfs on Kirkwood boxes for the first time, you can use the latest flashing utilities on the rootfs itself. No need to download the binpack. But if you'd prefer to have a tool box just in case,by bodhi - uBoot
Let me move this thread back to U-Boot section. This Rescue section is for OpenWRT and other older rescue systems.by bodhi - uBoot
Sash, > oh. i didnt get that the new uboot overwrites the > existing envars. put the openwrt back in and it > worked. Not quite. Did you got through the whole procedure of flashing u-boot image and u-boot envs image? 5. Flash u-boot image to NAND 6. Flash default u-boot envs image Post the flashing section if you have kept the log. The reason it did not boot was the eby bodhi - uBoot
> I have another question. I have read that > processor with bootrom 1.1 whici is my case have > the capability to boot from NAND, SPI, SATA. Yes, this 6281 SoC BootROM does have the capability to boot with one of those boot sources. > I should be able to recover it by > placing uboot kwb file on a sata HD starting from > sector 0 and be able to boot the uboot. >by bodhi - Rescue System