Announcement

Collapse
No announcement yet.

Updated and Optimized Ubuntu Free Graphics Drivers

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Originally posted by MastaG View Post
    Hi oibaf

    Is it possible you could update your signing key?
    I'm having trouble checking out your repository on 24.10 because of:

    The following signatures were invalid: 5ABCE68FF4633EA42E219156957D2708A03A4626 (untrusted public key algorithm: rsa1024) The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 93F4D583494746C8​
    How?

    I cannot do anything about it, see https://www.phoronix.com/forums/foru...88#post1472888

    Comment


    • Originally posted by MastaG View Post
      Hi oibaf

      Is it possible you could update your signing key?
      I'm having trouble checking out your repository on 24.10 because of:

      The following signatures were invalid: 5ABCE68FF4633EA42E219156957D2708A03A4626 (untrusted public key algorithm: rsa1024) The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 93F4D583494746C8​
      If you want to ask about it, you can do it here:
      I maintain several PPAs, and often use packaging recipes to build packages from source. When I run `sudo apt update` in Ubuntu 24.04, I get warnings like ``` W: https://ppa.launchpadcontent.net/apandada1/blanket/ubuntu/dists/noble/InRelease: Signature by key 95ACDEBD8BFF99ABE0F26A49A507B2BBA7803E3B uses weak algorithm (rsa1024) W: https://ppa.launchpadcontent.net/apandada1/foliate/ubuntu/dists/noble/InRelease: Signature by key 95ACDEBD8BFF99ABE0F26A49A507B2BBA7803E3B uses weak algorithm (rsa...

      In Ubuntu 24.04, APT will require repositories to be signed using one of the following public key algorithms: RSA with at least 2048-bit keys Ed25519 Ed448 This has been made possible thanks to recent work in GnuPG 2.4 by Werner Koch to allow us to specify a “public key algorithm assertion” in APT when calling the gpgv tool for verifying repositories. As a first stage, warnings will be enabled for such repositories with apt 2.7.13. In a second stage, once all PPAs have been resigned, we will...

      Comment


      • Originally posted by jeff416 View Post
        Hello, I know 20.04 (focal) is no longer supported, but I am stuck with it until next year and I have an obscure issue with monitors going blank and sometimes xrandr showing HDMI output as "disconnected". There is nothing in the logs, even with drm.debug set to 14. The same issue doesn't happen on 22.04 but I can't upgrade yet.

        Is there any way I can build the latest graphics stack from source myself?
        You may want to look into the Kisak PPA which still supports 20.04.

        Comment


        • Originally posted by oibaf View Post

          If you want to ask about it, you can do it here:
          I maintain several PPAs, and often use packaging recipes to build packages from source. When I run `sudo apt update` in Ubuntu 24.04, I get warnings like ``` W: https://ppa.launchpadcontent.net/apandada1/blanket/ubuntu/dists/noble/InRelease: Signature by key 95ACDEBD8BFF99ABE0F26A49A507B2BBA7803E3B uses weak algorithm (rsa1024) W: https://ppa.launchpadcontent.net/apandada1/foliate/ubuntu/dists/noble/InRelease: Signature by key 95ACDEBD8BFF99ABE0F26A49A507B2BBA7803E3B uses weak algorithm (rsa...

          https://discourse.ubuntu.com/t/new-r...in-24-04/42854
          Somebody posted a workaround:
          sudo echo 'APT::Key::Assert-Pubkey-Algo ">=rsa1024";' > /etc/apt/apt.conf.d/99weakkey-warning

          I now have my github actions runner working for Ubuntu 24.10 as well

          Comment


          • Originally posted by oibaf View Post
            23.10/mantic won't be updated anymore. I'll remove the package in some weeks.
            Removed.

            Comment


            • 22.04/jammy won't be updated anymore. I'll remove the package after 24.04.1 is released.

              Comment


              • back to work oibaf ppa, apparently llvm18 cause all troubles in my case



                and corectrl show correctly gpu vram usage

                Last edited by pinguinpc; 21 July 2024, 11:17 AM.

                Comment


                • pinguinpc
                  the ppa is still using llvm17, but I'd like to use 18 soon.
                  What trouble do you mean with llvm18?

                  Comment


                  • Originally posted by oibaf View Post
                    pinguinpc
                    the ppa is still using llvm17, but I'd like to use 18 soon.
                    What trouble do you mean with llvm18?
                    on corectrl dont appear vram usage, value appear frozen and when begins any 3d app crash (related dont find any 3d hardware device in my case)

                    Comment


                    • Originally posted by oibaf View Post
                      22.04/jammy won't be updated anymore. I'll remove the package after 24.04.1 is released.
                      Restored until most recent regressions are fixed.

                      Comment

                      Working...
                      X