The officially official Devuan Forum!

You are not logged in.

#1 2017-12-14 21:10:03

lunario
Member
Registered: 2017-11-18
Posts: 8

Black Screen on Devuan Ascii - acpi=off solves it (undesirable)

I am using devuan ascii on several machines with great pleasure.
This week I got my librebooted Thinkpad X60. Devuan was installed via netinstall and worked fine, but when I upgraded it to ascii, I booted into a black screen afterwards with only the cursor in the upper left cornor (the system was frozen and did not react to any input). I tried several ways to solve the problem, such as reinstalling X in a failsafe root sell (the only thing I could boot into) but nothing helped. I reinstalled devuan and then did the upgrade again to make sure I did not accidentally delete important packages before. Same result though.

Today, I decided to give debian 9 on the system a try (please don't stop reading here wink) just for what it's worth, which led to the same result. So the problem is definitely related to changes made between jessie and stretch.
I duckduckgo'ed around a bit and found out that I am not the only one with this problem and that a workaround consists in passing acpi=off as a kernel argument at boot. However, this is not really a desirable state since it disables important hardware features and e.g. prevents the system from shutting down (and I am not planning to just "pull the plug" whenever I want to power off the machine). I also tried passing acpi=noirq as an argument, which apparently solved the problem for some, but in my case it did not.

Has anybody else come across this problem with particular hardware or libreboot? I am not sure whether it is related to hardware or libreboot in my case, but it does not really matter since many people who do NOT use libreboot seem to have the problem as well, with debian 9 (and consequently would have it with devuan ascii too, most likely). Are there any possible explanations for this situation and does anybody maybe have a solution to it?

Offline

#2 2017-12-15 10:35:56

chillfan
Member
Registered: 2016-12-01
Posts: 41

Re: Black Screen on Devuan Ascii - acpi=off solves it (undesirable)

It's helpful to narrow down the issue a bit. At what point does the screen go black? Is it immediate or only when the xserver starts?

Last edited by chillfan (2017-12-15 10:42:39)

Offline

#3 2017-12-15 11:22:44

lunario
Member
Registered: 2017-11-18
Posts: 8

Re: Black Screen on Devuan Ascii - acpi=off solves it (undesirable)

It goes blank as soon as the login screen (slim/lightdm) would normally appear, in other words: when X starts.
After I deinstalled slim/lightdm to start x with "startx", it did no go blank anymore but instead it froze as soon as XFCE/i3wm started (so I save the basic XFCE desktop with the mouse in the middle but could neither move the mouse nor give any keyboard input, not even to open a virtual console).

Offline

#4 2017-12-15 16:23:21

chillfan
Member
Registered: 2016-12-01
Posts: 41

Re: Black Screen on Devuan Ascii - acpi=off solves it (undesirable)

So it's probably the same as this issue.

You could try using noapic or nolapic as a kernel parameter, it's been known to fix some blank screen issues in the past.

Or try with the latest kernel from ascii-backports.

apt-get -t ascii-backports install linux-image-4.13.0-0.bpo.1-amd64

Failing that you could try to use the xorg vesa driver instead of the intel driver.

Last edited by chillfan (2017-12-15 16:25:44)

Offline

#5 2017-12-15 18:19:01

lunario
Member
Registered: 2017-11-18
Posts: 8

Re: Black Screen on Devuan Ascii - acpi=off solves it (undesirable)

Would I have to install that kernel after upgrading, or before? Also, does it not break my sources.list if I am on ascii and at the same time add ascii backports?

Offline

#6 2017-12-15 20:55:05

ralph.ronnquist
Administrator
From: Clifton Hill, Victoria, AUS
Registered: 2016-11-30
Posts: 137

Re: Black Screen on Devuan Ascii - acpi=off solves it (undesirable)

You should "pin" backports, i.e., add a file "reluctant-backports" with the following into /etc/apt/preferences.d

Package: *
Pin: release a=ascii-backports
Pin-Priority: 100

With that, apt will not upgrade to backports versions of packages unless you ask for them explicitly.

The "-t ascii-backports" argument opens it up a little, so that the nominated package and its dependents get pulled from backports, but nothing else.

Later on, without "-t ascii-backports", only packages already from backports will be upgraded from backports.

Offline

#7 2017-12-15 22:36:10

lunario
Member
Registered: 2017-11-18
Posts: 8

Re: Black Screen on Devuan Ascii - acpi=off solves it (undesirable)

Thank you for the explanation.

Just to make sure I am on the safe side and don't need to go through the reinstall process again for some silly mistake, did I get you right that the order of how I do things is the following for upgrading to ascii and installing the ascii-backports kernel:

1. pin the backports as you described
2. apt-get -t ascii-backports install linux-image-4.13.0-0.bpo.1-amd64
3. change etc/apt/sources.list for ascii and do normal apt-get dist-upgrade, which will heed the reluctant-backports file
4. reboot

Is that correct?

Offline

#8 2017-12-16 01:02:43

chillfan
Member
Registered: 2016-12-01
Posts: 41

Re: Black Screen on Devuan Ascii - acpi=off solves it (undesirable)

You should upgrade the kernel after the dist-upgrade. If the backported kernel doesn't solve the problem you could just remove it and the backports repo.

To make testing the screen problem a bit easier you could disable the display manager.

update-rc.d -f slim remove

Do this before you dist-upgrade. That should let you upgrade the kernel and make other tests without having to recover.

To start the display manager and test the xserver you can just use

/etc/init.d/slim start

Last edited by chillfan (2017-12-16 01:33:51)

Offline

#9 2017-12-16 11:14:44

lunario
Member
Registered: 2017-11-18
Posts: 8

Re: Black Screen on Devuan Ascii - acpi=off solves it (undesirable)

I just found out how to successfully run devuan ascii (mostly), however sadly none of your suggestions really solved the problem (thanks a lot though because they led me to the right track).


After upgrading and installing the new kernel as you suggested, the situation was exactly the same as before, I could not even get into a virtual console unless I was in recovery mode. What helped a bit was replacing the intel driver with vesa because then I could at least get into a normal virtual console, however starting slim or X still did not work (Permission denied).
I then created a xorg.conf (X -configure), which AFAIK should not be necessary these days anymore unless there are video driver issues, moved the xorg.conf.new from /root to /etc/X11, renamed it to xorg.conf and then "startx" would at least open XFCE, however with no reaction to my input. I also tried to manually add a section for the vesa driver in my xorg.conf, which did not solve it. The error error in Xorg.0.log was:

[    43.712] (EE) modeset(0): drmSetMaster failed: Permission denied
[    43.712] (EE)
Fatal server error:
[    43.712] (EE) AddScreen/ScreenInit failed for driver 0




My solution to get devuan ascii running was to change the sources.list back to jessie after upgrading, then deinstall xserver + xorg, reinstall xserver + xorg, xserver-xorg-video-intel -> you get with all packages except X on ascii. After rebooting, some packages naturally needed to be autoremoved and I was worried that this might crash the system again, but somehow it did not.
I am aware that this is not a clean solution, but it solves it for me at least. It also does not allow you to install any ascii packages anymore as soon as you have changed the sources back to jessie of course, but if you really want/need packages from ascii, this works, provided you install them before reinstalling X.

Last edited by lunario (2017-12-16 11:15:38)

Offline

#10 2017-12-16 19:45:19

chillfan
Member
Registered: 2016-12-01
Posts: 41

Re: Black Screen on Devuan Ascii - acpi=off solves it (undesirable)

lunario wrote:

After upgrading and installing the new kernel as you suggested, the situation was exactly the same as before, I could not even get into a virtual console unless I was in recovery mode. What helped a bit was replacing the intel driver with vesa because then I could at least get into a normal virtual console, however starting slim or X still did not work (Permission denied).

So you probably can get around the issue by forcing xorg to use only the vesa driver for now. That seems like the best option to me unless you really do need the accelerated driver, at least until you can find a better work-around.

I think the problem with xorg permissions is already known and I noticed there was an update yesterday for the xserver-xorg-legacy package that allows setting permissions for xorg (dpkg-reconfigure xserver-xorg-legacy). Using the console users only setting and starting as root works fine for me.

You seem to have narrowed it down quite a bit there. You only have problems when the intel driver loads so you could try a few work-arounds if you want, like disabling modesetting or maybe try the pci=noacpi boot parameter.

Last edited by chillfan (2017-12-16 20:19:13)

Offline

Board footer