intel_ish_ipc: ISH loader "cmd 2 failed 10" on HP OmniBook X Flip 14-fm0xxx (Lunar Lake), no sensors

intel_ish_ipc: ISH loader "cmd 2 failed 10" on HP OmniBook X Flip 14-fm0xxx (Lunar Lake), no sensors

[José Miguel Castellanos Valladolid]

Hello,

On an HP OmniBook X Flip Laptop 14-fm0xxx (Lunar Lake, ISH 8086:a845) the ISH
never starts under Linux, so there is no accelerometer, hinge sensor or
auto-rotation. The 2-in-1 keyboard/touchpad disable at 180 degrees works, but
that is handled outside the ISH.

Kernel: 7.2.12 (Fedora 44), linux-firmware 20261019, BIOS Insyde F.20
(04/27/2026, latest available from the vendor).

DMI:
  sys_vendor     = HP
  product_name   = HP OmniBook X Flip Laptop 14-fm0xxx
  product_family = 103C_5335M8 HP OmniBook X
  product_sku    = B5UJ1UA#ABA

dmesg:
  intel_ish_ipc 0000:00:12.0: ISH loader: load firmware: intel/ish/ish_lnlm.bin
  intel_ish_ipc 0000:00:12.0: ISH loader: cmd 2 failed 10   (three times)

From drivers/hid/intel-ish-hid/ishtp/loader.h, command 2 is LOADER_CMD_START,
so the query and fragment transfer steps succeed and the bootloader refuses to
start the image. I have not been able to confirm what status 10 means.

The vendor-specific lookup finds nothing for this machine. The CRC32 values
are vendor(HP)=12128606, family=604fc7b4, name=e4cc03e5, sku=dc6e7f5f, and
none of the ish_lnlm_* names built from them exist, so the generic
ish_lnlm.bin is loaded. linux-firmware does carry an HP file,
intel/ish/ish_lnlm_12128606_f9751b71.bin (5.8.200.7720_1029), but its second
CRC matches neither this product name nor this SKU.

A complete power-off (not a reboot) and a BIOS check did not change anything.

Questions:
 1. Does status 10 mean the bootloader rejected the image (signature or
    platform mismatch), and is the generic firmware expected to work on
    OEM-customised ISH platforms at all?
 2. Is there a known HP firmware for this SKU/family, or is HP expected to
    submit one to linux-firmware?

I can provide more logs or test patches on this hardware.

Thanks,
José Miguel Castellanos Valladolid

Re: intel_ish_ipc: ISH loader "cmd 2 failed 10" on HP OmniBook X Flip 14-fm0xxx (Lunar Lake), no sensors

[Pandruvada, Srinivas]

Hello,

On Tue, 2026-10-27 at 10:34 -0600, José Miguel Castellanos Valladolid
wrote:
> Hello,
> 
> On an HP OmniBook X Flip Laptop 14-fm0xxx (Lunar Lake, ISH 8086:a845)
> the ISH
> never starts under Linux, so there is no accelerometer, hinge sensor
> or
> auto-rotation. The 2-in-1 keyboard/touchpad disable at 180 degrees
> works, but
> that is handled outside the ISH.
> 
> Kernel: 7.2.12 (Fedora 44), linux-firmware 20261019, BIOS Insyde F.20
> (04/27/2026, latest available from the vendor).
> 
> DMI:
>   sys_vendor     = HP
>   product_name   = HP OmniBook X Flip Laptop 14-fm0xxx
>   product_family = 103C_5335M8 HP OmniBook X
>   product_sku    = B5UJ1UA#ABA
> 
> dmesg:
>   intel_ish_ipc 0000:00:12.0: ISH loader: load firmware:
> intel/ish/ish_lnlm.bin
>   intel_ish_ipc 0000:00:12.0: ISH loader: cmd 2 failed 10   (three
> times)
> 

It is likely that vendor has his own firmware, which needs to be
uploaded to Linux firmware.
If that is the case only HP can upload to Linux firmware.

Thanks,
Srinivas

> From drivers/hid/intel-ish-hid/ishtp/loader.h, command 2 is
> LOADER_CMD_START,
> so the query and fragment transfer steps succeed and the bootloader
> refuses to
> start the image. I have not been able to confirm what status 10
> means.
> 
> The vendor-specific lookup finds nothing for this machine. The CRC32
> values
> are vendor(HP)=12128606, family=604fc7b4, name=e4cc03e5,
> sku=dc6e7f5f, and
> none of the ish_lnlm_* names built from them exist, so the generic
> ish_lnlm.bin is loaded. linux-firmware does carry an HP file,
> intel/ish/ish_lnlm_12128606_f9751b71.bin (5.8.200.7720_1029), but its
> second
> CRC matches neither this product name nor this SKU.
> 
> A complete power-off (not a reboot) and a BIOS check did not change
> anything.
> 
> Questions:
>  1. Does status 10 mean the bootloader rejected the image (signature
> or
>     platform mismatch), and is the generic firmware expected to work
> on
>     OEM-customised ISH platforms at all?
>  2. Is there a known HP firmware for this SKU/family, or is HP
> expected to
>     submit one to linux-firmware?
> 
> I can provide more logs or test patches on this hardware.
> 
> Thanks,
> José Miguel Castellanos Valladolid