i'm trying to run a update via pacman, but it finds a conflits: [code]…
- User
i'm trying to run a update via pacman, but it finds a conflits:
linux-firmware-nvidia: /usr/lib/firmware/nvidia/ad103 exists in filesystem linux-firmware-nvidia: /usr/lib/firmware/nvidia/ad104 exists in filesystem linux-firmware-nvidia: /usr/lib/firmware/nvidia/ad106 exists in filesystem linux-firmware-nvidia: /usr/lib/firmware/nvidia/ad107 exists in filesystemlinux-firmware-nvidiais currently not installed, and the mentioned files don't appear to have a owner (package)❯ sudo pacman -Qkp /usr/lib/firmware/nvidia/ad107 error: could not open file /usr/lib/firmware/nvidia/ad107: Error reading fd 4 error: could not load package '/usr/lib/firmware/nvidia/ad107': cannot open package filethis is the same result for all the above mentioned files
Assistant
This is a common conflict issue where files exist on your filesystem but aren't properly tracked by pacman. The command you used isn't quite right - you want to check file ownership with
pacman -Qo, notpacman -Qkp.Try this to check which package owns those files:
pacman -Qo /usr/lib/firmware/nvidia/ad107If that also shows the files are unowned (orphaned), here are a few ways to resolve this:
Option 1: Force the installation (if you're sure it's safe)
sudo pacman -S linux-firmware-nvidia --overwrite '/usr/lib/firmware/nvidia/*'Option 2: Remove the conflicting files first
sudo rm -rf /usr/lib/firmware/nvidia/ad10* sudo pacman -S linux-firmware-nvidiaOption 3: Check if these are leftover files from a previous installation
# Check if there are any nvidia firmware files ls -la /usr/lib/firmware/nvidia/ # Check for any partial package installs pacman -Qm | grep -i nvidiaThe most likely scenario is that these files were left behind from a previous package installation or manual installation. Since
linux-firmware-nvidiaisn't installed but wants to place files that already exist, using the--overwriteflag is usually the safest approach.What does
pacman -Qo /usr/lib/firmware/nvidia/ad107return?- User
let alone not needing custome firmware, i dont have a nvidea gpu in my system
❯ pacman -Qo /usr/lib/firmware/nvidia/ad107 /usr/lib/firmware/nvidia/ad107/ is owned by linux-firmware 20250508.788aadc8-2 Assistant
Ah, that explains it! The nvidia firmware files are currently owned by the main
linux-firmwarepackage, but they're being split out into a separatelinux-firmware-nvidiapackage. This is causing a conflict because both packages want to own the same files.Since you don't have an NVIDIA GPU, you don't need these firmware files at all. Here's how to resolve this:
Option 1: Remove the nvidia firmware files and exclude the nvidia package
# Remove the nvidia firmware files sudo rm -rf /usr/lib/firmware/nvidia/ # Add linux-firmware-nvidia to your ignore list so it won't try to install echo "IgnorePkg = linux-firmware-nvidia" | sudo tee -a /etc/pacman.conf # Or add it to the ignore list temporarily for this update sudo pacman -Syu --ignore linux-firmware-nvidiaOption 2: Let the split happen and then remove the nvidia package
# Allow the overwrite to happen during the update sudo pacman -Syu --overwrite '/usr/lib/firmware/nvidia/*' # Then remove the nvidia firmware package since you don't need it sudo pacman -Rs linux-firmware-nvidiaI'd recommend Option 1 since you don't have an NVIDIA GPU - there's no point in having nvidia firmware files on your system. The
linux-firmwarepackage is being restructured to split out vendor-specific firmware into separate packages, which is why you're seeing this conflict.- User
looking at
https://archlinux.org/packages/core/any/linux-firmware-nvidia/it appears to be required bylinux-firmwareso i'm guessing overwriting should be fine Assistant
Exactly right! This is a package split where Arch is breaking up the monolithic
linux-firmwarepackage into smaller vendor-specific packages. Thelinux-firmwarepackage now depends onlinux-firmware-nvidia(and likely other vendor firmware packages), so you do need to install it even without an NVIDIA GPU.This is just a reorganization - the same firmware files that were previously in
linux-firmwareare now being moved tolinux-firmware-nvidia. The overwrite is safe and expected:sudo pacman -Syu --overwrite '/usr/lib/firmware/nvidia/*'This is a common pattern when Arch splits packages - the files temporarily exist in both the old and new package locations during the transition, causing conflicts that need to be resolved with
--overwrite. Once the update completes, the files will be properly tracked under the newlinux-firmware-nvidiapackage.The nvidia firmware will still be there (taking up the same disk space as before), but now it's properly organized in a separate package. This makes the system more modular even if you don't currently need those specific firmware files.
- User
kinda annoying how i have to have a nvidia specific package installed when i don't need it, as i don't have anything nvidea in my system
Assistant
I totally understand the frustration! It does seem wasteful to install firmware for hardware you don't have. Let me help you check if it's actually required or if there's a way around it.
First, let's verify the dependency relationship:
# Check what linux-firmware actually depends on pacman -Si linux-firmware | grep -E "(Depends|Opt)" # Check if linux-firmware-nvidia is a hard dependency or optional pactree linux-firmwareYou might also try:
# See what's trying to pull in linux-firmware-nvidia pacman -Syu --ignore linux-firmware-nvidiaIf
linux-firmware-nvidiais truly a hard dependency, you're stuck with it due to how Arch structured the split. But if it's optional or if you can find an alternative approach, you might be able to avoid it.Another option is to install it for now to resolve the conflict, then immediately remove it and see what breaks:
sudo pacman -Syu --overwrite '/usr/lib/firmware/nvidia/*' sudo pacman -Rs linux-firmware-nvidiaIf nothing complains after removing it, you might be able to add it to
IgnorePkgin/etc/pacman.confto prevent future installations.What does the dependency check show? That'll tell us if there's actually a way around this or if it's just how Arch decided to structure the firmware packages.
- User
❯ sudo pacman -Syu --overwrite '/usr/lib/firmware/nvidia/*' :: Synchronizing package databases... core is up to date extra is up to date multilib is up to date :: Starting full system upgrade... resolving dependencies... looking for conflicting packages... Packages (51) amd-ucode-20250613.12fe085f-6 ca-certificates-mozilla-3.113-1 enchant-2.8.9-1 iana-etc-20250612-1 kio-extras-25.04.2-2 lib32-gettext-0.25-1 lib32-libdrm-2.4.125-1 lib32-libgpg-error-1.55-1 lib32-nss-3.113-1 lib32-pixman-0.46.2-1 lib32-sqlite-3.50.1-1 lib32-vkd3d-1.16-1 libblockdev-3.3.1-1 libblockdev-crypto-3.3.1-1 libblockdev-fs-3.3.1-1 libblockdev-loop-3.3.1-1 libblockdev-mdraid-3.3.1-1 libblockdev-nvme-3.3.1-1 libblockdev-part-3.3.1-1 libblockdev-swap-3.3.1-1 liburcu-0.15.3-1 linux-6.15.3.arch1-1 linux-firmware-20250613.12fe085f-6 linux-firmware-amdgpu-20250613.12fe085f-6 linux-firmware-atheros-20250613.12fe085f-6 linux-firmware-broadcom-20250613.12fe085f-6 linux-firmware-intel-20250613.12fe085f-6 linux-firmware-mediatek-20250613.12fe085f-6 linux-firmware-nvidia-20250613.12fe085f-6 linux-firmware-other-20250613.12fe085f-6 linux-firmware-qlogic-20250613.12fe085f-6 linux-firmware-radeon-20250613.12fe085f-6 linux-firmware-realtek-20250613.12fe085f-6 linux-firmware-whence-20250613.12fe085f-6 linux-headers-6.15.3.arch1-1 linux-zen-6.15.3.zen1-1 linux-zen-headers-6.15.3.zen1-1 nss-3.113-1 perl-json-4.10-2 perl-uri-5.32-1 pkgconf-2.5.0-1 pyenv-1:2.6.3-2 python-hypothesis-6.135.12-1 python-multidict-6.5.0-1 python-numpy-2.3.1-1 python-urllib3-2.5.0-1 python-urwid-3.0.2-1 qtkeychain-qt6-0.15.0-2 ruby-bundler-2.6.9-1 udisks2-2.10.1-6 vkd3d-1.16-1 Total Installed Size: 1228.18 MiB Net Upgrade Size: 67.55 MiB :: Proceed with installation? [Y/n] (51/51) checking keys in keyring [###################################################################] 100% (51/51) checking package integrity [###################################################################] 100% (51/51) loading package files [###################################################################] 100% (51/51) checking for file conflicts [###################################################################] 100% error: failed to commit transaction (conflicting files) linux-firmware-nvidia: /usr/lib/firmware/nvidia/ad103 exists in filesystem linux-firmware-nvidia: /usr/lib/firmware/nvidia/ad104 exists in filesystem linux-firmware-nvidia: /usr/lib/firmware/nvidia/ad106 exists in filesystem linux-firmware-nvidia: /usr/lib/firmware/nvidia/ad107 exists in filesystem Errors occurred, no packages were upgraded. Assistant
The
--overwritepattern might not be matching correctly. Let's try a different approach:First, check what nvidia firmware files actually exist:
find /usr/lib/firmware/nvidia/ -type fThen try with a more specific overwrite pattern:
sudo pacman -Syu --overwrite "/usr/lib/firmware/nvidia/ad10*"Or if that doesn't work, try overwriting all nvidia firmware:
sudo pacman -Syu --overwrite "/usr/lib/firmware/nvidia/*"If the pattern matching is still problematic, you can manually remove the conflicting files first:
sudo rm /usr/lib/firmware/nvidia/ad10* sudo pacman -SyuLooking at your upgrade list, I can see that Arch has indeed split
linux-firmwareinto many vendor-specific packages (amdgpu, atheros, broadcom, intel, mediatek, nvidia, radeon, realtek, etc.). This is unfortunate if you only need firmware for specific hardware.You're right to be annoyed - this forces everyone to install firmware for hardware they don't have. After the update completes, you could potentially try removing some of the vendor-specific firmware packages you don't need, though it might break the dependency chain that
linux-firmwareexpects.Try the manual file removal approach first - that should get you past this conflict.
- User
looks like the
rm -rfmethod works, but that's really really dumb Assistant
Yeah, you're absolutely right - it's a pretty poor user experience. Having to manually
rm -rffiles to resolve conflicts that were created by upstream packaging decisions is definitely not great design.The whole situation is frustrating:
- You're forced to install firmware for hardware you don't have
- The package split created conflicts that should have been handled automatically
- The
--overwriteglob patterns didn't work as expected - Manual file deletion shouldn't be the solution for what's essentially a packaging transition issue
This is one of the downsides of rolling release distros - sometimes major package restructuring creates these awkward situations where users have to do manual cleanup for what should be seamless updates. Arch could have handled this transition better by making the old
linux-firmwarepackage handle the file conflicts automatically, or by making the vendor-specific firmware packages truly optional.At least you got through it, but I totally get why you're annoyed. It's the kind of thing that makes you question whether splitting the firmware package was actually worth the hassle it created for users.
Hopefully this was a one-time pain point and future updates will be smoother now that the split is complete.
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.