| Submitter | Khem Raj |
|---|---|
| Date | May 3, 2012, 3:35 a.m. |
| Message ID | <cover.1336015963.git.raj.khem@gmail.com> |
| Download | mbox |
| Permalink | /patch/26949/ |
| State | New |
| Headers | show |
Pull-request
git://git.openembedded.org/openembedded-core-contrib kraj/qemu-xserver-xorgComments
On 05/02/2012 08:35 PM, Khem Raj wrote: > Currently we use kdrive for all qemu machines except x86 and x86_64 > this patchset enables it for other qemu machines too > > I did not delete the kdrive recipes intentionally since I saw that > there were some images which were using kdrive as xserver > > I have successfully sato image in qemumips qemuarm and qemuppc > Khem, Not sure what I am doing differently, but I am not getting the xserver to start on at least ppc and mips (two that I tried just now). Are you build a Yocto sato image or oe-core sato image? I get the following on a ppc: Fatal server error: no screens found xinit: giving up xinit: unable to connect to X server: No such file or directory xinit: server error Sau! > The following changes since commit 35b5fb2dd2131d4c7dc6635c14c6e08ea6926457: > > eglibc-package: remove /var (2012-05-01 12:36:18 +0100) > > are available in the git repository at: > git://git.openembedded.org/openembedded-core-contrib kraj/qemu-xserver-xorg > http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=kraj/qemu-xserver-xorg > > Khem Raj (3): > qemumachines: Enable xserver-xorg as default xserver > xserver-xf86-config: Add xorg.conf for arm,mips,ppc,sh qemu machines > qemux86-64,qemux86: Override XSERVER variable > > meta/conf/machine/include/qemu.inc | 9 ++- > meta/conf/machine/qemux86-64.conf | 2 +- > meta/conf/machine/qemux86.conf | 2 +- > .../xserver-xf86-config/qemuarm/xorg.conf | 69 ++++++++++++++++++++ > .../xserver-xf86-config/qemumips/xorg.conf | 69 ++++++++++++++++++++ > .../xserver-xf86-config/qemumips64/xorg.conf | 69 ++++++++++++++++++++ > .../xserver-xf86-config/qemuppc/xorg.conf | 69 ++++++++++++++++++++ > .../xserver-xf86-config/qemush4/xorg.conf | 69 ++++++++++++++++++++ > .../xorg-xserver/xserver-xf86-config_0.1.bb | 2 +- > 9 files changed, 356 insertions(+), 4 deletions(-) > create mode 100644 meta/recipes-graphics/xorg-xserver/xserver-xf86-config/qemuarm/xorg.conf > create mode 100644 meta/recipes-graphics/xorg-xserver/xserver-xf86-config/qemumips/xorg.conf > create mode 100644 meta/recipes-graphics/xorg-xserver/xserver-xf86-config/qemumips64/xorg.conf > create mode 100644 meta/recipes-graphics/xorg-xserver/xserver-xf86-config/qemuppc/xorg.conf > create mode 100644 meta/recipes-graphics/xorg-xserver/xserver-xf86-config/qemush4/xorg.conf >
On Tue, May 8, 2012 at 3:06 PM, Saul Wold <sgw@linux.intel.com> wrote: >> > Khem, > > Not sure what I am doing differently, but I am not getting the xserver to > start on at least ppc and mips (two that I tried just now). > > Are you build a Yocto sato image or oe-core sato image? > > I get the following on a ppc: > > Fatal server error: > no screens found > xinit: giving up > xinit: unable to connect to X server: No such file or directory > xinit: server error > hmmm I have booted core-image-sato but I have bare OE-Core Do you have http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/qemu-xserver-xorg&id=8a60dabb7902b7be42d06cb735e96248e2e67dba is some layer on top changing it in some way ?
On Tue, May 8, 2012 at 3:09 PM, Khem Raj <raj.khem@gmail.com> wrote: > On Tue, May 8, 2012 at 3:06 PM, Saul Wold <sgw@linux.intel.com> wrote: >>> >> Khem, >> >> Not sure what I am doing differently, but I am not getting the xserver to >> start on at least ppc and mips (two that I tried just now). >> >> Are you build a Yocto sato image or oe-core sato image? >> >> I get the following on a ppc: >> >> Fatal server error: >> no screens found >> xinit: giving up >> xinit: unable to connect to X server: No such file or directory >> xinit: server error >> > > hmmm I have booted core-image-sato but I have bare OE-Core > Do you have > > > http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/qemu-xserver-xorg&id=8a60dabb7902b7be42d06cb735e96248e2e67dba > > is some layer on top changing it in some way ? hmmm another think I have is this patch http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/misc&id=955dee621361e01627ebfde152f25873070cf301 which deletes kdrive recipes. I did not propose it for inclusion yet but I wonder if there is any mix and match happening when these recipes are not deleted. You can cherry-pick it and see if that helps.
On 05/08/2012 03:18 PM, Khem Raj wrote: > On Tue, May 8, 2012 at 3:09 PM, Khem Raj<raj.khem@gmail.com> wrote: >> On Tue, May 8, 2012 at 3:06 PM, Saul Wold<sgw@linux.intel.com> wrote: >>>> >>> Khem, >>> >>> Not sure what I am doing differently, but I am not getting the xserver to >>> start on at least ppc and mips (two that I tried just now). >>> >>> Are you build a Yocto sato image or oe-core sato image? >>> >>> I get the following on a ppc: >>> >>> Fatal server error: >>> no screens found >>> xinit: giving up >>> xinit: unable to connect to X server: No such file or directory >>> xinit: server error >>> >> >> hmmm I have booted core-image-sato but I have bare OE-Core >> Do you have >> >> >> http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/qemu-xserver-xorg&id=8a60dabb7902b7be42d06cb735e96248e2e67dba >> >> is some layer on top changing it in some way ? > > hmmm another think I have is this patch > http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/misc&id=955dee621361e01627ebfde152f25873070cf301 > > which deletes kdrive recipes. I did not propose it for inclusion yet > but I wonder if there is any mix and match happening when these > recipes are not deleted. > You can cherry-pick it and see if that helps. > So I found that task-core-x11.bb also sets XSERVER XSERVER ?= "xserver-kdrive-fbdev" And this was being picked up it seems when I did the build. I commented that line out and it worked correctly. That seems wrong, since I thought the ??= should not allow the ?= to override, or do I have it backwards? Sau! >
On Tue, May 8, 2012 at 4:50 PM, Saul Wold <sgw@linux.intel.com> wrote: > On 05/08/2012 03:18 PM, Khem Raj wrote: >> >> On Tue, May 8, 2012 at 3:09 PM, Khem Raj<raj.khem@gmail.com> wrote: >>> >>> On Tue, May 8, 2012 at 3:06 PM, Saul Wold<sgw@linux.intel.com> wrote: >>>>> >>>>> >>>> Khem, >>>> >>>> Not sure what I am doing differently, but I am not getting the xserver >>>> to >>>> start on at least ppc and mips (two that I tried just now). >>>> >>>> Are you build a Yocto sato image or oe-core sato image? >>>> >>>> I get the following on a ppc: >>>> >>>> Fatal server error: >>>> no screens found >>>> xinit: giving up >>>> xinit: unable to connect to X server: No such file or directory >>>> xinit: server error >>>> >>> >>> hmmm I have booted core-image-sato but I have bare OE-Core >>> Do you have >>> >>> >>> >>> http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/qemu-xserver-xorg&id=8a60dabb7902b7be42d06cb735e96248e2e67dba >>> >>> is some layer on top changing it in some way ? >> >> >> hmmm another think I have is this patch >> >> http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/misc&id=955dee621361e01627ebfde152f25873070cf301 >> >> which deletes kdrive recipes. I did not propose it for inclusion yet >> but I wonder if there is any mix and match happening when these >> recipes are not deleted. >> You can cherry-pick it and see if that helps. >> > So I found that task-core-x11.bb also sets XSERVER > > XSERVER ?= "xserver-kdrive-fbdev" > > And this was being picked up it seems when I did the build. > > I commented that line out and it worked correctly. > > That seems wrong, since I thought the ??= should not allow the ?= to > override, or do I have it backwards? I think that was the real problem why my ??= was not working thanks for finding it out. I have gone ahead and posted a v2 of this patch series which should now work out better. > > Sau! > > > > >> >
On 05/02/2012 08:35 PM, Khem Raj wrote: > Currently we use kdrive for all qemu machines except x86 and x86_64 > this patchset enables it for other qemu machines too > > I did not delete the kdrive recipes intentionally since I saw that > there were some images which were using kdrive as xserver > > I have successfully sato image in qemumips qemuarm and qemuppc > Khem, Not sure if you saw this error: ERROR: Multiple .bb files are due to be built which each provide virtual/libgl (/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-mips/build/meta/recipes-graphics/mesa/mesa-dri_7.11.bb /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-mips/build/meta/recipes-graphics/mesa/mesa-xlib_7.11.bb). This usually means one provides something the other doesn't and should. I think this might be related to your change, I need to confirm it still. Builds are completeing but the error exists on all non-x86* qemu machines Thanks Sau! > The following changes since commit 35b5fb2dd2131d4c7dc6635c14c6e08ea6926457: > > eglibc-package: remove /var (2012-05-01 12:36:18 +0100) > > are available in the git repository at: > git://git.openembedded.org/openembedded-core-contrib kraj/qemu-xserver-xorg > http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=kraj/qemu-xserver-xorg > > Khem Raj (3): > qemumachines: Enable xserver-xorg as default xserver > xserver-xf86-config: Add xorg.conf for arm,mips,ppc,sh qemu machines > qemux86-64,qemux86: Override XSERVER variable > > meta/conf/machine/include/qemu.inc | 9 ++- > meta/conf/machine/qemux86-64.conf | 2 +- > meta/conf/machine/qemux86.conf | 2 +- > .../xserver-xf86-config/qemuarm/xorg.conf | 69 ++++++++++++++++++++ > .../xserver-xf86-config/qemumips/xorg.conf | 69 ++++++++++++++++++++ > .../xserver-xf86-config/qemumips64/xorg.conf | 69 ++++++++++++++++++++ > .../xserver-xf86-config/qemuppc/xorg.conf | 69 ++++++++++++++++++++ > .../xserver-xf86-config/qemush4/xorg.conf | 69 ++++++++++++++++++++ > .../xorg-xserver/xserver-xf86-config_0.1.bb | 2 +- > 9 files changed, 356 insertions(+), 4 deletions(-) > create mode 100644 meta/recipes-graphics/xorg-xserver/xserver-xf86-config/qemuarm/xorg.conf > create mode 100644 meta/recipes-graphics/xorg-xserver/xserver-xf86-config/qemumips/xorg.conf > create mode 100644 meta/recipes-graphics/xorg-xserver/xserver-xf86-config/qemumips64/xorg.conf > create mode 100644 meta/recipes-graphics/xorg-xserver/xserver-xf86-config/qemuppc/xorg.conf > create mode 100644 meta/recipes-graphics/xorg-xserver/xserver-xf86-config/qemush4/xorg.conf >
On Thu, May 10, 2012 at 9:07 PM, Saul Wold <sgw@linux.intel.com> wrote: > > > ERROR: Multiple .bb files are due to be built which each provide > virtual/libgl > (/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-mips/build/meta/recipes-graphics/mesa/mesa-dri_7.11.bb > /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-mips/build/meta/recipes-graphics/mesa/mesa-xlib_7.11.bb). > This usually means one provides something the other doesn't and should. > > I think this might be related to your change, I need to confirm it still. > > Builds are completeing but the error exists on all non-x86* qemu machines interesting I do not see this error on bare oe-core. Do you have some layer which could be doing something to virtual/libgl provide
On 05/02/2012 08:35 PM, Khem Raj wrote: > Currently we use kdrive for all qemu machines except x86 and x86_64 > this patchset enables it for other qemu machines too > > I did not delete the kdrive recipes intentionally since I saw that > there were some images which were using kdrive as xserver > > I have successfully sato image in qemumips qemuarm and qemuppc > > The following changes since commit 35b5fb2dd2131d4c7dc6635c14c6e08ea6926457: > > eglibc-package: remove /var (2012-05-01 12:36:18 +0100) > > are available in the git repository at: > git://git.openembedded.org/openembedded-core-contrib kraj/qemu-xserver-xorg > http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=kraj/qemu-xserver-xorg > > Khem Raj (3): > qemumachines: Enable xserver-xorg as default xserver > xserver-xf86-config: Add xorg.conf for arm,mips,ppc,sh qemu machines > qemux86-64,qemux86: Override XSERVER variable > > meta/conf/machine/include/qemu.inc | 9 ++- > meta/conf/machine/qemux86-64.conf | 2 +- > meta/conf/machine/qemux86.conf | 2 +- > .../xserver-xf86-config/qemuarm/xorg.conf | 69 ++++++++++++++++++++ > .../xserver-xf86-config/qemumips/xorg.conf | 69 ++++++++++++++++++++ > .../xserver-xf86-config/qemumips64/xorg.conf | 69 ++++++++++++++++++++ > .../xserver-xf86-config/qemuppc/xorg.conf | 69 ++++++++++++++++++++ > .../xserver-xf86-config/qemush4/xorg.conf | 69 ++++++++++++++++++++ > .../xorg-xserver/xserver-xf86-config_0.1.bb | 2 +- > 9 files changed, 356 insertions(+), 4 deletions(-) > create mode 100644 meta/recipes-graphics/xorg-xserver/xserver-xf86-config/qemuarm/xorg.conf > create mode 100644 meta/recipes-graphics/xorg-xserver/xserver-xf86-config/qemumips/xorg.conf > create mode 100644 meta/recipes-graphics/xorg-xserver/xserver-xf86-config/qemumips64/xorg.conf > create mode 100644 meta/recipes-graphics/xorg-xserver/xserver-xf86-config/qemuppc/xorg.conf > create mode 100644 meta/recipes-graphics/xorg-xserver/xserver-xf86-config/qemush4/xorg.conf > Khem, Finally merged this into OE-Core, next step will be to look at updating the xserver! This is something I think that we will be looking into. Thanks for this contribution Sau!