All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Miata <mrmazda@earthlink.net>
To: intel-gfx@lists.freedesktop.org
Subject: Re: startx on Fedora died today
Date: Fri, 11 Jul 2014 04:30:04 -0400	[thread overview]
Message-ID: <53BFA08C.6000701@earthlink.net> (raw)
In-Reply-To: <20140711062204.GS8986@nuc-i3427.alporthouse.com>

On 2014-07-11 07:22 (GMT+0100) Chris Wilson composed:

> On Thu, Jul 10, 2014 at 09:09:31PM -0400, Felix Miata wrote:

>> F21 branched off Rawhide over recent hours. On i945G host gx62b I
>> cloned first, then upgraded one to current F21 state and the other
>> to Rawhide. Before today's upgrade, which moved server from
>> 1.15.99.903 to 1.15.99.904 on both, and kernel from rc4git0.1 to
>> rc4git2.1, booting first to multi-user, startx was working normally.
>> Now it won't[1], though X (KDM/KDE) does work by booting to
>> graphical instead of multi-user[2].

>> Is this an already known driver problem? Server? Kernel?

> The difference being when it crashed it tried to open the logind fd. This
> is a server bug - it looks like the recent non-pci platform device
> conflicts with the systemd integration.

Thanks.

>> [1] http://fm.no-ip.com/Tmp/Linux/F/Xorg.0.log-fc21-3
>> [2] http://fm.no-ip.com/Tmp/Linux/F/Xorg.0.log-fc21-5

https://bugzilla.redhat.com/show_bug.cgi?id=1118540 already filed some hours 
before I found this, and happening with rv200 Radeon as well as Intel. I 
don't find anything related filed yet on bugs.freedesktop.org/
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

  Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

  reply	other threads:[~2014-07-11  8:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-11  1:09 startx on Fedora died today Felix Miata
2014-07-11  6:22 ` Chris Wilson
2014-07-11  8:30   ` Felix Miata [this message]
2014-07-11  8:43   ` Hans de Goede

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=53BFA08C.6000701@earthlink.net \
    --to=mrmazda@earthlink.net \
    --cc=intel-gfx@lists.freedesktop.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.