Can't configure XServer because of "i915.modeset"

fromage · 2017-01-09 20:18:37

I've followed multiple guides but have yet to see one which encounters a Catch-22 problem like this one.

I am working on a fresh install of Arch on a low-end laptop (Dell Inspiron 15 3552, the one with a Celeron Processor, N3050). I am not dualbooting.
I have used UEFI to install Arch.

The screen would go black once I selected Arch from GRUB. I found out that I needed to add the kernel parameter "nomodeset" or "i915.modeset=0" in order for Arch to even show me a tty.
However, my second problem is that any form of trying to start XServer is broken; it complains about either no screens or not enough. Here is my Xorg.0.log: ( http://pastebin.com/wLjtmtnW )
I think X -configure worked, because I have a somewhat complete xorg.conf file ( here: http://pastebin.com/hD01yPqs )

After rereading the Wiki, I found that in order for Intel drivers to work, one must not have modeset kernel parameters. ( https://wiki.archlinux.org/index.php/In … cs#Loading )

I need modeset to let me boot, but modeset stops me from running X... Any ideas on how to work around this?

jasonwryan · 2017-01-09 20:21:49

Remove all the unnecessary drivers and the conf file and start X again; paste that log.

loqs · 2017-01-09 20:27:57

Please do a single boot with the kernel parameters to disable modesetting removed, then reboot blindly, then post the journal for the boot with the parameters absent.
Edit:
spelling

Last edited by loqs (2017-01-09 20:28:22)

fromage · 2017-01-09 20:51:26

jasonwryan wrote:

Remove all the unnecessary drivers and the conf file and start X again; paste that log.

Here is the new xorg.conf http://pastebin.com/NRGRh6hg

loqs wrote:

Please do a single boot with the kernel parameters to disable modesetting removed, then reboot blindly, then post the journal for the boot with the parameters absent.
Edit:
spelling

Here is the output of journalctl for the boot without any kernel parameters. http://pastebin.com/pKUdDskw

loqs · 2017-01-09 21:13:09

Does Kernel_mode_setting#Early_KMS_start help?
Also I think jasonwryan wanted an xorg.log from startx being run with no config files in use not a log from from a run of X -configure.

jasonwryan · 2017-01-09 21:19:42

loqs wrote:

Also I think jasonwryan wanted an xorg.log from startx being run with no config files in use not a log from from a run of X -configure.

Yes.

fromage · 2017-01-09 21:35:40

loqs wrote:

Does Kernel_mode_setting#Early_KMS_start help?

No change. Adding i915 to the MODULES line still boots me to a black screen.

loqs wrote:

Also I think jasonwryan wanted an xorg.log from startx being run with no config files in use not a log from from a run of X -configure.

Whoops, here it is. http://pastebin.com/bi4mf23e

jasonwryan · 2017-01-09 21:48:37

Please paste the output of:

pacman -Qs 'xf86-*'

Gusar · 2017-01-09 21:52:44

There is no workaround, you need kernel modesetting. Turning it off, all you get is unaccelerated vesa mode (which probably won't be in your display's native resolution), if that. Support for Intel SoC (system-on-a-chip, which is what your Celeron N3050 is, it belongs to the Braswell family) video output is known to be buggy. So you're plain out of luck. Complain to Intel.

fromage · 2017-01-10 07:01:46

Gusar wrote:

There is no workaround, you need kernel modesetting.

Dang it. Are there no alternatives? The machine is so bad that the Windows 10 it shipped with practically stops it from running

jasonwryan wrote:

Please paste the output of:
pacman -Qs 'xf86-*'

Here it is, in case anyone's wondering. http://pastebin.com/ChR69H28

Trilby · 2017-01-10 12:42:58

Without the nomodeset option does boot actually fail, or are you just unable to see the tty?

As long as boot succeeds, you can just set up autologin and startx on login (both covered in the wiki) so when you boot up it goes right into X.

Not being able to see the init process is sub-optimal as it hinders some early detection and troubleshooting - but it certainly isn't a show-stopper.

I'd also wonder whether fbterm or similar tools would work for tty access.

Of course if modesetting just completely fails all together, than this is a moot point. But there are cases where the modesetting needed for Xorg prevents the normal tty display, but X can work fine.

seth · 2017-01-10 17:38:31

Modesetting support is madantory for Xorg/intel, but you can drop it from GRUB: https://wiki.archlinux.org/index.php/GR … ramebuffer

fromage · 2017-01-11 22:00:29

Sorry for the late response

Trilby wrote:

Without the nomodeset option does boot actually fail, or are you just unable to see the tty?

What actually happens is that it halts at the step "Flushing Journal to Persistent Storage", after which the screen just turns off. Does this count as a failed boot?
I've looked all over for a general solution for this problem but am yet to find one which works.

Trilby · 2017-01-11 22:25:33

No, there's nothing to distinguish that from the other alternative. It's likely everything works, you just can't see the tty.

loqs · 2017-01-11 22:37:30

If you could login in blindly or remotely then perform some action such as powerdown the system that would demonstrate the rest of the system is still functional.

fromage · 2017-01-11 23:01:49

I tried to login blindly and shutdown, but the computer did not respond. It seems like the computer just hangs... The journalctl of the boot also just cuts abruptly after saying it's loading the laptop's Hotkeys. I will continue investigating

fromage · 2017-01-12 07:47:22

On a whim I decided to plug in my monitor via the HDMI port, and voila! The machine boots like a charm. I'm able to log in through LightDM and do anything in an XFCE session.
But the catch is that my monitor needs to be plugged in for it to not hang during the boot. Is there any way I can trick the machine into thinking I've got a 1920x1080 screen plugged in, so it actually boots?
Sorry if this is going off topic.

seth · 2017-01-12 12:11:29

broken edid/inompatible uefi mode.
enforce a mode or drop the framebuffer console from grub.

fromage · 2017-01-12 12:56:55

seth wrote:

broken edid/inompatible uefi mode.
enforce a mode or drop the framebuffer console from grub.

Thank you.
I tried to drop the framebuffer, but without success.
The EDID didn't work either, but something I neglected to mention is that with the HDMi plugged in, even the laptop screen works. So I don't think this is to do with faulty firmware; but maybe to do with the faulty way in which the firmware is loaded at boot time.

R00KIE · 2017-01-12 13:22:56

There are dongles that emulate a monitor but buying one just to workaround this problem might be a bit too much. Try searching for "hdmi dummy" or "hdmi monitor emulator" if you think that might be a quick workaround until you report the bug upstream and someone gets around to fixing it.

seth · 2017-01-12 18:28:51

Can you run that UEFI in BIOS mode?

fromage · 2017-01-12 18:40:19

Sorry for the late response. I guess my problem is "Fixed".
All I needed was to reinstall Arch in BIOS mode. So I think Seth was right about a faulty UEFI mode.
Thanks for the help everybody.

Arch Linux

#1 2017-01-09 20:18:37

Can't configure XServer because of "i915.modeset"

#2 2017-01-09 20:21:49

Re: Can't configure XServer because of "i915.modeset"

#3 2017-01-09 20:27:57

Re: Can't configure XServer because of "i915.modeset"

#4 2017-01-09 20:51:26

Re: Can't configure XServer because of "i915.modeset"

#5 2017-01-09 21:13:09

Re: Can't configure XServer because of "i915.modeset"

#6 2017-01-09 21:19:42

Re: Can't configure XServer because of "i915.modeset"

#7 2017-01-09 21:35:40

Re: Can't configure XServer because of "i915.modeset"

#8 2017-01-09 21:48:37

Re: Can't configure XServer because of "i915.modeset"

#9 2017-01-09 21:52:44

Re: Can't configure XServer because of "i915.modeset"

#10 2017-01-10 07:01:46

Re: Can't configure XServer because of "i915.modeset"

#11 2017-01-10 12:42:58

Re: Can't configure XServer because of "i915.modeset"

#12 2017-01-10 17:38:31

Re: Can't configure XServer because of "i915.modeset"

#13 2017-01-11 22:00:29

Re: Can't configure XServer because of "i915.modeset"

#14 2017-01-11 22:25:33

Re: Can't configure XServer because of "i915.modeset"

#15 2017-01-11 22:37:30

Re: Can't configure XServer because of "i915.modeset"

#16 2017-01-11 23:01:49

Re: Can't configure XServer because of "i915.modeset"

#17 2017-01-12 07:47:22

Re: Can't configure XServer because of "i915.modeset"

#18 2017-01-12 12:11:29

Re: Can't configure XServer because of "i915.modeset"

#19 2017-01-12 12:56:55

Re: Can't configure XServer because of "i915.modeset"

#20 2017-01-12 13:22:56

Re: Can't configure XServer because of "i915.modeset"

#21 2017-01-12 18:28:51

Re: Can't configure XServer because of "i915.modeset"

#22 2017-01-12 18:40:19

Re: Can't configure XServer because of "i915.modeset"

Board footer