search for: config_fb_efi

...est for such tests. Right, I've confirmed boot failure using CONFIG_RELOCATABLE with unmodified Linux 3.12.24, 3.13, 3.15, 3.18, and 3.19-rc7 kernels. > I know that for EFISTUB, the kernel config should include: > > CONFIG_RELOCATABLE=y > CONFIG_EFI=y > CONFIG_EFI_STUB=y > CONFIG_FB_EFI=y > CONFIG_FRAMEBUFFER_CONSOLE=y > > For UEFI ia32 firmware, it should be possible (in theory, and if I > understand correctly) to use 32 bit Syslinux to load a 64 bit kernel, > as long as the latter has CONFIG_EFI_MIXED enabled. > > We have seen reports of failure to boot...

...Testing with public popular kernels that are known to work (so to compare the behavior) might be useful too, but I don't know of any particular kernels to suggest for such tests. I know that for EFISTUB, the kernel config should include: CONFIG_RELOCATABLE=y CONFIG_EFI=y CONFIG_EFI_STUB=y CONFIG_FB_EFI=y CONFIG_FRAMEBUFFER_CONSOLE=y For UEFI ia32 firmware, it should be possible (in theory, and if I understand correctly) to use 32 bit Syslinux to load a 64 bit kernel, as long as the latter has CONFIG_EFI_MIXED enabled. We have seen reports of failure to boot relocatable kernels when they are...

...firmed boot failure using CONFIG_RELOCATABLE with > unmodified Linux 3.12.24, 3.13, 3.15, 3.18, and 3.19-rc7 kernels. > > > I know that for EFISTUB, the kernel config should include: > > > > CONFIG_RELOCATABLE=y > > CONFIG_EFI=y > > CONFIG_EFI_STUB=y > > CONFIG_FB_EFI=y > > CONFIG_FRAMEBUFFER_CONSOLE=y > > > > For UEFI ia32 firmware, it should be possible (in theory, and if I > > understand correctly) to use 32 bit Syslinux to load a 64 bit kernel, > > as long as the latter has CONFIG_EFI_MIXED enabled. > > > > We ha...

On Fri, 6 Feb 2015, Ady wrote: > ... > But if we are talking about Chromebooks with SeaBIOS, are we talking > about booting kernels in CSM mode? Or in UEFI mode? > > Other than Chromebooks with (stock) SeaBIOS, is this new reported > behavior also seen under other cases / hardware / firmware / kernels > (versions)? Hi Ady, With a clone of the git repo on kernel.org I run

...-bit kernels, got the same problem, that is, nothing after "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 pro...

> 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

...rnel hangs before then. Anyway, I was wondering if anyone reading this has any experience that might suggest why 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...

...s has any experience that >> might suggest why 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?...

...ondering if anyone reading this has any experience that > might suggest why 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? Regarding the configurati...

...ff --git a/arch/x86/include/asm/vga.h b/arch/x86/include/asm/vga.h > index 44282fb..c4b9dc2 100644 > --- a/arch/x86/include/asm/vga.h > +++ b/arch/x86/include/asm/vga.h > @@ -17,10 +17,4 @@ > #define vga_readb(x) (*(x)) > #define vga_writeb(x, y) (*(y) = (x)) > > -#ifdef CONFIG_FB_EFI > -#define __ARCH_HAS_VGA_DEFAULT_DEVICE > -extern struct pci_dev *vga_default_device(void); > -extern void vga_set_default_device(struct pci_dev *pdev); > -#endif > - > #endif /* _ASM_X86_VGA_H */ > diff --git a/arch/x86/pci/fixup.c b/arch/x86/pci/fixup.c > index 94ae9ae.....

Hi, I'm pleased to announce release 0.8 of efilinux, a reference implementation of a minimal UEFI bootloader. This bootloader has no bells or whistles, it is simply a prototype with the minimum amount of smarts required to load a linux kernel (though loaders for other formats could be added). Currently it only supports booting x86-64 bzImages but i386 support is planned for release 0.9, with

Hi, Following is a simple patch that is needed in nouveau to get accelerated X on a Xen dom0 pv_ops kernel. The kernel is jeremy's 2.6.31.6 as of 20100222. The whole gpu tree of nouveau (which is almost the mainline merge), was substituted into the kernel-tree. All components of X (mesa, Xorg-server-7.5, xf86-nouveau, libdrm) used of the same day. Patch: diff -Naur

Hi, Following is a simple patch that is needed in nouveau to get accelerated X on a Xen dom0 pv_ops kernel. The kernel is jeremy's 2.6.31.6 as of 20100222. The whole gpu tree of nouveau (which is almost the mainline merge), was substituted into the kernel-tree. All components of X (mesa, Xorg-server-7.5, xf86-nouveau, libdrm) used of the same day. Patch: diff -Naur

...; # CONFIG_FB_CIRRUS is not set > # CONFIG_FB_PM2 is not set > # CONFIG_FB_CYBER2000 is not set > # CONFIG_FB_ARC is not set > # CONFIG_FB_ASILIANT is not set > # CONFIG_FB_IMSTT is not set > # CONFIG_FB_VGA16 is not set > # CONFIG_FB_UVESA is not set > CONFIG_FB_VESA=y > CONFIG_FB_EFI=y > # CONFIG_FB_HECUBA is not set > # CONFIG_FB_HGA is not set > # CONFIG_FB_S1D13XXX is not set > # CONFIG_FB_NVIDIA is not set > # CONFIG_FB_RIVA is not set > # CONFIG_FB_I810 is not set > # CONFIG_FB_LE80578 is not set > # CONFIG_FB_INTEL is not set > # CONFIG_FB_MATRO...

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 ***

...HT=y CONFIG_FB_MODE_HELPERS=y CONFIG_FB_TILEBLITTING=y # # Frame buffer hardware drivers # CONFIG_FB_CIRRUS=m CONFIG_FB_PM2=m CONFIG_FB_PM2_FIFO_DISCONNECT=y CONFIG_FB_CYBER2000=m CONFIG_FB_ARC=m CONFIG_FB_ASILIANT=y CONFIG_FB_IMSTT=y CONFIG_FB_VGA16=m CONFIG_FB_UVESA=m # CONFIG_FB_VESA is not set CONFIG_FB_EFI=y CONFIG_FB_HECUBA=m CONFIG_FB_HGA=m # CONFIG_FB_HGA_ACCEL is not set CONFIG_FB_S1D13XXX=m CONFIG_FB_NVIDIA=m CONFIG_FB_NVIDIA_I2C=y # CONFIG_FB_NVIDIA_DEBUG is not set CONFIG_FB_NVIDIA_BACKLIGHT=y CONFIG_FB_RIVA=m CONFIG_FB_RIVA_I2C=y # CONFIG_FB_RIVA_DEBUG is not set CONFIG_FB_RIVA_BACKLIGHT=y CO...

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

...S=y CONFIG_FB_TILEBLITTING=y # # Frame buffer hardware drivers # # CONFIG_FB_CIRRUS is not set CONFIG_FB_PM2=m CONFIG_FB_PM2_FIFO_DISCONNECT=y # CONFIG_FB_CYBER2000 is not set CONFIG_FB_ARC=m # CONFIG_FB_ASILIANT is not set # CONFIG_FB_IMSTT is not set # CONFIG_FB_VGA16 is not set CONFIG_FB_VESA=y CONFIG_FB_EFI=y # CONFIG_FB_N411 is not set CONFIG_FB_HGA=m CONFIG_FB_OPENCORES=m CONFIG_FB_S1D13XXX=y CONFIG_FB_NVIDIA=m CONFIG_FB_NVIDIA_I2C=y # CONFIG_FB_NVIDIA_DEBUG is not set CONFIG_FB_NVIDIA_BACKLIGHT=y # CONFIG_FB_RIVA is not set # CONFIG_FB_I740 is not set CONFIG_FB_LE80578=m CONFIG_FB_CARILLO_RANCH=m #...

...S=y CONFIG_FB_TILEBLITTING=y # # Frame buffer hardware drivers # # CONFIG_FB_CIRRUS is not set CONFIG_FB_PM2=m CONFIG_FB_PM2_FIFO_DISCONNECT=y # CONFIG_FB_CYBER2000 is not set CONFIG_FB_ARC=m # CONFIG_FB_ASILIANT is not set # CONFIG_FB_IMSTT is not set # CONFIG_FB_VGA16 is not set CONFIG_FB_VESA=y CONFIG_FB_EFI=y # CONFIG_FB_N411 is not set CONFIG_FB_HGA=m CONFIG_FB_OPENCORES=m CONFIG_FB_S1D13XXX=y CONFIG_FB_NVIDIA=m CONFIG_FB_NVIDIA_I2C=y # CONFIG_FB_NVIDIA_DEBUG is not set CONFIG_FB_NVIDIA_BACKLIGHT=y # CONFIG_FB_RIVA is not set # CONFIG_FB_I740 is not set CONFIG_FB_LE80578=m CONFIG_FB_CARILLO_RANCH=m #...

...# # Frame buffer hardware drivers # # CONFIG_FB_CIRRUS is not set # CONFIG_FB_PM2 is not set # CONFIG_FB_CYBER2000 is not set # CONFIG_FB_ARC is not set # CONFIG_FB_ASILIANT is not set # CONFIG_FB_IMSTT is not set # CONFIG_FB_VGA16 is not set # CONFIG_FB_UVESA is not set # CONFIG_FB_VESA is not set CONFIG_FB_EFI=y # CONFIG_FB_N411 is not set # CONFIG_FB_HGA is not set # CONFIG_FB_OPENCORES is not set # CONFIG_FB_S1D13XXX is not set # CONFIG_FB_NVIDIA is not set # CONFIG_FB_RIVA is not set # CONFIG_FB_I740 is not set # CONFIG_FB_LE80578 is not set # CONFIG_FB_MATROX is not set # CONFIG_FB_RADEON is not set...