github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-06 19:08:59 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #574] Enhance GPU Detection Logic for WSL2 Compatibility #27655

New Issue
Closed
opened 2026-04-25 02:23:58 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-25 02:23:58 -05:00
Owner
Copy Link

Originally created by @Mulugruntz on GitHub (Jan 25, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/574

Bug Report

Description

Bug Summary:
The setup script fails to detect NVIDIA GPUs in Windows Subsystem for Linux 2 (WSL2) environments due to its reliance on lspci, which does not list NVIDIA GPUs as it would on a native Linux system.

Steps to Reproduce:

  1. Set up WSL2 on a Windows system with an NVIDIA GPU.
  2. Install NVIDIA drivers for WSL2 and verify the installation using nvidia-smi.
  3. Run the setup script that includes GPU detection logic using lspci | grep -i nvidia.
  4. Observe that the script fails to detect the NVIDIA GPU.
$ lspci
0e2b:00:00.0 SCSI storage controller: Red Hat, Inc. Virtio filesystem (rev 01)
19c5:00:00.0 SCSI storage controller: Red Hat, Inc. Virtio filesystem (rev 01)
2761:00:00.0 3D controller: Microsoft Corporation Device 008e
2dec:00:00.0 SCSI storage controller: Red Hat, Inc. Virtio filesystem (rev 01)
3ad0:00:00.0 SCSI storage controller: Red Hat, Inc. Virtio filesystem (rev 01)
75bc:00:00.0 SCSI storage controller: Red Hat, Inc. Virtio filesystem (rev 01)
8973:00:00.0 SCSI storage controller: Red Hat, Inc. Virtio filesystem (rev 01)
92df:00:00.0 SCSI storage controller: Red Hat, Inc. Virtio filesystem (rev 01)
aad0:00:00.0 SCSI storage controller: Red Hat, Inc. Virtio filesystem (rev 01)
b110:00:00.0 SCSI storage controller: Red Hat, Inc. Virtio filesystem (rev 01)
ce28:00:00.0 System peripheral: Red Hat, Inc. Virtio file system (rev 01)
def6:00:00.0 SCSI storage controller: Red Hat, Inc. Virtio console (rev 01)
e643:00:00.0 SCSI storage controller: Red Hat, Inc. Virtio filesystem (rev 01)
f6cd:00:00.0 3D controller: Microsoft Corporation Device 008e
$ nvidia-smi
Thu Jan 25 18:13:30 2024
+---------------------------------------------------------------------------------------+
| NVIDIA-SMI 545.29.04              Driver Version: 546.17       CUDA Version: 12.3     |
|-----------------------------------------+----------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |         Memory-Usage | GPU-Util  Compute M. |
|                                         |                      |               MIG M. |
|=========================================+======================+======================|
|   0  NVIDIA GeForce RTX 3050 ...    On  | 00000000:01:00.0 Off |                  N/A |
| N/A   52C    P8               9W /  45W |    556MiB /  4096MiB |      0%      Default |
|                                         |                      |                  N/A |
+-----------------------------------------+----------------------+----------------------+

+---------------------------------------------------------------------------------------+
| Processes:                                                                            |
|  GPU   GI   CI        PID   Type   Process name                            GPU Memory |
|        ID   ID                                                             Usage      |
|=======================================================================================|
|  No running processes found                                                           |
+---------------------------------------------------------------------------------------+

Expected Behavior:
The script should correctly identify the presence of an NVIDIA GPU in WSL2 environments, allowing for further GPU-related setup processes to proceed.

Actual Behavior:
The script does not detect the NVIDIA GPU in WSL2, likely skipping any setup steps that depend on GPU presence, due to lspci not listing the GPU as expected.

Environment

  • Operating System: Windows 11 Pro with WSL2 enabled
  • Browser (if applicable): N/A

Reproduction Details

Confirmation:

  • I have read and followed all the instructions provided in the README.md.
  • I have reviewed the troubleshooting.md document.
  • I have included the browser console logs.
  • I have included the Docker container logs.

Logs and Screenshots

Browser Console Logs:
N/A

Docker Container Logs:
N/A

Screenshots (if applicable):
N/A

Installation Method

I encountered this issue while running a shell script (run-compose.sh) designed to set up a Docker environment that requires GPU support. The script attempts to automatically detect the presence of NVIDIA GPUs using lspci.

Additional Information

Considering WSL2's architecture, which abstracts hardware access through a virtualization layer, utilities like lspci do not directly interact with the hardware in the same way they do on a native Linux system. This can lead to false negatives when detecting hardware, such as NVIDIA GPUs. A potential solution could involve enhancing the detection logic to also check for GPU presence using nvidia-smi, which is known to work reliably in WSL2 environments.

Note

I understand the importance of providing a complete and detailed bug report. I have attempted to provide all necessary information based on my current setup and the issue encountered. I'm looking forward to any guidance or suggestions on addressing this issue. Thank you!

Originally created by @Mulugruntz on GitHub (Jan 25, 2024). Original GitHub issue: https://github.com/open-webui/open-webui/issues/574 # Bug Report ## Description **Bug Summary:** The setup script fails to detect NVIDIA GPUs in Windows Subsystem for Linux 2 (WSL2) environments due to its reliance on `lspci`, which does not list NVIDIA GPUs as it would on a native Linux system. **Steps to Reproduce:** 1. Set up WSL2 on a Windows system with an NVIDIA GPU. 2. Install NVIDIA drivers for WSL2 and verify the installation using `nvidia-smi`. 3. Run the setup script that includes GPU detection logic using `lspci | grep -i nvidia`. 4. Observe that the script fails to detect the NVIDIA GPU. <details> ```text $ lspci 0e2b:00:00.0 SCSI storage controller: Red Hat, Inc. Virtio filesystem (rev 01) 19c5:00:00.0 SCSI storage controller: Red Hat, Inc. Virtio filesystem (rev 01) 2761:00:00.0 3D controller: Microsoft Corporation Device 008e 2dec:00:00.0 SCSI storage controller: Red Hat, Inc. Virtio filesystem (rev 01) 3ad0:00:00.0 SCSI storage controller: Red Hat, Inc. Virtio filesystem (rev 01) 75bc:00:00.0 SCSI storage controller: Red Hat, Inc. Virtio filesystem (rev 01) 8973:00:00.0 SCSI storage controller: Red Hat, Inc. Virtio filesystem (rev 01) 92df:00:00.0 SCSI storage controller: Red Hat, Inc. Virtio filesystem (rev 01) aad0:00:00.0 SCSI storage controller: Red Hat, Inc. Virtio filesystem (rev 01) b110:00:00.0 SCSI storage controller: Red Hat, Inc. Virtio filesystem (rev 01) ce28:00:00.0 System peripheral: Red Hat, Inc. Virtio file system (rev 01) def6:00:00.0 SCSI storage controller: Red Hat, Inc. Virtio console (rev 01) e643:00:00.0 SCSI storage controller: Red Hat, Inc. Virtio filesystem (rev 01) f6cd:00:00.0 3D controller: Microsoft Corporation Device 008e $ nvidia-smi Thu Jan 25 18:13:30 2024 +---------------------------------------------------------------------------------------+ | NVIDIA-SMI 545.29.04 Driver Version: 546.17 CUDA Version: 12.3 | |-----------------------------------------+----------------------+----------------------+ | GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |=========================================+======================+======================| | 0 NVIDIA GeForce RTX 3050 ... On | 00000000:01:00.0 Off | N/A | | N/A 52C P8 9W / 45W | 556MiB / 4096MiB | 0% Default | | | | N/A | +-----------------------------------------+----------------------+----------------------+ +---------------------------------------------------------------------------------------+ | Processes: | | GPU GI CI PID Type Process name GPU Memory | | ID ID Usage | |=======================================================================================| | No running processes found | +---------------------------------------------------------------------------------------+ ``` </details> **Expected Behavior:** The script should correctly identify the presence of an NVIDIA GPU in WSL2 environments, allowing for further GPU-related setup processes to proceed. **Actual Behavior:** The script does not detect the NVIDIA GPU in WSL2, likely skipping any setup steps that depend on GPU presence, due to `lspci` not listing the GPU as expected. ## Environment - **Operating System:** Windows 11 Pro with WSL2 enabled - **Browser (if applicable):** N/A ## Reproduction Details **Confirmation:** - [x] I have read and followed all the instructions provided in the README.md. - [x] I have reviewed the troubleshooting.md document. - [ ] I have included the browser console logs. - [ ] I have included the Docker container logs. ## Logs and Screenshots **Browser Console Logs:** N/A **Docker Container Logs:** N/A **Screenshots (if applicable):** N/A ## Installation Method I encountered this issue while running a shell script (`run-compose.sh`) designed to set up a Docker environment that requires GPU support. The script attempts to automatically detect the presence of NVIDIA GPUs using `lspci`. ## Additional Information Considering WSL2's architecture, which abstracts hardware access through a virtualization layer, utilities like `lspci` do not directly interact with the hardware in the same way they do on a native Linux system. This can lead to false negatives when detecting hardware, such as NVIDIA GPUs. A potential solution could involve enhancing the detection logic to also check for GPU presence using `nvidia-smi`, which is known to work reliably in WSL2 environments. ## Note I understand the importance of providing a complete and detailed bug report. I have attempted to provide all necessary information based on my current setup and the issue encountered. I'm looking forward to any guidance or suggestions on addressing this issue. Thank you!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#27655
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?