search for: config_efi_vars

...hat late. (I had some issues with my server's Ethernet NIC, and without it, no PXE / syslinux.) So, it's time to be a bit more specific. The kernel I want to boot in EFI mode is a debian installer. It *has* a module "efivars" loaded. Which means this kernel has been compiled with CONFIG_EFI_VARS, which itself depends on CONFIG_EFI. Therefore I should be able to boot this kernel in EFI mode. I don't remember whether I tried or not, so I'll re-test ASAP. However, as I discussed on IRC, the 'file' command only say "x86 boot sector". Celelibi

...;> Ethernet NIC, and without it, no PXE / syslinux.) >> >> So, it's time to be a bit more specific. >> The kernel I want to boot in EFI mode is a debian installer. It *has* >> a module "efivars" loaded. Which means this kernel has been compiled >> with CONFIG_EFI_VARS, which itself depends on CONFIG_EFI. Therefore I >> should be able to boot this kernel in EFI mode. >> >> I don't remember whether I tried or not, so I'll re-test ASAP. >> However, as I discussed on IRC, the 'file' command only say "x86 boot >> sec...

..."Loading vmlinuz... ok". I took a punt on something. From the docs, I thought that the kernel parameter CONFIG_EFI_STUB is not required. However, I set it: CONFIG_EFI_PARTITION=y CONFIG_EFI=y CONFIG_EFI_STUB=y CONFIG_EFI_MIXED=y CONFIG_FB_EFI=y CONFIG_DMI_SCAN_MACHINE_NON_EFI_FALLBACK=y CONFIG_EFI_VARS=m # CONFIG_EFIVAR_FS is not set CONFIG_EARLY_PRINTK_EFI=y For a generic x86-64 kernel, after the "Loading vmlinux... ok", I now get kernel logging to the screen. It has a kernel panic as cannot run init, but that is another problem. The same EFI config with a 32-bit kernel does NOT work...

> I have done another install to the usb stick. > > # syslinux --directory EFI/BOOT --install /dev/sdc1 > > ...this creates files ldlinux.c32 and ldlinux.sys in /EFI/BOOT > > I then mounted the 1st partition of the usb stick and copied > syslinux.efi and ldlinux.e64 from /usr/share/syslinux/efi64 to > /EFI/BOOT in the usb stick. > > I renamed syslinux.efi to

...I have the hanging after the "ok". Oh, I suppose for completeness, I should show the config of the kernel: CONFIG_EFI_PARTITION=y CONFIG_EFI=y # CONFIG_EFI_STUB is not set # CONFIG_FB_EFI is not set CONFIG_DMI_SCAN_MACHINE_NON_EFI_FALLBACK=y # EFI (Extensible Firmware Interface) Support CONFIG_EFI_VARS=m # CONFIG_EFIVAR_FS is not set # CONFIG_EARLY_PRINTK_EFI is not set ...hmm, is that last one the cause of the problem? When I do get this working, I shall write it up, step by step, as guide to others. Regards, Barry

...eness, I should show the config of the kernel: >> >> CONFIG_EFI_PARTITION=y >> CONFIG_EFI=y >> # CONFIG_EFI_STUB is not set >> # CONFIG_FB_EFI is not set >> CONFIG_DMI_SCAN_MACHINE_NON_EFI_FALLBACK=y >> # EFI (Extensible Firmware Interface) Support >> CONFIG_EFI_VARS=m >> # CONFIG_EFIVAR_FS is not set >> # CONFIG_EARLY_PRINTK_EFI is not set >> >> ...hmm, is that last one the cause of the problem? > > Regarding the configuration of the kernel, I am not sure / don't > know. I would suggest first finding out which specific arch...

...> Oh, I suppose for completeness, I should show the config of the kernel: > > CONFIG_EFI_PARTITION=y > CONFIG_EFI=y > # CONFIG_EFI_STUB is not set > # CONFIG_FB_EFI is not set > CONFIG_DMI_SCAN_MACHINE_NON_EFI_FALLBACK=y > # EFI (Extensible Firmware Interface) Support > CONFIG_EFI_VARS=m > # CONFIG_EFIVAR_FS is not set > # CONFIG_EARLY_PRINTK_EFI is not set > > ...hmm, is that last one the cause of the problem? Regarding the configuration of the kernel, I am not sure / don't know. I would suggest first finding out which specific architecture you are actually...

...with my server's > Ethernet NIC, and without it, no PXE / syslinux.) > > So, it's time to be a bit more specific. > The kernel I want to boot in EFI mode is a debian installer. It *has* > a module "efivars" loaded. Which means this kernel has been compiled > with CONFIG_EFI_VARS, which itself depends on CONFIG_EFI. Therefore I > should be able to boot this kernel in EFI mode. > > I don't remember whether I tried or not, so I'll re-test ASAP. > However, as I discussed on IRC, the 'file' command only say "x86 boot > sector". > Wel...

Hello, My question is quite straightforward, still I couldn't find an anwser on the interweb. Is it possible to boot the Linux kernels I used to boot in legacy mode, but now in EFI mode? I mean, I would like to keep all my PXE settings with my menus and kernels and stuff, but now boot them in PXE-EFI mode. I've been able to boot on syslinux.efi and keep my config files, but when I try

...s not set +CONFIG_IA64_MCA_RECOVERY=y +CONFIG_PERFMON=y +CONFIG_IA64_PALINFO=y +# CONFIG_IA64_MC_ERR_INJECT is not set +# CONFIG_IA64_ESI is not set +# CONFIG_IA64_HP_AML_NFW is not set +CONFIG_KEXEC=y +# CONFIG_CRASH_DUMP is not set + +# +# Firmware Drivers +# +# CONFIG_FIRMWARE_MEMMAP is not set +CONFIG_EFI_VARS=y +CONFIG_EFI_PCDP=y +CONFIG_DMIID=y +CONFIG_BINFMT_ELF=y +# CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is not set +# CONFIG_HAVE_AOUT is not set +CONFIG_BINFMT_MISC=m + +# +# Power management and ACPI options +# +CONFIG_PM=y +# CONFIG_PM_DEBUG is not set +CONFIG_PM_SLEEP=y +CONFIG_SUSPEND=y +CONFIG_SUSP...

...s not set +CONFIG_IA64_MCA_RECOVERY=y +CONFIG_PERFMON=y +CONFIG_IA64_PALINFO=y +# CONFIG_IA64_MC_ERR_INJECT is not set +# CONFIG_IA64_ESI is not set +# CONFIG_IA64_HP_AML_NFW is not set +CONFIG_KEXEC=y +# CONFIG_CRASH_DUMP is not set + +# +# Firmware Drivers +# +# CONFIG_FIRMWARE_MEMMAP is not set +CONFIG_EFI_VARS=y +CONFIG_EFI_PCDP=y +CONFIG_DMIID=y +CONFIG_BINFMT_ELF=y +# CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is not set +# CONFIG_HAVE_AOUT is not set +CONFIG_BINFMT_MISC=m + +# +# Power management and ACPI options +# +CONFIG_PM=y +# CONFIG_PM_DEBUG is not set +CONFIG_PM_SLEEP=y +CONFIG_SUSPEND=y +CONFIG_SUSP...

...-CONFIG_X86_MCE_NONFATAL=m -CONFIG_X86_MCE_P4THERMAL=y CONFIG_VM86=y CONFIG_TOSHIBA=m CONFIG_I8K=m @@ -163,37 +156,31 @@ CONFIG_MICROCODE=m CONFIG_X86_MSR=m CONFIG_X86_CPUID=m +CONFIG_SWIOTLB=y # # Firmware Drivers # CONFIG_EDD=m -CONFIG_EFI_VARS=m CONFIG_DELL_RBU=m CONFIG_DCDBAS=m # CONFIG_NOHIGHMEM is not set -CONFIG_HIGHMEM4G=y -# CONFIG_HIGHMEM64G is not set +# CONFIG_HIGHMEM4G is not set +CONFIG_HIGHMEM64G=y CONFIG_PAGE_OFFSET=0xC0000000 CONFIG_HIGHMEM=y -CONFIG_ARCH_FLATMEM_ENABLE=y -CO...

On 12/20/2011 10:47 PM, Stephen Rothwell wrote: > Hi all, > > Changes since 20111220: drivers/xen/xenbus/xenbus_dev_backend.c:74:2: error: implicit declaration of function ''xen_initial_domain'' Full randconfig file is attached. -- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code ***

...NFIG_THINKPAD_ACPI_BAY=y CONFIG_THINKPAD_ACPI_VIDEO=y CONFIG_THINKPAD_ACPI_HOTKEY_POLL=y CONFIG_INTEL_MENLOW=m # CONFIG_EEEPC_LAPTOP is not set CONFIG_ACPI_WMI=m # CONFIG_ACPI_ASUS is not set # CONFIG_ACPI_TOSHIBA is not set # # Firmware Drivers # # CONFIG_EDD is not set CONFIG_FIRMWARE_MEMMAP=y # CONFIG_EFI_VARS is not set CONFIG_DELL_RBU=m CONFIG_DCDBAS=m CONFIG_DMIID=y CONFIG_ISCSI_IBFT_FIND=y CONFIG_ISCSI_IBFT=m # # File systems # CONFIG_EXT2_FS=m CONFIG_EXT2_FS_XATTR=y CONFIG_EXT2_FS_POSIX_ACL=y CONFIG_EXT2_FS_SECURITY=y # CONFIG_EXT2_FS_XIP is not set CONFIG_EXT3_FS=m CONFIG_EXT3_FS_XATTR=y CONFIG_EX...

...NFIG_THINKPAD_ACPI_BAY=y CONFIG_THINKPAD_ACPI_VIDEO=y CONFIG_THINKPAD_ACPI_HOTKEY_POLL=y CONFIG_INTEL_MENLOW=m # CONFIG_EEEPC_LAPTOP is not set CONFIG_ACPI_WMI=m # CONFIG_ACPI_ASUS is not set # CONFIG_ACPI_TOSHIBA is not set # # Firmware Drivers # # CONFIG_EDD is not set CONFIG_FIRMWARE_MEMMAP=y # CONFIG_EFI_VARS is not set CONFIG_DELL_RBU=m CONFIG_DCDBAS=m CONFIG_DMIID=y CONFIG_ISCSI_IBFT_FIND=y CONFIG_ISCSI_IBFT=m # # File systems # CONFIG_EXT2_FS=m CONFIG_EXT2_FS_XATTR=y CONFIG_EXT2_FS_POSIX_ACL=y CONFIG_EXT2_FS_SECURITY=y # CONFIG_EXT2_FS_XIP is not set CONFIG_EXT3_FS=m CONFIG_EXT3_FS_XATTR=y CONFIG_EX...

...NFIG_THINKPAD_ACPI_BAY=y CONFIG_THINKPAD_ACPI_VIDEO=y CONFIG_THINKPAD_ACPI_HOTKEY_POLL=y CONFIG_INTEL_MENLOW=m # CONFIG_EEEPC_LAPTOP is not set CONFIG_ACPI_WMI=m # CONFIG_ACPI_ASUS is not set # CONFIG_ACPI_TOSHIBA is not set # # Firmware Drivers # # CONFIG_EDD is not set CONFIG_FIRMWARE_MEMMAP=y # CONFIG_EFI_VARS is not set CONFIG_DELL_RBU=m CONFIG_DCDBAS=m CONFIG_DMIID=y CONFIG_ISCSI_IBFT_FIND=y CONFIG_ISCSI_IBFT=m # # File systems # CONFIG_EXT2_FS=m CONFIG_EXT2_FS_XATTR=y CONFIG_EXT2_FS_POSIX_ACL=y CONFIG_EXT2_FS_SECURITY=y # CONFIG_EXT2_FS_XIP is not set CONFIG_EXT3_FS=m CONFIG_EXT3_FS_XATTR=y CONFIG_EX...

...# CONFIG_FW_CFG_SYSFS_CMDLINE is not set CONFIG_GOOGLE_FIRMWARE=y # CONFIG_GOOGLE_SMI is not set CONFIG_GOOGLE_COREBOOT_TABLE=y CONFIG_GOOGLE_MEMCONSOLE=y CONFIG_GOOGLE_MEMCONSOLE_X86_LEGACY=y CONFIG_GOOGLE_MEMCONSOLE_COREBOOT=y CONFIG_GOOGLE_VPD=y # # EFI (Extensible Firmware Interface) Support # CONFIG_EFI_VARS=y CONFIG_EFI_ESRT=y CONFIG_EFI_RUNTIME_MAP=y CONFIG_EFI_FAKE_MEMMAP=y CONFIG_EFI_MAX_FAKE_MEM=8 CONFIG_EFI_RUNTIME_WRAPPERS=y CONFIG_EFI_BOOTLOADER_CONTROL=m # CONFIG_EFI_CAPSULE_LOADER is not set # CONFIG_EFI_TEST is not set # CONFIG_EFI_RCI2_TABLE is not set # CONFIG_EFI_DISABLE_PCI_DMA is not se...

...# CONFIG_FW_CFG_SYSFS_CMDLINE is not set CONFIG_GOOGLE_FIRMWARE=y # CONFIG_GOOGLE_SMI is not set CONFIG_GOOGLE_COREBOOT_TABLE=y CONFIG_GOOGLE_MEMCONSOLE=y CONFIG_GOOGLE_MEMCONSOLE_X86_LEGACY=y CONFIG_GOOGLE_MEMCONSOLE_COREBOOT=y CONFIG_GOOGLE_VPD=y # # EFI (Extensible Firmware Interface) Support # CONFIG_EFI_VARS=y CONFIG_EFI_ESRT=y CONFIG_EFI_RUNTIME_MAP=y CONFIG_EFI_FAKE_MEMMAP=y CONFIG_EFI_MAX_FAKE_MEM=8 CONFIG_EFI_RUNTIME_WRAPPERS=y CONFIG_EFI_BOOTLOADER_CONTROL=m # CONFIG_EFI_CAPSULE_LOADER is not set # CONFIG_EFI_TEST is not set # CONFIG_EFI_RCI2_TABLE is not set # CONFIG_EFI_DISABLE_PCI_DMA is not se...

I can''t boot my PV domU domain using a pv_ops 2.6.30.1 kernel. Using the xenified standard debian kernel (2.6.26, the same as in dom0) in DomU it does boot with pvgrub. Any clues, to what to try or test ? Regards, Sander xm dmesg gives: traps.c:437:d12 Unhandled general protection fault fault/trap [#13] on VCPU 0 [ec=0000] (XEN) domain_crash_sync called from entry.S (XEN) Domain 12

...E_MEMMAP=y # CONFIG_DELL_RBU is not set # CONFIG_DCDBAS is not set # CONFIG_DMIID is not set CONFIG_DMI_SYSFS=y CONFIG_DMI_SCAN_MACHINE_NON_EFI_FALLBACK=y CONFIG_ISCSI_IBFT_FIND=y # CONFIG_FW_CFG_SYSFS is not set # CONFIG_GOOGLE_FIRMWARE is not set # # EFI (Extensible Firmware Interface) Support # CONFIG_EFI_VARS=y CONFIG_EFI_ESRT=y # CONFIG_EFI_RUNTIME_MAP is not set CONFIG_EFI_FAKE_MEMMAP=y CONFIG_EFI_MAX_FAKE_MEM=8 CONFIG_EFI_RUNTIME_WRAPPERS=y # CONFIG_EFI_BOOTLOADER_CONTROL is not set CONFIG_EFI_CAPSULE_LOADER=m # CONFIG_EFI_CAPSULE_QUIRK_QUARK_CSH is not set CONFIG_EFI_TEST=m CONFIG_APPLE_PROPERTIES=y...