# Furiosa-smi info command error

**URL:** <https://forums.furiosa.ai/t/furiosa-smi-info-command-error/324>\
**Category:** 일반\
**Created:** [August 5, 2025, 8:24am UTC](https://forums.furiosa.ai/t/furiosa-smi-info-command-error/324 "2025-08-05T08:24:58Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![taek2](https://avatars.discourse-cdn.com/v4/letter/t/9e8a1a/32.png) [@taek2](https://forums.furiosa.ai/u/taek2)\
**Post date:** [August 5, 2025, 8:24am UTC](https://forums.furiosa.ai/t/furiosa-smi-info-command-error/324/1 "2025-08-05T08:24:58Z")

</div>

Hello FuriosaAI Support Team,

I would like to report a bug regarding the `furiosa-smi info` command after updating to SDK 2025.3.0. (I am using Renegade resources, which have been provided to me in the form of a container instance.)

After a recent firmware and SDK update to version 2025.3.0, most `furiosa-smi` commands now work correctly, but `furiosa-smi info` specifically fails with an `Unexpected value` error related to the device governor.

When I run the `furiosa-smi info` command, it fails immediately. However, other commands like `furiosa-smi status` now work as expected after the update.

### Additional Context:

This is a significant improvement from the previous SDK version. For context:

- **Before the update:** My NPU core numbering did not start from `npu0`. Most of `furiosa-smi` commands (like `info`, `status`, `topo`) would fail. Inference commands only worked if I explicitly specified a device, such as `--devices "npu:2"`.

- **After the update:** The core numbering issue seems to be resolved. Inference commands now work even with `npu:0`, and commands like `furiosa-smi status` function correctly.

The `furiosa-smi info` command is the only remaining issue. It seems the `furiosa-smi` software has not been updated to recognize the new `simple_ondemand` governor value, which is likely being reported by the new firmware.

Could you please look into this issue?

Thank you.

 ![image](https://canada1.discourse-cdn.com/flex031/uploads/furiosa_ai/original/1X/67ec461e5d27843dedcaef5d4bf98c1957b95a31.png)

```auto
elicer@160e589f91b9:~$ apt list --installed | grep furiosa

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.     

furiosa-bench/now 0.10.3-3 amd64 [installed,local]
furiosa-compiler/jammy,now 2025.2.0-3 amd64 [installed,upgradable to: 2025.3.0-3]   
furiosa-driver-rngd/jammy,now 2025.3.0-3 amd64 [installed]
furiosa-firmware-image-rngd/jammy,now 2025.3.0 amd64 [installed]
furiosa-firmware-tools-rngd/jammy,now 2025.3.0-3 amd64 [installed]
furiosa-libcompiler/now 0.10.1-3 amd64 [installed,local]
furiosa-libhal-warboy/now 0.12.0-3 amd64 [installed,local]
furiosa-libnux/now 0.10.1-3 amd64 [installed,local]
furiosa-libsmi/jammy,now 2025.3.0-3 amd64 [installed,automatic]
furiosa-mlperf-resources/jammy,now 5.0.0 amd64 [installed,automatic]
furiosa-mlperf/jammy,now 2025.2.0-3 amd64 [installed]
furiosa-pert-rngd/jammy,now 2025.3.0-3 amd64 [installed]
furiosa-smi/jammy,now 2025.3.0-3 amd64 [installed]
furiosa-toolkit/now 0.11.0-3 amd64 [installed,local]

----------------------------------------------------------------
elicer@160e589f91b9:~$ pip list | grep furiosa

furiosa-llm 2025.3.0
furiosa-llm-models 2025.3.0
furiosa-model-compressor 2025.3.0
furiosa-model-compressor-impl 2025.3.0
furiosa-models-lang 2025.3.0
furiosa-native-compiler 2025.3.0
furiosa-native-llm-common 2025.3.0
furiosa-native-runtime 2025.3.0
furiosa-smi-py 2025.3.0
furiosa-torch-ext 2025.3.0

```

---

<div class="post-metadata">

**Author:** ![jongwook.kim](https://avatars.discourse-cdn.com/v4/letter/j/b5a626/32.png) [@jongwook.kim](https://forums.furiosa.ai/u/jongwook.kim)\
**Post date:** [August 5, 2025, 3:05pm UTC](https://forums.furiosa.ai/t/furiosa-smi-info-command-error/324/2 "2025-08-05T15:05:54Z")

</div>

> [@taek2](#):
>
> - **After the update:** The core numbering issue seems to be resolved. Inference commands now work even with `npu:0`, and commands like `furiosa-smi status` function correctly.

First, we need to verify the source of the environment you’re using.

For firmware and drivers, updates are not possible in the instance environment, so you’ll need to contact the vendor that provided the instance. This error is related to this issue.