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.
Will compiling a new kernel help solve this problem ?
Maybe that will give you a newer graphics driver and help, but I wouldn't count on that unless you find something in the kernel changelogs indicating that a bug related to your problem has been fixed.
Do you have any other monitor you can try with? Do you get the same problem also with other monitors? Does your monitor and graphics card have any other interfaces and do you have cables for those interfaces (DVI / HDMI / DisplayPort / VGA)? Do you also get the same problem with other interfaces?
When I change to runlevel 4 the login prompt loads properly. When I enter the password the window manager sometimes loads properly and sometimes only on the second time it loads. So there should not be any issue with the X. So I am puzzled with it.
When I change to runlevel 4 the login prompt loads properly. When I enter the password the window manager sometimes loads properly and sometimes only on the second time it loads. So there should not be any issue with the X. So I am puzzled with it.
Each time X is restarted (possible because of some kind of crash) a new Xorg.0.log is created and the old log file with clues of what caused the crash is renamed to Xorg.0.log.old.
Each time you successfully log in the .xsession-errors is recreated. To study that file after a failed login attempt you will need to login on a virtual text console or from the network by something like ssh.
I have to ask, given one of Slackware's advantages over most systemd based distros is human readable text-based configuration, what do you think is the value advantage in creating "/etc/X11/xorg.conf.d/20-intel.conf" over just placing those lines in "/etc/X11/xorg.conf" ?
I believe it's to avoid the change of the file and rather have one added : moduarity to get easier backup/sink and readability (a named change rather than everything in the same place).
Thanks for the response, Tonus. IO understand modularity even if I disagree that is at all helpful but that's just my personal preference. I want everything to do with X features in one place. Also I like the documentation Slackware provides in the xorg.conf.example and the NVIDIA-foo.run installer offers to write the Display options for you in "/etc/X11/xorg.conf", not a major concern now but it does hint at how universal that configuration is or can be.
I don't understand what you mean by "change of the file". Could you expand please?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.