1. 21 Sep, 2020 1 commit
  2. 20 Sep, 2020 1 commit
  3. 18 Sep, 2020 3 commits
  4. 16 Sep, 2020 3 commits
  5. 15 Sep, 2020 2 commits
    • Hans de Goede's avatar
      NL translation update · 8dba434b
      Hans de Goede authored
      8dba434b
    • Hans de Goede's avatar
      drm: Honor modes selected by the user through video= kernel cmdline argument · 18f87e81
      Hans de Goede authored
      Before this commit we would skip preferred-mode selection if a video=
      kernel cmdline is argument, instead relying on the kernel to have activated
      all the outputs and then we would inherit those modes.
      
      But this relies on fbcon having initialized the outputs, which it does not
      do when deferred-fbcon-takeover is used. Deferred-fbcon-takeover is
      necessary for flickerfree boot, so this is now the default in many distros.
      
      Instead of relying on the kernel having setup everything for us, honor
      the video= mode selection by checking for modes with a DRM_MODE_TYPE_USERDEF
      flag before checking for modes with a DRM_MODE_TYPE_PREFERRED flag.
      
      Note that the DRM_MODE_TYPE_USERDEF flag is only ever set based on a
      video= argument. So on systems without a video= argument on the kernel
      cmdline nothing changes.
      Signed-off-by: default avatarHans de Goede <hdegoede@redhat.com>
      18f87e81
  6. 24 Aug, 2020 1 commit
  7. 23 Aug, 2020 1 commit
  8. 08 Aug, 2020 1 commit
  9. 07 Aug, 2020 1 commit
    • Sebastien's avatar
      Initialize the translations on start if they are available · f33e2014
      Sebastien authored
      setlocale was already called on filesystem mounting but that's not enough
      to cover all the cases. The call needs to be conditional because doing it
      at a time where the locales are not available (in the initrd) would
      result in translations to not be working.
      f33e2014
  10. 01 Aug, 2020 1 commit
  11. 31 Jul, 2020 1 commit
  12. 09 Jul, 2020 1 commit
  13. 08 Jul, 2020 8 commits
  14. 30 May, 2020 2 commits
  15. 01 May, 2020 1 commit
  16. 21 Apr, 2020 1 commit
  17. 18 Apr, 2020 1 commit
  18. 17 Apr, 2020 1 commit
    • Daniel van Vugt's avatar
      main: Don't bail out of load_settings if "Theme" is missing · 3a4b35b6
      Daniel van Vugt authored
      Because on some systems (like Ubuntu with its alternatives) the "Theme="
      line will be missing from plymouthd.defaults. And bailing out early was
      causing other settings like DeviceTimeout to never be loaded, which would
      then cause the graphics renderers to fail.
      3a4b35b6
  19. 07 Apr, 2020 3 commits
    • Ray Strode's avatar
      Merge branch 'wip/close-the-log' into 'master' · 6ca4b5b2
      Ray Strode authored
      main: switch log file when switching mode
      
      See merge request !102
      6ca4b5b2
    • Laurent Bigonville's avatar
      main: fix mode changing before splash is shown · 702fd05f
      Laurent Bigonville authored
      At the moment switching modes affects two aspects of how plymouth
      runs.
      
      1) What log file is opened (i.e., boot.log or no log file at all)
      2) What type of splash gets shown (the details of which are relegated
         to the individual splash plugins)
      
      The mode change handler has a check in place to avoid changing the
      type of splash getting shown in the event no splash is supposed to
      be shown yet.  This check just makes the function return without
      doing anything.
      
      Unfortunately, the check is placed at the top of the function, so
      it runs before the log file is changed.
      
      This commit moves the check lower down, so the log file gets properly
      updated when the mode is changed.
      702fd05f
    • Ray Strode's avatar
      main: switch log file when switching mode · 5cb1ad3a
      Ray Strode authored
      plymouthd can be run in various modes, for, e.g., boot up,
      shutdown, and software upgrades.
      
      The mode plymouthd is using can be changed at runtime.
      
      The "boot" mode keeps a log of the console messages that
      happen during boot up.  At the moment, when changing from
      the "boot" mode to any other mode, the log file is kept
      open.
      
      That open file can cause problems during shutdown.
      
      This commit makes sure the log file is properly closed when
      the mode is changed from boot to another mode.
      
      #88
      5cb1ad3a
  20. 06 Apr, 2020 4 commits
  21. 25 Mar, 2020 2 commits
    • Hans de Goede's avatar
      Merge branch 'drm-probe-speedups' into 'master' · e31c81f9
      Hans de Goede authored
      drm/kms probe speedups
      
      See merge request !101
      e31c81f9
    • Hans de Goede's avatar
      drm: Do not unnecessarily get output info twice · 3aa76fcd
      Hans de Goede authored
      When a kernel-mode-setting driver loads it will trigger an add udev event
      for /dev/dri/card0, followed by one udev change event per connector on the
      card. This means that after our initial probe of the card,
      create_heads_for_active_connectors is called a number of times for all the
      udev change events.
      
      After the initial enum our outputs array will contain active entries for
      all connected displays. Meaning that the first loop in
      create_heads_for_active_connectors would call get_output_info for
      these outputs. Under the hood this does a number of ioctls and especially
      the drmModeGetConnector call can be quite expensive.
      
      Then in the second loop create_heads_for_active_connectors would call
      get_output_info for all connectors, including for the once which were
      checked in the first loop.
      
      There is no reason why we cannot check if active connectors in the
      old outputs array have changed when we are calling get_output_info for
      all connectors to build the new array. This avoids unnecessarily making
      the expensive get_output_info call twice for active connectors in the
      old outputs array.
      Signed-off-by: default avatarHans de Goede <hdegoede@redhat.com>
      3aa76fcd