| Summary: | x fails to start on liveboot for crownbay-noemgd | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BSPs | Reporter: | Alexandru Georgescu <alexandru.c.georgescu> | ||||
| Component: | bsps-meta-intel | Assignee: | Nitin Kamble <nitin.a.kamble> | ||||
| Status: | VERIFIED WORKSFORME | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | Medium | CC: | dvhart, tom.zanussi | ||||
| Version: | 1.4.1 | ||||||
| Target Milestone: | 1.5 | ||||||
| Hardware: | Crownbay | ||||||
| OS: | Multiple | ||||||
| Whiteboard: | |||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |||||
| Attachments: |
|
||||||
|
Description
Alexandru Georgescu
2013-06-18 08:42:50 UTC
This is typically due to a lack of memory. Live images should really not be used to test sato-sdk. In this case, the error may not be related: [1449748.591] (EE) Screen(s) found, but none have a usable configuration. Does this also fail on just sato? Does it fail if run from an installed image? Perhaps an xorg config failure or a unique monitor setup? Is this hardware configuration known to work previously? Is this a regression? Hi Darren, We don't test sato-sdk using live images, just that they can live boot. We perform the tests only on the installed ones. And as an update, you can mark this one as worksforme since the latest weekly build can show up the X. Thanks! Closing this as per Alex's comment. . |