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'm making an effort to migrate from windows 7, I chose slack because it's the one I'm the most familiar with and the one I always end up going back to.
On a previous attempt to migrate, I successfully installed slackware on CSM mode, a bios update I made earlier this year seems to have changed something that makes LILO puke. I remedied this by switching to EFI mode and installing with ELILO, install went smoothly after that, set up my main user profile and SBOpkg, but I have a problem.
When I try to start X, the server blanks out my screen and immediately returns to the command line. logs show a segmentation fault, signal (11) or something like that. I don't understand why this would happen, as I had just overwritten a debian install which did have a working X- on EFI as well.
how can I fix my Xserver so I can get my icons running again?
Since you say X won't start, I'm assuming you can log in to the command line. Check the logs in /var/log, in particular Xorg.0.log, messages, and syslog; they may shed some light on this issue. Post any log output that seems relevant here, being sure to surround it with "code" tags, which become available when you click the "Go Advanced" button at the bottom of the "compose post" window.
I'm posting this straight from links on slackware itself. I cannot remember that one commandline-based window manager that I might be able to use to copy-paste the logs, I know I can copy-paste with just the mouse button but I cannot copy-paste from different command-line sessions. I'll give what I find is relevant and type as much as my patience is willing to allow.
I have not touched slackware.current, this all happened just after installing slackware on my main machine.
Code:
## /var/log/Xorg.0.log
(II) AIGLX: Screen 0 is not DRI2 capable
(EE) Reverting to software rendering
## ...command repeats
(II) AIGLX: enabled GLX_MESA_copy_sub_buffer
(II) AIGLX: loaded and initialized swrast
(II) GLX Initialized DRISWRAST GL Provider for screen 0
(EE) ## blank error
(EE) backtrace:
##nine erros that complain about the following Xorg directories with hex-symbols I cannot understand
#/usr/libexec/Xorg
#/lib64/libthread.so.0
#/lib64/libc.so.6
(EE) segmentation fault at address 0xa0
here's some things I found that looked relevant when looking through dmesg
Code:
##system wakeup disabled on several PCI devices
##...
radeon 0000:07:00.0: No connecters reported with connected nodes
[drm] cannot find any crtc or sizes - going 1024x768
FAT-fs (sda1): volume was not properly unmounted. some data may be corrupt. please run fsck
could not find much else in var/log about anything important, no major or notable errors in dmesg. fsck just showed a bad bit as a result of improperly unmounting my boot partition. nothing else showed in that.
If you have a thumbdrive, you could copy the files (or output in the case of dmesg) to it, then you could use a different computer to post them.
I may not be the best at reading the logs, but I'm not seeing any causes for those errors with the amount posted. A full log might provide us more information. Based on the little we do have, it might be a graphics driver issue. What video card do you have? Can you post the following?
attached is the output of dmesg, and Xorg.0.log. below is the result of the lspci command bassmadrigal listed.
Code:
##my GPUs
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Device 67df (rev c7)
Subsystem: PC Partner Limited / Sapphire Technology Device e347
01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device aaf0
Subsystem: PC Partner Limited / Sapphire Technology Device aaf0
--
07:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM]
Subsystem: PC Partner Limited / Sapphire Technology Radeon HD 6450 1 GB DDR3
Kernel driver in use: radeon
Kernel modules: radeon
I have non-matching GPUs because I was attempting to do VGA-passthrough using the caicos as the host GPU.
if I understand this lspci output right, my computer is using the wrong GPU for display... which does not make sense to me, since my Sapphire R290+ is the GPU I'm operating with right now. this display worked fine the last time I rage-quit to windows 7, the only other thing I can think it would be that the bios update caused some kind of snafu with the huge kernel during install.
Last edited by lawnm0wer; 12-01-2017 at 10:08 PM.
Reason: clarification
One thing that could have changed during a bios alteration/update is "preferred graphics device" when you have both an onboard graphics chip as well as one in a slot, presumably PCIe or PCI Express. Make sure it points to your preferred use. Sometimes conflicts arise and it may be necessary to blacklist the one you don't want to use, at least until you have X working and can troubleshoot in an environment more comfortable to you.
In your Xorg.0.log the first indication of a problem I see is
Code:
[ 75.301] (II) AIGLX: Screen 0 is not DRI2 capable
[ 75.301] (EE) AIGLX: reverting to software rendering
So not only may there be a conflict in GPUs but it is possible you also need a more complete and specific definition of "Monitor" and "Screen" in your /etc/X11/xorg.conf.
I wish I could be more helpful but I am unfamiliar with AMD/ATi graphics. For examp0le, nVidia driver comes with nvidia-settings that provides the means to extract the monitor's EDID to a bin file to evoke the exact internal instructions on every xserver restart. If AMD has anything like that, it could be very helpful.
Also, I always setup X manually so I am a bit unfamiliar here as well but iirc /usr/bin/xorgsetup is helpful to many. Did you run that?
Another personal preference that can eliminate some issues, at least for troubleshooting, is to login to runlevel 3 as root and invoke xdm, gdm, or kdm to get a display manager working immediately as well as a login screen where user can login to the selected WM/DE of choice. This can make getting back to runlevel 3, if X fails, a bit easier by various means such as Ctrl-Alt-Backspace (assuming you have that enabled) or just Alt-F4 followed by Alt-F1.
It might be instructive to try Alien Bob's Slack Live to see if that works for you as well as how and why. -- Slack Live --
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.