Hello everyone…I’m getting these integrity and confit errors during startup. Nothing seems broken. Does anyone know a fix or should i just ignore? Thanks!

  • voidMainVoid@lemmy.world
    14·
    1 year ago

    As a rule of thumb, if my computer is working without any problems, I’ll just ignore warnings and errors that show up during boot or shutdown.

  • darcmage@lemm.eeEnglish
    12·
    1 year ago

    Did a search for ubuntu “integrity: problem loading x.509 certificate” and the first result indicates out of date bios certificates needed for secure boot on older laptops. Disabling secure boot seems to be the suggested fix.

    • med@sh.itjust.works
      8·
      1 year ago

      You might check your BIOS clock time too, if the certs are ‘expired’, it might be the future, or more likely, the past. Certs have validity timers that specify start and end.

      It’s more likely that your BIOS is just old, and you’ll have to keep secure boot disabled from now on.

    • Another_username@lemmy.worldOP
      2·
      1 year ago

      I did try disabling secure boot and the errors are still there…just double checked it. My machine is new so I wouldn’t thing âge is the problem.

  • Quereller@lemmy.one
    9·
    1 year ago

    The amd_gpio line is a bug to ignore, the message has the wrong priority and should only be written to the log file.

  • atzanteol@sh.itjust.works
    7·
    1 year ago

    Kernel boot logs aren’t well disciplined to be careful about what is an error or not. Sometimes it’s just checking for the existence of hardware and reports the error it gets if it doesn’t exist.

    If things are working I wouldn’t worry.

  • MrAlternateTape@lemm.ee
    7·
    1 year ago

    As far as I know, other distributions just don’t show these errors, but Ubuntu choose to show them.

    Most of them are just due too a BIOS implementation that is not entirely up to standards, from what I understand. It seems some manufacturers have chosen to make their system easier to use with Windows instead of strictly enforcing standards.

    I just ignore the errors. As long as everything works properly, I feel fine with that.

    • merthyr1831@lemmy.world
      1·
      11 months ago

      yup. and it’s usually on laptops that run less standard bios setups that aren’t easily flashed anyway

  • cbarrick@lemmy.worldEnglish
    52·
    1 year ago

    X.509 certs are commonly used in TLS/HTTPS.

    Why is one needed in your boot process?

    Is your drive encrypted?

      • cbarrick@lemmy.worldEnglish
        21·
        1 year ago

        Did you try to set up that container to serve HTTPS?

        It sounds like you have some service configured to serve HTTPS, and it’s having trouble starting because the cert is broken.

        Only that particular service will be broken. The rest of the system is fine.

        Check systemctl status --failed for more info.

        Edit: I’m only talking about the X.509 error. The AMD error is probably related to your hardware.

        • Another_username@lemmy.worldOP
          1·
          11 months ago

          I was setting up the containers to fix a problem when using wine, but found a different solution. I checked the system status. 0 units failed and x.509 isn’t mentioned

  • merthyr1831@lemmy.world
    2·
    11 months ago

    It’s a thing with certain laptops, where their secure boot certs are outdated or something. Not really anything you can do to fix, but it doesnt mean anything in practice - I never had issues with it after running linux across multiple distros about a year on my Acer nitro 5.

    only thing you might have issues with is using secure boot in certain distros but if you don’t have problems then no need to worry