Return to Level1Techs.com

Ubuntu 20.04 Rainbow Screen After Waking From Suspend

Before anything else, current specs.

System Info

Processor: Intel® Pentium® CPU G630 @ 2.70GHz × 2

Graphics: Intel® HD Graphics 2000 (SNB GT1)

Memory: 8 GB / 7.7 usable.

I’m using Ubuntu 20.04 LTS and it’s been the least buggy of the distros I’ve tried. Anyway, sometimes, after waking up from suspend, I get the following rainbow screen.

What can be causing it? I have tried Elementary OS, Linux Mint, lightweight distros and DE’s, and they all do this, if not worse. Ubuntu 20.04 seems to do this least often compared to the previous versions, but what can be causing such issue?

Also, for my specs, is Ubuntu 20.04 LTS a good distro?

Uh, IDK man, but from what I have seen on old igpu systems, that tends to be the gpu is dying

1 Like

Yikes. But the irony is it didn’t happen at all on Windows. Could it be a kernel support thing?

…Huh

@wendell help I’m scared

1 Like

Can you switch to a TTY when the display takes on the colourful appearance? If so, after logging in, run journalctl --catalog --boot and try to see if there are any errors or warnings related to graphics, particularly kernel ones coming from the driver. If you cannot switch to a TTY, then just append =-1 to --boot (--boot=-1) to see the log from your previous boot.

This should provide us a clue or two to help determine whether or not this is a failing GPU or just a failing driver. Also, could you share the output of uname --all?

1 Like

Thanks for this! I, unfortunately, can’t switch to a TTY, so here are the results:

Uname all: Linux Paradox 5.4.0-39-generic #43-Ubuntu SMP Fri Jun 19 10:28:31 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Is that what you were looking for?

For the first request:

– Logs begin at Mon 2020-06-29 18:18:39 EDT, end at Tue 2020-06-30 16:33:56 ED>
Jun 29 18:18:39 Paradox kernel: microcode: microcode updated early to revision >
Jun 29 18:18:39 Paradox kernel: Linux version 5.4.0-26-generic ([email protected]>
Jun 29 18:18:39 Paradox kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26>
Jun 29 18:18:39 Paradox kernel: KERNEL supported cpus:
Jun 29 18:18:39 Paradox kernel: Intel GenuineIntel
Jun 29 18:18:39 Paradox kernel: AMD AuthenticAMD
Jun 29 18:18:39 Paradox kernel: Hygon HygonGenuine
Jun 29 18:18:39 Paradox kernel: Centaur CentaurHauls
Jun 29 18:18:39 Paradox kernel: zhaoxin Shanghai
Jun 29 18:18:39 Paradox kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 f>
Jun 29 18:18:39 Paradox kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE r>
Jun 29 18:18:39 Paradox kernel: x86/fpu: Enabled xstate features 0x3, context s>
Jun 29 18:18:39 Paradox kernel: BIOS-provided physical RAM map:
Jun 29 18:18:39 Paradox kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000>
Jun 29 18:18:39 Paradox kernel: BIOS-e820: [mem 0x000000000009c000-0x0000000000>
Jun 29 18:18:39 Paradox kernel: BIOS-e820: [mem 0x00000000000e0000-0x0000000000>
Jun 29 18:18:39 Paradox kernel: BIOS-e820: [mem 0x0000000000100000-0x000000001f>
Jun 29 18:18:39 Paradox kernel: BIOS-e820: [mem 0x0000000020000000-0x0000000020>
Jun 29 18:18:39 Paradox kernel: BIOS-e820: [mem 0x0000000020200000-0x000000003f>
Jun 29 18:18:39 Paradox kernel: BIOS-e820: [mem 0x0000000040000000-0x0000000040>
Jun 29 18:18:39 Paradox kernel: BIOS-e820: [mem 0x0000000040200000-0x00000000ba>
Jun 29 18:18:39 Paradox kernel: BIOS-e820: [mem 0x00000000bad8f000-0x00000000ba>
lines 1-23…skipping…
– Logs begin at Mon 2020-06-29 18:18:39 EDT, end at Tue 2020-06-30 16:33:56 EDT. –
Jun 29 18:18:39 Paradox kernel: microcode: microcode updated early to revision 0x2f, date = 2019-02-17
Jun 29 18:18:39 Paradox kernel: Linux version 5.4.0-26-generic ([email protected]) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 (Ubuntu 5.4.0-26.30-generic 5.4.30)
Jun 29 18:18:39 Paradox kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=3ec3ad91-fdc5-49e5-a8f0-c1472708858b ro quiet splash
Jun 29 18:18:39 Paradox kernel: KERNEL supported cpus:
Jun 29 18:18:39 Paradox kernel: Intel GenuineIntel
Jun 29 18:18:39 Paradox kernel: AMD AuthenticAMD
Jun 29 18:18:39 Paradox kernel: Hygon HygonGenuine
Jun 29 18:18:39 Paradox kernel: Centaur CentaurHauls
Jun 29 18:18:39 Paradox kernel: zhaoxin Shanghai
Jun 29 18:18:39 Paradox kernel: x86/fpu: Supporting XSAVE feature 0x001: ‘x87 floating point registers’
Jun 29 18:18:39 Paradox kernel: x86/fpu: Supporting XSAVE feature 0x002: ‘SSE registers’
Jun 29 18:18:39 Paradox kernel: x86/fpu: Enabled xstate features 0x3, context size is 576 bytes, using ‘standard’ format.
Jun 29 18:18:39 Paradox kernel: BIOS-provided physical RAM map:
Jun 29 18:18:39 Paradox kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009bfff] usable
Jun 29 18:18:39 Paradox kernel: BIOS-e820: [mem 0x000000000009c000-0x000000000009ffff] reserved
Jun 29 18:18:39 Paradox kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jun 29 18:18:39 Paradox kernel: BIOS-e820: [mem 0x0000000000100000-0x000000001fffffff] usable
Jun 29 18:18:39 Paradox kernel: BIOS-e820: [mem 0x0000000020000000-0x00000000201fffff] reserved
Jun 29 18:18:39 Paradox kernel: BIOS-e820: [mem 0x0000000020200000-0x000000003fffffff] usable
Jun 29 18:18:39 Paradox kernel: BIOS-e820: [mem 0x0000000040000000-0x00000000401fffff] reserved
Jun 29 18:18:39 Paradox kernel: BIOS-e820: [mem 0x0000000040200000-0x00000000bad8efff] usable
Jun 29 18:18:39 Paradox kernel: BIOS-e820: [mem 0x00000000bad8f000-0x00000000badd5fff] ACPI NVS
Jun 29 18:18:39 Paradox kernel: BIOS-e820: [mem 0x00000000badd6000-0x00000000baddcfff] ACPI data
Jun 29 18:18:39 Paradox kernel: BIOS-e820: [mem 0x00000000baddd000-0x00000000bae00fff] reserved
Jun 29 18:18:39 Paradox kernel: BIOS-e820: [mem 0x00000000bae01000-0x00000000bae01fff] usable
Jun 29 18:18:39 Paradox kernel: BIOS-e820: [mem 0x00000000bae02000-0x00000000bae11fff] reserved
Jun 29 18:18:39 Paradox kernel: BIOS-e820: [mem 0x00000000bae12000-0x00000000bae1efff] ACPI NVS
Jun 29 18:18:39 Paradox kernel: BIOS-e820: [mem 0x00000000bae1f000-0x00000000bae42fff] reserved
Jun 29 18:18:39 Paradox kernel: BIOS-e820: [mem 0x00000000bae43000-0x00000000bae85fff] ACPI NVS
Jun 29 18:18:39 Paradox kernel: BIOS-e820: [mem 0x00000000bae86000-0x00000000baffffff] usable
Jun 29 18:18:39 Paradox kernel: BIOS-e820: [mem 0x00000000bb800000-0x00000000bf9fffff] reserved
Jun 29 18:18:39 Paradox kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jun 29 18:18:39 Paradox kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jun 29 18:18:39 Paradox kernel: BIOS-e820: [mem 0x0000000100000000-0x000000023fdfffff] usable
Jun 29 18:18:39 Paradox kernel: NX (Execute Disable) protection: active
Jun 29 18:18:39 Paradox kernel: SMBIOS 2.6 present.
Jun 29 18:18:39 Paradox kernel: DMI: Dell Inc. Vostro 260s /0GDG8Y , BIOS A03 09/29/2011
Jun 29 18:18:39 Paradox kernel: tsc: Fast TSC calibration using PIT
Jun 29 18:18:39 Paradox kernel: tsc: Detected 2693.685 MHz processor
Jun 29 18:18:39 Paradox kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jun 29 18:18:39 Paradox kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Jun 29 18:18:39 Paradox kernel: last_pfn = 0x23fe00 max_arch_pfn = 0x400000000
Jun 29 18:18:39 Paradox kernel: MTRR default type: uncachable
Jun 29 18:18:39 Paradox kernel: MTRR fixed ranges enabled:
Jun 29 18:18:39 Paradox kernel: 00000-9FFFF write-back
Jun 29 18:18:39 Paradox kernel: A0000-BFFFF uncachable
Jun 29 18:18:39 Paradox kernel: C0000-CFFFF write-protect
Jun 29 18:18:39 Paradox kernel: D0000-E7FFF uncachable
Jun 29 18:18:39 Paradox kernel: E8000-FFFFF write-protect
Jun 29 18:18:39 Paradox kernel: MTRR variable ranges enabled:
Jun 29 18:18:39 Paradox kernel: 0 base 000000000 mask E00000000 write-back
Jun 29 18:18:39 Paradox kernel: 1 base 200000000 mask FC0000000 write-back
Jun 29 18:18:39 Paradox kernel: 2 base 0BB800000 mask FFF800000 uncachable
Jun 29 18:18:39 Paradox kernel: 3 base 0BC000000 mask FFC000000 uncachable
Jun 29 18:18:39 Paradox kernel: 4 base 0C0000000 mask FC0000000 uncachable


The whole “Rainbow Screen” thing never happened on Windows, so I can only “assume” that it’s something to be fixed or configured on Linux, but that’s only speculation, I don’t know much about these things, but any help is appreciated. :slight_smile:

Suspend to RAM doesn’t play nice with the Linux graphics stack. If you fully shutdown and it’s still happening, that’s cause for concern. If it’s only happening on suspend to RAM and recalling the RAM, Suspend is the issue.

2 Likes

Yes. All right, you’re using the regular Ubuntu kernel. Maybe you could try the latest mainline kernel and see if you have better luck with it (it does not automatically update, so you would have to manually download updates if you choose to stick with it)?

Navigating journalctl --catalog --boot=[int] (plain --boot is the same as selecting the number of your latest, current, boot; int — integer) is like navigating Vim, so you have to press Shift+G to get to the bottom of the log (I am assuming that you are simply shutting the computer down by force, in which case the bottom of the log should show the error without the need to navigate upwards with the up arrow key). What you pasted in your reply was just the initialization of the hardware during bootup.

Good luck!

Edit

As my previous laptop, a 2016 dual-core HP AMD laptop, can attest, that is quite true, but it doesn’t usually lead to such psychedelic results as the one shown above. Thankfully, my Dell Inspiron has no issues with suspension to RAM (I was trying to get a newer AMD laptop, but time was short and the only decent laptop that was available in Sarajevo at that SARS-CoV-2-striken time was my current blue’n’green Inspiron; there was actually a really good Ryzen laptop, but it went out of stock at the last minute and I still wanted dedicated graphics, so…).

If only Ubuntu’s latest version of GNOME supported EGLStreams…

1 Like