Re: Xvfb and number of bytes per pixel

On Wed, 2020-09-09 at 13:28 +0200, Marcin K wrote: > Hello, > I'm grabbing frames from Xvfb to use them as an opengl texture. I've > noticed that there are 4 bytes per pixel, that suggest that there's > an alpha channel, or something else. Is it possible to force Xvfb to > store only RGB values in

Re: no screens detected

On Wed, 2020-09-09 at 16:56 +, Paul Kagan wrote: > What do I do to get this to work? > > x.org.log: > > https://bsd.to/T3hR The relevant bits of the log here are: [ 53814.484] (--) PCI:*(0@0:2:0) 1013:00b8:1af4:1100 rev 0, Mem @ 0xfc00/33554432, 0xfebd/4096, BIOS @

Re: Xvfb and number of bytes per pixel

Thank you for explanation. That was my deepest fear. The main issue is that I'm copying the image data real-time, and in my case, on 4* UWXGA display, this one byte means 9MB less data per frame. czw., 10 wrz 2020 o 23:32 Adam Jackson napisał(a): > On Wed, 2020-09-09 at 13:28 +0200, Marcin K

[ANNOUNCE] xf86-video-vesa 2.5.0

This release rolls up a few minor bug fixes since 2.4.0. We now refuse to run on machines with UEFI firmware (on Linux only, patches welcome for other OSes) since it won't work in the general case and you probably have a kernel framebuffer driver running already. We also only attempt to use 24bpp

no screens detected

What do I do to get this to work? x.org.log: https://bsd.to/T3hR Thank you… Provenance : Courrier pour Windows 10 ___ xorg@lists.x.org: X.Org support Archives:

[ANNOUNCE] xf86-video-vesa 2.5.0

This release rolls up a few minor bug fixes since 2.4.0. We now refuse to run on machines with UEFI firmware (on Linux only, patches welcome for other OSes) since it won't work in the general case and you probably have a kernel framebuffer driver running already. We also only attempt to use 24bpp