TC 16+ Xorg does not see layout changes

[aus9]

Once you have the  correct setting you know how to test for....try create
/etc/modprobe.d/drm.conf perm 644
contents
options drm debug=something

add etc/modprobe.d/drm.conf to your /opt/.filetool.lst

remove the blacklist ....the file under .X.d and the .local/bin/drmconfig file

[andyj]

I tried the debug thing, I didn't get what I wanted:

Code: [Select]

tc@box:~$ cat /etc/modprobe.conf
# /etc/modprobe.conf: Modprobe config file.
#
options drm debug=0x1b7
tc@box:~$ sudo cat /sys/module/drm/parameters/debug
0
What am I doing wrong here?

What I thought I was showing with this is that the parameter set (or not in this case) in modprobe.conf was not being picked up by modprobe. I apologize for the confusion. My question still stands, why isn't modprobe picking up the parameter in modprobe.conf?

[andyj]

One thing that would be nice is if there was a way to run ~/.setbackground whenever the display resolution changes. Is it possible to set up a trigger for this?

I'm using a gradient set in ~/.setbackground:

Code: [Select]

#!/bin/sh
hsetroot  -add "#1B79B8" -add "#AF77CC" -gradient 0
[ $(which wbar.sh) ] && wbar.sh

It would be nice if I could cause this or something like this to run when the resolution changes so I don't get a tiled gradient. It might be helpful if when the wallpaper dialog creates this script that it insert a second line something like "# Created by TC Wallpaper app date/time"

[andyj]

Some pressure testing blew a gasket. After a few cycles of the monitors FLWM just went away. I didn't find a dump anywhere. This got me thinking that the dialog moving issue isn't from vmware_drv but from flwm not liking all the resolution changes. Any way to start flwm with debug or tracing?

[Juanito]

Much better. But...

libxatracker is from the last version of mesa to support it - mesa-24.1.7 - (the xatracker code in mesa was supplied by vmware)

xf86-video-vmware is from https://gitlab.freedesktop.org/xorg/driver/xf86-video-vmware last (cosmetic) commit 25/07/12

i.e. it's not going to get any better than that for the moment - would you like me to post the extensions, or would you like to continue testing?

[andyj]

I've made a lot of hand changes, running tce-update and seeing if it continues to work would be the next logical test. Let's post it to TC 16 and 17 and once it hits my mirror I try it.

[Juanito]

posted to tc-16.x/17.x x86_64 repos

I'll look at x86 once we've finished testing this.

[andyj]

In 17.1 64-bit  libxatracker is built against llvm19, but llvm22 seems to be the new norm. Xorg crashes with vmware_drv.so apparently because it's using both versions. Can libxtracker get updated? I haven't tried 32-bit yet.

[Juanito]

libxatracker will not build against llvm22 and, since it is depreciated since mesa-24.1.7, there's not much hope of a fix.

As per:

Switch to the Modesetting Driver: For systems using the X.Org Server, replace xf86-video-vmware with the generic modesetting driver. The underlying Linux kernel DRM driver (vmwgfx) remains fully active and perfectly supports the default modesetting driver.

..and:

Code: [Select]

cat /usr/local/share/X11/xorg.conf.d/10-monitor.conf
Section "Device"
    Identifier "VirtualBox GPU"
    Driver "modesetting"
    Option "AccelMethod" "glamor"
EndSection
Does the modesetting driver work for you?