[Bug 789472] vaapih264enc bitrate target not respected in low-power mode

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=789472

--- Comment #8 from Florent Thiéry <florent.thiery at ubicast.eu> ---
I do see this, but seems unrelated:

# dmesg | grep i915 | grep loading
[    2.316605] [drm] Finished loading i915/skl_dmc_ver1_26.bin (v1.26)

I'm running 4.9.66-1-lts, is that even supported ? 

I tried this:
# cat /etc/modprobe.d/i915.conf 
enable_guc_loading=1 enable_guc_submission=1

I do have a recent linux-firmware: 20171123.90436ce-1
# pacman -Ql linux-firmware | grep skl
linux-firmware /usr/lib/firmware/i915/skl_dmc_ver1.bin
linux-firmware /usr/lib/firmware/i915/skl_dmc_ver1_23.bin
linux-firmware /usr/lib/firmware/i915/skl_dmc_ver1_26.bin
linux-firmware /usr/lib/firmware/i915/skl_guc_ver1.bin
linux-firmware /usr/lib/firmware/i915/skl_guc_ver4.bin
linux-firmware /usr/lib/firmware/i915/skl_guc_ver6.bin
linux-firmware /usr/lib/firmware/i915/skl_guc_ver6_1.bin
linux-firmware /usr/lib/firmware/i915/skl_guc_ver9_33.bin
linux-firmware /usr/lib/firmware/i915/skl_huc_ver01_07_1398.bin

But no joy:

# cat /sys/kernel/debug/dri/0/i915_huc_load_status
cat: /sys/kernel/debug/dri/0/i915_huc_load_status: No such file or directory

# cat /sys/kernel/debug/dri/0/i915_guc_load_status
GuC firmware status:
    path: i915/skl_guc_ver6_1.bin
    fetch: NONE
    load: NONE
    version wanted: 6.1
    version found: 0.0
    header: offset is 0; size = 0
    uCode: offset is 0; size = 0
    RSA: offset is 0; size = 0

GuC status 0x00000001:
    Bootrom status = 0x0
    uKernel status = 0x0
    MIA Core status = 0x0

Scratch registers:
     0:     0x0
     1:     0x0
     2:     0x0
     3:     0x0
     4:     0x0
     5:     0x0
     6:     0x0
     7:     0x0
     8:     0x0
     9:     0x0
    10:     0x0
    11:     0x0
    12:     0x0
    13:     0x0
    14:     0x0
    15:     0x0

Looks like a very recent kernel is necessary.

What happens if i don't have the updated HuC firmware loaded ? What is the rate
control then ?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.