Problems using 2.4 kernels with colo

atopo

Hi,

I'm fine booting 2.6 Kernels. But when I try a 2.4 Kernel the boot process fails. This is what I get:

2> select "Which Kernel?" 50 vmlinux kernel-2.4.31
2> goto {menu-option}
2> var image-name kernel-2.4.31.gz
2> lcd "Loading Linux" {image-name}
2> load /{image-name}
000d6f52 880466t
2> lcd "Booting..."
2> execute root=/dev/hda3 ro console=ttyS0,115200
elf32: 00080000 - 0023f4cf (801c6040) (ffffffff.80000000)
elf32: 80080000 (80080000) 1667072t + 165072t

and then the system hangs.

Kernel is from the emerged mips-sources 2.4.31, compiled locally.

This is my Kernel-config:

Redhatter · Posted: Mon Oct 10, 2005 12:55 pm Post subject:

Is there a reason why you're using kernel 2.4? The 2.4.31 image was primarily for R4600 Indy's, which, until recently, did not run Linux 2.6 reliably. This has now been fixed in upstream CVS, and so the 2.4 ebuilds will probably disappear in the next month or so.

When emerging the sources, did it apply any Cobalt patches? Also, I don't see any serial support enabled...
_________________
Stuart Longland (a.k.a Redhatter, VK4MSL)
I haven't lost my mind - it's backed up on a tape somewhere...

Gentoo/MIPS Cobalt developer, Mozilla herd member.

atopo · Posted: Mon Oct 10, 2005 1:42 pm Post subject:

Yes, there is a reason: I have an encrypted partition that I've used with a debian 3.0, and a custom kernel with the kerneli patches. The way passphrases are hashed have been changed between 2.4 and 2.6 kernels (AFAIK), and the method described using hashalot fails for some reason.

I don't mid trying an quite old kernel just to see if I can still access the data there

br
Alexander

Redhatter · Posted: Tue Oct 11, 2005 12:44 am Post subject:

Okay, there are a couple of options...

How did you go about encrypting the partition? Perhaps there's a way to get Linux 2.6 to be backward compatable?

The other alternative, is to perhaps fetch new kernel sources, patch by hand, then try to build a kernel from that.

I have some snapshots of Linux/MIPS CVS. (Go easy though, that box is on my ADSL link) From there, you should be able to patch the kernel with the Cobalt patch set.

Then apply any patches you need for encrypted filesystems. I'd suggest once you gain access to the encrypted partition, you back it up and upgrade the format of the partition, so that you can access it from Kernel 2.6 -- as support for kernel 2.4 has been discontinued upstream, and will discontinue here.
_________________
Stuart Longland (a.k.a Redhatter, VK4MSL)
I haven't lost my mind - it's backed up on a tape somewhere...

Gentoo/MIPS Cobalt developer, Mozilla herd member.