• Home
  • Help
  • Search
  • Login
  • Register
Pages: [1] 2
Author Topic: 2.6.30-rc2 and 2.6.30-rc3 new releases  (Read 11025 times)
cbxbiker61
Global Moderator
Sr. Member
*****

Karma: 38
Posts: 497


View Profile
« on: April 22, 2009, 10:33:39 PM »

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), usb-serial, uvcvideo.

my usb-serial  driver has been patched to allow full-speed downloads using high-speed wireless modems, (EVDO for example) as per this thread. http://www.evdoforums.com/thread4381.html Anyone interested in testing out EVDO modems with SheevaPlug?

uvcvideo is not supported in the 2.6.22.19 kernel.
Logged

mavr15
Newbie
*

Karma: 0
Posts: 8


View Profile
« Reply #1 on: April 23, 2009, 12:05:29 PM »

Can you put on site .config for this kernels. I downloaded 2.6.30-rc3, and need compile some modules. Thanks.
Logged

cbxbiker61
Global Moderator
Sr. Member
*****

Karma: 38
Posts: 497


View Profile
« Reply #2 on: April 23, 2009, 03:06:29 PM »

Yes.  The configs are now online.  BTW, I also created a patches subdirectory for patches that are applied.

Which modules are you needing?  If they're generally useful, I'd be happy to add them to the default build.
Logged

pauldy
Newbie
*

Karma: 0
Posts: 17


View Profile
« Reply #3 on: April 23, 2009, 06:44:48 PM »

Downloaded the 2.6.30-rc3 image ran the readme now all I see via the serial console is.

Code:
Marvell>> boot

NAND read: device 0 offset 0x100000, size 0x400000

Reading data from 0x4ff800 -- 100% complete.
 4194304 bytes read: OK
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.30-rc3
   Created:      2009-04-23  11:41:15 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2174060 Bytes =  2.1 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Not sure what is missing but I was just running a default install, the only change I made was to move /var to an SD card because of mysql database.

Logged

mavr15
Newbie
*

Karma: 0
Posts: 8


View Profile
« Reply #4 on: April 23, 2009, 08:12:08 PM »

I need tun.ko modulles. I want to connect to openvpn server, and don't have /dev/net/tun devices.
Logged

kilowatt
Global Moderator
Full Member
*****

Karma: 3
Posts: 106


View Profile
« Reply #5 on: April 23, 2009, 08:20:40 PM »

Quote
Not sure what is missing but I was just running a default install
Did you set the two  variables you need in uBoot?

setenv mainlineLinux yes
setenv arcNumber 2097

These are needed to run 2.6.30 but if you need to run the old kernel you need to remember to:
setenv mainlineLinux no
« Last Edit: April 23, 2009, 08:22:37 PM by kilowatt » Logged

pauldy
Newbie
*

Karma: 0
Posts: 17


View Profile
« Reply #6 on: April 23, 2009, 09:03:15 PM »

Yup I ran the following on the reboot:
Quote
setenv mainlineLinux yes
setenv arcNumber 2097
setenv bootargs rootfstype=jffs2 console=ttyS0,115200 mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/mtdblock1 rw ip=192.168.200.242:255.255.255.0:DB88FXX81:eth0:none
saveenv
boot

Maybe a bad flash?  I didn't see any errors when I ran it.
Logged

cbxbiker61
Global Moderator
Sr. Member
*****

Karma: 38
Posts: 497


View Profile
« Reply #7 on: April 23, 2009, 11:57:51 PM »

The first time I rebooted after flashing.  I had a similar response.  In my case A hard reset fixed the problem and It's been working fine ever since.  The most interesting problem I had was the kernel not being able to identify what the root filesystem type was.  That's where the "rootfstype=jffs2" came in.

I'd suggest using tftp to boot the kernel if you're still having problems and then do a  reflash.
Logged

cbxbiker61
Global Moderator
Sr. Member
*****

Karma: 38
Posts: 497


View Profile
« Reply #8 on: April 24, 2009, 12:28:53 AM »

I just added the tun driver to 2.6.30-rc2 and 2.6.30-rc3.  It was already in 2.6.22.19.
Logged

kim.toms
Newbie
*

Karma: 0
Posts: 3


View Profile
« Reply #9 on: April 24, 2009, 07:18:40 AM »

The -rc3 still does not have the patch for SD cards (mmc).  Has this been submitted to the maintainers?
Logged

cbxbiker61
Global Moderator
Sr. Member
*****

Karma: 38
Posts: 497


View Profile
« Reply #10 on: April 24, 2009, 07:35:54 AM »

I'm pretty sure it's been submitted to the maintainers.  It might take a while to trickle up into the official kernel.  Hopefully the fix will be in the official .30 kernel.
Logged

mavr15
Newbie
*

Karma: 0
Posts: 8


View Profile
« Reply #11 on: April 24, 2009, 08:11:20 AM »

Thanks, I am install modules for 2.6.30-rc3 kernel and have some troubles with tun device. Can't start tun device, unknown symbol....
I rollback to 2.6.22.19 kernel, and all work perfect. In console i see load tun modules and start vpn.
Logged

cbxbiker61
Global Moderator
Sr. Member
*****

Karma: 38
Posts: 497


View Profile
« Reply #12 on: April 24, 2009, 08:26:02 AM »

mavr15, Were you getting "unknown symbol" when you modprobed tun?  I actually tested tun on my system and it loaded fine when I modprobed tun.  I wonder if you were using the previous version of the kernel that was build without tun with the new Modules.  That could cause a potential "unknown symbol".

In any case the 2.6.22.19 kernel should work just fine.
Logged

mavr15
Newbie
*

Karma: 0
Posts: 8


View Profile
« Reply #13 on: April 24, 2009, 09:43:31 AM »

Yes , I am use old previous build, without tun modules, and modules from new build. when i do modprobe i have errors. But usually i can make modules for hardware and use then withou recompile kernel.
Logged

cbxbiker61
Global Moderator
Sr. Member
*****

Karma: 38
Posts: 497


View Profile
« Reply #14 on: April 24, 2009, 07:00:47 PM »

mavr15, In a lot of cases you can get away with using a previous kernel with new modules, but there are cases where it just won't work.  Apparently this is one of those cases.  When you enable a new module it "may" enable features (export symbols) that weren't exported before the module was enabled.  The most prudent approach is to flash the matching kernel if the modules have been changed/updated.
Logged

Pages: [1] 2
Print
Jump to: