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

Karma: 38
Posts: 497


View Profile
« on: May 16, 2009, 01:22:08 AM »

Release candidate 6 is now available.

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.
Logged

jaebird
Newbie
*

Karma: 0
Posts: 7


View Profile
« Reply #1 on: May 17, 2009, 04:11:13 PM »

Just installed the rc6 kernel and got this error, is this something i should just delete with the new kernel?

fat: version magic '2.6.22.18 mod_unload ARMv5 ' should be '2.6.30-rc6 preempt mod_unload ARMv5 '
insmod: error inserting '/boot/fat.ko': -1 Invalid module format

EDIT: Nevermind, I forgot to change the /etc/rc.local file after latest ubuntu blast!

Thanks,
Jae
« Last Edit: May 17, 2009, 04:43:20 PM by jaebird » Logged

CharlesWGreenJr
Newbie
*

Karma: 0
Posts: 28



View Profile
« Reply #2 on: May 17, 2009, 05:15:18 PM »

I happened to notice that error this weekend on an earlier kernel (RC4), but I haven't investigated it yet.

-Charles
Logged

jaebird
Newbie
*

Karma: 0
Posts: 7


View Profile
« Reply #3 on: May 17, 2009, 07:26:36 PM »

I'm having serious issues with an external hdd that is formatted ext3. The drive works fine with my desktop ubuntu box. If I try to create a dir:

end_request: I/O error, dev sda, sector 250871817
EXT3-fs error (device sda1): read_inode_bitmap: Cannot read inode bitmap - block_group = 957, inode_bitmap = 31358977
EXT3-fs error (device sda1) in ext3_new_inode: IO failure
Aborting journal on device sda1.
journal commit I/O error

I ended up wiping the drive cause i thought something else was wrong. What are we to do with this  Grin

Anyone else?

Jae

EDIT2: I think I may have figured out the problem. This particular USB to IDE device is 14cd:6600 Super Top USB 2.0 IDE DEVICE. There was a bug in the kernel prior to 2.6.20 (https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.17/+bug/81059). So it is fixed in my x86 version of Ubuntu, but perhaps the fix never made it into the ARM port? I verified the error occurs with the stock SheevaPlug kernel 2.6.28, so it is not related to this kernel.
« Last Edit: May 19, 2009, 05:28:31 AM by jaebird » Logged

rooster
Guest
« Reply #4 on: May 19, 2009, 12:03:37 AM »

Hi cbxbiker61,

Can you please add reiserfs.ko?

Thanks  Smiley
Logged

cbxbiker61
Global Moderator
Sr. Member
*****

Karma: 38
Posts: 497


View Profile
« Reply #5 on: May 20, 2009, 05:09:32 AM »

reiserfs.ko has been added.
Logged

plugit
Global Moderator
Full Member
*****

Karma: 0
Posts: 139



View Profile
« Reply #6 on: May 21, 2009, 07:50:15 AM »

Another flawless upgrade on my SheevaPlug. Thanks, cbxbiker61!
Logged

dumper
Newbie
*

Karma: 0
Posts: 19


View Profile
« Reply #7 on: May 21, 2009, 03:55:33 PM »

Hi, i'm newbee

looks great, the kernel from Marvell doesnt support NFS & usb-automount (when i plug a usb stick or USB-HD , always need to mount it manually)
my Questions:
1. does the new kernel support automount ? since i want to use the plug as a Fileserver with attached USB-HDs (which are on only when needed , so it should me automatically mouted in /media, samba & nfs need only share on /media)
2. can you add support for hfs/hfsplus ?

thanx alot
Logged

cbxbiker61
Global Moderator
Sr. Member
*****

Karma: 38
Posts: 497


View Profile
« Reply #8 on: May 21, 2009, 06:01:23 PM »

autofs, autofs4, hfs and hfsplus modules have been added.

I'm not sure autofs will help with respect to automounting usb drives.  Personally I'm not too keen on automounting USB drives on a headless computer.  I'd be more inclined to write a couple of scripts.  Although I find "prompted" automounting to be acceptable on workstations running KDE4.
Logged

pauldy
Newbie
*

Karma: 0
Posts: 17


View Profile
« Reply #9 on: May 21, 2009, 08:17:35 PM »

I've noticed something and wondered if you might have seen it to, anytime I run a mono app under this kernel series is segfaults immediately.   Seems to have something to do with /proc/self/maps going to hit up someone on that team as well just thought I would get it out here too.
Logged

dumper
Newbie
*

Karma: 0
Posts: 19


View Profile
« Reply #10 on: May 22, 2009, 01:29:31 PM »

works great, NFS & hfsplus  works, automount still doesnt work. which solution would u suggest as a NAS with usb-hds /automount when connected?
thanx
Logged

rooster
Guest
« Reply #11 on: May 22, 2009, 09:38:43 PM »

udev scripts that detect USB "add/remove" events and perform the mount/umount commands, I am not aware of another way to do it.
Logged

bogolisk
Newbie
*

Karma: 0
Posts: 6


View Profile
« Reply #12 on: May 23, 2009, 08:04:25 AM »

udev scripts that detect USB "add/remove" events and perform the mount/umount commands, I am not aware of another way to do it.

Yeah, I've done that and it works quite well. Much more lightweight than installing the whole gang of hal+dbus+......

Logged

dumper
Newbie
*

Karma: 0
Posts: 19


View Profile
« Reply #13 on: May 23, 2009, 10:57:53 AM »

i tried it too, works, the only prob. is that i couldnt get the HD-Volumes Label, have to mount it like sda1, sda2..  or usb1, usb2...
any suggestion ?
Logged

bogolisk
Newbie
*

Karma: 0
Posts: 6


View Profile
« Reply #14 on: May 23, 2009, 02:31:07 PM »

i tried it too, works, the only prob. is that i couldnt get the HD-Volumes Label, have to mount it like sda1, sda2..  or usb1, usb2...
any suggestion ?

caveat utilitor: likely buggy scripts (work for me, ymmv)


/etc/udev/rules.d/99-partition.rule
Code:
SUBSYSTEM=="block", ACTION=="add", ATTR{partition}=="1", RUN+="/usr/local/sbin/add_partition.sh", ENV{REMOVE_CMD}:="/usr/local/sbin/remove_partition.sh"

/usr/local/sbin/add_partition.sh
Code:
#!/bin/bash

MGID=1001
MUID=1001

if [ -n ${ID_FS_TYPE} -a -z ${ID_FS_LABEL} ]; then
    i=1
    mountpoint=/media/${ID_FS_TYPE}_${ID_TYPE}_${i}
    while [ -d ${mountpoint} ]; do
i=$((i+1))
mountpoint=/media/${ID_FS_TYPE}_${ID_TYPE}_${i}
    done
else
    mountpoint=/media/${ID_FS_LABEL}
fi

case ${ID_FS_TYPE} in
    vfat)
options="rw,noatime,nosuid,nodev,uid=${MUID},gid=${MGID},fmask=0077,dmask=0077,iocharset=iso8859-1,utf8,flush"
;;
    ext3)
options="rw,noatime,nosuid,nodev,errors=remount-ro,data=ordered"
;;
    ext2)
options="rw,noatime,nosuid,nodev,errors=remount-ro"
;;
    *)
echo "fixme" | logger
exit
;;
esac

mkdir -p ${mountpoint}
mount -t ${ID_FS_TYPE} -o ${options} ${DEVNAME} ${mountpoint}


/usr/local/sbin/remove_partition.sh
Code:
#!/bin/sh

mountpoint=`sed -nre "s=^${DEVNAME} ([^ ]+) ${ID_FS_TYPE}.+$=\1=p" < /proc/mounts`

umount -f ${DEVNAME}

# should check if it was really under /media
if [ -d ${mountpoint} ]; then
    rmdir ${mountpoint}
fi
Logged

Pages: [1] 2
Print
Jump to: