Re: bochs_hw_init fails to request framebuffer on EFI boot with plymouth visible

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Jan 15, 2020 at 03:27:41PM +0100, Marek Marczykowski-Górecki wrote:
> On Wed, Jan 15, 2020 at 03:13:53PM +0100, Gerd Hoffmann wrote:
> >   Hi,
> > 
> > > > And "grep -A1 0000:00:02.0 /proc/iomem" ?
> > > 
> > >   c0000000-c0ffffff : 0000:00:02.0
> > >   c1000000-c103ffff : 0000:00:04.0
> > 
> > So no reservation left.  Whatever blocked the pci bar resource (efifb
> > probably) is gone now.
> > 
> > So the interesting question is why that reservation sticked long enough
> > to prevent bochs-drm from initializing.  In theory efifb de-init should
> > be completed when drm_fb_helper_remove_conflicting_pci_framebuffers()
> > returns.
> 
> Maybe the fact that switching to text mode plymouth help, gives some
> hint?

Maybe plymouth having a /dev/fb0 file handle open in gfx mode has
something to do with it.  But if that is the case I should be able to
reproduce it in theory.  Which is not the case though ...

cheers,
  Gerd

_______________________________________________
Virtualization mailing list
Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linuxfoundation.org/mailman/listinfo/virtualization




[Index of Archives]     [KVM Development]     [Libvirt Development]     [Libvirt Users]     [CentOS Virtualization]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite Forum]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux