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

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

  • lyamc
    replied
    I got the Intel Xe Driver running on my A770, in case anyone wants to take it for a spin, here's how I did it (instructions for Arch):

    Code:
    paru -Syu linux-firmware-git linux-drm-xe-next-git linux-drm-xe-next-headers-git
    Once installed, you'll need to copy the firmware folder:

    Code:
    sudo cp -r /lib/firmware/i915 /lib/firmware/xe
    Code:
    paru -G mesa-git rust-bindgen; cd mesa-git; nano PKGBUILD
    or, if you've already installed it once before
    Code:
    cd ~/.cache/paru/clone/mesa-git/; nano PKGBUILD
    I have the following build(), but you just have to add the intel specific things. I enabled lto and added rusticl in addition to the intel stuff:

    Code:
    build () {
      meson setup mesa _build \
         -D b_ndebug=true \
         -D b_lto=true \
         -D platforms=x11,wayland \
         -D gallium-drivers=r300,r600,radeonsi,nouveau,virgl,svga,swrast,i915,iris,crocus,zink,d3d12 \
         -D vulkan-drivers=amd,intel,swrast,virtio,intel_hasvk,microsoft-experimental \
         -D vulkan-layers=device-select,overlay,intel-nullhw \
         -D dri3=enabled \
         -D egl=enabled \
         -D gallium-extra-hud=true \
         -D gallium-nine=true \
         -D gallium-omx=bellagio \
         -D gallium-opencl=disabled \
         -D gallium-rusticl=true \
         -D gallium-va=enabled \
         -D gallium-vdpau=enabled \
         -D gallium-xa=enabled \
         -D gbm=enabled \
         -D gles1=disabled \
         -D gles2=enabled \
         -D glvnd=true \
         -D glx=dri \
         -D libunwind=enabled \
         -D llvm=enabled \
         -D rust_std=2021 \
         -D lmsensors=enabled \
         -D intel-clc=enabled \
         -D intel-xe-kmd=enabled \
         -D osmesa=true \
         -D opencl-spirv=true \
         -D shared-glapi=enabled \
         -D microsoft-clc=disabled \
         -D valgrind=disabled \
         -D tools=[] \
         -D zstd=enabled \
         -D video-codecs=vc1dec,h264dec,h264enc,h265dec,h265enc,av1dec,av1enc \
         -D buildtype=plain \
         --wrap-mode=nofallback \
         -D prefix=/usr \
         -D sysconfdir=/etc
    
       meson configure --no-pager _build
    
       ninja $NINJAFLAGS -C _build
    }
    
    ​
    You'll also want to change
    Code:
    rmdir
    to
    Code:
    rm -rf
    the post-install script that does the rmdir.

    Build and install the the modified mesa-git. the "-f" in -sif is needed to rebuild the pkg.zst if it already exists

    Code:
    makepkg -sif
    Blacklist the i915 driver

    Code:
    echo "blacklist i915" | sudo tee /etc/modprobe.d/xe.conf
    And reboot into the new kernel.

    To revert, all that should be needed is to
    Code:
    sudo rm /etc/modprobe.d/xe.conf
    followed by a reboot
    Last edited by lyamc; 21 January 2024, 01:30 AM.

    Leave a comment:


  • qarium
    replied
    Originally posted by Quackdoc View Post
    any desktop oriented distro that cannot manage to have working support when the card is released, when other distros do, is IMO a bad distro. now to be fair, intel did a pretty bad job with dkms support, they failed to have a DKMS package for the current LTS. that being said, ordinary desktop use IMO shouldnt be using LTS kernels. so yes, intel did do a bad job, but the current linux stable at the time had everything working but media accel, and even that worked when paired with dkms and the appropriate kernel
    and you expect my old mother wo is already in pension to know this?

    it works now good enough... but if i had bought a amd GPU there would had be no problem at all.

    Leave a comment:


  • darkbasic
    replied
    Originally posted by WannaBeOCer View Post

    Why do you think Intel wouldn’t follow?
    Because their first gen cards suck and their drivers are even worse? Shouldn't they give you at least ONE reason to buy them?
    Also Intel already had SR-IOV in some of their integrated gpus.

    Leave a comment:


  • Quackdoc
    replied
    Originally posted by syrjala View Post

    This is more or less my current unload script:
    Code:
    grep dummy /sys/class/vtconsole/vtcon0/name > /dev/null && echo 1 > /sys/class/vtconsole/vtcon0/bind
    grep dummy /sys/class/vtconsole/vtcon1/name > /dev/null && echo 1 > /sys/class/vtconsole/vtcon1/bind
    grep frame /sys/class/vtconsole/vtcon0/name > /dev/null && echo 0 > /sys/class/vtconsole/vtcon0/bind
    grep frame /sys/class/vtconsole/vtcon1/name > /dev/null && echo 0 > /sys/class/vtconsole/vtcon1/bind
    rmmod snd_sof_pci_intel_tgl
    rmmod snd_hda_intel
    rmmod intel_ips
    rmmod i915
    yeah this isn't working for me, I suppose this could be a zen kernel issue since im on arch I suppose I wanted to test out xe driver perf anyways anyways so ill go ahead and test on that. interestinly the command just hangs, dmesg doesn't log anything, lspci shows i915 still in control of the gpu, the gpu becomes useless though, dri_prime falls back to my rx580 and vulkan just errors out, I tried to modprobe i915 out of curiosity and got device or resource busy.

    ill try linux git and the xe kernels, if both have an issue ill report to i915 I suppose

    Leave a comment:


  • WannaBeOCer
    replied
    Originally posted by darkbasic View Post

    It works, but without 3D acceleration: SR-IOV is not supported on Arc.
    GPU pass through works for VMs. Just like AMD SR-IOV is limited to their server GPUs. Their server GPUs are cheaper than their competitors and don’t have licensing cost.

    AMD/Nvidia have been segregating their GPUs via firmware for years. Why do you think Intel wouldn’t follow? At least Intel’s affordable Flex GPUs support SR-IOV while AMD only has three GPUs I can think of and they’re expensive or power hungry or no longer in production. While Nvidia’s are more affordable but they have expensive licensing cost.

    Leave a comment:


  • syrjala
    replied
    Originally posted by Quackdoc View Post

    unloading i915 when DG2 sadly doesn't work for me. do you have a script or any other prep you do to unload the module?
    This is more or less my current unload script:
    Code:
    grep dummy /sys/class/vtconsole/vtcon0/name > /dev/null && echo 1 > /sys/class/vtconsole/vtcon0/bind
    grep dummy /sys/class/vtconsole/vtcon1/name > /dev/null && echo 1 > /sys/class/vtconsole/vtcon1/bind
    grep frame /sys/class/vtconsole/vtcon0/name > /dev/null && echo 0 > /sys/class/vtconsole/vtcon0/bind
    grep frame /sys/class/vtconsole/vtcon1/name > /dev/null && echo 0 > /sys/class/vtconsole/vtcon1/bind
    rmmod snd_sof_pci_intel_tgl
    rmmod snd_hda_intel
    rmmod intel_ips
    rmmod i915

    Leave a comment:


  • Quackdoc
    replied
    Originally posted by darkbasic View Post

    It works, but without 3D acceleration: SR-IOV is not supported on Arc.
    oh you mean SR-IOV, no idea if this is a hardware or software limitation, but VFIO works fine.

    Leave a comment:


  • darkbasic
    replied
    Originally posted by Quackdoc View Post

    it doesn't work in a VM? which OS? I had it working inside of a linux VM perfectly fine
    It works, but without 3D acceleration: SR-IOV is not supported on Arc.

    Leave a comment:


  • Quackdoc
    replied
    Originally posted by qarium View Post

    it works now in fedora 38. and in fedora 37 my mother worked 2-3 month in 1024x800 pixels so it was not a big damange.
    i really don't get why you claim FEdora is "shit"



    fine. i will watch the situation closely in the future. for my mother the old GPU was death and the intel arc a380 was the cheapest one to repleace it. for the desktop work she does it works perfect she does not have high standards.



    my mother is not affected by this. but honestly to read about stuff like that gives me a bad taste.

    its a bit like AMD ROCm HIP they claim my vega64 is supported and they claim Blender3D supports ROCm HIP
    but everytime i check blender on my fedora 38 it does not work and blender claims there is no supported device.
    and yes i have ROCm/HIP installed.

    thats the point intel and AMD in my point of view are not in competition because they both only have one enemy: Nvidia....

    Nvidia/CUDA dominate the maket and Intel and AMD would be better of working together to fix this monopole.
    any desktop oriented distro that cannot manage to have working support when the card is released, when other distros do, is IMO a bad distro. now to be fair, intel did a pretty bad job with dkms support, they failed to have a DKMS package for the current LTS. that being said, ordinary desktop use IMO shouldnt be using LTS kernels. so yes, intel did do a bad job, but the current linux stable at the time had everything working but media accel, and even that worked when paired with dkms and the appropriate kernel

    Leave a comment:


  • qarium
    replied
    Originally posted by Quackdoc View Post
    dont blame intel for your shitty distro's issues.
    it works now in fedora 38. and in fedora 37 my mother worked 2-3 month in 1024x800 pixels so it was not a big damange.
    i really don't get why you claim FEdora is "shit"

    Originally posted by Quackdoc View Post
    ubuntu rhel and sles had decent day one support. Arch wasn't bad, but the media driver didn't work out of box on kernel so another user and I were figuring out how to get it going, cheers to kkartaltepe for the patched ubuntu kernel pkgbuild. DG2 has honestly had quite good support, things have obviously been rocky, but running linux drm tip and mesa-git, I often find noticable improvements.
    fine. i will watch the situation closely in the future. for my mother the old GPU was death and the intel arc a380 was the cheapest one to repleace it. for the desktop work she does it works perfect she does not have high standards.

    Originally posted by Quackdoc View Post
    the only major gripe I have now is this specifc issue, which it's not too late for them to walk back on. one of the devs in the repo seemingly didn't understand the importance of VM_BIND and is going back to investigate it. I don't care which kernel driver it is so long as it's the complete package. assuming they find VM_BIND to indeed be necessary, I am still willing to put faith that either HUC will be added to XE, or VM_BIND to i915. which ever is the least effort and intrusive.
    my mother is not affected by this. but honestly to read about stuff like that gives me a bad taste.

    its a bit like AMD ROCm HIP they claim my vega64 is supported and they claim Blender3D supports ROCm HIP
    but everytime i check blender on my fedora 38 it does not work and blender claims there is no supported device.
    and yes i have ROCm/HIP installed.

    thats the point intel and AMD in my point of view are not in competition because they both only have one enemy: Nvidia....

    Nvidia/CUDA dominate the maket and Intel and AMD would be better of working together to fix this monopole.

    Leave a comment:

Working...
X