Bug 807447 - F17 Alpha- [drm:intel_framebuffer_init] *ERROR* unsupported pixel format
F17 Alpha- [drm:intel_framebuffer_init] *ERROR* unsupported pixel format
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel (Show other bugs)
i686 Linux
unspecified Severity low
: ---
: ---
Assigned To: Adam Jackson
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-03-27 15:50 EDT by Martin Thain
Modified: 2012-03-28 15:25 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-03-28 15:25:30 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Smolt Profile (2.68 KB, text/plain)
2012-03-27 15:50 EDT, Martin Thain
no flags Details
Output from dmesg (56.89 KB, text/plain)
2012-03-27 15:51 EDT, Martin Thain
no flags Details

  None (edit)
Description Martin Thain 2012-03-27 15:50:58 EDT
Created attachment 573160 [details]
Smolt Profile

Description of problem:

During boot of Fedora 17 Alpha the following error message is noted
[drm:intel_framebuffer_init] *ERROR* unsupported pixel format

Version-Release number of selected component (if applicable):
Linux localhost.localdomain 3.3.0-0.rc3.git7.2.fc17.i686 #1 SMP Fri Feb 17 19:00:46 UTC 2012 i686 i686 i386 GNU/Linux

How reproducible:
Every time on my EEEPC900

Steps to Reproduce:
1.Boot F17 
3.search for error
Actual results:
[drm:intel_framebuffer_init] *ERROR* unsupported pixel format

Expected results:
No error

Additional info: see attachment of smolt profile and error log
Comment 1 Martin Thain 2012-03-27 15:51:54 EDT
Created attachment 573161 [details]
Output from dmesg
Comment 2 Adam Jackson 2012-03-28 15:25:30 EDT
Both known causes of this should be fixed in kernel-3.3.0-8.fc17 (probably earlier too, that's just what's current).

Please reopen if upgrading doesn't fix this for you.  Thanks!

Note You need to log in before you can comment on or make changes to this bug.