@Johnny, Some USB sticks have problem with coldboot (some also have problem with warmboot, but not coldboot). If you can, get a Sandisk stick (any model) and try that. nc problem: this is expected with stock u-boots in general. So don't waste time trying. Usually we need custom u-boot to support netconsole. @pengu, No, I think the watchdog problem is diffferent. Eventhough it seeby bodhi - Debian
ubermacin Wrote: ------------------------------------------------------- > Also strange, when I try to boot into arch I see > in the net console: Unknown command 'setexpr' - > try 'help' > > I see that in the bootcmd, and now I can't boot > into arch now: > > [ 12.439090] scsi 0:0:0:0: Direct-Access > SanDisk Cruzer Glideby bodhi - uBoot
Johnny, I'd strongly recommend using a SINGLE partition of type Ext3. Extract the rootfs to it. Dont worry about swap until you can boot consistently.by bodhi - Debian
Sure, but you will run into problem later! See "u-boot and kernel booting process" in my signature for explanation.by bodhi - Debian
What pengu said were all true, but one item: the u-boot envs are not set up properly for 2 partition rootfs, yet. So Johnny should use only one Ext3 partition, to ensure successful booting.by bodhi - Debian
Johnny, Your u-boot envs look sane. So it's not that. Since you did this on a Ubuntu VM, retrace your steps to make sure: - When you copied rootfs, you were the root user? - The USB has only one partition and it must be Ext3 - The partition label must be rootfs When preparing the rootfs (either new or update), you must be the root user. If you still can't boot afer verifby bodhi - Debian
@maihoamv, I did not see any familiar config listed (I have not looked closely). However, in general, it's needed to be little endian and arch needed to be ARM.by bodhi - Off-Topic
Johnny, cd to the USB boot directory (assuming the USB is mounted as sdb1), and then cd /media/sdb1/boot cp -a zImage-3.18.5-kirkwood-tld-1 zImage.fdt cat dts/kirkwood-nsa320s.dtb >> zImage.fdt mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-3.18.5-kirkwood-tld-1 -d zImage.fdt uImage mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -eby bodhi - Debian
maihoaomv Wrote: ------------------------------------------------------- > I was able to compile rtl8812au on my GoFlexHome. > I changed Makefile PLATFORM like this i386=n and > ARM_Rpi=y as mentioned back on page 1 of the post. > I was able to build it with a bunch of warnings > but no errors. it worked when i did insmod > 8812au.ko and it seems so far to be working finby bodhi - Off-Topic
@pengu, Since you are using the NSA320S DTS, have you verified that the all specs is the same? Ie. find the differences between NSA310S and NSA320S and make sure they are taken cared of.by bodhi - Debian
pengu, See the u-boot installation thread. The uboot.2014.07-tld-2.environment.bodhi.tar tarball has the envs in text format. QuoteB. Flashing default u-boot envs image This section describes how to flash a default set of u-boot envs. The bootcmd in this setup is set to boot from USB, MMC, and SATA in this order (USB will be tried first, if unsuccessful then MMC will be tried, and thenby bodhi - uBoot
Joey, > One attempt into doing my Debian PogoPro and got > the error Failed to connect to VMware vCenter > Converter Standalone and think it might be > because Pogo isn't playing nice on port 56789. And > I'm not saying for sure VMware will reenact ARM > architecture I don't think this would work. I don't recall VMware can emulate ARM.by bodhi - Off-Topic
@pbg4, > but a small patch is still needed - instead of my > big patch included in your kernel now - mostly > concerning secure and fast locking of tt-s2-4600 > on dvb-s2-transponders with the latest changes > from > Olli Salonen's git, in the next days I am going to > prepare a clean patch and send it to you for > integration > into your next 4.1 kernelby bodhi - Debian
JT, I think it's worth a try. And you don't need to connect serial console to try it. With the latest u-boot, you can add the quirks in the bootargs env in the uEnv.txt so that it is not set permanently. For example, if the bootargs is: usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_paby bodhi - Debian
Thanks pbg4, Great mod, it's well thought out and very informative!by bodhi - Debian
JT, > Could the fact that the Fantoms are USB > 3.0 have anything to do with it? It could be the USB controller inside the Fantom enclosure. We've seen the Sandisk Ultra Fit exhibited the same problem (see recent posts in the forum).by bodhi - Debian
raja Wrote: ------------------------------------------------------- > Hello all, > > I have a black pogoplug (no WIFI model) and was > successfully running Debian Squeeze for several > days. I installed uBoot, left the internal flash > untouched and booted Debian off a 4GB USB flash > drive. > > All was good until my device stopped booting into > Debian.by bodhi - Debian
Pit, Cool. > Appolgies from my side. No need to!by bodhi - uBoot
JT, Have you tried to plug the Fantom drive to the USB port in the back (next to the ethernet port)?by bodhi - Debian
Pit, Something is missing in the bootargs, it's is hard to tell without seeing the kernel command line. Please post the entire serial boot log including the mount error above.by bodhi - uBoot
Pit, >. From Debian > "cat /proc/mtd" shows: > mtd0: 10000000 00020000 "orion_nand" > "cat /proc/cmdline" shows: > console=ttyS0,115200 root=/dev/sda1 rootdelay=10 > rootfstype=ext3 > orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(dat > a) This was because your u-boot env for mtdparts was not defined correctly. When you do cby bodhi - uBoot
trisk, These drives are not good to use as boot drives. You should get a Sandisk (any model is fine).by bodhi - uBoot
trisk Wrote: ------------------------------------------------------- > I have severe problems with USB booting on both > oxnas devices I've tried (a black POGO-P21 and > pink POGO-B01). This has happened with a couple of > different USB flash drives/card readers and both > U-Boot 2013.10-tld-4 and U-Boot 2013.10-tld-5. > Using the default environment with dt_bootcmd_by bodhi - uBoot
Val532, Sure, I'll add it to kernel 4.1.by bodhi - Debian
ubermacin, u-boot does not have wget. And you can't install u-boot at u-boot prompt in a normal way as in Debian or Arch (different instructions is needed). The best way to install u-boot is to boot into Arch or Debian and start from there.by bodhi - uBoot
workingman, FreeBSD wiki: https://wiki.freebsd.org/FreeBSD/arm Looks like we'll need new u-boot version to support bootelf. This kernel file has elf headesr: /rootfs/boot/kernel/kernel However, according to this, we don't need bootlef if using NetBSD image: https://code.google.com/p/beagleboard-freebsd/wiki/BuildingAndBootingby bodhi - Off-Topic
Joey, > Running at 1066 MHz is less processing > than any Pogplug, and I've learned that even with > 2Gigs of fast RAM, the bottleneck is the > CPU.moreso than using swap file. > Very true! I think you'll be surprised to find how much it improves just with 1.6 GHz plug and 512MB RAM running Debian. So the plugs like NSA325 is a step up that makes quite a non-tby bodhi - Off-Topic
pengu Wrote: ------------------------------------------------------- > SUCCESS!!! > > sorry for the late response > > I've found the NSA320s DTB (included in your > linux-4.0.0-kirkwood-tld-1(and -2) but not in the > 3.18.5 rootfs. > So ist wasn't there because I didn't unpack dtb > tar file. > > > ... > [ 0.000000] Linuxby bodhi - Debian
@erwin, Try this: unplug the SSD, boot with USB. After it booted into Debian, plug in the Sandisk SDD. Do you see the kernel recognizing and initializing the SSD ? I am hoping the behavior is the same as we've seen with the Sandisk Readycache SSD. Eventhough u-boot failed to detect the identity of the SSD, Debian will detect it just fine. If that is the case, then it can be used as theby bodhi - uBoot
Ah! looks like it is the same problem as the Readycache Sandisk SSD. Reset IDE: Bus 0: OK Bus 1: not available Device 0: Model: ?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?� Firm: ?�?�?�?� Ser#: ?�?�?�?�?�?�?�?�?�?� Type: Hard Disk Supports 48-bit addressing Capacity: 427923841.5 MB = 417894.3 GB (4611474908973580287 x 5by bodhi - uBoot