good point you made with different uBoot versions on NSA320, both of my boxes still have the
stock firmware zyxel uBoot, maybe I should test davygravy's uBoot version,... he explicitly mentions
the ability to boot from BOTH sata ports with his uBoot version,.. which seems not to work with the stock uBoot,..
and also incorporated the [U-Boot] [PATCH] fix IDE_BUS(dev) macro,..

so perhaps there really is something different with SATA port number assignments and stock firmware uBoot,..
before building 3.10.18 longterm and incorporating your ide-disk patch I will switch to davygravy's uBoot version
and report back,..

gee-man Wrote:
-------------------------------------------------------
> The results of lsmod are attached. Since
> installing 3.11.1, I have experenced other
> problems with samba, and failed reboots.

gee-man,

There are differences in the list of modules loaded. I suspect that is your problem. I would do this:

Make a clone of your USB 3.3.2 rootfs stick. Use the new stick, boot the box, upgrade the kernel to 3.11.1, and then do
apt-get update
apt-get upgrade

I tried what you suggested, but I am still having the same problems. My system was already up to date, so apt-get update and apt-get upgrade didn't have any effect. I tried re-installing strongswan, but am still having the same problem.

Is this kernel missing AES support?? I can't seem to find the aes_generic and mv_cesa (for hardware accelerated encryption) modules that were included in 3.3.2..

mbmsof Wrote:
-------------------------------------------------------
> Hi, a few days ago that u-boot install in my
> nas320 and everything works perfect, but today
> tried to install a second hard drive and now not
> boot.
>
> Hard drives are Seagate 2TB, with either boots,
> but if I put the two no.
>
> This is what appears when you start:
>
>

To try building this kernel myself, which kernel source should I download? From kernel.org with no patches, or should I get the debian source that has all the debian patches applied (package linux-source-3.11)?

After I do that, I will apply your kernel patch, and use the kernel config in my /boot directory for this kernel.... I already downloaded and installed shyd's toolchain (http://dev.shyd.de/2011/03/dockstar-crosscompile-newer-kernel-set-toolchain/), will this work to compile this kernel?

The source should be from kernel.org with no patch. I'm not familiar with shyd's tool chain so can't comment on that. But it should compile if it is for the Dockstar. The problem you might run into is the difference in config options.

I'm building kernel 3.12, and will take a look in the config to see if any AES-related option is missing.
(UPDATE: just checked, nothing is missing, all options for crypto are selected).

Upstream Kernel 3.12 has removed all the Kirkwood patches for mach-types :)) They expect that everybody has switched to FDT scheme. So it is a little time consuming to get back all those files from 3.11.

Hmm. There is a symbolic link /lib/modules/3.12.0-kirkwood-tld-1/build
However, I can not read it: No such file or directory
Therefore, I am deleting /lib/modules/3.12.0-kirkwood-tld-1/build

Hmm. The package shipped with a symbolic link /lib/modules/3.12.0-kirkwood-tld-1/source
However, I can not read the target: No such file or directory
Therefore, I am deleting /lib/modules/3.12.0-kirkwood-tld-1/source

This is my autoremove settings. I think you should have "^linux-image.*", and other options too, in your NeverAutoRemove list. Modify your list and reboot to verify that it takes effect after the next boot. Remember to check your kernel files in /boot to make sure they are consistent before you reboot.

I noticed a strange problem.
I first compiled my own 3.11.6 kernel uImage and saw the problem and now tried your kernel 3.12 with the same results.

I have tried to setup different swap partitions/files whatever, which get recongnized and seen correctly, but it seems that these never get used. And that, although free memory gets VERY low while copying huge files. Even to the point where the OOM starts kicking in. VERY STRANGE!

Anyone of you checked their SWAP usage?
Does this work for you?

Greets from bavaria

Ingmar

Edit: Nevermind! Problem solved, although I don't know yet, how. I went back to using my own kernel and again added the entry for a swap partition on a USB stick into my fstab. And now, using stress as a test tool, I can see the system using swap. Very strange indeed. Will have to investigate why it didn't work before.

Edit 2: OK, had zcache and zswap enabled via the kernel commandline. One or both of those two probably made the "normal" swap not work anymore. Don't know if that is by design, or buggy behaviour. I would guess the latter.
Edit 3: Hmm, those were not even included in bodhi's kernel. So I guess it should've been something else. Oh well, maybe I will figure it out.

bodhi Wrote:
-------------------------------------------------------
> Upstream Kernel 3.12 has removed all the Kirkwood
> patches for mach-types :)) They expect that
> everybody has switched to FDT scheme. So it is a
> little time consuming to get back all those files
> from 3.11.

With those patches removed, does this mean the 3.12 kernel will not work as well as earlier versions? I tried compiling the kernel myself with your 3.12 configuration file and some additions. The goflex seems to have booted up, the solid green light came on, but then, I couldn't communicate (ping or ssh) at all with the device...

I'm now trying to build this kernel with the config file from 3.3.2 with some minor additions to the .config on the goflex itself. It will be another 5 hours before it finishes...

> With those patches removed, does this mean the
> 3.12 kernel will not work as well as earlier
> versions?

It works the same way. Just a matter of copy files back to their old place, and modify the configuration files to point the the old location. To compile the kernel you will need to apply the patches. Without them, the mainline code won't work for Kirkwook boxes with the current uBoot any more.

One observation: since you're upgrading from 3.3.2 to 3.11 or 3.12, I think a few of package configuration files might have changed. You might end up with the same errors even with your onw build.

That's all that happens, and the goflex shows a solid green light, but I can't ping the device or anything...I am going to try downloading and compiling 3.11 with your kernel source patch, and this config file and see if that works..

Since you're going to roll your own kernel, I would recommend to have serial console to watch the kernel booting progress. Netconsole does not show you the type of details needed to troubleshoot kernel booting.