While I'm waiting for my box, please try this build with kwboot. kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2016.05-tld-2.1.on100_k9.mtd0.kwb -p Interrupt serial console if you can load it with kwboot, and ping your router to see if you can get network connection. I still need to add GPIOs so disk drive might not work. Thanks Ray for the GPL, found the GPIOs in there.by bodhi - Debian
odinb Wrote: ------------------------------------------------------- > Is it perhaps because i run bash? > > > root@debian:~# myinfo > bash: myinfo: command not found > root@debian:~# > Because you've wiped out the /root/.profile I've included in the rootfs. Copy/paste the aliases from the original.by bodhi - uBoot
As Ray said below, run it as an alias, myinfo I forgot what I included in this rootfs :)by bodhi - uBoot
Here is the topic in the news: http://forum.doozan.com/read.php?8,29543,29543#msg-29543by bodhi - Debian
Indeed, thanks for checking Gravelrash. https://security-tracker.debian.org/tracker/CVE-2016-5696 It was fixed in kernel 4.7by bodhi - Off-Topic
armless, setenv mtdids 'nand0=orion_nand' setenv partition 'nand0,2' setenv bootargs 'console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)' printenv boot > We have a winner! cat /proc/mtd now shows 4 > partitions (and mtd0 is different size than > before): >by bodhi - uBoot
And Joey, this is a better Ars article: http://arstechnica.com/security/2016/08/linux-bug-leaves-1-4-billion-android-users-vulnerable-to-hijacking-attacks/ Fox "News"? common :))by bodhi - Off-Topic
feas, > Is this something we can fix on our own or do we > need a patch from bodhi for the kernel? This problem was fixed in 4.7. So work around needed for kernel 4.6.x ---------------------------------------------------------- EDITED: to correct info for version effected.by bodhi - Off-Topic
odinb, > debian:~# fw_setenv dtb_file > '/boot/dts/kirkwood-pogoplug_v4.dtb' Good! > Anything else I should do, except for Note 1 and > Note 2 (update SSH key and OS, run systemd)? > > Can I just run the command as-is, or are changes > needed? No need to change anything. The new u-boot envs take care of disk partitions selection. > root@debiaby bodhi - uBoot
odinb, > This time it boots to solid green, and I can ping > it! > > I can also SSH to it, but I do not know the > user/pass.... help! Cool! QuoteUpdated 20 Feb 2016: This Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 is to keep in sync with kernel Linux-4.4.0-kirkwood-tld-1. Basic minimal Debian Kirkwood rootfs for most Kirwood plugs: - tarball size: 1by bodhi - uBoot
odinb, > EP45-UD3L media # gparted > <Here I formatted to ext3, with label rootfs> > ====================== > libparted : 2.3 > ====================== > EP45-UD3L media # mount /dev/sde1 /media/usb/ > EP45-UD3L media # cd usb/ Are you root here? whoami The USB was not detected by the plug. So this might be a brand problem. Certain brand is pretty bby bodhi - uBoot
This is wrong: dtb_file=/boot/dts/kirkwood-pogo_e02.dtb Should be dtb_file=/boot/dts/kirkwood-pogoplug_v4.dtb If you've already rebooted, It will boot, but you need to adjust it later in Debian.by bodhi - uBoot
odinb, > "fw_setenv serverip" should be the IP of the > remote host > and > "fw_setenv ipaddr" should be the IP of the plug. > > Question, "fw_setenv ipaddr", this should be an IP > other than the DHCP IP of the plug, right? In > other words, the plug will have 2 IPs, one for net > console and one for the host. > > Ok,by bodhi - uBoot
odinb, > # uname -a > Linux eyez 3.1.10-35-ARCH #1 PREEMPT Fri Jan 23 > 19:14:18 MST 2015 armv5tel GNU/Linux This looks like a older non-FDT Arch kenel. > So, what should my next step be? Step "10. Set up > net console" (is this applicable to me?), Alsway good to set up netconsole, if you don't have serial console. > should I do "install Deby bodhi - uBoot
The thing that really annoyed me is the unit is sealed in box. Perhaps it was re-shrinkwrapped? I did not pay attention. I opened the case and turned it on withoutplugging the ethernet cable and all LEDS are flashing. That's it.by bodhi - Debian
odinb, > Ok, thanks for the hand-holding! Need a bit more > help.... On the contrary, I only need to help you to help yourself. You're doing everything right :) > > for Part B-e. > Was this mtdparts correct? > fw_setenv mtdparts 'orion_nand' No it is not. If you look back to your save envs using blparam > current_envs.txt The mtdparts vaby bodhi - uBoot
> For the moment I'm falling back to using fdisk > from busybox, as GPT is not a crucial feature. > > EDIT: now making a rootfs works, trying to install > uboot too. It's likely to fail somehow but I'm > kwbooting it anyway, soooo... :) Cool :) .. Let's not worry about GPT.by bodhi - uBoot
odinb, > Maybe I should add the current content of this > file. You're almost there! everything looks good. This is the correct content: cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd0 0xc0000 0x20000 0x20000by bodhi - uBoot
JoeyPogoPlugE02 Wrote: ------------------------------------------------------- > They say 10 seconds.. good luck :-) > -update- oh oh :-( Yup. All LEDs blinking, can't kwboot it. Piece of crap :)) But I will build new u-boot for you guys.by bodhi - Debian
Ok quite a bit missing from the OpenWrt u-boot flashing. How about doing 2 tests (with the new DTB) In serial console ver setenv mtdids 'nand0=orion_nand' setenv partition 'nand0,2' setenv bootargs 'console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial' printenv boot setenv mtdids 'nand0=orion_nand' setenv partition 'by bodhi - uBoot
odinb, > In d. above, does this mean I start in step 5 > "Extract the archive to /tmp ", and continue from > there? Yes. > # wget https://bitly.com/1UgznAq > --2016-08-13 23:37:24-- > https://bitly.com/1UgznAq > Resolving bitly.com (bitly.com)... 67.199.248.15, > 67.199.248.14 > Connecting to bitly.com > (bitly.com)|67.199.248.15|:443... cby bodhi - uBoot
OK. This time we're going to force it. It looks like the mtd partitions were not set in stock u-boot. In serial console, at step 3 in the procedure above: setenv mtdids 'nand0=orion_nand' setenv bootargs "console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)" Please bear with me :) I'd like you tby bodhi - uBoot
My box is no good :) I think it must have been DOA when I got it. Time to RTFM to see if it can be reset. There is a RESET button.by bodhi - Debian
odinb, > Currently running a couple of pogo plugs (one > standard with SATA, one mobile) on Archlinux > (https://archlinuxarm.org/platforms/armv5/pogoplug > -series-4). You are running a much older ALARM u-boot. So you should do these 2 steps below (if you have serial console connected or willing to connect one then the risk of bricking is very low). 1. Flash new u-boot frby bodhi - uBoot
Gravelrash, OTOH, stock u-boot does not come in to play when we do kwboot. So the fact that I have not been able to kwboot the box must have been caused by either the serial pins out, or the u-boot image being loaded. We know the pins out is correct. So I just need to find an image that can be loaded, or do what Ray did (compile the stock GPL, which might be different from one running in theby bodhi - Debian
Chuck99 Wrote: ------------------------------------------------------- > Here is the printenv. > > (I assume you have already created the Debian 4.4 > rootfs on USB). Answer is NO. > I just got finished downloading and trying follow > instructions with Ubuntu and did not work for me. > I am a neophyte at this stuff. I really want to > learn how to restore myby bodhi - uBoot
freestyle, Excellent! Now there is one problem with mounting rootfs. This was because your uImage still has the DTB embedded inside that you needed to boot with stock u-boot (step 4): Quote4. 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).by bodhi - Debian
Looks like your rootfs was corrupted. Take it to another LInux box and fsck it to fix errors.by bodhi - Debian