Hi,
I want to change the graphics driver from i915 to xe. I want to add the following options:
i915.force_probe=!7d55 xe.force_probe=7d55
When trying to use Yast2 I get the following error message:
Cannot update bootloader:
Command `[["/usr/bin/sdbootutil", "update-all-entries"]]`.
Error output: Garbage after device path end, ignoring.
Garbage after device path end, ignoring.
Garbage after device path end, ignoring.
Garbage after device path end, ignoring.
WARNING:esys:src/tss2-esys/api/Esys_PolicyOR.c:286:Esys_PolicyOR_Finish() Received TPM Error
ERROR:esys:src/tss2-esys/api/Esys_PolicyOR.c:100:Esys_PolicyOR() Esys Finish ErrorCode (0x000001c4)
None of the alternative values for PCR 9 encoded in policy match the current TPM state. Either the system has been tempered with or the provided policy is incorrect.
What is the correct way for changing the driver?
Best regards
Kay
@guckuck Use update-bootloader command (note the \);
update-bootloader --add-option i915.force_probe=\!7d55
update-bootloader --add-option xe.force_probe=7d55
update-bootloader --config
Depending on your setup you might need to add some variables to an /etc/environment file.
Thank you. The system now uses xe.
Are there any information what to add in /etc/environment? On my system there is no /etc/environment.
Sometimes the system stutters a bit.
Best regards
Kay
@guckuck Hi, if everything your using is working as expected, should be fine. When you say stuttering, in general or when running a specific application?
What is your setup, can you show the output from inxi -GSaz
In general, the mouse was a little bit stuttering. I temporally switch back to i915.
This is the output of inxi:
> inxi -GSaz ~@localhost.localdomain
System:
Kernel: 6.19.3-1-default arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
clocksource: tsc avail: acpi_pm
parameters: BOOT_IMAGE=/opensuse-tumbleweed/6.19.3-1-default/linux-70c85d8b4c51a755cefb1b7c402d54ed5e1ca0e5
splash=silent resume=/dev/system/swap quiet security=selinux selinux=1
mitigations=auto root=UUID=5e659972-3d04-4e3d-8671-533b8fdc3235
rootflags=subvol=@/.snapshots/1/snapshot
Desktop: KDE Plasma v: 6.6.0 tk: Qt v: N/A info: frameworks v: 6.23.0
wm: kwin_wayland with: krunner tools: avail: xscreensaver vt: 3 dm: SDDM
Distro: openSUSE Tumbleweed 20260226
Graphics:
Device-1: Intel Meteor Lake-P [Intel Arc Graphics] vendor: ASUSTeK
driver: i915 v: kernel alternate: xe arch: Xe-LPG process: Intel 4 (7nm+)
built: 2023+ ports: active: eDP-1 empty: DP-1,DP-2,HDMI-A-1
bus-ID: 0000:00:02.0 chip-ID: 8086:7d55 class-ID: 0300
Device-2: Shinetech USB2.0 FHD UVC WebCam driver: uvcvideo type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-9:2 chip-ID: 3277:0055
class-ID: fe01 serial: <filter>
Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9
compositor: kwin_wayland driver: X: loaded: modesetting unloaded: vesa
alternate: fbdev,intel dri: iris gpu: i915 display-ID: 0
Monitor-1: eDP-1 model: Samsung 0x419d built: 2022 res: mode: 2880x1800
hz: 120 scale: 175% (1.75) to: 1646x1029 dpi: 242 gamma: 1.2
size: 302x189mm (11.89x7.44") diag: 356mm (14") ratio: 16:10
modes: 2880x1800
API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris wayland:
drv: iris x11: drv: iris
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 26.0.1 glx-v: 1.4
direct-render: yes renderer: Mesa Intel Arc Graphics (MTL)
device-ID: 8086:7d55 memory: 29.99 GiB unified: yes display-ID: :1.0
API: Vulkan v: 1.4.341 layers: 5 device: 0 type: integrated-gpu name: Intel
Arc Graphics (MTL) driver: mesa intel v: 26.0.1 device-ID: 8086:7d55
surfaces: N/A device: 1 type: cpu name: llvmpipe (LLVM 21.1.8 256 bits)
driver: mesa llvmpipe v: 26.0.1 (LLVM 21.1.8) device-ID: 10005:0000
surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor wl: wayland-info
x11: xdpyinfo, xprop, xrandr
@guckuck that could be a desktop environment issue, there are a couple of Forum threads about mouse movement… I usually test (as in switch to Xe) on a new Mesa release. The support is getting better for sure.
The only other thing I would suggest is adding intel_iommu=on for some additional security, see the output from fwupdmgr security I also run zram for swap as this is automatically encrypted…