JanN, > Strange is: in u-boot i can set and read envs > manually and via script, and the box loads uImage > und uInitrd from sda1 as i want it. > It's OK not to have mtdparts definition at all in Linux. This comes into play only when you want to setup the envs for booting while inside a Linux shell. u-boot knows where the envs are, based on the the envs settings in thatby bodhi - Debian
@balbes150, Thanks!by bodhi - Debian
balbes150, Execellent! great job, and thanks for sharing your Asus-NAS-M25 successful installation. Could you attach the Asus-NAS-M25 DTS file here? I'd like to include it in the patch for the next release for general consumption.by bodhi - Debian
Waynosan, > http://www.instructables.com/id/Linux-hints/step6/ > Pogoplug-V2/ > > Do you foresee any issues with this approach? I would not use that approach. If you are going to run Arch, then you should use Arch u-boot and its installation procedure. But if you want to use a different u-boot, you can install my u-boot image later, after you got Arch running.by bodhi - uBoot
JanN, This is strange. Stock NSA320 mtds are: Creating 9 MTD partitions on "nand_mtd": 0x00000000-0x00100000 : "uboot" 0x00100000-0x00180000 : "uboot_env" 0x00180000-0x00200000 : "key_store" 0x00200000-0x00280000 : "info" 0x00280000-0x00c80000 : "etc" 0x00c80000-0x01680000 : "kernel_1" 0x01680000-0x04640000 : &quby bodhi - Debian
Jan, I'll look at the power button problem in the source. For the leds, you can add this to /etc/rc.local to turn on the green led and turn off orange led when the kernel has finished booting: if [ -d /sys/class/leds/nsa320:green:sys ]; then echo default-on > /sys/class/leds/nsa320:green:sys/trigger echo none > /sys/class/leds/nsa320:orange:sys/trigger fby bodhi - Debian
@robert Starting kernel ... Uncompressing Linux... done, booting the kernel. Make sure uImage is the one that came from the rootfs tarball. It should not have DTB embedded in it.by bodhi - uBoot
habibie, If you switch to GPT then you can have 128 partitions!by bodhi - uBoot
Hi JanN, > But there are some issues: leds and powerbutton > don't work, Please list the output of: ls -lR /sys/class/leds > and fw_-commands bring up the "Bad > CRC, using default environment"-message. According > to the latter, there are probably wrong settings > in /etc/fw_env.config, as i read earlier in this > thread. Yes. You are runniby bodhi - Debian
Waynosan, > I'm not married to Archlinux; it's just that there > are the most examples for setting it up on the > internet for at least some of what I want to do > with it. Being a noob regarding this stuff I > figured it would be the easiest way to approach > it. > I assume that Debian can probably do the same > stuff but I get the impression that iby bodhi - uBoot
@chrlee, Thanks for sharing! I will surely take a look at your patch. Is the NSA320S DTS different much from the NSA320 DTS?by bodhi - Debian
@Robert, Do what shv suggesting above to boot SATA. You are very close! And then you can flash NAND SPL (if necessary u-boot too) from Linux shell. It's good to have alternatives, and SATA booting is a good rescue mechanism, too, even if you don't plan to use it every day. However, as of right now, you can also flash it in u-boot console, if needed. The flashing commands are diffeby bodhi - uBoot
@Nate, I think you best next step is to: - See what robert did here: http://forum.doozan.com/read.php?3,16017,19718#msg-19718 Try using robert's u-boot envs file. - If it still fail, connect serial console.by bodhi - Debian
@robert, You have unbricked it! You can reflash u-boot in serial console now :) Quote> Is there any way to boot via usb or tftp? Is it > possible theoretically? Yes. Since you have booted into u-boot console with SATA u-boot. However, there is no need to do this. If you like, just reflash NAND u-boot/SPL. Then your pboblem is solved. To continue with SATA booting: You'by bodhi - uBoot
Waynosan, > > At this point, should I try to restart the > Archlinux installation process? Also, re-flashing > the mtd0 seems to have solved the connection > problem, doesn't that indicate that there was > indeed a problem with uboot? Just trying to make > sense of why the Archlinux install failed before I > try it again. Let me know if you know of a &gby bodhi - uBoot
Yes, you can run it on the rPi.by bodhi - Debian
Nate Wrote: ------------------------------------------------------- > Bodhi, > > I got this error when running mkenvimage: > > root@ubuntu-VirtualBox:/mnt/sdb1/boot# > ./mkenvimage -s 16384 -o u-boot.env > u-boot-env.txt > bash: ./mkenvimage: cannot execute binary file: > Exec format error > Ah! This binary is ARM (compiled on Kirkwood). So you canby bodhi - Debian
Don, I got f2fs to boot with a Jessie rootfs. But there were hurdles that I needed to work around. Here are a few problems that caused me to I think perhaps f2fs is not friendly enough to use as a set-and-forget root system (also, it could be that there are new released features that I'm not aware of yet). Problems to solve: - rootfs label does not seem to work in kernel command line.by bodhi - Debian
Nate, I've attached the mkenvimage tar file here. It is part of u-boot build (it's not available in Debian repo).by bodhi - Debian
Waynosan, Cool! you are back to Pogo OS. > How do I go about correcting the MAC address and > the other errors? Looks like the default envs are OK. Power up again, interrupt serial console and at the prompt, printenv again, make sure the MAC address is correct and other envs are listed OK like before. You can use setenv to set the MAC address in serial console. setenv ethaddrby bodhi - uBoot
Hi shv, > The latest rootfs is > Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2 but > this is not your problem because at least one of > two prerequisites for SATA booting seams to be not > met. Does your SATA u-boot envs setup work with rootfs Debian-3.12.13-oxnas-tld-5-rootfs-bodhi.tar.bz2 (with step 6 in the instruction to set up FDT envs)? Also should it work witby bodhi - uBoot
@Nate, I've noticed you did not state what u-boot envs were modified. What is the content of u-boot-env.txt? You can compare notes with what morph027 did to make it work here: http://forum.doozan.com/read.php?3,16017,19707#msg-19707by bodhi - Debian
Waynosan, > I can boot up > Mint and put it on the USB stick that way. Download it on Mint, put it on a different USB stick, plug the stick into the Pogo, and copy it to the same directory you are on (for convenience). Then execute it: ./blparam It is a precaution mostly. Since we can't do anything to verify the u-boot flash before reboot (other than dumping it and do a biby bodhi - uBoot
Waynosan, Looks great! Here is the blparam binary.by bodhi - uBoot
habibie, It would be easier to do if you have individual partition for each OS. Then it is just standard installation where u-boot controls which patition to load appropriate kernel. There is also the issue of mounting rootfs. You would need initrd for each rootfs so that it can be mounted properly. So it is possible, but the needed customization is not just with u-boot alone.by bodhi - uBoot
@Nate, Do you have the installation log? It is hard to say what went wrong without seeing exactly what you did.by bodhi - Debian
Waynosan, Step 1 output is different because the mtd parts definition are different between the Pogo V4 and the Pogo E02. And no special permission needed when you are root and root owns this mtd0 file. Revised instruction: Because mtd0 on the Pogo E02 is 1M, we need to erase 8 blocks, and write it without OOB data (as the back up does not contain OOB). In the same directory, executeby bodhi - uBoot
Waynosan, I think fw_printenv failed because you don't have this file: /etc/fw_env.config. It is not that important. Since we already know it's OK to flash mtd0 with this info: # cat /proc/mtd dev: size erasesize name mtd0: 00100000 00020000 "u-boot" mtd1: 07f00000 00020000 "rootfs" But if you like, create this file any way with the content below andby bodhi - uBoot
Waynosan, > I used this command: nanddump -nf mtd0 /dev/mtd0 > while in the backup directory on the USB drive. I > do not have the output as it's no longer in the > command window buffer. I can go back and re-do it > if necessary. Please redo with nanddump -nof mtd0 /dev/mtd0 > Have no idea what OOB data is... I want to cry. It's OK not to knowby bodhi - uBoot
grayman4hire, > Got it. That use to be a problem for me until I > discovered the "nofail" option. > > echo "/media/usb/swapfile.img none swap > sw,nofail 0 0" >> /etc/fstab Indeed! that would get around the problem, but silently so.by bodhi - Debian