Bugzilla – Bug 441404
No longer run SaX2 during installation, i.e. get rid of xorg.conf
Last modified: 2021-03-09 12:00:58 UTC
A static configuration of resolution (Screen section), monitor sync values (Monitor section) and driver entry (Device section) avoids dynamic changes in display configuration. SaX2 no longer writing these sections would allow to have such changes configured automatically. Xserver probes for the right driver, driver probes for the monitor(s) and selects the native resolution(s) of the monitor(s). The alignment of several monitors can be done on-the-fly with your favorite RANDR >= 1.2 tool (xrandr, krandrtry, gnome-display-properties). Prerequsite are RANDR >= 1.2 drivers like intel, radeon, radeonhd, nv (G80 only).
*** Bug 433953 has been marked as a duplicate of this bug. ***
*** Bug 440965 has been marked as a duplicate of this bug. ***
I do not get it. How can this be seen as an enhancement if it does not allow me to use my external display, anymore? https://bugzilla.novell.com/440965 Alin
It does. You just need to reconfigure your setup, if you change it.
Stefan if you don't have any monitor screen device sections anymore you don't need sax2 at all. I suggest to spent some time in a new configuration backend. I wrote sax2 in a way which separates the backend from the frontend. In fact the GUI module which is the one you don't want to loose just writes a file /var/lib/sax/apidata which is used by the backend to incorporate the changes into the current configuration I more and more have the feeling that the detection process and all the detailed exceptions from one vendor to the other are now handled by the drivers themselves and doesn't required any configuration information. At least for the newer cards this applies and so the sax2 backend which creates a first suggestion of a configuration file by detecting all these things outside of Xorg seems to become a useless part in the near future I will not allow changes which can be only hacks to the current backend to rip out core sections as of the original design. I'm fine with a new and modern backend while using the existing frontend Thanks
We have bugs like bug #429282, in which xrandr(1) and the graphical tools do not show resolutions that the monitor supports, even though the monitor's EDID data says they are supported. Is the static configuration from sax2 the reason why this happens? If so, what can we do in the 11.1 time-frame (or even SLED11)? [By the way, it made me extremely happy to see from this bug that the plan is to get rid of the static configurations - kudos!]
(In reply to comment #7 from Federico Mena Quintero) > We have bugs like bug #429282, in which xrandr(1) and the graphical tools do > not show resolutions that the monitor supports, even though the monitor's EDID > data says they are supported. Is the static configuration from sax2 the reason > why this happens? It shouldn't. It rather looks like a driver bug. > [By the way, it made me extremely happy to see from this bug that the plan is > to get rid of the static configurations - kudos!] We always wanted to get there ASAP. But no earlier :-P
*** Bug 450130 has been marked as a duplicate of this bug. ***
*** Bug 472604 has been marked as a duplicate of this bug. ***
*** Bug 381024 has been marked as a duplicate of this bug. ***
*** Bug 466003 has been marked as a duplicate of this bug. ***
*** Bug 476478 has been marked as a duplicate of this bug. ***
*** Bug 440973 has been marked as a duplicate of this bug. ***
*** Bug 508534 has been marked as a duplicate of this bug. ***
We just decided to not create any xorg.conf any longer for openSUSE 11.2. Jens-Daniel, we already talked about this option. Mainly this means removing code. Could you take care of that in YaST? AFAIK this is in yast2-x11 (second stage). Not sure about the details. I would like to see this change for Milestone 4. This gives us enough time for testing for the issues, which might arise in Xserver's driver autoconfiguration.
I will remove the x11 setup from the proposal during installation, drop the desktop files and prevent the module from creating an xorg.conf (will be basically the same as for Moblin). Jiri: yast2-country is calling XLib.pm to set language settings. All yast2-x11 interfaces will be deactivated in order to never write an xorg.conf. In the long run yast2-x11 will be dropped. Please adapt your code. Stefan: Do you think we sh/could try to drop yast2-x11 for 11.2 already in a later milestone?
(In reply to comment #20) > Stefan: Do you think we sh/could try to drop yast2-x11 for 11.2 already in a > later milestone? Maybe. Let's wait for the results for next milestone.
(In reply to comment #20) > Jiri: yast2-country is calling XLib.pm to set language settings. All yast2-x11 > interfaces will be deactivated in order to never write an xorg.conf. > In the long run yast2-x11 will be dropped. Please adapt your code. It is used in 2 cases: 1. when YaST fails to read current keyboard settings (e.g. sysconfig file is corrupted), it reads the keyboard settings from current X11 configuration using XLib->getXkbLayout. How could I get these settings when XLib is gone? (Looking into it longer, maybe this part won't be needed as it is used on installed system [where X11 keyboard config should be dropped] and during firstboot [when administrator should ensure sysconfig files are correct]) 2. During installation and/or firstboot, YaST sets the keyboard layout via setxkbmap calls. Than, at the end, it saves the layout to xorg.conf using XLib. Do I understand it right that after these features are implemented, the setting done by setxkbmap will stay without explicit writing of xorg?
(In reply to comment #22) > It is used in 2 cases: > > 1. when YaST fails to read current keyboard settings (e.g. sysconfig file is > corrupted), it reads the keyboard settings from current X11 configuration using > XLib->getXkbLayout. How could I get these settings when XLib is gone? Is this fallback really still required? The global keyboard setting is now saved in /usr/share/hal/fdi/policy/20thirdparty/11-keymap.fdi. > (Looking into it longer, maybe this part won't be needed as it is used on > installed system [where X11 keyboard config should be dropped] Correct. This already happened. > and during firstboot [when administrator should ensure sysconfig files are > correct]) Ok. > 2. During installation and/or firstboot, YaST sets the keyboard layout via > setxkbmap calls. Then, at the end, it saves the layout to xorg.conf using > XLib. Do I understand it right that after these features are implemented, the > setting done by setxkbmap will stay without explicit writing of xorg? Exactly. :-) I hope you still write /etc/sysconfig/keyboard:KEYTABLE, do you?
(In reply to comment #23) > Exactly. :-) I hope you still write /etc/sysconfig/keyboard:KEYTABLE, do you? Yes. XLibAPI usage removed from yast2-country-2.18.13. Other packages adapted: yast2-firstboot-2.18.7, yast2-installation-2.18.20.
Thanks, Jiří!
I submitted yast2-x11 version 2.18.0 and yast2-mouse version 2.18.1 to OBS. Just two things left to do: 1) Jiri, please also drop the keyboard.desktop file from yast2-country. 2) Lukas, the installation somehow copies an xorg.conf to the installed system. Could you please make sure that this does not happen. In 11.2 no xorg.conf should be created at all. (FYI: I already disabled the x11 proposal and configuration during installation). ... then please close the bug (I'm on vacation next week). Thanks.
*** Bug 483554 has been marked as a duplicate of this bug. ***
(In reply to comment #26) > 2) Lukas, the installation somehow copies an xorg.conf to the installed system. > Could you please make sure that this does not happen. It does still make sense to copy xorg.conf from installatation to installed system as xorg.conf.install as before, so it can still be used for failsafe boot entry. > In 11.2 no xorg.conf should be created at all. (FYI: I already disabled the x11 > proposal and configuration during installation). This is correct.
(In reply to comment #26) > I submitted yast2-x11 version 2.18.0 and yast2-mouse version 2.18.1 to OBS. > > > Just two things left to do: > > 1) Jiri, please also drop the keyboard.desktop file from yast2-country. yast2-country-2.18.15 > 2) Lukas, the installation somehow copies an xorg.conf to the installed system. > Could you please make sure that this does not happen. In 11.2 no xorg.conf > should be created at all. (FYI: I already disabled the x11 proposal and > configuration during installation). > > ... then please close the bug (I'm on vacation next week). Thanks. I hope I can close it as the other issue seems to be irrelevant (comment 28)
There must have been a misunderstanding. :-( After installing Milestone 5 there are now two xorg.conf files. 1) /etc/X11/xorg.conf.install (content from installation; that's fine!) *and* 2) /etc/X11/xorg.conf (with the same content!). We no longer want the latter. There shouldn't be any xorg.conf any longer right after installation. Thus reopening and reassigning to Lukas as discussed with Jens Daniel.
*** Bug 533586 has been marked as a duplicate of this bug. ***
Any chance to get this fixed for Milestone 7? 1) I would like to avoid bugreports due to fbdev driver being used instead of the native driver. 2) I would like to address bugs, which would be reported if the native instead of fbdev driver would be running.
*** Bug 534151 has been marked as a duplicate of this bug. ***
- Do not copy xorg.conf to installed system anymore (bnc #441404). - yast2-installation-2.18.23
Thanks a bunch!
Well, I'm really sorry for doing this so late. Too much other work.
This is an autogenerated message for OBS integration: This bug (441404) was mentioned in https://build.opensuse.org/request/show/18139 Factory / yast2-x11