[opensuse-factory] How do I suppress the flashing cursor before plymouth starts up
Hi all, Does anyone know how to suppress the annoying flashing cursor at the top-left corner of the screen - just before plymouth starts up? I would like to submit a bug report. Is this systemd? Cheers! Roman IRC: 551368250 ============== -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Saturday 2016-06-25 23:16, Roman Bysh wrote:
Does anyone know how to suppress the annoying flashing cursor at the top-left corner of the screen - just before plymouth starts up?
I would like to submit a bug report. Is this systemd?
One can come up with ample opportunities where splash flickering _could_ occur. * bootloader switching back from graphics mode to text after loading, but before running, the kernel. * when switching drivers at runtime (X11 usermode switching; kernel driver switch e.g. vesafb->someother.) * kernel and firmware having a different idea of what to show. If the firmware just clones the boot console to all attached monitors, when the kernel loads its own driver, it may default to no cloning. Or vice-versa: boot console is just shown on one monitor, and loading the kernel graphic driver will clone. * hardware initiating a screen content reset on switching display parameters (like frequency, outputs) even if resolution stays the same * firmware messing with the graphics buffer between bootloader and kernel running even if loader and kernel themselves are in harmony. (VMware Workstation exhibited this visibly by showing red/green striped lines when booting the SUSE CD when I last used VMW some 10 years ago) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 06/26/2016 04:00 AM, Jan Engelhardt wrote:
On Saturday 2016-06-25 23:16, Roman Bysh wrote:
Does anyone know how to suppress the annoying flashing cursor at the top-left corner of the screen - just before plymouth starts up?
I would like to submit a bug report. Is this systemd?
One can come up with ample opportunities where splash flickering _could_ occur.
* bootloader switching back from graphics mode to text after loading, but before running, the kernel.
* when switching drivers at runtime (X11 usermode switching; kernel driver switch e.g. vesafb->someother.)
* kernel and firmware having a different idea of what to show. If the firmware just clones the boot console to all attached monitors, when the kernel loads its own driver, it may default to no cloning. Or vice-versa: boot console is just shown on one monitor, and loading the kernel graphic driver will clone.
* hardware initiating a screen content reset on switching display parameters (like frequency, outputs) even if resolution stays the same
* firmware messing with the graphics buffer between bootloader and kernel running even if loader and kernel themselves are in harmony. (VMware Workstation exhibited this visibly by showing red/green striped lines when booting the SUSE CD when I last used VMW some 10 years ago)
Hhm.. Where to start. It begins flashing at a steady rate after you press the <enter> key at the Grub2 menu selection and it starts flashing faster just before the plymouth splash appears.
26.06.2016 21:04, Roman Bysh пишет:
On 06/26/2016 04:00 AM, Jan Engelhardt wrote:
On Saturday 2016-06-25 23:16, Roman Bysh wrote:
Does anyone know how to suppress the annoying flashing cursor at the top-left corner of the screen - just before plymouth starts up?
I would like to submit a bug report. Is this systemd?
One can come up with ample opportunities where splash flickering _could_ occur.
* bootloader switching back from graphics mode to text after loading, but before running, the kernel.
* when switching drivers at runtime (X11 usermode switching; kernel driver switch e.g. vesafb->someother.)
* kernel and firmware having a different idea of what to show. If the firmware just clones the boot console to all attached monitors, when the kernel loads its own driver, it may default to no cloning. Or vice-versa: boot console is just shown on one monitor, and loading the kernel graphic driver will clone.
* hardware initiating a screen content reset on switching display parameters (like frequency, outputs) even if resolution stays the same
* firmware messing with the graphics buffer between bootloader and kernel running even if loader and kernel themselves are in harmony. (VMware Workstation exhibited this visibly by showing red/green striped lines when booting the SUSE CD when I last used VMW some 10 years ago)
Hhm.. Where to start.
It begins flashing at a steady rate after you press the <enter> key at the Grub2 menu selection
It sounds like standard PC console cursor. You do not say whether you are using graphical or text menu.
and it starts flashing faster just before the plymouth splash appears.
On Mon, 27 Jun 2016 05:49:21 +0200, Andrei Borzenkov wrote:
26.06.2016 21:04, Roman Bysh пишет:
On 06/26/2016 04:00 AM, Jan Engelhardt wrote:
On Saturday 2016-06-25 23:16, Roman Bysh wrote:
Does anyone know how to suppress the annoying flashing cursor at the top-left corner of the screen - just before plymouth starts up?
I would like to submit a bug report. Is this systemd?
One can come up with ample opportunities where splash flickering _could_ occur.
* bootloader switching back from graphics mode to text after loading, but before running, the kernel.
* when switching drivers at runtime (X11 usermode switching; kernel driver switch e.g. vesafb->someother.)
* kernel and firmware having a different idea of what to show. If the firmware just clones the boot console to all attached monitors, when the kernel loads its own driver, it may default to no cloning. Or vice-versa: boot console is just shown on one monitor, and loading the kernel graphic driver will clone.
* hardware initiating a screen content reset on switching display parameters (like frequency, outputs) even if resolution stays the same
* firmware messing with the graphics buffer between bootloader and kernel running even if loader and kernel themselves are in harmony. (VMware Workstation exhibited this visibly by showing red/green striped lines when booting the SUSE CD when I last used VMW some 10 years ago)
Hhm.. Where to start.
It begins flashing at a steady rate after you press the <enter> key at the Grub2 menu selection
It sounds like standard PC console cursor. You do not say whether you are using graphical or text menu.
and it starts flashing faster just before the plymouth splash appears.
If the cursor in question is the standard cursor on Linux console, it can be suppressed by vt.cur_default=1 boot option. But this will keep the default cursor style as none as well, so you'll likely need to restore the original default (= 2, the underline) somehow during the boot, either by doing echo or changing /sys/module/vt/parameters/cur_default. Takashi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 06/27/2016 07:53 AM, Takashi Iwai wrote:
On Mon, 27 Jun 2016 05:49:21 +0200, Andrei Borzenkov wrote:
26.06.2016 21:04, Roman Bysh пишет:
On 06/26/2016 04:00 AM, Jan Engelhardt wrote:
On Saturday 2016-06-25 23:16, Roman Bysh wrote:
Does anyone know how to suppress the annoying flashing cursor at the top-left corner of the screen - just before plymouth starts up?
I would like to submit a bug report. Is this systemd?
One can come up with ample opportunities where splash flickering _could_ occur.
* bootloader switching back from graphics mode to text after loading, but before running, the kernel.
* when switching drivers at runtime (X11 usermode switching; kernel driver switch e.g. vesafb->someother.)
* kernel and firmware having a different idea of what to show. If the firmware just clones the boot console to all attached monitors, when the kernel loads its own driver, it may default to no cloning. Or vice-versa: boot console is just shown on one monitor, and loading the kernel graphic driver will clone.
* hardware initiating a screen content reset on switching display parameters (like frequency, outputs) even if resolution stays the same
* firmware messing with the graphics buffer between bootloader and kernel running even if loader and kernel themselves are in harmony. (VMware Workstation exhibited this visibly by showing red/green striped lines when booting the SUSE CD when I last used VMW some 10 years ago)
Hhm.. Where to start.
It begins flashing at a steady rate after you press the <enter> key at the Grub2 menu selection
It sounds like standard PC console cursor. You do not say whether you are using graphical or text menu.
and it starts flashing faster just before the plymouth splash appears.
If the cursor in question is the standard cursor on Linux console, it can be suppressed by vt.cur_default=1 boot option.
But this will keep the default cursor style as none as well, so you'll likely need to restore the original default (= 2, the underline) somehow during the boot, either by doing echo or changing /sys/module/vt/parameters/cur_default.
Takashi
The strange thing is that this problem did not exist four or five builds ago from the present build 625. And it certainly doesn't exist in openSUSE 13.2. Not sure about Leap. Roman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
28.06.2016 21:01, Roman Bysh пишет:
On 06/27/2016 07:53 AM, Takashi Iwai wrote:
On Mon, 27 Jun 2016 05:49:21 +0200, Andrei Borzenkov wrote:
26.06.2016 21:04, Roman Bysh пишет:
On 06/26/2016 04:00 AM, Jan Engelhardt wrote:
On Saturday 2016-06-25 23:16, Roman Bysh wrote:
Does anyone know how to suppress the annoying flashing cursor at the top-left corner of the screen - just before plymouth starts up?
I would like to submit a bug report. Is this systemd?
One can come up with ample opportunities where splash flickering _could_ occur.
* bootloader switching back from graphics mode to text after loading, but before running, the kernel.
* when switching drivers at runtime (X11 usermode switching; kernel driver switch e.g. vesafb->someother.)
* kernel and firmware having a different idea of what to show. If the firmware just clones the boot console to all attached monitors, when the kernel loads its own driver, it may default to no cloning. Or vice-versa: boot console is just shown on one monitor, and loading the kernel graphic driver will clone.
* hardware initiating a screen content reset on switching display parameters (like frequency, outputs) even if resolution stays the same
* firmware messing with the graphics buffer between bootloader and kernel running even if loader and kernel themselves are in harmony. (VMware Workstation exhibited this visibly by showing red/green striped lines when booting the SUSE CD when I last used VMW some 10 years ago)
Hhm.. Where to start.
It begins flashing at a steady rate after you press the <enter> key at the Grub2 menu selection
It sounds like standard PC console cursor. You do not say whether you are using graphical or text menu.
and it starts flashing faster just before the plymouth splash appears.
If the cursor in question is the standard cursor on Linux console, it can be suppressed by vt.cur_default=1 boot option.
But this will keep the default cursor style as none as well, so you'll likely need to restore the original default (= 2, the underline) somehow during the boot, either by doing echo or changing /sys/module/vt/parameters/cur_default.
Takashi
The strange thing is that this problem did not exist four or five builds ago from the present build 625.
And it certainly doesn't exist in openSUSE 13.2. Not sure about Leap.
I tried Leap (it is in QEMU, so should be taken with grain of salt) and I see the following: after I press ENTER in GRUB menu first GRUB command line window on top of usual green background appears; this window does have flashing cursor. After GRUB has finished loading of kernel and initrd screen is completely cleared and I do not see splashing cursor until plymouth splash is shown. With TW in QEMU I first see GRUB command line window; then screen is cleared and I see flashing cursor. But I do not even see plymouth splash (neither graphical nor text) although I plymouth is included in dracut. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 06/26/2016 11:49 PM, Andrei Borzenkov wrote:
26.06.2016 21:04, Roman Bysh пишет:
On 06/26/2016 04:00 AM, Jan Engelhardt wrote:
On Saturday 2016-06-25 23:16, Roman Bysh wrote:
Does anyone know how to suppress the annoying flashing cursor at the top-left corner of the screen - just before plymouth starts up?
I would like to submit a bug report. Is this systemd?
One can come up with ample opportunities where splash flickering _could_ occur.
* bootloader switching back from graphics mode to text after loading, but before running, the kernel.
* when switching drivers at runtime (X11 usermode switching; kernel driver switch e.g. vesafb->someother.)
* kernel and firmware having a different idea of what to show. If the firmware just clones the boot console to all attached monitors, when the kernel loads its own driver, it may default to no cloning. Or vice-versa: boot console is just shown on one monitor, and loading the kernel graphic driver will clone.
* hardware initiating a screen content reset on switching display parameters (like frequency, outputs) even if resolution stays the same
* firmware messing with the graphics buffer between bootloader and kernel running even if loader and kernel themselves are in harmony. (VMware Workstation exhibited this visibly by showing red/green striped lines when booting the SUSE CD when I last used VMW some 10 years ago)
Hhm.. Where to start.
It begins flashing at a steady rate after you press the <enter> key at the Grub2 menu selection
It sounds like standard PC console cursor. You do not say whether you are using graphical or text menu.
and it starts flashing faster just before the plymouth splash appears.
I am using the default Grub2 gui. First, let me find your link with the patched grub2 file and I'll be back.
On 06/27/2016 03:32 PM, Roman Bysh wrote:
On 06/26/2016 11:49 PM, Andrei Borzenkov wrote:
26.06.2016 21:04, Roman Bysh пишет:
On 06/26/2016 04:00 AM, Jan Engelhardt wrote:
On Saturday 2016-06-25 23:16, Roman Bysh wrote:
Does anyone know how to suppress the annoying flashing cursor at the top-left corner of the screen - just before plymouth starts up?
I would like to submit a bug report. Is this systemd?
One can come up with ample opportunities where splash flickering _could_ occur.
* bootloader switching back from graphics mode to text after loading, but before running, the kernel.
* when switching drivers at runtime (X11 usermode switching; kernel driver switch e.g. vesafb->someother.)
* kernel and firmware having a different idea of what to show. If the firmware just clones the boot console to all attached monitors, when the kernel loads its own driver, it may default to no cloning. Or vice-versa: boot console is just shown on one monitor, and loading the kernel graphic driver will clone.
* hardware initiating a screen content reset on switching display parameters (like frequency, outputs) even if resolution stays the same
* firmware messing with the graphics buffer between bootloader and kernel running even if loader and kernel themselves are in harmony. (VMware Workstation exhibited this visibly by showing red/green striped lines when booting the SUSE CD when I last used VMW some 10 years ago)
Hhm.. Where to start.
It begins flashing at a steady rate after you press the <enter> key at the Grub2 menu selection
It sounds like standard PC console cursor. You do not say whether you are using graphical or text menu.
and it starts flashing faster just before the plymouth splash appears.
I am using the default Grub2 gui. First, let me find your link with the patched grub2 file and I'll be back.
I wonder how we were able to do this in openSUSE 13.2? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thursday 2016-06-30 21:23, Roman Bysh wrote:
Does anyone know how to suppress the annoying flashing cursor at the top-left corner of the screen - just before plymouth starts up?
One can come up with ample opportunities where splash flickering _could_ occur. [List of 4 or 5 pitfalls]
I wonder how we were able to do this in openSUSE 13.2?
So do I. I expect that flicker-free booting was limited to a few platforms where it so happened that all 4, 5 problems do not occur. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2016-06-26 22:39, Roman Bysh wrote:
On 06/26/2016 04:17 AM, Carlos E. R. wrote:
On 2016-06-25 23:16, Roman Bysh wrote:
Is this systemd?
No.
Is there a way of debugging this?
With systemd, certainly not. It has not started yet. It looks a grub thing to me. I wouldn't know where exactly, because I disable plymouth in order to get a boot full of text in all its glory. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 06/27/2016 06:02 AM, Carlos E. R. wrote:
On 2016-06-26 22:39, Roman Bysh wrote:
On 06/26/2016 04:17 AM, Carlos E. R. wrote:
On 2016-06-25 23:16, Roman Bysh wrote:
Is this systemd?
No.
Is there a way of debugging this?
With systemd, certainly not. It has not started yet.
It looks a grub thing to me. I wouldn't know where exactly, because I disable plymouth in order to get a boot full of text in all its glory.
What if Plymouth started earlier with a black.png file that filled the screen preventing the flashing cursor from appearing followed by an animated Tumbleweed logo? Perhaps this is why we don't see a flashing cursor in openSUSE 13.2. Plymouth starts with a screen slowly fading up. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 07/01/2016 02:03 PM, Roman Bysh wrote:
On 06/27/2016 06:02 AM, Carlos E. R. wrote:
On 2016-06-26 22:39, Roman Bysh wrote:
On 06/26/2016 04:17 AM, Carlos E. R. wrote:
On 2016-06-25 23:16, Roman Bysh wrote:
Is this systemd?
No.
Is there a way of debugging this?
With systemd, certainly not. It has not started yet.
It looks a grub thing to me. I wouldn't know where exactly, because I disable plymouth in order to get a boot full of text in all its glory.
What if Plymouth started earlier with a black.png file that filled the screen preventing the flashing cursor from appearing followed by an animated Tumbleweed logo?
Perhaps this is why we don't see a flashing cursor in openSUSE 13.2. Plymouth starts with a screen slowly fading up.
See: https://cgit.freedesktop.org/plymouth/commit/?h=fix-text-spew On the Fedora website they comment about starting Plymouth before mounting / I guess this keeps the text and cursor from being shown. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Freitag, 1. Juli 2016, 14:03:29 schrieb Roman Bysh:
What if Plymouth started earlier with a black.png file that filled the screen preventing the flashing cursor from appearing followed by an animated Tumbleweed logo?
plymouth normally is started in the initrd already, much earlier isn't really possible... ;-) If it isn't for you, maybe check that you have plymouth-dracut installed. And maybe check that it is actually part of the initrd. (via lsinitrd e.g.)
Perhaps this is why we don't see a flashing cursor in openSUSE 13.2. Plymouth starts with a screen slowly fading up.
How would that make a difference? plymouth is starting up with a black screen on openSUSE 13.2 and slowly fading it in, it starts up with a not-black screen in Tumbleweed. As soon as it starts, it is displaying something, be it black or not black... Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 07/04/2016 09:03 AM, Wolfgang Bauer wrote:
Am Freitag, 1. Juli 2016, 14:03:29 schrieb Roman Bysh:
What if Plymouth started earlier with a black.png file that filled the screen preventing the flashing cursor from appearing followed by an animated Tumbleweed logo?
plymouth normally is started in the initrd already, much earlier isn't really possible... ;-)
If it isn't for you, maybe check that you have plymouth-dracut installed. And maybe check that it is actually part of the initrd. (via lsinitrd e.g.)
Perhaps this is why we don't see a flashing cursor in openSUSE 13.2. Plymouth starts with a screen slowly fading up.
How would that make a difference?
plymouth is starting up with a black screen on openSUSE 13.2 and slowly fading it in, it starts up with a not-black screen in Tumbleweed.
As soon as it starts, it is displaying something, be it black or not black...
Kind Regards, Wolfgang
But why do we need this? Don't you want slick clean boot up. If I want a flashing cursor block then I would set in up in the kernel option. When splash is enabled, the command doesn't say splash + text in kernel options. It's the annoying white flashing block AND the login prompt that appears just before and after plymouth. It also appears when we select shutdown from KDE gui. I'm not sure about GNOME. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Dienstag, 5. Juli 2016, 17:38:20 schrieb Roman Bysh:
But why do we need this?
Need what? As I wrote, plymouth should normally be started early enough, and it is not really possible to start it earlier. My point was that it does not make a difference whether plymouth displays a black screen or an actual picture.
Don't you want slick clean boot up.
Well, I don't see a flashing cursor after the boot menu that you mention. But then I'm still on 13.2. TBH, I don't really care though. I normally boot/shutdown my system once a day, and even then I'm normally not sitting in front of the screen and staring at the boot splash while it boots/shuts down...
It's the annoying white flashing block AND the login prompt that appears just before and after plymouth. It also appears when we select shutdown from KDE gui. I'm not sure about GNOME.
That's a different problem, and is caused by the fact that plymouth is quit before the display manager starts, to free up the console. And when you shut down, plymouth has to be restarted again after the display manager quits, so you see the text mode console for a short while. AIUI, gdm has a better plymouth integration than kdm or sddm, so you might try this one if that bothers you. Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 07/06/2016 04:58 AM, Wolfgang Bauer wrote:
Am Dienstag, 5. Juli 2016, 17:38:20 schrieb Roman Bysh:
But why do we need this?
Need what?
As I wrote, plymouth should normally be started early enough, and it is not really possible to start it earlier.
My point was that it does not make a difference whether plymouth displays a black screen or an actual picture.
Don't you want slick clean boot up.
Well, I don't see a flashing cursor after the boot menu that you mention. But then I'm still on 13.2.
TBH, I don't really care though. I normally boot/shutdown my system once a day, and even then I'm normally not sitting in front of the screen and staring at the boot splash while it boots/shuts down...
It's the annoying white flashing block AND the login prompt that appears just before and after plymouth. It also appears when we select shutdown from KDE gui. I'm not sure about GNOME.
That's a different problem, and is caused by the fact that plymouth is quit before the display manager starts, to free up the console. And when you shut down, plymouth has to be restarted again after the display manager quits, so you see the text mode console for a short while.
AIUI, gdm has a better plymouth integration than kdm or sddm, so you might try this one if that bothers you.
Kind Regards, Wolfgang
The issue about the log in prompt. Which selection should I choose for Bugzilla to report this bug? Plymouth? I'm also using openSUSE 13.2 as my main workstation as it has the most stable version of KDE4 where everything is working. The boot up is smooth. I will follow your advice and see about switching sddm to gdm. Cheers! Roman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (6)
-
Andrei Borzenkov -
Carlos E. R. -
Jan Engelhardt -
Roman Bysh -
Takashi Iwai -
Wolfgang Bauer