search for: efifb

On Mon, 02 June 2014 Bruno Pr?mont <bonbons at linux-vserver.org> wrote: > With commit b4aa0163056b ("efifb: Implement vga_default_device() (v2)") > Matthew Garrett introduced a efifb vga_default_device() so that EFI > systems that do not load shadow VBIOS or setup VGA get proper value for > boot_vga PCI sysfs attribute on the corresponding PCI device. > > Xorg is refusing to detect...

Hi All, I've been running Gentoo on a ZBook with great success for a couple years, but I've been stymied in my attempts to implement SecureBoot by an apparent problem with efifb to nouveaufb handoff, but only when external monitors are attached. The handoff works without issue when the BIOS is in Mixed EFI mode, with and without external monitors, and works in Native EFI mode without external monitors. Diffing dmesg from working (mixed) to nonworking (native), I find num...

...p at turmel.org> wrote: > On 02/01/2017 10:40 AM, Phil Turmel wrote: >> Hi All, >> >> I've been running Gentoo on a ZBook with great success for a couple years, >> but I've been stymied in my attempts to implement SecureBoot by an >> apparent problem with efifb to nouveaufb handoff, but only when external >> monitors are attached. The handoff works without issue when the BIOS is >> in Mixed EFI mode, with and without external monitors, and >> works in Native EFI mode without external monitors. > > Sorted by nouveau.config=NvForceP...

I think we had the wrong culprit: I just tried PCI-disabling the NVAC card (and keeping the NV96 one), and it just works: no garbage screen, and moreover, I get no hangs nor errors when enabling acceleration! I'll spend some time comparing both outputs (without NVAC, and without NV96) to find out what the NVAC is doing wrong. Pierre > On 31 Jan 2014, at 23:58, Ilia Mirkin <imirkin at

...ng GRUB as the boot loader. The kernel is based on 4.4.15 (specifically, Ubuntu's 4.4.0-34 kernel. Looking at dmesg shows some interesting differences regarding fb, which is why I suspect the device isn't getting automatically detected: $ egrep '^(nouveau|.*fb).*:' dmesg.notime efifb: dmi detected MacBookPro3,1 - framebuffer at 0xc0030000 (1440x900, stride 8192) efifb: probing for efifb efifb: framebuffer at 0xc0030000, mapped to 0xffffc90000800000, using 7232k, total 7232k efifb: mode is 1440x900x32, linelength=8192, pages=1 efifb: scrolling: redraw efifb: Truecolor: size=8:8:...

...I use the Macbook's native EFI mode (i.e. *without* BIOS emulation). If I use the BIOS emulation then nouveau works. Typing blindly, I extracted the dmesg output, from an EFI boot: #grep -i -e drm -e nouv -e fb efi-dmesg Kernel command line: BOOT_IMAGE=/boot/experimental root=/dev/sda5 video=efifb reboot=pci efifb: probing for efifb efifb: framebuffer at 0xc0010000, mapped to 0xffffc90004580000, using 6400k, total 6400k efifb: mode is 1280x800x32, linelength=8192, pages=1 efifb: scrolling: redraw efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0 fb0: EFI VGA frame buffer device [drm] Initializ...

.../EFI/BOOT/BOOTX86.efi) Problems: - System "crashes" when nouveau is loaded without any parameters. It would be nice if one can set individual parameters for each hardware (as in "modprobe nouveau -dev-pci=03:00.0 -noaccel=1" and "modprobe nouveau -dev-pci=02:00.0"). - EFIFB is required to get nouveau to bind panel to graphic-adapter(s). If EFIFB is not loaded, nouveau selects no graphic adapter and swiches off display on "echo OFF > ...". - EFIFB handover seems to be broken: As soon as nouveau loads, screen gets scrambled on the graphic adapter which is a...

...e: >> On 02/01/2017 10:40 AM, Phil Turmel wrote: >>> Hi All, >>> >>> I've been running Gentoo on a ZBook with great success for a couple years, >>> but I've been stymied in my attempts to implement SecureBoot by an >>> apparent problem with efifb to nouveaufb handoff, but only when external >>> monitors are attached. The handoff works without issue when the BIOS is >>> in Mixed EFI mode, with and without external monitors, and >>> works in Native EFI mode without external monitors. >> >> Sorted by nou...

It removes a hack from nouveau code which had to detect which region to pass to kick vesafb/efifb. Signed-off-by: Marcin Slusarz <marcin.slusarz at gmail.com> Cc: Eric Anholt <eric at anholt.net> Cc: Ben Skeggs <bskeggs at redhat.com> Cc: Thomas Hellstrom <thellstrom at vmware.com> Cc: Dave Airlie <airlied at redhat.com> Cc: Peter Jones <pjones at redhat.com&gt...

It simplifies nouveau code by removal of detection which region to pass to kick vesafb/efifb. Signed-off-by: Marcin Slusarz <marcin.slusarz at gmail.com> Cc: Eric Anholt <eric at anholt.net> Cc: Ben Skeggs <bskeggs at redhat.com> Cc: Thomas Hellstrom <thellstrom at vmware.com> Cc: Dave Airlie <airlied at redhat.com> Cc: Peter Jones <pjones at redhat.com&gt...

.../2017 10:40 AM, Phil Turmel wrote: >>>> Hi All, >>>> >>>> I've been running Gentoo on a ZBook with great success for a couple years, >>>> but I've been stymied in my attempts to implement SecureBoot by an >>>> apparent problem with efifb to nouveaufb handoff, but only when external >>>> monitors are attached. The handoff works without issue when the BIOS is >>>> in Mixed EFI mode, with and without external monitors, and >>>> works in Native EFI mode without external monitors. >>> >&g...

fb_do_apertures_overlap is returning wrong value when one aperture is completely whithin the other. Add generic ranges_overlap macro (probably kernel.h candidate) and use it here. Signed-off-by: Marcin Slusarz <marcin.slusarz at gmail.com> Cc: Dave Airlie <airlied at redhat.com> Cc: Peter Jones <pjones at redhat.com> Cc: Andrew Morton <akpm at linux-foundation.org> ---

...drm/nouveau/nouveau_drm.c index eb10c80ed853..e8560444ab57 100644 --- a/drivers/gpu/drm/nouveau/nouveau_drm.c +++ b/drivers/gpu/drm/nouveau/nouveau_drm.c @@ -697,7 +697,8 @@ static int nouveau_drm_probe(struct pci_dev *pdev, nvkm_device_del(&device); /* Remove conflicting drivers (vesafb, efifb etc). */ - ret = remove_conflicting_pci_framebuffers(pdev, "nouveaufb"); + if (IS_ENABLED(CONFIG_FBDEV)) + ret = remove_conflicting_pci_framebuffers(pdev, "nouveaufb"); if (ret) return ret; -- 2.26.2

...> 5.5 is OK. 5.6 is broken. > > I've heard some issues relating to missing firmware lately. It should > work fine without firmware, but perhaps that got broken. Can you log > into the machine and check dmesg to see what's there? My guess is that > nouveau takes over from efifb, and then fails to load at some point in > the middle. I've fixed the issue by including all firmware until "failed to load" messages disappeared. X works and fbconsole on VT1-VT6 works too. CONFIG_EXTRA_FIRMWARE="nvidia/gp104/gr/sw_nonctx.bin nvidia/gp104/gr/sw_ctx.bin nvid...

...hipset is supported before booting - * fbdev off the hardware, as there's no way to put it back. - */ - ret = nvkm_device_pci_new(pdev, NULL, "error", true, false, 0, &device); - if (ret) - return ret; - - nvkm_device_del(&device); - - /* Remove conflicting drivers (vesafb, efifb etc). */ - aper = alloc_apertures(3); - if (!aper) - return -ENOMEM; - - aper->ranges[0].base = pci_resource_start(pdev, 1); - aper->ranges[0].size = pci_resource_len(pdev, 1); - aper->count = 1; - - if (pci_resource_len(pdev, 2)) { - aper->ranges[aper->count].base = pci_resource_s...

Hi, I’m struggling with virsh not detecting my hugepage mount. I have the following kernel command line: BOOT_IMAGE=/vmlinuz-4.8.13-gentoo root=/dev/mapper/gensd-gentoo ro quiet splash intel_iommu=on video=efifb:off,vesafb:off,simplefb:off splash=verbose,theme:livedvd-aurora kvm.ignore_msrs=1 transparent_hugepage=never hugepages=3072 softlevel=qemuvm My startup script outputs the following: hugetlbfs /var/lib/hugetlbfs hugetlbfs rw,relatime,pagesize=2097152,uid=77,gid=77,mode=0770 0 0 [2016.12.13 22:22:50...

gp104 refuses to switch to "graphic" mode and show anything past this line: fb0: switching to nouveaufb from EFI VGA Machine is fine, as it I can press Ctrl+Alt+Delete and reboot it normally. 5.5 is OK. 5.6 is broken. Bisecting is kinda painful with miscompilation and init/main.c breakage. BTW do I need all those megabytes of firmware? [ 0.923273] fb0: switching to nouveaufb

The XenPVHVM extensions have not been tested much on very old hypervisors. At least Xen 3.4 gets some testing with the pvops kernel. Require at least Xen 3.4 for the PVonHVM extensions. If an older hypervisor is detected the extensions will be disabled and the guest will only see emulated hardware. Signed-off-by: Olaf Hering <olaf@aepfle.de> --- arch/x86/xen/enlighten.c | 27

...off the hardware, as there's no way to put it back. > - */ > - ret = nvkm_device_pci_new(pdev, NULL, "error", true, false, 0, > &device); > - if (ret) > - return ret; > - > - nvkm_device_del(&device); > - > - /* Remove conflicting drivers (vesafb, efifb etc). */ > - aper = alloc_apertures(3); > - if (!aper) > - return -ENOMEM; > - > - aper->ranges[0].base = pci_resource_start(pdev, 1); > - aper->ranges[0].size = pci_resource_len(pdev, 1); > - aper->count = 1; > - > - if (pci_resource_len(pdev, 2)) { > - ape...

...e the inactive GPU. + */ + if (IS_ENABLED(CONFIG_VGA_ARB) && IS_ENABLED(CONFIG_VGA_SWITCHEROO) && + apple_gmux_present() && pdev != vga_default_device() && + !vga_switcheroo_handler_flags()) + return -EPROBE_DEFER; + /* remove conflicting drivers (vesafb, efifb etc) */ aper = alloc_apertures(3); if (!aper) -- 1.8.5.2 (Apple Git-48)