LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
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-22-2018, 07:46 AM   #1
canopusx
LQ Newbie
 
Registered: May 2018
Distribution: Slackware
Posts: 12

Rep: Reputation: 0
Question Xorg segmentation fault after upgrading to -current.


Hello everyone. This is my first post. New install here. Yesterday, I installed 14.2 and upgraded to -current. When I tried to run startx, the screen went blank and the blinking cursor just stayed static at the top. That's it. Running
Code:
cat /var/log/Xorg.0.log | grep "(EE)"
gives me
Quote:
"module ABI major version (23) doesn't match the server's version (24)"
error for the modules
Code:
geode, r128, s3virge, savage, sis, and tseng
. I also tried to do
Code:
startx -- -ignoreABI
which basically summarized to a signal 11 Segmentation fault. Please help me! Also, since I don't have a working graphical environment, how can I post logs?

Edit: Also, ncurses also seems to be broken as some weird characters appear all over the screen.

Last edited by canopusx; 05-22-2018 at 07:56 AM.
 
Old 05-22-2018, 08:09 AM   #2
montagdude
Senior Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 2,011

Rep: Reputation: 1619Reputation: 1619Reputation: 1619Reputation: 1619Reputation: 1619Reputation: 1619Reputation: 1619Reputation: 1619Reputation: 1619Reputation: 1619Reputation: 1619
What steps did you take to upgrade to -current?
 
Old 05-22-2018, 08:21 AM   #3
RandomTroll
Senior Member
 
Registered: Mar 2010
Distribution: Slackware
Posts: 1,942

Rep: Reputation: 270Reputation: 270Reputation: 270
Quote:
Originally Posted by canopusx View Post
When I tried to run startx, the screen went blank and the blinking cursor just stayed static at the top.
Does the CapsLock key change the state of the CapsLock LED? What happens if you key control-alt-backspace?

I had the ABI version not-matching error for years without apparent problem.

Quote:
Originally Posted by canopusx View Post
Code:
cat /var/log/Xorg.0.log | grep "(EE)"
gives me error for the modules
Code:
geode, r128, s3virge, savage, sis, and tseng
.
These are all video chips; do you know what video chip you have?


Quote:
Originally Posted by canopusx View Post
since I don't have a working graphical environment, how can I post logs?
Why is this relevant? How did you use this site?

Quote:
Originally Posted by canopusx View Post
ncurses also seems to be broken as some weird characters appear all over the screen.
Do capital letters display properly? If you send 0E to stdout you switch to the alternative character set. I do this (accidentally) occasionally. 0F switches back. I have a script, FIXSCREEN:
Code:
echo -e \\017
.
 
Old 05-22-2018, 08:37 AM   #4
canopusx
LQ Newbie
 
Registered: May 2018
Distribution: Slackware
Posts: 12

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by montagdude View Post
What steps did you take to upgrade to -current?
Code:
1. slackpkg update
2. slackpkg install-new
3. slackpkg upgrade-all
4. slackpkg clean-system

Last edited by canopusx; 05-22-2018 at 08:48 AM.
 
Old 05-22-2018, 08:43 AM   #5
canopusx
LQ Newbie
 
Registered: May 2018
Distribution: Slackware
Posts: 12

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by RandomTroll View Post
Does the CapsLock key change the state of the CapsLock LED? What happens if you key control-alt-backspace?

I had the ABI version not-matching error for years without apparent problem.


These are all video chips; do you know what video chip you have?



Why is this relevant? How did you use this site?


Do capital letters display properly? If you send 0E to stdout you switch to the alternative character set. I do this (accidentally) occasionally. 0F switches back. I have a script, FIXSCREEN:
Code:
echo -e \\017
.
1. I tried to post this too, but thought it would be irrelevant: CapsLock doesn't change the state.
2. Ctrl+Alt+Bkspc gives nothing.
3. I have an intel chip.
4. I am posting this through my mobile.
5. Yes. Capital letters work.
Finally, thanks for posting soon. Thanks a lot.
 
Old 05-22-2018, 08:43 AM   #6
pan64
LQ Addict
 
Registered: Mar 2012
Location: Hungary
Distribution: debian/ubuntu/suse ...
Posts: 21,629

Rep: Reputation: 7265Reputation: 7265Reputation: 7265Reputation: 7265Reputation: 7265Reputation: 7265Reputation: 7265Reputation: 7265Reputation: 7265Reputation: 7265Reputation: 7265
this abi problem means incompatibility between the X server and video driver.
 
Old 05-22-2018, 09:06 AM   #7
ponce
LQ Guru
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 7,060

Rep: Reputation: 4139Reputation: 4139Reputation: 4139Reputation: 4139Reputation: 4139Reputation: 4139Reputation: 4139Reputation: 4139Reputation: 4139Reputation: 4139Reputation: 4139
as you have just installed have you considered reinstalling directly from a current iso (to avoid upgrading issues)?

http://bear.alienbase.nl/mirrors/sla...e-current-iso/
http://bear.alienbase.nl/mirrors/sla...4-current-iso/
 
Old 05-22-2018, 09:17 AM   #8
canopusx
LQ Newbie
 
Registered: May 2018
Distribution: Slackware
Posts: 12

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by ponce View Post
as you have just installed have you considered reinstalling directly from a current iso (to avoid upgrading issues)?

http://bear.alienbase.nl/mirrors/sla...e-current-iso/
http://bear.alienbase.nl/mirrors/sla...4-current-iso/
I'm now going to try it. Thanks a lot ponce. I'll be grateful for you for the current repo. But, maybe I should wait a bit more. For then someone may come up with some solution that might fix the problem. Also, if I change my distro, I can't prolong this post, can I? I'm new, hence these questions. Thanks.

Edit: Terminal output is also messed up. Some weird characters randomly appear, when I try lsblk, for example.

Last edited by canopusx; 05-22-2018 at 09:23 AM.
 
Old 05-22-2018, 09:21 AM   #9
ponce
LQ Guru
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 7,060

Rep: Reputation: 4139Reputation: 4139Reputation: 4139Reputation: 4139Reputation: 4139Reputation: 4139Reputation: 4139Reputation: 4139Reputation: 4139Reputation: 4139Reputation: 4139
IMHO, if you are new you should consider using slackware stable, current is the development tree, intended mainly for users that knows how to fix broken stuff theirselves.
I think I might warn you about this because you might get frustrated thinking it's a rolling release a-la Archlinux while it's not (it requires intervention, from time to time).

Last edited by ponce; 05-22-2018 at 09:24 AM.
 
Old 05-22-2018, 09:32 AM   #10
canopusx
LQ Newbie
 
Registered: May 2018
Distribution: Slackware
Posts: 12

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by ponce View Post
IMHO, if you are new you should consider using slackware stable, current is the development tree, intended mainly for users that knows how to fix broken stuff theirselves.
I think I might warn you about this because you might get frustrated thinking it's a rolling release a-la Archlinux while it's not (it requires intervention, from time to time).
Thanks. I've thoroughly gone through forums before coming to Slackware. I understand current's not rolling but I think I just want a wee bit of newer packages. I've used stable in the past btw.
 
Old 05-22-2018, 09:52 AM   #11
BW-userx
LQ Guru
 
Registered: Sep 2013
Location: Somewhere in my head.
Distribution: Slackware (15 current), Slack15, Ubuntu studio, MX Linux, FreeBSD 13.1, WIn10
Posts: 10,342

Rep: Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242
Quote:
Originally Posted by canopusx View Post
Code:
1. slackpkg update
2. slackpkg install-new
3. slackpkg upgrade-all
4. slackpkg clean-system
Code:
change mirror to current sight
slackpkg update gpg
slackpkg update
slackpkg install-new
slackpkg upgrade-all
always worked for me.
 
Old 05-22-2018, 12:04 PM   #12
chemfire
Member
 
Registered: Sep 2012
Posts: 410

Rep: Reputation: Disabled
Sat May 12 00:28:18 UTC 2018
Where possible, the driver packages for X11 have been recompiled. However,
there were some (xf86-video-geode, xf86-video-tseng, xf86-video-sis,
xf86-video-savage, xf86-video-s3virge, xf86-video-rendition, xf86-video-r128,
and xf86-video-mach64) that would not compile against xorg-server-1.20.0 and
for which no patches seem to be available. Is anyone still using those, or are
they finally obsolete? I'll hold off on removing them until I can find out one
way or the other.

-------

Its worth noting the issue seems to be with a lot of modules mentioned here. It looks like at least mach64 has since been updated again. Maybe these others can't run at all?

As far as the OP goes - it might be worth removing these packages as you probably don't have any of this hardware. That would make the errors go away most likely but its also not likely what is preventing the X.org server from running.
 
Old 05-22-2018, 12:35 PM   #13
orbea
Senior Member
 
Registered: Feb 2015
Distribution: Slackware64-current
Posts: 1,950

Rep: Reputation: Disabled
What video card and driver are you using? Does the modesetting xorg driver work? You should be able to test it with something like.

/etc/X11/xorg.conf.d/modesetting.conf
Code:
Section "Device"
   Identifier  "foo"
   Driver      "modesetting"
EndSection
The 'Identifier' field can be anything.
 
Old 05-22-2018, 12:50 PM   #14
canopusx
LQ Newbie
 
Registered: May 2018
Distribution: Slackware
Posts: 12

Original Poster
Rep: Reputation: 0
Ok. So, I reinstalled the whole slack system, but this time with the current builds by alienbob, as suggested by ponce. And guess what? It's the same again! But this time, I can't see any errors in /var/log/Xorg.*.config. But I can see the ABI mismatch errors when I run X -configure. Seems something's wrong

Last edited by canopusx; 05-22-2018 at 12:53 PM.
 
Old 05-22-2018, 01:13 PM   #15
ponce
LQ Guru
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 7,060

Rep: Reputation: 4139Reputation: 4139Reputation: 4139Reputation: 4139Reputation: 4139Reputation: 4139Reputation: 4139Reputation: 4139Reputation: 4139Reputation: 4139Reputation: 4139
Quote:
Originally Posted by canopusx View Post
Ok. So, I reinstalled the whole slack system, but this time with the current builds by alienbob, as suggested by ponce. And guess what? It's the same again! But this time, I can't see any errors in /var/log/Xorg.*.config. But I can see the ABI mismatch errors when I run X -configure. Seems something's wrong
can you paste your /var/log/Xorg.0.log somewhere like http://pastebin.com and post here the resulting link to the paste?
the output of lspci might be useful too...

Last edited by ponce; 05-22-2018 at 01:16 PM.
 
  


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
Xorg dies with segmentation fault on Ubuntu 13.04 shachter Ubuntu 6 11-15-2013 01:57 PM
xgames current 13.37 segmentation fault anti_user Slackware 7 03-20-2011 04:23 AM
Xorg segmentation fault igadoter Slackware 4 07-03-2010 07:40 PM
Slackware64-current Segmentation Fault in cryptsetup Ron Parker Slackware 2 08-19-2009 02:04 PM
mplayerplug-in with current causes segmentation fault Daedra Slackware 2 03-27-2009 06:22 PM

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

All times are GMT -5. The time now is 11:51 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