Skip to contentSkip to conversation

Linux 3.18.3

DISCUSSION Nick Warne 1 participant 2 messages Jan 17, 2015

lore
Share & tools
lore

Nick Warne

author
#0 lore raw
Quoted 4 lines · Heinz Diehl

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

Nick

Signature · 4 lines
"A bug in the code is worth two in the documentation."
http://linicks.net/
http://slackpi.linicks.net/
http://fishpi.linicks.net/
author
#1 lore raw
Quoted 14 lines · Nick Warne
Quoted 4 lines · Heinz Diehl

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

Quoted 7 lines

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

Signature · 4 lines
"A bug in the code is worth two in the documentation."
http://linicks.net/
http://slackpi.linicks.net/
http://fishpi.linicks.net/