All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: "Bodke, Kishore K" <kishore.k.bodke@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	"Hart, Darren" <darren.hart@intel.com>
Subject: Re: [PATCH 0/1] Fix X issue on crownbay
Date: Tue, 18 Sep 2012 21:02:57 -0700	[thread overview]
Message-ID: <505943F1.4060306@linux.intel.com> (raw)
In-Reply-To: <D956029D25CF204F948EA0FB515E1EE21C10A3A9@ORSMSX105.amr.corp.intel.com>

On 09/18/2012 07:35 PM, Bodke, Kishore K wrote:
>
>
>> -----Original Message-----
>> From: Kamble, Nitin A
>> Sent: Thursday, September 13, 2012 12:58 PM
>> To: Bodke, Kishore K; Zanussi, Tom
>> Cc: Hart, Darren; yocto@yoctoproject.org
>> Subject: RE: [PATCH 0/1] Fix X issue on crownbay
>>
>> Thanks Kishore for reporting it. I am trying to get to bottom of this by today or
>> tomorrow.
>
> Hi Nitin,
>
> I still cannot see the X with the latest poky/master and meta-intel/master for Romley.
> No /usr/bin/Xorg and /usr/bin/X .
>

The patch is pending on stage/master_under_test, it's changes an 
RPROVIDES to an RCONFLICTS.

Sau!

> Thanks
> Kishore.
>
>>
>> Thanks,
>> Nitin
>>
>>
>>> -----Original Message-----
>>> From: Bodke, Kishore K
>>> Sent: Wednesday, September 12, 2012 1:57 PM
>>> To: Kamble, Nitin A; Zanussi, Tom
>>> Cc: Hart, Darren; yocto@yoctoproject.org
>>> Subject: RE: [PATCH 0/1] Fix X issue on crownbay
>>>
>>>
>>>
>>>> -----Original Message-----
>>>> From: yocto-bounces@yoctoproject.org [mailto:yocto-
>>>> bounces@yoctoproject.org] On Behalf Of Kamble, Nitin A
>>>> Sent: Wednesday, September 12, 2012 1:14 PM
>>>> To: Zanussi, Tom
>>>> Cc: Hart, Darren; yocto@yoctoproject.org
>>>> Subject: Re: [yocto] [PATCH 0/1] Fix X issue on crownbay
>>>>
>>>> FYI While testing on the fishriver platform, I also find that there is
>>>> no X log, and looking further found out that xorg executable is not on
>>>> the image. I think the same thing is also happening on crownbay.
>>>
>>> FYI.. I also see the similar issue for Romley.
>>> There is no Xlog and X does not comes up.
>>>
>>> Thanks
>>> Kishore.
>>>
>>>>
>>>> Nitin
>>>>
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From: Kamble, Nitin A
>>>>> Sent: Wednesday, September 12, 2012 9:18 AM
>>>>> To: Zanussi, Tom
>>>>> Cc: Hart, Darren; yocto@yoctoproject.org
>>>>> Subject: RE: [PATCH 0/1] Fix X issue on crownbay
>>>>>
>>>>> Hi Tom,
>>>>>    Thanks for looking into the matter. I will try to reproduce the
>>>>> issue you are seeing with master. And send another pull request with all
>>> the fixes.
>>>>>
>>>>> Regards,
>>>>> Nitin
>>>>>
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Zanussi, Tom
>>>>>> Sent: Monday, September 10, 2012 4:34 PM
>>>>>> To: Kamble, Nitin A
>>>>>> Cc: Hart, Darren; yocto@yoctoproject.org
>>>>>> Subject: Re: [PATCH 0/1] Fix X issue on crownbay
>>>>>>
>>>>>> On Wed, 2012-09-05 at 17:59 -0700, nitin.a.kamble@intel.com wrote:
>>>>>>> From: Nitin A Kamble <nitin.a.kamble@intel.com>
>>>>>>>
>>>>>>> The following changes since commit
>>>>>> 66b516f3d3a287eecbf8804b2221bfc27e36db63:
>>>>>>>
>>>>>>>    README: add info explaining meta-tlk layer purpose (2012-09-06
>>>>>>> 10:36:02 -0500)
>>>>>>>
>>>>>>> are available in the git repository at:
>>>>>>>    git://git.yoctoproject.org/meta-intel-contrib nitin/work
>>>>>>>
>>>>>>> http://git.yoctoproject.org/cgit.cgi/meta-intel-contrib/log/?h=ni
>>>>>>> tin
>>>>>>> /w
>>>>>>> ork
>>>>>>>
>>>>>>
>>>>>> I built and tried this, but it still didn't boot into X, and now
>>>>>> there's not even an Xorg.log to look at:
>>>>>>
>>>>>> root@crownbay:/var/log# ls -al
>>>>>> drwxr-xr-x    2 root     root            80 Sep 10 20:15 .
>>>>>> drwxrwxrwt    7 root     root           140 Jan  6  2009 ..
>>>>>> -rw-r--r--    1 root     root         78429 Sep 10 20:17 messages
>>>>>> -rw-rw-r--    1 root     root          4224 Sep 10 20:17 wtmp
>>>>>>
>>>>>> I assume this is a different X problem related to recent changes in
>>> mater.
>>>>>> Can you update the bug report with the commits that you tested with
>>>>>> so I can verify that your patch at least works?
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Tom
>>>>>>
>>>>>>
>>>>>>
>>>>>>> Nitin A Kamble (1):
>>>>>>>    emgd-driver-bin: Fix package naming issue
>>>>>>>
>>>>>>>   .../xorg-xserver/emgd-driver-bin_1.14.bb           |    8 +++++++-
>>>>>>>   1 files changed, 7 insertions(+), 1 deletions(-)
>>>>>>>
>>>>>>
>>>>
>>>> _______________________________________________
>>>> yocto mailing list
>>>> yocto@yoctoproject.org
>>>> https://lists.yoctoproject.org/listinfo/yocto
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>


      reply	other threads:[~2012-09-19  4:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-06  0:59 [PATCH 0/1] Fix X issue on crownbay nitin.a.kamble
2012-09-06  0:59 ` [PATCH 1/1] emgd-driver-bin: Fix package naming issue nitin.a.kamble
2012-09-07  9:29   ` Burton, Ross
2012-09-07 17:32     ` Kamble, Nitin A
2012-09-10 23:34 ` [PATCH 0/1] Fix X issue on crownbay Tom Zanussi
2012-09-12 16:18   ` Kamble, Nitin A
2012-09-12 20:14   ` Kamble, Nitin A
2012-09-12 20:43     ` Burton, Ross
2012-09-13 19:56       ` Kamble, Nitin A
2012-09-12 20:57     ` Bodke, Kishore K
2012-09-13 19:57       ` Kamble, Nitin A
2012-09-19  2:35         ` Bodke, Kishore K
2012-09-19  4:02           ` Saul Wold [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=505943F1.4060306@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=darren.hart@intel.com \
    --cc=kishore.k.bodke@intel.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.