Bug 8503

Summary: Graphic interface problems on 1.8.1 on NUC NUC5i5RYH
Product: [Build System, Metadata & Runtime] BSPs Reporter: Cristina Agurida <cristina-danielax.agurida>
Component: bsps-runtimeAssignee: Saul Wold <sgw>
Status: VERIFIED WONTFIX QA Contact: Cristina Agurida <cristina-danielax.agurida>
Severity: normal    
Priority: Medium CC: alexandru.c.georgescu, georgex.l.musat, yp.kernel.watcher, yp.watcher
Version: 1.8.1   
Target Milestone: 1.8.2   
Hardware: NUC   
OS: x86_64   
Whiteboard: Possible release note for 1.8.1 use meta-intel for Intel Hardware!
OS type for building Yocto: --- Type of Regression: Regression (Used to work)
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
first attachment
none
second attachment none

Description Cristina Agurida 2015-10-13 13:21:51 UTC
Created attachment 2795 [details]
first attachment

BUILD: 1.8.1: b74ea963cefffad9fbd91d4eb9b240f6a8c86cd0
ENVIRONMENT: genericx86-64 on NUC
IMAGE: core-image-sato-sdk
HARDWARE MODEL: NUC5i5RYH

STEPS TO REPRODUCE: 
boot up system with default runlevel

EXPECTED OUTCOME: 
X server can start up well and desktop display has no problemS .

Actual outcome:
 After boot up, the graphic interface does not show up properly as you can notice in the first attachment.
 Mouse and keyboard are working but the interface is not responding as expected.
 After pressing ctrl+alt+f1 the text console is displayed and works fine, but after trying to start X again it fails with an error( as you can see in the second attachment)
Comment 1 Cristina Agurida 2015-10-13 13:23:02 UTC
Created attachment 2796 [details]
second attachment
Comment 2 Cristina Agurida 2015-10-16 12:11:53 UTC
On D54250WYK NUC model the issue cannot be reproduced.
Comment 3 Saul Wold 2015-10-29 19:35:10 UTC
This is not actually a regression since you are testing newer hardware relative 
to what was released at the time of this release.  I did some further testing 
with the 3.19 kernel which has support for the newer HD 6000 Graphics device 
and it works correctly for genericx86-64, so a workaround would be to use 3.19 
as the PREFERRED_VERSION for 1.8.1. or to use the meta-intel intel-corei7-64 
MACHINE type.

Since we don't upgrade the kernel version (we might update the srcrev, but not 
the version) during a dot.dot, this will not be fixed.
Comment 4 Cristina Agurida 2015-11-04 12:24:14 UTC
As per last comment set it as verified won't fix.