Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Just upgraded from 13.04 to 13.10 and all I got was a black screen. The hardware I'm running is Asus Zenbook UX31A (Intel GPU).

I do hear that the login screen drums do play, so the system does boot to login screen. When I try to boot using kernel 3.11.0-12 recovery mode, it tells me "initctl: event failed". Then if I go on an press ctrl+alt+f2, log in and command startx, it dies because "Fatal server error: no screens found". Here are some logs from /var/log/Xorg.0.log

Kernel 3.8.0-31 work ok, as did things before the upgrade.

share|improve this question

closed as off-topic by bain, chaskes, Sneetsher, bodhi.zazen, Radu Rădeanu Jul 15 '14 at 17:43

This question appears to be off-topic. The users who voted to close gave these specific reasons:

If this question can be reworded to fit the rules in the help center, please edit the question.

I had an acer netbook. The upgrade took forever and I ended up with said black screen. I didn't bother with all the above complexities. Instead made a 13.10 live boot stick and installed wiping out 13.04. Worked like a charm. Only down side had to reget extras I had before like a video editor I like. – user251986 Feb 25 '14 at 0:51
up vote 2 down vote accepted

It's a kernel bug, as reported here:

Quick solution is to switch to BIOS mode instead of UEFI mode.
= Disable Secure Boot and enable "Launch CSM".

You can peruse the Archlinux thread above if you want a more permanent fix and you feel like patching the kernel yourself. I don't consider myself technically good enough to do that safely (or quickly), so I'm putting up with running in BIOS mode for now and waiting until another Kernel is released.

share|improve this answer
Awesome, thanks! Never done any kernel patching before, but weekend is coming and it is not like I have any better things to do ;) – Harri Oct 18 '13 at 6:43
@Harri I'm facing the same. ANy simpler solutions?… – MalTec Nov 23 '13 at 14:59
Install kernel 3.12 and use that… – Harri Nov 24 '13 at 17:47

It is a known bug ( ) with medium priority (althought this bug leaves the system unusable for people). If you set your system as affected in launchpad you will get status updates regarding this issue.

Set the compatibility mode (as mentioned by user203894) is one solution or just use an older kernel (max 3.9.9).

share|improve this answer
Can also install fixed kernel packages from the duplicate bug:… – Beni Cherniavsky-Paskin Oct 28 '13 at 17:18

protected by Community Feb 25 '14 at 2:52

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged or ask your own question.