2.6.30-rc8 cryptsetup support

[fragfutter]

where did you get/find the patches to fix the cpu_idle warning?

[calamari]

It's linked in the post above: http://patchwork.kernel.org/patch/40871/

However you can't directly apply the patch automatically since apparently the line numbers have changed. But it's pretty simple to apply manually.

[fragfutter]

Thanks. now my plug no longer complains

[micky]

There's a commit note from Aug 27th:

This adds support for Marvell's Cryptographic Engines and Security Accelerator (CESA) which can be found on a few SoC.
Tested with dm-crypt.

http://git.marvell.com/?p=orion.git;a=commit;h=24eb3f0cb48da8244d8c02bcb38e003e9c94522f

[calamari]

Yes, I guess that commit should already be contained in the orion build above. At least it also contains a Marvell-specific hardware accelerated crypto module.

[chronoboy]

Could someone post a HowTo on how to compile in dm-crypt support into a kernel on the PlugComputer wiki?  This would be a good addition to the wiki.

Kevin.

[calamari]

Could someone post a HowTo on how to compile in dm-crypt support into a kernel on the PlugComputer wiki?  This would be a good addition to the wiki.

Adding dm-crypt support is only a matter of selecting it in the menuconfig when you compile the kernel. Good HowTos on how to compile a custom kernel can be found at http://plugcomputer.org/plugwiki/index.php/Compiling_Linux_Kernel_for_the_Plug_Computer and http://computingplugs.com/index.php/Building_a_custom_kernel.

Note that cbxbiker61's precompiled kernels come with dm-crypt enabled, however it still seems to be broken.

If you only need a kernel with dm-crypt working, you can download one of those linked in http://plugcomputer.org/plugforum/index.php?topic=425.msg4152#msg4152 or http://plugcomputer.org/plugforum/index.php?topic=425.msg4164#msg4164.

[chronoboy]

Thank you, I will first try to compile my own kernel and see if that works...  I compiled a Linux kernel for Intel processor before and had various issues from time to time.  To make a failsafe kernel for the Sheeva plug, it would be best to use the default kernel config and then just add to that?  Also, would it be best for a first time Sheeva plug kernel hacker to use kernel.org, Debian source, or the kernel source from Marvell?

Also, is there a default ARM kernel in the Debian repos which would boot on the Marvell for testing purposes?

Kevin.

[micky]

I just tried the README-2.6.31-rc7-00165-g97f6ce5 kernel. It works fine with cryptsetup, but samba has a bug with this kernel (causes "Failed to read all inotify data" errors all the time).

I then tried the 2.6.31.1 kernel with your configuration from the kernel above (from /proc/config.gz). cryptsetup luksOpen crashed with this one.

Finally I switched back to the stock kernel which works stable with cryptsetup and Samba.

[Lt_Flash]

Tried compiling versions from Orion and from kernel.org - no luck. Still cryptsetup fails when tries to format device. Tried created by calamari image - works fine, don't know why Used same configs as he did, tried with or without patches - no luck. I need my own kernel to be built, can't use already compiled ones.

BTW - kernels from sheevaplug page doesn't work too, even latest 2.6.32.2.
Any ideas?

[Lt_Flash]

RESOLVED!
I was using shipped with SheevaPlug compile tools, after switching to latest tools from here: http://www.codesourcery.com/sgpp/lite/arm/portal/subscription3053 and re-compiling vanilla kernel everything's seems to be working fine!