2.6.32.5 new release

[cbxbiker61]

2.6.32.5 is now available.

Thanks to the discussion in other threads regarding crypt support, this kernel seems to finally be working properly with dmcrypt!  So please give it a go.  In a nutshell it seems that the toolchain distributed with the sheeva creates a broken dmcrypt subsystem.  I've substituted the toolchain located here http://www.codesourcery.com/sgpp/lite/arm/portal/release1033 into my build process.

Kernel and modules are available from the following location:

http://sheeva.with-linux.com/sheeva/

Features dmcrypt, IPV6, CIFS, NFS4, EXT3, EXT4, JFS, XFS, FUSE(for ntfs-3g), UBIFS, usb-serial, uvcvideo, iptables, appletalk, bluetooth, v4l and ppp.

[thejoker]

Well done! dmcrypt works without segmentation faults.
I think the next step shout be to include the CryptoDev device into the kernel. I read this http://plugcomputer.org/plugforum/index.php?topic=1014.msg6587#msg6587 post. Maybe you can add the patch to the next kernel.

[calamari]

Works perfectly, thank you very much!

[restamp]

FWIW, I just tried upgrading to the 2.6.32 kernel.  I had previously been running on a .31 kernel.  Apparently the .32 line (at least .32.2) does not have kernel support for NFS, which is a showstopper for me:

Code:

* Starting NFS common utilities                                          [ OK ]
* Not starting NFS kernel daemon: no support in current kernel.

(Or am I missing something obvious here?)

In any event, thanks for providing 2.6.31.9, which is running in my plug now.

YMMV.

I just configured an nsf4 server setup on my plug with 2.6.32.2.  Seems to work fine.

I'd have to wonder if your nfsd module was getting loaded in, or before, nfs-common runs.  Not sure why your config would work with .31.9 and not with .32.2.  With regard to nfs, the .32.2 is configured the same way .31.9 is.

This is a continuation of the thread from the 2.6.32.2 topic.  I'm still not able to export NFS file systems under the 2.6.32.5 kernel.  the nfsd module seems to be getting loaded, but the init_nfsd symbol is not appearing in /proc/kallsyms:

2.6.31.9:

Code:

$ lsmod
Module                  Size  Used by
nfsd                  262372  9
exportfs                4400  1 nfsd
dm_crypt               14460  0
dm_mod                 70788  1 dm_crypt
pl2303                 18916  1
usbserial              36752  3 pl2303

$ grep init_nf /proc/kallsyms
c0015e58 t init_nfs_fs
c0016048 T nfs_init_nfspagecache
c0025e0c t __initcall_init_nfs_fs6
bf07f000 t init_nfsd    [nfsd]
$

2.6.32.5:

Code:

$ lsmod
Module                  Size  Used by
nfsd                  238440  2
exportfs                3096  1 nfsd
dm_crypt               11154  0
dm_mod                 55672  1 dm_crypt
pl2303                 14876  1
usbserial              28308  3 pl2303
mv_cesa                 4714  0

$ grep init_nf /proc/kallsyms
c0015718 t init_nfs_fs
c00158ec T nfs_init_nfspagecache
c0025288 t __initcall_init_nfs_fs6
$

The lack of init_nfsd is causing the nfs-kernel-server script in /etc/init.d to fail.  I'd really like to get this working on .32.  Any suggestions?

[cbxbiker61]

The lack of init_nfsd is causing the nfs-kernel-server script in /etc/init.d to fail.  I'd really like to get this working on .32.  Any suggestions?

This would be one reason why that script probably shouldn't be relying on kernel symbols to decide whether nfs server support is running.  I don't have that particular script on my machine so I can't give you the "ideal" way.  The brute force approach would be to modprobe nfsd in the script and comment out the section that verifies the kernel has nfs server support running.

[restamp]

The lack of init_nfsd is causing the nfs-kernel-server script in /etc/init.d to fail.  I'd really like to get this working on .32.  Any suggestions?

This would be one reason why that script probably shouldn't be relying on kernel symbols to decide whether nfs server support is running.  I don't have that particular script on my machine so I can't give you the "ideal" way.  The brute force approach would be to modprobe nfsd in the script and comment out the section that verifies the kernel has nfs server support running.

Well, duh, sometimes I don't see the forest for the trees!  Commenting out this check fixed the problem.  Thanks, cbxbiker61!

[birdman]

Well, duh, sometimes I don't see the forest for the trees!  Commenting out this check fixed the problem.  Thanks, cbxbiker61!

Also reported, and workaround given, on the 2.6.32.4 thread here