2.6.39.3 new kernel available

[cbxbiker61]

2.6.39.3 is now available.

I've flogged the 2.6.39.2 kernel hard (compiling code) for the last week or so with no hiccups.  So I'd say the .39 series is in real good shape.

For everything besides Dreamplugs:
sudo ./README-PLUG-UPDATE.sh 2.6.39.3 --nandkernel (installs 2.6.39.3 to nand)

For Dreamplugs:
sudo ./README-DREAM-UPDATE.sh 2.6.39.3 (installs 2.6.39.3 to disk)

Kernel and modules are available from the following locations:

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

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

[pacolm]

Seems that has dissapeared from the server...

[cbxbiker61]

Seems that has dissapeared from the server...

I think you mean that it's not on the mirror?  For some reason the mirror has been having trouble updating with rsync.  I'm pretty sure it's a problem on the mirror end, I've tested on my local net using the same commands and have no problem.

[pacolm]

Hi,

 In my case, the first link works, but no 2.6.39/ exists:

Code:

Directory Listing of /mirror/with-linux/
home
File
Size
Last Modified
2.6.30/2.6.30/ - Mar 28 2011 09:40:39 PM
2.6.31/2.6.31/ - Mar 28 2011 10:14:39 PM
2.6.32/2.6.32/ - May 10 2011 09:46:57 AM
2.6.33/2.6.33/ - Mar 28 2011 10:14:39 PM
2.6.34/2.6.34/ - Mar 28 2011 10:14:39 PM
2.6.35/2.6.35/ - May 02 2011 10:01:43 PM
2.6.36/2.6.36/ - Mar 28 2011 10:14:39 PM
2.6.37/2.6.37/ - Mar 28 2011 10:14:39 PM
2.6.38/2.6.38/ - Jun 15 2011 08:29:48 PM
flash/flash/ - Jan 03 2010 03:31:18 AM
historic/historic/ - Mar 28 2011 10:14:39 PM
java/java/ - Mar 21 2010 10:06:32 AM
testing/testing/ - Jan 22 2011 04:23:10 PM
tools/tools/ - Jun 16 2011 12:48:51 AM
README-DREAM-UPDATE.shREADME-DREAM-UPDATE.sh 4KB May 11 2011 04:17:58 PM
README-PLUG-UPDATE.shREADME-PLUG-UPDATE.sh 5KB May 11 2011 04:18:11 PM

The second link does not connect, it gives a timeout.

Regards,

PacoLM

[cbxbiker61]

The second link does not connect, it gives a timeout.

The second link should work.  I'd have to wonder if maybe you have a misconfigured ipv6 setup on the machine you're using.  sheeva.with-linux.com will resolve as both ipv6 and ipv4 addresses.

Try to access http://216.146.103.100/sheeva/

[bwooster0]

Hi,

Thanks for the links to uImage + modules. I am a newbie and I have a Dreamplug that I have been playing with.

I am not sure how to use the software that you've linked to.

Is this what I need to do?

1) set up my dreamplug uboot to boot from an sd card

2) Format an SD card with a fat13 partition and an ext3 partition

3) copy uimage to the fat13 partition

4) untar the modules into the ext3 partition

Then what do I do?

Thanks for any help

[cbxbiker61]

Hi,

Thanks for the links to uImage + modules. I am a newbie and I have a Dreamplug that I have been playing with.

I am not sure how to use the software that you've linked to.

Is this what I need to do?

1) set up my dreamplug uboot to boot from an sd card

2) Format an SD card with a fat13 partition and an ext3 partition

3) copy uimage to the fat13 partition

4) untar the modules into the ext3 partition

Then what do I do?

Thanks for any help

You've pretty much got it.

The fat16 partition should be mounted at /boot.  Then when you run README-PLUG-UPDATE.sh it will put the new kernel in /boot.  You can then link it to uImage in the boot directory.  My bootcmd on a sheeva looks like this:

(athough I'm using ext2load, fatload is very similar)

Code:

ba_con=console=ttyS0,115200
ba_root=ro root=/dev/mmcblk0p2
ba_mtd=mtdparts=orion_nand:0x100000@0(u-boot),0x400000@0x100000(uImage),0x1fb00000@0x500000(root)
ba_ip=ip=192.168.1.55:192.168.1.44:192.168.1.44:255.255.255.0:DB88FXX81:eth0:none
ba_init=init=/bin/systemd
bootargs_old=console=ttyS0,115200 mtdparts=orion_nand:0x100000@0(uboot),0x400000@0x100000(uImage),0x1fb00000@0x500000(root) ro root=/dev/mmcblk0p2 ip=192.168.1.9:192.168.1.4:192.168.1.4:255.255.255.0:DB88FXX81:eth0:none
uimage=/uImage
bootcmd_mmc=mmcinit; mmcinit; ext2load mmc 0:1 0x800000 $(uimage)
bootcmd_nand=nand read.e 0x800000 0x100000 0x400000; bootm 0x800000
bootcmd=setenv bootargs $(ba_con) $(ba_root) $(ba_mtd) $(ba_ip) $(ba_init); run bootcmd_mmc; bootm 0x800000

[bwooster0]

Do I have to run the script? Can I just copy the uImage and then untar the files into the ext3 partition?

[cbxbiker61]

Do I have to run the script? Can I just copy the uImage and then untar the files into the ext3 partition?

Yes.

[bwooster0]

Sorry to be so dense but when you wrote yes did you mean that "yes" I have to run the script? Or did you mean that copying the files would be sufficient?

Thanks for your help!

[bwooster0]

Hi,

I copied and renamed the uImage file to my fat partition.

Then I did sudo tar xzvf sheeva-2.6.39.3-Modules.tar.gz -C /media/dp_debian

which gave me a /lib folder in my ext partition that has some stuff in it

What else do I need to do to make this a bootable SD card (my system already can boot from another SD card) so that I can try out the new kernel?

[bwooster0]

Hi,

I am sorry that I am asking a lot of questions. Here is what I want to do:

take a new SD card and run dreamplugs debian distro with the latest kernel from it.

I used my desktop linux computer to download your script and inserted my SD card into the desktop. The card has two partitions, a fat16 one called dp_kernel and an ext3 one called dp_debian.

Can you please explain what steps I need to do to make this work?

Thanks for your help

[cbxbiker61]

Hi,

I copied and renamed the uImage file to my fat partition.

Then I did sudo tar xzvf sheeva-2.6.39.3-Modules.tar.gz -C /media/dp_debian

which gave me a /lib folder in my ext partition that has some stuff in it

What else do I need to do to make this a bootable SD card (my system already can boot from another SD card) so that I can try out the new kernel?

Sounds like you put the files where they belong. Now just make sure your uboot env is set correctly.  You should be able to figure out what changes are necessary be reading the README.