002-xorg module updated -> Xorg 1.19 + Mesa 17 + xf86plugins

Post#1 by **fulalas** » 22 Feb 2017, 06:28

I've been playing with 002-xorg module these days because I was having serious text artifact when using an Intel HD KabyLake GPU, as you can see here:

After finally succeeded updating Xorg server to 1.19.1v, Mesa to 17.0v and xf86plugins (all got from Slackware official FTP), I've managed to get rid of all artifacts. So if anyone is passing through any similar problem or is just curious about the updates, here is a link for the updated 002-xorg xzm module:

http://www.mediafire.com/file/bf5zgj14i ... x86_64.xzm
(90mb)

Considering this, maybe it's time for Porteus to update these libs (together with NetworkManager and FFMpeg) on the next version. What you think?

Post#2 by **Evan** » 22 Feb 2017, 07:03

Post#3 by **ztealmax** » 23 Feb 2017, 18:54

Couldnt get keyboard or mouse working with this package im affraid

Post#4 by **fulalas** » 24 Feb 2017, 01:05

ztealmax, can you try booting on Always Fresh mode? I tested this 002-xorg module with a desktop and a laptop and it worked flawlessly.

Post#5 by **Blaze** » 24 Feb 2017, 10:30

ztealmax wrote:Couldnt get keyboard or mouse working with this package im affraid

Confirm. I tried Xorg 1.19 + Mesa 17 + xf86plu in Always Fresh mode, but keyboard and mouse not functional.

Post#6 by **ztealmax** » 24 Feb 2017, 17:27

Blaze wrote:
ztealmax wrote:Couldnt get keyboard or mouse working with this package im affraid
Confirm. I tried Xorg 1.19 + Mesa 17 + xf86plu in Always Fresh mode, but keyboard and mouse not functional.

Also confirm the same

Post#7 by **fulalas** » 25 Feb 2017, 00:19

It's weird. I had this bug once but I though I managed to solve it. Maybe I've uploaded the buged version

I'll check!

Post#8 by **fulalas** » 25 Feb 2017, 01:23

OK, I confirmed the bug with official XFCE module, so now I see how to solve this issue. You need to update libxcb to 1.12 and all xcb modules inside your 003 module:

Code: Select all

xcb-proto-1.12-x86_64-1.txz
xcb-util-0.4.0-x86_64-2.txz
xcb-util-cursor-0.1.3-x86_64-1.txz
xcb-util-errors-1.0-x86_64-1.txz
xcb-util-image-0.4.0-x86_64-2.txz
xcb-util-keysyms-0.4.0-x86_64-2.txz
xcb-util-renderutil-0.3.9-x86_64-2.txz
xcb-util-wm-0.4.1-x86_64-2.txz

source: ftp://ftp.slackware.com/pub/slackware/s ... kware64/x/

In the meantime you can test it with this build of LXQt and see if it works for you, as for me it works on two different machines:
http://www.mediafire.com/file/esfvvlyyu ... 282%29.xzm

Post#9 by **ztealmax** » 25 Feb 2017, 09:54

Thank you, i did try it and it started as it should, but framerate ingame was terrible 4fps guess i need to get amdgpu-pro working anyway

Thank you for getting these working

SIncerally
M

Post#10 by **fulalas** » 26 Feb 2017, 11:52

We should look for Mesa 17.1. Look how it evolved, most of the time being faster than AMD official drivers!

http://www.phoronix.com/scan.php?page=a ... x470&num=2

Post#11 by **ztealmax** » 26 Feb 2017, 15:57

fulalas wrote:We should look for Mesa 17.1. Look how it evolved, most of the time being faster than AMD official drivers!

http://www.phoronix.com/scan.php?page=a ... x470&num=2

agree think this might the only right way to go

M

Post#12 by **ztealmax** » 26 Feb 2017, 16:57

fulalas wrote:OK, I confirmed the bug with official XFCE module, so now I see how to solve this issue. You need to update libxcb to 1.12 and all xcb modules inside your 003 module:
Code: Select all
xcb-proto-1.12-x86_64-1.txz
xcb-util-0.4.0-x86_64-2.txz
xcb-util-cursor-0.1.3-x86_64-1.txz
xcb-util-errors-1.0-x86_64-1.txz
xcb-util-image-0.4.0-x86_64-2.txz
xcb-util-keysyms-0.4.0-x86_64-2.txz
xcb-util-renderutil-0.3.9-x86_64-2.txz
xcb-util-wm-0.4.1-x86_64-2.txz
source: ftp://ftp.slackware.com/pub/slackware/s ... kware64/x/

In the meantime you can test it with this build of LXQt and see if it works for you, as for me it works on two different machines:
http://www.mediafire.com/file/esfvvlyyu ... 282%29.xzm

tried to update 003-lxde. with these modules still same problem, but i might be doing things wrong

Link to my lxde https://www.dropbox.com/s/8949yxstl2hwo ... e.xzm?dl=0

Post#13 by **brokenman** » 26 Feb 2017, 17:45

After finally succeeded updating Xorg server to 1.19.1v, Mesa to 17.0v and xf86plugins (all got from Slackware official FTP), I've managed to get rid of all artifacts. So if anyone is passing through any similar problem or is just curious about the updates, here is a link for the updated 002-xorg xzm module:

http://www.mediafire.com/file/u7uo80cqb ... 2-xorg.xzm
(86mb)

Considering this, maybe it's time for Porteus to update these libs (together with NetworkManager and FFMpeg) on the next version. What you think?

Porteus-3.2.2 is based on slackware-14.2. We follow the package versions in this version because they have been tested and known to be stable. Here is what mesa's own website has to say.

Mesa 17.0.0 is a new development release. People who are concerned with stability and reliability should stick with a previous release or wait for Mesa 17.0.1.

Please note that at home I am running mesa v17 and Xorg-server-1.19.1 as testing.

Post#14 by **fulalas** » 26 Feb 2017, 22:55

ztealmax, I'll take a look at your LXDE module and see what I can do.

brokenman, I see and agree with you. So let's wait until Slackware moves to the new version. No problem

BTW, how is your tests with new Mesa/Xorg going?

Post#15 by **fulalas** » 27 Feb 2017, 02:00

ztealmax, try this lxde module (I've updated some libs): http://www.mediafire.com/file/z50a2bp8p ... 3-lxde.xzm

Porteus