I use system with former sever board Supermicro X9SCL-F, with buil-in Matrox G200ew gaphics card, on Fedora 38. It has

file with defaults in the path:

One of rules in the file is:

This disables Wayland and forces xorg to run when defined Matrox device is detected. It is not possible to turn off the built-in Matrox G200ew in BIOS. Then even if PCIe graphics is installed the Matrox is still active, detected during system boot and disables Wayland.

How can I properly override the rule? By 'proper' I mean without editing the default rules file or shadowing it by file with same name under:

to avoid any problems after upgrades?

Hi, I'm not a slack user but can you use "modeset" to ban or promote a particular module for the kernel to use?

then wayland and X11 have no choice.

on the kernel command line, use e to edit...

modeset.<module-name>=0 to ban, eg.(matrox) I use this one to ban nouveau
modeset.<module-name>=1 to promote, eg.(nvidia)

if this works for you after testing, write it into your /etc/default/grub file so it is included each time the kernel is changed.

I hope this helps you.

How often do yo expect the default rule to get changed such that it breaks your override ?. Should be pretty obvious if it does happen.

Well this is not the case here. What udev is doing here is looking for the existence of particular device by its vendor id and device id and do not care if its functional by working kernel driver or not. What you referring to is just blacklisting the kernel driver preventing the device from using some part of its capabilities like higher resolutions etc. But the device is still listed and discovered by udev even when driver is not loaded.

By the way, to disable the driver you should add to kernel parameters parameter in this format:

Actually you can never be sure what update and in what extents will appear and be applied. This is the danger. Some more details can be found in this answer: https://stackoverflow.com/a/73661279/2968398

1 members found this post helpful.

Yes, I wondered if that thread prompted your concern. You should be aware of what changes are going into your system(s). Fedora doesn't blindly update /etc - maybe you should investigate rpmconf, although I've never used it; I hand check the rpm{save,new} files directly.
Later: oops, that's not what you're concerned about is it ... FWIW, I don't recall any over-rides of mine being regressed silently.