How can I have less “flickering” when booting?












8















What I expected




  1. Bios booting

  2. Loading screen

  3. Login window, similar theme as loading screen

  4. Personalized theme after login - by default similar themed like the login screen


What I observed



See https://www.youtube.com/watch?v=qC3EwNMvfS0 :




  1. 0:00 - 0:08 Bios

  2. 0:09 Black (no light)

  3. 0:10 - 0:11 Black (light)

  4. 0:12 Black (no light)

  5. 0:13 - 0:15 Bright screen

  6. 0:16 Black with light

  7. 0:17 Black without light

  8. 0:18 Loading screen

  9. 0:19 Change of Background

  10. 0:22 - 0:29 Login

  11. 0:30 Black with light

  12. 0:32 My wallpaper


My question



Can some of those observed changes be removed / made to look similar?



For example, I don't know what happens in the observed steps 2 - 7. Or why step 11 exists.



Making the login / loading screen look more similar / more similar to my personal screen is NOT the main question.










share|improve this question




















  • 1





    Only 14 people have seen this question, although 8 months have passed since I asked. Let's see what a 50-bounty changes :-)

    – Martin Thoma
    Feb 8 at 11:10











  • Some clarifications: 1. Is Ubuntu MATE is the only system installed to the machine? 2. Do you still want to see the MATE loading screen (before login)? 3. Do you need compositing feature turned on? Based on given information, I might be able to post an answer.

    – clearkimura
    Feb 8 at 18:11











  • (1) Yes, Ubuntu MATE is the only system installed on that laptop. (2) I don't care about the MATE loading screen too much (3) What is the compositing feature?

    – Martin Thoma
    Feb 8 at 19:54











  • Basically, the additional "flickering" you see most likely caused by combination of Ubuntu MATE (compared to other Ubuntu derivative) and your hardware driver support. It's all right, I will clarify the compositing feature from my side before writing my answer.

    – clearkimura
    Feb 9 at 11:01











  • I changed my Dell BIOS load time from 16 seconds to 4 seconds. Your hardware specs are missing, especially the video graphics. Posting contents of /etc/default/grub file would be helpful too.

    – WinEunuuchs2Unix
    Feb 10 at 12:11
















8















What I expected




  1. Bios booting

  2. Loading screen

  3. Login window, similar theme as loading screen

  4. Personalized theme after login - by default similar themed like the login screen


What I observed



See https://www.youtube.com/watch?v=qC3EwNMvfS0 :




  1. 0:00 - 0:08 Bios

  2. 0:09 Black (no light)

  3. 0:10 - 0:11 Black (light)

  4. 0:12 Black (no light)

  5. 0:13 - 0:15 Bright screen

  6. 0:16 Black with light

  7. 0:17 Black without light

  8. 0:18 Loading screen

  9. 0:19 Change of Background

  10. 0:22 - 0:29 Login

  11. 0:30 Black with light

  12. 0:32 My wallpaper


My question



Can some of those observed changes be removed / made to look similar?



For example, I don't know what happens in the observed steps 2 - 7. Or why step 11 exists.



Making the login / loading screen look more similar / more similar to my personal screen is NOT the main question.










share|improve this question




















  • 1





    Only 14 people have seen this question, although 8 months have passed since I asked. Let's see what a 50-bounty changes :-)

    – Martin Thoma
    Feb 8 at 11:10











  • Some clarifications: 1. Is Ubuntu MATE is the only system installed to the machine? 2. Do you still want to see the MATE loading screen (before login)? 3. Do you need compositing feature turned on? Based on given information, I might be able to post an answer.

    – clearkimura
    Feb 8 at 18:11











  • (1) Yes, Ubuntu MATE is the only system installed on that laptop. (2) I don't care about the MATE loading screen too much (3) What is the compositing feature?

    – Martin Thoma
    Feb 8 at 19:54











  • Basically, the additional "flickering" you see most likely caused by combination of Ubuntu MATE (compared to other Ubuntu derivative) and your hardware driver support. It's all right, I will clarify the compositing feature from my side before writing my answer.

    – clearkimura
    Feb 9 at 11:01











  • I changed my Dell BIOS load time from 16 seconds to 4 seconds. Your hardware specs are missing, especially the video graphics. Posting contents of /etc/default/grub file would be helpful too.

    – WinEunuuchs2Unix
    Feb 10 at 12:11














8












8








8


1






What I expected




  1. Bios booting

  2. Loading screen

  3. Login window, similar theme as loading screen

  4. Personalized theme after login - by default similar themed like the login screen


What I observed



See https://www.youtube.com/watch?v=qC3EwNMvfS0 :




  1. 0:00 - 0:08 Bios

  2. 0:09 Black (no light)

  3. 0:10 - 0:11 Black (light)

  4. 0:12 Black (no light)

  5. 0:13 - 0:15 Bright screen

  6. 0:16 Black with light

  7. 0:17 Black without light

  8. 0:18 Loading screen

  9. 0:19 Change of Background

  10. 0:22 - 0:29 Login

  11. 0:30 Black with light

  12. 0:32 My wallpaper


My question



Can some of those observed changes be removed / made to look similar?



For example, I don't know what happens in the observed steps 2 - 7. Or why step 11 exists.



Making the login / loading screen look more similar / more similar to my personal screen is NOT the main question.










share|improve this question
















What I expected




  1. Bios booting

  2. Loading screen

  3. Login window, similar theme as loading screen

  4. Personalized theme after login - by default similar themed like the login screen


What I observed



See https://www.youtube.com/watch?v=qC3EwNMvfS0 :




  1. 0:00 - 0:08 Bios

  2. 0:09 Black (no light)

  3. 0:10 - 0:11 Black (light)

  4. 0:12 Black (no light)

  5. 0:13 - 0:15 Bright screen

  6. 0:16 Black with light

  7. 0:17 Black without light

  8. 0:18 Loading screen

  9. 0:19 Change of Background

  10. 0:22 - 0:29 Login

  11. 0:30 Black with light

  12. 0:32 My wallpaper


My question



Can some of those observed changes be removed / made to look similar?



For example, I don't know what happens in the observed steps 2 - 7. Or why step 11 exists.



Making the login / loading screen look more similar / more similar to my personal screen is NOT the main question.







boot themes 18.04 mate






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited May 14 '18 at 18:22







Martin Thoma

















asked May 14 '18 at 18:13









Martin ThomaMartin Thoma

6,833155275




6,833155275








  • 1





    Only 14 people have seen this question, although 8 months have passed since I asked. Let's see what a 50-bounty changes :-)

    – Martin Thoma
    Feb 8 at 11:10











  • Some clarifications: 1. Is Ubuntu MATE is the only system installed to the machine? 2. Do you still want to see the MATE loading screen (before login)? 3. Do you need compositing feature turned on? Based on given information, I might be able to post an answer.

    – clearkimura
    Feb 8 at 18:11











  • (1) Yes, Ubuntu MATE is the only system installed on that laptop. (2) I don't care about the MATE loading screen too much (3) What is the compositing feature?

    – Martin Thoma
    Feb 8 at 19:54











  • Basically, the additional "flickering" you see most likely caused by combination of Ubuntu MATE (compared to other Ubuntu derivative) and your hardware driver support. It's all right, I will clarify the compositing feature from my side before writing my answer.

    – clearkimura
    Feb 9 at 11:01











  • I changed my Dell BIOS load time from 16 seconds to 4 seconds. Your hardware specs are missing, especially the video graphics. Posting contents of /etc/default/grub file would be helpful too.

    – WinEunuuchs2Unix
    Feb 10 at 12:11














  • 1





    Only 14 people have seen this question, although 8 months have passed since I asked. Let's see what a 50-bounty changes :-)

    – Martin Thoma
    Feb 8 at 11:10











  • Some clarifications: 1. Is Ubuntu MATE is the only system installed to the machine? 2. Do you still want to see the MATE loading screen (before login)? 3. Do you need compositing feature turned on? Based on given information, I might be able to post an answer.

    – clearkimura
    Feb 8 at 18:11











  • (1) Yes, Ubuntu MATE is the only system installed on that laptop. (2) I don't care about the MATE loading screen too much (3) What is the compositing feature?

    – Martin Thoma
    Feb 8 at 19:54











  • Basically, the additional "flickering" you see most likely caused by combination of Ubuntu MATE (compared to other Ubuntu derivative) and your hardware driver support. It's all right, I will clarify the compositing feature from my side before writing my answer.

    – clearkimura
    Feb 9 at 11:01











  • I changed my Dell BIOS load time from 16 seconds to 4 seconds. Your hardware specs are missing, especially the video graphics. Posting contents of /etc/default/grub file would be helpful too.

    – WinEunuuchs2Unix
    Feb 10 at 12:11








1




1





Only 14 people have seen this question, although 8 months have passed since I asked. Let's see what a 50-bounty changes :-)

– Martin Thoma
Feb 8 at 11:10





Only 14 people have seen this question, although 8 months have passed since I asked. Let's see what a 50-bounty changes :-)

– Martin Thoma
Feb 8 at 11:10













Some clarifications: 1. Is Ubuntu MATE is the only system installed to the machine? 2. Do you still want to see the MATE loading screen (before login)? 3. Do you need compositing feature turned on? Based on given information, I might be able to post an answer.

– clearkimura
Feb 8 at 18:11





Some clarifications: 1. Is Ubuntu MATE is the only system installed to the machine? 2. Do you still want to see the MATE loading screen (before login)? 3. Do you need compositing feature turned on? Based on given information, I might be able to post an answer.

– clearkimura
Feb 8 at 18:11













(1) Yes, Ubuntu MATE is the only system installed on that laptop. (2) I don't care about the MATE loading screen too much (3) What is the compositing feature?

– Martin Thoma
Feb 8 at 19:54





(1) Yes, Ubuntu MATE is the only system installed on that laptop. (2) I don't care about the MATE loading screen too much (3) What is the compositing feature?

– Martin Thoma
Feb 8 at 19:54













Basically, the additional "flickering" you see most likely caused by combination of Ubuntu MATE (compared to other Ubuntu derivative) and your hardware driver support. It's all right, I will clarify the compositing feature from my side before writing my answer.

– clearkimura
Feb 9 at 11:01





Basically, the additional "flickering" you see most likely caused by combination of Ubuntu MATE (compared to other Ubuntu derivative) and your hardware driver support. It's all right, I will clarify the compositing feature from my side before writing my answer.

– clearkimura
Feb 9 at 11:01













I changed my Dell BIOS load time from 16 seconds to 4 seconds. Your hardware specs are missing, especially the video graphics. Posting contents of /etc/default/grub file would be helpful too.

– WinEunuuchs2Unix
Feb 10 at 12:11





I changed my Dell BIOS load time from 16 seconds to 4 seconds. Your hardware specs are missing, especially the video graphics. Posting contents of /etc/default/grub file would be helpful too.

– WinEunuuchs2Unix
Feb 10 at 12:11










2 Answers
2






active

oldest

votes


















5














If you are using an intel integrated gpu, you can try adding the i915.fastboot=1 kernel parameter to avoid the flickering caused by unnecessary mode-setting operations.



First, try adding it temporarily at grub:




  1. Start your system and press and hold Shift (or Esc in UEFI systems) for grub menu to show up.

  2. Press e to edit the commands before booting.

  3. Add i915.fastboot=1 after quiet splash


Notice if it reduces flickering and if it has any side effects, like screen brightness not working.



To add this parameter permanently:




  1. From a terminal run gksudo gedit /etc/default/grub, replace gedit with your text editor.

  2. Add i915.fastboot=1 after quiet splash in line
    GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

  3. Run sudo update-grub


  4. Reboot and determine if it reduces flickering.




    • How do I add a kernel boot parameter?

    • https://www.phoronix.com/scan.php?page=news_item&px=Intel-Fastboot-Default-2019-Try








share|improve this answer


























  • I don't think it had any effect at all. Background of this: wiki.archlinux.org/index.php/intel_graphics#Fastboot

    – Martin Thoma
    Feb 14 at 21:46



















3





+50









The "flickering" occurs most likely when running Ubuntu MATE or a similar distribution. Such instances of screen on-and-off may be, but not necessarily, influenced by the graphic driver support.



In the following sections, I will use these terms:




  • "blank" to refer the instance when screen becomes completely dark with no light at all;

  • "shine" to refer the instance when screen at maximum brightness;

  • "blanking" to refer to the instance when screen becomes dark with light between login and desktop.


Based on the boot process described by OP, there are three instances of "blank", one instance of "shine" and one instance of "blanking".



The blank 1




0:00~0:08 Bios
0:09 Black (no light) <-- this



This is a common instance, which indicates the boot process proceeding from BIOS/UEFI to subsequent stage (usually MBR for a BIOS machine). The first blank is inevitable and most users can do nothing about this.



The blank 2




0:10~0:11 Black (light)
0:12 Black (no light) <-- this



The second blank is most likely shown when proceeding from the subsequent stage to the boot loader (usually GRUB for a GNU/Linux machine). The default timeout is usually set to 10 seconds, although built-in configuration may automatically reduce the timeout to several seconds when no other operating system is found. This will still cause some delay.



Workaround: Ensure boot loader timeout is zero and hidden.



In terminal, run sudo nano /etc/default/grub and modify the relevant lines as follows, then save changes by ^X Exit: press Ctrl+X then press Y and press Enter. Then, run sudo update-grub to update the modified configuration (before running the last command, user may want to apply the next workaround together in the same configuration file).



...
#GRUB_HIDDEN_TIMEOUT=0
#GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=0
...


The two lines with GRUB_HIDDEN... are deprecated parameters and should be disabled with comment syntax #. Not really related to the blank; just to rule out any unexpected result.



When other operating systems were found via 'os-prober', the timeout can not be zero and can not be hidden: the built-in configuration will enable the boot menu and timeout is only effective with a non-zero value. For a multiboot system, the menu will appear for at least 1 second and the second blank may be shown anyway.



The shine




0:13~0:15 Bright screen



This is most likely hardware-dependent. The symptom looks similar to this dated post or another dated post on Ask Ubuntu. Otherwise, look up by the machine model or hardware specification at relevant community sites for most appropriate solution.



The blank 3




0:16 Black with light
0:17 Black without light <-- this
0:18 Loading screen



The third blank is most likely shown when boot loader runs the application that provides a graphical boot animation (usually Plymouth for an Ubuntu-based distribution) a.k.a. boot splash. The boot splash has no meaningful purpose especially when the boot process is fast; what is shown by OP is very fast.



Workaround: Ensure boot loader does not run the boot splash.



Similarly run with sudo permission to edit /etc/default/grub and modify the line that contains "quiet splash" and change that part to "quiet", then save the changes. Finally, run sudo update-grub to update the modified configuration.



...
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
...


When the boot splash is disabled, some boot message may be shown instead during the boot process. For some reason, the result is inconsistent when running Ubuntu MATE (sometimes showing many lines despite the same "quiet" option), which is otherwise not seen when running other Ubuntu derivative like Xubuntu.



The blanking




0:19 Change of Background
0:22~0:29 Login
0:30 Black with light <-- this
0:32 My wallpaper



The blanking that occurs between login and desktop, is most likely specific to GNOME or similar desktop environments like MATE. I have confirmed that: in comparison, Cinnamon does show blanking like MATE; in contrast, Xfce does not show such behaviour.



Initially, I thought the blanking may be due to transition of loading the compositing window manager; however, changing or disabling the compositor in MATE either way does not affect the blanking behaviour. So the actual problem is something else.



Workaround: For Ubuntu MATE, the login screen should use a true black colour (#000000).



Go to Control Center > Login Window - Appearance and empty the path for Background, and then change Background colour to black (select the darkest monochrome shade in the bottom-left area). Close the window to finish. The main purpose of this workaround is to minimize the blanking; user may also change the theme to improve contrast and login window visibility.



The result



With workarounds above, most end-users will see only the first blank during the boot process. Except, OP and affected users will need to solve the shine issue separately.




  • blank 1: Always shown (inevitable)

  • blank 2: Use workaround

  • shine: Separate solution (hardware-dependent)

  • blank 3: Use workaround

  • blanking: Use workaround (software-dependent)


Tested workarounds with Ubuntu MATE 18.04, running on 32-bit machine Intel Celeron 1.6 GHz with Intel graphics. Minimal installation has boot time of about 45 seconds (non-optimal), with no shine and only the first blank and blanking were seen.






share|improve this answer



















  • 1





    When I remove the splash screen, I see even more flickering. But I admire the effort you put in the answer

    – Martin Thoma
    Feb 14 at 21:59











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1036212%2fhow-can-i-have-less-flickering-when-booting%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes









5














If you are using an intel integrated gpu, you can try adding the i915.fastboot=1 kernel parameter to avoid the flickering caused by unnecessary mode-setting operations.



First, try adding it temporarily at grub:




  1. Start your system and press and hold Shift (or Esc in UEFI systems) for grub menu to show up.

  2. Press e to edit the commands before booting.

  3. Add i915.fastboot=1 after quiet splash


Notice if it reduces flickering and if it has any side effects, like screen brightness not working.



To add this parameter permanently:




  1. From a terminal run gksudo gedit /etc/default/grub, replace gedit with your text editor.

  2. Add i915.fastboot=1 after quiet splash in line
    GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

  3. Run sudo update-grub


  4. Reboot and determine if it reduces flickering.




    • How do I add a kernel boot parameter?

    • https://www.phoronix.com/scan.php?page=news_item&px=Intel-Fastboot-Default-2019-Try








share|improve this answer


























  • I don't think it had any effect at all. Background of this: wiki.archlinux.org/index.php/intel_graphics#Fastboot

    – Martin Thoma
    Feb 14 at 21:46
















5














If you are using an intel integrated gpu, you can try adding the i915.fastboot=1 kernel parameter to avoid the flickering caused by unnecessary mode-setting operations.



First, try adding it temporarily at grub:




  1. Start your system and press and hold Shift (or Esc in UEFI systems) for grub menu to show up.

  2. Press e to edit the commands before booting.

  3. Add i915.fastboot=1 after quiet splash


Notice if it reduces flickering and if it has any side effects, like screen brightness not working.



To add this parameter permanently:




  1. From a terminal run gksudo gedit /etc/default/grub, replace gedit with your text editor.

  2. Add i915.fastboot=1 after quiet splash in line
    GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

  3. Run sudo update-grub


  4. Reboot and determine if it reduces flickering.




    • How do I add a kernel boot parameter?

    • https://www.phoronix.com/scan.php?page=news_item&px=Intel-Fastboot-Default-2019-Try








share|improve this answer


























  • I don't think it had any effect at all. Background of this: wiki.archlinux.org/index.php/intel_graphics#Fastboot

    – Martin Thoma
    Feb 14 at 21:46














5












5








5







If you are using an intel integrated gpu, you can try adding the i915.fastboot=1 kernel parameter to avoid the flickering caused by unnecessary mode-setting operations.



First, try adding it temporarily at grub:




  1. Start your system and press and hold Shift (or Esc in UEFI systems) for grub menu to show up.

  2. Press e to edit the commands before booting.

  3. Add i915.fastboot=1 after quiet splash


Notice if it reduces flickering and if it has any side effects, like screen brightness not working.



To add this parameter permanently:




  1. From a terminal run gksudo gedit /etc/default/grub, replace gedit with your text editor.

  2. Add i915.fastboot=1 after quiet splash in line
    GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

  3. Run sudo update-grub


  4. Reboot and determine if it reduces flickering.




    • How do I add a kernel boot parameter?

    • https://www.phoronix.com/scan.php?page=news_item&px=Intel-Fastboot-Default-2019-Try








share|improve this answer















If you are using an intel integrated gpu, you can try adding the i915.fastboot=1 kernel parameter to avoid the flickering caused by unnecessary mode-setting operations.



First, try adding it temporarily at grub:




  1. Start your system and press and hold Shift (or Esc in UEFI systems) for grub menu to show up.

  2. Press e to edit the commands before booting.

  3. Add i915.fastboot=1 after quiet splash


Notice if it reduces flickering and if it has any side effects, like screen brightness not working.



To add this parameter permanently:




  1. From a terminal run gksudo gedit /etc/default/grub, replace gedit with your text editor.

  2. Add i915.fastboot=1 after quiet splash in line
    GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

  3. Run sudo update-grub


  4. Reboot and determine if it reduces flickering.




    • How do I add a kernel boot parameter?

    • https://www.phoronix.com/scan.php?page=news_item&px=Intel-Fastboot-Default-2019-Try









share|improve this answer














share|improve this answer



share|improve this answer








edited Feb 12 at 11:26

























answered Feb 9 at 8:23









TheLinuxGKTheLinuxGK

146412




146412













  • I don't think it had any effect at all. Background of this: wiki.archlinux.org/index.php/intel_graphics#Fastboot

    – Martin Thoma
    Feb 14 at 21:46



















  • I don't think it had any effect at all. Background of this: wiki.archlinux.org/index.php/intel_graphics#Fastboot

    – Martin Thoma
    Feb 14 at 21:46

















I don't think it had any effect at all. Background of this: wiki.archlinux.org/index.php/intel_graphics#Fastboot

– Martin Thoma
Feb 14 at 21:46





I don't think it had any effect at all. Background of this: wiki.archlinux.org/index.php/intel_graphics#Fastboot

– Martin Thoma
Feb 14 at 21:46













3





+50









The "flickering" occurs most likely when running Ubuntu MATE or a similar distribution. Such instances of screen on-and-off may be, but not necessarily, influenced by the graphic driver support.



In the following sections, I will use these terms:




  • "blank" to refer the instance when screen becomes completely dark with no light at all;

  • "shine" to refer the instance when screen at maximum brightness;

  • "blanking" to refer to the instance when screen becomes dark with light between login and desktop.


Based on the boot process described by OP, there are three instances of "blank", one instance of "shine" and one instance of "blanking".



The blank 1




0:00~0:08 Bios
0:09 Black (no light) <-- this



This is a common instance, which indicates the boot process proceeding from BIOS/UEFI to subsequent stage (usually MBR for a BIOS machine). The first blank is inevitable and most users can do nothing about this.



The blank 2




0:10~0:11 Black (light)
0:12 Black (no light) <-- this



The second blank is most likely shown when proceeding from the subsequent stage to the boot loader (usually GRUB for a GNU/Linux machine). The default timeout is usually set to 10 seconds, although built-in configuration may automatically reduce the timeout to several seconds when no other operating system is found. This will still cause some delay.



Workaround: Ensure boot loader timeout is zero and hidden.



In terminal, run sudo nano /etc/default/grub and modify the relevant lines as follows, then save changes by ^X Exit: press Ctrl+X then press Y and press Enter. Then, run sudo update-grub to update the modified configuration (before running the last command, user may want to apply the next workaround together in the same configuration file).



...
#GRUB_HIDDEN_TIMEOUT=0
#GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=0
...


The two lines with GRUB_HIDDEN... are deprecated parameters and should be disabled with comment syntax #. Not really related to the blank; just to rule out any unexpected result.



When other operating systems were found via 'os-prober', the timeout can not be zero and can not be hidden: the built-in configuration will enable the boot menu and timeout is only effective with a non-zero value. For a multiboot system, the menu will appear for at least 1 second and the second blank may be shown anyway.



The shine




0:13~0:15 Bright screen



This is most likely hardware-dependent. The symptom looks similar to this dated post or another dated post on Ask Ubuntu. Otherwise, look up by the machine model or hardware specification at relevant community sites for most appropriate solution.



The blank 3




0:16 Black with light
0:17 Black without light <-- this
0:18 Loading screen



The third blank is most likely shown when boot loader runs the application that provides a graphical boot animation (usually Plymouth for an Ubuntu-based distribution) a.k.a. boot splash. The boot splash has no meaningful purpose especially when the boot process is fast; what is shown by OP is very fast.



Workaround: Ensure boot loader does not run the boot splash.



Similarly run with sudo permission to edit /etc/default/grub and modify the line that contains "quiet splash" and change that part to "quiet", then save the changes. Finally, run sudo update-grub to update the modified configuration.



...
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
...


When the boot splash is disabled, some boot message may be shown instead during the boot process. For some reason, the result is inconsistent when running Ubuntu MATE (sometimes showing many lines despite the same "quiet" option), which is otherwise not seen when running other Ubuntu derivative like Xubuntu.



The blanking




0:19 Change of Background
0:22~0:29 Login
0:30 Black with light <-- this
0:32 My wallpaper



The blanking that occurs between login and desktop, is most likely specific to GNOME or similar desktop environments like MATE. I have confirmed that: in comparison, Cinnamon does show blanking like MATE; in contrast, Xfce does not show such behaviour.



Initially, I thought the blanking may be due to transition of loading the compositing window manager; however, changing or disabling the compositor in MATE either way does not affect the blanking behaviour. So the actual problem is something else.



Workaround: For Ubuntu MATE, the login screen should use a true black colour (#000000).



Go to Control Center > Login Window - Appearance and empty the path for Background, and then change Background colour to black (select the darkest monochrome shade in the bottom-left area). Close the window to finish. The main purpose of this workaround is to minimize the blanking; user may also change the theme to improve contrast and login window visibility.



The result



With workarounds above, most end-users will see only the first blank during the boot process. Except, OP and affected users will need to solve the shine issue separately.




  • blank 1: Always shown (inevitable)

  • blank 2: Use workaround

  • shine: Separate solution (hardware-dependent)

  • blank 3: Use workaround

  • blanking: Use workaround (software-dependent)


Tested workarounds with Ubuntu MATE 18.04, running on 32-bit machine Intel Celeron 1.6 GHz with Intel graphics. Minimal installation has boot time of about 45 seconds (non-optimal), with no shine and only the first blank and blanking were seen.






share|improve this answer



















  • 1





    When I remove the splash screen, I see even more flickering. But I admire the effort you put in the answer

    – Martin Thoma
    Feb 14 at 21:59
















3





+50









The "flickering" occurs most likely when running Ubuntu MATE or a similar distribution. Such instances of screen on-and-off may be, but not necessarily, influenced by the graphic driver support.



In the following sections, I will use these terms:




  • "blank" to refer the instance when screen becomes completely dark with no light at all;

  • "shine" to refer the instance when screen at maximum brightness;

  • "blanking" to refer to the instance when screen becomes dark with light between login and desktop.


Based on the boot process described by OP, there are three instances of "blank", one instance of "shine" and one instance of "blanking".



The blank 1




0:00~0:08 Bios
0:09 Black (no light) <-- this



This is a common instance, which indicates the boot process proceeding from BIOS/UEFI to subsequent stage (usually MBR for a BIOS machine). The first blank is inevitable and most users can do nothing about this.



The blank 2




0:10~0:11 Black (light)
0:12 Black (no light) <-- this



The second blank is most likely shown when proceeding from the subsequent stage to the boot loader (usually GRUB for a GNU/Linux machine). The default timeout is usually set to 10 seconds, although built-in configuration may automatically reduce the timeout to several seconds when no other operating system is found. This will still cause some delay.



Workaround: Ensure boot loader timeout is zero and hidden.



In terminal, run sudo nano /etc/default/grub and modify the relevant lines as follows, then save changes by ^X Exit: press Ctrl+X then press Y and press Enter. Then, run sudo update-grub to update the modified configuration (before running the last command, user may want to apply the next workaround together in the same configuration file).



...
#GRUB_HIDDEN_TIMEOUT=0
#GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=0
...


The two lines with GRUB_HIDDEN... are deprecated parameters and should be disabled with comment syntax #. Not really related to the blank; just to rule out any unexpected result.



When other operating systems were found via 'os-prober', the timeout can not be zero and can not be hidden: the built-in configuration will enable the boot menu and timeout is only effective with a non-zero value. For a multiboot system, the menu will appear for at least 1 second and the second blank may be shown anyway.



The shine




0:13~0:15 Bright screen



This is most likely hardware-dependent. The symptom looks similar to this dated post or another dated post on Ask Ubuntu. Otherwise, look up by the machine model or hardware specification at relevant community sites for most appropriate solution.



The blank 3




0:16 Black with light
0:17 Black without light <-- this
0:18 Loading screen



The third blank is most likely shown when boot loader runs the application that provides a graphical boot animation (usually Plymouth for an Ubuntu-based distribution) a.k.a. boot splash. The boot splash has no meaningful purpose especially when the boot process is fast; what is shown by OP is very fast.



Workaround: Ensure boot loader does not run the boot splash.



Similarly run with sudo permission to edit /etc/default/grub and modify the line that contains "quiet splash" and change that part to "quiet", then save the changes. Finally, run sudo update-grub to update the modified configuration.



...
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
...


When the boot splash is disabled, some boot message may be shown instead during the boot process. For some reason, the result is inconsistent when running Ubuntu MATE (sometimes showing many lines despite the same "quiet" option), which is otherwise not seen when running other Ubuntu derivative like Xubuntu.



The blanking




0:19 Change of Background
0:22~0:29 Login
0:30 Black with light <-- this
0:32 My wallpaper



The blanking that occurs between login and desktop, is most likely specific to GNOME or similar desktop environments like MATE. I have confirmed that: in comparison, Cinnamon does show blanking like MATE; in contrast, Xfce does not show such behaviour.



Initially, I thought the blanking may be due to transition of loading the compositing window manager; however, changing or disabling the compositor in MATE either way does not affect the blanking behaviour. So the actual problem is something else.



Workaround: For Ubuntu MATE, the login screen should use a true black colour (#000000).



Go to Control Center > Login Window - Appearance and empty the path for Background, and then change Background colour to black (select the darkest monochrome shade in the bottom-left area). Close the window to finish. The main purpose of this workaround is to minimize the blanking; user may also change the theme to improve contrast and login window visibility.



The result



With workarounds above, most end-users will see only the first blank during the boot process. Except, OP and affected users will need to solve the shine issue separately.




  • blank 1: Always shown (inevitable)

  • blank 2: Use workaround

  • shine: Separate solution (hardware-dependent)

  • blank 3: Use workaround

  • blanking: Use workaround (software-dependent)


Tested workarounds with Ubuntu MATE 18.04, running on 32-bit machine Intel Celeron 1.6 GHz with Intel graphics. Minimal installation has boot time of about 45 seconds (non-optimal), with no shine and only the first blank and blanking were seen.






share|improve this answer



















  • 1





    When I remove the splash screen, I see even more flickering. But I admire the effort you put in the answer

    – Martin Thoma
    Feb 14 at 21:59














3





+50







3





+50



3




+50





The "flickering" occurs most likely when running Ubuntu MATE or a similar distribution. Such instances of screen on-and-off may be, but not necessarily, influenced by the graphic driver support.



In the following sections, I will use these terms:




  • "blank" to refer the instance when screen becomes completely dark with no light at all;

  • "shine" to refer the instance when screen at maximum brightness;

  • "blanking" to refer to the instance when screen becomes dark with light between login and desktop.


Based on the boot process described by OP, there are three instances of "blank", one instance of "shine" and one instance of "blanking".



The blank 1




0:00~0:08 Bios
0:09 Black (no light) <-- this



This is a common instance, which indicates the boot process proceeding from BIOS/UEFI to subsequent stage (usually MBR for a BIOS machine). The first blank is inevitable and most users can do nothing about this.



The blank 2




0:10~0:11 Black (light)
0:12 Black (no light) <-- this



The second blank is most likely shown when proceeding from the subsequent stage to the boot loader (usually GRUB for a GNU/Linux machine). The default timeout is usually set to 10 seconds, although built-in configuration may automatically reduce the timeout to several seconds when no other operating system is found. This will still cause some delay.



Workaround: Ensure boot loader timeout is zero and hidden.



In terminal, run sudo nano /etc/default/grub and modify the relevant lines as follows, then save changes by ^X Exit: press Ctrl+X then press Y and press Enter. Then, run sudo update-grub to update the modified configuration (before running the last command, user may want to apply the next workaround together in the same configuration file).



...
#GRUB_HIDDEN_TIMEOUT=0
#GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=0
...


The two lines with GRUB_HIDDEN... are deprecated parameters and should be disabled with comment syntax #. Not really related to the blank; just to rule out any unexpected result.



When other operating systems were found via 'os-prober', the timeout can not be zero and can not be hidden: the built-in configuration will enable the boot menu and timeout is only effective with a non-zero value. For a multiboot system, the menu will appear for at least 1 second and the second blank may be shown anyway.



The shine




0:13~0:15 Bright screen



This is most likely hardware-dependent. The symptom looks similar to this dated post or another dated post on Ask Ubuntu. Otherwise, look up by the machine model or hardware specification at relevant community sites for most appropriate solution.



The blank 3




0:16 Black with light
0:17 Black without light <-- this
0:18 Loading screen



The third blank is most likely shown when boot loader runs the application that provides a graphical boot animation (usually Plymouth for an Ubuntu-based distribution) a.k.a. boot splash. The boot splash has no meaningful purpose especially when the boot process is fast; what is shown by OP is very fast.



Workaround: Ensure boot loader does not run the boot splash.



Similarly run with sudo permission to edit /etc/default/grub and modify the line that contains "quiet splash" and change that part to "quiet", then save the changes. Finally, run sudo update-grub to update the modified configuration.



...
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
...


When the boot splash is disabled, some boot message may be shown instead during the boot process. For some reason, the result is inconsistent when running Ubuntu MATE (sometimes showing many lines despite the same "quiet" option), which is otherwise not seen when running other Ubuntu derivative like Xubuntu.



The blanking




0:19 Change of Background
0:22~0:29 Login
0:30 Black with light <-- this
0:32 My wallpaper



The blanking that occurs between login and desktop, is most likely specific to GNOME or similar desktop environments like MATE. I have confirmed that: in comparison, Cinnamon does show blanking like MATE; in contrast, Xfce does not show such behaviour.



Initially, I thought the blanking may be due to transition of loading the compositing window manager; however, changing or disabling the compositor in MATE either way does not affect the blanking behaviour. So the actual problem is something else.



Workaround: For Ubuntu MATE, the login screen should use a true black colour (#000000).



Go to Control Center > Login Window - Appearance and empty the path for Background, and then change Background colour to black (select the darkest monochrome shade in the bottom-left area). Close the window to finish. The main purpose of this workaround is to minimize the blanking; user may also change the theme to improve contrast and login window visibility.



The result



With workarounds above, most end-users will see only the first blank during the boot process. Except, OP and affected users will need to solve the shine issue separately.




  • blank 1: Always shown (inevitable)

  • blank 2: Use workaround

  • shine: Separate solution (hardware-dependent)

  • blank 3: Use workaround

  • blanking: Use workaround (software-dependent)


Tested workarounds with Ubuntu MATE 18.04, running on 32-bit machine Intel Celeron 1.6 GHz with Intel graphics. Minimal installation has boot time of about 45 seconds (non-optimal), with no shine and only the first blank and blanking were seen.






share|improve this answer













The "flickering" occurs most likely when running Ubuntu MATE or a similar distribution. Such instances of screen on-and-off may be, but not necessarily, influenced by the graphic driver support.



In the following sections, I will use these terms:




  • "blank" to refer the instance when screen becomes completely dark with no light at all;

  • "shine" to refer the instance when screen at maximum brightness;

  • "blanking" to refer to the instance when screen becomes dark with light between login and desktop.


Based on the boot process described by OP, there are three instances of "blank", one instance of "shine" and one instance of "blanking".



The blank 1




0:00~0:08 Bios
0:09 Black (no light) <-- this



This is a common instance, which indicates the boot process proceeding from BIOS/UEFI to subsequent stage (usually MBR for a BIOS machine). The first blank is inevitable and most users can do nothing about this.



The blank 2




0:10~0:11 Black (light)
0:12 Black (no light) <-- this



The second blank is most likely shown when proceeding from the subsequent stage to the boot loader (usually GRUB for a GNU/Linux machine). The default timeout is usually set to 10 seconds, although built-in configuration may automatically reduce the timeout to several seconds when no other operating system is found. This will still cause some delay.



Workaround: Ensure boot loader timeout is zero and hidden.



In terminal, run sudo nano /etc/default/grub and modify the relevant lines as follows, then save changes by ^X Exit: press Ctrl+X then press Y and press Enter. Then, run sudo update-grub to update the modified configuration (before running the last command, user may want to apply the next workaround together in the same configuration file).



...
#GRUB_HIDDEN_TIMEOUT=0
#GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=0
...


The two lines with GRUB_HIDDEN... are deprecated parameters and should be disabled with comment syntax #. Not really related to the blank; just to rule out any unexpected result.



When other operating systems were found via 'os-prober', the timeout can not be zero and can not be hidden: the built-in configuration will enable the boot menu and timeout is only effective with a non-zero value. For a multiboot system, the menu will appear for at least 1 second and the second blank may be shown anyway.



The shine




0:13~0:15 Bright screen



This is most likely hardware-dependent. The symptom looks similar to this dated post or another dated post on Ask Ubuntu. Otherwise, look up by the machine model or hardware specification at relevant community sites for most appropriate solution.



The blank 3




0:16 Black with light
0:17 Black without light <-- this
0:18 Loading screen



The third blank is most likely shown when boot loader runs the application that provides a graphical boot animation (usually Plymouth for an Ubuntu-based distribution) a.k.a. boot splash. The boot splash has no meaningful purpose especially when the boot process is fast; what is shown by OP is very fast.



Workaround: Ensure boot loader does not run the boot splash.



Similarly run with sudo permission to edit /etc/default/grub and modify the line that contains "quiet splash" and change that part to "quiet", then save the changes. Finally, run sudo update-grub to update the modified configuration.



...
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
...


When the boot splash is disabled, some boot message may be shown instead during the boot process. For some reason, the result is inconsistent when running Ubuntu MATE (sometimes showing many lines despite the same "quiet" option), which is otherwise not seen when running other Ubuntu derivative like Xubuntu.



The blanking




0:19 Change of Background
0:22~0:29 Login
0:30 Black with light <-- this
0:32 My wallpaper



The blanking that occurs between login and desktop, is most likely specific to GNOME or similar desktop environments like MATE. I have confirmed that: in comparison, Cinnamon does show blanking like MATE; in contrast, Xfce does not show such behaviour.



Initially, I thought the blanking may be due to transition of loading the compositing window manager; however, changing or disabling the compositor in MATE either way does not affect the blanking behaviour. So the actual problem is something else.



Workaround: For Ubuntu MATE, the login screen should use a true black colour (#000000).



Go to Control Center > Login Window - Appearance and empty the path for Background, and then change Background colour to black (select the darkest monochrome shade in the bottom-left area). Close the window to finish. The main purpose of this workaround is to minimize the blanking; user may also change the theme to improve contrast and login window visibility.



The result



With workarounds above, most end-users will see only the first blank during the boot process. Except, OP and affected users will need to solve the shine issue separately.




  • blank 1: Always shown (inevitable)

  • blank 2: Use workaround

  • shine: Separate solution (hardware-dependent)

  • blank 3: Use workaround

  • blanking: Use workaround (software-dependent)


Tested workarounds with Ubuntu MATE 18.04, running on 32-bit machine Intel Celeron 1.6 GHz with Intel graphics. Minimal installation has boot time of about 45 seconds (non-optimal), with no shine and only the first blank and blanking were seen.







share|improve this answer












share|improve this answer



share|improve this answer










answered Feb 10 at 11:53









clearkimuraclearkimura

4,23021957




4,23021957








  • 1





    When I remove the splash screen, I see even more flickering. But I admire the effort you put in the answer

    – Martin Thoma
    Feb 14 at 21:59














  • 1





    When I remove the splash screen, I see even more flickering. But I admire the effort you put in the answer

    – Martin Thoma
    Feb 14 at 21:59








1




1





When I remove the splash screen, I see even more flickering. But I admire the effort you put in the answer

– Martin Thoma
Feb 14 at 21:59





When I remove the splash screen, I see even more flickering. But I admire the effort you put in the answer

– Martin Thoma
Feb 14 at 21:59


















draft saved

draft discarded




















































Thanks for contributing an answer to Ask Ubuntu!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1036212%2fhow-can-i-have-less-flickering-when-booting%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

How to make a Squid Proxy server?

Is this a new Fibonacci Identity?

19世紀