WarheadsSE Wrote: ------------------------------------------------------- > Yes. Thanks! I will get to work on this.by bodhi - uBoot
jochar Wrote: ------------------------------------------------------- > Hello, > > So i have successfully booted into debian on my > NSA320S with lan and updated, now i need to figure > out how to update uboot so it boots into debian > instead if the ZyXel distro > > Thanks I have not been looked atthe difference between the 320 and 320s.by bodhi - uBoot
Leggo, I dont use display so not sure.by bodhi - Off-Topic
JoeyPogoPlugE02 Wrote: ------------------------------------------------------- > I'm too scared to partition my only working USB > stick with samba, but eventually I'll have to find > a way. Seems 30% of my 4GB USB stick is used on > Arch Linux, which is probably way too much. > Eventually i'll get the courage to try the Samba > technique, and of course sooby bodhi - Off-Topic
Amro, Change your bootm bootcmd_linux=setenv bootargs ${bootargs_linux}; mw.l f1010100 0020c000; usb reset; ext2load usb 0:1 ${loadaddr} /uImage; ext2load usb 0:1 0x01100000 /uInitrd; bootm ${loadaddr} 0x01100000 I forgot that with the new u-boot, you should change all $(var) to ${var} format. So change all your envs, but do one at the time. boot completly into Debian after each change tby bodhi - uBoot
Amro, I guess you were playing with the envs and has unintentionally removed the loadaddr! It has nothign to do with the USB /boot or rootfs. Boot, interrupt serial console/netconsole and setenv loadaddr 0x800000 And then boot And this is wrong (extra quote), setenv needs quotes to include space. But when you list the envs, there should be no quote. bootcmd='run bootcby bodhi - uBoot
@Lenny, Do what Gravelrash suggested on Ubuntu, not Windows.by bodhi - Debian
It's the Year of The Goat :) Happy New Year everybody! Peace to the world.by bodhi - Off-Topic
Also see this thread: Debian Linux on Zyxel NSA320S (success) It might or might not be because you're booting with the NSA320 DTB. chrlee has a new DTS for NSA320S which I'm going to include in the next kernel release to see if it will be enough.by bodhi - Debian
@jochar, > Issues: > No network (no light on the back of the unit, > switch does not detect the port, i have tested the > cable with the tester and tryed the port with a > pc, but no luck) > > Plase help to resolve this network issue Please post your dmesg output after booting and logged in as root with serial console.by bodhi - Debian
Addy, The kernel installation was successful. It has finished booting. The problem now is with the rootfs. To recover: - Download and put the 3.17 rootfs on a USB thumb drive. - Boot and interrupt serial console. - Temporarily change u-boot env for bootcmd to boot USB first. If not sure how, please list your u-boot envs in serial console here. Don't save your envs. After bootingby bodhi - Debian
LeggoMyEggo, > I am just saying it would be nice if the script > was updated to 1) to load the latest u-boot and > root-fs and 2) took into account the platform it > was being installed on and customized the > installation based on that. Agreed. I just need to find time to write and test it, since Jeff has stopped the maintenance for the script.by bodhi - Debian
Joey, QuoteW: Failure trying to run: chroot > /tmp/debian mount -t proc proc /proc > W: See /tmp/debian/debootstrap/debootstrap.log for > details > debootstrap failed. > See /tmp/debian/debootstrap/debootstrap.log for > more information. > Pogoplug:/tmp$ When you've installed with Jeff's wheezy/squeeze script and got to this point, then: - u-boot versby bodhi - Debian
@yhfudev, > > -CONFIG_TREE_PREEMPT_RCU=y > -CONFIG_RESOURCE_COUNTERS=y > -CONFIG_PM_RUNTIME=y > -CONFIG_BT_6LOWPAN=m # this one is missing even I > select in the menu > -CONFIG_IEEE802154_FAKEHARD=m > -CONFIG_IR_IMG_HW=y > -CONFIG_IR_IMG_NEC=y > -CONFIG_IR_IMG_JVC=y > -CONFIG_IR_IMG_SONY=y > -CONFIG_IR_IMG_SHARP=y > -CONFIG_IR_IMG_SANYO=yby bodhi - Debian
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