• Home
  • Help
  • Search
  • Login
  • Register
Pages: 1 [2] 3 4
Author Topic: 2.6.31 new release  (Read 13251 times)
cbxbiker61
Global Moderator
Sr. Member
*****

Karma: 38
Posts: 497


View Profile
« Reply #15 on: September 16, 2009, 01:35:40 PM »

UBIFS only affects the "root" mtd partition.  The kernel is written to the "uImage" mtd partition in a raw format.

If you "cat /proc/mtd" and you see a "uImage" partition you'll be fine.
Logged

DamonHD
Full Member
***

Karma: 4
Posts: 169


View Profile WWW
« Reply #16 on: September 16, 2009, 01:41:52 PM »

Hi,

I do, thank you:

dev:    size   erasesize  name
mtd0: 00400000 00020000 "uImage"
mtd1: 1fb00000 00020000 "rootfs"

I'll try to 'flash' tomorrow morning.  I'll let you know how it goes.

Rgds

Damon
Logged

cbxbiker61
Global Moderator
Sr. Member
*****

Karma: 38
Posts: 497


View Profile
« Reply #17 on: September 16, 2009, 01:55:21 PM »

cbxbiker61, first, thanks for all the work you do in order to make up-to-date kernels available to us.  I would personally suggest that you consider modifying your README script so as to reverse the sense of the "--rootkernel" argument, or require an argument one way or the other.  My reasoning is this:  If one mistypes or forgets this argument, they'll wind up inadvertently blowing away their NAND kernel, something which may be difficult for them to undo.  However, if the default were to copy the kernel into /boot, then a typo only creates an extra file on their filesystem - something that does not break anything and is easily remedied.  (You might also consider adding a line to create the /boot directory, if it does not exist.)

README-2.6.31 and README-2.6.30.7 have been updated to accept two arguments.  No arguments prints help.
--nandkernel, writes kernel to NAND
--rootkernel, writes kernel to /boot
Logged

restamp
Global Moderator
Sr. Member
*****

Karma: 4
Posts: 273


View Profile
« Reply #18 on: September 16, 2009, 01:57:40 PM »

Thanks!
Logged

birdman
Sr. Member
****

Karma: 4
Posts: 443


View Profile WWW
« Reply #19 on: September 16, 2009, 02:56:27 PM »

Then again, for all I know, I may be the only person using BTRFS on the sheevaplug.
I was going to have a play with it once I have 2.6.31 in place.  I've taken a copy, thanks.
Logged

Catalina
Newbie
*

Karma: 0
Posts: 2


View Profile
« Reply #20 on: September 16, 2009, 03:27:45 PM »

I just ran the V1.0 Installer on my Sheeva which gets it to version 2.6.30.2.  Once you get through that (see other threads), getting the 2.6.31 kernel going was very easy.  Download the README-2.6.31 file to your Sheeva, make it executable and type:
./README-2.6.31 --nandkernel

Wait for the files to be downloaded and a re-flash.

Reboot and wait for the Sheeva to come up.

Type
uname -a

and you'll get
Linux ubuntu 2.6.31 #2 PREEMPT Wed Sep 16 00:55:42 MDT 2009 armv5tel GNU/Linux

I haven't run any extensive tests, but the application I run and ssh runs without a hitch.

Nice work and thanks to all!
Logged

DamonHD
Full Member
***

Karma: 4
Posts: 169


View Profile WWW
« Reply #21 on: September 17, 2009, 01:08:40 AM »

Yes!!!

--nandflash did the business for me, I'm now using 2.6.31, and in particular plugging in an empty USB hub no longer soaks up 1W!

That will make my life so much easier!

(However, plugging anything into the hub eats up that power again...)

Rgds

Damon

« Last Edit: September 17, 2009, 01:29:39 AM by DamonHD » Logged

nephilim1973
Newbie
*

Karma: 0
Posts: 17


View Profile
« Reply #22 on: September 17, 2009, 04:42:34 AM »

Great work !

Short question:  Is it possible to add support for em28xx (video4linux) in kernel ?

Please look at
http://plugcomputer.org/plugforum/index.php?topic=730.0

Best regards
Nephilim
« Last Edit: September 17, 2009, 09:40:50 AM by nephilim1973 » Logged

rooster
Administrator
Sr. Member
*****

Karma: 8
Posts: 311


View Profile
« Reply #23 on: September 17, 2009, 04:53:41 AM »

guys, if you want to burn the new kernel with the installer simply do the following on your PC:

wget http://sheeva.with-linux.com/sheeva/2.6.31/sheeva-2.6.31-uImage
wget http://sheeva.with-linux.com/sheeva/2.6.31/sheeva-2.6.31-Modules.tar.gz
mv sheeva-2.6.31-uImage uImage
mv sheeva-2.6.31-Modules.tar.gz modules.tar.gz

Now place the uImage and modules.tar.gz in the sheevaplug-installer-v1.0/installer/ directory and run the runme.php to start the installer.
Logged

DamonHD
Full Member
***

Karma: 4
Posts: 169


View Profile WWW
« Reply #24 on: September 17, 2009, 05:13:39 AM »

Good info, thanks!

Rgds

Damon
Logged

nephilim1973
Newbie
*

Karma: 0
Posts: 17


View Profile
« Reply #25 on: September 17, 2009, 11:09:06 AM »

2.6.31 works...  but...
Code:
root@ubuntu:~# lsmod
Module                  Size  Used by
ipv6                  271508  10
dm_crypt               14460  0
dm_mod                 70700  1 dm_crypt

... the number of loaded modules is very low.

You'll get the same result?
Logged

DamonHD
Full Member
***

Karma: 4
Posts: 169


View Profile WWW
« Reply #26 on: September 17, 2009, 11:47:56 AM »

Basically, yes.

Is that just because most stuff is compiled in rather than loadable modules?

Rgds

Damon
Logged

TJeh
Newbie
*

Karma: 0
Posts: 20


View Profile
« Reply #27 on: September 17, 2009, 01:11:36 PM »

 Grin brilliant.. upgrade went smoothly from 2.6.30.2 to 2.6.31

thanks!
Logged

calamari
Newbie
*

Karma: 0
Posts: 23


View Profile
« Reply #28 on: September 19, 2009, 03:45:02 AM »

Boots fine.  Seems robust.  dm_crypt still broken.

Strange that dm_crypt still seems to be broken, as I did work for the release candidates: http://plugcomputer.org/plugforum/index.php?topic=425.msg4164#msg4164
Logged

rooster
Administrator
Sr. Member
*****

Karma: 8
Posts: 311


View Profile
« Reply #29 on: September 19, 2009, 09:13:02 AM »

I also updated my plug with 2.6.31 and got the following warning:
Quote
------------[ cut here ]------------
WARNING: at arch/arm/kernel/process.c:171 cpu_idle+0x80/0xc0()
Modules linked in: dm_crypt dm_mod snd_usb_audio snd_pcm snd_timer snd_page_alloc snd_usb_lib snd_rawmidi snd_seq_device snd_hwdep snd soundcore
[<c0031a78>] (unwind_backtrace+0x0/0xe0) from [<c00423f8>] (warn_slowpath_common+0x50/0x68)
[<c00423f8>] (warn_slowpath_common+0x50/0x68) from [<c002d8d0>] (cpu_idle+0x80/0xc0)
[<c002d8d0>] (cpu_idle+0x80/0xc0) from [<c00089ec>] (start_kernel+0x268/0x2c0)
[<c00089ec>] (start_kernel+0x268/0x2c0) from [<00008034>] (0x8034)
---[ end trace a3132aad8b495ecd ]---

I saw a thread related to 2.6.31_rc7 relating to this warning, has anyone else got this warning?
Logged

Pages: 1 [2] 3 4
Print
Jump to: