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

Karma: 38
Posts: 497


View Profile
« Reply #15 on: March 02, 2010, 12:39:35 PM »

I finally updated 2.6.32.9 to initialize sata support.  This is release 3 of 2.6.32.9.

Maybe someone can test it if they get a chance.
Logged

portnawak
Newbie
*

Karma: 0
Posts: 16


View Profile
« Reply #16 on: March 02, 2010, 01:28:26 PM »

I finally updated 2.6.32.9 to initialize sata support.  This is release 3 of 2.6.32.9.

Great, thanks a lot.

My 4.5TB raid5 is currently resyncing so I probably won't be able to reboot the sheeva during the next 2 days, but no doubt I'll test it as soon as I can.
Logged

cbxbiker61
Global Moderator
Sr. Member
*****

Karma: 38
Posts: 497


View Profile
« Reply #17 on: March 02, 2010, 01:48:37 PM »

I finally updated 2.6.32.9 to initialize sata support.  This is release 3 of 2.6.32.9.

Great, thanks a lot.

My 4.5TB raid5 is currently resyncing so I probably won't be able to reboot the sheeva during the next 2 days, but no doubt I'll test it as soon as I can.

Unfortunately I'm not sure I'm going to be able to keep the sata patch in the kernel.  It seems that with the patch in place the kernel locks up at "sata_mv sata_mv.0: version 1.28" when on a standard unmodified plug.  It would be nice if sata_nv would timeout nicely on a plug without sata support.  Anyone have suggestions on how to accomplish this?
Logged

pingtoo
Sr. Member
****

Karma: 15
Posts: 318


View Profile
« Reply #18 on: March 02, 2010, 02:05:08 PM »

I finally updated 2.6.32.9 to initialize sata support.  This is release 3 of 2.6.32.9.

Great, thanks a lot.

My 4.5TB raid5 is currently resyncing so I probably won't be able to reboot the sheeva during the next 2 days, but no doubt I'll test it as soon as I can.

Unfortunately I'm not sure I'm going to be able to keep the sata patch in the kernel.  It seems that with the patch in place the kernel locks up at "sata_mv sata_mv.0: version 1.28" when on a standard unmodified plug.  It would be nice if sata_nv would timeout nicely on a plug without sata support.  Anyone have suggestions on how to accomplish this?
How about make it a modules and let udev handle the device? if some one want to root it then they have to use initrd/initramfs.
Logged

Good Luck Smiley

cbxbiker61
Global Moderator
Sr. Member
*****

Karma: 38
Posts: 497


View Profile
« Reply #19 on: March 02, 2010, 02:08:04 PM »

I finally updated 2.6.32.9 to initialize sata support.  This is release 3 of 2.6.32.9.

Maybe someone can test it if they get a chance.

I've decided to revert 2.6.32.9 from release 3 to release 2 until we can figure out an appropriate way to get "sata_mv" not to fail on a standard plug.

I have a version of 2.6.33 on the site that has the sata patch applied, although I'm not going to officially release it until the "sata_mv" issue is resolved.

I guess I'll put a bunch of printk's in sata_mv until I figure out where the hang is occurring.
Logged

cbxbiker61
Global Moderator
Sr. Member
*****

Karma: 38
Posts: 497


View Profile
« Reply #20 on: March 02, 2010, 02:12:16 PM »

How about make it a modules and let udev handle the device? if some one want to root it then they have to use initrd/initramfs.
[/quote]

That's not a bad idea.  I think I'll play with printk a bit before committing to a decision.  I'm not totally against an initrd, although I'd like to avoid it if I can.
Logged

portnawak
Newbie
*

Karma: 0
Posts: 16


View Profile
« Reply #21 on: March 02, 2010, 02:40:51 PM »

It seems that with the patch in place the kernel locks up at "sata_mv sata_mv.0: version 1.28" when on a standard unmodified plug.  It would be nice if sata_nv would timeout nicely on a plug without sata support.  Anyone have suggestions on how to accomplish this?

If I remember well, the first time I tried the kernel I cross-compiled here, I had the same error until I upgrade u-boot to a version with eSata support (found somewhere here in the forums, have it on disk but don't remember the URL of the post). May be this is something to test on a Sheeva without the esata port ?
Logged

Abra
Newbie
*

Karma: 1
Posts: 29


View Profile
« Reply #22 on: March 02, 2010, 04:40:39 PM »

same here: http://plugcomputer.org/plugforum/index.php?topic=1408.msg8678#msg8678, definitely seems to be uboot-related... I'm confused
Logged

darkscout
Newbie
*

Karma: 0
Posts: 26


View Profile
« Reply #23 on: March 02, 2010, 11:41:41 PM »

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

I still get this when trying to run the server:

Code:
/etc/init.d/nfs-kernel-server start
Not starting NFS kernel daemon: no support in current kernel. ... (warning).

Bug in my init script, see http://plugcomputer.org/plugforum/index.php?topic=1412.0
« Last Edit: March 03, 2010, 11:12:09 AM by darkscout » Logged

hideoushog
Newbie
*

Karma: 0
Posts: 23


View Profile
« Reply #24 on: March 03, 2010, 04:38:03 AM »

Thanks for the advice regarding "su" failure. The problem is now resolved. Should have RTFM  Embarrassed though if I had FTFM it would have saved some time.

echo 32768 > /proc/sys/vm/mmap_min_addr

This also enables user login by SSH and subsequent su to any user.  Smiley  Thankyou for your assistance.
Logged

Pages: 1 [2]
Print
Jump to: