Maybe you could work around the bootarg problem by using kernels that you compiled yourself. This way you could tell the kernel to use hardcoded bootargs instead of the ones provided by uBoot. This can be done pretty easily in the kernel configuration.by ingmar_k - uBoot
To know which kernel you are running at the moment, please run the command "uname -a". ;-) Just because there is a certain kernel image in the "right" directory, it doesn't necessarily mean that it is actually being used. The kernel you are running right now gets loaded directly from NAND. There is no directory (by default) to browse that.by ingmar_k - uBoot
If the Pogo P25 is OXNAS based, which I don't know ATM, then there is a new Uboot version provided by kref that supports USB boot etc. I flashed it to one of my B04 Pogo V3s a few weeks back. Seems to run just fine. Only the power consumption numbers seem a bit higher. But considering that the device only stays at the Uboot prompt if you explicitly stop it there, that is NOT a problem atby ingmar_k - uBoot
I probably did not include all wifi modules in my kernels. If that is the case for the one you need, then feel free to recompile the kernel with a configuration of you liking. I provide the sources via github ( www.github.com/ingmar-k ). If you need a newer kernel than version 2.6.31, you could have a look at kref's work ( www.github.com/kref ).by ingmar_k - uBoot
This would normally be done via hdparm (hdparm.conf settings-file). But having the system directly on the drive, makes hdparm ignore it for spindown, IIRC. So, best solution would be to have the system on USB, NAND or whatever and only using the drive for storage. IF, spindown is mandatory for you, that is. ;-)by ingmar_k - Debian
@ricke: Vmlinuz should indicate the use of a compression algorithm. I would guess gzip, but you should be able to find out exactly with the help of some tools. "file" perhaps? @WarheadsSE: Thank you for the useful information! I didn't do extensive tests yet and just used xz as an example above. One thing, though: Isn't there special ARM-asm code for some selected compby ingmar_k - uBoot
If the NSA325 has enough NAND Flash (>=128MB), then a Emdebian install in NAND should not be too difficult.by ingmar_k - Debian
And that is curious how? You set the command. Then I guess that no bootcmd was set before and autoload is enabled. That could probably explain why your Pogo then runs that bootcmd_usb. I don't know what you did besides that. The main point is: You try to load a kernel compiled for kirkwood devices (look at the output you posted) and that leads to a reboot. Simple as that. Get the rightby ingmar_k - Debian
An interesting question at that point is: What file do you use as a basis for creating the Uboot uImage? I'm asking this, because most of the time, it's zImage for example, which is already compressed. Trying to recompress that doesn't gain much. So, creating the uImage with the compression option "none" could yield the exactly same results (worst case) as using a speciby ingmar_k - uBoot
For those wanting to try the 3.12 kernel with a Pogoplug V3 Classic, here is a test version: http://www.hs-augsburg.de/~ingmar_k/Pogoplug_V3/kernels/3.12.0-ppv3-classic-1.0.tar.bz2by ingmar_k - uBoot
English is not my native language. ;-) IMHO, the risk alone of getting a damaged image, while still thinking this is a safe way, is enough to indicate that it is probably wrong advice.by ingmar_k - uBoot
IIRC nanddump does mind the nands error correction algorithms, which should always result in a useable image. 'dd' on the other hand doesn't care, which could result in a unuseable image. But I didn't do extensive testing and/or source code reading on the matter. The question is: Why risk it?by ingmar_k - uBoot
You don't use 'dd', but 'nanddump' for nand images, if you want a working copy.by ingmar_k - uBoot
Good to hear that you got it working. But you know that you made your life harder than necessary? You should really read up a bit on apt, the sources.list and the available repositories. This could definitely help you next time. https://wiki.debian.org/Apt https://wiki.debian.org/SourcesListby ingmar_k - Debian
Big thanks to navym, again! Highly appreciated! I just asked him for details and he was nice enought to provide all necessary steps in the archlinux forums: Quotenavym https://github.com/kref/linux-oxnas/wik ... the-kernel to generate old u-boot compatible uImage ARCH=arm make ox820_defconfig ARCH=arm make menuconfig Boot options ---> [*] Use appended device tree blob to zImageby ingmar_k - uBoot
I'm experiementing with it at the moment. It seems like we need a newer Uboot version first to handle the new 3.12 kernel. At least my stock uboot couldn't load any of the test kernels yesterday. Others already have it working, so it nearly has to be the old Uboot version. And yes I am still testing with Debian. In this case with Debian Jessie/Ttesting to be precise. Will run moreby ingmar_k - Debian
You should check your facts, my friend. ;-) The package is readily available for all current debian versions on ARM (armel in this case). Check here: http://packages.debian.orgby ingmar_k - Debian
Yesterday evening I did compile a test kernel (v3.12) for the Pogoplug V3 Classic and Pro. I will test the kernels today and upload them, if they work. Did want to try the new version anyway.by ingmar_k - Debian
I don't know if there are any ready-to-use solutions yet. If not you could read up on debootstrap and its use. If Arch works you probably already have a kernel to use. So all you need is a rootfs.by ingmar_k - Debian
Interesting! When setting up my Goflex some days ago I noticed some strange behaviour, too. You could try setting the priority of the swap, explicitly, to something like 1 or 10. Per default I think it gets assigned a priority of -1. When experimenting with swap I found that the swap with no explicit priority setting just didn't get utilized. Set the swap priority to some explicit numbeby ingmar_k - Debian
If Arch works, Debian should work, too. I don't see a reason, why not.by ingmar_k - Debian
I guess setting swappiness to 1 was a quite bad idea. Now you seem to run out of RAM, it seems and the swapping doesn't kick in fast enough. You could try the solutions suggested here: http://serverfault.com/questions/236170/page-allocation-failure-am-i-running-out-of-memory Just the result of a little quick googling.by ingmar_k - Debian
If you are impatient, you can be one of the first to try the new kernel. There is also a slightly different, previous version available. It is based on kernel 3.1.11. Have a look here: https://github.com/kref/linux-oxnas There are different branches for 3.1.11 (branch oxnas) and 3.12 (branch 3.12).by ingmar_k - Debian
apt-get install openvpn etc. ...?by ingmar_k - Debian
You could wait. There is some development going on. An effort of the OpenWRT community to get kernel version 3.12 working on the PLX7821 devices.by ingmar_k - Debian
You are right, for "older" versions of either Debian or Ubuntu "qemu-system-arm" does not exist. It does however for all new Ubuntu versions and debian (starting with sid). I will probably change this soon. At least for Debian. Thanks for the hint! About the kernel: It is not that easy. The Kernels with version number 3.1.10 are suboptimal, to say the least. The best kernby ingmar_k - Debian
Nice! I thought I had that problem covered and luckily enough, it works. About the thread you linked to: BIG MISTAKE! "Kirkwood" is the codename of a CPU, as is "OXNAS". Now you obviously have a Pogoplug V3 (for example B04). This unit uses a PLX 7821, a.k.a OXNAS 820 a.k.a OX820 CPU. Kirkwood is the codename of a CPU made by Marvell. You can't ever use a kernel thaby ingmar_k - Debian
Good to hear. Your problems at first with Debian were simply caused by the Arch kernel being too old. I don't know which of bodhi's threads you mean. Care to post a link? The usual method for a kernel update for NON-SATA boot is described here (section "Flashing and testing a new kernel"): https://github.com/ingmar-k/Pogoplug_V3_Emdebian_Debian/blob/master/README.md Concby ingmar_k - Debian
No worries! If you have any good points, for example where the descriptions needs to be clearer or something like that, let me know. If you write the software yourself, you often forget to explain some things, because they are obvious to you. So input would be welcome.by ingmar_k - Debian
Have a look at this: https://github.com/ingmar-k/Pogoplug_V3_Emdebian_Debian BUT, please read the instructions and the comments in the settings-file VERY carefully. If you have questions, just ask.by ingmar_k - Debian