Yep. Looks like you did not flash the new default envs image. These current envs are back in the days of u-boot 2012. See here for how to load the new default envs: https://forum.doozan.com/read.php?3,29362,29390#msg-29390 Since your box is Pogo V4, instead of setenv dtb_file '/boot/dts/kirkwood-goflexnet.dtb' You need setenv dtb_file '/boot/dts/kirkwood-pogoplugby bodhi - uBoot
nikolarobottesla, > When I try to boot with the below setenv > settings I get "Verifying Checksum ... Bad Data > CRC" error when loading the kernel image > "Linux-4.16.1-kirkwood-tld-1" Is there something > I'm missing in the below setenv stuff? The envs look OK. Usually this CRCR error indicates that your rootfs is corrupted. You could post thby bodhi - Debian
ayosher, > Anyway, I added uEnv.txt to the /boot of the > rootfs with: > custom_params='ip=dhcp' It is not necessary to do this, since you have full control of the box. And the rootfs is already set to boot with dhcp. You could also edit /etc/network/interfaces in the rootfs to make it use a static IP 10.0.0.57. If you think the IP is causing problem. > root@deby bodhi - Debian
Jxjhheric Wrote: ------------------------------------------------------- > sorry about another problem after upgrade the > lastest kernel on pogo v4 > > here is the log: > > U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:59:45) > Pogoplug V4 > > SoC: Kirkwood 88F6192_A1 > DRAM: 128 MiB > WARNING: Caches not enabled > NAND: 128 MiB > MMC: kwsby bodhi - uBoot
Martin, Here is the u-boot release thread in this forum: https://forum.doozan.com/read.php?3,16017 You can install u-boot from stock OS, or from Debian/Arch if you already running those distro.by bodhi - uBoot
herb, > When I boot from this drive I get a kernel panic. > > Is there something I did that caused this? Any > suggestions? Yes. The rootfs you have created or reused has the DTB embedded inside uImage. That has intefered with the DTB loaded by the new u-boot. Quote 4a. Boot with DTB file (standard way to boot FDT kernel). Recommended. - Generate the uImage and uInitrby bodhi - uBoot
ayosher, On this box, the USB 3.0 slot can only be used after the kernel has started. u-boot will not recognize it. Your u-boot installation was good. Nothing is wrong with it. > Please see log below (kernel fails to start). With netconsole, the only output you will see after 1st installation is this: > Starting kernel ... After you have booted into Debian, you need to dby bodhi - Debian
goshty, You've missed this adjustment during u-boot installation. dtb_file=/boot/dts/kirkwood-pogo_e02.dtb Should be dtb_file=/boot/dts/kirkwood-pogoplug_v4.dtbby bodhi - uBoot
BTW, I've confirmed that RTC works, too. [ 5.170730] rtc-mv f1010300.rtc: setting system clock to 2018-06-28 08:27:34 UTC (1530174454)by bodhi - Debian
JDS420, Right, it shows that we can just brute force our way to find these GPIO easily. I can see only one LED in the back that blinks constanly. Is there other LEDs that you can see? Update: That's it. Only 1 LED that can be turned on White or Orange.by bodhi - Debian
QuoteIs there some mismatch with tar on my NSA320 or tar on my laptop running Linux Mint Mate 18.3??? All Linux system tar works the same way. Redownload the tarball and try again.by bodhi - uBoot
herb, I've moved your posts to the thread below. Next time, please post installation problem in a new thread.by bodhi - uBoot
herb, uboot.2016.05-tld-1.environment.bodhi.tar Is the latest u-boot env image. It should work fine.by bodhi - uBoot
I've moved herb's posts to its own topic below.by bodhi - uBoot
JDS420, > There's a php/? script in the kbox directory that > controls the led status and color. Might it have > the GPIO pins listed in it? > > Part of the LED functions: > > private function _led($args) { > $this->_ledstatus($args); > } > > private function _ledstatus($args) { > echo PlatformUtility::LEDSby bodhi - Debian
jmandawg Wrote: ------------------------------------------------------- > Thanks Bodhi, > > Your right, after giving the drive more power via > plugging both ends of the "Y" usb cable in, it > hasn't happened again. I also tuned the network > and samba config as recommended in this article > and seems like it's running smoothly now (no more >by bodhi - Debian
renojim Wrote: ------------------------------------------------------- > Did anyone try to contact Dell at > opensource@dell.com? Please do. I have not.by bodhi - Debian
JDS420, > There's a php/? script in the kbox directory that > controls the led status and color. Might it have > the GPIO pins listed in it? Very promising! now we just need to drill down to the low level script (but if the low level is binary then it's a bit more difficult).by bodhi - Debian
argent88 Wrote: ------------------------------------------------------- > Trying again, it stays there at > > > [ ok ] Starting ftp server: proftpd. > > > Any ideas? No idea! I dont use OMV. Anybody?by bodhi - Debian
Gravelrash Wrote: ------------------------------------------------------- > @bodhi > Thanks for the education :) > > > ... ill get back in my corner now... :)))) Not at all:) that’s a good question that cleared up a few things for some users. We certainly need a diagram to describe all possible paths in the boot process.by bodhi - Rescue System
JDS420, You and JT already searched for this. So I'm not going waste time :) Without GPL, we're not going to have new u-boot and have to use stock uboot. But that's enough to run Debian. We don't know yet which GPIO controls which LED lights (that's just cosmetics). Everything else is running OK. I will try kwboot to at least get a recovery mechanism (in case soby bodhi - Debian
@Gravelrash, There is nothing new in that post. We covered this a few times in this forum already. The Wiki thread "Backup and Restore NAND mtds - Pogoplug V4 original MTD partitions" describes a similar process. https://forum.doozan.com/read.php?3,16789,16789#msg-16789 Note that of loading uboot image (in this case, the entire mtd0 is the uboot image) from USB or tftp achieby bodhi - Rescue System
There is a PCI bus. Does anybody see it exposed any where on the board?by bodhi - Debian
JDS420, > In order to enable ssh the way Dell intended, you > have to enter a "tether key" which allows customer > support to ssh into the box an undo/fix anything > someone may have broken. Without a legitimate key, > you have you purge all openssh packages and > reinstall them. You might have to remove the > kace-tether app too, but it's been monthsby bodhi - Debian
jmandawg, > [ 362.200133] sata_oxnas: resetting SATA core > [ 362.560099] ata1.00: exception Emask 0x0 SAct > 0x0 SErr 0x0 action 0x6 frozen > [ 362.567132] ata1.00: failed command: WRITE DMA > EXT I have not seen this on the Popgo OXNAS V3. But have seen similar error on a Kirkwood box. I can't say it is the same. But usually when you see this, check your SATby bodhi - Debian
That's encouraging! See how well it run :) When it's all done, please make a nice post for your OMV installation, including your log. I'd like to add this to the Wiki.by bodhi - Debian
Looker, Something strange in your system. The only way is to find out is to observe it booting with serial console. My Pogo V4's don't have any problem booting with drives attached to USB 3.0 ports. One boots with USB 2.0 on top, and other boot with NFS rootfs. Once in a while, I plugged in a USB 3.0 drive and don't recall any problem. But it would be great if there is inby bodhi - uBoot
Jxjhheric, The reason you can't see anything after this was because you have netconsole activated at the same time you're connecting with serial console. > host 192.168.1.105 is alive So what you can do to fix this quiclky: change the IP address of the box that you have serial console module plugged in to other number, eg. 192.168.1.106. If you'd rather not doing thby bodhi - uBoot
bodhi note: This old installation instruction is deprecated. Please see this post for new Installation Instruction: https://forum.doozan.com/read.php?2,61344,89559,page=5#msg-89559 =================== A. Installation instruction. Here is how to boot the new Debian rootfs 1. Create the USB rootfs using Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 from the kernel/rooby bodhi - Debian
Jxjhheric Wrote: ------------------------------------------------------- > here is console : > > 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: egiga0 > Using egiga0 devicby bodhi - uBoot