| Summary: | [FRI2]X server fails to start | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BSPs | Reporter: | Alexandru Palalau <alexandrux.palalau> | ||||||
| Component: | bsps-meta-intel | Assignee: | Darren Hart <dvhart> | ||||||
| Status: | VERIFIED OBSOLETE | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | Medium+ | CC: | ross.burton, song.liu, tom.zanussi | ||||||
| Version: | 1.3 | ||||||||
| Target Milestone: | 1.3 M4 | ||||||||
| Hardware: | Other | ||||||||
| OS: | Multiple | ||||||||
| Whiteboard: | (Scheduled) | ||||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||||
| Verified: | Documentation change: | --- | |||||||
| Attachments: |
|
||||||||
|
Description
Alexandru Palalau
2012-08-23 14:42:24 UTC
Created attachment 728 [details]
syslog
Please include some description of the problem encountered in the bug itself. It's good to include the logs (thanks for that) but please summarize the failure in the bug itself. In this case the X Server found the EMGD device but was unable to use any of the defined screen configurations. 1) Is this with the Kontron AMI BIOS or Intel Fast Boot firmware? 2) Which version of the firmware? 3) How are you connected to the FRI2 for video output? 4) Which micro HDMI port are you using? 5) Do you get boot messages to the display? 6) Have you tried with a different display? Well, the behavior was first encountered in WW34 Weekly tests and nothing was changed on the FRI2 terminal I am testing. Updated the BIOS version from the Kontron Website (the FastBoot BIOS version does not allow internal HDD (memory card) boot).
1,2)Currently I am running:
BIOS Project Version: updated to FRI2R102.003.KAI (From the Kontron Website)
EFI Vendor: American Megatrends
EFI Revision: 4.641
EFI Specification Revision: 2.0
3,4)microHDMI port 2 (Secondary Monitor). The first port does not provide output, not even from BIOS
5) On microHDMI port 2 (secondary monitor) boot messages are displayed.
6) Same behavior on three monitors. One of them available on the supported monitor list provided by Kontron.
The behavior is encountered on Sato and Sato-SDK images.
FRI2 has just been updated to linux-yocto-3.4 and emgd 1.14. I have verified the X server starts and the sato desktop is displayed. I'm closing this out (as obsolete since a specific fix wasn't identified). Please re-open if this resurfaces. The behavior cannot be reproduced under 1.3_M5 branch that is currently under test. Switched to verified. |