LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 05-12-2014, 08:02 AM   #1
brodo
Member
 
Registered: Jan 2004
Location: Poland, Poznan
Distribution: Slackware current 32 / 64
Posts: 414

Rep: Reputation: 32
Old IBM T23 Xorg error after upgrading to current (3.14.3 and so on)


No XFCE anymore in my old IBM T23 after upgrading to latest current (kernel 3.14.3 and the rest).
Changing video driver from vesa to savage doesn't help.

Here are the error (EE) sections from Xorg.0.log :

1. Using vesa driver:

[ 1398.344] (EE)
[ 1398.344] (EE) Backtrace:
[ 1398.344] (EE) 0: /usr/bin/X (xorg_backtrace+0x49) [0x81d6099]
[ 1398.345] (EE) 1: /usr/bin/X (0x8048000+0x191ac4) [0x81d9ac4]
[ 1398.345] (EE) 2: linux-gate.so.1 (__kernel_rt_sigreturn+0x0) [0xffffe40c]
[ 1398.345] (EE) 3: /lib/libc.so.6 (memcpy+0x27) [0xb73305f7]
[ 1398.345] (EE) 4: /usr/lib/xorg/modules/libshadow.so (shadowUpdatePacked+0x18c) [0xb76b4c2c]
[ 1398.345] (EE) 5: /usr/lib/xorg/modules/drivers/vesa_drv.so (0xb76e7000+0x25a3) [0xb76e95a3]
[ 1398.346] (EE) 6: /usr/lib/xorg/modules/libshadow.so (0xb76b3000+0x1482) [0xb76b4482]
[ 1398.346] (EE) 7: /usr/bin/X (BlockHandler+0xc8) [0x807d998]
[ 1398.346] (EE) 8: /usr/bin/X (WaitForSomething+0xf8) [0x81d3598]
[ 1398.346] (EE) 9: /usr/bin/X (0x8048000+0x3129e) [0x807929e]
[ 1398.346] (EE) 10: /usr/bin/X (0x8048000+0x1f69a) [0x806769a]
[ 1398.347] (EE) 11: /lib/libc.so.6 (__libc_start_main+0xf3) [0xb72c6963]
[ 1398.347] (EE) 12: /usr/bin/X (0x8048000+0x1fa69) [0x8067a69]
[ 1398.347] (EE)
[ 1398.347] (EE) Bus error at address 0xb6197000
[ 1398.347] (EE)
Fatal server error:
[ 1398.348] (EE) Caught signal 7 (Bus error). Server aborting
[ 1398.348] (EE)
[ 1398.348] (EE)
Please consult the The X.Org Foundation support at http://wiki.x.org for help.
[ 1398.348] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 1398.348] (EE)
[ 1398.808] (EE) Server terminated with error (1). Closing log file.


2. Using savage driver

[ 1267.955] (EE)
[ 1267.956] (EE) Backtrace:
[ 1268.018] (EE) 0: /usr/bin/X (xorg_backtrace+0x49) [0x81d6099]
[ 1268.018] (EE) 1: /usr/bin/X (0x8048000+0x191ac4) [0x81d9ac4]
[ 1268.018] (EE) 2: linux-gate.so.1 (__kernel_rt_sigreturn+0x0) [0xffffe40c]
[ 1268.019] (EE) 3: /usr/lib/libpixman-1.so.0 (0xb75fa000+0x71d00) [0xb766bd00]
[ 1268.019] (EE) 4: /usr/lib/libpixman-1.so.0 (0xb75fa000+0x575ac) [0xb76515ac]
[ 1268.019] (EE) 5: /usr/lib/libpixman-1.so.0 (pixman_fill+0x5d) [0xb760029d]
[ 1268.019] (EE) 6: /usr/lib/xorg/modules/libfb.so (fbFill+0x2f5) [0xb302b7b5]
[ 1268.019] (EE) 7: /usr/lib/xorg/modules/libfb.so (fbPolyFillRect+0x1b8) [0xb302bfe8]
[ 1268.020] (EE) 8: /usr/lib/xorg/modules/libexa.so (0xb3000000+0x11316) [0xb3011316]
[ 1268.020] (EE) 9: /usr/lib/xorg/modules/libexa.so (0xb3000000+0xa7b1) [0xb300a7b1]
[ 1268.020] (EE) 10: /usr/bin/X (miPaintWindow+0x208) [0x81b6e08]
[ 1268.020] (EE) 11: /usr/bin/X (miWindowExposures+0x20c) [0x81b777c]
[ 1268.020] (EE) 12: /usr/bin/X (DRIWindowExposures+0x8c) [0x819fa5c]
[ 1268.021] (EE) 13: /usr/bin/X (0x8048000+0x8cd84) [0x80d4d84]
[ 1268.021] (EE) 14: /usr/bin/X (MapWindow+0x263) [0x80a7b43]
[ 1268.021] (EE) 15: /usr/bin/X (InitRootWindow+0x124) [0x80a7c94]
[ 1268.021] (EE) 16: /usr/bin/X (0x8048000+0x1f620) [0x8067620]
[ 1268.022] (EE) 17: /lib/libc.so.6 (__libc_start_main+0xf3) [0xb7317963]
[ 1268.022] (EE) 18: /usr/bin/X (0x8048000+0x1fa69) [0x8067a69]
[ 1268.022] (EE)
[ 1268.022] (EE) Bus error at address 0xb30bc000
[ 1268.022] (EE)
Fatal server error:
[ 1268.023] (EE) Caught signal 7 (Bus error). Server aborting
[ 1268.023] (EE)
[ 1268.023] (EE)
Please consult the The X.Org Foundation support at http://wiki.x.org for help.
[ 1268.023] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 1268.023] (EE)
[ 1268.122] (EE) Server terminated with error (1). Closing log file.
 
Old 05-12-2014, 11:27 AM   #2
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,727

Rep: Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247
At first sight, one can say that is an X.org problem on your Savage.

But, on Current, we do not have major changes on X.org stack, if you upgraded from previously stable, 14.1. So, also considering the failure on the signal 7 (Bus error), I suspect an "The kernel 3.14.3 hit again!(tm)". My suggestion is to grab quickly the old version, 3.10.30, while not all mirrors are in sync, and to try it. Eventually, on continued failure, return to the 14.1 kernel, version 3.10.17.

Still, I suggest you to understand that while Slackware claim to run in anything sporting an i486 or superior, the sad truth is that in the old hardware you'll hit these driver problems, specially I talk about video drivers for the oldies. Then, will be very clever to stop on latest Slackware version of where the software stack support your hardware. You can't expect wonders from Slackware, where even Microsoft abandoned the house. I.e. you known that your computer it's NOT SUPORTED by Windows 8, right?

In other hand, The Guru Way will be to port old X.org stacks on Slackware Current and to build & use kernels on old versions, etc.

Last edited by Darth Vader; 05-12-2014 at 11:44 AM.
 
Old 05-12-2014, 02:06 PM   #3
rokytnji
LQ Veteran
 
Registered: Mar 2008
Location: Waaaaay out West Texas
Distribution: antiX 23, MX 23
Posts: 7,255
Blog Entries: 21

Rep: Reputation: 3499Reputation: 3499Reputation: 3499Reputation: 3499Reputation: 3499Reputation: 3499Reputation: 3499Reputation: 3499Reputation: 3499Reputation: 3499Reputation: 3499
On my IBM T23. I run AntiX and test new kernels for Anticapitalista. The only ones that boot on mine anymore are 3.12 on down.
Anything from 13.3 on up are failures on mine also.
So you are not alone.

http://antix.freeforums.org/post34925.html#p34925
 
Old 05-17-2014, 02:53 PM   #4
careca
LQ Newbie
 
Registered: May 2014
Posts: 2

Rep: Reputation: 0
My Fujitsu-Siemens LIFEBOOK E6585 shows exactly same behaviour after updating to kernel 3.14.[2-4].
X can't start.
Xorg.0 shows same error: Bus error at address ...

I think we could ask for a patch. It can't be big thing to keep providing driver compatibility.

Where should we input a request?

Last edited by careca; 05-17-2014 at 03:00 PM.
 
Old 05-17-2014, 03:10 PM   #5
rokytnji
LQ Veteran
 
Registered: Mar 2008
Location: Waaaaay out West Texas
Distribution: antiX 23, MX 23
Posts: 7,255
Blog Entries: 21

Rep: Reputation: 3499Reputation: 3499Reputation: 3499Reputation: 3499Reputation: 3499Reputation: 3499Reputation: 3499Reputation: 3499Reputation: 3499Reputation: 3499Reputation: 3499
Since my last post.

I installed http://www.linuxquestions.org/questi...zy-4175505021/

It boots and runs OK on my T23. The config file in /boot should help you Slackware users when asking
for a change.
 
Old 05-19-2014, 02:49 PM   #6
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 2,735

Rep: Reputation: 8994Reputation: 8994Reputation: 8994Reputation: 8994Reputation: 8994Reputation: 8994Reputation: 8994Reputation: 8994Reputation: 8994Reputation: 8994Reputation: 8994
It looks like the same problem happened with Arch. Unfortunately, they don't say how they fixed it.

A diffconfig between the two mentioned kernel versions would probably reveal the required kernel config changes to address this problem.

https://bbs.archlinux.org/viewtopic.php?id=180301
 
Old 05-19-2014, 03:45 PM   #7
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,727

Rep: Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247
Quote:
Originally Posted by volkerdi View Post
It looks like the same problem happened with Arch. Unfortunately, they don't say how they fixed it.

A diffconfig between the two mentioned kernel versions would probably reveal the required kernel config changes to address this problem.

https://bbs.archlinux.org/viewtopic.php?id=180301
How about an diff on current 3.14.4?

Bare config:

https://projects.archlinux.org/svnto...packages/linux

Diff to current generic smp attached.
Attached Files
File Type: txt config.diff.txt (118.9 KB, 9 views)
 
Old 05-19-2014, 03:52 PM   #8
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 2,735

Rep: Reputation: 8994Reputation: 8994Reputation: 8994Reputation: 8994Reputation: 8994Reputation: 8994Reputation: 8994Reputation: 8994Reputation: 8994Reputation: 8994Reputation: 8994
Quote:
Originally Posted by Darth Vader View Post
How about an diff on current 3.14.4?
Thanks, but I had that already. It doesn't narrow things down all that much, though. Especially since I have no Savage video chipset to test with here, we're really going to need a diff between those two Arch kernels to see what changed.

Or, I suppose, we could try asking them.
 
Old 05-19-2014, 03:58 PM   #9
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,727

Rep: Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247
Quote:
Originally Posted by volkerdi View Post
Thanks, but I had that already. It doesn't narrow things down all that much, though. Especially since I have no Savage video chipset to test with here, we're really going to need a diff between those two Arch kernels to see what changed.

Or, I suppose, we could try asking them.
Still, I noticed that they do not include a Savage framebuffer module at all.

Code:
CONFIG_FB_SAVAGE is not set
We, we have it in the form of module.
 
Old 05-19-2014, 10:06 PM   #10
ReaperX7
LQ Guru
 
Registered: Jul 2011
Location: California
Distribution: Slackware64-15.0 Multilib
Posts: 6,563
Blog Entries: 15

Rep: Reputation: 2104Reputation: 2104Reputation: 2104Reputation: 2104Reputation: 2104Reputation: 2104Reputation: 2104Reputation: 2104Reputation: 2104Reputation: 2104Reputation: 2104
Technically you shouldn't have to use the kernel framebuffer modules for specific cards. The specific card framebuffers have been known to have varied issues with correct displays. Most kernel config wikis usually state, such as Gentoo's here: https://wiki.gentoo.org/wiki/Xorg/Configuration to disable the framebuffer support in favor of the newer Kernel Modesetting features for DRM and DRI.
 
Old 05-20-2014, 02:14 AM   #11
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,727

Rep: Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247
Quote:
Originally Posted by volkerdi View Post
Thanks, but I had that already. It doesn't narrow things down all that much, though. Especially since I have no Savage video chipset to test with here, we're really going to need a diff between those two Arch kernels to see what changed.

Or, I suppose, we could try asking them.
Here we go...

https://projects.archlinux.org/svnto...8478706a2aa44e

Code:
diff --git a/trunk/config b/trunk/config
index 7899a16..89209a4 100644
--- a/trunk/config
+++ b/trunk/config
@@ -252,8 +252,8 @@ CONFIG_SECCOMP_FILTER=y
CONFIG_HAVE_CC_STACKPROTECTOR=y
CONFIG_CC_STACKPROTECTOR=y
# CONFIG_CC_STACKPROTECTOR_NONE is not set
-CONFIG_CC_STACKPROTECTOR_REGULAR=y
-# CONFIG_CC_STACKPROTECTOR_STRONG is not set
+# CONFIG_CC_STACKPROTECTOR_REGULAR is not set
+CONFIG_CC_STACKPROTECTOR_STRONG=y
CONFIG_HAVE_IRQ_TIME_ACCOUNTING=y
CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE=y
CONFIG_HAVE_ARCH_SOFT_DIRTY=y
@@ -1502,7 +1502,8 @@ CONFIG_DMA_SHARED_BUFFER=y
#
# Bus devices
#
-CONFIG_CONNECTOR=m
+CONFIG_CONNECTOR=y
+CONFIG_PROC_EVENTS=y
CONFIG_MTD=m
CONFIG_MTD_TESTS=m
CONFIG_MTD_REDBOOT_PARTS=m
 
Old 05-20-2014, 02:30 AM   #12
dunne
Member
 
Registered: May 2014
Distribution: OpenBSD
Posts: 67

Rep: Reputation: 36
Fix


This happened to me under OpenBSD 5.5 on a T23. I found a solution here:

http://www.physics.wustl.edu/~alford...d/T23_F17.html

Basically, edit the /etc/X11/xorg.conf file: uncomment Option "DisableTile"
in the Section "Device" that contains the Savage driver options.
 
Old 05-20-2014, 05:49 AM   #13
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,727

Rep: Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247
Lacking Mesa drivers?

If we really want to support those old videocards, we need to have by default a compat mesa drivers package.

Bellow is my build, tested (and used) with success with an old SiS. I known, only OpenGL 1.2, but still better than nothing...

MesaLib-7.11.2.tar.bz2


slack-desc:

Code:
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description.  Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in.  You must
# make exactly 11 lines for the formatting to be correct.  It's also
# customary to leave one space after the ':'.

         |-----handy-ruler------------------------------------------------------|
mesa-dri1: mesa-dri1 (Old DRI drivers support for MESA - a 3-D graphics library)
mesa-dri1:
mesa-dri1: Mesa is a 3-D graphics library with an API very similar to that of
mesa-dri1: another well-known 3-D graphics library.  :-)  The Mesa libraries are
mesa-dri1: used by X to provide both software and hardware accelerated graphics.
mesa-dri1:
mesa-dri1: This package contains the DRI drivers for these old videocards:
mesa-dri1: unichrome, i810, mach64, mga, r128, savage, sis, tdfx
mesa-dri1:
mesa-dri1: Mesa was written by Brian Paul.
mesa-dri1:

mesa-dri1.SlackBuild:

Code:
#!/bin/sh

# Copyright 2014 Virgil-Adrian Teaca <darkstarlinux_at_gmail_dot_com>
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
#    notice, this list of conditions and the following disclaimer.
#
#  THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR IMPLIED
#  WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
#  MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO
#  EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
#  SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
#  PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
#  OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
#  WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
#  OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
#  ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

PKGNAM=mesa-dri1
VERSION=7.11.2
BUILD=${BUILD:-1}

NUMJOBS=${NUMJOBS:--j8}

# Be sure this list is up-to-date:
DRI_DRIVERS="unichrome,i810,mach64,mga,r128,savage,sis,tdfx"

if [ -z "$ARCH" ]; then
  case "$( uname -m )" in
    i?86) export ARCH=i486 ;;
    arm*) export ARCH=arm ;;
       *) export ARCH=$( uname -m ) ;;
  esac
fi

CWD=$(pwd)
TMP=${TMP:-/tmp}
PKG=$TMP/package-mesa-dri1

if [ "$ARCH" = "i486" ]; then
  SLKCFLAGS="-O2 -march=i486 -mtune=i686"
  LIBDIRSUFFIX=""
elif [ "$ARCH" = "x86_64" ]; then
  SLKCFLAGS="-O2 -fPIC"
  LIBDIRSUFFIX="64"
else
  SLKCFLAGS="-O2"
  LIBDIRSUFFIX=""
fi

rm -rf $PKG
mkdir -p $TMP $PKG
cd $TMP
rm -rf Mesa-${VERSION}

tar xvf $CWD/MesaLib-${VERSION}.tar.?z* || exit 1
cd Mesa-$VERSION


# Let's kill the warning about operating on a dangling symlink:
rm -f src/gallium/state_trackers/d3d1x/w32api

# Make sure ownerships and permissions are sane:
chown -R root:root .
find . \
  \( -perm 777 -o -perm 775 -o -perm 711 -o -perm 555 -o -perm 511 \) \
  -exec chmod 755 {} \; -o \
  \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 \) \
  -exec chmod 644 {} \;

# Running autoreconf to avoid problems if our autotools don't match upstream's:
autoreconf -vfi

CFLAGS="$SLKCFLAGS" \
./configure \
  --prefix=/usr \
  --sysconfdir=/etc \
  --libdir=/usr/lib${LIBDIRSUFFIX} \
  --mandir=/usr/man \
  --docdir=/usr/doc/mesa-$VERSION \
  --with-dri-driverdir=/usr/lib${LIBDIRSUFFIX}/xorg/modules/dri \
  --with-dri-drivers="$DRI_DRIVERS" \
  --with-gallium-drivers= \
  --disable-gallium-llvm \
  --enable-glx-tls \
  --with-driver=dri \
  --enable-xcb \
  --disable-glut \
  --enable-gles1 \
  --enable-gles2 \
  --enable-egl \
  --enable-texture-float \
  --disable-shared-dricore \
  --build=$ARCH-slackware-linux


make $NUMJOBS || make || exit 1

# First, we install the license file, in the TXT format
mkdir -p $PKG/usr/doc/mesa-dri1-$VERSION
lynx -dump docs/license.html > $PKG/usr/doc/mesa-dri1-$VERSION/LICENSE

# Then, we install our precious DRI drivers for oldies
cd src/mesa/drivers/dri || exit 1

make -C unichrome install DESTDIR=$PKG || exit 1
make -C i810 install DESTDIR=$PKG || exit 1
make -C mach64 install DESTDIR=$PKG || exit 1
make -C mga install DESTDIR=$PKG || exit 1
make -C r128 install DESTDIR=$PKG || exit 1
make -C savage install DESTDIR=$PKG || exit 1
make -C sis install DESTDIR=$PKG || exit 1
make -C tdfx install DESTDIR=$PKG || exit 1

# Finally, we install the slack-desc and we create the package
mkdir -p $PKG/install
cat $CWD/slack-desc > $PKG/install/slack-desc

cd $PKG
/sbin/makepkg -l y -c n $TMP/${PKGNAM}-$VERSION-$ARCH-$BUILD.txz

Last edited by Darth Vader; 05-20-2014 at 05:53 AM.
 
Old 06-19-2014, 04:15 PM   #14
careca
LQ Newbie
 
Registered: May 2014
Posts: 2

Rep: Reputation: 0
Thumbs up Problem solved with Kernel 3.14.7 - Fujitsu-Siemens LIFEBOOK E6585

After upgrading my Fujitsu-Siemens LIFEBOOK E6585 with kernel 3.14.7, I get X starting correctly again.

In fact I use Fedora distribution, but I can't see why it wouldn't work for you guys on Slackware as well.

Wish all the best!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Current - problem with Xorg on IBM T23 brodo Slackware 6 05-17-2013 02:20 PM
High CPU load after upgrading to xorg 1.6.3 (-current) Poetics Slackware 5 08-27-2009 12:46 AM
problem with suse & IBM T23 quierolinux Linux - Laptop and Netbook 3 05-05-2007 02:19 PM
IBM T23 - clearing CMOS Emerson Linux - Laptop and Netbook 2 06-11-2005 10:09 PM
Mandrake 10.1 in IBM Thinkpad T23 tantotea Mandriva 3 03-11-2005 10:47 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 08:28 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration