2.6.37.3 new kernel available

[cbxbiker61]

2.6.37.3 is now available.

Apparently the dreamplug is working with the .35 kernels but not the .36 and .37 kernels.  If someone could research that a bit and find out why that is I could roll in the fixes.

Kernel and modules are available from the following locations:

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

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

[savale]

running it on my guruplug now. I'll post my experience. So far so good.

[aliosa27]

My dream/guru/pogoplug v2 are running 2.6.38-rc8 with the patches from your 2.6.37.x kernel.

[pacolm]

Hi,

 Newbie question: will the upgrade of kernel need to reinstall all the applications, or are they keep as they are?

Thanks,

PacoLM

[cbxbiker61]

Hi,

 Newbie question: will the upgrade of kernel need to reinstall all the applications, or are they keep as they are?

Thanks,

PacoLM

Upgrading the kernel doesn't affect the installed apps.

[newitjames]

For anyone wishing to solve the Dreamplug boot issue with kernels .36 and .37 here are my observations.

During the Boot:

loop: module loaded

<--- This is the point it freezes.

NAND device: Manufacturer ID: 0xec, Chip ID: 0xdc (Samsung NAND 512MiB 3,3V 8-bit)
Scanning device for bad blocks

<--- And I assume it never gets here because it's expecting an onboard Nand to be present and waits until it's found.

Can anyone find code in the kernel that would cause this?

[mihanson]

For anyone wishing to solve the Dreamplug boot issue with kernels .36 and .37 here are my observations.

During the Boot:

loop: module loaded

<--- This is the point it freezes.

NAND device: Manufacturer ID: 0xec, Chip ID: 0xdc (Samsung NAND 512MiB 3,3V 8-bit)
Scanning device for bad blocks

<--- And I assume it never gets here because it's expecting an onboard Nand to be present and waits until it's found.

Can anyone find code in the kernel that would cause this?

Has anyone figured this out yet? I see it on 2.6.38 as well. I was trying to look at a diff of the working 2.6.33 kernel config vs my 2.6.38 config and nothing jumps out at me.

Mike

[newitjames]

I have compiled the sheeva.with-linux kernel 2.6.38.2 with MTD support unchecked and that boots fine on the Dreamplug.

So that confirms the theory that it's waiting for a Nand device that it hasn't got.


     < > Memory Technology Device (MTD) support  ---> 


NewIT James