> Oh my god. I figured it out. > All I have to do is install systemd-sysv. > Installing only apt-get install systemd was not > enough. Cool! that was probably new requirement in later Debian versions.by bodhi - Debian
I guess you should try using the same addresses that boot tftp to double check, before investigating it further. setenv bootcmd 'nand read.e 0x02000000 0x500000 0x500000;nand read.e 0x03000000 0xa00000 0x500000;bootm 0x02000000 0x03000000' and then boot See if this stock u-boot will take the modified bootcmd, or will it overwrite the boocmd in memory.by bodhi - Debian
gigas root@debian:~# fw_printenv custom_params custom_params= That was correct. When you use uEnv.txt, the changes are transient, i.e. applicable during u-boot booting. So that why it was not what you want to see in Debian. That custom_params is actually working, as your bootlog showed: Quote[ 0.000000] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdpby bodhi - Debian
codingdave, > Marvell>> printenv > CASset=min > MALLOC_len=5 > autoload=no > baudrate=115200 > bootargs=root=/dev/ram console=ttyS0,115200 > max_loop=32 > bootargs_end=:10.4.50.254:255.255.255.0:KW40:eth0:none > bootargs_root=root=/dev/nfs rw > bootcmd=nand read.e 0xa00000 0x500000 > 0x500000;nand read.e 0xf00000 0xa00000 > 0x500000;bootmby bodhi - Debian
Jan, Please post complete dmesg log, so I know which kernel we are looking at. That does not look like latest kernel, is that stock? If it is stock, then it's only good for information about how stock kernel spinning up the HDDs.by bodhi - Debian
QuoteQuestioning if I should pick one up... seeing as the M300 outdoes it in the RAM department probably not, but it's yet another device with a 2GHz Kirkwood and knowing it's at least in some part related to the M300 gives me some hope. It's actually also related to Zyxel NSA325, and a few others 6282 SoCs based Kirwood boxes.by bodhi - Debian
> Hi, bodhi, just found one typo here, C220 should > be C200 Thanks David! fixed.by bodhi - Debian
Leggo, > Can't wait to see cheap dual core 64 bit processor > 2gb RAM SBC devices become sub 25 dollar eBay > scores someday. That day should be near :) for some of the Realtek SoC boards. It's a lot cheaper than Marvell SoCs.by bodhi - Debian
Jan, > I wonder why they use regulators-hdd-34 for a box > with 4 disk slots in the dts file Usually if a hard disk was powered on in u-boot, there is no need for regulator (to power it on in Linux). So that must have been the reason. So HDD 1 should be able to spin up in u-boot. This u-boot is old, therefore use the ide command to test. Insert an HDD to the 1st slot. Shutdown andby bodhi - Debian
Jan, Quote[ 8.546433][ T1] mdio_bus f1072004.mdio-bus-mii: MDIO device at address 8 is missing. [ 8.554785][ T1] mdio_bus f1072004.mdio-bus-mii: MDIO device at address 9 is missing. That's why I was thinking about the GPL source. It means there are more differences from the ds411. kirkwood-synology.dtsi &mdio { status = "okay"; ethphyby bodhi - Debian
This USI Topkick has been done and should be on the support list. There it is: QuoteLinux Kernel 5.17.x Kirkwood package and rootfs for GoFlex Home/Net, Pogoplug E02/Mobile/V4, iConnect, Dockstar, Sheevaplug, NSA320, NSA320S, NSA325, NSA310S, NSA310, Topkick, Netgear Stora, ASUS-M25, Iomega ix4-200d, QiZhiTong 501mv2, HP Thin Client T5325, LG N1T1, Linksys EA4500, Lenovo/Iomega ix2-ng, Toshby bodhi - Debian
ddl2000, > Got it. Thank you very much. Cool! so you see the MAC address in u-boot is > ethaddr=52:3b:20:9c:11:51 It's a local MAC address that I generated for the u-boot installation. You can either continue using it (good to mask your real MAC address to avoid being tracked on the net). But you can also set it to the real one with fw_setenv. fw_setenv ethaddr 00:25:by bodhi - Debian
Actually another package QuoteUpdated 26 Sept 2021: Basic Debian bullseye Kirkwood rootfs for most Kirwood plugs: - tarball size: 234M - install size: 668M - The init system used in this rootfs is sysvinit . To boot with systemd, see Notes below. - Installed packages: nano, avahi, ntp, busybox-syslogd (log to RAM), htop, isc-dhcp-client, dialog, bzip2, nfs server/client, iperf, eby bodhi - Debian
OK so the change did not stick. But your router took the local MAC 52:3b:20:9c:11:51 anyway and generated the dynamic IP. DHCPACK of 192.168.1.231 from 192.168.1.1 If you like, keep using the local IP. Or later change it in Debian using fw_setenv to make the real MAC address permanent. Now on your Mac OS erminal you can log in the Pogo through SSH. The root credential is root/root.by bodhi - Debian
Jan, > the box does have 1 Ethernet port. With 1 ethernet port, it is eth0. The envs confirmed that. So this kirkwood-ds411.dts is mismatched in that it also specifies eth1. Looks like the ds413jv10 version has 2 ethernet ports. > ethprime=egiga0 > ethact=egiga0 > I checked that the sources seem to be available. > Not the latest as this box is EOL but they are > fby bodhi - Debian
It was a successful boot. But you don't have network. QuoteNo DHCPOFFERS received. So reboot shutdown -r now And interrupt serial console at count down. QuoteHit any key to stop autoboot: 0 Execute printenv See that you have the MAC set to the local MAC (not the real one). ethaddr=52:3b:20:9c:11:51 Some router is picky, and will not assign IP addr when you chby bodhi - Debian
Jan, 2 questions. 1. Does this box have 2 Ethernet ports? 2. Can you request the latest GPL source from Synology? there seems to be some difference between this box and the DS413jv10 (not sure what v10 is about?).by bodhi - Debian
ddl2000, > I followed your instruction at Updated 26 Sept > 2021 for rootfs creation. and created a usb boot > drive. > > now I am getting the boot message from pogoplug > E02. anything I did wrong? > > ** File not found /boot/uInitrd ** This error indicates that the rootfs was not created correctly. > Image Name: Linux-5.17.4-kirkwood-tld-1 >by bodhi - Debian
Jan, Quote[ 8.556268][ T1] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4 [ 8.564242][ T1] kirkwood-pinctrl f1010000.pin-controller: pin PIN20 already requested by f1080000.sata; cannot claim for f1076000.ethernet-controller [ 8.578076][ T1] kirkwood-pinctrl f1010000.pin-controller: pin-20 (f1076000.ethernet-controller) status -22 [ 8.588144][ T1] kirkby bodhi - Debian
Added to the Wiki thread. https://forum.doozan.com/read.php?2,23630 QuoteUnbricking with Serial Console & JTAG console .... Unbrick Synology DS214 Synology NAS Serial Consoleby bodhi - uBoot
Thanks Jan! that's answered my question.by bodhi - Debian
Hi Jan, > well, the DS214 boots now and is fully unbricked > and functional again ;) I'm half falling asleep but fully awake when I saw this :) > > What did I change? Believe it or not, I simply > unplugged the serial connector before booting > after reading this in the file > /arch/arm/boot/dts/armada-xp-synology-ds414.dts > > > /* Connecby bodhi - uBoot
Hi Jan, BTW, could you answer this post about serial pinouts, for your DS214 box? https://forum.doozan.com/read.php?2,76314,132346,page=25#msg-132346by bodhi - uBoot
Jan, > The second stage also loads very fast. This is > definitely not loaded over the serial but from > flash. That looks good! The message "Booting from SPI flash" is always there, regardless which boot method (the indicator is in the image you used). But it does seem the u-boot image on flash was OK. > This stock uboot sits in the partition > mtd0, startby bodhi - uBoot
> Why does someone with programming skills patches > the Kernel to fake this values? For what? 30 Euros > / box price difference? Google for > foxluo@hugsun02 > > What a shame. The people who did the fake might not have been the same ones who used it.by bodhi - Off-Topic
ddl2000 Wrote: ------------------------------------------------------- > Hi, bodhi, > > Thank you for quick response. I am not clear how > to do usbfs. I don't have linux machine. only mac > and windowspc. so I cannot follow the steps like > apt-get and dpkg command. any more instruction on > how to do it on nonlinux machine? > > Thank you very much.by bodhi - Debian
Ext4 partition is OK too. But care must be taken to avoid lazy init issue.by bodhi - Debian
ddl2000 , > I am also bricked my pogoplug E02 after trying to > install debian.. It is very far from bricked! > U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:13:18 > -0700) > Pogo E02 > > SoC: Kirkwood 88F6281_A0 > DRAM: 256 MiB > WARNING: Caches not enabled > NAND: 128 MiB > In: serial > Out: serial > Err: serial > Net: egiga0by bodhi - Debian
Jan, What you see is the 2-stage boot, used on these Marvell Armada XP (and 37x, 38x) SoC boxes. Quoteboot, blue lights blinking. No serial output. Simply bricked. It means that the 1st stage (SPL) image is corrupted. When you kwboot with stock u-boot image and see the SPL is running QuoteSending boot image... Booting from SPI flash High speed PHY - Version: 2.1.2 (COM-PHY-V20)by bodhi - uBoot