On a fully updated Zotac ZBox machine sporting an Intel Atom IGD, I have noticed a regression between kernel 3.7.2 and 3.7.6 in Fedora 18 64 bits. Symptoms: - At startup, instead of getting the "textured gray" login screen of GDM, you get only the blue Fedora wallpaper. No toolbars or widgets. - If you test with a touchscreen monitor (I tried with two monitors connected through VGA, one of which is an Iyama ProLite T2250MTS touchscreen), you'll see that the mouse cursor position is actually disconnected from the position of the finger (the cursor is 10 centimeters on the left of the finger) - If you switch to another VT, the screen resolution is incorrect: it is missing one line of text at the top, and the bottom and right edges are incorrect (the bottom is 25% too high and the right-edge is 1/8th too far to the left) There doesn't seem to be errors related to the graphics at the end of dmesg. Booting back into kernel 3.7.2 works fine, I get GDM's "gray" login screen.
Please attach the dmesg output, and /var/log/Xorg.0.log, from both the 3.7.2 and 3.7.6 kernels.
Created attachment 696884 [details] dmesg for kernel 3.7.2
Created attachment 696885 [details] dmesg for kernel 3.7.6
Created attachment 696886 [details] xorg log for kernel 3.7.2
Created attachment 696887 [details] xorg log for kernel 3.7.6
Created attachment 696888 [details] lspci -vvvv
Argh. So there's this patch in 3.7.6 now: commit 7d70ef5bba98643d31917590bea352c9857ddbc7 Author: Daniel Vetter <daniel.vetter> Date: Mon Jan 7 10:27:13 2013 +0100 Revert "drm/i915: no lvds quirk for Zotac ZDBOX SD ID12/ID13" commit 48e858340dae43189a4e55647f6eac736766f828 upstream. This reverts commit 9756fe38d10b2bf90c81dc4d2f17d5632e135364. The bogus lvds output is actually a lvds->hdmi bridge, which we don't really support. But unconditionally disabling it breaks some existing setups. Note that in the X log from 3.7.6 you have an LVDS output "detected" where you didn't before. It turns out your particular Atom GPU doesn't have native HDMI support, but since it _does_ have LVDS support, Chrontel built a converter chip from one to the other. As root, please run: # dd if=/dev/mem of=/tmp/rom bs=64k skip=12 count=1 And attach the resulting /tmp/rom to this bug. Hopefully there's something in there that we can key off to decide whether this adaptor chip is actually present, and adapt accordingly.
Created attachment 697976 [details] memory dump with kernel 3.7.6 As requested.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.