• 18 Posts
  • 143 Comments
Joined 3 years ago
Aquileo | cake
Cake day: June 10th, 2023

Aquileo | help-circle
  • vole@lemmy.worldtoLinux@lemmy.mlWhy is the TPM so slow on boot?
    Aquileo | link
    Aquileo | fedilink
    English
    Aquileo | arrow-up
    10
    ·
    20 hours ago

    The first thing is to do is to understand what you’re looking at. Read this:

    systemd-analyze blame¶

    This command prints a list of all running units, ordered by the time they took to initialize. This information may be used to optimize boot-up times. Note that the output might be misleading as the initialization of one service might be slow simply because it waits for the initialization of another service to complete. Also note: systemd-analyze blame does not display results for services with Type=simple, because systemd considers such services to be started immediately, hence no measurement of the initialization delays can be done. Also note that this command only shows the time units took for starting up, it does not show how long unit jobs spent in the execution queue. In particular it shows the time units spent in “activating” state, which is not defined for units such as device units that transition directly from “inactive” to “active”. This command hence gives an impression of the performance of program code, but cannot accurately reflect latency introduced by waiting for hardware and similar events.

    For example: I have passphrase disk encryption (no TPM encryption), and the time I take to enter the passphrase is added to many entries in systemd-analyze blame. Here is the output of systemd-analyze blame if I wait 2 minutes to enter my disk encryption passphrase:

    2min 12.640s sys-module-fuse.device
    2min 12.618s sys-devices-platform-MSFT0101:00-tpm-tpm0.device
    2min 12.618s dev-tpm0.device
    2min 12.551s dev-ttyS0.device
    2min 12.551s sys-devices-pnp0-00:00-00:00:0-00:00:0.0-tty-ttyS0.device
    2min 12.550s dev-ttyS2.device
    ...
    

    So, I guess my advice is that systemd-analyze blame is not always going to be a clear indicator that a particular service is holding your boot times back. The .device entries in particular probably just represent how long after boot that the device became active. And unfortunately the systemd-analyze tools do not always lead you to the underlying delay.

    $ systemd-analyze critical-chain dev-tpm0.device
    The time when unit became active or started is printed after the "@" character.
    The time the unit took to start is printed after the "+" character.
    
    dev-tpm0.device +2min 12.618s
    
    $ systemd-analyze critical-chain dracut-initqueue.service
    The time when unit became active or started is printed after the "@" character.
    The time the unit took to start is printed after the "+" character.
    
    dracut-initqueue.service +2min 11.123s
    └─systemd-udev-trigger.service @770ms +158ms
      └─systemd-udevd-varlink.socket @760ms +65us
        └─system.slice
          └─-.slice
    

    If you are trying to deal with an issue that is causing significant delays in your boot time, journalctl --boot can sometimes be helpful. For the example boot above where I waited 2 minutes before entering the disk encryption passphrase:

    Jul 31 14:09:39 mycomputer kernel: Linux version 7.1.5-201.fc44.x86_64 (mockbuild@9b86e96a386140128351588d751166fd) (gcc (GCC) 16.1.1 20260515 (Red Hat 16.1.1-2), GNU ld versi>
    ... (a lot of log lines within a few seconds, but then I find a big jump) ...
    Jul 31 14:09:44 mycomputer kernel: [drm] pre_validate_dsc:1667 MST_DSC dsc precompute is not needed
    Jul 31 14:11:48 mycomputer systemd-cryptsetup[551]: Set cipher aes, mode xts-plain64, key size 512 bits for device /dev/disk/by-uuid/...
    ... (and then there are a lot of log lines in the following seconds after the above line) ...
    



  • vole@lemmy.worldtoAnime@ani.socialAnime I've tried in 2026
    Aquileo | link
    Aquileo | fedilink
    English
    Aquileo | arrow-up
    2
    ·
    11 days ago

    Daemons is like a good rendition of a forgettable 2000’s shounen battle anime. It might shine compared against Shaman King and Zatch Bell (I was so young when I watched these, I don’t remember if they’re actually good), but it’s hard to think much of Daemons once you’ve seen battle shounen done well (Jojo, FMA, HxH). I was watching the series as it aired, and I dropped off after episode 12 (I think because there was a short break). I will continue to watch it, but it doesn’t pop out as a show to watch even though episode 12 ended with a cliffhanger.

    It could be a slow burn, but perhaps too slow. From a recent MAL thread on the manga:

    Is the manga anywhere near completion?

    No way. We’re still on setup arcs. We don’t even know who the main antagonists are yet.


  • With most Linux OS’s you have a choice of what desktop environment to use. The desktop environment controls most of what I would call the OS experience. Most linux distros will have KDE or Gnome installed as the default desktop environment, though there are often some more minimal or power-user focused desktop environments offered. I’ve heard Cinnamon is another good choice.

    Ctrl-C, Ctrl-X, Ctrl-V, Ctrl-F, F3, F11 generally behave the same on most Linux desktop environment and software as they do on Windows.

    Alt-Tab, Alt-F4 are commonly supported

    For the run menu, Alt-F2 opens a similar menu in KDE and Gnome. I can only go into the specifics with KDE, but I can also run commands with the regular Windows key start menu. Though when I personally run commands, I generally open a terminal (Ctrl-Alt-T) so I can get tab completion. On KDE, Win+E opens a file explorer. Almost all the keyboard shortcuts are customizable on KDE, but I prefer to swim with the current whenever possible.

    For some distros, you can write a “Live” version to a flash drive to try it out before installing, but opening applications will be slower than running on an SSD.











  • I also don’t remember why Meili is on Subaru’s side now, and who her mom is. I feel like they have too many things to explain and didn’t have enough time.

    Season 2 is wiped from my mind… I looked back to remember what happened with Meili. As far as I can tell she was rescued/captured by Frederica in episode 48, very briefly shown passed out in episode 49, and that was the last of her. There are a couple of Break-Time episodes with Elsa and Meili talking, and one with Meili looking at the burnt ruins of Roswaal’s estate. Perhaps there was dialog afterwards that explained it later, but I think not.

    I’ve been looking through the wikis, trying not to spoil myself too much (though I ended up spoiling myself on the mom part a little bit, because of the way character wikis are laid out). To avoid being spoiled, it’s probably better to just stick to the Arc 1-5 story recaps and avoid character wikis altogether. The way the anime portrayed Subaru’s and Meili’s interaction made me think that I was supposed to know more, but I think most of the details around Meili – including events that happened in season 2 – are supposed to be vague at this point and we’ll get more details now that she’s part of the cast again. There was a 1-year gap between season 2 and season 3, so perhaps we’re to conclude that some development with Meili happened during that time.

    It would be pretty crazy if the story gives no explanation as to why Subaru can trust Meili now.



  • From the title I thought this was going to be about making hats for magicians. I love the world building (A+ so far, though the idea of being able to keep magic secret is little hard to accept. I doubt that the series will focus on that so I think that I can lock in going forward.) and the fascination with the magic system (B to A+, depending on how well it explains advanced magic). The pacing so far is great: fast but doesn’t feel rushed. I suspect that this will be my favorite show of the season.

    I went back to look at the easy-to-see magic circles. It seems that there is a wide variety of sigils. The signs around the sigils seem to have less variety. And there seems to be some variations on the enclosing circles. The floating carriage and the forbidden spell appear to have 2-levels of nested magic circles. If this was a re-incarnation power-fantasy show, the protagonist would probably immediately aim to create 3±levels of nested magic circles… but judging from the forbidden spell, 3-levels might have the potential to instantly destroy cities.

    How the magic circles function with stone formations is a little bit of a mystery for now, I guess you could just say that there’s durable special ink (or whatever the ink’s made of) in the cracks.


  • A developer submitted a PR code change for systemd userdb.

    My proposals (that’s really what PRs are) are to implement a solution that meets the regulatory requirements in several jurisdictions by providing a way to store a self-reported birthdate locally on the machine. These laws also require that this date is collected during account creation (hence why I made PRs against installers) and you can enter any value here, even January 1st, 1900. There is no proof required, no ID scanning, and no external tracking. Nor do I have any desire for that to ever change.

    Apparently the developer is confirmed to be just a regular guy. He thinks it’d be worse if every desktop environment implements their own solution to comply with these laws. He’s against the various laws related to this incident.

    As a fallout for submitting this pull request, he has been extensively harassed. His personal information being repeatedly posted online; his information used to sign up to a lot of sites, groups, churches, car dealerships, ordering food for him; threats of murder; regular textual harassment.