Installation of OpenWebUI with the last update "Hardware Accelaration" not working on Proxmox

[Daniel-Leito]

In this script, I have seen in the file [ProxmoxVE] > [misc] > [tools.func] this line:
$STD apt -y install firmware-amd-graphics 2>/dev/null || true

But this seems to be wrong? In my point, the installation fails.

From a forum post of a Proxmox Staff Member here I would like to quote the following sentence:

Our pve-firmware package already ships those files, and thus conflicts with "firmware-amd-graphics", so when you try to install it apt sees the conflict and suggest trying to remove pve-firmware, which then in a chain would remove proxmox-ve et al., on current PVE 5.4 a apt hook will avoid that (if not special flag is set) from happening independent of your choice, FYI.

The firmware files shipped by pve-firmware should be as uptodate, and probably even newer, than the ones from Debian upstream anyway, so I'm do not think those will help you...

Source:
https://forum.proxmox.com/threads/apt-wants-to-remove-proxmox-ve-pve-firmware-and-autoremove-essentials.54959/post-253019

I am asking, because the script installation fails:

1. Helper Scripts: https://community-scripts.github.io/ProxmoxVE/scripts?id=openwebui
2. Install on Proxmox with cmd:
   bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/openwebui.sh)"
3. Standard Installation

Screen:

   ____                      _       __     __    __  ______
  / __ \____  ___  ____     | |     / /__  / /_  / / / /  _/
 / / / / __ \/ _ \/ __ \    | | /| / / _ \/ __ \/ / / // /  
/ /_/ / /_/ /  __/ / / /    | |/ |/ /  __/ /_/ / /_/ // /   
\____/ .___/\___/_/ /_/     |__/|__/\___/_.___/\____/___/   
    /_/                                                     
  ⚙️  Using Default Settings on node pve
  💡  PVE Version 9.1.2 (Kernel: 6.17.4-1-pve)
  🆔  Container ID: 102
  🖥️  Operating System: debian (13)
  📦  Container Type: Unprivileged
  💾  Disk Size: 25 GB
  🧠  CPU Cores: 4
  🛠️  RAM Size: 8192 MiB
  🎮  GPU Passthrough: Enabled
  🚀  Creating a Open WebUI LXC using the above default settings
  
  ✔️   Storage local (Free: 81.1GB  Used: 6.0GB) [Template]
  ✔️   Storage local-lvm (Free: 791.5GB  Used: 5.7GB) [Container]
  ✔️   Storage 'local-lvm' (lvmthin) validated
  ✔️   Template storage 'local' validated
  ✔️   Template search completed
  ✔️   Template debian-13-standard_13.1-2_amd64.tar.zst [online]
  ✔️   LXC Container 102 was successfully created.
 🎮 Detected AMD GPU
  ✔️   Automatically configuring AMD GPU passthrough
  ✔️   AMD GPU passthrough configured (2 devices)
  ✔️   Started LXC Container
  ✔️   Network in LXC is reachable (ping)
  ✔️   GPU passthrough configured (video:44, render:992)
  ✔️   Customized LXC Container
  ✔️   Set up Container OS
  ✔️   Network Connected: 192.168.0.174 
  ✔️   IPv4 Internet Connected
  ✖️   IPv6 Internet Not Connected
  ✔️   Git DNS: github.com:(✔️ ) raw.githubusercontent.com:(✔️ ) api.github.com:(✔️ ) git.community-scripts.org:(✔️ )
  ✔️   Updated Container OS
  ✔️   Installed Dependencies
 → apt -y install firmware-amd-graphics
--- Last 10 lines of silent log ---
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Reading package lists...
Building dependency tree...
Reading state information...
Package firmware-amd-graphics is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Error: Package 'firmware-amd-graphics' has no installation candidate
-----------------------------------
 📋 View full log (1547 lines): /root/.install-558fe815.log
  ✖️   Installation failed in container 102 (exit code: 100)

✔ Installation log: /tmp/install-lxc-102-558fe815.log

Remove broken container 102? (Y/n) [auto-remove in 60s]: 
No response - auto-removing container
   Removing container 102
  ✔️  Container 102 removed

Last lines of the .log file:

`Setting up mesa-opencl-icd:amd64 (25.0.7-2) ...
Processing triggers for man-db (2.13.1-1) ...
Processing triggers for base-files (13.8+deb13u2) ...
Processing triggers for libc-bin (2.41-12) ...

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Reading package lists...
Building dependency tree...
Reading state information...
Package firmware-amd-graphics is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Error: Package 'firmware-amd-graphics' has no installation candidate
root@pve:~# `

[MickLesk]

Nobody has ever tested AMD. Thats the simple reason. Every Feature i build dont get any Feedback

By the way, its never new, because we had never supported AMD GPUs. You can skip the GPU-HW-Bypass and it Work.

[Daniel-Leito]

"You can skip the GPU-HW-Bypass and it Work."

We have tried the advanced install to skip the GPU Bypass, but it still tried to install the firmware and stopps. It is true, that it skipped and ignored at the beginning of the script the recognizing GPU, but stopps at the same error point.