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

Karma: 38
Posts: 497


View Profile
« on: September 15, 2009, 05:45:06 PM »

2.6.31 is now available.

CONFIG_USB_SUSPEND has been enabled.  Please report any issues.

Kernel and modules are available from the following locations:

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

IPV6: http://sheeva6.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.
Logged

restamp
Global Moderator
Sr. Member
*****

Karma: 4
Posts: 273


View Profile
« Reply #1 on: September 15, 2009, 08:32:41 PM »

Boots fine.  Seems robust.  dm_crypt still broken.   Also, I notice about a second's delay when I access my USB HD initially and after some period of inactivity (perhaps 5 mins).  I think this is likely due to the USB_SUSPEND.  Is there any way to turn this option off if we don't want it?
Logged

cbxbiker61
Global Moderator
Sr. Member
*****

Karma: 38
Posts: 497


View Profile
« Reply #2 on: September 15, 2009, 09:19:04 PM »

You should be able to disable autosuspend by appending usbcore.autosuspend=-1 to the kernel boot options.

Alternatively you should be able to disable autosuspend on a device by device basis by finding the appropriate autosuspend file under /sys.

find /sys -name autosuspend
echo "-1" > /sys/path_to_autosuspend_file

Documentation is in kernel source Documentation/kernel-parameters.txt.
Logged

Rabeeh Khoury
Administrator
Full Member
*****

Karma: 5
Posts: 218


View Profile
« Reply #3 on: September 15, 2009, 10:44:39 PM »

If auto sespend is problematic; i would disable it by default.

cbxbiker - can you please look at this -
http://plugcomputer.org/plugforum/index.php?topic=727.msg4494#msg4494

can you please enable SCSI multi lun scan for next builds?

Thanks.
Logged

DamonHD
Full Member
***

Karma: 4
Posts: 169


View Profile WWW
« Reply #4 on: September 15, 2009, 11:57:09 PM »

Whoops, missed this, looks great, thanks!

Still not clear how I'm meant to apply it to a V1.0 install?  --rootkernel or not or something different?

Rgds

Damon
Logged

cbxbiker61
Global Moderator
Sr. Member
*****

Karma: 38
Posts: 497


View Profile
« Reply #5 on: September 16, 2009, 12:13:07 AM »

SCSI Multi-lun is now supported (also true of the 2.6.30.7 kernel).
Logged

cbxbiker61
Global Moderator
Sr. Member
*****

Karma: 38
Posts: 497


View Profile
« Reply #6 on: September 16, 2009, 12:20:27 AM »

Whoops, missed this, looks great, thanks!

Still not clear how I'm meant to apply it to a V1.0 install?  --rootkernel or not or something different?

Rgds

Damon

I haven't used the V1.0 installer.  My script is writing the kernel to /boot when you use --rootkernel.  If the V1.0 installer is doing something else, someone please let me know.
Logged

DamonHD
Full Member
***

Karma: 4
Posts: 169


View Profile WWW
« Reply #7 on: September 16, 2009, 01:16:20 AM »

I'll give it a whirl with --rootkernel and tell you what happens!

Rgds

Damon
Logged

DamonHD
Full Member
***

Karma: 4
Posts: 169


View Profile WWW
« Reply #8 on: September 16, 2009, 01:48:38 AM »

No, still comes up a 2.6.30.2 reported by uname, and the new options don't appear in the /proc/config.gz:

ubuntu:/proc> uname -a
Linux ubuntu 2.6.30.2 #11 PREEMPT Wed Jul 22 19:53:31 MDT 2009 armv5tel GNU/Linux
ubuntu:/proc> gzip -d < /proc/config.gz | egrep CONFIG_USB_SUSPEND
ubuntu:/proc>

So, I'm obviously too stupid to be allowed loose on combination of the V1.0 installer and your README!

Rgds

Damon


Logged

cbxbiker61
Global Moderator
Sr. Member
*****

Karma: 38
Posts: 497


View Profile
« Reply #9 on: September 16, 2009, 02:34:03 AM »

DamonHD: post the output of the following.

cat /proc/partitions
mount
find / -name uImage
Logged

DamonHD
Full Member
***

Karma: 4
Posts: 169


View Profile WWW
« Reply #10 on: September 16, 2009, 02:42:52 AM »

Hi,

Your wish is my command:

major minor  #blocks  name

  31        0       4096 mtdblock0
  31        1     519168 mtdblock1
 179        0    8003584 mmcblk0
 179        1    1004031 mmcblk0p1
 179        2    6996307 mmcblk0p2

(note that I have two big non-boot DC partitions on an 8G SD card)

tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
varrun on /var/run type tmpfs (rw,nosuid,mode=0755)
varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
rootfs on / type rootfs (rw)
/dev/mmcblk0p1 on /usr2 type ext3 (ro,noatime,commit=30,data=ordered)
/dev/mmcblk0p2 on /local type ext3 (rw,noatime,commit=600,data=ordered)

and:

/boot/uImage

Note that a full listing of /boot gives:

drwxr-xr-x  2 root root     456 Sep 16 08:31 .
drwxr-xr-x 23 root root    1568 Sep 16 07:04 ..
-rwxr-xr-x  1 root root 2620504 Sep 12 12:53 2.6.30.2-uImage
-rwxr-xr-x  1 root root 2626588 Sep 12 13:31 sheeva-2.6.30.6-uImage
-rw-r--r--  2 root root 2766512 Sep 16 08:23 sheeva-2.6.31-uImage
-rw-r--r--  2 root root 2766512 Sep 16 08:23 uImage

so I hard-linked your new uImage in place...

Rgds

Damon
« Last Edit: September 16, 2009, 11:31:25 AM by DamonHD » Logged

SgtPepper
Newbie
*

Karma: 2
Posts: 19


View Profile
« Reply #11 on: September 16, 2009, 11:21:49 AM »

If anyone is interested, I compiled a btrfs-tools 0.19-3 package to take advantage of the BTRFS improvements in 2.6.31.  You can download it here (my plug) for now.  I can't guarantee I'll keep it up forever and my internet connection sucks, so if someone would be willing to host it elsewhere, I wouldn't argue  Smiley

Then again, for all I know, I may be the only person using BTRFS on the sheevaplug.
« Last Edit: September 16, 2009, 11:33:03 AM by SgtPepper » Logged

cbxbiker61
Global Moderator
Sr. Member
*****

Karma: 38
Posts: 497


View Profile
« Reply #12 on: September 16, 2009, 12:10:25 PM »

DamonHD:  If you are using NAND to boot (which I believe you are from a different thread), then you don't use "--rootkernel".  Without "--rootkernel" the README* flashes the kernel to NAND.
Logged

restamp
Global Moderator
Sr. Member
*****

Karma: 4
Posts: 273


View Profile
« Reply #13 on: September 16, 2009, 12:48:19 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.)
Logged

DamonHD
Full Member
***

Karma: 4
Posts: 169


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

Hi cbxbiker61,

Thank you again.

I am indeed booting from NAND.

The reason I thought that I had to use --rootkernel is (my ignorance writ large again) is I note that the V1.0 install is using UBIFS and I wasn't sure if your flashing command would attempt to revert to jffs2, getting me in a tangle (and blowing away the speed and other UBIFS advantages).

What would happen?  Will I revert to UBIFS and have to change my bootparams?  What is happening with those uImage files that I've been dutifully copying into boot? And is there honey still for tea?  B^>

Rgds

Damon
Logged

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