Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen

Bug #1724639 reported by Ian Bruntlett on 2017-10-18
334
This bug affects 64 people
Affects Status Importance Assigned to Milestone
Linux
Invalid
High
openSUSE
Fix Released
Critical
linux (Ubuntu)
Medium
Unassigned

Bug Description

Installed O.S. on Samsung NC10. Display worked O.K. in text mode so the install went smoothly. When the system is rebooted, however, switching to graphics mode results in the below described screen corruption:-

Left Hand Side 80% of screen black with a blue of white pixels and some blue lines at the top
Right Hand Side 20% of screen OK.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-16-generic 4.13.0-16.19
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.13.0-16-generic.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
ApportVersion: 2.20.7-0ubuntu3
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ian 918 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf0340000 irq 25'
   Mixer name : 'Realtek ALC272'
   Components : 'HDA:10ec0272,144dca00,00100001'
   Controls : 25
   Simple ctrls : 12
CurrentDesktop: LXDE
Date: Wed Oct 18 18:30:15 2017
HibernationDevice: RESUME=UUID=c54e130e-6625-4d96-ba75-4efaa6a9da75
InstallationDate: Installed on 2017-10-18 (0 days ago)
InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
MachineType: SAMSUNG ELECTRONICS CO., LTD. NC10
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=d74a58ab-e96e-4531-a2eb-13f0d1610658 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-16-generic N/A
 linux-backports-modules-4.13.0-16-generic N/A
 linux-firmware 1.169
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/14/2009
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 07CA.M002.20090414.KTW
dmi.board.name: NC10
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr07CA.M002.20090414.KTW:bd04/14/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnNC10:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNC10:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
dmi.product.name: NC10
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

My graphic card is a Intel(R) Graphics 520.

Could you attach output of dmesg?

Created attachment 741173
dmesg

It should be noted that the screen distortion appears in runlevel 3 as well. so it is not an issue of the video driver!

Hmm...

Can you create a bug at https://bugs.freedesktop.org -- product DRI, component DRM/Intel?

plane B assertion failure, should be off on pipe B but is still active
------------[ cut here ]------------
WARNING: CPU: 1 PID: 259 at ../drivers/gpu/drm/i915/intel_display.c:1252 assert_planes_disabled+0x128/0x140 [i915]
Modules linked in: ata_piix i915(+) serio_raw i2c_algo_bit uhci_hcd ehci_pci drm_kms_helper ehci_hcd syscopyarea sysfillrect sysimgblt usbcore fb_sys_fops drm video button sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua
CPU: 1 PID: 259 Comm: systemd-udevd Not tainted 4.13.1-1-pae #1
Hardware name: ASUSTeK Computer INC. 901/901, BIOS 1903 03/17/2009
task: f4ae4700 task.stack: f4b3c000
EIP: assert_planes_disabled+0x128/0x140 [i915]
EFLAGS: 00010286 CPU: 1
EAX: 00000046 EBX: f4bbc000 ECX: f71eb340 EDX: f71e486c
ESI: 00000001 EDI: 00000001 EBP: f4b3dbe4 ESP: f4b3dbc8
 DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
CR0: 80050033 CR2: b7152000 CR3: 34aeca60 CR4: 000006f0
Call Trace:
 ? intel_disable_pipe+0x45/0x220 [i915]
 ? i9xx_crtc_disable+0x5c/0x3a0 [i915]
 ? drm_connector_list_iter_next+0x71/0xa0 [drm]
 ? drm_atomic_add_affected_connectors+0xd0/0xf0 [drm]
 ? intel_crtc_disable_noatomic+0xb5/0x290 [i915]
 ? intel_modeset_setup_hw_state+0xa58/0xc40 [i915]
 ? intel_modeset_setup_hw_state+0xa85/0xc40 [i915]
 ? intel_modeset_init+0x4d1/0xea0 [i915]
 ? intel_setup_gmbus+0x1e1/0x270 [i915]
 ? i915_driver_load+0xa4c/0x1330 [i915]
 ? local_pci_probe+0x35/0x80
 ? pci_device_probe+0x158/0x170
 ? driver_probe_device+0x2b9/0x410
 ? __driver_attach+0x99/0xe0
 ? driver_probe_device+0x410/0x410
 ? bus_for_each_dev+0x4f/0x80
 ? driver_attach+0x19/0x20
 ? driver_probe_device+0x410/0x410
 ? bus_add_driver+0x187/0x230
 ? 0xf8306000
 ? driver_register+0x56/0xd0
 ? 0xf8306000
 ? do_one_initcall+0x46/0x170
 ? do_init_module+0x21/0x1d9
 ? do_init_module+0x50/0x1d9
 ? load_module+0x1435/0x1980
 ? SyS_finit_module+0x79/0xc0
 ? do_fast_syscall_32+0x71/0x150
 ? entry_SYSENTER_32+0x4e/0x7c
Code: ff 83 c4 10 e9 44 ff ff ff 57 68 a0 91 29 f8 e8 cc 8c 2d e0 0f ff 58 5a e9 30 ff ff ff ff 75 f0 50 68 d8 91 29 f8 e8 b5 8c 2d e0 <0f> ff 83 c4 0c e9 3e ff ff ff 8d b4 26 00 00 00 00 8d bc 27 00
---[ end trace 0e7d08f54709149f ]---

BTW, I noticed the same exception when booting kernel 4.12.11, but with no further impact

(In reply to Axel Braun from comment #8)
> BTW, I noticed the same exception when booting kernel 4.12.11, but with no
> further impact

So are any of these (there are more of them) actually new? We need to know if this is something related to any of those warnings as it can help debugging.

Download full text (3.3 KiB)

There is indeed a difference:
 Kernel 4.13.1 throws 2 exceptions:
[ 7.353528] ------------[ cut here ]------------
[ 7.353698] WARNING: CPU: 1 PID: 259 at ../drivers/gpu/drm/i915/intel_display.c:1252 assert_planes_disabled+0x128/0x140 [i915]
[ 7.353703] Modules linked in: ata_piix i915(+) serio_raw i2c_algo_bit uhci_hcd ehci_pci drm_kms_helper ehci_hcd syscopyarea sysfillrect sysimgblt usbcore fb_sys_fops drm video button sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua
[ 7.353757] CPU: 1 PID: 259 Comm: systemd-udevd Not tainted 4.13.1-1-pae #1
[ 7.353777] Hardware name: ASUSTeK Computer INC. 901/901, BIOS 1903 03/17/2009
[ 7.353793] task: f4ae4700 task.stack: f4b3c000
[ 7.353956] EIP: assert_planes_disabled+0x128/0x140 [i915]
[ 7.353960] EFLAGS: 00010286 CPU: 1
[ 7.353965] EAX: 00000046 EBX: f4bbc000 ECX: f71eb340 EDX: f71e486c

and

[ [ 7.448321] ------------[ cut here ]------------
[ 7.448362] WARNING: CPU: 0 PID: 270 at ../drivers/gpu/drm/drm_atomic_helper.c:912 drm_atomic_helper_update_legacy_modeset_state+0x220/0x230 [drm_kms_helper]
[ 7.448365] Modules linked in: ata_piix i915 serio_raw i2c_algo_bit uhci_hcd ehci_pci drm_kms_helper ehci_hcd syscopyarea sysfillrect sysimgblt usbcore fb_sys_fops drm video button sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua
[ 7.448407] CPU: 0 PID: 270 Comm: kworker/u4:2 Tainted: G W 4.13.1-1-pae #1
[ 7.448410] Hardware name: ASUSTeK Computer INC. 901/901, BIOS 1903 03/17/2009
[ 7.448422] Workqueue: events_unbound async_run_entry_fn
[ 7.448427] task: f4bb2780 task.stack: f4bb4000
[ 7.448457] EIP: drm_atomic_helper_update_legacy_modeset_state+0x220/0x230 [drm_kms_helper]
[ 7.448460] EFLAGS: 00010246 CPU: 0
[ 7.448464] EAX: f4b6e800 EBX: f4b0ac00 ECX: f4bc5e00 EDX: f4ba1b00
[ 7.448468] ESI: f4ba2780 EDI: 00000000 EBP: f4bb5c38 ESP: f4bb5c1c
[ 7.448473] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[ 7.448477] CR0: 80050033 CR2: b7153000 CR3: 349d0060 CR4: 000006f0
   7.353969] ESI: 00000001 EDI: 00000001 EBP: f4b3dbe4 ESP: f4b3dbc8
[ 7.353975] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[ 7.353980] CR0: 80050033 CR2: b7152000 CR3: 34aeca60 CR4: 000006f0

while Kernel 4.12.11 has only one:

[ 7.349601] ------------[ cut here ]------------
[ 7.349637] WARNING: CPU: 1 PID: 276 at ../drivers/gpu/drm/drm_atomic_helper.c:842 drm_atomic_helper_update_legacy_modeset_state+0x220/0x230 [drm_kms_helper]
[ 7.349640] Modules linked in: ata_piix i915 serio_raw i2c_algo_bit drm_kms_helper ehci_pci uhci_hcd ehci_hcd usbcore syscopyarea sysfillrect sysimgblt fb_sys_fops drm video button sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua
[ 7.349680] CPU: 1 PID: 276 Comm: kworker/u4:2 Not tainted 4.12.11-1-pae #1
[ 7.349683] Hardware name: ASUSTeK Computer INC. 901/901, BIOS 1903 03/17/2009
[ 7.349696] Workqueue: events_unbound async_run_entry_fn
[ 7.349700] task: f4aec6c0 task.stack: f4be6000
[ 7.349728] EIP: drm_atomic_helper_update_legacy_modeset_state+0x220/0x230 [drm_kms_helper]
[ 7.349731] EFLAGS: 00010246 CPU: 1
[ 7.349735] EAX: f56ce400 EBX: f4bb7c00 ECX: f4...

Read more...

1 comments hidden view all 112 comments

The same Problem appeares on an Acer Aspire One A110L

80 comments hidden view all 112 comments
Ian Bruntlett (ian-bruntlett) wrote :
Ian Bruntlett (ian-bruntlett) wrote :

Here is a photo of the problem.

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc5

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1724639

tags: added: iso-testing

Hi Joseph,

On 18 October 2017 at 19:47, Joseph Salisbury <<email address hidden>
m> wrote:

> Did this issue start happening after an update/upgrade? Was there a
> prior kernel version where you were not having this particular problem?
>

I received an e-mail from <email address hidden> with a subject of "A new
build of Lubuntu Alternate i386 is ready for testing!" - referring to
version: 20171017.1, with a link to http://iso.qa.ubuntu.com/qatra
cker/milestones/383/builds/159145/testcases

This was downloaded by me:-
ian@turing:~/isos/2017-10-17.1$ md5sum artful-alternate-i386.iso
6beffce30b77f7c8105bde2c4e4d69b8 artful-alternate-i386.iso

I created install media by running Startup Disc Creator and the above iso.

Booted my Samsung NC10 and installed the lubuntu 32-bit version. During
installation, everything was text mode and O.K. On booting into the system,
as soon as it switched from text mode to graphics mode, I experienced this
graphics corruption:-

Left Hand Side 80% of screen black with a blue of white and some blue at
the top
Right Hand Side 20% of screen OK.

I'm exhausted. I'll do those further tests tomorrow evening.

BW,

Ian

--
-- ACCU - Professionalism in programming - http://www.accu.org
-- My writing - https://sites.google.com/site/ianbruntlett/
-- Free Software page - https://sites.google.com/site/
ianbruntlett/home/free-software

Ian Bruntlett (ian-bruntlett) wrote :

SUMMARY:-
Installed upscreen kernel, still got problems. See below for details:-

Did this on personal computer...
================================
Downloaded these files:-

total 58M
-rw-rw-r-- 1 ian ian 11M Oct 19 12:18
linux-headers-4.14.0-041400rc5_4.14.0-041400rc5.201710152230_all.deb
-rw-rw-r-- 1 ian ian 657K Oct 19 12:18
linux-headers-4.14.0-041400rc5-generic_4.14.0-041400rc5.201710152230_i386.deb
-rw-rw-r-- 1 ian ian 48M Oct 19 12:19
linux-image-4.14.0-041400rc5-generic_4.14.0-041400rc5.201710152230_i386.deb

Put onto flash drive.

Did this on the Samsung NC10 NetBook (hostname "hawking") with the graphics
problem.
====================================================================================
Copied into ~/usk folder on NetBook
Did a sudo dpkg -i *.deb
Rebooted.

Using this kernel:-
===================
Linux hawking 4.14.0-041400rc5-generic #201710152230 SMP Mon Oct 16
02:43:31 UTC 2017 i686 i686 i686 GNU/Linux

When NetBook connected to an external monitor
=============================================
It appears that, when the system is connected to an external monitor, the
graphics corruption doesn't happen. However, the login screen is black with
a mouse pointer. Typed password in blind - no luck. Did it a few times,
eventually managed to login.

On the external monitor, the display is perfect.
On the NetBook screen, it is almost perfect - the task bar at the bottom of
the screen is not present.

Note: with this kernel, the system can't see my Ethernet connection.

When NetBook only using built in screen
=======================================
Boot screen left hand side 80% black with some smudges of text, remainder
20% of screen is black with the occasional part of a kernel message, later
in boot process is blue.
Login screen left hand side 80% black, remainder perfect
Typed password in blind.
Login screen left hand side 80% black, remainder perfect - even part of the
taskbar is visible.
Anomaly - when I do a screen shot by pressing the Print Screen key, when
viewed on my personal computer, the image is *perfect*. I'm no graphics
developer but it suggests to me the frame buffer is OK, so the problem is
something else.

--
-- ACCU - Professionalism in programming - http://www.accu.org
-- My writing - https://sites.google.com/site/ianbruntlett/
-- Free Software page -
https://sites.google.com/site/ianbruntlett/home/free-software

tags: added: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed

As I mentioned earlier, when a screenshot is taken of the corrupted screen, a perfect snapshot is produced, suggesting the frame buffer is OK and the problem lies elsewhere.

Kai-Heng Feng (kaihengfeng) wrote :

Does this also happen to 64bit version?

Hi Kal,

On 19 October 2017 at 18:17, Kai-Heng Feng <email address hidden>
wrote:

> Does this also happen to 64bit version?
>

The equipment being tested, a Samsung NC10 Netbook, is a 32-bit device, so
I am unable to test it on that.

For convenience, here are some hardware details:-
Intel Atom N270, 1.66GHz, 32-bit, 2GiB RAM, 149.05 GiB hard drive, no
optical drive, Ethernet and WiFi connections, lubuntu typically installed
via USB flashdrive

HTH

Ian

--
-- ACCU - Professionalism in programming - http://www.accu.org
-- My writing - https://sites.google.com/site/ianbruntlett/
-- Free Software page -
https://sites.google.com/site/ianbruntlett/home/free-software

You need to file an upstream bug at https://bugs.freedesktop.org/
Product: DRI
Component: DRM/Intel

Ian Brown (ianbrown) wrote :

I can't add much to this apart from a small amount of personal experience.

A couple of weeks ago, I installed lubuntu 17.04 onto my Samsung NC10. It behaved perfectly.
After 17.10 came out, I selected to upgrade and this problem occurred, exactly as described above.

I am new to Linux, but curious, so I tried all combinations of Xubuntu and Lubuntu from 16.04, 17.04 and 17.10 on clean install and upgrade.

Whatever combo I tried, 17.10 had the same issue and anything else was fine.

Eduard (eddy-spageddy) wrote :

I can confirm the bug too.
After the Xubuntu update from 17.04 to 17.10, the intel mobile graphics is broken.

Moreover, the issue seems to be a little bigger.
The bug here is the same one as bug #1720703 , so Mods please merge the two bugs.
(https://bugs.launchpad.net/ubuntu-mate/+bug/1720703)
It seems to have nothing to do with the Ubuntu distro, as is is present in Ubuntu Mate,
Ubuntu, Lubuntu und Xubuntu, all Versions 17.10 -- > so this indicates that it is Kernel 4.13
related.

And it seems to affect other distros as well.
The bug also affects OpenSuse, with Kernel 4.13:
https://bugzilla.opensuse.org/show_bug.cgi?id=1058870

So there seems to be something wrong with Kernel 4.13 with the Intel Graphics 945.

In the openSUSE Bug Report, users state that Kernels 4.11 and 4.12 are still working.

I will test that right now and report back.

Thank you Community for all the efforts.

Eduard (eddy-spageddy) wrote :

@kaihengfeng;

I have tried both kernels you proposed, and can confirm what has been stated in the opensuse-Forum:
Both Kernels 4.11 and 4.12 SEEM to be working and show no graphic glitches.

So the first idea would be that something happend within the Kernel transition from 4.12 to 4.13, , but not too easy.
Trying to open differnet Applications with 4.12 shows that there is already something fishy going on with the graphics, e.g. LibreOffice will not start with Kernel 4.12 and I believe it must have to do with the graphics.

This is in accordance with the errors / logs / exceptions posted in the opensuse bug-report.

So for Computers / Laptops / Netbooks using the Intel Mobile 945 Chipsets and Ubuntu 17.10, I would personally recommend the 4.11 Kernel, for I found it to be most stable and all applications I have tested so far do work.

I can help with logs and dmesg if needed, please just tell me what logs you need.

For everyone who has this error, I will show you a workaround so you can still use your computer even after the update to 17.10.
The workaround consists of installing kernel 4.11 and using it.

Enter Grub (which is the startup manager) by holding down the shift key while booting.
If you have Grub showing up on every boot (e.g. if you have a multi OS and also have Win 7/8/10) installed, even better.
Now select Ubuntu ... enhanced options and then select starting up with the 4.10 Kernel (which still should be installed if you have updated from 17.04). If the option to start up with the 4.10 kernel is not available, select recovery mode (which should also work fine, but you have to work with a low resolution then)

In the 4.10 Ubuntu (recovery mode) open your browser and go to this directory:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11/

under "Build for i386 succeeded" download these 3 files:

linux-headers-4.11.0-041100_4.11.0-041100.201705041534_all.deb
linux-headers-4.11.0-041100-generic_4.11.0-041100.201705041534_i386.deb
linux-image-4.11.0-041100-generic_4.11.0-041100.201705041534_i386.deb

After the download, put those 3 Files in a new, seperate folder, and open the directory with the terminal (right click on the folder --> open in Terminal).

In the Terminal post:

sudo dpkg -i *.deb

Press enter and wait. The 4.11 Kernel will be installed, it takes a while.
After that, you can reboot your computer and in Grub in the enhanced options you can now start your computer with the 4.11 generic kernel, which works fine for me.

If you want Ubuntu to start up everytime with the 4.11 Kernel, you can use the "Grub Customzier" for that. Here is how you install the grub customizer:

http://ubuntuhandbook.org/index.php/2014/04/install-grub-customizer-ubuntu-1404/

Let's hope that someone in this Linux world can make the Intel Mobile Graphics card work again in a de-bugged 4.13 kernel =)

Cheers and Kudos everyone !

Eduard (eddy-spageddy) on 2017-10-22
summary: - Graphics problem - 80% of the Left hand side of screen solid black
+ Bug in Kernel 4.13 : Intel Mobile Graphics show 80 % black screen
summary: - Bug in Kernel 4.13 : Intel Mobile Graphics show 80 % black screen
+ Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen
Eduard (eddy-spageddy) on 2017-10-22
affects: linux (Ubuntu) → ubuntu

Hi All,

On 21 October 2017 at 19:38, Kai-Heng Feng <email address hidden>
wrote:

> The it's a regression.
>
> Please try v4.11 [1] and v4.12 [2].
>
> [1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11/
> linux-image-4.11.0-041100-generic_4.11.0-041100.201705041534_i386.deb
> [2] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12/
> linux-image-4.12.0-041200-generic_4.12.0-041200.201707022031_i386.deb

OK, I installed those versions. Did some testing. Here are the results for
kernels 4.11, 4.12, 4.13, 4.14:-

4.11 - display OK, Ethernet (Internet) OK
4.12 - display OK, Ethernet (Internet) OK
4.13 - display problem (80% of the left hand side of screen black with
smudges) occurs, Ethernet (Internet) OK
4.14 - *Very* occasionally the display works. Usually the display problem
(80% of the left hand side of screen black with smudges) occurs

Note: also saw on 4.14 that Internet(Ethernet does not work). The other
kernels (4.11,4.12,4.13) can see ethernet and internet OK.

HTH,

Ian

--
-- ACCU - Professionalism in programming - http://www.accu.org
-- My writing - https://sites.google.com/site/ianbruntlett/
-- Free Software page -
https://sites.google.com/site/ianbruntlett/home/free-software

Ian Bruntlett (ian-bruntlett) wrote :

Hi All,

Been doing some testing on my Samsung NC10 NetBook.

I can get the display to work OK if I do this:-
* Boot NetBook.
* As soon as Samsung BIOS logo shows, press and the power switch down till
it does a hard power down.
* Switch computer on. Boot messages appear as text, everything just works.

HTH,

Ian

--
-- ACCU - Professionalism in programming - http://www.accu.org
-- My writing - https://sites.google.com/site/ianbruntlett/
-- Free Software page -
https://sites.google.com/site/ianbruntlett/home/free-software

Kai-Heng Feng (kaihengfeng) wrote :

Please try versions form 4.13-rc1 to 4.13-rc7.

Find the first version that has this issue.

Schoof (andreas-schoof) wrote :

with ideapad S10-2 noplymouth start process runs until tty1-login. After that only blueish pixels appear at the upper edge of the screen. With nomodeset edit in grub the netbook can be used. About 5(?) years ago intel 945 had similar trouble with kernel.

Hi Kai-Heng,

On 23 October 2017 at 08:02, Kai-Heng Feng <email address hidden>
wrote:

> Please try versions form 4.13-rc1 to 4.13-rc7.
>
> Find the first version that has this issue.
>
I'm new to this kernel thing.

I went to http://kernel.ubuntu.com/~kernel-ppa/mainline/ and found
v4.13-rc1/ <http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc1/>
through to v4.13-rc7/
<http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc7/> so downloaded
them.
There is no v4.13-rc5.

Testing on Monday, 23rd October 2017

Started off with these files in ~/isos/2017-10-17.1/upstream-kernel
-rw-rw-r-- 1 ian ian 48M Oct 23 10:13
linux-image-4.13.0-041300rc1-generic_4.13.0-041300rc1.201707151931_i386.deb
-rw-rw-r-- 1 ian ian 48M Oct 23 10:14
linux-image-4.13.0-041300rc2-generic_4.13.0-041300rc2.201707232231_i386.deb
-rw-rw-r-- 1 ian ian 48M Oct 23 10:14
linux-image-4.13.0-041300rc3-generic_4.13.0-041300rc3.201707301631_i386.deb
-rw-rw-r-- 1 ian ian 48M Oct 23 10:15
linux-image-4.13.0-041300rc4-generic_4.13.0-041300rc4.201708062231_i386.deb
-rw-rw-r-- 1 ian ian 48M Oct 23 10:56
linux-image-4.13.0-041300rc6-generic_4.13.0-041300rc6.201708201831_i386.deb
-rw-rw-r-- 1 ian ian 48M Oct 23 10:18
linux-image-4.13.0-041300rc7-generic_4.13.0-041300rc7.201708272131_i386.deb

TESTING 4.13-rc1
* Trackpad and USB Mouse - does not work
* Display - corrupted

TESTING 4.13-rc2
* Trackpad and USB Mouse - does not work
* Display - corrupted

TESTING 4.13-rc3
* Trackpad and USB Mouse - works
* Display - corrupted

TESTING 4.13-rc4
* Trackpad and USB Mouse - works
* Display - corrupted

TESTING 4.13-rc6
* Trackpad and USB Mouse - works
* Display - corrupted

TESTING 4.13-rc7
* Trackpad and USB Mouse - works
* Display - corrupted

Note: on occasion, Internet (Ethernet) access did not work. Due to poor
note-taking, I can't add more than that.
If it is important though, I can re-run the tests and carefully note if the
networking is OK or not.

Can confirm! I have two laptops with Atom n270, both are affected.

My post at AskUbuntu: https://askubuntu.com/questions/969014/part-of-the-screen-desktop-is-black-pic-inside-happens-with-17-10s-on-atom

A copy from my post:

"The mouse is visible on the black part, and i can drag windows from there. Print screen produces a normal pic with all the desktop as it should look like.

I have this problem with 2 atom n270 laptops, With the first one I could "fix" it temproary by connecting an external screen, then switching to CLI (Ctrl+Alt+F1) and back to the gui (Ctrl+Alt+F7). It might be a temporary fix for the second laptop too, just didn't check it.

It happens only in 17.10 versions (Ubuntu, Ubuntu mate, Lubuntu). Previous versions of Ubuntu are fine. Also Windows and Manjaro are fine.

Pic of second laptop having this: https://imgur.com/b6iTmFi

Possible tags: screen, screen black, monitor, laptop, monitor and laptop, monitor display, 17.10, atom, atom n270, n270, intel atom,

I had problems with LIbreofiice too, but only with "Writer", which refuses to open. Calc is working fine.

My laptop is working now. I don't know how (One of them at least). I don't remember that I've done anything to it. I was using windows...

affects: ubuntu → linux (Ubuntu)
Lukasz Pozniak (rox-lukas) wrote :

I have the same exact issue on Acer Aspire One A110 (ZG5). In my case this happened after upgrade from 17.04 to 17.10. The workarounds are either pass nomodeset option to kernel at boot, or just choose the previous kernel (4.10 in my case). The latter solution gives me correct 1024x600 resolution and is preferred until this problem is resolved.

Eugene Romanenko (eros2) wrote :

Have same issue on Fujitsu M2010 laptop.

Same issue after upgrade from Xubuntu 17.04 to 17.10 32 bits on Samsung NC10.
So I still use 4.10.0-37-generic xubuntu 17.04 kernel.
But Booting on 17.10 xubuntu 32 bits live CD works.

Eugene Romanenko (eros2) wrote :

Just found some sort of workaround - boot to login screen (gdm) which is 80% invisible and press Power button. Notebook going to suspend. Press Power button again - notebook waking up and screen is ok!

John Roe (johndroe) wrote :

I can confirm that this works on the Samsung NC10 too. I had to start up first in the previous version of the Kernel and set the function of the Power Button to suspend ( it was set to power off.

Gerald Huber (ge-huber) wrote :

I can confirm the bug occurring after an upgrade from Lubuntu 17.04 to 17.10 on a HP Mini 5101 Netbook.

Eduard (eddy-spageddy) wrote :

@kaihengfeng

Just installed the 4.14 Kernel that you linked.
The bug is still present in this kernel version.

Eduard (eddy-spageddy) wrote :

@ Everyone confirming this bug... Please click on "This bug affects me" on the top of the page (right underneath the title in small and green). Thank you =)

Steve (spinal) wrote :

I got it working in Arch without downgrading the kernel it may work for Ubuntu as well.
Edit the grub file and comment the following entry;
GRUB_GFXPAYLOAD_LINUX=keep
Then rebuild the grub

sudo grub-mkconfig -o /boot/grub/grub.cfg

Reboot and enjoy
I was going to settle for running lts but this works for my setup no issues at all.

Kai-Heng Feng (kaihengfeng) wrote :

Does "GRUB_GFXPAYLOAD_LINUX=text" make the issue reappear?

Steve (spinal) wrote :

No the issue does not reappear

Robert V. (robertvalik) wrote :

Toshiba NB100, screen resolution 1024x600, after upgrading to kernel 4.13.0-16 (from 4.10.0-37) also affected. VGA:

00:02.0 VGA compatible controller: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller (rev 03)

Workaround with GRUB_GFXPAYLOAD_LINUX=text seems to be working.

inugami (inugami-mamoru) wrote :

I have edited /etc/default/grub on my EeePC-901X as "GRUB_GFXPAYLOAD_LINUX=text".
Then, I rebuild grub by sudo grub-mkconfig -o /boot/grub/grub.cfg.

It seems to be fine and well working on my EeePC 901.

Schoof (andreas-schoof) wrote :

"GRUB_GFXPAYLOAD_LINUX=text" works with ideapad S10-2 (Atom with Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller rev 03) after kicking out noplymouth für quiet splash.

John Roe (johndroe) wrote :

Can someone help me out how to do this edit. As I have never edited a GRUB before.I'm not even sure what the GRUB is
If I press e is this giving me the GRUB?
Where do I insert the Line GRUB_GFXPAYLOAD_LINUX=text?
Do I then Ctrl_x and go to terminal to do the sudo bit?
Or should I be editing a file from the terminal?

Eugene Romanenko (eros2) wrote :

John, from the terminal issue command

sudo nano /etc/default/grub

Simple editor 'nano' will open.
Add line
GRUB_GFXPAYLOAD_LINUX=text
at the end of file.

Save file and exit from nano.

issue command:

sudo update-grub

reboot.

Ian Bruntlett (ian-bruntlett) wrote :

Hi,

Sorry for the slow reply. I have been somewhat distracted by a physical
illness

As others have done, I set a GRUB variable with the line:-
GRUB_GFXPAYLOAD_LINUX=text

I also commented out the line that set the GRUB variable
GRUB_HIDDEN_TIMEOUT=0

With those changes in place,
1. Graphics problems disappear.
2. It is easier to choose a particular kernel at boot time

However, in last week's testing I noticed a few problems with other
kernels. I'll summarise my notes because I tested about 11 kernels.

The 4.14.-041400rc5-generic kernel doesn't have network access - both
ethernet and Wi-Fi don't work.

There was a temporary regression in 4.13.0-0413rc1-generic
and4.13.0-0413rc2-generic where the trackpad doesn't work.

HTH,

Ian

--
-- ACCU - Professionalism in programming - http://www.accu.org
-- My writing - https://sites.google.com/site/ianbruntlett/
-- Free Software page -
https://sites.google.com/site/ianbruntlett/home/free-software

Gianlo (gianlo) on 2017-11-11
Changed in linux (Ubuntu):
status: Confirmed → In Progress
dino99 (9d9) on 2017-11-11
Changed in linux (Ubuntu):
status: In Progress → Confirmed
Changed in linux:
importance: Unknown → Medium
status: Unknown → Incomplete
Changed in linux:
importance: Medium → High
status: Incomplete → Confirmed
Changed in linux:
status: Confirmed → Incomplete
Changed in linux:
status: Incomplete → Confirmed
42 comments hidden view all 112 comments

I'm seeing the same problem on Gateway LT2030u with Intel Mobile 945 GME Graphics Chipset, after an autoupdate of the kernel from 4.12.9-1-default to 4.14.8-1-default

(In reply to Shon Vella from comment #13)
> I'm seeing the same problem on Gateway LT2030u with Intel Mobile 945 GME
> Graphics Chipset, after an autoupdate of the kernel from 4.12.9-1-default to
> 4.14.8-1-default

The patch is not yet in Kernel 4.15 - see link in comment 7

Changed in opensuse:
importance: Unknown → Critical
status: Unknown → Confirmed

Toshiba Portege R500 (Graphics Processor Intel GMA 950, Intel Core 2 Duo CPU U7700 @ 1.33 GHz)

Downloaded the official lubuntu-17.10-desktop-amd64.iso on January 4th 2018, installed it from USB flashdrive without issues. Reboot => strange flash of screen during boot, X not showing up properly: black screen, graphical mouse cursor visible and moving, but no action possible. Possible to switch to text console with CTRL-ALT-F1 normally.

Updating the system did not help (having kernel 4.13.0-21).

/var/log/syslog contained the errors shown in the included files.

In the file /etc/default/grub I've commented out the line
#GRUB_TERMINAL=console

changing it to:

GRUB_TERMINAL=console

then issued:

sudo update-grub

then reboot, and things are nice, X comes as expected, I can login to graphical screen and everything works, and those errors in the included files are not present anymore.
Thank you for the hints!
Good luck fixing the bug.

Rü (ruebuntu) wrote :

I confirm the issue with an Samsung NC10 with integrated Intel Mobile 945 GSE After a fresh install of lubuntu 16.04.3 and first Auto-Update. The current 32 Bit Desktop iso brought kernel 4.10, everything was fine. The first update installed Kernel 4.13.0-26 which still has the defect.
GRUB_GFXPAYLOAD_LINUX=text solved the problem. Thanks for this Solution!

krystan@gmail.com (krystan) wrote :

IBM Thinkpad t60 running ubuntu 16.04 LTS just got kernel update and experiencing this issue.

Above workarounds work, when falling back to a previous kernel there is no issue so looks like a Kernel bug.

Pawel Por (porparek) wrote :

I'm using laptop Samsung N130 and also have this issue with kernel 4.13.0-26-generic. Downgrading to kernel 4.10.0-42-generic solves the issue but this kernel is Meltdown vulnerable. I've reported my issue #1742756

Lukasz Pozniak (rox-lukas) wrote :

@Pawel Por don't worry about Meltdown, afaik Atom N270 CPU in your netbook is not vulnerable

Hello,

I just installed the latest (2018-1-20) kernel 4.15 build. The issue is finally fixed, atleast in my Asus Eee PC901 945GSE. Display works finally fine without extra grub parameters.

So most likely 4.15 release will be fine. The problem is/was real in 4.13-4.14...

Merge tag 'drm-fixes-for-v4.15-rc9' of git://people.freedesktop.org/~…

Most likely the "Redo plane sanitation.." Thanx Ville S, Dave A & co.

Br,
Tarmo

Matti Ylönen (maanylon) wrote :

I like how all others list this as "critical" or "high" priority, but Ubuntu is like "it's mostly 32-bit users, *bleep* 'em". Shows that they're dropping 32-bit support when they don't care about critical bugs.

The grub edit stuff works btw. Asus EeePC 1005HA here.

Matti, it affects 64-bit as well.
It's a pity 4.15 is not yet in Ubuntu,
in fact even with the grub edit stuff, I need
to reboot the machine once after power-on
to get graphics X, and my CTRL key is broken,
so I can't boot without external keyboard
as I cannot even switch to a text console. :(

tom (akkermans-tom) wrote :

With my Ubuntu version 16.04 LTS i didn't have the problem, until recently!
I suspect with an update from kernel 4.10.x to 4.13.x
So I manually removed the kernel image and headers from version 4.13.x, thereby in fact downgrading again to the older kernel, fixing my problem.
So this confirms the statement above that kernel 4.13 is a problematic one.

best regards
Tom

Hi Tom,

On 23 January 2018 at 19:02, tom <email address hidden> wrote:

> With my Ubuntu version 16.04 LTS i didn't have the problem, until recently!
> I suspect with an update from kernel 4.10.x to 4.13.x
> So I manually removed the kernel image and headers from version 4.13.x,
> thereby in fact downgrading again to the older kernel, fixing my problem.
> So this confirms the statement above that kernel 4.13 is a problematic one.
>

Ubuntu keeps more than one kernel on the hard drive. It defaults to using
the most current one.

You can choose which Linux kernel to boot from by using the GRUB menu on
booting.

To do that, switch your computer on, and, as soon as you see the
manufacturer's logo (i.e. the BIOS screen), press and hold down the
right-hand SHIFT key.

You should then see a menu with a title at the top that reads like "GNU
GRUB version" (etc). This is where you can do quite a few things. Use the
down arrow key to select "Advanced Options for Ubuntu". This takes you to a
screen where you choose a kernel to boot or choose to boot a particular
kernel in"recovery mode".

The command "uname -a" gives info on the current running kernel.

The command "lsb_release -a" gives distro-specific info.

HTH,

Ian

--
-- ACCU - Professionalism in programming - http://www.accu.org
-- My writing - https://sites.google.com/site/ianbruntlett/
-- Free Software page - https://sites.google.com/site/
ianbruntlett/home/free-software

Ricardus (ricardus) wrote :

This bug affected me on my old Dell Mini 9. I hadn't used the thing in years because the battery died. I found am inexpensive battery and figured I'd make a coffee table machine putting lubuntu on it, and I had the same problem. A friend of mine and I fixed it as per this thread:

https://ubuntuforums.org/showthread.php?t=2384579&p=13738255#post13738255

kybernetes (kybernetes) wrote :

Bug affects me on Acer Aspire One ZG5; Intel Graphics is GMA 950 however.
4.13.0-32-generic
Xubuntu 16.04.3 LTS
Grub Version 2.02~beta2-36ubuntu3.15

Easy Workaround: On boot hit F1 for Grub menu and hit enter (first entry for newest generic kernel). I did not change anything in the grub parameters (some people suggest 'text' parameter). Just starting from the menu seems to circumvent the problem.

bcewkurm (bcewkurm) wrote :

Deal all,

I have encountered the same problem with an old MSI Wind U100 netbook (kernel 4.14.10-1 / not Ubuntu, sorry).

To start it, I just edited the grub settings at start-up: "set gfxoayload=text" (instead of keep). [enter in edition mode by "e", then "F10" after modification]

That worked: after that, I modified the /boot/grub.cfg file consequently.

Regards,

steve.horsley (steve-horsley) wrote :

"GRUB_TERMINAL=console" in /etc/default.grub followed by "sudo update-grub" fixed it for me after I updated my Mum's laptop.

J. Janel (jjanel) wrote :

The 'grub workarounds' DID work for me (Lubuntu 16.04 on 1000H; once I stumbled across right search keywords, they are 'easy' do/try, tho I don't understand HOW they work).

Looks like it's fixed in 4.15: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744852
(I wish I knew/understood how/what)

<IMHO (naively), *I* feel this should be a HIGHER PRIORITY (than Medium) for Ubuntu/Canonical to FIX!!!
(STOP auto-breakxxxxxUpgrad-ing to 4.13! This is my 1st experience trying [non-VBox] Linux: shameful /IMHO>

iav (iav) wrote :

I try all 4.15 kernels via UKUU on Asus EeePC-1007HE. Bug present until I apply "grub fix" from this thread.

Michael Rhein (freddy1985) wrote :

Hi People,

i have the any Problem with the "Intel Gmx 945".
The Problem have it with "GRUB_GFXPAYLOAD_LINUX=text" solved.

Workaround:

Go to Terminal

Get input: sudo nano /etc/default/grub
Play input Your Password.

Give in (in the 6 - 8 row)

GRUB_GFXPAYLOAD_LINUX=text

Press Strg+o
Press Enter
Press Strg+x

Give input: sud update-Grub

If this Finisch
Give in: reboot

please pay attention to the correct spelling

Big thanks on the People hier.

Best regards
Michael

I had the same issue on an Acer Aspire One with a fresh Lubuntu 17.10.1 install. Trying to prevent the system from continuously going to sleep I set "HandleSuspendKey" and "HandleLidSwitch" to ignore in /etc/systemd/login.conf. After that the screen problem appeared.
When I commented out the HandleSuspendKey again, everything worked fine!

Hope that helps

Sorry, but after upgrading the kernel to 4.13.0-36, the screen went bad again. Even booting with the old kernel did not work anymore. But the GRUB_GFXPAYLOAD_LINUX=text solution worked...

la Nube (anselch1011) wrote :

Maybe same issue at Ubuntu 16.04.4 with Intel Graphic 945.

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754913

Martin (martin3000) wrote :

My my Lenovo has a Intel Mobile 945GM/GMS/GME integrated graphics controller.
Using "nomodeset" in the boot menu helps.

Martin (martin3000) wrote :

Installing kernel 4.16 (see https://wiki.ubuntu.com/Kernel/MainlineBuilds?action=show&redirect=KernelMainlineBuilds) fixed it.
But now the wifi adapter is not found.

Nicolas Krzywinski (nsk7even) wrote :

Same problem on Gigabyte GA-T1028X
Intel® Atom™ Processor N280(1.66GHz)
Mobile Intel® GS945 Express Chipsets
Intel® GMA 950

Adding this to /etc/default/grub helped me too:
GRUB_GFXPAYLOAD_LINUX=text

Additionally adding this to the GRUB_CMDLINE_LINUX_DEFAULT line enabled the touchpad (which wasn't working before):
i8042.noloop=1 usbhid.quirks=0xeef:0x1:0x40

Changed in linux:
status: Confirmed → Invalid

confirming that on TOSHIBA Portege, the bug has disappeared after upgrade to 18.04 beta with kernel 4.15.0-13.

The line
GRUB_TERMINAL=console
is not needed anymore and X starts OK, and the error message I mentioned above is not reported in the log.

I am getting an error message in dmesg though:

[ 24.576771] [drm:intel_enable_lvds [i915]] *ERROR* timed out waiting for panel to power on

maybe because 1000 msec delay that is in the kernel source is not sufficient, who knows.

Also, lxrandr is unable to save and then next time properly load settings. I have read somewhere that it may be because the modes are somehow not properly reported during start.

Also, plugging the monitor to VGA requires restart before X is shown there, even though it is recognised after plugging in (i.e. with randr output)

And also, nothing is shown on the screen during grub booting, no menu, graphics screen, or whatever, but maybe that is to be expected, I do not know.

jesus (jexux) wrote :

Hi,

GRUB_GFXPAYLOAD_LINUX=text
(line added in grub as described in some posts above)

has solved the issue in a Asus EeePC with Intel 945
thanks!

Zdenek Hrebenar (zhrebenar) wrote :

Hi,

GRUB_GFXPAYLOAD_LINUX=text works on Acer Aspire One with Intel 945GSE.

Ubuntu 16.04.4
Kernel 4.13.0-36-generic
Xorg 1.19.5

Many thanks!!!

So it looks like the bug is fixed since 4.15.3.

Changed in opensuse:
status: Confirmed → Fix Released

The issue reported in comment #108 is still present in kernel 4.15.3:

4.15.3-041503-generic #201802120730
[ 4.645868] [drm:intel_enable_lvds [i915]] *ERROR* timed out waiting for panel to power on

It is also present in kernel 4.15.18.
However, it is not present in kernel 4.16.16 and it is also not present in kernel 4.17.2.
All kernels were downloaded from http://kernel.ubuntu.com/~kernel-ppa/mainline/ and installed with sudo dpkg -i
The latest kernel offered by Ubuntu 18.04 is still 4.15.0, but that one already fixes the original issue with the X Windows not working, at least it does so on Toshiba Portege laptop. However 4.15.0 does not fix the issue reported in comment #108. I do not know what was fixed in 4.15.3, but it may refer to some other issues.

Displaying first 40 and last 40 comments. View all 112 comments or add a comment.