Because those distributions offer unstable, testing, and bleeding edge software that is not fully confirmed to be long term stable. A thousand to a billion developers can all do as they please, but Slackware is Slackware. It is not Debian, Arch, LFS, or any other distribution. While we all suggest new things and new ways to do things, the core fundamentals of Slackware, are what they are. Slackware only distributes tested, stable, and sane orders of packages. Even -Current follows a similar trend of test before public release.

Slackware offers a full source package that can be edited, rebuilt, and used to change local-state packages rather than use the default global distribution packages.

This is part of maintaining your system, rebuilding packages to suit your needs on the local level. Unfortunately, not all people understand this.

Something's still missing, the fact that glxinfo freezes and I have to Ctrl-c to stop it and Kodi doesn't start for that very same reason, when I typed kodi at the command prompt, one of the first things it does is some glxinfo thing. Other programs too.

Some file must still be missing.

and they do

of course

and that's why we have a buggy make?
sorry, but Slackware is just made by a human, it's not divine

so it's like all distributions in this point


so the stable packages are not to be used, rather be replaced ...



only if you have no other hobbies

indeed


ReaperX7, I like you enthusiasm, but sometimes it's just s small step to awkward fanboyism

No a4z, it's called uncommon sense. That's why it has been recommended to follow the standard protocols when rebuilding packages, yet when people don't and use non-standard to the distribution methods, and things break, they wonder why people first and foremost recommend using the standard model for that distribution.

It used to be called common sense, but when you have a bunch of fucktarded hipsters running the world into a progressivist hellhole to shitville, common sense ended up dead.

Sorry for the rant, and no offense to New Jersey.

Ok so when I type glxinfo I get:

name of display: :0

and that's it, it's running but not showing anything else, I need to Ctrl-c to stop it.

If I type glxinfo -i I get:

name of display: :0
display: :0 screen: 0
direct rendering: No (-i specified)
server glx vendor string: SGI
server glx version string: 1.4
server glx extensions:
GLX_ARB_create_context, GLX_ARB_create_context_profile,
GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_multisample,
GLX_EXT_create_context_es2_profile, GLX_EXT_framebuffer_sRGB,
GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info,
GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer,
GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig,
GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_swap_control
client glx vendor string: Mesa Project and SGI
client glx version string: 1.4
client glx extensions:
GLX_ARB_create_context, GLX_ARB_create_context_profile,
GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float,
GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample,
GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile,
GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB,
GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info,
GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer,
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control,
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,
GLX_SGIX_visual_select_group, GLX_SGI_make_current_read,
GLX_SGI_swap_control, GLX_SGI_video_sync
GLX version: 1.4
GLX extensions:
GLX_ARB_create_context, GLX_ARB_create_context_profile,
GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB,
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age,
GLX_EXT_create_context_es2_profile, GLX_EXT_framebuffer_sRGB,
GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info,
GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer,
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control,
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,
GLX_SGIX_visual_select_group, GLX_SGI_make_current_read,
GLX_SGI_swap_control, GLX_SGI_video_sync
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD PITCAIRN
OpenGL version string: 1.4 (3.0 Mesa 10.5.4)

and so on, you know it's a long listing.

It does show this: OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD PITCAIRN
OpenGL version string: 1.4 (3.0 Mesa 10.5.4)

which it's suppose to but no direct rendering.

You might have screwed up X using that guy's method to rebuild and reinstall X outside of a SlackBuild script and package.

At this point, I don't know how to help other than trying to remove all parts of Xorg and reinstalling them, or even reinstalling the whole operating system. You can try to remove X, but be careful.

Actually I built it from the slackbuild in the x11 folder from slackware-current and it's the exact same outcome.

What I'll try later is to rebuild mesa but not like it's in the slackware-current slackbuild but how it's configured in linux from scratch.

Yep, that fixed things with the other programs working.

I installed mako:

slpkg -s salix python-mako

Then the configure I used for mesa was:

autoreconf -f -i &&
./configure CFLAGS='-O2' CXXFLAGS='-O2' \
--prefix=/usr \
--sysconfdir=/etc \
--enable-texture-float \
--enable-gles1 \
--enable-gles2 \
--enable-osmesa \
--enable-xa \
--enable-gbm \
--enable-nine \
--enable-debug \
--enable-glx-tls \
--with-egl-platforms="drm,x11" \
--with-gallium-drivers="nouveau,r300,r600,radeonsi,svga,swrast" &&
make -j8

Then I installed mesa-deomos and things seem to be working.

The only thing that still shoots out error is:

glxinfo

name of display: :0
Error: couldn't find RGB GLX visual or fbconfig

glxgears

Error: couldn't get an RGB, Double-buffered visual

Otherwise everthing seems to work fine, going to install
kodi to see if that works, but you see, the other guy's not
at fault at all in fact he should be praised, his script just enabled glamor in
xorg-server which Patrick should have already done by default
for slack-ware current.

I return to say only , i need finally upgrade other packages.


This is only need for kernels 4.X

I need


libdrm updrade to latest
mesa upgrade to 10.6.2
xorg-server 1.17.2 (with enable glamor)

and voila, finally all works , recompiling only xorg 1.16.4 i have issues with chrome (no start)

but now all works fine.


libdrm and mesa, are build using stock slackware slackbuilds and configs.

and xorg server same config as a 1.16.4 but adding --enable-glamor


libdrm nees http://slackbuilds.org/repository/14...ment/valgrind/

or

--disable-valgrind

_________________________

That`s only temporally , kernel 4.2 arrives with support driver amdgpu for lastest amd cards and apus.