Skip to content

update kernel information and add ROCm 7.2 status#151

Merged
th3cavalry merged 7 commits intoth3cavalry:mainfrom
mantkiew:kernel_updates
Feb 16, 2026
Merged

update kernel information and add ROCm 7.2 status#151
th3cavalry merged 7 commits intoth3cavalry:mainfrom
mantkiew:kernel_updates

Conversation

@mantkiew
Copy link
Copy Markdown
Contributor

@mantkiew mantkiew commented Feb 5, 2026

Add documentation of the kernel and ROCm 7.2 status as of Feb 2026.

Copy link
Copy Markdown
Owner

@th3cavalry th3cavalry left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary

Thanks for contributing ROCm 7.2 documentation! The gfx1151 native support info is valuable. However, there are a few issues that should be addressed before merging.


🔴 Request Changes

1. Model Numbers - Please Revert

File: docs/kernel-support.md

The model suffixes indicate RAM configuration, not sequential model numbers:

  • XS99 = 128GB RAM (top config)
  • XS64 = 64GB RAM
  • XS32 = 32GB RAM

XS98/XS96 don't exist in ASUS's product lineup. Please revert to XS99/XS64/XS32.


🟡 Suggestions

2. Add Kernel Availability Note

Most distributions don't ship kernel 6.18+ yet. Consider adding a note that this is currently only available in Arch (testing), CachyOS, and via mainline kernel installation.

3. Future: Update gz302-llm.sh

The gz302-llm.sh module currently sets HSA_OVERRIDE_GFX_VERSION=11.0.0 unconditionally. With ROCm 7.2 supporting gfx1151 natively, a follow-up PR should detect ROCm version and skip the override for 7.2+.


✅ Looks Good

  • ROCm 7.2 native gfx1151 support documentation
  • Kernel 6.18.4+ and linux-firmware 20260108+ requirements
  • --no-dkms flag for mainline kernel installs
  • Ollama incompatibility warning with upstream PR link
  • aptapt-get change

Once the model number is fixed, this is ready to merge. Thanks!

@mantkiew
Copy link
Copy Markdown
Contributor Author

Re: model suffixes. That's interesting! I referred to ASUS Canada https://rog.asus.com/ca-en/laptops/rog-flow/rog-flow-z13-2025/spec/ and they list GZ302EA-XS96 (32Gb) and GZ302EA-XS98 (64Gb) there. However, checking ASUS Global, they list different ones on https://rog.asus.com/laptops-group/allmodels/?items=124783%2C20392 : GZ302EAC-XS99 and GZ302EA-XS98.

I wasn't able to find GZ302EA-XS32 and GZ302EA-XS64 anywhere.

@mantkiew
Copy link
Copy Markdown
Contributor Author

We can check ROCm version

$ cat /opt/rocm/.info/version
7.2.0

or

if [ -f /opt/rocm/.info/version ]; then
    ROCM_VERSION=$(cat /opt/rocm/.info/version)
    echo $ROCM_VERSION 
fi

outputs

7.2.0

@mantkiew
Copy link
Copy Markdown
Contributor Author

mantkiew commented Feb 15, 2026

I see that you've already incorporated most of these changes into main. I updated this branch and resolved conflicts. It's pretty minimal now.

I also changed the display manager output to list all available environments. When Wayland is active on Ubuntu, the x11 checks also return 0. So, these checks are not really exclusive (display_is_x11==0 and display_is_wayland==0 at the same time). To determine which one is actually running

$ echo "$XDG_SESSION_TYPE"
wayland

will return only one or the other.

Copy link
Copy Markdown
Owner

@th3cavalry th3cavalry left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review Update

Thanks for the thorough work and the follow-up discussion!

Model Numbers - Resolved ✅

You were right. I verified on ASUS Canada — the SKUs are:

  • GZ302EA-XS96 (32GB) — CA$2,999
  • GZ302EA-XS98 (64GB) — CA$3,299
  • GZ302EAC-XS99 (128GB) — listed on ASUS Global

I've corrected XS64→XS98 and XS32→XS96 across the entire codebase (kernel-support.md, obsolescence-analysis.md, gz302-main.sh).

Changes I've incorporated into main

I've pulled your improvements directly into main in commit c84b00f:

  1. display-manager.shdisplay_has_gdctl() function + multi-environment status output (good catch that both X11 and Wayland checks can return true simultaneously on Ubuntu)
  2. Model numbers — corrected across all files
  3. ShellCheck CI — fixed the 3 pre-existing warnings (SC1090 directives + SC2043 single-iteration loop) that were causing the check to fail

ROCm 7.2 docs

The ROCm 7.2 documentation was already incorporated into main in v4.1.0 (commit f5ed945), including the automatic ROCm version detection in gz302-llm.sh. Your ai-ml-packages.md section would be a duplicate at this point.

ROCm version detection

Already implemented in gz302-llm.sh — it reads /opt/rocm/.info/version via get_rocm_version() and conditionally applies the HSA override. Thanks for the snippet confirmation.

What remains in this PR

Since I've incorporated the display-manager and model number changes into main, this PR's diff against main should now be minimal (likely just the duplicate ROCm 7.2 header in ai-ml-packages.md). You may want to rebase and check if there's anything left to merge, or we can close this.

@mantkiew
Copy link
Copy Markdown
Contributor Author

I updated with the latest main. There's just the link I added to ROCm on Ryzen docs left.

@th3cavalry th3cavalry merged commit 378ab63 into th3cavalry:main Feb 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants