Kernel Bug Tracker – Bug 60881
Dell XPS 13 (L322X) display does not work anymore with kernel 3.10
Last modified: 2013-09-10 06:58:04 UTC
I updated my Dell XPS 13 (aka "Sputnik") and after the reboot I only got a completely garbled display as if the display frequency isn't right for the monitor.
Once I boot into the previous 3.9 kernel things start working again as expected. It seems the driver got broken in kernel 3.10.
When started with the "nomodeset" kernel option the display is no longer distorted but X doesn't start anymore but that might be related to Fedora 19 not handling the non-KMS fallback case well (Xorg aborts with no usable screen configuration).
We need a big pile of infomartion here first:
- What's "the monitor"? xrandr --verbose output from a working kernel is the best to get all info.
- Screenshot (with a camera or so) of the corruptions would be useful.
- Please boot the broken kernel with drm.debug=0xe and then grab the dmesg from the logfiles after rebooting (or ssh into the machine if you can).
Also properly marking as a regression.
Created attachment 107821 [details]
xrandr --verbose output
Created attachment 107831 [details]
lspci output for vga device
Created attachment 107841 [details]
boot log with drm.debug=0xe
On fedora-devel somebody pointed me to this bug which might be what I'm seeing:
The patches in this bug don't seem to have made it into any release yet though.
Dell XPS13 eDP broken at 3.10, dithering 24->18 bpp, smells like dupe of bug 59841.
Do you use UEFI boot? Can you check if enabling CSM in the BIOS helps?
Looks like it. I enabled "Load Legacy Option ROM" (which I assume is CSM) and I can indeed boot the latest 3.10 Kernel normally.
Interesting. Please attach /sys/kernel/debug/dri/0/i915_opregion for non-working and working setting of the BIOS option. Thanks.
Created attachment 107871 [details]
Load Legacy Option ROM => disabled
Created attachment 107881 [details]
Load Legacy Option ROM => enabled
Duplicate. We are still trying to figure out the least ugly fix that doesn't break other machines. In the mean time, the workarounds are using legacy boot or patching your kernel. Thanks for the report.
*** This bug has been marked as a duplicate of bug 59841 ***