[SOLVED] Xorg problem after upgrade in CURRENT x86_64
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I suspect i need a libGL x86_64 but i don't know where it is after the upgrade.
I remember some issues with intel boards on current about a year ago, on kernel 3.10.X I think, but this one seems a xorg issue.
Thanks
X.Org X Server 1.17.2
Release Date: 2015-06-16
[ 4073.774] X Protocol Version 11, Revision 0
[ 4073.775] Build Operating System: Slackware 14.2 Slackware Linux Project
[ 4073.775] Current Operating System: Linux notebook 4.1.6 #1 SMP Fri Aug 21 01:21:18 CDT 2015 x86_64
[ 4073.775] Kernel command line: BOOT_IMAGE=Slackware ro root=801 vt.default_utf8=1
[ 4073.776] Build Date: 20 August 2015 02:00:58AM
[ 4073.777]
[ 4073.777] Current version of pixman: 0.33.2
[ 4073.778] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 4073.778] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 4073.780] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Aug 22 00:16:03 2015
[ 4073.781] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 4073.781] (==) No Layout section. Using the first Screen section.
[ 4073.781] (==) No screen section available. Using defaults.
[ 4073.781] (**) |-->Screen "Default Screen Section" (0)
[ 4073.781] (**) | |-->Monitor "<default monitor>"
[ 4073.781] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 4073.781] (==) Automatically adding devices
[ 4073.781] (==) Automatically enabling devices
[ 4073.781] (==) Automatically adding GPU devices
[ 4073.781] (WW) The directory "/usr/share/fonts/local" does not exist.
[ 4073.781] Entry deleted from font path.
[ 4073.781] (WW) The directory "/usr/share/fonts/CID" does not exist.
[ 4073.781] Entry deleted from font path.
[ 4073.781] (==) FontPath set to:
/usr/share/fonts/TTF,
/usr/share/fonts/OTF,
/usr/share/fonts/Type1,
/usr/share/fonts/misc,
/usr/share/fonts/75dpi/:unscaled,
/usr/share/fonts/100dpi/:unscaled,
/usr/share/fonts/75dpi,
/usr/share/fonts/100dpi,
/usr/share/fonts/cyrillic
[ 4073.781] (==) ModulePath set to "/usr/lib64/xorg/modules"
[ 4073.781] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 4073.781] (II) Loader magic: 0x804e40
[ 4073.781] (II) Module ABI versions:
[ 4073.781] X.Org ANSI C Emulation: 0.4
[ 4073.781] X.Org Video Driver: 19.0
[ 4073.781] X.Org XInput driver : 21.0
[ 4073.781] X.Org Server Extension : 9.0
[ 4073.781] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 4073.783] (--) PCI:*(0:0:2:0) 8086:1616:1028:06ae rev 9, Mem @ 0xf6000000/16777216, 0xe0000000/268435456, I/O @ 0x0000f000/64
[ 4073.783] (II) Open ACPI successful (/var/run/acpid.socket)
[ 4073.783] (II) LoadModule: "glx"
[ 4073.783] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
[ 4073.880] (II) Module glx: vendor="X.Org Foundation"
[ 4073.880] compiled for 1.17.2, module version = 1.0.0
[ 4073.880] ABI class: X.Org Server Extension, version 9.0
[ 4073.880] (==) AIGLX enabled
[ 4073.880] (==) Matched intel as autoconfigured driver 0
[ 4073.880] (==) Matched intel as autoconfigured driver 1
[ 4073.880] (==) Matched modesetting as autoconfigured driver 2
[ 4073.880] (==) Matched fbdev as autoconfigured driver 3
[ 4073.880] (==) Matched vesa as autoconfigured driver 4
[ 4073.880] (==) Assigned the driver to the xf86ConfigLayout
[ 4073.880] (II) LoadModule: "intel"
[ 4073.880] (II) Loading /usr/lib64/xorg/modules/drivers/intel_drv.so
[ 4073.880] (II) Module intel: vendor="X.Org Foundation"
[ 4073.880] compiled for 1.17.2, module version = 2.99.917
[ 4073.880] Module class: X.Org Video Driver
[ 4073.880] ABI class: X.Org Video Driver, version 19.0
[ 4073.880] (II) LoadModule: "modesetting"
[ 4073.880] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
[ 4073.880] (II) Module modesetting: vendor="X.Org Foundation"
[ 4073.880] compiled for 1.17.2, module version = 1.17.2
[ 4073.880] Module class: X.Org Video Driver
[ 4073.880] ABI class: X.Org Video Driver, version 19.0
[ 4073.880] (II) LoadModule: "fbdev"
[ 4073.881] (WW) Warning, couldn't open module fbdev
[ 4073.881] (II) UnloadModule: "fbdev"
[ 4073.881] (II) Unloading fbdev
[ 4073.881] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 4073.881] (II) LoadModule: "vesa"
[ 4073.881] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
[ 4073.881] (II) Module vesa: vendor="X.Org Foundation"
[ 4073.881] compiled for 1.17.2, module version = 2.3.4
[ 4073.881] Module class: X.Org Video Driver
[ 4073.881] ABI class: X.Org Video Driver, version 19.0
[ 4073.881] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
[ 4073.881] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000
[ 4073.881] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100
[ 4073.881] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200, 6200, P6300
[ 4073.881] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 4073.881] (II) VESA: driver for VESA chipsets: vesa
[ 4073.881] (--) using VT number 7
[ 4073.884] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20150327
[ 4073.884] (WW) Falling back to old probe method for modesetting
[ 4073.885] (WW) Falling back to old probe method for vesa
[ 4073.885] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD graphics 5500
[ 4073.885] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2, avx, avx2
[ 4073.885] (II) intel(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 4073.885] (==) intel(0): Depth 24, (--) framebuffer bpp 32
[ 4073.885] (==) intel(0): RGB weight 888
[ 4073.885] (==) intel(0): Default visual is TrueColor
[ 4073.885] (EE)
[ 4073.885] (EE) Backtrace:
[ 4073.885] (EE) 0: /usr/libexec/Xorg (xorg_backtrace+0x49) [0x5816e9]
[ 4073.885] (EE) 1: /usr/libexec/Xorg (0x400000+0x1855c9) [0x5855c9]
[ 4073.885] (EE) 2: /lib64/libpthread.so.0 (0x7f0ce2477000+0x11340) [0x7f0ce2488340]
[ 4073.885] (EE)
[ 4073.885] (EE) Segmentation fault at address 0x0
[ 4073.885] (EE)
Fatal server error:
[ 4073.885] (EE) Caught signal 11 (Segmentation fault). Server aborting
[ 4073.885] (EE)
[ 4073.885] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 4073.885] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 4073.885] (EE)
[ 4073.889] (EE) Server terminated with error (1). Closing log file.
Think i'm gonna wait for the Slackware team to fix things up. Tomorrow i'l try it again.
This has nothing to do with that. the fbdev driver is not shipped in Slackware but this "error" (which is not new at all) is actually a harmless warning. I would tend to think that the "old" mesa, built with an older gcc + glibc, won't work anymore in -current. Just a guess.
ftp://ftp.slackware.com/pub/slackwar...6.4-i586-1.txz has a good signature. It, indeed, contains only 32-bit binaries. So we can be pretty sure it's only a glitch in the release process. If you already upgraded and got the issue, you have 2 options:
Wait for the file upload to be fixed and upgrade again
Rebuild mesa for x86_64 by yourself using the current available source
ftp://ftp.slackware.com/pub/slackwar...6.4-i586-1.txz has a good signature. It, indeed, contains only 32-bit binaries. So we can be pretty sure it's only a glitch in the release process. If you already upgraded and got the issue, you have 2 options:
Wait for the file upload to be fixed and upgrade again
Rebuild mesa for x86_64 by yourself using the current available source
Rebuilding mesa from source for x86_64 does work.
Grab the mesa directory and all of its files from the web:
ftp://ftp.slackware.com/pub/slackwar...6.4-i586-1.txz has a good signature. It, indeed, contains only 32-bit binaries. So we can be pretty sure it's only a glitch in the release process. If you already upgraded and got the issue, you have 2 options:
Wait for the file upload to be fixed and upgrade again
Rebuild mesa for x86_64 by yourself using the current available source
waiting for the first option I have done the second on a fresh installed vm: if anyone is in need and wish to try a self-built package (waiting for the official one) is here (EDIT: link removed as the right package is now on the mirrors), it has a custom label so that it will upgrade fine with slackpkg once the official is available.
while building I just noticed a small glitch that you should consider if you wish to rebuild this yourself from the official sources: the demos need mesa already installed to build or the final package just doesn't contain them.
I just built it a first time, installed it and built it a second time.
I'll try to check how to point their build system to the just built headers/libraries in $PKG but if someone beat me to it he/she's welcome!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.