2.6.33 new release

[cbxbiker61]

2.6.33 is now available.

Added support for sata using the "sata_mv" module.  If for any reason your sheeva seems to hang when initializing sata_mv, you should blacklist the "sata_mv" module in your modules config file.  So far in my testing this hasn't been necessary.

Kernel and modules are available from the following location:

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

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

[jrmt]

Yup, this kernel works fine. Many thanks.

[Abra]

I compiled a vanilla 2.6.33 + sata patch (the one modifying sheevaplug-setup.c), and with the original uboot (I have an esata sheeva from newit), which is marvell version 3.4.16 I think, it hangs when initializing sata_mv:
....
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
console [ttyS0] enabled
loop: module loaded
sata_mv sata_mv.0: version 1.28

and it hangs at that point

using the uboot found here: http://www.naobsd.org/sheeva/ (I had to flash uboot to load the kernel from a sata HD whatsoever), no problem.
So apparently uboot changes something... this is quite a mystery to me  
If anyone has an explanation, I would be very interested.
Btw, is there an "official" version/repo of u-boot? It seems everyone patches an already patched version etc. What is recommended?

[meditux]

the kernel works fine.

thanks. 

[mgillespie]

Thanks, working here Globalscale 1.3 Sheevaplug.

[xoxox]

Thanks, pptpd with mppe-encryption works out-of-the-box now.

[TheBigYahi]

Can anyone confirm if SATA works without hassle on a modified V1.3 Globalscale plug?  After seeing it supported now I went ahead and ordered the parts for the mod from this thread.

[robot_maker]

Hello.  Hopefully you can easily answer this.  I am interested in a kernel with support for GPIO pins as have been discussed in earlier posts.  Are there kernel versions available with GPIO support or do I need to compile one.  If I need to compile one, how do I go about doing that?  I have never compiled a custom kernel.  Thanks.

[UnaClocker]

So what's the story behind the 2.6.32.x vs a version without the extra .x? Does that mean 2.6.33 is a more stable release than say 2.6.32.8?

[mundhra]

So what's the story behind the 2.6.32.x vs a version without the extra .x? Does that mean 2.6.33 is a more stable release than say 2.6.32.8?

the progression goes:

2.6.32
2.6.32.1
...
2.6.32.12 (until they decide to rollover to .33)
2.6.33
2.6.33.1
...

if you notice the dates on the kernel directories at http://sheeva.with-linux.com/sheeva/, 2.6.31 is located in the sort order after 2.6.31.12 but by date falls between 2.6.30.9 and 2.6.31.1. i don't know for sure but i would assume that the 2.6.32.x revs are all bug fixes/security updates to the major changes brought up in 2.6.32. 2.6.33 then brings new things and gets bug fixes as well. theoretically then, the last .x build would be the most stable compared to a non-.x build.

this is just post-drinking conjecture, mind you.

oh, found a link (http://en.wikipedia.org/wiki/Linux_kernel#Version_numbering).

[dattaway]

And if you want even more current bleeding edge updates, there is the "git" patches from kernel.org:

linux-2.6.33-git15

http://kernel.org/

[snake]

Hello cbxbiker61,

Upon trying to update my plug's kernel image from sheeva-2.6.30.2-uImage to sheeva-2.6.33-uImage I encountered errors.

My procedure was:
1. Use sheevaplug-installer-v1.0
2. populate the usb stick and use sheeva-2.6.30.2-uImage and modules

I tried it again and just replaced the uImage with sheeva-2.6.33-uImage and its corresponding modules. I am attaching the logs in case someone would like to see.

By comparing the logs, I am having some speculation that the problem starts at initializing the UBI device but I am not sure at all...

Hope you could help point out which part of the kernel source is affecting this. (if possible).

Thanks in advance.

[snake]

Hello cbxbiker61,

I also tried writing the sheeva-2.6.33-uImage directly into the NAND by:

1. Flashing the plug first with sheeva-2.6.30.2-uImage
2. Boot-up the plug
3. Use "nandwrite" to write the sheeva-2.6.33-uImage directly into the NAND
4. Reboot


The plug was able to boot-up successfully. I think this will do for my case.

I am just wondering whether this is a bug during compilation... Thanks again!