I can upload it, but it will be a while, since I'm on the road for a couple weeks.by bodhi - Debian
Quite a few people has problem with the rescue systems lately. I'm not sure why. I don't use it because I don't have a need for it, so I can't really have a good feel for the problem. If you can't make it work then I would suggest abandoning it for now. Just rerun the complete installation, and force a uBoot update and uBoot envs reset so you can get back to a bootingby bodhi - uBoot
Every thing looks normal. Another possible reason could be the USB brand, what brand the stick is? and can you try the intallation on another stick?by bodhi - uBoot
1. What is your envs looks like? from serial console uBoot prompt: printenv 2. Mount the Squeeze USB on another Linux box, and run (assuming the USB drive is mounted as /media/sda1) ls -l /media/sda1/boot/ What is the output of this ls -l command? do you see uImage and uInitrd ? if not, you will need to boot back to rescue system and generate them. If you've saved the installation loby bodhi - uBoot
Since so your situation is you can log in to the rescue system, and you have problem with Davy NSA320 rootfs, you should rerun the installation to install Debian Squeeze , and then upgrade to Wheezy. - Log in to the rescue system. - Use an empty USB thumb drive (it will be erased during installation). - Follow the installation instruction: http://projects.doozan.com/debian (use this scriptby bodhi - uBoot
It won't work on NSA320. I did not include support for it, since I don't have the NSA320, and don't have the appropriate patch.by bodhi - Debian
P21 is usually Oxnas, and has different installation procedure. To make sure that you have Oxnas version look at dmesg output (the first few lines shows the machine type). If it is V2 then all you need is to either rerun the installation for Debian. If it is Oxnas then see here: http://forum.doozan.com/read.php?3,6336by bodhi - Debian
I took a peak at the specs, some model has both master and slave mode. But still entirely not sure how it works :) does it work it just like a USB Bluetooth dongle?by bodhi - Off-Topic
@maihoa, Very interesting! have you found more info about tthis? Does it have to be plugged in to another USB Bluetooth adapter?by bodhi - Off-Topic
> # the next commands could brick the device if > something is wrong > cd /root > flash_erase /dev/mtd0 0 4 > nandwrite /dev/mtd0 uboot-original-mtd0.kwb > reboot Yeah :) best to double check the size of this image.by bodhi - uBoot
nguyen Wrote: ------------------------------------------------------- > Have anyone able to boot original Pogoplug Linux > using this uBoot? I never really try to do that. But it would be very doable. Just remember to save your orginal uBoot envs to a text file. And then later set them back to boot the correct mtdparts. Installing this uBoot image using Linux command only overwrites mby bodhi - uBoot
I've uploaded kernel 3.8.11 kirkwood package. See 1st post for updates.by bodhi - Debian
sosuke, You could execute uBoot envs in netconsole and see what happen. Execute this mmc boot command in 4 steps: mmc_bootcmd=mmc init; mmc init; ext2load mmc 0:1 0x00800000 /boot/uImage; if ext2load mmc 0:1 0x01100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi So stop uBoot at netconsole, and do these 4 commands consecutively. If you have get error with mmc_iniby bodhi - uBoot
@chessplayer, Unfortunately I can't find the individual patch for NSA320! there is a consolidated patch for Arch (by moonman) which has NSA320: https://github.com/archlinuxarm/PKGBUILDs/blob/master/core/linux-kirkwood/archlinuxarm.patch But it will take some works to extract it.by bodhi - Debian
chessplayer Wrote: ------------------------------------------------------- > bodhi, > > unfortunately, your package does not boot on the > Zyxel NSA320, as it does not recognize the machine > id (arcNumber = 3956; machid=f74). What must be > done to remedy this? > > Like davy's 3.3.2 kernel, it should not really be > a problem to use your's, I thinby bodhi - Debian
shv Wrote: ------------------------------------------------------- > Because also the 3.8.4 kernel doesn't work > flawlessly I am not sure if it is a FW or HW > problem. Before I try other things I will try an > old Squeeze with an old 2.x.y kernel. Until the > device don't work properly I will not change the > uboot. There are no problems with SATA but a lot &by bodhi - Debian
pr0, You're running stock uBoot, and this version is very limited in what you can do with uBoot envs. If you are comfortable with flashing new uBoot using a manual procedure (only recommended for more experienced users and with serial console for recovery purpose), then check out this thread, starting here: http://forum.doozan.com/read.php?2,6624,6959#msg-6959 and instructions here: htby bodhi - uBoot
First step, please post your output of fw_printenv from Debian. And also describe your setup a little more: if I understood correctly, the other 2 sticks are USB ? plugged into the front USB ports?by bodhi - uBoot
sosuke, Looking back at Davy's thread: The rootfs is packaged as an ext3 image (kirkwood-debian_image.img) so you'll have to mount with the loop option, and cp -a the contents onto a preformatted sda1 partition. Did you do this to create the rootfs stick? note that the rootfs image is ext3. So your uBoot env for rootfs type should be ext3. Usually it's OK for booting ext3 eby bodhi - uBoot
SiruS, I will upload kernel 3.8.11 in a couple days.by bodhi - Debian
SiruS, I think you probably solved this with this solution! we will see if the error repeat. But looking at the explanation for memory tuning at openSUSE site, it is very specific how this number would help to eliminate page allocation failure error. Yeah, LOL at 64M :)) we don't have that much to spare :)by bodhi - Debian
> > p.s. a few blogs/forum threads related to openwrt > and similar lowmem devices I've found recommended > setting /proc/sys/vm/min_free_kbytes at least 8192 > bytes to eliminate this failtures. This is interesting. Thanks SiruS! BTW, when you see this error, are you running your boot HDD as USB or SATA? I've moved the swap file to a different stick otherby bodhi - Debian
ian, How long have you waited before trying to log in through ssh? which file system is on your USB, ext2 or ext3? If it's ext2, then take the stick to a different Linux box and run e2fsck to check error. If it ext3 then wait for a few minutes to see if it was recovering from error.by bodhi - Debian
Of course you're right! I turned on debug for both netconsole and hush parser. Hush parser works with no problem. Netconsole was the problem since it echos back the incompeted command string before hush takes it. The strange thing is if I turned on netconsole debug option, then the command was echo back OK (no dropped 2nd char). But still it won't boot with netconsole.by bodhi - uBoot
shv, I see now. I agree that if you're booting with a power USB hub only and uBoot shows "EHCI timed out" error, then it sounds like uBoot problem. That's what I've learned also, people reported this problem quite often with USB hub. It might be some settings need to be adjusted in uBoot like you're mentioned. I've compiled a GoFlex Net uBoot 2013.01 for Fby bodhi - Debian
syong, No effect of the error. Everything works normally. It occured while rsync was coppying 11GB file over wire. The plug that showed error was the source plug, the destination plug runs identical kernel with HDD swap, and showed no error.by bodhi - Debian
@syong, Re http://forum.doozan.com/read.php?3,12218,12378#msg-12378 Reset_phys does not seems to be the problem. I think it might be a bug in hush parser.by bodhi - uBoot
@chessplayer, Did you set up rootfs label envs for your SATA booting? what your envs look like? The same concept here: http://forum.doozan.com/read.php?2,12045,12432#msg-12432by bodhi - Debian
Syong, Right now, I'm seeing a similar error (rsync other ethernet related) you got. This is in my plug that has USB swap. Not on another plug with only HDD swap. And both are being used heavily as NAS. I think I will try to use another ext3 USB for swap to see if I can isolate this. And then perhaps kernel 3.8.x. To see if this error is just with ethernet activity.by bodhi - Debian