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
Added to the Wiki thread. QuoteBooting Debian on Pogoplug ... Booting Pogoplug V4 with Kernel from NANDby bodhi - Debian
> See > Recovering > a Failed Synology Diskstation with a Serial > Console for details regarding pin out for > most Marvell based Synology NAS. Thanks, I found that too. But that was DS212+, i.e. not one of these 3 boxes. So the questions to users in this thread is "do they all have same pinouts like below?" 1 3.3V 2 GND 4 TX 6 RXby bodhi - Debian
> They really are just Pogoplug Mobile devices with > the Zigbee module soldered to the serial pins. I > believe the overclocking to 1 GHz was done by > jumping some pins on the serial. Interesting! yeah, the overclocking is done after market. I'm just not aware of anybody is actually doing that and selling a product. > I have a box > full of these devices, iby bodhi - Debian
> Forgot to name the partion > there. Oeps. Cool! glad you've figured that out.by bodhi - Debian
What David said. The USB rootfs must be labeled rootfs. And a bit more: I've reconfigured mtdblock to loadable module in kernel linux-5.16.5-kirkwood-tld-1. Just so to avoid the problem with the kernel's scanning mtds during boot. Yes, the ECC errors could be misleading (if the USB rootfs was not labeled rootfs, and never was mounted successfully).by bodhi - Debian
> The > Smartenit > Harmony P2 which was a re-labeled Pogoplug > Mobile with a Jennic Zigbee card attached to the > serial pins was overclocked to 1 GHz. Thanks Ray! I did not know such as a box exists. Are they really overclocked? They might have a better batch of the 6192 SoC chips from Marvell.by bodhi - Debian
I'm revisiting this topic and don't recall we have the serial pinouts post for RS816, DS116, or DS118. If you own one of these boxes, please post the serial pinouts. Thanks!by bodhi - Debian
> Oh, those faster ones (esp 1.2 & 1.5GHz) were not > Pogoplug but in some NAS. It's the same processor > but running at a higher speed. I wish I could find > that info now. > It is rare to find a 88f6192 SoC faster than 1Ghz (88f6192 is the SoC in the Pogo V4 and Mobile). I think I only have seen 1 board at 1Ghz, but cant recall which. Those 1.2Ghz or 1.5Ghz aby bodhi - Debian
QuoteAnd some users even said they get ~ 1000-1500 BogoMIPS with the same processor as PogoPlug Mobile. Given there are a few versions, if I remember correctly were 1.0, 1.2 & 1.5GHz (read it last night but can't find the website now) And 1.0, 1.2 & 1.5GHz are just wrong numbers. There is no Pogo Mobile faster than 800 MHz. Unless they overclocked it (possible to do).by bodhi - Debian
dkyyz, Don't worry about it. BogoMIPS has been misleading since after Debian Jessie (at one point, Linus even wanted to remove BogoMIPS from the log). The reason is the calculated BogoMIPS is oftenly wrong on multicore processors. And also as you might have known, cpufreq-info will only output the current frequency at the time you run it. With the governor "ondemand", thiby bodhi - Debian
camstar, > > ## Unknown partition table type 0 > loading envs from usb 0 ... > ** File not found /boot/uEnv.txt ** Ignore the noisy log above. Those are not errors, they are just information. That's u-boot scanning the drive partitions and looking for uEnv.txt. This is the default behavior, which I did not try to change to make it less noisy. > Really sorry top boby bodhi - Debian
This is also suspected. Will get to that if the setenv's did not work. Sun Jun 12 17:49:29 UTC 2022 upgrade: Device cloudengines,pogoe02 not supported by this imageby bodhi - Rescue System