[opensuse-factory] Graphical Plymouth Themes not working in Tumbleweed, Text Mode Themes works fine
Hi All,
Not sure whether this is this is the correct place to discuss this. I am currently on the latest tumbleweed snapshot (20150330) with kernel 3.19.3-1-desktop X86_64 and Gnome 3.16. Since Last few updates, Plymouth themes that display some graphics or animation like the default openSUSE theme etc do not work. Instead the text theme with 3 question marks at the center of screen kicks in.
If I set it to some text based theme like tribar, details etc, it works fine. From the look of the display, it seems there is some problem with Plymouth while switching to the graphical mode. BTW, I am using it on a Thinkpad X240 with Haswell Core i7 4600U, 8 GB RAM and Intel HD4400 graphics.
Can anybody guide me how to resolve this? I am new to openSUSE but I have been a Linux user since 8-9 years, mostly Fedora and little bit of Debian experience as well.
Thanks.
В Fri, 03 Apr 2015 17:12:09 +0530 Sumit Bhardwaj sumitkbhardwaj@gmail.com пишет:
Hi All,
Not sure whether this is this is the correct place to discuss this. I am currently on the latest tumbleweed snapshot (20150330) with kernel 3.19.3-1-desktop X86_64 and Gnome 3.16. Since Last few updates, Plymouth themes that display some graphics or animation like the default openSUSE theme etc do not work. Instead the text theme with 3 question marks at the center of screen kicks in.
If I set it to some text based theme like tribar, details etc, it works fine. From the look of the display, it seems there is some problem with Plymouth while switching to the graphical mode. BTW, I am using it on a Thinkpad X240 with Haswell Core i7 4600U, 8 GB RAM and Intel HD4400 graphics.
Can anybody guide me how to resolve this? I am new to openSUSE but I have been a Linux user since 8-9 years, mostly Fedora and little bit of Debian experience as well.
Thanks.
This is likely the same problem as discussed recently on systemd list. Plymouth needs graphic driver loaded and fully initialized to display graphic theme. It does use (indirectly) udevadm settle but it now exits immediately if queue is empty. Which means plymouth can be started too early.
See https://www.mail-archive.com/systemd-devel@lists.freedesktop.org/msg28739.ht... for details.
On 04/03/2015 12:04 PM, Andrei Borzenkov wrote:
В Fri, 03 Apr 2015 17:12:09 +0530 Sumit Bhardwaj sumitkbhardwaj@gmail.com пишет:
Hi All,
Not sure whether this is this is the correct place to discuss this. I am currently on the latest tumbleweed snapshot (20150330) with kernel 3.19.3-1-desktop X86_64 and Gnome 3.16. Since Last few updates, Plymouth themes that display some graphics or animation like the default openSUSE theme etc do not work. Instead the text theme with 3 question marks at the center of screen kicks in.
If I set it to some text based theme like tribar, details etc, it works fine. From the look of the display, it seems there is some problem with Plymouth while switching to the graphical mode. BTW, I am using it on a Thinkpad X240 with Haswell Core i7 4600U, 8 GB RAM and Intel HD4400 graphics.
Can anybody guide me how to resolve this? I am new to openSUSE but I have been a Linux user since 8-9 years, mostly Fedora and little bit of Debian experience as well.
Thanks.
This is likely the same problem as discussed recently on systemd list. Plymouth needs graphic driver loaded and fully initialized to display graphic theme. It does use (indirectly) udevadm settle but it now exits immediately if queue is empty. Which means plymouth can be started too early.
I had this same problem, cleared it up by using YaST-->Boot Loader to recreate all of the boot stuff and splash now plymonth now works as expected. Oh, I had a boot problem after one of the upgrades that forced me to recreate the boot loader stuff, next boot plymonth worked as designed.
Ok Got your point, so basically it will be resolved once the Plymouth developers find out the correct way to detect loading of drm devices at boot time, right?
Regards, Sumit Bhardwaj
On Saturday 04 April 2015 05:37 PM, Ken Schneider - openSUSE wrote:
On 04/03/2015 12:04 PM, Andrei Borzenkov wrote:
В Fri, 03 Apr 2015 17:12:09 +0530 Sumit Bhardwaj sumitkbhardwaj@gmail.com пишет:
Hi All,
Not sure whether this is this is the correct place to discuss this. I am currently on the latest tumbleweed snapshot (20150330) with kernel 3.19.3-1-desktop X86_64 and Gnome 3.16. Since Last few updates, Plymouth themes that display some graphics or animation like the default openSUSE theme etc do not work. Instead the text theme with 3 question marks at the center of screen kicks in.
If I set it to some text based theme like tribar, details etc, it works fine. From the look of the display, it seems there is some problem with Plymouth while switching to the graphical mode. BTW, I am using it on a Thinkpad X240 with Haswell Core i7 4600U, 8 GB RAM and Intel HD4400 graphics.
Can anybody guide me how to resolve this? I am new to openSUSE but I have been a Linux user since 8-9 years, mostly Fedora and little bit of Debian experience as well.
Thanks.
This is likely the same problem as discussed recently on systemd list. Plymouth needs graphic driver loaded and fully initialized to display graphic theme. It does use (indirectly) udevadm settle but it now exits immediately if queue is empty. Which means plymouth can be started too early.
I had this same problem, cleared it up by using YaST-->Boot Loader to recreate all of the boot stuff and splash now plymonth now works as expected. Oh, I had a boot problem after one of the upgrades that forced me to recreate the boot loader stuff, next boot plymonth worked as designed.
On Saturday, April 04, 2015 08:07:47 Ken Schneider - openSUSE wrote:
On 04/03/2015 12:04 PM, Andrei Borzenkov wrote:
В Fri, 03 Apr 2015 17:12:09 +0530
Sumit Bhardwaj sumitkbhardwaj@gmail.com пишет:
Hi All,
Not sure whether this is this is the correct place to discuss this. I am currently on the latest tumbleweed snapshot (20150330) with kernel 3.19.3-1-desktop X86_64 and Gnome 3.16. Since Last few updates, Plymouth themes that display some graphics or animation like the default openSUSE theme etc do not work. Instead the text theme with 3 question marks at the center of screen kicks in.
If I set it to some text based theme like tribar, details etc, it works fine. From the look of the display, it seems there is some problem with Plymouth while switching to the graphical mode. BTW, I am using it on a Thinkpad X240 with Haswell Core i7 4600U, 8 GB RAM and Intel HD4400 graphics.
Can anybody guide me how to resolve this? I am new to openSUSE but I have been a Linux user since 8-9 years, mostly Fedora and little bit of Debian experience as well.
Thanks.
This is likely the same problem as discussed recently on systemd list. Plymouth needs graphic driver loaded and fully initialized to display graphic theme. It does use (indirectly) udevadm settle but it now exits immediately if queue is empty. Which means plymouth can be started too early.
I had this same problem, cleared it up by using YaST-->Boot Loader to recreate all of the boot stuff and splash now plymonth now works as expected. Oh, I had a boot problem after one of the upgrades that forced me to recreate the boot loader stuff, next boot plymonth worked as designed.
I removed all of plymouth just because, i dont see much boot-up and the system does not complain, just a thought, https://gist.github.com/anonymous/b9f6866098e417ff8d56
one way of working around this issue is to create a file called /etc/sysconfig/kernel and add a line for 'INITRD_MODULES=' in it
However, you need to set the value of INITRD_MODULES to your DRM driver, eg
INITRD_MODULES=i915 or INITRD_MODULES=nvidia or INITRD_MODULES=radeon
then running mkinitrd will recreate your initrd, tell Dracut to load your driver, and Plymouth will use it
On 5 April 2015 at 10:33, emanuel emanuel.castelo@gmail.com wrote:
On Saturday, April 04, 2015 08:07:47 Ken Schneider - openSUSE wrote:
On 04/03/2015 12:04 PM, Andrei Borzenkov wrote:
В Fri, 03 Apr 2015 17:12:09 +0530
Sumit Bhardwaj sumitkbhardwaj@gmail.com пишет:
Hi All,
Not sure whether this is this is the correct place to discuss this. I am currently on the latest tumbleweed snapshot (20150330) with kernel 3.19.3-1-desktop X86_64 and Gnome 3.16. Since Last few updates, Plymouth themes that display some graphics or animation like the default openSUSE theme etc do not work. Instead the text theme with 3 question marks at the center of screen kicks in.
If I set it to some text based theme like tribar, details etc, it works fine. From the look of the display, it seems there is some problem with Plymouth while switching to the graphical mode. BTW, I am using it on a Thinkpad X240 with Haswell Core i7 4600U, 8 GB RAM and Intel HD4400 graphics.
Can anybody guide me how to resolve this? I am new to openSUSE but I have been a Linux user since 8-9 years, mostly Fedora and little bit of Debian experience as well.
Thanks.
This is likely the same problem as discussed recently on systemd list. Plymouth needs graphic driver loaded and fully initialized to display graphic theme. It does use (indirectly) udevadm settle but it now exits immediately if queue is empty. Which means plymouth can be started too early.
I had this same problem, cleared it up by using YaST-->Boot Loader to recreate all of the boot stuff and splash now plymonth now works as expected. Oh, I had a boot problem after one of the upgrades that forced me to recreate the boot loader stuff, next boot plymonth worked as designed.
I removed all of plymouth just because, i dont see much boot-up and the system does not complain, just a thought, https://gist.github.com/anonymous/b9f6866098e417ff8d56 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi Cristian,
But can there be an issue if I do what is suggested by Richard? Or is it just about good practice? Right now, this issue is irritating me a little.
Thanks.
Regards, Sumit Bhardwaj
On Sunday 05 April 2015 09:45 PM, Cristian Rodríguez wrote:
On Sun, Apr 5, 2015 at 6:10 AM, Richard Brown RBrownCCB@opensuse.org wrote:
one way of working around this issue is to create a file called /etc/sysconfig/kernel and add a line for 'INITRD_MODULES=' in it
However, you need to set the value of INITRD_MODULES to your DRM driver, eg
INITRD_MODULES=i915 or INITRD_MODULES=nvidia or INITRD_MODULES=radeon
then running mkinitrd will recreate your initrd, tell Dracut to load your driver, and Plymouth will use it
Nope.. nope. nope.. do not recommend people to do this.. dracut has to include the needed modules in the initrd automatically.. if it does not.. then there is a bug..
On Sun, Apr 5, 2015 at 6:10 AM, Richard Brown RBrownCCB@opensuse.org wrote:
one way of working around this issue is to create a file called /etc/sysconfig/kernel and add a line for 'INITRD_MODULES=' in it
However, you need to set the value of INITRD_MODULES to your DRM driver, eg
INITRD_MODULES=i915 or INITRD_MODULES=nvidia or INITRD_MODULES=radeon
then running mkinitrd will recreate your initrd, tell Dracut to load your driver, and Plymouth will use it
Nope.. nope. nope.. do not recommend people to do this.. dracut has to include the needed modules in the initrd automatically.. if it does not.. then there is a bug..
On Sun, Apr 5, 2015 at 9:46 AM, Sumit Bhardwaj sumitkbhardwaj@gmail.com wrote:
Hi Cristian,
But can there be an issue if I do what is suggested by Richard? Or is it just about good practice? Right now, this issue is irritating me a little.
Something like that just continues the long standing tradition of papering over bugs somewhere else, if we need drm devices drivers in the initrd and dracut does not pull them in when plymouth is installed then there is a bug that needs fixing.
On Sunday, April 05, 2015 01:15:48 PM Cristian Rodríguez wrote:
then running mkinitrd will recreate your initrd, tell Dracut to load
your driver, and Plymouth will use it
Nope.. nope. nope.. do not recommend people to do this.. dracut has to
include the needed modules in the initrd automatically.. if it does
not.. then there is a bug..
Actually the issue is not with Dracut :) If you run a dracut -H and have a
new initrd file generated, then dracut will recognize the video driver
required and included it into the initrd file.
However as with many things, due to the sake of compatibility with other
programs the mkinitrd wrapper seems to be the culprit. I haven't checked, but
I guess that it calls dracut in such a way that it no longer checks which
video driver is required. I wonder when we can actually switch to just calling
dracut with the right parameters and drop these type of wrappers.
Regards
Raymond
On Sun, Apr 5, 2015 at 8:51 PM, Cristian Rodríguez crrodriguez@opensuse.org wrote:
On Sun, Apr 5, 2015 at 9:46 AM, Sumit Bhardwaj sumitkbhardwaj@gmail.com wrote:
Hi Cristian,
But can there be an issue if I do what is suggested by Richard? Or is it just about good practice? Right now, this issue is irritating me a little.
Something like that just continues the long standing tradition of papering over bugs somewhere else, if we need drm devices drivers in the initrd and dracut does not pull them in when plymouth is installed then there is a bug that needs fixing. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-
Andrei Borzenkov -
Cristian Rodríguez -
emanuel -
Ken Schneider - openSUSE -
Raymond Wooninck -
Richard Brown -
Sumit Bhardwaj