From: Nick Warne <nick@linicks.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 3.18.3
Date: Sat, 17 Jan 2015 10:07:44 +0000 [thread overview]
Message-ID: <54BA3470.8040302@linicks.net> (raw)
In-Reply-To: <54BA2EC1.8060606@linicks.net>
On 17/01/15 09:43, Nick Warne wrote:
> On 17.01.2015, Heinz Diehl wrote:
>
> > Since 3.18, machines with Ironlake Intel Graphics are left with a
> > black screen when booting into X. I reported the bug here:
> >
> > https://www.libreoffice.org/bugzilla/show_bug.cgi?id=87330
>
> Yes (since 3.18.), and on my notebook with:
>
> 00:02.0 VGA compatible controller: Intel Corporation Atom Processor
> D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller
> 00:02.1 Display controller: Intel Corporation Atom Processor
> D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller
>
> if I use the Intel sna driver, just running glxgears crashes X to the
> console, and videos run in mplayer but just appear black. Strangely
> enough, after X crashes, if I restart it, all works fine?
>
> I am currently using the Intel uxa driver which works OK on any occasion.
>
> The above symptoms are still the same in 3.18.3
OK, perhaps I should have reported this when it happened, but I thought
it was the notebook/me/the dog causing it.
I applied the changes from here:
http://cgit.freedesktop.org/drm-intel/patch/?id=d472fcc8379c062bd56a3876fc6ef22258f14a91
albeit on different code lines on 3.18.3 and all is hunky dory again
using driver sna!
Greg, me thinks this should go in next -stable.
Thanks!
Nick
--
"A bug in the code is worth two in the documentation."
http://linicks.net/
http://slackpi.linicks.net/
http://fishpi.linicks.net/
next prev parent reply other threads:[~2015-01-17 10:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-17 9:43 Linux 3.18.3 Nick Warne
2015-01-17 10:07 ` Nick Warne [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-01-16 18:39 Greg KH
2015-01-16 18:39 ` Greg KH
2015-01-17 8:05 ` Heinz Diehl
2015-01-17 8:13 ` Heinz Diehl
2015-01-17 14:59 ` Greg KH
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=54BA3470.8040302@linicks.net \
--to=nick@linicks.net \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox