tdd, These little boxes will do all of the above, pretty efficiently. I would move all those chores to the Pogo E02(s) without hesitation. Here is a very good thread we have recently about serial console: http://forum.doozan.com/read.php?8,13263 And you probably already knew this: it is pefectly OK to have a USB thumb for rootfs formatted as Ext3, if you move all your logging to /tmp.by bodhi - Debian
musselmanb, Your theory is correct :) because your bad block was on the first 4 blocks (I did not notice if you've posted the output of flashing uBoot on bad block). Original uBoot uses 0xa0000 for the envs. Jeff/Davy's uBoot uses 0xc0000. The reason was so that original uBoot envs would stay intact so it could be used in booting Pogo OS. But because of bad block, we wiped out blockby bodhi - uBoot
tdd, - The very first thing you should do is to setup netconsole, if you don't have serial console. netconsole will let you recover from a bad rootfs to a certain degree (till before the kernel is loaded), and hopefully to observe more of kernel booting. http://forum.doozan.com/read.php?3,14 - /dev/sda1 does not need to be in fstab. You have /dev/root. That's the rootfs where you cby bodhi - Debian
In pogo OS, what is your output of cat /etc/fw_env.config does it show 0xa0000 as the address? If you have use fw_setenv in Pogo OS. Then continue using fw_setenv, don't use blparam. But if you have not, then use blparam. Because they have different checksum.by bodhi - uBoot
twinclouds, If you are running Debian Squeeze rootfs on this OXNAS B01, you can upgrade the rootfs to Wheezy. But udev will cause problem, so it will need to be hold back to the current version you have. t's very simple as running a command: http://forum.doozan.com/read.php?3,6336,13058#msg-13058 So: - hold udev - changing apt/source.list to wheezy - apt-get update - apt-get upgrby bodhi - Debian
tdd, > Am I correct in thinking that > upgrading it to wheezy is not as simple as > changing "squeeze" to "wheezy" in > /etc/apt/sources.list and dist-upgrading? It is as simple as that, no extra steps needed. But you should clone your USB stick to another one in case there is problem.by bodhi - Debian
Of course, it's nice to build your own rootfs from the kernel tree. But if you want to save time, use this wheezy rootfs: http://forum.doozan.com/read.php?2,12096,12096#msg-12096by bodhi - Debian
musselmanb, 1. The nanddump and nandwrite go in pair. But I don't know the nanddump and nandwrite version you're using. Are you using what Jeff script uses? Your nanddump and nandwrite look OK to me if those were same one that Jeff script uses. nanddump -nof ~/backup/mtd1 /dev/mtd1 nandwrite /dev/mtd1 ~/backup/mtd1 2. Your flashing would work only if the stock Pogoplug NANby bodhi - uBoot
musselmanb, Look like it booted the orginal Pogo OS. No way to tell for sure without serial console, though. But if you use nmap to scan your network, you should see whether port 22 is opened for SSH. Have you registered this pogoplug E02 before at pogoplug.com? if you did, then try log in to that site and re-enable SSH. It should allow you to change password (the default login is root/ceadby bodhi - uBoot
Kristoff, - Kernel 2.6.31.6_SMP_820 is Arch Linux kernel. When you boot this Pogo V3 with Debian, the kernel uImage is Arch and stored in NAND mtd, but the rootfs on USB is Debian. This is not a normal process. - To use rtl8187-based wifi device, this module needs to be Arch, and must reside in /lib/modules/2.6.31.6_SMP_820. So find that module and do modprobe in /etc/rc.local. See the origby bodhi - Debian
krbonne, For Pogo V2, use this rootfs on USB: http://forum.doozan.com/read.php?2,12096 For your pogo V3, you're running Debian Kirkwood rootfs (probably varkey's rootfs or shv's rootfs), so apt-get update && apt-get upgrade will install kernel and/or initrd for kirkwood device. Ignore this, the Kirkwood kernel files are not used in this configuration.by bodhi - Debian
musselmanb, Sorry, I was posting from my phone and text got cut off! There is no real mount command for jffs2. I meant it seems the original kernel uImage and rootfs were written to NAND in jffs2. That's why you have successfully mounted the rootfs in Linux with mount -t jffs2 /dev/mtdblock2 command. This command was the correct one to run to boot back to stock. pogo_bootcmd=if fsloby bodhi - uBoot
musselmanb Wrote: ------------------------------------------------------- > bodhi, > > Thanks for your guide from your old post. I am > able to get usb to boot. It is nice to be able to > use the stock OS to troubleshoot failed to boot > thumb drive > > 1. fw_printenv output > > > # fw_printenv > ethact=egiga0 > bootdelay=3 > baudrateby bodhi - uBoot
Hi musselmanb, I was hoping to see some error when you mount it, but it looks like your mtd2 is good! how about get back to netconsole and try both: > ubi part rootfs > ubifsmount ubi0:rootfsby bodhi - uBoot
musselmanb, Yours is no longer a bad block problem. This ubi error is typical, i.e. after the Pogo E02 installation we all have this error. Booting with USB is never a problem, but to try booting back to stock Pogo OS is problematic because of this (there had been frequent postings about this issue). 1. Please stop your netconsole and print out your envs. And I'll take a look. > pby bodhi - uBoot
@Geo, I'm also having problem with a Sandisk microSDHC 16GB (with Sandisk adapter). It was not recognized by this uBoot. Debian was fine with it after boot.by bodhi - uBoot
Kernel 3.12.0-kirkwood-tld-3 package was uploaded. Please see 1st post for download link.by bodhi - Debian
Geo, I did not see anything peculiar other than the read errors. Have you tried to reformat the 16GB card? (ie. on Windows or Mac).by bodhi - uBoot
fma965 Wrote: ------------------------------------------------------- > how can i get the hdd led's working on the nsa320, > ide-trigger doesn't seem to work any more. There is so little info in your post so we have no way to know how help. What kernel you're using? what do you boot with (USB, HDD)…., what did you see before updating …..and any log file.by bodhi - Debian
Geo, Quoteboot the kernel and or ramdisk. The MMC driver in uBoot seems to have problem with some SD cards. Might be the timing setings was too short and it's timed out too quickly. Exactly what point did the block read error occurred? Did you mean during loading either one of the images? But once both were loaded, then it is OK? Do you still have the log or can recreate it? Iby bodhi - uBoot
That should work. But cost a lot more than one without the cover on eBay. They all come from China so it will take the same amount of time to get to where you are!by bodhi - Off-Topic
dinjo Wrote: ------------------------------------------------------- > Little off topic but why doesn't /var/log/messages > gets updated with any actions ? It's in the instruction in first post. syslogd logs to RAM.by bodhi - Debian
SOL, No, currently your bootcmd boot Archlinux but not Debian. This needs to be changed bootcmd_linux=setenv bootargs $(bootargs_linux); ide reset; ext2load ide 0:1 $(loadaddr) /uImage; bootm $(loadaddr) to something like this: bootcmd_linux=setenv bootargs $(bootargs_linux); ide reset; ext2load ide 0:1 $(loadaddr2) /uInitrd; ext2load ide 0:1 $(loadaddr) /uImage; bootm $(loadaddr) $by bodhi - Debian
@eas, Sure, will add zswap to the next update. I think it is a little more flexible than zram in that it can age out the pages to disk.by bodhi - Debian
SOL, IIRC, WarheadsSE said the NSA325 stock uBoot does not support netconsole (it is very limited). You will need to have a newer uBoot such as Davy's NSA320 uBoot to provide that. However, I'm not 100% sure if it boots the NSA325 (but my guess is very probably it does). Your best approach is to get serial console working. It is quite easy to do that for the NSA3xxx boxes, all theby bodhi - Debian
Hi Davy, Welcome back! hope the life gear has shifted into a happier and better times for you! -bodhiby bodhi - Debian
Right! Don't mess with uBoot envs. Best if you print out uBoot envs while in Arch Linux so that we can check if they are set to boot both Debian and Arch. fw_printenv The uBoot bootcmd env might have been set to boot Arch only. So if that's the case, it will need to change to boot Debian. It's all depending on the current uBoot settings, so we need to verify that. If netconsby bodhi - Debian
Thanks for the info ricke.by bodhi - Debian
SOL, See this thread for the latest Debian rootfs and instruction: http://forum.doozan.com/read.php?2,12096 After you created the rootfs USB stick and booted into Debian, install this kernel (instruction also in that thread). The current rootfs has kernel linux-3.12.0-kirkwood-tld-1.by bodhi - Debian
Sheman, Which port did you plug in the USB thumb? Have you tried the back port next to the Ethernet? Also, if trying different port did not wok, then try this: reboot, interrupt netconsole, and manuall run "usb start" a few times to see how many tries you need before it is successfuly started.by bodhi - uBoot