Bug 5108 - Lack of xf86-video-mga package in genericX86-64/genericX86
Summary: Lack of xf86-video-mga package in genericX86-64/genericX86
Status: RESOLVED WONTFIX
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-meta-intel (show other bugs)
Version: 1.5.2
Hardware: Other x86_64
: Medium major
Target Milestone: Future
Assignee: Darren Hart
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-09-04 06:59 UTC by Yunguo
Modified: 2013-11-06 16:31 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Yes (doc changes required)


Attachments
Xorg.0.log (8.13 KB, text/plain)
2013-09-10 02:21 UTC, Yunguo
no flags Details
dmesg (77.47 KB, text/plain)
2013-09-10 02:22 UTC, Yunguo
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Yunguo 2013-09-04 06:59:39 UTC
Romley platforms use MGA but apparent it is not supported by neither genericX86 nor generic X86-64.
Comment 1 Darren Hart 2013-09-05 00:43:58 UTC
Patches sent to poky/oe-core
Comment 2 Darren Hart 2013-09-06 20:28:49 UTC
Getting pushback on MGA in oe-core. Is there a reason we need this and the vesa option will not work?

We could fight this as we already have omap and intel in oe-core (seems rather silly not to include MGA to me honestly).

But, first I need to know if/why vesa doesn't fill the need.
Comment 3 Yunguo 2013-09-09 02:07:05 UTC
(In reply to comment #2)
> Getting pushback on MGA in oe-core. Is there a reason we need this and the
> vesa option will not work?
> 
> We could fight this as we already have omap and intel in oe-core (seems
> rather silly not to include MGA to me honestly).
> 
> But, first I need to know if/why vesa doesn't fill the need.

You can reproduced it on SDP S2R3, a Romley-EP ivy board. Without mga package, graphics doesn't work.

Checkout romley-ivb.conf:

XSERVER ?= "${XSERVER_IA32_BASE} \
           ${XSERVER_IA32_EXT} \
           ${XSERVER_IA32_MATROX_MGA} \
           "


Yunguo
Comment 4 Darren Hart 2013-09-10 01:17:14 UTC
It was my understanding that Romley should work with VESA graphics. Have you tried to use VESA?

How exactly is it failing? What is the contents of the xorg.conf file.
Comment 5 Yunguo 2013-09-10 02:21:36 UTC
Created attachment 1480 [details]
Xorg.0.log
Comment 6 Yunguo 2013-09-10 02:22:26 UTC
Created attachment 1481 [details]
dmesg
Comment 7 Yunguo 2013-09-10 02:25:14 UTC
(In reply to comment #4)
> It was my understanding that Romley should work with VESA graphics. Have you
> tried to use VESA?

That was my understanding as well, but even with VESA package, it didn't work.


root@genericx86:~# rpm -qa |grep vesa
kernel-module-uvesafb-3.10.9+git0+1b9b113837_6c1528b2b7-r0.genericx86
xf86-video-vesa-2.3.2-r21.0.core2
root@genericx86:~# 
root@genericx86:~# 
root@genericx86:~# uname -a
Linux genericx86 3.10.9-yocto-standard #1 SMP PREEMPT Wed Aug 28 17:47:21 CST 2013 i686 GNU/Linux
root@genericx86:~# 


> 
> How exactly is it failing? What is the contents of the xorg.conf file.

No xorg.conf found. 
Please find the attachments for dmesg and Xorg.0.log.


Yunguo
Comment 8 Darren Hart 2013-09-17 17:00:33 UTC
mga isn't going to make it into oe-core

it might be appropriate for meta-yocto-bsp, but only if vesa can't be made to work

for now, romley users wanting graphics should use the romley bsp in meta-intel

this needs more information on why vesa doesn't work
Comment 9 Darren Hart 2013-11-06 16:31:29 UTC
Closing this out as it will not make it into oe-core and there has been no additional response. Please reopen if there is still interest and resources to help follow-up.