Xorg segmentation fault after upgrading to -current.
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.
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.
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
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
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
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:
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.
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.
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).
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.
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.
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
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...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.