Bug 60715 - unable to get video output on console with kernel 3.10 or higher
Summary: unable to get video output on console with kernel 3.10 or higher
Status: RESOLVED INSUFFICIENT_DATA
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - Intel) (show other bugs)
Hardware: x86-64 Linux
: P1 normal
Assignee: Damien Lespiau
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-07 18:51 UTC by Sean
Modified: 2014-08-14 08:23 UTC (History)
3 users (show)

See Also:
Kernel Version: 3.10.5
Subsystem:
Regression: Yes
Bisected commit-id:

Attachments
kernel config file (86.00 KB, text/plain)
2013-08-07 18:51 UTC, Sean 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Sean 2013-08-07 18:51:04 UTC 
I am currently running gentoo and use the vanilla kernel from kernel.org.  I am on version 3.9.11 and my framebuffer works great at 1920x1080 (Asus zenbook with i5 ivybridge and hd4000 intel graphics).

If i update to a 3.10 kernel (or higher i have tried 3.11 mainline as well) i cannot get any display unless i add "nomodeset" to the boot options.  This however gives me a not so nice looking console.  I have tried many options of compiling things in and out of the kernel with no avail.  I have attached my 3.9.11 kernel config (which i apply to the 3.10.5 and run make oldconfig without changing anything).

I have read this may be caused by ACPI, however i have tried acpi=off and compiling a kernel without ACPI and it still has the same behavior.

Thanks,

Sean
Comment 1 Sean 2013-08-07 18:51:42 UTC 
Created attachment 107144 [details]
kernel config file
Comment 2 Alan 2013-11-13 16:18:34 UTC 
Please confirm if thep problem is present with a newer kernel and if so please attach a dmesg
Comment 3 Jani Nikula 2013-11-14 06:53:54 UTC 
This *might* be a dupe of bug 59841. Are you booting in UEFI mode? Please try CSM/legacy as a workaround, or try kernel version 3.12.

Please use drm.debug=0xe module parameter for attaching the dmesg.
Comment 4 Jani Nikula 2014-08-14 08:23:35 UTC 
Timeout. Please reopen if the problem persists with recent kernels.
Note You need to log in before you can comment on or make changes to this bug.