#6619 [GUI] Regression: default GPU selection for 8060S (gfx1151) changed to R9700 (gfx1201) between 0.2.12 and 0.2.19

open · @Twilight-lxy · 0 Kommentare · Auf GitHub

Setup & installServer & APIAMD / HIPModels & quantsWindows

Beschreibung

### Environment

- **Strata version**: 0.2.19 (regression)
- **Working version**: Strata **0.2.12** with engine **0.1.65**
- **OS**: Windows11
- **iGPU**: AMD Radeon 8060S, `gfx1151` (Strix Halo)(Actually using this GPU in strata)
- **dGPU**: AMD Radeon R9700, `gfx1201` (RDNA 4)(This is GPU0 displayed in the task manager, as the only monitor is connected to it)
- **Engine package**: `0.1.65 windows-x86_64-hip-rdna3` (contains `gfx1100`, `gfx1101`, `gfx1102`, `gfx1151`, but **not** `gfx1201`)

### Description

On a hybrid AMD system with both a Radeon 8060S (`gfx1151`) and a Radeon R9700 (`gfx1201`), the **GUI first-run setup in Strata 0.2.19 selects the R9700 as the default GPU**, whereas **Strata 0.2.12 correctly selects the 8060S** when using the same engine version 0.1.65.

Because the downloaded `hip-rdna3` engine contains `gfx1151` code but not `gfx1201` code, selecting the R9700 causes engine validation to fail. More importantly, even if the user manually imports a correctly downloaded engine package containing `gfx1151`, the GUI still does not allow launching on the 8060S and appears to remain locked to the R9700 selection.

The expected behavior is that the GUI should either default to the 8060S, or at minimum allow the user to manually import the correct engine package and start on the 8060S without being forced onto the R9700.

### Steps to Reproduce

1. Use a Windows machine with both an AMD Radeon 8060S (`gfx1151`) and an AMD Radeon R9700 (`gfx1201`).
2. Install **Strata 0.2.12** and launch for the first time.
   - **Observed**: the GUI correctly defaults to the 8060S (`gfx1151`), and engine **0.1.65** works normally.
3. Clean the installation, then install **Strata 0.2.19** and launch for the first time.
   - **Observed**: the GUI **defaults to the R9700 (`gfx1201`)** instead of the 8060S.
4. Proceed with the guided engine installation or run `strata update`.
   - **Result**: Strata downloads `0.1.65 windows-x86_64-hip-rdna3`, but post-switch validation fails:
     > This build of Strata is for AMD RX 7000 and Ryzen AI Max cards. This computer has an AMD RX 9000 card (gfx1201). Ask for the RX 9000 build.
     > (No engine for this PC was found in `C:\Users\<user>\AppData\Local\Strata\components`: `0.1.65 windows-x86_64-hip` has code for `gfx1100, gfx1101, gfx1102, gfx1151`, this PC's GPU is `gfx1201`.)
5. Manually download and import the correct `hip-rdna3` engine package containing `gfx1151` into the Strata component folder.
   - **Expected**: the GUI should allow starting on the 8060S using the manually imported engine.
   - **Actual**: the GUI still does not start correctly on the 8060S and remains locked to the R9700 selection.

### Expected Behavior

- On first launch in 0.2.19, the GUI should **default to the 8060S (`gfx1151`)** on this hybrid configuration, as 0.2.12 does.
- The user should be able to **manually import a downloaded engine package** that contains `gfx1151` and then start Strata on the 8060S. The GUI should not force the R9700 selection.
- The user should be able to explicitly choose the 8060S. On this platform the 8060S is the preferred device because it provides much higher prompt-processing throughput than the R9700.

### Actual Behavior

- 0.2.19 GUI first-run selection defaults to the **R9700 (`gfx1201`)**.
- This causes engine selection / validation to fail because the downloaded `hip-rdna3` package does not include `gfx1201` code.
- Manually importing the correct engine package containing `gfx1151` does not allow the GUI to start on the 8060S; the selection appears to remain locked to the R9700.

### Regression Note

This is a clear version regression between Strata 0.2.12 and 0.2.19 with the same engine version:

| Strata version | Engine version | First-run GUI default | Result |
|---|---|---|---|
| **0.2.12** | **0.1.65** | **8060S (`gfx1151`)** | ✅ Works normally |
| **0.2.19** | **0.1.65** | **R9700 (`gfx1201`)** | ❌ Engine mismatch; 8060S cannot be used normally |

The change in GUI first-run GPU selection between these versions is the root cause of this regression.

### Possible Root Cause / Related Issues

https://github.com/Niko1221/Strata/issues/5525

### Workaround

- Revert to **Strata 0.2.12** with engine **0.1.65**, which works correctly on this system.
- If 0.2.19 must be used, manually force the 8060S GPU index in the model configuration (identify the correct `gfx1151` device index via `strata-device.exe --list-devices`) as a temporary bypass. This should not be necessary if the GUI correctly allowed manual engine import and GPU selection.

### Additional Context

On this platform, the R9700 operates at **PCIe 4.0 x4**, and its prompt-processing speed is about **600 t/s**, while the 8060S reaches about **1300 t/s**. Therefore the 8060S is the clearly preferred device for this user, and the GUI should not force selection of the slower R9700. The `hip-rdna3` engine package itself is correct for the 8060S because it contains `gfx1151` code; the failure is caused by the GUI choosing the R9700 (`gfx1201`) as the default target in 0.2.19.

Mehr auf der Site

Links zu Install, Modellen, Releases.