[opensuse-factory] Getting Plymouth to work in Beta 1
Hello all, Has anyone been able to get Plymouth to work by it's default setting? What other packages are required? Cheers! Roman ----------------------------------------------------- openSUSE -- Get it! Discover it! Share it! ----------------------------------------------------- http://linuxcounter.net/ #179293 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 01/06/12 18:18, Roman Bysh escribió:
Hello all,
Has anyone been able to get Plymouth to work by it's default setting? What other packages are required?
Yes, working here in two different systems (nvidia/propietary, Intel/i915+kms) I got a warning that solved installing plugin-label package. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Friday, June 01, 2012, Cristian Rodríguez <crrodriguez@opensuse.org> wrote:
El 01/06/12 18:18, Roman Bysh escribió:
Hello all,
Has anyone been able to get Plymouth to work by it's default setting? What other packages are required?
Yes, working here in two different systems (nvidia/propietary, Intel/i915+kms) I got a warning that solved installing plugin-label package.
This particular issue is already resolved in Factory. What I also noticed is that the kernel command line is not adjusted. Please validate that in your grub settings the kernel command line is correct "splash quiet" instead of "splash=silent" or "splash=verbose". The last two are incompatible with plymouth and would cause a black screen. Regards Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On June 2, 2012 11:03:25 AM Raymond Wooninck wrote:
On Friday, June 01, 2012, Cristian Rodríguez <crrodriguez@opensuse.org> wrote:
El 01/06/12 18:18, Roman Bysh escribió:
Hello all,
Has anyone been able to get Plymouth to work by it's default setting? What other packages are required?
Yes, working here in two different systems (nvidia/propietary, Intel/i915+kms) I got a warning that solved installing plugin-label package. This particular issue is already resolved in Factory. What I also noticed is that the kernel command line is not adjusted. Please validate that in your grub settings the kernel command line is correct "splash quiet" instead of "splash=silent" or "splash=verbose". The last two are incompatible with plymouth and would cause a black screen.
Regards
Raymond
I'm still seeing a very brief black screen between the space flares and kdm theme to desktop. Is there a way of removing the black screen? Are there plans to have a smooth transition between Plymouth and kdm theme? Have you decided which Plymouth theme will be used as the default? Cheers! Roman ----------------------------------------------------- openSUSE -- Get it! Discover it! Share it! ----------------------------------------------------- http://linuxcounter.net/ #179293 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Saturday, June 02, 2012, Roman Bysh <rbtc1@rogers.com> wrote:
I'm still seeing a very brief black screen between the space flares and kdm theme to desktop. Is there a way of removing the black screen?
Are there plans to have a smooth transition between Plymouth and kdm theme?
Have you decided which Plymouth theme will be used as the default?
I am not the one deciding on the default Plymouth theme. I know that that artwork team is working hard on providing an openSUSE theme for plymouth which would be similar to the bootsplash one. Which theme are you currently using ? I know about a black screen transition from grub to plymouth, which is caused by the intel driver and some screen writes (echo "..") inside the initrd. The other one could be caused by the change of backgrounds when switching from plymouth to KDM Regards Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On June 2, 2012 05:58:56 PM Raymond Wooninck wrote:
On Saturday, June 02, 2012, Roman Bysh <rbtc1@rogers.com> wrote:
I'm still seeing a very brief black screen between the space flares and kdm theme to desktop. Is there a way of removing the black screen?
Are there plans to have a smooth transition between Plymouth and kdm theme?
Have you decided which Plymouth theme will be used as the default?
I am not the one deciding on the default Plymouth theme. I know that that artwork team is working hard on providing an openSUSE theme for plymouth which would be similar to the bootsplash one.
Which theme are you currently using ?
I know about a black screen transition from grub to plymouth, which is caused by the intel driver and some screen writes (echo "..") inside the initrd. The other one could be caused by the change of backgrounds when switching from plymouth to KDM
Regards
Raymond
I am using the solar flares. Even if there was a change of backgrounds, there shouldn't be a delay. Look at at Windows. Even Windows switches from one scene to another without a small delay between images filled with black. Isn't this the reason we are using Plymouth? To get away from from the flickering and black screens. Can we set the echo to 0 ms? Cheers! Roman ----------------------------------------------------- openSUSE -- Get it! Discover it! Share it! ----------------------------------------------------- http://linuxcounter.net/ #179293 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le samedi 02 juin 2012 à 11:03 +0200, Raymond Wooninck a écrit :
On Friday, June 01, 2012, Cristian Rodríguez <crrodriguez@opensuse.org> wrote:
El 01/06/12 18:18, Roman Bysh escribió:
Hello all,
Has anyone been able to get Plymouth to work by it's default setting? What other packages are required?
Yes, working here in two different systems (nvidia/propietary, Intel/i915+kms) I got a warning that solved installing plugin-label package.
This particular issue is already resolved in Factory. What I also noticed is that the kernel command line is not adjusted. Please validate that in your grub settings the kernel command line is correct "splash quiet" instead of "splash=silent" or "splash=verbose". The last two are incompatible with plymouth and would cause a black screen.
Really ? IIRC, "splash" should be handled as "splash=silent" (I fixed that bugs some years ago in plymouth code). If not, we should fix it again. -- Frederic Crozat <fcrozat@suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Monday, June 04, 2012, Frederic Crozat <fcrozat@suse.com> wrote:
This particular issue is already resolved in Factory. What I also noticed is that the kernel command line is not adjusted. Please validate that in your grub settings the kernel command line is correct "splash quiet" instead of "splash=silent" or "splash=verbose". The last two are incompatible with plymouth and would cause a black screen.
Really ? IIRC, "splash" should be handled as "splash=silent" (I fixed that bugs some years ago in plymouth code). If not, we should fix it again.
Hi Frederic, Well, this is based on my own findings. When I put splash=silent as the kernel-option then I do not see any Plymouth screen. Changing this to just splash, makes things work. I guess we have to check the plymouth code then to see if your bugfix is still in there or that things have changed and fix it again. At the moment I am fixing it by changing the kernel command line option and removing everything behind splash. As that we are working on a full integration with grub2, we might not need to have this fixed. Regards Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le lundi 04 juin 2012 à 11:09 +0200, Raymond Wooninck a écrit :
On Monday, June 04, 2012, Frederic Crozat <fcrozat@suse.com> wrote:
This particular issue is already resolved in Factory. What I also noticed is that the kernel command line is not adjusted. Please validate that in your grub settings the kernel command line is correct "splash quiet" instead of "splash=silent" or "splash=verbose". The last two are incompatible with plymouth and would cause a black screen.
Really ? IIRC, "splash" should be handled as "splash=silent" (I fixed that bugs some years ago in plymouth code). If not, we should fix it again.
Hi Frederic,
Well, this is based on my own findings. When I put splash=silent as the kernel-option then I do not see any Plymouth screen. Changing this to just splash, makes things work.
I guess we have to check the plymouth code then to see if your bugfix is still in there or that things have changed and fix it again.
I just did a quick search on git and "splash" and "splash=silent" should be handled the same way. -- Frederic Crozat <fcrozat@suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Friday 01 June 2012 18:18:56 Roman Bysh wrote:
Has anyone been able to get Plymouth to work by it's default setting? What other packages are required?
Is it possible to use Plymouth with grub legacy? I'm multibooting Beta1 with 12.1's grub, and get a black screen between the bootsplash and KDE autologin. Will -- Will Stephenson | openSUSE Board, openSUSE Boosters Team, KDE Developer SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le lundi 04 juin 2012 à 12:54 +0200, Will Stephenson a écrit :
On Friday 01 June 2012 18:18:56 Roman Bysh wrote:
Has anyone been able to get Plymouth to work by it's default setting? What other packages are required?
Is it possible to use Plymouth with grub legacy? I'm multibooting Beta1 with 12.1's grub, and get a black screen between the bootsplash and KDE autologin.
Nothing prevents that. But to be a smooth transition between splash and display manager, there is some adaptation needed on the display manager side (I know KDM needs a patch, I don't know if we have it already or not), so X server is started in a mode which doesn't reset the screen to black and KDM will notify plymouth to quit and handle the nice fade.. -- Frederic Crozat <fcrozat@suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Monday, June 04, 2012, Frederic Crozat <fcrozat@suse.com> wrote:
Le lundi 04 juin 2012 à 12:54 +0200, Will Stephenson a écrit :
Is it possible to use Plymouth with grub legacy? I'm multibooting Beta1 with 12.1's grub, and get a black screen between the bootsplash and KDE autologin. Nothing prevents that.
Plymouth can be used with Grub and Grub2. No difference in it's behaviour.
But to be a smooth transition between splash and display manager, there is some adaptation needed on the display manager side (I know KDM needs a patch, I don't know if we have it already or not), so X server is started in a mode which doesn't reset the screen to black and KDM will notify plymouth to quit and handle the nice fade..
That patch was installed already, but somehow it doesn't prevent this from happening. I have to see if GDM has the same behaviour or not. Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Monday, June 04, 2012, Raymond Wooninck <tittiatcoke@gmail.com> wrote:
On Monday, June 04, 2012, Frederic Crozat <fcrozat@suse.com> wrote:
But to be a smooth transition between splash and display manager, there is some adaptation needed on the display manager side (I know KDM needs a patch, I don't know if we have it already or not), so X server is started in a mode which doesn't reset the screen to black and KDM will notify plymouth to quit and handle the nice fade..
I just rebooted with a changed setup and with GDM as the display manager. What I see is that the screen turns black, but at that moment I also have a mouse cursor already active., so GDM must be active and busy loading the graphics (background, menu, etc). I am not sure how we can optimize this further unless we find a way to make GDM switch off plymouth only when it has finished loading everything. I also tried the splash=silent and this one indeed works. Don't know what happened in the past, but it seems to be initializing plymouth correctly and I will adjust the plymouth packages to remove the part where I change the splash= lines. Regards Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le lundi 04 juin 2012 à 14:38 +0200, Raymond Wooninck a écrit :
On Monday, June 04, 2012, Raymond Wooninck <tittiatcoke@gmail.com> wrote:
On Monday, June 04, 2012, Frederic Crozat <fcrozat@suse.com> wrote:
But to be a smooth transition between splash and display manager, there is some adaptation needed on the display manager side (I know KDM needs a patch, I don't know if we have it already or not), so X server is started in a mode which doesn't reset the screen to black and KDM will notify plymouth to quit and handle the nice fade..
I just rebooted with a changed setup and with GDM as the display manager. What I see is that the screen turns black, but at that moment I also have a mouse cursor already active., so GDM must be active and busy loading the graphics (background, menu, etc). I am not sure how we can optimize this further unless we find a way to make GDM switch off plymouth only when it has finished loading everything.
This is the way it is supposed to work: if gdm is handling plymouth shutdown, it should not be done at systemd / initscript level. I guess /etc/init.d/xdm should be modified to terminate plymouth when not starting gdm / kdm (if we have the needed support in kdm) but only when starting xdm (or maybe lxdm, not 100% sure about its status).
I also tried the splash=silent and this one indeed works. Don't know what happened in the past, but it seems to be initializing plymouth correctly and I will adjust the plymouth packages to remove the part where I change the splash= lines.
Excellent. -- Frederic Crozat <fcrozat@suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Monday, June 04, 2012, Frederic Crozat <fcrozat@suse.com> wrote:
What I see is that the screen turns black, but at that moment I also have a mouse cursor already active., so GDM must be active and busy loading the graphics (background, menu, etc). I am not sure how we can optimize this further unless we find a way to make GDM switch off plymouth only when it has finished loading everything.
This is the way it is supposed to work: if gdm is handling plymouth shutdown, it should not be done at systemd / initscript level. I guess /etc/init.d/xdm should be modified to terminate plymouth when not starting gdm / kdm (if we have the needed support in kdm) but only when starting xdm (or maybe lxdm, not 100% sure about its status).
At this moment openSUSE would offer at least 3 DM's that are aware of plymouth and can handle it correctly. These are GDM, KDM and lightdm. I guess xdm is a different case, but I am not sure if openSUSE provides a desktop that uses a different displaymanager than the three indicated. I have to checkout the Fedora release, but as far as I know they do not have this "black screen" when starting up KDM/GDM. So somehow here the loading of the graphics is faster or they are doing something different. I know that the "black screen" between grub and plymouth is caused by the moment where plymouth is started within the initrd sequence. However plymouth is depending on the creation of devices (udev step), and I am not really sure if we want to go toward the direction where the plymouth script is creating the console devices, etc (like Fedora is doing),. But this could always be targetted for the 12.3 release. Regards Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le lundi 04 juin 2012 à 15:19 +0200, Raymond Wooninck a écrit :
On Monday, June 04, 2012, Frederic Crozat <fcrozat@suse.com> wrote:
What I see is that the screen turns black, but at that moment I also have a mouse cursor already active., so GDM must be active and busy loading the graphics (background, menu, etc). I am not sure how we can optimize this further unless we find a way to make GDM switch off plymouth only when it has finished loading everything.
This is the way it is supposed to work: if gdm is handling plymouth shutdown, it should not be done at systemd / initscript level. I guess /etc/init.d/xdm should be modified to terminate plymouth when not starting gdm / kdm (if we have the needed support in kdm) but only when starting xdm (or maybe lxdm, not 100% sure about its status).
At this moment openSUSE would offer at least 3 DM's that are aware of plymouth and can handle it correctly. These are GDM, KDM and lightdm. I guess xdm is a different case, but I am not sure if openSUSE provides a desktop that uses a different displaymanager than the three indicated.
I have to checkout the Fedora release, but as far as I know they do not have this "black screen" when starting up KDM/GDM. So somehow here the loading of the graphics is faster or they are doing something different.
black screen usually means X wasn't started with "-background none" as an option (it is up to GDM / KDM to add this to X server command line, if they detected plymouth was running. -- Frederic Crozat <fcrozat@suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Monday, June 04, 2012, Frederic Crozat <fcrozat@suse.com> wrote:
black screen usually means X wasn't started with "-background none" as an option (it is up to GDM / KDM to add this to X server command line, if they detected plymouth was running.
I can remember that I already checked this once with Vincent and I can confirm that both KDM and GDM are starting the X-server with the following arguments: ServerArgsLocal=-nolisten tcp -background none So this should be fine. I have now Fedora 17 running in a Virtualbox, so will check what parameters they use. Regards Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi, see https://bugzilla.novell.com/show_bug.cgi?id=765277#c4 Two installations, one with grub, one with grub2, both with systemd now do the plymouth-branding-openSUSE job. Seems not to be related to X, gdm, kdm or whatever displaymanager. Good luck Hans-Peter -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Monday, June 04, 2012, Hans-Peter Holler <holler@nefkom.info> wrote:
see https://bugzilla.novell.com/show_bug.cgi?id=765277#c4
Two installations, one with grub, one with grub2, both with systemd now do the plymouth-branding-openSUSE job. Seems not to be related to X, gdm, kdm or whatever displaymanager.
Hi Hans-Peter, Thanks for sorting this one out :-) I should have checked that one before making plymouth the default. The behavior of the packages is different than when it is installed separetely. There the %post installation script of the branding-openSUSE changed the theme correctly. Will update the package and submit to factory. Thanks Regards Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Monday 04 June 2012 20.29:56 Raymond Wooninck wrote:
On Monday, June 04, 2012, Hans-Peter Holler <holler@nefkom.info> wrote:
see https://bugzilla.novell.com/show_bug.cgi?id=765277#c4
Two installations, one with grub, one with grub2, both with systemd now do the plymouth-branding-openSUSE job. Seems not to be related to X, gdm, kdm or whatever displaymanager.
Hi Hans-Peter,
Thanks for sorting this one out :-) I should have checked that one before making plymouth the default. The behavior of the packages is different than when it is installed separetely. There the %post installation script of the branding-openSUSE changed the theme correctly.
Will update the package and submit to factory.
Thanks
Regards
Raymond
Damn I've seen that before, and was too much conditioned to make manually plymouth-set-default openSUSE && mkinitrd :-) -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Ambassador GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Montag 04 Juni 2012, 20:39:56 schrieb Bruno Friedmann: ...
Damn I've seen that before, and was too much conditioned to make manually plymouth-set-default openSUSE && mkinitrd
:-)
We, me as a former employee and now more than years user, and you as the distributors, all these former collegues and all the community members and working people should have an eye what an upcoming release of openSUSE can have an impact on Linux-Users: this booting up with _this_ theme, then go further with another (plymouth) then in the end ending with an (k,g,whatever d)m-theme is not _good_ as an eye-catch for an everytime-suse-user and worse for an newbie.This is annoying at beta-time! At old times beta told us: all is closed ,) but allow us to fix bugs. Is this a bug? Greetings, Hans-Peter -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Monday, June 04, 2012, Hans-Peter Holler <holler@nefkom.info> wrote:
this booting up with _this_ theme, then go further with another (plymouth) then in the end ending with an (k,g,whatever d)m-theme is not _good_ as an eye-catch for an everytime-suse-user and worse for an newbie.This is annoying at beta-time!
Plymouth was already in Factory for some time, but as it got installed separately the %post scripts worked and set the correct theme. With Beta 1 it was set as default so that it would get a wider testing and to allow us to fix bugs. And this is exactly what happened and we are fixing every bug that appears. So with Beta 2 the experience should be much better. Regards Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Monday 04 June 2012 21.49:13 Hans-Peter Holler wrote:
this booting up with _this_ theme, then go further with another (plymouth) then in the end ending with an (k,g,whatever d)m-theme is not _good_ as an eye-catch for an everytime-suse-user and worse for an newbie.This is annoying at beta-time!
At old times beta told us: all is closed ,) but allow us to fix bugs.
Is this a bug?
Greetings, Hans-Peter
Don't forget that we didn't have lot of chance during 12.2 factory devel process before beta with all the external defect that have affected the infrastructure. Then yes those ~15 days missing are visible :-( -- Bruno Friedmann openSUSE Member & Ambassador GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
I have to checkout the Fedora release, but as far as I know they do not have this "black screen" when starting up KDM/GDM. So somehow here the loading of the graphics is faster or they are doing something different.
RHEL has it, not sure about Fedora, F17 doesn't install with my partition layout (openSUSE does though ;))
I know that the "black screen" between grub and plymouth is caused by the moment where plymouth is started within the initrd sequence. However plymouth is depending on the creation of devices (udev step), and I am not really sure if we want to go toward the direction where the plymouth script is creating the console devices, etc (like Fedora is doing),.
Can this black screen have it's origins on VT switch from 1 to 7 ? Everyone else moved X session to vt1, I'm pretty sure there's something behind it, maybe asking Strode would be a good idea, of all, he's the one who probably knows it. If I recall correctly from the docs in 2010, plymouth should exit without refreshing the screen (thus keeping the last image on the display) and X needed to be restarted with a switch (-r if I recall correctly) so it doesn't refresh the screen in order to keep the 'frozen' screen image from plymouth exit until GDM loads up. May it be that X is actually kicking in before plymouth actually exits? May it be that the vt transiction from 1 to 7 originates this? I mean, are you sure that screen isn't meant to updated on a vt switch ? ;=) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
RHEL has it, not sure about Fedora, F17 doesn't install with my partition layout (openSUSE does though ;))
I installed Fedora 17 in a virtualbox to test further. I am quite impressed with the startup speed, but I also looked carefully at the Plymouth behavior. And what I can see is similar to what we have on openSUSE, namely: 1) There is a small flicker happening between Grub2 and Plymouth. This is a shorter flicker than on openSUSE, due to the fact that Fedora is initializing deviced inside the Plymouth startup scripts. 2) There is a black screen between Plymouth and KDM. However the question arises if this is indeed a flicker/black screen, as that there is a mouse pointer visible which indicates that KDM is loading.
Can this black screen have it's origins on VT switch from 1 to 7 ? Everyone else moved X session to vt1, I'm pretty sure there's something behind it, maybe asking Strode would be a good idea, of all, he's the one who probably knows it.
As indicated above also Fedora has the small flicker in between Grub and Plymouth. Working on VT 7 doesn't influence this, but it points all to the fact that as soon as Grub starts loading the initrd, it's graphical screen is disabled and then it waits until Plymouth starts.
If I recall correctly from the docs in 2010, plymouth should exit without refreshing the screen (thus keeping the last image on the display) and X needed to be restarted with a switch (-r if I recall correctly) so it doesn't refresh the screen in order to keep the 'frozen' screen image from plymouth exit until GDM loads up.
It seems that the question is more how fast can GDM/KDM loads its graphical screen. Maybe an idea would be to see if GDM/KDM can kill plymouth at a later stage, but I am not sure about that. Regards Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le mardi 05 juin 2012 à 10:08 +0200, Raymond Wooninck a écrit :
2) There is a black screen between Plymouth and KDM. However the question arises if this is indeed a flicker/black screen, as that there is a mouse pointer visible which indicates that KDM is loading.
Hmm, did you test on "real" hardware ? To get a smooth transition, there is some patches needed in Xorg driver. I know we have them for Intel, Radeon and nouveau but I don't think we have similar stuff for vesa nor virtualbox driver (but I might be wrong). -- Frederic Crozat <fcrozat@suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
2012/6/5 Frederic Crozat <fcrozat@suse.com>:
Le mardi 05 juin 2012 à 10:08 +0200, Raymond Wooninck a écrit :
2) There is a black screen between Plymouth and KDM. However the question arises if this is indeed a flicker/black screen, as that there is a mouse pointer visible which indicates that KDM is loading.
Hmm, did you test on "real" hardware ? To get a smooth transition, there is some patches needed in Xorg driver. I know we have them for Intel, Radeon and nouveau but I don't think we have similar stuff for vesa nor virtualbox driver (but I might be wrong).
You need a driver that supports KMS; proprietary drivers do have the black screen.
-- Frederic Crozat <fcrozat@suse.com> SUSE
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- Nelson Marques // I've stopped trying to understand sandwiches with a third piece of bread in the middle... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le mardi 05 juin 2012 à 12:36 +0100, Nelson Marques a écrit :
2012/6/5 Frederic Crozat <fcrozat@suse.com>:
Le mardi 05 juin 2012 à 10:08 +0200, Raymond Wooninck a écrit :
2) There is a black screen between Plymouth and KDM. However the question arises if this is indeed a flicker/black screen, as that there is a mouse pointer visible which indicates that KDM is loading.
Hmm, did you test on "real" hardware ? To get a smooth transition, there is some patches needed in Xorg driver. I know we have them for Intel, Radeon and nouveau but I don't think we have similar stuff for vesa nor virtualbox driver (but I might be wrong).
You need a driver that supports KMS; proprietary drivers do have the black screen.
KMS usually is not enough (unless it changed recently). PS: please don't cc me. -- Frederic Crozat <fcrozat@suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 06/05/2012 04:18 AM, Frederic Crozat wrote:
Le mardi 05 juin 2012 à 10:08 +0200, Raymond Wooninck a écrit :
2) There is a black screen between Plymouth and KDM. However the question arises if this is indeed a flicker/black screen, as that there is a mouse pointer visible which indicates that KDM is loading.
Hmm, did you test on "real" hardware ? To get a smooth transition, there is some patches needed in Xorg driver. I know we have them for Intel, Radeon and nouveau but I don't think we have similar stuff for vesa nor virtualbox driver (but I might be wrong).
I am always testing Plymouth on real hardware. I am using an older nVIDIA GeForce 8600 GTS graphics card. The default installation of Plymouth with Beta 1 produced nothing but a black screen up until the kdm theme appeared. Cheers! Roman --------------------------------------------------------------- openSUSE -- Get it! Discover it! Share it! --------------------------------------------------------------- http://linuxcounter.net/ #179293 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (8)
-
Bruno Friedmann -
Cristian Rodríguez -
Frederic Crozat -
Hans-Peter Holler -
Nelson Marques -
Raymond Wooninck -
Roman Bysh -
Will Stephenson