2.6.32.4 new release

[cbxbiker61]

2.6.32.4 is now available. 2.6.31.12 is also available in case .32 exhibits any problems.

dm9601 support has been added.

Kernel and modules are available from the following location:

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

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

[hacker_54]

Thanks, you´re the best 

[TJeh]

Hi,

while trying to set up NFS i keep running into the following message:

Code:

* Not starting NFS kernel daemon: no support in current kernel.

any thoughts why it is not working ?

Regards,

TJeh

P.S.: I am using the current 2.6.32.4

[birdman]

Hi,

while trying to set up NFS i keep running into the following message:

Code:

* Not starting NFS kernel daemon: no support in current kernel.

any thoughts why it is not working ?

Hve you loaded nfsd?  It's a module:

birdman@plug:~ $ zgrep NFS /proc/config.gz
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
# CONFIG_NFS_V3_ACL is not set
CONFIG_NFS_V4=y
# CONFIG_NFS_V4_1 is not set
CONFIG_ROOT_NFS=y
CONFIG_NFSD=m
CONFIG_NFSD_V3=y
# CONFIG_NFSD_V3_ACL is not set
CONFIG_NFSD_V4=y
CONFIG_NFS_COMMON=y

[pallinger]

I tried tried to use this kernel image, to no avail. If I type the following in uboot prompt:

Code:

mmcinit
ext2load mmc 0 0x0800000 /sheeva-2.6.32.4-initrd
ext2load mmc 0 0x400000 /sheeva-2.6.32.4-uImage

I simply hangs there, I can't run the bootm command, I have to hard reset.
Does anyone have any idea what the problem could be?
Maybe the kernel is too big, and overwrites something (the uboot itself, maybe)?
Did anyone have a similar problem?

Ps: I generated the initrd with debian's standard tools, but even without loading it, the ex2load for the uimage hangs. However, it loads fine with the old kernel (kirkwood's 2.6.30-2).
Ps2: U-Boot 1.1.4 (Sep 14 2009 - 15:36:37) Marvell version: 3.4.19

[pingtoo]

I tried tried to use this kernel image, to no avail. If I type the following in uboot prompt:

Code:

mmcinit
ext2load mmc 0 0x0800000 /sheeva-2.6.32.4-initrd
ext2load mmc 0 0x400000 /sheeva-2.6.32.4-uImage

I simply hangs there, I can't run the bootm command, I have to hard reset.
Does anyone have any idea what the problem could be?
Maybe the kernel is too big, and overwrites something (the uboot itself, maybe)?
Did anyone have a similar problem?

Ps: I generated the initrd with debian's standard tools, but even without loading it, the ex2load for the uimage hangs. However, it loads fine with the old kernel (kirkwood's 2.6.30-2).
Ps2: U-Boot 1.1.4 (Sep 14 2009 - 15:36:37) Marvell version: 3.4.19

I read somewhere in this forums the 0x400000 is not a good place to load kernel, I recommend use 0x02000000 for kernel and 0x01100000 fro initrd/initramfs.

[TJeh]

@birdman

here is the output:

Code:

root@ubuntu:~# zgrep NFS /proc/config.gz
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
# CONFIG_NFS_V3_ACL is not set
CONFIG_NFS_V4=y
# CONFIG_NFS_V4_1 is not set
CONFIG_ROOT_NFS=y
CONFIG_NFSD=m
CONFIG_NFSD_V3=y
# CONFIG_NFSD_V3_ACL is not set
CONFIG_NFSD_V4=y
CONFIG_NFS_COMMON=y
root@ubuntu:~# lsmod
Module                  Size  Used by
nfsd                  251628  1
exportfs                3308  1 nfsd
ipv6                  246849  16
dm_crypt               12186  0
dm_mod                 60748  1 dm_crypt
mv_cesa                 4982  0
root@ubuntu:~# /etc/init.d/nfs-kernel-server start
 * Not starting NFS kernel daemon: no support in current kernel.
root@ubuntu:~#

the module nfsd seems to be loaded... any other ideas?

Regards,

TJeh

[birdman]

I tried tried to use this kernel image, to no avail. If I type the following in uboot prompt:

Code:

mmcinit
ext2load mmc 0 0x0800000 /sheeva-2.6.32.4-initrd
ext2load mmc 0 0x400000 /sheeva-2.6.32.4-uImage

I simply hangs there,

Where did sheeva-2.6.32.4-initrd come from?
I use:

ext2load mmc 0:1 0x800000 /uImage; bootm 0x800000

and always hard link uImage to the latest kernel, so I don't need to change anything under uboot.  Copy in files, boot from slogin.  Never need serial console.

[birdman]

the module nfsd seems to be loaded... any other ideas?

I've added nfs so I can have a look.

Code:

sh -x /etc/init.d/nfs-kernel-server start

show this to be the problem:
+ grep -qE init_nf(sd|  ) /proc/kallsyms                                       

+ log_warning_msg Not starting NFS kernel daemon: no support in current kernel.[/tt]
It seems that the symbol is not there (but lots of $a and $d symbols are, whatever that is).

If you edit /etc/init.d/nfs-kernel-server and change the grep command on line 76 to be

Code:

grep -qE 'init_nf(s_fs|sd|   ..... 

(JUST INSERT s_fs| at the start - there a tab later in the line...) then the server starts up and seems to work (it lets me mount filesystems remotely, anyway).

[TJeh]

Thanks birdman... that solved the startup issue

I am trying to set up a nfs connection between my plug and a windows 7 machine but have failed miserably so far.

If I manage to set it up I will post it...

Regards,

TJeh

[pallinger]

Where did sheeva-2.6.32.4-initrd come from?

sheeva.with-linux.com

I use:
ext2load mmc 0:1 0x800000 /uImage; bootm 0x800000
and always hard link uImage to the latest kernel, so I don't need to change anything under uboot.  Copy in files, boot from slogin.  Never need serial console.

Well, that is okay if your boot process does not hang...

[pallinger]

I read somewhere in this forums the 0x400000 is not a good place to load kernel, I recommend use 0x02000000 for kernel and 0x01100000 fro initrd/initramfs.

Thanks for the recommendation, now loading the kernel into memory works. However, the bootm 0x02000000 0x01100000  command does have difficulties:

Code:

## Booting image at 02000000 ...
   Image Name:   Linux-2.6.32.4
   Created:      2010-01-18  22:56:18 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2861348 Bytes =  2.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 01100000 ...
Bad Magic Number�

(And it reboots after that...) It seems that the problem is with the initrd, as the kernel boots if I only specify bootm 0x02000000. This is all right for me, as I do not use an encrypted or remote root file system currently.
However, I may want to do that later, so if anyone has experience with debian initrd creation on the sheeva plug, please don't hold yourself back to share it with me.

[pingtoo]

Where did sheeva-2.6.32.4-initrd come from?

sheeva.with-linux.com
...

I am curious which subdirectory in sheeva.with-linux.com? I can not find it.

[pallinger]

I am curious which subdirectory in sheeva.with-linux.com? I can not find it.

http://sheeva.with-linux.com/sheeva/index.php?dir=2.6.32.4%2F

[pingtoo]

I am curious which subdirectory in sheeva.with-linux.com? I can not find it.

http://sheeva.with-linux.com/sheeva/index.php?dir=2.6.32.4%2F

But In the directory there is no *initrd* I think this is the whole point we are asking Did you construct it you self? if yes how? that may help us to understand why the load got crc error.