building process of netboot2 success (dropbeard... -similar to template-) but ramdisk stop on PXE boot. Error was similar to: Failed to execute /init /linuxrc. Attempting defaults... Kernel panic_ not syncing: No init found. Try parsing init= option to kernel I have tried a lot of configurations sending kernel options for boot but unsuccessfully (I tried changing kernel, linuxrc/init and only worked changing ramdisk) Reproducible: Always Steps to Reproduce: 1.make netboot2 kernel+ramdisk similar to template on x86 2.try PXE boot (quick with knoppix terminal server) 3. Actual Results: Failed to execute /init /linuxrc. Attempting defaults... Kernel panic_ not syncing: No init found. Try parsing init= option to kernel Expected Results: Perhaps error finding root filesystem or shell requesting something 1) linuxrc script don't have information related to x86 arch, only sparc, mips and ppc 2) Why I wasn't able to find squash or similar image for PXE booting? Is netboot thought only for nfs boot? Thanks. Feel free for request test/files
I'd be very surprised if the template worked at all. The netboot2 target is still "experimental". At this point, I'm (for the most part) the only user and the only developer for it. However, I have built completely functional netbootable (via pxelinux) kernel/initramfs images for x86 using the netboot2 target. I built one just a few months ago. Most likely, you're missing some necessary libs for busybox to function. The file names in the template are out of date. However, that's not a problem with catalyst. It's up to you to figure out which files you need and list them properly.
(In reply to comment #1) > I'd be very surprised if the template worked at all. The netboot2 target is > still "experimental". At this point, I'm (for the most part) the only user and > the only developer for it. I'm using it too 1 year ago my friend! > However, I have built completely functional netbootable (via pxelinux) > kernel/initramfs images for x86 using the netboot2 target. I built one just a > few months ago. > > Most likely, you're missing some necessary libs for busybox to function. The > file names in the template are out of date. However, that's not a problem with > catalyst. It's up to you to figure out which files you need and list them > properly. 1) Look at the error found, firstly there is a problem with ramdisk "only" because it is not loaded in memory (I changed linuxrc script with no success with same ramdisk)So there is a problem in how catalyst biult it (I think) 2) I saw outdated messages for files missing, but files which names was correct I wasn't able to found it into ramdisk and I wasn'a able to find it anywhere! In short, I think there is a problem in how catalyst built ramdisk Thanks for so fast reply and for your great work (and sorry for my english) Feel free for request test to me if you need it
This isn't a problem with catalyst. You'll get that error if you're missing libs required by busybox or some other utility. The example netboot2 spec installed with catalyst will not work as-is, since many of the filenames have changed with updated versions.
