> 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
Also try, Bring the USB rootfs to another Linux box and check the file system. If the USB drive is assigned /dev/sdb, e2fsck /dev/sdb1by bodhi - Debian
jason1, Your system has booted OK. The USB rootfs has been mounted > Welcome to Debian GNU/Linux 12 (bookworm)! Debian is running. But systemd has some problem. > You are in emergency mode. After logging in, type > "journalctl -xb" to view > system logs, "systemctl reboot" to reboot, > "systemctl default" or "exit" > to booby bodhi - Debian
Joe, > If I move /var/log to an ext3 formatted usb > drive will it reduce the sata drive access and > allow it to sleep after long periods of > inactivity? It's hard to completely eliminate all disk activity on the rootfs. Even with /var/log mounted on another disk, there might be read access to the rootfs while the system is running. You could try, but it's noby bodhi - Debian
jason1, > I have a NAS326 running > Debian-6.6.2-mvebu-tld-1-rootfs-bodhi.tar.bz2 (16 > Dec 2023) on USB, and a 2TB HDD drive in slot one. > My plan is to replace the 2TB drive with two 12TB > drives and run Raid1 on it. > > A few days ago I added a second disk in slot 2, to > prepare for Raid. After I copied all the data from > disk1 to disk2, I replaced dby bodhi - Debian
Roger, You don't really need another u-boot to boot from the USB rootfs. You just need to follow the instruction here: QuoteBooting Kirkwood SoC NAS with stock u-boot https://forum.doozan.com/read.php?2,139998 Create USB rootfs using Debian-6.5.7-kirkwood-tld-1-rootfs-bodhi.tar.bz2 from the release thread. And use method 1 Quote1. Booting with stock u-boot that supports usb, exby bodhi - uBoot
Maarten, Sounds like a good plan. BTW, please convert your log files to .txt before posting here.by bodhi - Debian
Roger, > For my HMEZ, I need a file such as: > • u-boot-ix2-200.kwb > • u-boot-ix1-spi.kwb > • u-boot-hmnhd.kwb > • or, more generally, an SPI boot loader for > 88F6282 > Can you provide me with one? I don't have any of the u-boots listed above. You can try these u-boots from the release thread: Quotehttps://forum.doozan.com/read.php?3,12381 2by bodhi - uBoot
Roger, Sounds like you need to connect serial console and try to boot as described here: Booting Kirkwood SoC NAS with stock u-boot https://forum.doozan.com/read.php?2,139998 ====== That specific kernel you are looking for is here: https://forum.doozan.com/read.php?2,12096by bodhi - uBoot
> so this should also view on 115200 baud? Of course, this box only works with 115200.by bodhi - uBoot
Sash, I'm not "expecting" but hoping to see if we can trick the BootROM. As mentioned, if somehow the strapping register was corrupted, it could be stuck trying to read an unsuported source.by bodhi - uBoot
MaartenJD, > Might the cause of this issue have something to do > with the link-down fix (at 4.92 seconds, hardware > or driver related) > > ifupdown-pre.serv… synchronize boot up for > ifupdown > > at 40.53 seconds or is it systemd-related (e.g > wrong commands, dependencies or sequences)? It's systemd. Looks like the init sequence has a lot moreby bodhi - Debian
@tmcatalin, > I see on some tutorials the move/install of rootfs > into HDD. Doesn't this prevent HDD to spin-down? Yes. When the rootfs is on an HDD, you can't spin down that HDD. Logging and other activities will bring it back active frequently, so there is no point to put it to sleep. HDD rootfs is for systems that actively running applications and optimum performane isby bodhi - Debian
Jader, > 1) How / where should I run the commands > 2) what exactly they will do. > > on separated folder, download > https://forum.doozan.com/file.php?2,file=6518,filename=uboot.2022.04-tld-1.m300.bodhi.tar > uncompress to get > uboot.2022.04-tld-1.m300.mtd0.kwb file Yes. Also the Linux host OS usually already has its own kwboot which can be used too. Theseby bodhi - Debian
> I installed systemd earlier. And th question is > does this installation process (with sysv init > remove step) save for my system? I'm not so > qualified, so could you help me with that > question? I'm not using systemd for any of these small embedded devices, and therefore not using cockpit. So I'm not the best person to answer this question.by bodhi - Debian
> Thank you for the detailed explanation. One more > thing, is it possible to create 2 partitions on > one USB drive? Like this, first one - /boot, and > the second one is / ? Indeed. 2 partition USB drive is the ideal set up. After you've create 2 partitions, the process is basically the same, but with the following requirements. - The BOOT (or whatever name you chooseby bodhi - Debian
To boot with kernel on and Ext3/Ext4 drive and rootfs on F2FS rootfs. Assuming you've already booted the USB drive on the NAS (with instruction in this forum). Shutdown. On another Linux host. Attach both USB drives. Assuming the USB rootfs is assigned /dev/sdc, and the F2FS rootfs drive is assigned /dev/sdb. 1. Create new rootfs on the F2FS drive /dev/sdb1 (like you did for the USBby bodhi - Debian