LinuxQuestions.org - [SOLVED] No screens found

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - No screens found (https://www.linuxquestions.org/questions/slackware-14/no-screens-found-4175641724/)

No screens found

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

What is going on?
Can I fix this?

Oh, and it's an Asus mobo with Intel chips.
And Windows works OK, so it's not a hardware problem.

# lspci | grep -i vga might tell you which module you should be loading for your video card. Did this problem start after a kernel update?

Thanks for your answer.
lspci | grep -i vga

Code:

00:02.0 VGA compatible controller: Intel corporation device 3e92

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.

It booted into X at least 4 times.

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*

Quote:

Originally Posted by adriv (Post 5922714)

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.

Further reading:

About Slackware -current
How stable is current compared to stable?
Is Slackware current worth it?
How stable is Slackware current?

Basically, bass sums it up nicely:

Quote:

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.

I believe someone on here provides custom made kernels. You should look into that I think.

Quote:

How stable is -current?

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.:cry:

Any suggestions?

Put on -current and enjoy!

Quote:

Originally Posted by allend (Post 5922727)

Put on -current and enjoy!

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.

Quote:

Originally Posted by Lysander666 (Post 5922729)

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.

Quote:

Originally Posted by RadicalDreamer (Post 5922720)

I believe someone on here provides custom made kernels. You should look into that I think.

You can find various kernels from David Spencer's (idlemoor) web site and give a newer kernel a shot.

https://dusk.idlemoor.tk/

In most cases there is no "tinerking" required.