Sash, I don't have new uboot for thix box. You can boot this FDT kernel with stock uboot . Look back in this thread to see how it was done.by bodhi - Debian
mrmees Wrote: ------------------------------------------------------- > I picked up a Pogoplug a while back and had messed > with it a little before putting it on the shelf. > > Plugged it back in recently to try and use it for > a little home server and proceeded to bork it up > something fierce while trying to install Arch. > It's very possible I tried to insby bodhi - uBoot
Chuck, Sine you can kwboot the box like this, so you can proceed to boot the Debian rootfs without changing u-boot envs. From there you can decide whether to restore stock MTDs if you want. 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 plby bodhi - uBoot
Sash, > Hi, > i tried to find the binray on my box, with no > result. > where is the binary located in general? Some old Kirkwood boxes use blparam, some new boxes do not. So this box probably use modern fw_printenv/fw_setenv. Log in to stock OS and list the envs to see if it is supported. fw_printenvby bodhi - Debian
armless Wrote: ------------------------------------------------------- > Regarding your 4.6 Kernel update notes: > > > cd /boot > apt-get remove flash-kernel > dpkg -i > linux-image-4.6.0-kirkwood-tld-1_1.0_armel.deb > > > The package flash-kernel was not installed so no > need to remove it. > > Also installing the 4.6 kernel DEB file gaveby bodhi - uBoot
armless Wrote: ------------------------------------------------------- > bodhi Wrote: > -------------------------------------------------- > ----- > > I think that this version of flash_erase output > is > > misleading. Go ahead repeat the flashing (step > 7, > > 8). > > > > And do fw_printenv afterward for sanity check. > And > >by bodhi - uBoot
Sash Wrote: ------------------------------------------------------- > just for the record. these are the 2 different > uboot versions the different revisions of the unit > was delivered with. > > i can also provide a wholeflash backup of the > cloud und noncloud version on request if there is > any demand..... Thanks Sash! it will be very helpful to have these sby bodhi - Debian
rayknight Wrote: ------------------------------------------------------- > Playing around with this again trying to boot a > Linux kernel with a hacked dtb file appended. > Get the following output: > > Uncompressing Linux... done, booting the kernel. > > Error: unrecognized/unsupported machine ID (r1 = > 0x0000020f). > > Available machine support: &by bodhi - Debian
Thanks Ray! 1. USB works. Cool. 2. MMC is missing. This is true. I forgot to port this code. 3. Ethernet Now same setup but using kwboot with your latest uboot file. This time Link and Act lites are on for the MON port and Act is on for the LAN port. Other lites are the same as with stock U-Boot. After this ON100_K9> setenv eth1addr 64:00:F1:20:DF:66 ON100_K9> ping 19by bodhi - Debian
armless Wrote: ------------------------------------------------------- > bodhi Wrote: > -------------------------------------------------- > ----- > > And do fw_printenv afterward for sanity check. > And > > cross your fingers and reboot :) > > Flashed u-boot again and default environment. > > Now doing environment variable "fixup". >by bodhi - uBoot
armless, I think that this version of flash_erase output is misleading. Go ahead repeat the flashing (step 7, 8). And do fw_printenv afterward for sanity check. And cross your fingers and reboot :)by bodhi - uBoot
heychris_1 Wrote: ------------------------------------------------------- > Thank you for the quick reply. > > I appreciate you validating the mtd0 layout. > > What about using Jeff's rescue system in the rest > of the mtd0? Would that boot OK? Jeff's rescue system has not been reported to work with the Stora. And it needs to be installed from stock. Iby bodhi - uBoot
This version has 2 new things added: 1. Activate egiga0 and egiga1 2. Turn on GPIOs (I am not really sure which one is which yet). Stock u-boot is a real pain to read :) Please try kwboot like before. This time try both egiga 0 and 1, and then do some USB or SD initialization ping <router ip> usb start mmc rescanby bodhi - Debian
armless, > > flash_erase /dev/mtd0 0 4 > > > you indicate the expected output is: > > > Erase Total 4 Units > Performing Flash Erase of length 131072 at offset > 0x60000 done > > > whereas I see: > > > Erasing 128 Kibyte @ 60000 -- 100 % complete > > The above is wrong. > > > /usr/sbin/flash_erase /by bodhi - uBoot
And please post netconsole bootlog with USB rootfs.by bodhi - uBoot
And how did you determine this? LEDs? > > Quote> I did notice that this has egiga0 and > egaga1 > > switched from what stock U-Boot identifies. > Your > > U-Boot identifies the MON port as egiga0 device > > while stock identifies the LAN port as > egiga0. Remmember I dont have the box, you need to describe what you saw as much as you can. Ie, didby bodhi - Debian
checktravis Wrote: ------------------------------------------------------- > I've had "U-Boot 2016.05-1 (Jun 20 2016 - 01:58:53 > -0600) Arch Linux ARM" running on my GoFlex Home > for a while, but I would like to leave that > working on the sata as it does now, but run Debian > from a usb. It must have an ip because nc sees it, > but i can't ping or sby bodhi - uBoot
heychris, You have switched to boot with DTB, but your uImage still has the DTB embedded in it. You need to restore to it to the original. This was the step in the Debian rootfs installation that you need to reverse: 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 installby bodhi - uBoot
heychris, > My question is about using the > uboot.2016.05-tld-1.environment.bodhi.tar > > The default mtdparts for a netgear stora are > mtdparts=mtdparts=orion_nand:1M(u-boot),512K(uboot > _env),512K(key_store),512K(info),10M(etc),10M(kern > el_1),48896K(rootfs1),10M(kernel_2),-(rootfs2) > > Since I am not using a large chuck of that, Does > it makeby bodhi - uBoot
rayknight, > U-Boot 2016.05-tld-2.1 (Aug 18 2016 - 01:44:47 > -0700) > Cisco ON100_K9 > > SoC: Kirkwood 88F6282_A1 > DRAM: 512 MiB > WARNING: Caches not enabled > NAND: 512 MiB > *** Warning - bad CRC, using default environment > > In: serial > Out: serial > Err: serial > Net: egiga0, egiga1 > Error: egiga1 address not sby bodhi - Debian
ElMariachi Wrote: ------------------------------------------------------- > Hi! > > In some threads I one had read that ext3 was the > recommended filesystem to use for the rootfs. > Does this still apply with current UBoot > versions? > Am I safe to use ext4 in the long instead? > > Thank you! > :) Ext4 is fine, and it is supported by the current u-bby bodhi - Off-Topic
Joey, No need to search, it's mentioned in the main u-boot thread: http://forum.doozan.com/read.php?3,12381 QuoteImportant Note: If possible, try to test this boot image with UART booting before flashing to NAND. See davygravy's UART booting using kwboot instruction here in this thread. The latest u-boot image released here should be used for UART booting, if your box is the typeby bodhi - Debian
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