Skip to content

fix: clarify 'Torch not compiled with CUDA enabled' error for Intel GPU users - #1307

Open
lin-bot23 wants to merge 3 commits into
Comfy-Org:mainfrom
lin-bot23:fix/issue-1298-intel-gpu-cuda-error
Open

fix: clarify 'Torch not compiled with CUDA enabled' error for Intel GPU users#1307
lin-bot23 wants to merge 3 commits into
Comfy-Org:mainfrom
lin-bot23:fix/issue-1298-intel-gpu-cuda-error

Conversation

@lin-bot23

Copy link
Copy Markdown
Contributor

Summary

Intel GPU users seeing the error "Torch not compiled with CUDA enabled" in the NVIDIA section currently have no guidance about what this means for their hardware. They may mistakenly follow the CUDA reinstallation steps instead of installing the XPU-enabled PyTorch.

Files

  • troubleshooting/overview.mdx — Added 11 lines to the Intel GPU Issues section explaining that this error is expected for Intel GPUs and directing users to verify XPU availability and install XPU-enabled PyTorch.

Source

Issue #1298 — user reports getting "Torch not compiled with CUDA enabled" on an Intel Arc GPU while using XPU.

Checklist

  • self-reviewed diff
  • tested XPU verification command syntax

…PU users

Intel GPU users see 'Torch not compiled with CUDA enabled' and
mistakenly follow the NVIDIA CUDA reinstallation steps. Added a note
explaining this error is expected for Intel hardware — they should
verify XPU availability instead.

Closes Comfy-Org#1298
@coderabbitai

coderabbitai Bot commented Jul 22, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@lin-bot23, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 32 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 02d36170-cc04-406d-8470-9e8b7cb861ff

📥 Commits

Reviewing files that changed from the base of the PR and between 9100e87 and 89efa52.

📒 Files selected for processing (1)
  • troubleshooting/overview.mdx
📝 Walkthrough

Walkthrough

The Intel GPU troubleshooting section now explains expected CUDA errors, adds an XPU availability check, and describes ComfyUI’s behavior when XPU support is detected.

Changes

Intel GPU troubleshooting

Layer / File(s) Summary
XPU detection guidance
troubleshooting/overview.mdx
Documents that CUDA-related errors are expected on Intel GPUs, provides torch.xpu.is_available() for checking XPU support, and directs users to XPU-enabled PyTorch installation options when needed.
🚥 Pre-merge checks | ✅ 2
✅ Passed checks (2 passed)
Check name Status Explanation
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
✨ Simplify code
  • Create PR with simplified code

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@troubleshooting/overview.mdx`:
- Line 343: Update the Intel GPU guidance sentence in the MDX to replace the em
dash after “expected behavior” with a period or colon, keeping the existing
meaning and avoiding dash punctuation.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 1d1ad796-aa51-4646-b657-8fcca3ac698c

📥 Commits

Reviewing files that changed from the base of the PR and between 008532d and 9100e87.

📒 Files selected for processing (1)
  • troubleshooting/overview.mdx

Comment thread troubleshooting/overview.mdx Outdated
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.

1 participant