002-xorg -> Xorg 1.19.3 + Mesa 17.1.0 + plugins

Here is a place for your projects which are not officially supported by the Porteus Team. For example: your own kernel patched with extra features; desktops not included in the standard ISO like Gnome; base modules that are different than the standard ISO, etc...
Post Reply
fulalas
DEV Team
DEV Team
Posts: 838
Joined: 26 Oct 2016, 15:34
Distribution: Porteus
Location: Brazil

002-xorg -> Xorg 1.19.3 + Mesa 17.1.0 + plugins

Post#1 by fulalas » 17 May 2017, 05:49

This is a full 002-xorg module with the following updates (when compared to the module that comes with Porteus 3.2.2):

xorg server -> 1.19.3
mesa -> 17.1.0
xf86 video plugins -> last Slackware update (May 17th)
xf86 input plugins -> last Slackware update (May 17th)
libvdpau -> 1.1.1
libva -> 1.8.0
libva-intel -> 1.7.3

Also, I updated Porteus script that creates xzm modules through context menu. Now it's compressing just like dir2xzm script (i.e. more). :)

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

raja
Black ninja
Black ninja
Posts: 65
Joined: 02 May 2017, 09:51
Distribution: v3.2.2-32bit and v3.2.2-64 bit
Location: Chennai,India

002-xorg -> Xorg 1.19.3 + Mesa 17.1.0 + plugins

Post#2 by raja » 26 Sep 2017, 09:13

I tried this module once long back, it threw up many errors, and did not boot up to the desktop.

Any one else is using this module in Porteus 3.2.2,64 bit, original installation without any additions/modifications? I would like to try again on confirmation.

Thanks.

raja
Black ninja
Black ninja
Posts: 65
Joined: 02 May 2017, 09:51
Distribution: v3.2.2-32bit and v3.2.2-64 bit
Location: Chennai,India

002-xorg -> Xorg 1.19.3 + Mesa 17.1.0 + plugins

Post#3 by raja » 30 Sep 2017, 10:25

Tried with LXDE desk top.Boots without showing any error messages. But no mouse or keyboard inputs are available. I have seen this Xorg behaviour when you unpack 002 and do some additions/deletions.

Any solution please?

fulalas
DEV Team
DEV Team
Posts: 838
Joined: 26 Oct 2016, 15:34
Distribution: Porteus
Location: Brazil

002-xorg -> Xorg 1.19.3 + Mesa 17.1.0 + plugins

Post#4 by fulalas » 30 Sep 2017, 20:26

@raja, try with together with this module: https://www.dropbox.com/s/ypim23oqbedfu ... 7.xzm?dl=1

It has an updated version of libinput and libwacom. :good:

raja
Black ninja
Black ninja
Posts: 65
Joined: 02 May 2017, 09:51
Distribution: v3.2.2-32bit and v3.2.2-64 bit
Location: Chennai,India

002-xorg -> Xorg 1.19.3 + Mesa 17.1.0 + plugins

Post#5 by raja » 01 Oct 2017, 10:04

Fulala,Thanks for the updated input drivers. Problem solved. Perfect boot. Your module replaces the original,hereafter. :)

Code: Select all

13.663] (II) LoadModule: "libinput"
[    13.664] (II) Loading /usr/lib64/xorg/modules/input/libinput_drv.so
[    13.709] (II) Module libinput: vendor="X.Org Foundation"
[    13.709] 	compiled for 1.19.3, module version = 0.25.1
[    13.709] 	Module class: X.Org XInput Driver
[    13.709] 	ABI class: X.Org XInput driver, version 24.1

fulalas
DEV Team
DEV Team
Posts: 838
Joined: 26 Oct 2016, 15:34
Distribution: Porteus
Location: Brazil

002-xorg -> Xorg 1.19.3 + Mesa 17.1.0 + plugins

Post#6 by fulalas » 01 Oct 2017, 20:14

Cool :)

raja
Black ninja
Black ninja
Posts: 65
Joined: 02 May 2017, 09:51
Distribution: v3.2.2-32bit and v3.2.2-64 bit
Location: Chennai,India

002-xorg -> Xorg 1.19.3 + Mesa 17.1.0 + plugins

Post#7 by raja » 03 Oct 2017, 11:20

As I said earlier,somewhere here, a very modern Laptop with 7th generation Kaby Lake processor and DDR4 memory with very high bandwidth, could not render Full HD videos, where as my old Laptop even while running Porteus 3.1 with openchrome video driver, used to play Full HD videos flawlessly.

The video driver developed by a Hardware man(Open Chrome) could exploit and accelerate hardware to play videos in a slow old hardware.

I was intrigued why even latest versions of Linux and X ORG could not recognize the latest graphic chip Intel HD Graphics 620. Donald's Kodi could use Mesa and Intel open source driver to play Full HD videos where as MPV and Gnome Mplayer failed to do so.

This drove me to try Fulalas latest Xorg+mesa+plugins module. My earlier attempt with XFCE threw up many errors.

Now with JsSouzas LXDE, no errors and booted fine with new input drivers.

Today, in Gnome Mplayer I selected new menu addition for GL3 for Video output, and it played Full HD efforlessly.

Assuming , this could be due to the latest module from Fulalas, I typed glxinfo in the terminal and it confirmed OpenGL availability.

Code: Select all

direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel Open Source Technology Center (0x8086)
    Device: Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2)  (0x5916)
    Version: 17.1.0
    Accelerated: yes
    Video memory: 3072MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 4.5
    Max compat profile version: 3.0
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2) 
OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.1.0
Intel HD Graphics 620 (Kaby Lake GT2 is recognized.

opened Xorg log, and found these new entries,

Code: Select all

13.476] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20161121
[    13.476] (WW) Falling back to old probe method for modesetting
[    13.476] (WW) Falling back to old probe method for vesa
[    13.476] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD Graphics 620
[    13.476] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2, avx, avx2; using a maximum of 2 threads
Again Graphics chipset found its mention here too.

This detailed message is for information.

Thanks all folks for providing latest modules to tackle problems thrown up in latest Hardware.

fulalas
DEV Team
DEV Team
Posts: 838
Joined: 26 Oct 2016, 15:34
Distribution: Porteus
Location: Brazil

002-xorg -> Xorg 1.19.3 + Mesa 17.1.0 + plugins

Post#8 by fulalas » 03 Oct 2017, 20:08

@raja, running videos with GPU assist has little to do with Mesa. You need libva and a good video player with the right flags set (I recommend Mpv, instead of MPlayer). Here's a tutorial: How to watch videos with GPU assistance . Although in this tutorial I recommend using Mpv together with SMPlayer, you can use just Mpv.

raja
Black ninja
Black ninja
Posts: 65
Joined: 02 May 2017, 09:51
Distribution: v3.2.2-32bit and v3.2.2-64 bit
Location: Chennai,India

002-xorg -> Xorg 1.19.3 + Mesa 17.1.0 + plugins

Post#9 by raja » 04 Oct 2017, 11:23

Fulalas, I don't think so. Video driver from Xorg and Mesa must be playing a part. In Porteus 3.1, my old Laptop used to play full HD videos without any problem. In 3.2.2, after a long struggle ,I located a correct openchrome driver and there also both Gnome Player and MPV used to play videos effortlessly, mainly due to the driver.

But in a latest machine, both the players failed, whereas Kodi played the videos and Kodi settings says about Intel open source driver and openGL and Mesa.

Today, I tested Gnome player with video output set at vaapi. No video output as jssouza said. But selecting GL3 output plays the video.

MPV, version 0.17, still fails. I added a config entry for mpv, vo=openGL, fails again.

There is more to this behaviour than we understand. A correct video driver from Xorg for the video chipset concerned, should be okay.

In Linux 4.10.8, dmesg, had this entry for the video capture card, but no driver module has been loaded.

Code: Select all

1.568831] usb 1-2: new high-speed USB device number 3 using xhci_hcd
[    1.739626] usb 1-2: New USB device found, idVendor=1b80, idProduct=a418
[    1.739629] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    1.739631] usb 1-2: Product: Polaris AV Capture
[    1.739633] usb 1-2: Manufacturer: Conexant Corporation
[    1.739635] usb 1-2: SerialNumber: 0000000000
[    1.804698] random: fast init done
So, there is hope.

fulalas
DEV Team
DEV Team
Posts: 838
Joined: 26 Oct 2016, 15:34
Distribution: Porteus
Location: Brazil

002-xorg -> Xorg 1.19.3 + Mesa 17.1.0 + plugins

Post#10 by fulalas » 04 Oct 2017, 20:20

@raja, have you followed the tutorial I sent you? For new Intel HD graphics card you need a newer libva that doesn't come with Porteus 3.2.2.

As long as I understand, libva decodes the video, and it sends the set of pixels to a 2D billboard rendered in OpenGL. So, although the final image is rendered in OpenGL (using Mesa), the hard work is done by libva outside the OpenGL domain. But I may be wrong.

apollo
White ninja
White ninja
Posts: 23
Joined: 28 Oct 2017, 13:40
Distribution: 4.0 XFCE, Manjaro
Location: .bay.de
Contact:

002-xorg -> Xorg 1.19.3 + Mesa 17.1.0 + plugins

Post#11 by apollo » 01 Nov 2017, 16:56

Hi there,

i've put an old Fujitsu-Siemens thinclient (single core amd cpu and amd rs690-based onboard graphics) back to live thanks porteus. I runs quite ok with kernel 4.13.5 and xfce.
Thought i could gain a bit better performance with an updated mesa cause from what i've heard about the last time they managed to improve performance of amd hardware greatly. So i tried the new xorg-module in combination with the updated libinput-module. Booting in always-fresh mode to xfce-desktop without any problems, but the output of glxinfo took me to the conclusion that something might be wrong:

With "old" Mesa 11.2.2:

Code: Select all

...
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: X.Org R300 Project (0x1002)
    Device: ATI RS690 (0x791f)
    Version: 11.2.2
    Accelerated: yes
    Video memory: 128MB
    Unified memory: no
    Preferred profile: compat (0x2)
    Max core profile version: 0.0
    Max compat profile version: 2.1
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 2.0
OpenGL vendor string: X.Org R300 Project
OpenGL renderer string: Gallium 0.4 on ATI RS690
OpenGL version string: 2.1 Mesa 11.2.2
OpenGL shading language version string: 1.20
...
with updated mesa-lib:

Code: Select all

name of display: :0.0
Error: couldn't find RGB GLX visual or fbconfig
any hint what might be wrong? I have not yet tried the older Mesa 17.0-packages provided by fulalas.

addition:
runs perfect on my old thinkpad t510 with i7-620m apu :)

apollo

fulalas
DEV Team
DEV Team
Posts: 838
Joined: 26 Oct 2016, 15:34
Distribution: Porteus
Location: Brazil

002-xorg -> Xorg 1.19.3 + Mesa 17.1.0 + plugins

Post#12 by fulalas » 01 Nov 2017, 20:23

@apollo, maybe you can try to manually convert the new Mesa to a xzm module and see if it works out of the box: http://ftp.slackware.com/pub/slackware/ ... 6_64-1.txz

You also probably need to update xf86 video for AMD: http://ftp.slackware.com/pub/slackware/ ... 6_64-1.txz

If it doesn't work, I believe you'll have to wait a little bit until we release Porteus 4 -- which is almost there, I believe. :)

apollo
White ninja
White ninja
Posts: 23
Joined: 28 Oct 2017, 13:40
Distribution: 4.0 XFCE, Manjaro
Location: .bay.de
Contact:

002-xorg -> Xorg 1.19.3 + Mesa 17.1.0 + plugins

Post#13 by apollo » 01 Nov 2017, 20:33

@fulalas
thanks for your reply.

I've digged a bit further into the issue, according to Xorg.0.log loading of some shared objects fails:

Code: Select all

...
[    38.889] (II) LoadModule: "fbdev"
[    38.892] (WW) Warning, couldn't open module fbdev
[    38.892] (II) UnloadModule: "fbdev"
[    38.892] (II) Unloading fbdev
[    38.892] (EE) Failed to load module "fbdev" (module does not exist, 0)
...
[    39.094] (EE) AIGLX error: dlopen of /usr/lib64/xorg/modules/dri/r300_dri.so failed (libLLVM-4.0.so: cannot open shared object file: No such file or directory)
[    39.094] (EE) AIGLX: reverting to software rendering
[    39.109] (EE) AIGLX error: dlopen of /usr/lib64/xorg/modules/dri/swrast_dri.so failed (libLLVM-4.0.so: cannot open shared object file: No such file or directory)
[    39.109] (EE) GLX: could not load software renderer
[    39.109] (II) GLX: no usable GL providers found for screen 0
...
From my point of view, all required files are there:

Code: Select all

-rwxr-xr-x 1 root  root   96944 Mar 15  2017 libexa.so*
-rwxr-xr-x 1 root  root  146416 Mar 15  2017 libfb.so*
-rwxr-xr-x 1 root  root   18624 Mar 15  2017 libfbdevhw.so*
-rwxr-xr-x 1 root  root  208952 Mar 15  2017 libglamoregl.so*
-rwxr-xr-x 1 root  root  146088 Mar 15  2017 libint10.so*
-rwxr-xr-x 1 root  root   34944 Mar 15  2017 libshadow.so*
-rwxr-xr-x 1 root  root   10336 Mar 15  2017 libshadowfb.so*
-rwxr-xr-x 1 root  root   26992 Mar 15  2017 libvbe.so*
-rwxr-xr-x 1 root  root   31808 Mar 15  2017 libvgahw.so*
-rwxr-xr-x 1 root  root  187376 Mar 15  2017 libwfb.so*
I'll give the modules you mentioned a try...but not today. ;)

Can't wait to see Porteus 4.0... :Yahoo!:

fulalas
DEV Team
DEV Team
Posts: 838
Joined: 26 Oct 2016, 15:34
Distribution: Porteus
Location: Brazil

002-xorg -> Xorg 1.19.3 + Mesa 17.1.0 + plugins

Post#14 by fulalas » 01 Nov 2017, 21:12

Hmmm! So maybe you just need LLVM 4: http://slackmirror.cbpf.br/pub/slackwar ... 6_64-1.txz

Post Reply