Please post the entire boot log. If you have serial console log then post that. If not, post dmesg ouput.by bodhi - uBoot
Thanks for your contribution. I guessed you have not read this thread? We are running kernel 4.6 and u-boot 2016.05 on this box!by bodhi - Debian
Fix mtdparts first: fw_setenv mtdparts 'mtdparts=orion_nand:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2)'by bodhi - uBoot
Thanks Rainer! I've added this to the Wiki thread also.by bodhi - Debian
> It works and that is what is important. Good job > :) Yes, indeed. Thanks notoneofmyseeds :)by bodhi - Debian
Follow up on number 1 above: To boot with rootfs label in Arch: Quotemoonman initramfs-linux.img needs to be under /boot So initramfs-linux.img is now an extra kernel file provided by Arch Linux ARM.by bodhi - uBoot
mxhdrm, > I'm > going to go back and read the entire thread and > see what's going on so that I can more properly > see what's going on here for everyone. But I guess > I should note that simply having the server is one > thing, but it needs a client before anything else > will work. I'd suggested that you look at notoneofmyseeds thread, too:by bodhi - Debian
notoneofmyseeds, > As regards this, I've chosen to use fstab for now, > as USBmount is no longer supported. I got > irritated with pmount, which is another > alternative being maintained. Even if usbmount is no longer supported, it is such a simple function, I don't see if it is in any danger of breaking. It is OK to use. Or you can switch to using autofs whichby bodhi - Debian
notoneofmyseeds Wrote: ------------------------------------------------------- > know of a way that I could adjust my account so > notifications are sent me on threads that I > comment on. Use the "Follow Topic" button at the bottom of the post.by bodhi - Debian
The Armada kernel was built easily, without any trouble. But I have been quite busy so have not got back to this. And I don't have the hardware yet, either :).by bodhi - Debian
mandm, > Your earlier versions of environment > variables allowed for that and worked well. > I just > pass this along to you in case you plan on > updating U-Boot for ArchLinux in the future. > Modifying U-Boot is something I have little > experience with, so I am a little uncertain at > this stage what would need to be changed in other > environment variby bodhi - uBoot
ptosch Wrote: ------------------------------------------------------- > Hi Bodhi, > > I solved this by setting machid=831. Seems like > this kernel ignores arcnumber and uses machid. > Cool! > This is how it looks now: > > > host 192.168.10.254 is alive > Using egiga0 device > host 192.168.10.254 is alive > Using egiga0 device > hostby bodhi - uBoot
nibbler Wrote: ------------------------------------------------------- > Ok, thank you for the clarifications. It's hard to > combine all the bits and pieces from various > threads and posts. > > Quotebodhi > You don't need 2 partitions. One is better. > > > Yes I agree that one would be better. But I tried > booting with a single ext2 and ext3by bodhi - Debian
nibbler Wrote: ------------------------------------------------------- > Now I managed to get Debian up and running without > touching the u-boot envs. I had to use a usb stick > with two partition and the > Debian-3.16.0-kirkwood-tld-2 rootfs. I don't > understand why the newer rootfs packages don't > boot The last kernel that kills the watchdog by itself isby bodhi - Debian
Darkphyer Wrote: ------------------------------------------------------- > hi, I cant seem to get ssh enabled on my PogoPlug > Mobile > the option is not listed in my.pogoplug.com and > https not accepting connections > "https:///sqdiag/HBPlug?action= > command&command=dropbear%20start" > I can access the > "http:///sqdiag/" pages > iby bodhi - Debian
arcNumber should be 2097 for the rescue system. Do you keep a log of you old envs? something else might be missing.by bodhi - uBoot
I should have mentioned this new feature (described in the first post): Quote- The default envs were modified slightly to make it more robust. If you are upgrading u-boot, there is no need to reflash, but worth taking a look at the envs text file to see the differences.by bodhi - uBoot
For anybody who has this T5325 box and only follows this thread. I've released 2016.05-tld-1 U-Boot images in the main u-boot release thread.. Please go there for general information about the new u-boot-2016.05-tld-1.by bodhi - uBoot
I've released 2016.05-tld-1 U-Boot images. Please see 1st post for download link.by bodhi - uBoot
Francesco, I don't have this box so I'm not sure.by bodhi - Debian
nibbler , QuoteFirst I set the device to boot from the USB with the "usb-debian-uboot.tar.gz". Then I installed the system following the instructions from here and using a single ext3 partition. Somewhere in this thread: http://forum.doozan.com/read.php?2,14351,page=1. You'll find the u-boot envs adjustment to boot with stock u-boot. The errors in indicated that your u-bootby bodhi - Debian
Install locale: apt-get install localesby bodhi - Debian
Create rootfs on USB drive following instruction from the kernel/rootfs thread: http://forum.doozan.com/read.php?2,12096. In section: 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. To boot with stock u-boot, pay attention to section 4 Quote4. Create uImage with embedded DTB for booting with oldby bodhi - Debian
> Tried booting to a fresh USB drive created from > Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2. > Then followed the instructions for installing the > Kirkwood U-Boot. I had to install mtd-utils, but > after that the instructions were successful and > I'm now booting straight into the USB drive!!! That was what I suspected above why you did not get network cby bodhi - uBoot
LeggoMyEggo Wrote: ------------------------------------------------------- > bodhi Wrote: > -------------------------------------------------- > ----- > > > :o) you been having a tipple?? > > > > Too early in the day for that :)) > > Care to share? > > WTF is tipple....I realize my geezerhood may > prevent me from being aware of moderby bodhi - Debian
> :o) you been having a tipple?? Too early in the day for that :))by bodhi - Debian
Peter, > It boots from rescue, even though You wrote "NOTE: > the envs below are not to be used in your box. > They are for example only.". These were the same > settings before flashing the ENVs (except bootcmd > value). I should have worded it a little bit more clear (late night and all that :). These were from my log long ago. So I can't be sure if I hby bodhi - uBoot
Francesco, > > i've applied first option and work fine. Now for > save the boot parameter in eeprom, what should I > do? > 1. Sanity check: - Boot up with serial console again. - Interrupt serialconsole - Enter the evns like you did before - Copy this serial console log to your note to reference it later - Boot into Debian like before 2. Do it for real:by bodhi - Debian
notoneofmyseeds, Best way to do this is: create a new rootfs on USB drive (wheezy or jessie where appropriate). Do all the experiments on it and keep a log. Backup as you go, when you think it is messed up and you've lost track then just restore the last backup. You might do many iterations until you get a good installation. And then go back to your log and make clean procedure, do real iby bodhi - Debian