[opensuse-factory] How to test modesetting driver in TW
Dear all, I just read that ubuntu and debian are switching to the modesetting driver in favor of the intel-driver. Now, I am wondering how to test the modesetting driver in TW and how to check which driver is actually used here? Kind regards, Robby.
On 01.08.2016 19:58, Robby Engelmann wrote:
Dear all,
I just read that ubuntu and debian are switching to the modesetting driver in favor of the intel-driver. Now, I am wondering how to test the modesetting driver in TW and how to check which driver is actually used here?
Kind regards, Robby.
Same as everwhere, I assume: set 'Driver "modesetting"' in /etc/X11/xorg.conf.d/50-device.conf and restart X. However, "modesetting" is quite bad for radeon cards with multiple monitors, at least for me. I have no idea what hacks they use to automatically replace only intel driver with it, maybe just not installing it is sufficient.
is this enough?: Section "Device" Identifier "intel" Driver "modesetting" EndSection On Montag, 1. August 2016 20:19:08 CEST Sergey Kondakov wrote:
On 01.08.2016 19:58, Robby Engelmann wrote:
Dear all,
I just read that ubuntu and debian are switching to the modesetting driver in favor of the intel-driver. Now, I am wondering how to test the modesetting driver in TW and how to check which driver is actually used here?
Kind regards, Robby.
Same as everwhere, I assume: set 'Driver "modesetting"' in /etc/X11/xorg.conf.d/50-device.conf and restart X. However, "modesetting" is quite bad for radeon cards with multiple monitors, at least for me. I have no idea what hacks they use to automatically replace only intel driver with it, maybe just not installing it is sufficient.
On 01.08.2016 20:39, Robby Engelmann wrote:
is this enough?:
Section "Device" Identifier "intel" Driver "modesetting" EndSection
On Montag, 1. August 2016 20:19:08 CEST Sergey Kondakov wrote:
On 01.08.2016 19:58, Robby Engelmann wrote:
Dear all,
I just read that ubuntu and debian are switching to the modesetting driver in favor of the intel-driver. Now, I am wondering how to test the modesetting driver in TW and how to check which driver is actually used here?
Kind regards, Robby.
Same as everwhere, I assume: set 'Driver "modesetting"' in /etc/X11/xorg.conf.d/50-device.conf and restart X. However, "modesetting" is quite bad for radeon cards with multiple monitors, at least for me. I have no idea what hacks they use to automatically replace only intel driver with it, maybe just not installing it is sufficient.
I don't know. You tell us ;) I hope you are able to deal with broken X and have nice console text editor, in case anything goes wrong. I also just read that for modesetting driver to be automatically activated for any hardware with "missing" "native" one, packages xorg-x11-driver-video, xf86-video-vesa and xf86-video-fbdev are also should be deleted because vesa and fbdev are both generic drivers and have higher priority than modesetting. But you don't need to do that.
That's exactly my problem. I am not sure, how to force modesetting driver. I guess that the entry in xorg.conf is not enough. However, I can also not figure out, how to check which driver is actually used. On Montag, 1. August 2016 22:52:28 CEST Sergey Kondakov wrote:
On 01.08.2016 20:39, Robby Engelmann wrote:
is this enough?:
Section "Device" Identifier "intel" Driver "modesetting" EndSection
On Montag, 1. August 2016 20:19:08 CEST Sergey Kondakov wrote:
On 01.08.2016 19:58, Robby Engelmann wrote:
Dear all,
I just read that ubuntu and debian are switching to the modesetting driver in favor of the intel-driver. Now, I am wondering how to test the modesetting driver in TW and how to check which driver is actually used here?
Kind regards, Robby.
Same as everwhere, I assume: set 'Driver "modesetting"' in /etc/X11/xorg.conf.d/50-device.conf and restart X. However, "modesetting" is quite bad for radeon cards with multiple monitors, at least for me. I have no idea what hacks they use to automatically replace only intel driver with it, maybe just not installing it is sufficient.
I don't know. You tell us ;) I hope you are able to deal with broken X and have nice console text editor, in case anything goes wrong.
I also just read that for modesetting driver to be automatically activated for any hardware with "missing" "native" one, packages xorg-x11-driver-video, xf86-video-vesa and xf86-video-fbdev are also should be deleted because vesa and fbdev are both generic drivers and have higher priority than modesetting. But you don't need to do that.
On 01.08.2016 22:56, Robby Engelmann wrote:
That's exactly my problem. I am not sure, how to force modesetting driver. I guess that the entry in xorg.conf is not enough. However, I can also not figure out, how to check which driver is actually used.
On Montag, 1. August 2016 22:52:28 CEST Sergey Kondakov wrote:
On 01.08.2016 20:39, Robby Engelmann wrote:
is this enough?:
Section "Device" Identifier "intel" Driver "modesetting" EndSection
On Montag, 1. August 2016 20:19:08 CEST Sergey Kondakov wrote:
On 01.08.2016 19:58, Robby Engelmann wrote:
Dear all,
I just read that ubuntu and debian are switching to the modesetting driver in favor of the intel-driver. Now, I am wondering how to test the modesetting driver in TW and how to check which driver is actually used here?
Kind regards, Robby.
Same as everwhere, I assume: set 'Driver "modesetting"' in /etc/X11/xorg.conf.d/50-device.conf and restart X. However, "modesetting" is quite bad for radeon cards with multiple monitors, at least for me. I have no idea what hacks they use to automatically replace only intel driver with it, maybe just not installing it is sufficient.
I don't know. You tell us ;) I hope you are able to deal with broken X and have nice console text editor, in case anything goes wrong.
I also just read that for modesetting driver to be automatically activated for any hardware with "missing" "native" one, packages xorg-x11-driver-video, xf86-video-vesa and xf86-video-fbdev are also should be deleted because vesa and fbdev are both generic drivers and have higher priority than modesetting. But you don't need to do that.
Ah, just do a thing and see what happens, read /var/log/Xorg.0.log and Xorg.0.log.old (from previous X launch). Read up on Arch and Gentoo wiki pages, they are usually the most complete. Like https://wiki.archlinux.org/index.php/xorg
On lundi, 1 août 2016 23.53:28 h CEST Sergey Kondakov wrote:
On 01.08.2016 22:56, Robby Engelmann wrote:
That's exactly my problem. I am not sure, how to force modesetting driver. I guess that the entry in xorg.conf is not enough. However, I can also not figure out, how to check which driver is actually used.> On Montag, 1. August 2016 22:52:28 CEST Sergey Kondakov wrote:
On 01.08.2016 20:39, Robby Engelmann wrote:
is this enough?:
Section "Device" Identifier "intel" Driver "modesetting" EndSection
On Montag, 1. August 2016 20:19:08 CEST Sergey Kondakov wrote:
On 01.08.2016 19:58, Robby Engelmann wrote:
Dear all,
I just read that ubuntu and debian are switching to the modesetting driver in favor of the intel-driver. Now, I am wondering how to test the modesetting driver in TW and how to check which driver is actually used here?
Kind regards, Robby.
Same as everwhere, I assume: set 'Driver "modesetting"' in /etc/X11/xorg.conf.d/50-device.conf and restart X. However, "modesetting" is quite bad for radeon cards with multiple monitors, at least for me. I have no idea what hacks they use to automatically replace only intel driver with it, maybe just not installing it is sufficient.
I don't know. You tell us ;) I hope you are able to deal with broken X and have nice console text editor, in case anything goes wrong.
I also just read that for modesetting driver to be automatically activated for any hardware with "missing" "native" one, packages xorg-x11-driver-video, xf86-video-vesa and xf86-video-fbdev are also should be deleted because vesa and fbdev are both generic drivers and have higher priority than modesetting. But you don't need to do that.
Ah, just do a thing and see what happens, read /var/log/Xorg.0.log and Xorg.0.log.old (from previous X launch). Read up on Arch and Gentoo wiki pages, they are usually the most complete. Like https://wiki.archlinux.org/index.php/xorg
the simple thing is zypper al xf86-video-* then you will be able to have modesetting, btw say good bye to dpms support, hidpi, multiple screen etc ... ;-) -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 02.08.2016 00:20, Bruno Friedmann wrote:
On lundi, 1 août 2016 23.53:28 h CEST Sergey Kondakov wrote:
On 01.08.2016 22:56, Robby Engelmann wrote:
That's exactly my problem. I am not sure, how to force modesetting driver. I guess that the entry in xorg.conf is not enough. However, I can also not figure out, how to check which driver is actually used.> On Montag, 1. August 2016 22:52:28 CEST Sergey Kondakov wrote:
On 01.08.2016 20:39, Robby Engelmann wrote:
is this enough?:
Section "Device" Identifier "intel" Driver "modesetting" EndSection
On Montag, 1. August 2016 20:19:08 CEST Sergey Kondakov wrote:
On 01.08.2016 19:58, Robby Engelmann wrote: > Dear all, > > I just read that ubuntu and debian are switching to the modesetting > driver > in favor of the intel-driver. > Now, I am wondering how to test the modesetting driver in TW and how > to > check which driver is actually used here? > > Kind regards, > Robby.
Same as everwhere, I assume: set 'Driver "modesetting"' in /etc/X11/xorg.conf.d/50-device.conf and restart X. However, "modesetting" is quite bad for radeon cards with multiple monitors, at least for me. I have no idea what hacks they use to automatically replace only intel driver with it, maybe just not installing it is sufficient.
I don't know. You tell us ;) I hope you are able to deal with broken X and have nice console text editor, in case anything goes wrong.
I also just read that for modesetting driver to be automatically activated for any hardware with "missing" "native" one, packages xorg-x11-driver-video, xf86-video-vesa and xf86-video-fbdev are also should be deleted because vesa and fbdev are both generic drivers and have higher priority than modesetting. But you don't need to do that.
Ah, just do a thing and see what happens, read /var/log/Xorg.0.log and Xorg.0.log.old (from previous X launch). Read up on Arch and Gentoo wiki pages, they are usually the most complete. Like https://wiki.archlinux.org/index.php/xorg
the simple thing is zypper al xf86-video-* then you will be able to have modesetting, btw say good bye to dpms support, hidpi, multiple screen etc ... ;-)
1) What package lock have to do with anything ? It only would prevent updates of X server. 2) If you meant deleting all the drivers... might as well suggest striking monitor with a hammer. 3) If modesetting wouldn't support DPMS then why it would have DPMS-fixing patches and log lines of 'modeset(0): DPMS enabled' ? https://patchwork.freedesktop.org/patch/66272/ https://www.linuxquestions.org/questions/linux-hardware-18/xorg-modesetting-... 4) What is this "hidpi" which supposedly is unsupported ? Because the DPI of X screen seem to depend only on resolution and hardware size of the panel which it supposed to provide them via EDID, driver should be irrelevant. The only problem is that X screws up its calculations on multi-monitor setups even with "native" drivers. Probably doesn't even try to set DPI independently. X's DPI settings generally suck, and so does multi-screen colour correction. 5) `man modesetting`: "RandR 1.2 is supported." It even supports "ZaphodHeads", non-RandR dual-head. In theory. X's multiscreen is also generally sucks because of obsession with screen cloning from laptops to projectors and, now, multi-panel screen-walls. Apparently, no one needs simple multi-monitor "multiple real desktops" setup that doesn't suck.
Robby Engelmann composed on 2016-08-01 16:58 (UTC+0200):
I just read that ubuntu and debian are switching to the modesetting driver in favor of the intel-driver. Now, I am wondering how to test the modesetting driver in TW
As an alternative to driver specification via xorg.con* as provided by others in this thread, Egbert Eich implemented a new-for-TW alternative one might find less cumbersome. I have no idea what doc does or should contain a proper explanation of it, but you should be able to figure out /etc/X11/xorg_pci_ids/ from: https://bugzilla.opensuse.org/show_bug.cgi?id=972126#c6 If you can't, let me know and I'll do more digging on my to and fro with Egbert, who implemented it this past winter.
and how to check which driver is actually used here?
Xorg.#.log has numerous mostly sequential entries that will early include intel(0), radeon(0), nouveau(0), etc. according to the driver used. The modesetting driver in server <1.17.x will read modesetting(0), while in server >1.16.x (1.18.x in TW currently) it will read modeset(0). -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (4)
-
Bruno Friedmann
-
Felix Miata
-
Robby Engelmann
-
Sergey Kondakov