Bug 3207 - meta-cedartrail: corrupted framebuffer
Summary: meta-cedartrail: corrupted framebuffer
Status: RESOLVED FIXED
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-meta-intel (show other bugs)
Version: 1.3
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.6
Assignee: Ong Boon Leong
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2012-10-02 16:14 UTC by Ross Burton
Modified: 2014-06-03 09:57 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: Regression (Used to work)
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments
Photo of splash (337.48 KB, image/jpeg)
2012-10-04 09:16 UTC, Ross Burton
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ross Burton 2012-10-02 16:14:53 UTC
I've an Acer Aspire One D270 netbook which is Cedar Trail based.  MeeGo 1.2 (for CDT) works perfectly well on it.  When I install a core-image-sato built with meta-cedartrail, I get a corrupted splash screen.

Presumably we're missing something in the 400kb cdv patch at http://build.meego.com/package/files?package=kernel-adaptation-pc&project=MeeGo%3A1.2.0%3Aoss%3AUpdate%3ATesting...

(insert standard why isn't this upstream rant)
Comment 1 Darren Hart 2012-10-02 18:32:22 UTC
Kishore, can you have a look?
Comment 2 kishore 2012-10-02 18:39:38 UTC
Hi Rahul,

Can you look into this?

Thanks
Kishore.
Comment 3 Rahul Saxena 2012-10-03 21:29:39 UTC
Ross, I believe Meego is using the same linux-3.0.0-cdv.patch as Yocto. Am wondering why it would impact only Yocto.  I am not sure where to start looking to root cause this problem, I changed the splash screen image to try the poky image but I still see a grainy rectangle area at the bottom that covers the whole screen width. I assume that is the issue you are seeing  too ?
Comment 4 Ross Burton 2012-10-04 09:16:53 UTC
Created attachment 868 [details]
Photo of splash

It's really hard to explain corruption so here's a photo.  The visible splash takes up about half of the vertical size of the screen.
Comment 5 Rahul Saxena 2012-10-06 23:59:19 UTC
Ross, can you try the following Kernel command line parameters (can add in cedartrail.conf) as in Crownbay BSP:


APPEND += "video=vesafb vga=0x318"

also try adding in addition to or instead of above:
APPEND += "vmalloc=256MB"

The behavior in my CRB is different than yours, I will try these out to see if it makes any difference.
Comment 6 Ross Burton 2012-10-08 10:00:03 UTC
I get a slightly different framebuffer console, but the splash is still corrupted.
Comment 7 Rahul Saxena 2012-12-20 19:30:20 UTC
Playing around with Kernel boot parameters mentioned in my previous comment, resulted in some changes to the splash screen, but always showed some form of corruption on some monitors.  Will try out a few more things..
Comment 8 Rahul Saxena 2013-02-01 02:18:39 UTC
While fixing bug # 3607, I discovered that the fix for #3607 fixes the corrupt splash screen issue on my system. The fix is summarized below:

Assuming you are using a VGA display add the following to the kernel boot command line and try booting again:

video=LVDS-1:d video=VGA-1:e 

"d" is for disable and "e" is for enable in above command line.

If you have a LVDS display add following to command line instead:

video=LVDS-1:e video=VGA-1:d 


Pl also see #3607 for further background on this fix..
Comment 9 kishore 2013-05-03 00:00:41 UTC
Changing the Owner to Foo Chien.
Comment 10 Darren Hart 2013-09-23 18:45:34 UTC
Foo Chien, will you be able to have a look at this in the next week or so? Are you still the correct owner?
Comment 11 Ong Boon Leong 2013-11-26 10:13:07 UTC
Based on guidance from this document, http://download.intel.com/support/motherboards/desktop/sb/enabling_hardware_accelerated_playback_fedora_16_v.pdf

If the user add the following into 
meta-cedartrail/conf/machine/cedartrail.conf

APPEND += " video=LVDS-1:d vmalloc=256MB"

The corrupted frame-buffer issue seen will be resolved. 
We have tested this on Cedar Rock platform.
Comment 12 Ong Boon Leong 2014-05-08 15:44:55 UTC
On comment-11, the steps to disable the issue are listed. The steps are recommended by official product documentation. Please review if that is ok and can be closed
Comment 13 Ong Boon Leong 2014-06-03 00:19:05 UTC
Ross, can you take a look at the resolution for the bug report?
We posted this since 2013/11
Comment 14 Ross Burton 2014-06-03 09:57:44 UTC
I'll close as you've provided what looks like a good fix but I don't have the hardware anymore so I can't test it.