General TC > General TC Talk

[Solved]: how to boot alternate kernel of same architecture

<< < (2/4) > >>

GNUser:
Maybe the imported kernel needs something from the other system's (Devuan's) initrd? I will explore this.

Another, albeit unlikely, possibility is that there is a compatibility issue between imported kernel and TCL13.1's glibc. But I don't think this is the issue because Devuan Chimaera's glibc (version 2.31) is older than TCL13.1's glibc (version 2.34). New glibc versions generally work just fine with binaries compiled using older glibc versions (a fortunate fact which TCL's repo takes full advantage of).

Rich:
Hi GNUser
I would think the kernel might want the the matching libraries from its /lib (or is that /lib64) directory.
Does Devuan use systemd? I wonder if maybe it's waiting for a missing systemd to do something.

mocore:
> Does Devuan use systemd?

 its a devian fork *apparently*  created to avoid that init system ! ( hard deps ect )

> I wonder if maybe it's waiting for a missing systemd to do something.

id guess turning kernel debugging "up to 11" might help lessen speculation  ?

GNUser:
Hi, Rich and mocore.

Devuan does not use systemd. It supports a handful of init systems. I use the default, which is SysVinit. (BTW I only keep the Devuan partition around for this kind of inter-distro exploration. TCL does everything I need, extremely well and with elegance.)

I unpacked and explored Devuan's initrd. It turned out to contain a lot more than I expected--not just kernel modules and firmware, but even its own set of shared libraries and executables...which are only around for first part of Devuan's boot process, until the root filesystem is mounted and a whole different set of kernel modules etc. become available.

So it seems that I'm dealing with 3 sets of files: Those in Devuan initrd, those in Devuan root filesystem, and those in TCL (ingeniously, TCL never leaves the initrd stage). Figuring out how to create a Frankenstein monster out of these three sets of files just to enable booting TCL with an imported kernel does not sound like my idea of fun.

Thanks for your support. It was still an interesting exercise and reinforced my love for TCL and its tendency to make things as least complicated as possible :)

curaga:
The only kernel version dependency is in glibc, it has a compile-time setting on which kernel version to require as a minimum. We usually set it to the previous version's kernel IIRC. So 5.10 should be new enough to boot TC 13.

There are a number of config options that may cause that. E.g. not having squashfs would mean extensions won't load. A hang at that point may be related to one of the config options that affect udev operation.

Navigation

[0] Message Index

[#] Next page

[*] Previous page