vinibali, > Mainline doesn't seem to have the speed, I assume > for some reason the CPU is running on very low > frequency. > [ 0.000000] Booting Linux on physical CPU > 0x0000000000 [0x410fd034] > [ 0.000000] Linux version 6.18.7 (user@PC) > (aarch64-linux-gnu-gcc (GCC) 15.1.0, GNU ld (GNU > Binutils) 2.44) #3 SMP PREEMPT Mon Jan 26 07:05:26 >by bodhi - uBoot
> bonjour, je suivais votre post, et cela m'a donné > envie de restaurer mon ds218. j'ai un petit ch341, > je viens de controler son fonctionnement, le petit > truc important, c'est surtout que je souhaiterai > trouver le Dump de l'eeprom , et je pense que cela > sera compliqué à trouver, mais je demande, si > quelqu'un a le dump d'un DSby bodhi - uBoot
Alex, User name _ae9o has been approved! Please try logging in.by bodhi - Debian
Alex, > Could you please activate my ae9o > account? I registered, but can't log in because it > requires admin activation. I don't see any unapproved users. You could try register again with a slightly different user name. > Press Ctrl+C to abort autoboot in 3 second I forgot to ask if you can interrupt the countdown and printenv and then boot > [by bodhi - Debian
kally, > root@hal4:/hal/u-boot# ./tools/kwboot -b > ../uboot.2023.04-tld-1.ds411j.kwb -s 0 -B 115200 > -t /dev/ttyUSB0 > This exact command was working before but it is > not anymore, the NAS does not trigger anything > > I suppose my image is not corrupt enough and the > NAS tries to start it without looking at UART I'd doubt that was the reason. If theby bodhi - Debian
Ray, > I have a RackStation RS816 with Armada 385 SOC, so > perhaps this will be helpful when I start working > on support for it. > > Ray RS816 is basically done here: Quotehttps://forum.doozan.com/read.php?2,32146 Synolgy RS816 (Armada 385) Installation: see Installation with USB rootfs (Section I). And see Installation with HDD rootfs (Section II). https://forumby bodhi - Debian
_ae9o, > I've successfully adapted the Device Tree for the > Synology DS216j NAS. Cool! could you also post the bootlog (serial bootlog prefered, so we can see how you boot the box). Thanks!by bodhi - Debian
> Is there a way to change where uboot looks for > environment from 0xc0000 to 0xe0000? If I could > tweak that then I think I could get both preboot > and OpenWRT working. No, there is no way to change the envs address from the user interface. u-boot does have a redundant envs capability (fallback), but I did not configure it in the 2017.07 version. > probably wouldnby bodhi - uBoot
> Tried "kwboot -t -B 115200 /dev/ttyUSB0 -b > uboot.2017.07-tld-1.pogo_v4.mtd0.kwb" a few times, > starting kwboot before powering up pogoplug, and > powering up pogoplug before kwboot, but nothing > there either. Did you try kwboot before flashing? > I have one with bad block 6 that failed awhile back, > but with different symptoms. > > ubootby bodhi - uBoot
kally, > Damn, and now kwboot does not work anymore... If you keep the log of what you did, perhaps I can help to recover.by bodhi - Debian
rsantag, The "work around" is not something that works in all scenarios. I wrote that to mean in each case, the bad blocks and their location must be considered before the flashing is attempted. > I'm assuming I need > to somehow configure it with the new locations for > uboot and environment. Am I on the right track? No need to reconfigure anything! ===by bodhi - uBoot
> I setup a USB LaserJet yesterday and used slightly > different steps. Thanks! added to the Wiki.by bodhi - Off-Topic
Roger, > For now, I'm happy if I can start the NAS with a > USB stick in combination with the SATA drive. See the post above It is possible to boot the rootfs on SATA, but the kernel files on USB. But this solution is bit cumbersome. The example is for F2FS rootfs, but it is basically the same for Ext3 rootfs. You just need to clone your current USB rootfs to an Ext3 partiby bodhi - uBoot
QuoteRoger Unfortunately, certain commands are missing in this version, for example: sata, ide, ext4load, fatload... If the ide command is not available then there is no way to read the HDD using any method.by bodhi - uBoot
> Would changing this permanently on the USB drive > correct the problem ? Yes, according to the DTS, the network should be eth1. > 2) Edit /etc/network/interfaces, and replaced eth0 > with eth1 Yes.by bodhi - Debian
deb http://archive.debian.org/debian bullseye main deb-src http://archive.debian.org/debian bullseye main Good to know! > I'm still > debating whether or not I want to upgrade to > bookworm. Trixie seems to force systemd on us, so > I really don't know whether I want to upgrade to > that. I think you should at least upgrade to bookworm. Since it is old-stablby bodhi - Debian
> However, no ip address has been configured With serial console connected, power up, boot with the setenv commands like you did before. Log in Debian through serial console, and ifconfig -a ethtool eth0 And then post the entire serial console log (from the u-boot banner) here.by bodhi - Debian
romiz, Try "Booting Kirkwood SoC NAS with stock u-boot" https://forum.doozan.com/read.php?2,139998 I think it does not matter which A/B u-boot version, you might be able to boot with the LaCie net2big v2 DTB.by bodhi - Rescue System
phloks, The panic might have been related to the non-existent console. Your boot log: > usb_set_bootargs=setenv bootargs > console=ttyUSB0,115200 root=LABEL=rootfs > rootdelay=10 earlyprintk=serial The instruction said setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=sby bodhi - Debian
romiz, > I'll post the detailed logs, Please do that. > but I suspect > something wrong with NAND chip. You only need the first 1MB NAND for u-boot to boot Debian on USB/HDD. So bad block like this is OK: Bad block at 0x100000 in erase block from 0x100000 will be skippedby bodhi - Rescue System
phloks, I'll take a close look at the log. For now, these are suggestions to try. 1. Use a different older type of USB 3.0 thumb drive, or better yet, use a USB 2.0 thumb drive for rootfs. 2. Don't use dd, use fdisk subcommand o to wipe the partition properly. > dd if=/dev/zero of=/dev/sdc bs=1M count=1 fdisk /dev/sdc Command (m for help): o Command (m for helby bodhi - Debian
phloks, > As you can see, I'm trying to get an old ix2-200 to play Debian... Is your box the ix2-200? or other variation? > I did step 4, with the difference that I could not > find Linux-6.5.7-kirkwood-tld-1 in my /boot, so I > used vmlinuz-6.5.7-kirkwood-tld-1 instead. Linux-6.5.7-kirkwood-tld-1 in > root@Vulcan:/mnt/boot# mkimage -A arm -O linux -T >by bodhi - Debian
Roger, > I've already tried it, but I think my Marvel > U-Boot is too old. > Unfortunately, certain commands are missing in > this version, for example: sata, ide, ext4load, > fatload... Right. When you do help OR ide reset And don't see ide command, then you can not boot from SATA. It is possible to boot the rootfs on SATA, but the kernel files onby bodhi - uBoot
phloks, You've missed Step 4 in the rootfs creation. Quotehttps://forum.doozan.com/read.php?2,12096 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 (or are installing this u-boot at the same time, or running kwboot with latest u-boot image). Please replaceby bodhi - Debian
> The Sandisk Ultra Fit that didn't work is a 64GB > USB 3.2 Gen 1 drive. The one that works is a > Sandisk Ultra Fit 128GB USB 3.1 Gen 1. So, > something about USB 3.2 it apparently doesn't > like. Has anybody else run across anything like > this before? Yes. With this Pogo V3 Oxnas, the way to boot consistently is to use a USB 2.0 drive. And also attach itby bodhi - Debian
vinibali, > IIRC this SoC pretty much gained mainline > support for the Linux kernel in the recent years, > compared to how RTD12xx was in the first years. Yes. But this specific board QNAP TS-228A is not supported in the mainline kernel or u-boot yet. > But I couldn't get the U-Boot shell, even if there > is a message in the logs: > "Hit Esc or Tab key toby bodhi - uBoot
MaartenJD, I don't see this network problem on my NSA325 running 6.17.7 and sysvinit. And root@debian:~# [ 79.145766][ T8] mv643xx_eth_port mv643xx_eth_port.0 eth0: No phy led trigger registered for speed(1000) The above was not an error. Just a warning that the LED trigger is not registered so the port LED cannot be set. The NIC should be running fine without the trigger. Dby bodhi - Debian
rsantag, > It boots up fine, but it won't let me log in as > root with password "root". > Anybody have any ideas? The default password IS > "root", right? Yes. Credential is root/root. Connect serial console, restsart, and post the entire serial console log here.by bodhi - Debian
jason1, > The issue is resolved. > I indeed did what the log suggested, logged in as > root in emergency mode, changed rootfs to > writable, opened /etc/fstab and commented out the > line with the uuid of old drive, saved the file, > and after a reboot the system booted up normally > and I had access to ssh. :-) Cool! > For future stability when replacingby bodhi - Debian
Roger, > Thank you very much for your reply. I tried your > tip to create USB rootfs using > Debian-6.5.7-kirkwood-tld-1-rootfs-bodhi.tar.bz2 > and method 1, but unfortunately the output hangs > again at Kernel: Note this step in the rootfs installation Quotehttps://forum.doozan.com/read.php?2,12096 4. (Stock u-boot only) Create uImage with embedded DTB for bootingby bodhi - uBoot