Tiny Core Base > TCB Q&A Forum

Kernel modules in multiple initrd files

<< < (2/2)

hiro:
i have been googling for a long time and i barely see this referenced anywhere, had to figure it out by trial&error in the end.
it's also not clear where the docs should be, in my case i suppose this is an ipxe feature, so the syntax is slightly different, but i'm not even sure about that :D

in any way here's what i figured out. with modern tc you can boot with pxe even when using the separate modules and rootfs for initrd.
this worked for me from the ipxe console:


--- Code: ---
kernel http://tinycorelinux.net/13.x/x86_64/release/distribution_files/vmlinuz64 loglevel=3 initrd=modules64.gz initrd=rootfs64.gz
module http://tinycorelinux.net/13.x/x86_64/release/distribution_files/modules64.gz
initrd http://tinycorelinux.net/13.x/x86_64/release/distribution_files/rootfs64.gz
boot

--- End code ---

somehow this thread is the only thing that mentions tinycorelinux and that "initrd=" option.
it's needed, somehow without this, the kernel doesn't know where root comes from. (errors like "VFS: Cannot open root device "(null)" or unknown-block"...).

initrd=file1,file2 doesn't work in this case, instead you just have to supply initrd= twice.

if anybody knows how this can be documented in a central place, that would be very nice for new users now that i found out how :)
i was expecting to find information about how modules64.gz and rootfs64.gz goes together (and are the same as corepure64.gz alone) on the main site, as that's important enough.

horrible modern EFI based system, and this problem kept me from enjoying TC for a while now. maybe this means i can afford some more time with tc again.

gadget42:
it would be good to modify parts of the above post so that...if used by the greater interwebz...it wouldn't cause some 'serious'(?) server abuse...sigh...

hiro:
I'm happy if even one person finds value in this. It's not abuse as the files are very small (smaller than the full iso).

I don't understand your definition of server abuse,.

I also noticed that this *was* documented somewhere else, too. Not in the docs, but by example:
http://boot.ipxe.org/tinycore.ipxe

Curiously they even picked our distro as the example! :D

I also found out more details about this issue. The OP in this thread was using the syslinux syntax to supply multiple initrd (just separated by commas). in ipxe this doesn't work and you have to adjust like shown above with multiple initrd= strings on the kernel line.

it's a common feature for multiboot-compatible bootloaders, even if syntax has to be adjusted every time slightly.

andyj:
The syslinux multiple initrd syntax does work in pxelinux though.

hiro:
indeed.
syslinux: initrd=1,2,3
grub: initrd 1 2 3
ipxe: initrd=1 initrd=2 initrd=3

Navigation

[0] Message Index

[*] Previous page