Re: Issue with i915 PSR module option
Hi Reco, Didier,
28 mars 2020 à 17:55 de recoverym4n@enotuniq.net:
> Probably because your /etc/modprobe.d/i915.conf did not get included in
> initrd. "i915" usually gets loaded before root filesystem is loaded, so
> your file does not get any effect.
> Execute "update-initramfs -k all -u", check the presence of i915.conf in
> initrd (lsinitrams), reboot and check it one more time.
>
$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-5.4.0-0.bpo.2-amd64
W: Possible missing firmware /lib/firmware/i915/icl_dmc_ver1_07.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_dmc_ver2_04.bin for module i915
W: Possible missing firmware /lib/firmware/i915/bxt_huc_ver01_8_2893.bin for module i915
$ lsinitramfs /boot/initrd.img-5.4.0-0.bpo.2-amd64 | grep -i i915
etc/modprobe.d/i915.conf
usr/lib/firmware/i915
usr/lib/firmware/i915/bxt_dmc_ver1_07.bin
usr/lib/firmware/i915/bxt_guc_33.0.0.bin
usr/lib/firmware/i915/cnl_dmc_ver1_07.bin
usr/lib/firmware/i915/glk_dmc_ver1_04.bin
usr/lib/firmware/i915/glk_guc_33.0.0.bin
usr/lib/firmware/i915/glk_huc_ver03_01_2893.bin
usr/lib/firmware/i915/icl_guc_33.0.0.bin
usr/lib/firmware/i915/icl_huc_ver8_4_3238.bin
usr/lib/firmware/i915/kbl_dmc_ver1_04.bin
usr/lib/firmware/i915/kbl_guc_33.0.0.bin
usr/lib/firmware/i915/kbl_huc_ver02_00_1810.bin
usr/lib/firmware/i915/skl_dmc_ver1_27.bin
usr/lib/firmware/i915/skl_guc_33.0.0.bin
usr/lib/firmware/i915/skl_huc_ver01_07_1398.bin
usr/lib/modules/5.4.0-0.bpo.2-amd64/kernel/drivers/gpu/drm/i915
usr/lib/modules/5.4.0-0.bpo.2-amd64/kernel/drivers/gpu/drm/i915/i915.ko
[reboot]
$ sudo cat /sys/module/i915/parameters/enable_psr
0
=> Thank you :)
I suppose I'm expected now to download my potential missing firmwares for module i915 from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915 and move them to /lib/firmware/i915?
Why aren't they distributed via traditional Debian packages?
28 mars 2020 à 18:00 de didier.gaumet@gmail.com:
> and enable_psr must be set to 1, not 0
>
I set it up to 0 because I have frequent err/3 on journalctl like the following:
kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=38584 end=38585) time 167 us, min 1073, max 1079, scanline start 1070, end 1080
Some Internet resources seem to indicate PSR could be involved.
Do you think I'm gonna have more issues with PSR deactivated than left at value -1?If you have any advice, feel free :)
Thank you.Best regards,
l0f4r0
Reply to: