Overcoming black text and blank screens between plymouth and gdm-login boot stagesHow to fix plymouth (splash screen) in all Ubuntu releases!How to change boot splash screen in 18.04Problem with GRUB resolution - Ubuntu 18.04When I boot up the computer normally, gdm won't workI want my grub2 background to be black but setting it to black is not enoughHow do I enable the GRUB splash screen in Xubuntu 12.10?Linux Plymouth splash screen works only recovery modeShow a consistent background image from grub2's boot to unity's login for Ubuntu 16.04.3 with Nvidia GPU18.04: Low Resolution In Grub and Splash After Installing Nvidia DriverHow to show boot text instead of the splash or blank screen on Ubuntu/Kubuntu 18.04?Kubuntu 18.04 LTS splash screen is blackRemoving/hiding all boot screensChange Background Color between Login and Wallpaper load animation Ubuntu 18.04
What are the differences in architecture of Model 2 and Model 3B+? (SD card not working in model 3B+)
Company looks for long-term employees, but I know I won't be interested in staying long
When designing an adventure, how can I ensure a continuous player experience in a setting that's likely to favor TPKs?
How can I help our ranger feel special about her beast companion?
How to delete all messages in the message window programmatically?
Did Hitler say this quote about homeschooling?
Three Subway Escalators
Should I have one hand on the throttle during engine ignition?
Which modern firearm should a time traveler bring to be easily reproducible for a historic civilization?
Available space differs between sys.database_files and database properties dialog in SQL Server Management Studio
Inscriptio Labyrinthica
How to interpret a promising preprint that was never published in peer-review?
Whipping heavy cream with melted chocolate
How was Luke's prosthetic hand in Episode V filmed?
Who determines when road center lines are solid or dashed?
How did J. J. Thomson establish the particle nature of the electron?
Importing data into PostgreSQL from remote text file using ftplib class
In this iconic lunar orbit rendezvous photo of John Houbolt, why do arrows #5 and #6 point the "wrong" way?
Why aren't there any women super GMs?
Left crank keeps coming loose
Last-minute canceled work-trip mean I'll lose thousands of dollars on planned vacation
Zhora asks Deckard: "Are you for real?" Was this meant to be significant?
Why does a tetrahedral molecule like methane have a dipole moment of zero?
Is this Android phone Android 9.0 or Android 6.0?
Overcoming black text and blank screens between plymouth and gdm-login boot stages
How to fix plymouth (splash screen) in all Ubuntu releases!How to change boot splash screen in 18.04Problem with GRUB resolution - Ubuntu 18.04When I boot up the computer normally, gdm won't workI want my grub2 background to be black but setting it to black is not enoughHow do I enable the GRUB splash screen in Xubuntu 12.10?Linux Plymouth splash screen works only recovery modeShow a consistent background image from grub2's boot to unity's login for Ubuntu 16.04.3 with Nvidia GPU18.04: Low Resolution In Grub and Splash After Installing Nvidia DriverHow to show boot text instead of the splash or blank screen on Ubuntu/Kubuntu 18.04?Kubuntu 18.04 LTS splash screen is blackRemoving/hiding all boot screensChange Background Color between Login and Wallpaper load animation Ubuntu 18.04
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
In Ubuntu 18.04.2, I would like to show a consistent background image from the start of Grub2 to the appearance of the GDM login screen.
I have customized the ubuntu-logo plymouth theme to show the background image that I would like. All the necessary procedures as described by @Jake were done, and tested. Even the test procedure described by @Jake were performed. However, the plymouth theme just does not appear. Between the Grub2 and GDM login stage, I still encounter 6-7 seconds of black screen each time the system boots up.
What can I do to discover the issue(s) for this black screen? How should I fix this missing splash screen issue.? The system uses NVidea driver version:418.56.
Remark: The system is able to boot up and login at the GDM login screen.
Update 1:
I introduced the following amendments to try to resolve my issue:
I added the following commands in the default Grub2 file
/etc/defaults/grub
:GRUB_GFXMODE=1920x1080x32
GRUB_GFXPAYLOAD_LINUX="keep"According to
GRUB_GFXPAYLOAD_LINUX
, the value"keep"
preserves the graphics mode set usingGRUB_GFXMODE
when the linux kernel is booted.The resolution of
1920x1080x32
was selected forGRUB_GFXMODE
because it was the highest resolution available in the video driver detected by Grub2, which was a EFI GOP driver.To get available resolutions detected by Grub2, at the Grub2 menu during the boot phase, I pressed the keyboard 'c' key. Then at grub> prompt, I entered the command
videoinfo
(see below Videoinfo); the commandvbeinfo
did not exist in Grub2.I created a splash file to set FRAMEBUFFER on with this terminal command:
echo FRAMEBUFFER=y | sudo tee /etc/initramfs-tools/conf.d/splash
As a splash image is involved, I performed the amendments described in the section on Configuration settings (splash image present) in this ubuntu wiki.
Ran terminal commands:
sudo update-initramfs -u
andsudo update-grub
reference
Videoinfo:
grub> videoinfo
List of supported video modes:
Legend: mask/position=red,green,blue,reserved
Adapter 'Bochs PCI Video Driver':
No info available
Adapter 'Cirruls CLGD 5446 PCI Video Driver':
No info available
Adapter 'EFI GOP Driver':
* 0x000 1920 x 1080 x 32 (7680) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
0x001 640 x 480 x 32 (2560) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
0x002 800 x 600 x 32 (3200) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
0x003 1024 x 768 x 32 (3200) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
0x004 1280 x 800 x 32 (5120) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
0x005 1280 x 1024 x 32 (5120) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
0x006 1440 x 900 x 32 (5760) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
0x007 1400 x 1050 x 32 (5600) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
0x008 1680 x 1050 x 32 (6720) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
EDID version: 1.3
Preferred mode: 1920x1080
grub>
Issue:
During my many reboots checks, the good news is that I am able now able to see the plymouth splash the I had implemented. However, the bad news is that the plymouth splash does not last all the way till the GDM login screen appears; the splash is still proceeded by first a black text screen(see below images on 1st reboot and subsequents reboots) and then followed by a complete black screen, before the GDM login screen appears. The appears for about 5 to 10 secs. Also, after I had made the amendments that I had described above, on the first reboot, the plymouth splash appeared the longest. On my 2nd and subsequent reboots, the appearance of the splash was shortened. Strange...
1st Reboot(left) and Subequent Reboots(right):
Question: How can I avoid/overcome these black text screen and black blank screen that appears between the plymouth-splash and gdm-login stages? Is there another stage in the boot sequeence to implement a background image that I have not attended to? Thus far, I only know of the the need to put a background image in the grub, plymouth and gdm stages, and I have perform these setups.
Update 2:
I like to share here my findings from using GRUB_GFXPAYLOAD_LINUX="keep"
and when I instructed Grub2 to process the linux kernel with these values: ro
, ro splash
, ro nomodeset
, ro quiet
, ro quiet splash
, ro quiet splash
, $vt_handoff
, and ro splash $vt_handoff
. For each case, I recorded the boot events from the moment after I had pressed F10 while at the Grubmenu->pressed-key-"e"-environment up till the appearance of the GDM-login screen, and I conducted the same video measurement thrice. Resolution of the reported timings is 1 second. The reported timings is constrained by Seagate's Firecuda internal 2.5" SATA3 HDD performance and would not apply to OS installed on a SSD.
A summary of my measurements are given here.
A chart of their cumulative timings is shown below. Note that when the curve between two events is horizontal, it means that the event on the left did not occur.
Key Findings:
Using$vt_handoff
allowed an uninterrupted display of the Grub background image from the Grub Menu stage to the Plymouth Splash stage.- The performance from using
ro splash $vt_handoff
andro quiet splash $vt_handoff
are similar, except that the former can be slightly faster (in my case it was 1 sec faster) than the latter. - The shortest boot duration of 20 sec was achieved using
ro
orro splash $vt_handoff
. The latter is most suited when a background image needs to be displayed.
Comments:
My setup presently is still plagued by 2 phenomenon.
- The appearance of a black blank screen, for 8 to 10 seconds, prior
to the appearance of the GDM-Login screen, and - A 1 sec appearance of the Boot Log immediately after the Plymouth Splash or just before the black blank screen mentioned earlier. It appeared even when the value
quiet
was used.
I suspect these two issues have something to do with the communication between the Nvidia driver and Grub, or timing issues when transitioning between various virtual screens. Can someone who is knowledgeable of these phenomenons advice me on how to overcome/investigate them? Thank you.
boot grub2 nvidia gdm plymouth
add a comment |
In Ubuntu 18.04.2, I would like to show a consistent background image from the start of Grub2 to the appearance of the GDM login screen.
I have customized the ubuntu-logo plymouth theme to show the background image that I would like. All the necessary procedures as described by @Jake were done, and tested. Even the test procedure described by @Jake were performed. However, the plymouth theme just does not appear. Between the Grub2 and GDM login stage, I still encounter 6-7 seconds of black screen each time the system boots up.
What can I do to discover the issue(s) for this black screen? How should I fix this missing splash screen issue.? The system uses NVidea driver version:418.56.
Remark: The system is able to boot up and login at the GDM login screen.
Update 1:
I introduced the following amendments to try to resolve my issue:
I added the following commands in the default Grub2 file
/etc/defaults/grub
:GRUB_GFXMODE=1920x1080x32
GRUB_GFXPAYLOAD_LINUX="keep"According to
GRUB_GFXPAYLOAD_LINUX
, the value"keep"
preserves the graphics mode set usingGRUB_GFXMODE
when the linux kernel is booted.The resolution of
1920x1080x32
was selected forGRUB_GFXMODE
because it was the highest resolution available in the video driver detected by Grub2, which was a EFI GOP driver.To get available resolutions detected by Grub2, at the Grub2 menu during the boot phase, I pressed the keyboard 'c' key. Then at grub> prompt, I entered the command
videoinfo
(see below Videoinfo); the commandvbeinfo
did not exist in Grub2.I created a splash file to set FRAMEBUFFER on with this terminal command:
echo FRAMEBUFFER=y | sudo tee /etc/initramfs-tools/conf.d/splash
As a splash image is involved, I performed the amendments described in the section on Configuration settings (splash image present) in this ubuntu wiki.
Ran terminal commands:
sudo update-initramfs -u
andsudo update-grub
reference
Videoinfo:
grub> videoinfo
List of supported video modes:
Legend: mask/position=red,green,blue,reserved
Adapter 'Bochs PCI Video Driver':
No info available
Adapter 'Cirruls CLGD 5446 PCI Video Driver':
No info available
Adapter 'EFI GOP Driver':
* 0x000 1920 x 1080 x 32 (7680) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
0x001 640 x 480 x 32 (2560) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
0x002 800 x 600 x 32 (3200) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
0x003 1024 x 768 x 32 (3200) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
0x004 1280 x 800 x 32 (5120) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
0x005 1280 x 1024 x 32 (5120) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
0x006 1440 x 900 x 32 (5760) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
0x007 1400 x 1050 x 32 (5600) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
0x008 1680 x 1050 x 32 (6720) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
EDID version: 1.3
Preferred mode: 1920x1080
grub>
Issue:
During my many reboots checks, the good news is that I am able now able to see the plymouth splash the I had implemented. However, the bad news is that the plymouth splash does not last all the way till the GDM login screen appears; the splash is still proceeded by first a black text screen(see below images on 1st reboot and subsequents reboots) and then followed by a complete black screen, before the GDM login screen appears. The appears for about 5 to 10 secs. Also, after I had made the amendments that I had described above, on the first reboot, the plymouth splash appeared the longest. On my 2nd and subsequent reboots, the appearance of the splash was shortened. Strange...
1st Reboot(left) and Subequent Reboots(right):
Question: How can I avoid/overcome these black text screen and black blank screen that appears between the plymouth-splash and gdm-login stages? Is there another stage in the boot sequeence to implement a background image that I have not attended to? Thus far, I only know of the the need to put a background image in the grub, plymouth and gdm stages, and I have perform these setups.
Update 2:
I like to share here my findings from using GRUB_GFXPAYLOAD_LINUX="keep"
and when I instructed Grub2 to process the linux kernel with these values: ro
, ro splash
, ro nomodeset
, ro quiet
, ro quiet splash
, ro quiet splash
, $vt_handoff
, and ro splash $vt_handoff
. For each case, I recorded the boot events from the moment after I had pressed F10 while at the Grubmenu->pressed-key-"e"-environment up till the appearance of the GDM-login screen, and I conducted the same video measurement thrice. Resolution of the reported timings is 1 second. The reported timings is constrained by Seagate's Firecuda internal 2.5" SATA3 HDD performance and would not apply to OS installed on a SSD.
A summary of my measurements are given here.
A chart of their cumulative timings is shown below. Note that when the curve between two events is horizontal, it means that the event on the left did not occur.
Key Findings:
Using$vt_handoff
allowed an uninterrupted display of the Grub background image from the Grub Menu stage to the Plymouth Splash stage.- The performance from using
ro splash $vt_handoff
andro quiet splash $vt_handoff
are similar, except that the former can be slightly faster (in my case it was 1 sec faster) than the latter. - The shortest boot duration of 20 sec was achieved using
ro
orro splash $vt_handoff
. The latter is most suited when a background image needs to be displayed.
Comments:
My setup presently is still plagued by 2 phenomenon.
- The appearance of a black blank screen, for 8 to 10 seconds, prior
to the appearance of the GDM-Login screen, and - A 1 sec appearance of the Boot Log immediately after the Plymouth Splash or just before the black blank screen mentioned earlier. It appeared even when the value
quiet
was used.
I suspect these two issues have something to do with the communication between the Nvidia driver and Grub, or timing issues when transitioning between various virtual screens. Can someone who is knowledgeable of these phenomenons advice me on how to overcome/investigate them? Thank you.
boot grub2 nvidia gdm plymouth
add a comment |
In Ubuntu 18.04.2, I would like to show a consistent background image from the start of Grub2 to the appearance of the GDM login screen.
I have customized the ubuntu-logo plymouth theme to show the background image that I would like. All the necessary procedures as described by @Jake were done, and tested. Even the test procedure described by @Jake were performed. However, the plymouth theme just does not appear. Between the Grub2 and GDM login stage, I still encounter 6-7 seconds of black screen each time the system boots up.
What can I do to discover the issue(s) for this black screen? How should I fix this missing splash screen issue.? The system uses NVidea driver version:418.56.
Remark: The system is able to boot up and login at the GDM login screen.
Update 1:
I introduced the following amendments to try to resolve my issue:
I added the following commands in the default Grub2 file
/etc/defaults/grub
:GRUB_GFXMODE=1920x1080x32
GRUB_GFXPAYLOAD_LINUX="keep"According to
GRUB_GFXPAYLOAD_LINUX
, the value"keep"
preserves the graphics mode set usingGRUB_GFXMODE
when the linux kernel is booted.The resolution of
1920x1080x32
was selected forGRUB_GFXMODE
because it was the highest resolution available in the video driver detected by Grub2, which was a EFI GOP driver.To get available resolutions detected by Grub2, at the Grub2 menu during the boot phase, I pressed the keyboard 'c' key. Then at grub> prompt, I entered the command
videoinfo
(see below Videoinfo); the commandvbeinfo
did not exist in Grub2.I created a splash file to set FRAMEBUFFER on with this terminal command:
echo FRAMEBUFFER=y | sudo tee /etc/initramfs-tools/conf.d/splash
As a splash image is involved, I performed the amendments described in the section on Configuration settings (splash image present) in this ubuntu wiki.
Ran terminal commands:
sudo update-initramfs -u
andsudo update-grub
reference
Videoinfo:
grub> videoinfo
List of supported video modes:
Legend: mask/position=red,green,blue,reserved
Adapter 'Bochs PCI Video Driver':
No info available
Adapter 'Cirruls CLGD 5446 PCI Video Driver':
No info available
Adapter 'EFI GOP Driver':
* 0x000 1920 x 1080 x 32 (7680) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
0x001 640 x 480 x 32 (2560) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
0x002 800 x 600 x 32 (3200) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
0x003 1024 x 768 x 32 (3200) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
0x004 1280 x 800 x 32 (5120) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
0x005 1280 x 1024 x 32 (5120) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
0x006 1440 x 900 x 32 (5760) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
0x007 1400 x 1050 x 32 (5600) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
0x008 1680 x 1050 x 32 (6720) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
EDID version: 1.3
Preferred mode: 1920x1080
grub>
Issue:
During my many reboots checks, the good news is that I am able now able to see the plymouth splash the I had implemented. However, the bad news is that the plymouth splash does not last all the way till the GDM login screen appears; the splash is still proceeded by first a black text screen(see below images on 1st reboot and subsequents reboots) and then followed by a complete black screen, before the GDM login screen appears. The appears for about 5 to 10 secs. Also, after I had made the amendments that I had described above, on the first reboot, the plymouth splash appeared the longest. On my 2nd and subsequent reboots, the appearance of the splash was shortened. Strange...
1st Reboot(left) and Subequent Reboots(right):
Question: How can I avoid/overcome these black text screen and black blank screen that appears between the plymouth-splash and gdm-login stages? Is there another stage in the boot sequeence to implement a background image that I have not attended to? Thus far, I only know of the the need to put a background image in the grub, plymouth and gdm stages, and I have perform these setups.
Update 2:
I like to share here my findings from using GRUB_GFXPAYLOAD_LINUX="keep"
and when I instructed Grub2 to process the linux kernel with these values: ro
, ro splash
, ro nomodeset
, ro quiet
, ro quiet splash
, ro quiet splash
, $vt_handoff
, and ro splash $vt_handoff
. For each case, I recorded the boot events from the moment after I had pressed F10 while at the Grubmenu->pressed-key-"e"-environment up till the appearance of the GDM-login screen, and I conducted the same video measurement thrice. Resolution of the reported timings is 1 second. The reported timings is constrained by Seagate's Firecuda internal 2.5" SATA3 HDD performance and would not apply to OS installed on a SSD.
A summary of my measurements are given here.
A chart of their cumulative timings is shown below. Note that when the curve between two events is horizontal, it means that the event on the left did not occur.
Key Findings:
Using$vt_handoff
allowed an uninterrupted display of the Grub background image from the Grub Menu stage to the Plymouth Splash stage.- The performance from using
ro splash $vt_handoff
andro quiet splash $vt_handoff
are similar, except that the former can be slightly faster (in my case it was 1 sec faster) than the latter. - The shortest boot duration of 20 sec was achieved using
ro
orro splash $vt_handoff
. The latter is most suited when a background image needs to be displayed.
Comments:
My setup presently is still plagued by 2 phenomenon.
- The appearance of a black blank screen, for 8 to 10 seconds, prior
to the appearance of the GDM-Login screen, and - A 1 sec appearance of the Boot Log immediately after the Plymouth Splash or just before the black blank screen mentioned earlier. It appeared even when the value
quiet
was used.
I suspect these two issues have something to do with the communication between the Nvidia driver and Grub, or timing issues when transitioning between various virtual screens. Can someone who is knowledgeable of these phenomenons advice me on how to overcome/investigate them? Thank you.
boot grub2 nvidia gdm plymouth
In Ubuntu 18.04.2, I would like to show a consistent background image from the start of Grub2 to the appearance of the GDM login screen.
I have customized the ubuntu-logo plymouth theme to show the background image that I would like. All the necessary procedures as described by @Jake were done, and tested. Even the test procedure described by @Jake were performed. However, the plymouth theme just does not appear. Between the Grub2 and GDM login stage, I still encounter 6-7 seconds of black screen each time the system boots up.
What can I do to discover the issue(s) for this black screen? How should I fix this missing splash screen issue.? The system uses NVidea driver version:418.56.
Remark: The system is able to boot up and login at the GDM login screen.
Update 1:
I introduced the following amendments to try to resolve my issue:
I added the following commands in the default Grub2 file
/etc/defaults/grub
:GRUB_GFXMODE=1920x1080x32
GRUB_GFXPAYLOAD_LINUX="keep"According to
GRUB_GFXPAYLOAD_LINUX
, the value"keep"
preserves the graphics mode set usingGRUB_GFXMODE
when the linux kernel is booted.The resolution of
1920x1080x32
was selected forGRUB_GFXMODE
because it was the highest resolution available in the video driver detected by Grub2, which was a EFI GOP driver.To get available resolutions detected by Grub2, at the Grub2 menu during the boot phase, I pressed the keyboard 'c' key. Then at grub> prompt, I entered the command
videoinfo
(see below Videoinfo); the commandvbeinfo
did not exist in Grub2.I created a splash file to set FRAMEBUFFER on with this terminal command:
echo FRAMEBUFFER=y | sudo tee /etc/initramfs-tools/conf.d/splash
As a splash image is involved, I performed the amendments described in the section on Configuration settings (splash image present) in this ubuntu wiki.
Ran terminal commands:
sudo update-initramfs -u
andsudo update-grub
reference
Videoinfo:
grub> videoinfo
List of supported video modes:
Legend: mask/position=red,green,blue,reserved
Adapter 'Bochs PCI Video Driver':
No info available
Adapter 'Cirruls CLGD 5446 PCI Video Driver':
No info available
Adapter 'EFI GOP Driver':
* 0x000 1920 x 1080 x 32 (7680) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
0x001 640 x 480 x 32 (2560) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
0x002 800 x 600 x 32 (3200) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
0x003 1024 x 768 x 32 (3200) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
0x004 1280 x 800 x 32 (5120) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
0x005 1280 x 1024 x 32 (5120) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
0x006 1440 x 900 x 32 (5760) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
0x007 1400 x 1050 x 32 (5600) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
0x008 1680 x 1050 x 32 (6720) Direct color, mask: 8/8/8/8 pos: 16/8/0/24
EDID version: 1.3
Preferred mode: 1920x1080
grub>
Issue:
During my many reboots checks, the good news is that I am able now able to see the plymouth splash the I had implemented. However, the bad news is that the plymouth splash does not last all the way till the GDM login screen appears; the splash is still proceeded by first a black text screen(see below images on 1st reboot and subsequents reboots) and then followed by a complete black screen, before the GDM login screen appears. The appears for about 5 to 10 secs. Also, after I had made the amendments that I had described above, on the first reboot, the plymouth splash appeared the longest. On my 2nd and subsequent reboots, the appearance of the splash was shortened. Strange...
1st Reboot(left) and Subequent Reboots(right):
Question: How can I avoid/overcome these black text screen and black blank screen that appears between the plymouth-splash and gdm-login stages? Is there another stage in the boot sequeence to implement a background image that I have not attended to? Thus far, I only know of the the need to put a background image in the grub, plymouth and gdm stages, and I have perform these setups.
Update 2:
I like to share here my findings from using GRUB_GFXPAYLOAD_LINUX="keep"
and when I instructed Grub2 to process the linux kernel with these values: ro
, ro splash
, ro nomodeset
, ro quiet
, ro quiet splash
, ro quiet splash
, $vt_handoff
, and ro splash $vt_handoff
. For each case, I recorded the boot events from the moment after I had pressed F10 while at the Grubmenu->pressed-key-"e"-environment up till the appearance of the GDM-login screen, and I conducted the same video measurement thrice. Resolution of the reported timings is 1 second. The reported timings is constrained by Seagate's Firecuda internal 2.5" SATA3 HDD performance and would not apply to OS installed on a SSD.
A summary of my measurements are given here.
A chart of their cumulative timings is shown below. Note that when the curve between two events is horizontal, it means that the event on the left did not occur.
Key Findings:
Using$vt_handoff
allowed an uninterrupted display of the Grub background image from the Grub Menu stage to the Plymouth Splash stage.- The performance from using
ro splash $vt_handoff
andro quiet splash $vt_handoff
are similar, except that the former can be slightly faster (in my case it was 1 sec faster) than the latter. - The shortest boot duration of 20 sec was achieved using
ro
orro splash $vt_handoff
. The latter is most suited when a background image needs to be displayed.
Comments:
My setup presently is still plagued by 2 phenomenon.
- The appearance of a black blank screen, for 8 to 10 seconds, prior
to the appearance of the GDM-Login screen, and - A 1 sec appearance of the Boot Log immediately after the Plymouth Splash or just before the black blank screen mentioned earlier. It appeared even when the value
quiet
was used.
I suspect these two issues have something to do with the communication between the Nvidia driver and Grub, or timing issues when transitioning between various virtual screens. Can someone who is knowledgeable of these phenomenons advice me on how to overcome/investigate them? Thank you.
boot grub2 nvidia gdm plymouth
boot grub2 nvidia gdm plymouth
edited Apr 16 at 17:05
Sun Bear
asked Apr 13 at 18:59
Sun BearSun Bear
3333 silver badges18 bronze badges
3333 silver badges18 bronze badges
add a comment |
add a comment |
0
active
oldest
votes
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
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1133622%2fovercoming-black-text-and-blank-screens-between-plymouth-and-gdm-login-boot-stag%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1133622%2fovercoming-black-text-and-blank-screens-between-plymouth-and-gdm-login-boot-stag%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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