Talk:ATI

The generic modesetting driver

We should also mention the generic modesetting driver. For my card (HD6570), this driver outperforms the ATI driver (I have tested it with glxgears, gtkperf and Unigene Valley) and some benchmarks available on the web seems to go in the same direction. The generic driver gives 2D acceleration via glamor and the 3D mesa libraries; 3D acceleration is given by the Mesa libraries. It is not clear that the modesetting driver is better under all circumstances but it is a "real" driver that is worth considering.

—This unsigned comment is by Olive (talk) 07:08, 6 October 2016‎. Please sign your posts with ~~~~!

Turn vsync off

Latest comment: 1 February 20171 comment1 person in discussion

driver="dri2" works both with DRI2 and DRI3. Also I would suggest changing vblank_mode to 1, because 0 is "force disable" and 1 is "disable by default", which seems more correct to me.

—This unsigned comment is by Equeim (talk) 19:55, 12 December 2016‎. Please sign your posts with ~~~~!

You are completely right, this section should be edited, there's no need for "Reason: Is this still valid with DRI3? (which is default)", I will be free to remove it since it works on all drivers with DRI3 (nouveau, radeon etc.). You are also right about vblank_mode, but I've tested it just now, and it should stay 0 because some applications may refuse to disable it when it's "by default" (such as Chromium/Chrome).

However, there is something with mutter/clutter on Gnome-Shell/Cinnamon/Budgie etc. that makes browsers behave weird if it's set to 0, with 1, behaviour is as expected, so maybe we should add that as an note or added section? Here is bug explained: https://bugs.freedesktop.org/show_bug.cgi?id=99418

I would add notice for Gnome-Shell (mutter/clutter based WM), but I need second opinion. Lpr (talk) 22:36, 1 February 2017 (UTC)Reply[reply]

Wayland requires initramfs?

The recent problem with GDM (https://bbs.archlinux.org/viewtopic.php?id=231381) forced me to do some tests by starting GDM from the command line. That bug is now fixed but what I found out was that GDM/Gnome starts in Wayland mode only if I start GDM from the command line ("start"). When I start it in boot ("enable") it always starts in x11 mode.

This made no sense at first but then I thought maybe there is something missing in early starting of GDM. So I added amdgpu/radeon to /etc/mkinitcpio.conf and now Gnome always starts in Wayland mode (GDM should start in Wayland mode by default). There are some differences with Wayland vs. x11: Wayland mode has less animations in window maximizing/restore so I can't really say which one is the "correct" one for my AMD A10 7850K integrated graphics.

—This unsigned comment is by Beoldhin (talk) 07:04, 1 November 2017‎. Please sign your posts with ~~~~!