Re: mplayer screws up colormap as cursor moved into the video window

From: Jin Guojun[VFF] <jguojun_at_gmail.com>
Date: Thu, 30 May 2024 02:01:39 UTC
On 5/29/24 04:20, Polytropon wrote:
> On Tue, 28 May 2024 22:21:09 -0700, Jin Guojun[VFF] wrote:
>> When upgraded to 13.3-R, I have experienced a problem that Mplayer can
>> cause system colormap distorted when the cursor moved into the video window.
>>
>> [...]
>>
>> On this 13.3 machine, one thing have been changed -- the video device.
>> X.org is no longer supporting older video cards, such as Radeon 370,
>> NV210, etc., so I used AMD APU video (Radeon HD 8570D). xf86-video-ati
>> driver does not support it, therefore no /etc/X11/xorg.conf is created,
>> and X is started with default configuration (VESA?), not sure if mplayer
>> does not like it.
> The mplayer program uses the specified output, and it is
> preferring direct rendering if your graphics card and driver
> supports it, which in case of a Radeo HD should absolutely
> be no problem. However, it seems that your X currently uses
> VESA, and that's why you're seeing this problem.
>
> Sadly, graphics configuration has become quite complicated
> on FreeBSD, and you need to check several things:
>
> 1. Is the correct KMS kernel module loaded?
>
> 2. Is the correct X driver loaded?
>
> 3. What output is mplayer configured to use?
>
> You can check "kldstat" and "dmesg" output for question 1,
> /var/log/Xorg.0.log for question 2, and the mplayer configuration
> directory, whererever it might be today, for question 3. You
> can also manually check:
>
> 	$ mplayer -vo x11 test.avi
>
> for VESA (should always work), and
>
> 	$ mplayer -vo gl test.avi
>
> for direct rendering (works if question 1 and 2 have been
> answered with "yes").
>
> I have a reference system (HP mini-laptop) with AMD graphics
> that I can check a working configuration for.
Thanks for the information. The output was configured to x11. Changing 
to gl solved the problem.

No KMS is loaded. Loading drm-510-kmod-5.10.163_8 and 
xf86-video-ati-19.1.0_6,1 will cause system crash.

  1   33 0xffffffff80200000  21430f0 kernel
  2    1 0xffffffff82520000     3378 acpi_wmi.ko
  3    1 0xffffffff82524000     3218 intpm.ko
  4    1 0xffffffff82528000     2180 smbus.ko
  5    1 0xffffffff8252b000     3340 uhid.ko
  6    1 0xffffffff8252f000     3380 usbhid.ko
  7    1 0xffffffff82533000     32b0 hidbus.ko
  8    1 0xffffffff82537000     3320 wmt.ko
  9    1 0xffffffff8253b000     4350 ums.ko
10    1 0xffffffff82540000     3538 fdescfs.ko

X driver is VESA

[  2016.900] (II) LoadModule: "ati"
[  2016.900] (WW) Warning, couldn't open module ati
[  2016.900] (EE) Failed to load module "ati" (module does not exist, 0)
[  2016.900] (II) LoadModule: "modesetting"
[  2016.900] (II) Loading 
/usr/local/lib/xorg/modules/drivers/modesetting_drv.so
[  2016.900] (II) Module modesetting: vendor="X.Org Foundation"
[  2016.900]    compiled for 1.21.1.11, module version = 1.21.1
[  2016.900]    Module class: X.Org Video Driver
[  2016.900]    ABI class: X.Org Video Driver, version 25.2
[  2016.900] (II) LoadModule: "scfb"
[  2016.900] (II) Loading /usr/local/lib/xorg/modules/drivers/scfb_drv.so
[  2016.900] (II) Module scfb: vendor="X.Org Foundation"
[  2016.900]    compiled for 1.21.1.11, module version = 0.0.5
[  2016.900]    ABI class: X.Org Video Driver, version 25.2
[  2016.900] (II) LoadModule: "vesa"
[  2016.900] (II) Loading /usr/local/lib/xorg/modules/drivers/vesa_drv.so
[  2016.901] (II) Module vesa: vendor="X.Org Foundation"
[  2016.901]    compiled for 1.21.1.11, module version = 2.5.0
[  2016.901]    Module class: X.Org Video Driver
[  2016.901]    ABI class: X.Org Video Driver, version 25.2
[  2016.901] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[  2016.901] (II) scfb: driver for wsdisplay framebuffer: scfb
[  2016.901] (II) VESA: driver for VESA chipsets: vesa
[  2016.901] (--) Using syscons driver with X support (version 2.0)
[  2016.901] (--) using VT number 9

[  2016.907] (EE) open /dev/dri/card0: No such file or directory

-Jin