UEFI

[Factionite]

I'm trying to boot linux in uefi to a ramfs with the tmpfs flag set in the kernel config it seems(it seems tmpfs is being forced). This is in a CPIO format that iPxe is able to recognize when it's in BIOS. However when i change the VM to boot in UEFI it consistently fails at

A few lines above all of this it also says RAMDISK: incomplete write (20526 != 32768)
devtmpfs: error mounting -2
write error
VFS Mounted root (ramfs filesystem) on device 0:14
.
.
.
Failed to execute <init>. (or whatever I put after init=____; which i've tried 3 and various other directories)
Attempting defaults...
kernel panic - not syncing: no init found. try passing init= option to kernel.
Pid: 1, comm: swapper/o not tainted 3.5.0



The configuration is set to:
kernel http://$nextserver/vmlinuz-3.5.0 init=/sbin/init rootfstype=ramfs
initrd http://$nextserver/initramfs-2.6.32.x86_64.img
boot

It seems to me that its recognizing that its a gzip but not that its in cpio. If anyone has run into this I would greatly appreciate some tips. I'm not sure if this is a problem with iPXE or if its something with my linux setup, however since it works in BIOS and not UEFI I'm starting with iPXE because of everything else that I've herd.
Note: I do have the efi stub enabled, as I've herd it was necassary elsewhere.

[robinsmidsrod]

This code (initrd+name) should make the ramdisk loadable under UEFI.

Code:

kernel http://$nextserver/vmlinuz-3.5.0 initrd=initramfs
initrd --name initramfs http://$nextserver/initramfs-2.6.32.x86_64.img

[Factionite]

Its still failing with all of the same information.

[mcb30]

(2015-06-25 16:39)Factionite Wrote:  Its still failing with all of the same information.

I think you're hitting a known bug in pre-3.16 kernels. Try upgrading to a newer kernel.

Michael

[Factionite]

(2015-06-25 17:24)mcb30 Wrote:  

(2015-06-25 16:39)Factionite Wrote:  Its still failing with all of the same information.

I think you're hitting a known bug in pre-3.16 kernels. Try upgrading to a newer kernel.

Michael

Well I'm using the 3.5.0 kernel which I thought was a safe bet. However, I'm still using a previous image.