Le jeudi 16 février 2012 à 11:25 +0100, Ludwig Nussel a écrit :

Vincent Untz wrote:

...

[...] The difference between a smooth boot without a flicker and a switch to another tty on ctrl+alt+Fn is that in the latter case, you do a specific action to create the flicker -- it's still bad, but at least it results from user action.

So when you boot on vt1 and X starts up on vt1 it takes over settings and there is no flicker, right? So shouldn't it be possible for X to start on vt7 and take the settings from vt1? There shouldn't be any flicker when switching vt's that have the same settings, right?

you won't get flicker either if both plymouth when starting switch to vt7 before displaying it splash, then X starting in vt7 won't cause any flickr. We had it configured this way (and Ubuntu too IIRC) in Mandriva. I'd say it is more a decision on keeping the current setup or switching to X being on vt1 (which would be, in a way, easier, so we know it won't switch from vt7 to vt8 for no really good reason if X get restarted). -- Frederic Crozat SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Doesn't plymouthd supports a '--tty' argument ? NM 2012/2/16 Raymond Wooninck :

Hi Frederic,

...

you won't get flicker either if both plymouth when starting switch to vt7 before displaying it splash, then X starting in vt7 won't cause any flickr. We had it configured this way (and Ubuntu too IIRC) in Mandriva.

As indicated also on IRC, building plymouth in the same way as on Mandriva (using vt7) leads to a text mode boot, without any signs of Plymouth (not on vt7 nor on vt1). Question would be if something else needs to be reconfigured as well in order to have vt7 available.  At the moment it looks like that only vt1 is supported during the boot process until the moment where the other VT's are becoming available. It could be that this is a simple parameter somewhere, but I haven't found this one yet. So any help in this area is more than welcome.

...

I'd say it is more a decision on keeping the current setup or switching to X being on vt1 (which would be, in a way, easier, so we know it won't switch from vt7 to vt8 for no really good reason if X get restarted).

In the past it made sense to keep vt1 available for all the messages that sysvinit was giving during the boot process. However now with systemd, the usage of vt1 as a kind of error logging device seems to be over as that most information is only available in the syslog (or the journal of systemd).

Thanks

Regards

Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-- Nelson Marques /* http://www.marques.so   nmo.marques@gmail.com */ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Hi Nelson,

Doesn't plymouthd supports a '--tty' argument ?

Well it does. However it seems that for openSUSE we need to follow a little different specification for the argument. During the build process you can indicate which tty's to use for boot and shutdown. It should be enough to just use tty1 or tty7. However this results in the text mode boot that I indicated in my email. Today I got a step closer as that it seems that I need to specify the full patch (/dev/ttyX). With this I have now plymouth running on tty7 (and of course also the Graphical session). I still have to test what effect this will have on the transistion from GRUB to Plymouth, but at least we can now choose on which tty plymouth should run. At the moment I see two outstanding issues which would prevent switching to Plymouth (besides the necessary Artwork). The first issue would be with encrypted disks. Plymouth comes to the point to ask the passphrase, but something goes wrong here. Currently I am trying to patch cryptsetup to have a kind of plymouth support here. The second issue is with suspend/hibernate. As was indicated already at the beginning, these two rely on splashy for their splashscreen. With the help of Frederic Crozat, we have now a patch for suspend which should bring us plymouth support for suspend/hibernate. I still need to test this. So it seems that every day we are getting closer and closer to a situation where I can submit the changes to Factory to enable Plymouth support. Regards Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Thu 16 Feb 2012 03:50:15 PM EST, Nelson Marques wrote:

2012/2/16 Raymond Wooninck:

...

Hi Nelson,

...

Doesn't plymouthd supports a '--tty' argument ?

Well it does. However it seems that for openSUSE we need to follow a little different specification for the argument. During the build process you can indicate which tty's to use for boot and shutdown. It should be enough to just use tty1 or tty7. However this results in the text mode boot that I indicated in my email.

Today I got a step closer as that it seems that I need to specify the full patch (/dev/ttyX). With this I have now plymouth running on tty7 (and of course also the Graphical session). I still have to test what effect this will have on the transistion from GRUB to Plymouth, but at least we can now choose on which tty plymouth should run.

At the moment I see two outstanding issues which would prevent switching to Plymouth (besides the necessary Artwork). The first issue would be with encrypted disks. Plymouth comes to the point to ask the passphrase, but something goes wrong here. Currently I am trying to patch cryptsetup to have a kind of plymouth support here.

Please check this from Jeff's repo, I think he has sorted this in the past:

https://build.opensuse.org/package/files?package=cryptsetup&project=home%3Ajeff_mahoney%3Abetterbooting

boot.crypto-plymouth

Hope it helps, a lot of work has been done by Jeff on the past, maybe some of the answers for what you need are there ;)

NM

...

The second issue is with suspend/hibernate. As was indicated already at the beginning, these two rely on splashy for their splashscreen. With the help of Frederic Crozat, we have now a patch for suspend which should bring us plymouth support for suspend/hibernate. I still need to test this.

So it seems that every day we are getting closer and closer to a situation where I can submit the changes to Factory to enable Plymouth support.

Regards

Raymond

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

I would like to test Plymouth with Milestone 1. Which packages should be desinstalled before installing Plymouth? -- Cheers! Roman ------------------------------------------------------------------ openSUSE Linux -- Get it! Discover it! Share it! ------------------------------------------------------------------ http://counter.li.org #179293 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Raymond, Anyway we can have a wiki page for this? I would be interested in testing this as well ;) NM 2012/2/16 Raymond Wooninck :

Hi Roman,

...

I would like to test Plymouth with Milestone 1.

Which packages should be desinstalled before installing Plymouth?

The Plymouth package has been setup in such a way that the bootsplash package is automatically de-installed and the systemd-plymouth package is installed. However at this moment there are two systemd services that needs to be disabled manually.  I want to check with Frederic how I can do this automatically and then things should be ready,

So please wait till tomorrow and then I will announce how and what on this mailinglist. Include the repository to use.

Regards

Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-- Nelson Marques /* http://www.marques.so   nmo.marques@gmail.com */ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

* Roman Bysh [02-16-12 16:53]:

On Thu 16 Feb 2012 04:43:00 PM EST, Nelson Marques wrote:

...

Raymond,

Anyway we can have a wiki page for this? I would be interested in testing this as well ;)

No problem. The more testers we have the better.

I will also, on my 12.2 factory test machine. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Le jeudi 16 février 2012 à 22:40 +0100, Raymond Wooninck a écrit :

Hi Roman,

...

I would like to test Plymouth with Milestone 1.

Which packages should be desinstalled before installing Plymouth?

The Plymouth package has been setup in such a way that the bootsplash package is automatically de-installed and the systemd-plymouth package is installed. However at this moment there are two systemd services that needs to be disabled manually. I want to check with Frederic how I can do this automatically and then things should be ready,

First, I suggest pushing plymouth package to Factory (even if it not 100% working), since it will need to pass legal review and it will take some time. Once it is in Factory, we'll be able to handle correctly plymouth vs bootsplash (I'll probably move the current bootsplash service from systemd package to bootsplash). -- Frederic Crozat SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org