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.
Hi, got a new computer with Windows 10 and made a dual boot with Slackware.
Had a bit of hassle with UEFI, but all went well and booted into Slack with X a few times (!).
Now the system still boots, but there's a problem with X.
/var/log/Xorg.0.log:
Code:
ll unloadmodule: "vesa"
ll unloadsubmodule: "int10"
ll unloading int10
ll unloadsubmodule: "vbe"
ll unloading vbe
EE Screens found, but none have a usable configuration.
EE
Fatal Server error
no screens found
It was a fresh install, so no kernel-upgrades.
I installed Refind (from SBO), but wasn't happy with it, so I uninstalled it.
Even reinstalled Slackware, but no luck.
Looks like you have a newer system that isn't properly supported by 14.2. The easiest way around this is to install -current, however, that is a development version of Slackware that may or may not break on you.
If you want to stick with 14.2, the first thing you'd want to do is upgrade the kernel, but I imagine you would also need to upgrade at least the xf86-video-intel driver.
Agree with bassmadrigal. Lack of CONFIG_DRM_I915_ALPHA_SUPPORT appears to be the problem with the 14.2 kernel. I'd also agree with the upgrade to current.
How stable is -current?
I also need this computer for my work.
*shivers*
This is a common question. The bottom line is that -current is not recommended for production machines. That said, a lot of users here say it's OK for a work machine.
I think really it depends on your knowledge of *nix and if you are able to sort out problems when, or if, they arise. One thing I will say is that, from a cursory glance, there are a lot more threads here for issues in -current than stable.
Usually the software included in Slackware will be stable in -current. However, -current can and will break your 3rd-party packages when core components in Slackware are updated (which still tends to not be very common). All that is required is to recompile those packages to use the new core libraries.
You may also run into issues with 3rd-party scripts, like SBo's in that they are only tested for the stable version and some require changes when updated software is introduced in Slackware.
I wouldn't suggest -current if you're not very familiar with SlackBuilds, dependencies, and how to work through any problems that come up.
Last edited by Lysander666; 11-04-2018 at 09:29 AM.
Generally very stable, but there have been exceptions. Recently there was an update in -current to the icu4c package that required rebuilding many third party software packages. Alien_Bob released updated Libreoffice packages in a few days and I had a compile fest rebuilding my R installation.
If you depend on your machine, I advise keeping a working installation and have a second installation for testing upgrades.
-current is not really my cup of tea...
I never thought I'd ever say this, but I'm thinking about putting another distro on it until Slackware reaches a new stable version.
Really I would imagine how much time a] adriv has to dedicate to a major issue if it happens and b] it's nice not having to worry about issues on a stable release.
In my own case, I don't run -current since I am very busy and if there is a major issue, I may not have time to sort it out. It could get in the way of time-sensitive work. I wouldn't want to miss a deadline because I had to sort out some library issue.
OP, to answer your points about distros with newer kernels, you could consider Devuan stable [4.9.82], antiX [4.9.126] or maybe Alpine stable [4.14.69]. Not to deter you from using Slackware, of course.
Last edited by Lysander666; 11-04-2018 at 09:53 AM.
Really I would imagine how much time a] adriv has to dedicate to a major issue if it happens and b] it's nice not having to worry about issues on a stable release.
In my own case, I don't run -current since I am very busy and if there is a major issue, I may not have time to sort it out. It could get in the way of time-sensitive work. I wouldn't want to miss a deadline because I had to sort out some library issue.
OP, to answer your points about distros with newer kernels, you could consider Devuan stable [4.9.82] or maybe Alpine stable [4.14.69]. Not to deter you from using Slackware, of course.
10 Years ago I would've jumped into it probably, but just don't have the time anymore (and energy) to tinker with computers night after night. Been there, done that.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
