Re: Bug#734093: debian-installer: install plymouth by default
On 22.01.2014 03:05, Josh Triplett wrote:
On Wed, Jan 22, 2014 at 02:53:51AM +0100, Andreas Cadhalpun wrote:
Why do you think it would be bad to enable 'splash' by default?
Because then the splash screen would show up. :)
See my previous mails in this thread; I would like to avoid having a
splash screen enabled by default, in favor of keeping boot silent on
success, and making it as quick as possible.
I prefer the nice plymouth password prompt...
But perhaps we should let others state their opinion now.
And yes, the latter option would be easier for the user, but
probably more difficult for the package maintainer.
Seems rather straightforward for both, really; why would it be more
difficult for the maintainer?
How to make sure the 'splash' option is added to the boot command line
(and stays there, even if you purge grub and install lilo or similar
things)?
Thanks for the info. I tried to use 'i915.fastboot=1', but
unfortunately this just produced:
[drm:hsw_unclaimed_reg_check] *ERROR* Unclaimed write to 68080
[drm:hsw_unclaimed_reg_check] *ERROR* Unclaimed write to 68070
[drm:intel_uncore_check_errors] *ERROR* Unclaimed register before interrupt
[drm:hsw_unclaimed_reg_check] *ERROR* Unclaimed write to 68074
[drm:hsw_unclaimed_reg_check] *ERROR* Unclaimed write to 68080
[drm:hsw_unclaimed_reg_check] *ERROR* Unclaimed write to 68070
[drm:hsw_unclaimed_reg_check] *ERROR* Unclaimed write to 68074
I guess this is still in development.
You probably need newer kernel bits than you have, if you're seeing
those messages.
I just installed linux-image-3.13-trunk from experimental and still see
these errors.
This seems not to work for me, as I can't find any .svg's in /run/log.
I also tried 'init=/lib/systemd/systemd-bootchart' (the actual
location, this seems to be documented wrong) and this also didn't
work.
That may have been fixed in more recent versions of systemd;
discrepancies like that, which only matter on systems that still keep /
and /usr separate, will be an ongoing issue.
I don't know why you aren't seeing the files in /run/log. Do you see
them in the journal?
I tried:
sudo journalctl -F BOOTCHART
This gave no output.
Encryption will really throw off your numbers. If you want to do
boot-time testing, you should use a test system or test partition
without encryption.
Why? I'm more interested in the boot time of the machine I use than in
the boot time of some test system.
(Also, if you're using encryption, you're probably also using LVM, which
causes major boot-time slowdowns on all distributions, and is outright
broken on Debian systems. If udevadm settle is running at all in your
boot path, that needs fixing.)
Luckily I have no problems with LVM and systemd. (lvm2.service takes 548ms)
At least the systemd-udev-settle.service is not called during boot.
Best regards,
Andreas
Reply to: