<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - kernel 3.15 regression, drm i915 chooses wrong monitor resolution"
href="https://bugs.freedesktop.org/show_bug.cgi?id=78655#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - kernel 3.15 regression, drm i915 chooses wrong monitor resolution"
href="https://bugs.freedesktop.org/show_bug.cgi?id=78655">bug 78655</a>
from <span class="vcard"><a class="email" href="mailto:Knut_Petersen@t-online.de" title="Knut Petersen <Knut_Petersen@t-online.de>"> <span class="fn">Knut Petersen</span></a>
</span></b>
<pre>Created <span class=""><a href="attachment.cgi?id=98973" name="attach_98973" title="dmesg with drm.debug=0xe">attachment 98973</a> <a href="attachment.cgi?id=98973&action=edit" title="dmesg with drm.debug=0xe">[details]</a></span>
dmesg with drm.debug=0xe
Hardware AOpen i915GMm-hfs motherboard, TFT monitor attached to VGA-1
As you can see, the monitor supports a resolution of 1280x1024, and that is
what kernels up to 3.14 use. After 3.14 that changes, and the reason is quite
obvious
[ 4.002464] [drm:intelfb_create] no BIOS fb, allocating a new one
[ 4.002470] [drm:i915_gem_object_create_stolen] creating stolen object:
size=1d5000
[ 4.002481] [drm:i915_pages_create_for_stolen] offset=0x1f5000, size=1921024
[ 4.003880] [drm:intelfb_create] allocated 800x600 fb: 0x00200000, bo
f638cc00
[ 4.007426] fbcon: inteldrmfb (fb0) is primary device
Without testing I would think this is another regression introduced by commit
d978ef14456a38034f6c0e94a794129501f89200
Jesse, do you agree?
cu,
Knut</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>