#4153 [Other] setup: recognize the Instinct MI50 / MI60 / Radeon VII (gfx906) as a supported card
closed · @ken2425pm · 0 コメント · GitHub で見る
Setup & installAMD / HIPDocumentationWindows
本文
Replaces the same-numbered closed PR (0.2.0-beta tracker reset; its /reopen check passed but GitHub would not reopen the closed PR after the branch update - new PR per the check bot's guidance). Problem and result: on a gfx906 box, setup says "not supported", and pushed past that the ROCm wheel lookup dies in a KeyError (AMD's wheels hold 7.x families only; gfx906 runs from a source build on a system ROCm 6.x). After the change setup lists the card, and the wheel path fails with the build instruction instead of the KeyError. Related discussion: #2883 (gfx906 community validation — reopened by the bot with a maintainer pick-up promised); the closed #3080 of the same content (0.2.0-beta tracker reset). Approach: `AMD_ARCHS` / `AMD_NAMES` / `AMD_CARDS` gain gfx906, pointing at the gfx906 source-build section of `docs/AMD_HIP.md`; `rocm_root()` fails for archs without a wheel index instead of raising KeyError. No builder branch — setup does not drive a gfx906 build, it names the path. No other card's route changes; the wheel-driven default path is untouched. Validation: - Passed: `python tools/test_setup_amd.py` on this checkout (v0.2.6): 51 of 52 tests pass, including the new no-wheels exception cases (`gfx906` is the one supported arch deliberately absent from `ROCM_INDEXES`, and `amd_problem` stays quiet for it). - Failed: `test_setup_points_windows_gfx12_to_the_entry` — pre-existing: it also fails on the pristine v0.2.6 tag (`Windows AMD: the driver resets` is absent from `docs/TROUBLESHOOTING.md` there), untouched by this change. - Not run: a live setup run against the hardware with this patch (the card on this box was set up by hand, per `docs/ROCm_6_3_3.md`). Limits: MI50 is validated on hardware (2x, system ROCm 6.3.3, the docs PR); MI60 is recognized by arch only, not run here.
関連リンク
インストール・モデル・リリースへのサイト内リンク。