Bug 6807 - crownbay-noemgd with 3.17 kernel doesn't boot into graphics
Summary: crownbay-noemgd with 3.17 kernel doesn't boot into graphics
Status: VERIFIED FIXED
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-meta-intel (show other bugs)
Version: unspecified
Hardware: Crownbay x86
: Medium+ major
Target Milestone: 1.7 M4
Assignee: Nitin Kamble
QA Contact: Lucian Musat
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2014-10-06 21:27 UTC by Tom Zanussi
Modified: 2015-02-24 08:29 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know

Attachments
Xorg.log (6.81 KB, text/x-log)
2014-10-06 21:27 UTC, Tom Zanussi 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tom Zanussi 2014-10-06 21:27:27 UTC 
Created attachment 2170 [details]
Xorg.log

Build Configuration:
BB_VERSION        = "1.24.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "Fedora-19"
TARGET_SYS        = "i586-poky-linux"
MACHINE           = "crownbay-noemgd"
DISTRO            = "poky"
DISTRO_VERSION    = "1.7"
TUNE_FEATURES     = "m32 core2"
TARGET_FPU        = ""
meta              
meta-yocto        
meta-yocto-bsp    = "master3:505a6b696ae990442de720e5e1135a3e44d5f75c"
meta-intel        
meta-crownbay     = "master5:8e5fe6c0f5cf710e1a46c5f203e52f069874768a"
Comment 1 Nitin Kamble 2014-10-09 20:36:43 UTC 
I was able to reproduce this issue locally. After debugging on the target I found out that gma500 is taking ower the graphics h/w causing this failure. Blacklisting the gma500 driver fixes the issue.
Comment 2 Nitin Kamble 2014-10-14 16:47:43 UTC 
commit 911f7f8b73d7f3f4d36e35a070c524be3e4df3a1
Author: Nitin A Kamble <nitin.a.kamble@intel.com>
Date:   Thu Oct 9 14:44:42 2014 -0700

    crownbay-noemgd: Disable the gma500_gfx module
    
    The gmx500 graphics driver does not work on this BSP, but it takes the
    ownership of the graphics hardware at boot time, blocking other
    drivers from using the graphics hardware.
    
    Fix the issue by blacklisting the gma500_gfx kernel module in the kmod
    configuration, so that it doesn't get loaded at boot time.
    
    Fixes Bug:
    [YOCTO #6807]
    
    Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
    Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Comment 3 Lucian Musat 2015-02-24 08:29:28 UTC 
Verified on 1.8.M2_RC1 (d9d5b8b499af3ae01a1e33d0d3969c54c2d4ab1b).