Intel's Experimental Xe Driver For Linux Lacking HuC Media Support For DG2/Alchenist

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • abott
    Senior Member
    • Apr 2018
    • 271

    #31
    Originally posted by Sonadow View Post

    You paid for a card that was released for the fucking i915 driver.

    And anybody who is not paid $10000 an hour has no excuse talking about how they cannot take 5 minutes out of their lives to reboot a computer.
    They're supporting this generation in Xe sans paid features. Get out of here with that crap. I will literally not see any new features into the future, to boot. You are actually idiotic to say it shouldn't be supported. It's BRAND NEW.

    You can say what you want, I know MY money will go back to AMD. Their hardware wasn't even worth $350 if it isn't completely support for MULTIPLE YEARS, MINIMUM.
    Last edited by abott; 10 May 2023, 12:49 AM.

    Comment

    • Quackdoc
      Senior Member
      • Oct 2020
      • 5114

      #32
      Originally posted by Sonadow View Post

      h264_vaapi

      Problem solved.
      A) vaapi is worse in efficiency:quality then qsv
      B) hevc is still much prefered and even necessary to get a good experience for streaming when bandwidth limited like myself, as well as a massive boon when it comes to recording videos. only a couple problems were solved. there are still many to go

      Comment

      • nyanmisaka
        Junior Member
        • Dec 2020
        • 49

        #33
        Originally posted by Sonadow View Post

        h264_vaapi

        Problem solved.
        It's not just that. The HuC firmware is mandatory for doing the video encoding on DG2, including QuickSync/VA-API H.264, HEVC, VP9 and AV1 fixed-function encoders. So no Huc support means no hardware encoding support on Arc.

        Comment

        • Quackdoc
          Senior Member
          • Oct 2020
          • 5114

          #34
          Originally posted by nyanmisaka View Post

          It's not just that. The HuC firmware is mandatory for doing the video encoding on DG2, including QuickSync/VA-API H.264, HEVC, VP9 and AV1 fixed-function encoders. So no Huc support means no hardware encoding support on Arc.
          I've seen at least two different people reporting of av1 qsv encoding working with huc forcibly disabled. I believe it's [i915.enable_guc=1]? I plan on personally testing it, but even if this is the case, it's still not a full solution. I personally don't massively care about XE or i915 if it's a complete package. I realize xe will be the better driver, so obviously I would prefer HUC in XE, but if i915 becomes a complete package, that would still be fine with me.

          at the very least as I commented earlier, it looks like one of the devs is looking into the VM_BIND necessity. I only hope that this leads to A) intel realizing VM_BIND is a necessity and B) them deciding the best way to get it is through the xe driver and not the i915 driver. I do think intel still wants to do right by the community, just had a lapse in judgement due to lacking info, Im not going to tell anyone to get rid of their cards yet, but that doesn't mean im going to keep reccomending them for now. that's definitely on pause.

          Comment

          • TemplarGR
            Senior Member
            • Dec 2009
            • 1627

            #35
            Lots of vitriol from obvious AMD fanbois who never owned any intel gpu hardware in their lives, let alone an ARC dgpu, and it shows (despite their claims, anyone can claim anything on the internet)....

            Yes, it is a nasty move by Intel to not provide support for every hardware feature on the new experimental driver. I agree. Is it a first in the industry? No, AMD takes the cake on unsupported features on Linux historically, or "barely supported" or "semi-supported", yet the amd fanbois pretend only Intel does this.

            Reminds us please about the RoCm and the OpenCL situation on opensource drivers please.... Oh, remind us about gpu encoding/decoding support on opensource drivers too, particularly for older generations, since it is kinda unfair to be so harsh against an experimental driver on brand new dgpus while AMD had decades to perfect their support, and they needed help by Valve and other players to do so....

            Is the experimental Xe driver even out at this point? Are all these supposed "hurt intel customers" who insult passive aggressively all of us who welcomed the competition in the gpu space, using the experimental driver right now, and they needed the video encoding so badly? You don't say?

            Just because something isn't planned for now, doesn't mean it will never be implemented. The focus on the experimental driver is to make it functional for the things most people use their gpus for....

            It is strange that in the past when i used amd hardware, everyone and their dog told me it is ok that i can't do stuff like video encoding with it because everyone prefers software encoding and multicore cpus are fast enough anyway, but apparently today lacking this feature is a deal breaker when it comes to Intel....

            Comment

            • nyanmisaka
              Junior Member
              • Dec 2020
              • 49

              #36
              Originally posted by Quackdoc View Post

              I've seen at least two different people reporting of av1 qsv encoding working with huc forcibly disabled. I believe it's [i915.enable_guc=1]? I plan on personally testing it, but even if this is the case, it's still not a full solution. I personally don't massively care about XE or i915 if it's a complete package. I realize xe will be the better driver, so obviously I would prefer HUC in XE, but if i915 becomes a complete package, that would still be fine with me.

              at the very least as I commented earlier, it looks like one of the devs is looking into the VM_BIND necessity. I only hope that this leads to A) intel realizing VM_BIND is a necessity and B) them deciding the best way to get it is through the xe driver and not the i915 driver. I do think intel still wants to do right by the community, just had a lapse in judgement due to lacking info, Im not going to tell anyone to get rid of their cards yet, but that doesn't mean im going to keep reccomending them for now. that's definitely on pause.
              As per https://github.com/intel/media-drive...nd-limitations

              HuC firmware is necessary for AVC/HEVC/VP9/AV1 low power encoding bitrate control, including CBR, VBR, etc.

              It might "work" but has no rate control such as CBR and VBR, so it's still useless for real world use cases.

              Comment

              • Quackdoc
                Senior Member
                • Oct 2020
                • 5114

                #37
                Originally posted by nyanmisaka View Post

                As per https://github.com/intel/media-drive...nd-limitations

                HuC firmware is necessary for AVC/HEVC/VP9/AV1 low power encoding bitrate control, including CBR, VBR, etc.

                It might "work" but has no rate control such as CBR and VBR, so it's still useless for real world use cases.
                ahh I see, thanks for the update.

                Comment

                • darkbasic
                  Senior Member
                  • Nov 2009
                  • 3088

                  #38
                  Originally posted by Sonadow View Post

                  And how much of your life will a reboot require?

                  5 minutes, tops.

                  Add separate entries to Grub2 to load the kernel with Xe or i915.

                  Play games and do normal computing stuff in Xe. Reboot to i915 when doing video encode.

                  Or do it the other way. Stay in i915 for everything. Reboot to Xe for gaming.
                  Yeah sure, what about recording your own game play? Schrodinger's bootloader where your GPU driver is both i915 and Xe? Maybe that's what Intel developers where thinking about
                  ## VGA ##
                  AMD: X1950XTX, HD3870, HD5870
                  Intel: GMA45, HD3000 (Core i5 2500K)

                  Comment

                  • darkbasic
                    Senior Member
                    • Nov 2009
                    • 3088

                    #39
                    Originally posted by Sonadow View Post

                    You paid for a card that was released for the fucking i915 driver.
                    I would have bought A380 just because of the Xe driver, I cannot use i915 on ppc64. I didn't trust Intel on that because of the lack of VM GPU acceleration (if you play anti-consumer on your fist shitty generation you cannot be trusted) and made the right call. Not going to buy second gen either unless it supports hardware acceleration in VMs.
                    ## VGA ##
                    AMD: X1950XTX, HD3870, HD5870
                    Intel: GMA45, HD3000 (Core i5 2500K)

                    Comment

                    • RejectModernity
                      Senior Member
                      • Dec 2021
                      • 379

                      #40
                      Originally posted by Sonadow View Post

                      And how much of your life will a reboot require?

                      5 minutes, tops.

                      Add separate entries to Grub2 to load the kernel with Xe or i915.

                      Play games and do normal computing stuff in Xe. Reboot to i915 when doing video encode.

                      Or do it the other way. Stay in i915 for everything. Reboot to Xe for gaming.
                      You're delusional, holy

                      Comment

                      Working...
                      X