On Wed, Aug 07, 2019 at 07:47:43PM +0200, Matthieu Herrb wrote:
> On Wed, Aug 07, 2019 at 11:32:09AM +0200, Matthieu Herrb wrote:
> > 
> > I will also have a look on why did the extra built-in modes disapear.
> > But I think that if you can run a better driver than xf86-video-vesa,
> > it is better.
> 
> Hi again,
> 
> I think I've found the problem.
> It's caused by this commit:
> https://gitlab.freedesktop.org/xorg/xserver/commit/fdc79fe72bc0b97776df2c3a664076c60e08a87c
> 
> Can you try this patch to xserver 1.20.5 ?
> 
> The reason why xf86PruneDuplicateModes() removes modes that are not
> duplicated is still to be identified though.
> 
> Index: hw/xfree86/modes/xf86EdidModes.c
> ===================================================================
> RCS file: /cvs/xenocara/xserver/hw/xfree86/modes/xf86EdidModes.c,v
> retrieving revision 1.18
> diff -u -p -u -r1.18 xf86EdidModes.c
> --- hw/xfree86/modes/xf86EdidModes.c  27 Jul 2019 07:57:17 -0000      1.18
> +++ hw/xfree86/modes/xf86EdidModes.c  7 Aug 2019 17:42:14 -0000
> @@ -1220,8 +1220,6 @@ xf86EdidMonitorSet(int scrnIndex, MonPtr
>              Monitor->Modes = Modes;
>          }
>  
> -        Monitor->Modes = xf86PruneDuplicateModes(Monitor->Modes);
> -
>          /* Update pointer to last mode */
>          for (Mode = Monitor->Modes; Mode && Mode->next; Mode = Mode->next) {}
>          Monitor->Last = Mode;
> 

I confirm the diff solves the issue.

[    39.848] (II) VESA(0): Total Memory: 256 64KB banks (16384kB)
[    39.848] (II) VESA(0): <default monitor>: Using hsync range of 30.00-83.00 
kHz
[    39.848] (II) VESA(0): <default monitor>: Using vrefresh range of 
56.00-75.00 Hz
[    39.848] (II) VESA(0): <default monitor>: Using maximum pixel clock of 
145.00 MHz
[    39.848] (WW) VESA(0): Unable to estimate virtual size
[    39.848] (II) VESA(0): Not using built-in mode "1400x1050" (no mode of this 
name)
[    39.848] (II) VESA(0): Not using built-in mode "640x400" (no mode of this 
name)
[    39.848] (II) VESA(0): Not using built-in mode "640x400" (no mode of this 
name)
[    39.848] (II) VESA(0): Not using built-in mode "640x350" (no mode of this 
name)
[    39.848] (II) VESA(0): Not using built-in mode "512x384" (no mode of this 
name)
[    39.848] (II) VESA(0): Not using built-in mode "320x240" (no mode of this 
name)
[    39.848] (II) VESA(0): Not using built-in mode "320x200" (no mode of this 
name)
[    39.848] (II) VESA(0): Virtual size is 1280x1024 (pitch 1280)
[    39.848] (**) VESA(0): *Built-in mode "1280x1024"
[    39.848] (**) VESA(0): *Built-in mode "1280x1024"
[    39.848] (**) VESA(0): *Built-in mode "1152x864"
[    39.849] (**) VESA(0): *Built-in mode "1024x768"
[    39.849] (**) VESA(0): *Built-in mode "800x600"
[    39.849] (**) VESA(0): *Built-in mode "640x480"
[    39.849] (**) VESA(0): *Built-in mode "720x400"
[    39.849] (**) VESA(0): Display dimensions: (430, 270) mm
[    39.849] (**) VESA(0): DPI set to (75, 96)
[    39.849] (**) VESA(0): Using "Shadow Framebuffer"

The virtual size isn't "720x400" anymore.

Thanks.
-- 
Sebastien Marie

Reply via email to