balbes150, It means that: - The Asus-NAS-M25 has UART booting capability, good news :) Now you can experimenting with flashing newer u-boot, knowing there is a rescue mechanism. - The Sheevaplug is the reference board, so it works with the ASUS. - To build newer u-boot for the ASUS, the Sheevaplug's u-boot can be used as a base. But changes might be needed to make it work correctlyby bodhi - uBoot
Joey, These are installation links that you might want to read (but not attempt right away, I'd expect you will have questions): 1. Jeff's script to install u-boot and Debian (the Debian rootfs part has problem, because it is out of date) http://projects.doozan.com/debian/ 2. To create latest version of Debian rootfs: http://forum.doozan.com/read.php?2,12096 3. To installby bodhi - Debian
yhfudev, Unfortunately, AUFS is not in the mainline Linux kernel. So I can't add it without patching. Also, there are some inpact to the current kernel with other config options above (will alter the behavior).by bodhi - Debian
@JanN, Try cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd1 0x0000 0x20000 0x20000by bodhi - Debian
balbes150 Wrote: ------------------------------------------------------- > U-Boot Asus-NAS-M25 Doesn't support booting from > SATA (HDD). > There is only support for USB and NAND. Ah, I've mixed up yours and Jan's :) then try that change "orion_nand" on USB.by bodhi - Debian
Yes, console=console=ttyS0,115200 mtdparts=orion_nand:0xc0000@0(uboot)ro,0x7f00000@0x100000(root) Your dmesg showed that the mtdparts did not get into the command line.by bodhi - Debian
@thebladerunner, You are running the new u-boot, but with the default envs from internal u-boot settings. You should have also flashed the default envs image (step 10) if you are going to run an FDT kernel/rootfs such as this rootfs. 10. Flash uboot environment to 0x00100000 (See caveat in step 2, do not flash this if the kernel is not FDT) So right now, to recover you can do either onby bodhi - uBoot
@laprjns, It's because codier has flashed new u-boot and new default envs images. The original settings for the old u-boot can be used as is with the new u-boot, but the new defaults envs can also be flashed to start anew. @codier, Replicate what you did for the 1st Dockstar. You can compare the the 1st Dockstar envs and the 2nd one. Recall you have to add the rescue envs setting bby bodhi - uBoot
balbes150, I think you should put the mtdparts definition in the kernel command line (looks like it is not currently). See if it will appear. [ 0.000000] Kernel command line: console=ttyS0,115200n8 user_debug=31 :::DB88FXX81:eth0:noneby bodhi - Debian
LeggoMyEggo, > Edit 3 hour later: Just loaded 3.18 over my 3.17 > disk. Boots fine but stock Realtek wifi does not > respond to modprobe rt3390sta.ko or rt3390sta. > Also tried modprobe rt2800pci. rt3390sta does not > show up in lsmod. What was the error when you did modprobe? Look for the module see if you can find it: find /lib/modules/ -name '*3390*by bodhi - Debian
rkrug, - Simple approach: use usbmount (install the usbmount package). - More complicated approach (and more flexible and powerful): use udev rules. Also be aware that if you use a remote dekstop (xfce, lxde,...) then the automounting behavior is potentially different when you are in desktop.by bodhi - Debian
habibie, > I will give it a try to see how it goes. The only > problem I can think of right now is do I have to > make any necessary changes to the u-boot > environments when migrating to GPT? What I tried > to say is if GPT still uses the /dev/sdXn, where X > can be a, b, c, etc. and n starts from 1 to 128? With the new u-boot, I am not aware there is any differenceby bodhi - uBoot
I've heard that in Debian Sid, initramfs can do fsck.f2f2 mounted drives (I have not verified this). And there are a few bug fixes came in for 3.19, and more bug fixes for 3.20. So don't use it for your data drives yet. Also, using it for rootfs on remote administering devices seems unfeasible. Unless you have a rescue system installed in NAND.by bodhi - Debian
@Robert, QuoteIt will write UBOOT to Sata disk on the beginning (in the first 2048 sector) on the disk (not on rootfs.) (??) Should be: QuoteIt will write U-Boot SPL to Sata disk on the beginning (in the first 2048 sector) on the disk.by bodhi - uBoot
habibie, > IIRC, this was flashed somewhere in 8/2014 by a > friend. I believe she just followed the > instructions on the ArchLinux ARM site and the > procedure automatically upgraded the u-boot. This is the later version. > Right > now, I don't even know if the original PogoPlug OS > on the NAND space is still there or not. However, > if I take out tby bodhi - uBoot
dump, When you install kernel with dpkg, initramfs-3.18.5-oxnas-tld-1 will be generated automatically.by bodhi - Debian
@Jan, > What did you guess, and: were you right? Yes, there must have been a subtle change in 3.18 that seems to affect stock u-boot only. In the following bootargs, try changing it as followed (the bold part). And please do this in serial console only (don't save). bootargs_sata1linux=console=ttyS0,115200 mtdparts=orion_nand:0x100000(uboot),0x80000(uboot_env),0x80000(key_sby bodhi - Debian
balbes150 Wrote: ------------------------------------------------------- > bodhi Wrote: > -------------------------------------------------- > ----- > > > Looking at the dmesg log, is this the ASUS-M25 > > boot log or something else? > > > > Marvell DB-88F6281-BP Development Board > > > > > Yes. Out console Asus-NAS-M25. > fby bodhi - Debian
habibie Wrote: ------------------------------------------------------- > Hello Bodhi, > > Thank you for your suggestion on GPT. Is this GPT > the same as the gdisk on a debian Wheezy > (v7.1.xx)? > > Currently, I have a 1TB SATA HDD on a Seagate > GoFLEX Home flashed with ArchLinux ARM (including > the uboot from ArchLinux ARM). If I format my 1TB > SATAby bodhi - uBoot
LeggoMyEggo, This update includes the config CONFIG_CFG80211_WEXT, that was omitted. A few people have reported this particular config missing that cause problem with the supplicant . I suspect that the problem also has something to do with the updated Realtek drivers in kernel 3.17+. Please try. I don't have the wifi card installed in my Pogo Pro currently so can't test it. Ifby bodhi - Debian
balbes150, > To make changes in U-Boot, you can use the system > with non-FDT kernel (3.16 =<) and then move on FDT > ? > This is possible ? > See if I understood your question: you want to have newer u-boot (e.g. 2014 or 2015) that can boot with non-FDT 3.16 and FDT 3.17+ kernel? The answer is: u-boot that has FDT support can be used for booting both non-FDT andby bodhi - Debian
Kernel linux-3.18.5-oxnas-tld-1 package was uploaded. Please see 1st post for download link. The following features are new in this version: - Added various kernel configuration that are newly available in 3.18, and also various kernel configuration per forum users requests: loop device, stock wifi supports, encrypted fs.by bodhi - Debian
codier, scanning usb for storage devices... 0 Storage Device(s) found This means your USB was not detected. Try plug it in the port in the back, right next to the Ethernet port. Power up. OTOH, if you intended to boot rescue system without the USB attached, then your envs are not set up for that.by bodhi - uBoot
@Don, - It is not swap related. fsck.f2fs simply does not like to fsck a mounted drive. So there is not much we can do other than turn off fsck for rootfs. - You can use uuid to mount rootfs. There should be no problem doing that. I think we will have to wait for future kernel version to the label to work.by bodhi - Debian
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