[Solved] Warnings from recent linux firmware update safe to ignore?

dan123 · 2025-06-25 09:27:10

Running pacman -Syu gave me the following warnings when updating from linux firmware 20250613.12fe085f-6 to linux firmware 20250613.12fe085f-9 Are they save to ignore?

warning: could not get file information for usr/lib/firmware/nvidia/ad103
warning: could not get file information for usr/lib/firmware/nvidia/ad104
warning: could not get file information for usr/lib/firmware/nvidia/ad106
warning: could not get file information for usr/lib/firmware/nvidia/ad107

might be worth noting that the root directory ( / ) isnt included in the file path warning messages, which might be triggering the warnings

edit: added formatting

Last edited by dan123 (2025-06-26 05:56:09)

SimonJ · 2025-06-25 09:36:03

Did you read the news here https://archlinux.org

Or search the forum for firmware error message?

dan123 · 2025-06-25 09:57:13

its not an error message, its a warning message. the update from 20250613.12fe085f-6 to linux firmware 20250613.12fe085f-9 went ahead and wasn't stopped. the news was for yesterday's because the update was stopped and needed manual intervention to complete.

dan123 · 2025-06-25 10:04:23

[me@archlinux ~]$ ls -l usr/lib/firmware/nvidia
ls: cannot access 'usr/lib/firmware/nvidia': No such file or directory
[me@archlinux ~]$ ls -l /usr/lib/firmware/nvidia
total 132
drwxr-xr-x 3 root root 4096 May 25 10:15 ad102
lrwxrwxrwx 1 root root    5 Jun 23 23:44 ad103 -> ad102
lrwxrwxrwx 1 root root    5 Jun 23 23:44 ad104 -> ad102
lrwxrwxrwx 1 root root    5 Jun 23 23:44 ad106 -> ad102
lrwxrwxrwx 1 root root    5 Jun 23 23:44 ad107 -> ad102
...

edit: added formatting

Last edited by dan123 (2025-06-25 11:55:53)

Lone_Wolf · 2025-06-25 11:33:05

Please post the output of

$ pacman -Qikk linux-firmware-nvidia

Edit your post #1 and #4 to use code tags

dan123 · 2025-06-25 11:56:51

Lone_Wolf wrote:

Please post the output of
$ pacman -Qikk linux-firmware-nvidia
Edit your post #1 and #4 to use code tags

Name            : linux-firmware-nvidia
Version         : 20250613.12fe085f-9
Description     : Firmware files for Linux - Firmware for NVIDIA GPUs and SoCs
Architecture    : any
URL             : https://gitlab.com/kernel-firmware/linux-firmware
Licenses        : LicenseRef-WHENCE  LicenseRef-nvidia
Groups          : None
Provides        : None
Depends On      : linux-firmware-whence
Optional Deps   : None
Required By     : linux-firmware
Optional For    : None
Conflicts With  : None
Replaces        : None
Installed Size  : 103.55 MiB
Packager        : Jan Alexander Steffens (heftig) <heftig@archlinux.org>
Build Date      : Mon 23 Jun 2025 23:44:01 BST
Install Date    : Wed 25 Jun 2025 10:05:12 BST
Install Reason  : Installed as a dependency for another package
Install Script  : No
Validated By    : Signature

linux-firmware-nvidia: 615 total files, 0 altered files

Lone_Wolf · 2025-06-25 12:13:00

Looks good, let's check the overall installation health .

Run as root/with root rights

# LC_ALL=C pacman -Qkk |& grep -v ', 0 altered files'

and post the output .

dan123 · 2025-06-25 12:41:47

ran

sudo LC_ALL=C pacman -Qkk |& grep -v ', 0 altered files' > output.txt

https://pastebin.com/a0L15L6Z

what does the output mean?

seth · 2025-06-25 13:01:57

You've quite some libraries with wrong (non-root) ownership, why is that?

stat /usr/lib/libcurl.so.4.8.0

dan123 · 2025-06-25 13:38:15

idk. would it be best to uninstall then reinstall packages or to fully reinstall arch to fix the issue?
i only have a few files to copy over. reinstalling arch isnt too much of a deal to me

seth · 2025-06-25 13:42:46

Just re-installing the affected packages will hopefully sanitize the permissions, but you still might want to look into the causes.

dan123 · 2025-06-25 14:00:21

do all the packages with "mismatch" in the brackets need to be uninstalled then reinstalled?
i'll make my own script to uninstall them reinstall them. i'm not going to go one by one manually.

thanks

seth · 2025-06-25 14:08:13

You don't have to uninstall anything (and should not)

pacman -Syu  acl  alsa-lib  appstream  appstream-qt  ark  aspell  aspell-en  at-spi2-core  audit  avahi  baloo-widgets  bash  bluez  bluez-libs  brotli  bzip2  cairo  composefs  cryptsetup  cups  cups-browsed  curl  dbus  dconf  device-mapper  dolphin  double-conversion  duktape  e2fsprogs  editorconfig-core-c  exiv2  expat  findutils  flac  flatpak  fontconfig  freetype2  fribidi  fuse3  gcc  gcc-libs  gdk-pixbuf2  glib-networking  glibc  gmp  gnutls  gpgme  gpgmepp  graphite  gsettings-desktop-schemas  gtk3  gwenview  harfbuzz  hunspell  icu  jansson  jasper  jbigkit  json-c  json-glib  kaccounts-integration  kate  keyutils  kirigami-addons  kmod  konsole  krb5  lame  lcms2  leancrypto  libaccounts-glib  libaccounts-qt  libarchive  libassuan  libasyncns  libatasmart  libb2  libbpf  libbytesize  libcanberra  libcap  libcap-ng  libcloudproviders  libcups  libcupsfilters  libdaemon  libdatrie  libdecor  libdisplay-info  libdmtx  libdrm  libedit  libei  libelf  libepoxy  libevdev  libexif  libfdk-aac  libffi  libfontenc  libfreeaptx  libgcrypt  libgpg-error  libgudev  libice  libidn2  libimobiledevice  libinih  libinput  libjpeg-turbo  libkexiv2  liblc3  libldac  libldap  libmalcontent  libnghttp3  libnl  libnm  libnsl  libnvme  libogg  libp11-kit  libpaper  libpciaccess  libpipewire  libppd  libproxy  libpsl  libpulse  libqaccessibilityclient-qt6  libqalculate  libsasl  libseccomp  libsecret  libsm  libsndfile  libsodium  libssh2  libstemmer  libtasn1  libthai  libtiff  libtirpc  libtool  libunistring  libunwind  libusb  libva  libvorbis  libwebp  libwireplumber  libx11  libxau  libxcb  libxcomposite  libxcrypt  libxcursor  libxcvt  libxdamage  libxdmcp  libxext  libxfixes  libxfont2  libxi  libxinerama  libxkbcommon  libxkbcommon-x11  libxmlb  libxrandr  libxrender  libxshmfence  libxtst  libxxf86vm  libyaml  llvm-libs  lm_sensors  lmdb  lz4  md4c  mpfr  mpg123  mtdev  ncurses  nettle  networkmanager  noto-fonts  noto-fonts-extra  nspr  openjpeg2  openssh  openssl  opus  ostree  p11-kit  pango  passim  pcre2  pcsclite  phonon-qt6  pipewire  pipewire-audio  pipewire-pulse  pixman  polkit  polkit-qt6  poppler  qca-qt6  qcoro  qpdf  qrencode  qt6-5compat  qt6-declarative  qt6-multimedia  qt6-positioning  qt6-sensors  qt6-shadertools  qt6-speech  qt6-svg  qt6-translations  qt6-wayland  qt6-webengine  readline  rtkit  sbc  signond  spirv-tools  sqlite  sudo  systemd  systemd-libs  tdb  tinysparql  tpm2-tss  ttf-hack  ttf-liberation  tzdata  ufw  util-linux-libs  volume_key  wayland  wireplumber  wpa_supplicant  xcb-util  xcb-util-cursor  xcb-util-image  xcb-util-keysyms  xcb-util-renderutil  xcb-util-wm  xdg-desktop-portal  xdg-desktop-portal-gtk  xf86-video-amdgpu  xf86-video-ati  xkeyboard-config  xz  zlib  zstd  zxing-cpp

dan123 · 2025-06-26 05:55:16

If pacman -Sy was mentioned sooner to reinstall the packages, that would have been better. Already generated a list of unique packages names. But then added functionality to remove then add the packages. In doing so I broke the system to the point of not even pacman -S , pacman -Q or chrooting from a live usb working. I was at least able to use mount, cp and ls to copy files over to an external drive. Part way through reinstalling arch. Trying the manual method rather than archinstall this time. I'll get there eventually. Lack of boot loader issues

Scimmia · 2025-06-26 12:42:25

First, not -Sy, -Syu. Second, nobody ever said to remove. In fact, when you said "uninstall then reinstall", you were told "Just re-installing". Don't put this on anyone but you, you had this idea of removing stuck in your head and wouldn't be persuaded.

dan123 · 2025-06-27 15:25:22

Scimmia wrote:

First, not -Sy, -Syu. Second, nobody ever said to remove. In fact, when you said "uninstall then reinstall", you were told "Just re-installing". Don't put this on anyone but you, you had this idea of removing stuck in your head and wouldn't be persuaded.

"Reinstalling" typically means "uninstalling then reinstalling", in the same way that "free" typically means "no cost" and not "freedom". I didn't check for updates on the thread before proceeding. I made a script and it didn't work in the intended way. I dealt with it, so it isn't an issue anymore. No need to come across as hostile about it.

Identifying the various mismatches issues helped. Reinstalling whole system restored functionality that used to exist which I had previously broken somehow. Could it have been done in a less drastic way? Yes. If the pacman command for how to reinstall was shown in same post, that would have made it clear.

My guess for how it became like that is ctrl+c while building a custom arch iso for personal use. At some point I noticed I was removed from the wheel group and added myself back, using a live usb. Turns out that may not have been the only type of software-level breakage.

seth · 2025-06-27 15:43:48

"Reinstalling" typically means "uninstalling then reinstalling"

Read that three times. Loud. Think about it. No? Read it out couple of times more, maybe louder.

Then read https://wiki.archlinux.org/title/Pacman - first to familiarize yourself with the system in front of you, second pay attention to how "re-installing" is used there.

dan123 · 2025-06-27 17:00:33

This is a help thread. Assume no level of knowledge. Be clearer when giving help.

I hope to never use the forums again.

seth · 2025-06-27 17:09:37

Good luck with the rest of your life.
You'll need it.

Nikolai5 · 2025-06-27 17:16:34

In order to get this far though you must have had some level of knowledge, or else how did you install Arch or learn how to use Pacman, the only resources are the wiki and man pages.

Having no knowledge implies you had someone else install the system for you, which is not the point.

Everyone here volunteers their time to try to help, nobody is perfect, and I agree sarcasm and combativeness is poor form, but so is ignoring what people are saying and not wanting to learn.
I'm sorry you had a bad experience on the forums, having computer issues can be stressful and that is understood, hopefully your issues are resolved going forward and the suggestion to read the pacman page on the wiki is a good one, as well as the page here: https://wiki.archlinux.org/title/AUR_helpers just in case you are tempted by suggestions to use things like yay as many newcomers are.

dan123 · 2025-06-27 17:59:10

It's obviously the user's fault for needing help, especially when it's "it's just me" issue that no one else has ever encountered and isn't documented anywhere. Help as a topic should be disallowed and removed entirely.

There was only 1 helpful poster and it was an admin. For that, I am grateful. No one is under any obligation to give help (why does "help vampires" even exist as a rule?) ; but if you do, make it crystal clear what the instructions are.

Large sections of the wiki are out of date or have factually disputes. Other times it just isn't clear.

The only reason I am able to install arch is because of archiso. Has CLI and can modify JSON files to easily install just the packages I want. Only major thing I needed to do was make the login manager work and start some system services. I have about a decade's worth of programming experience.

Scimmia · 2025-06-27 18:05:30

dan123 wrote:

There was only 1 helpful poster and it was an admin.

seth tried to help you. You made WILD assumptions about things, then blamed him for not spoonfeeding you basic commands earlier. When someone tells you to reinstall packages, they should not have to tell you that that doesn't mean uninstall, nor should they have to tell you the exact command to install things. You took this WAY off track and torpedoed your system because you refused to listen, nothing more.

seth · 2025-06-27 18:07:15

Here's a weird thought: next time you're unsure about basic english and what to do, just ask back.
Also, reminder of the beginning of your journey to litigate the meaning of common words to justify your haphazard errands.

you wrote:

idk. would it be best to uninstall then reinstall packages or to fully reinstall arch to fix the issue?

me wrote:

Just re-installing the affected packages will hopefully sanitize the permissions,

you wrote:

do all the packages with "mismatch" in the brackets need to be uninstalled then reinstalled?

me wrote:

You don't have to uninstall anything (and should not)

You asked whether you need to uninstall and the reinstall, I told you that just reinstalling will do, you asked whether you need to uninstall and reinstall and I told you again to not uninstall anything.
Then you went on to complain that nobody told you that you should not uninstall things and now you fucked up your system and it's absolutely everyone elses fault for not telling you to not uninstall this.

https://www.urbandictionary.com/define. … m=Trumping

dan123 · 2025-06-27 19:39:27

I wasnt blaming you. Your reply about using pacman -Sy followed by the package list came after I tried to fix it. I didn't check forum again until the system broke.

A couple of days ago when the firmware update has issues, the fix was to remove the package then add it pack with pacman -Syu linux-firmware . I was trying achieve same sort of result following that logic (remove packages then adding the packages) AKA reinstalling the packages.

I broke my system. No need to have a go with me on that. Issue still got resolved in the end. All posts after that added nothing of value.

Arch Linux

#1 2025-06-25 09:27:10

[Solved] Warnings from recent linux firmware update safe to ignore?

#2 2025-06-25 09:36:03

Re: [Solved] Warnings from recent linux firmware update safe to ignore?

#3 2025-06-25 09:57:13

Re: [Solved] Warnings from recent linux firmware update safe to ignore?

#4 2025-06-25 10:04:23

Re: [Solved] Warnings from recent linux firmware update safe to ignore?

#5 2025-06-25 11:33:05

Re: [Solved] Warnings from recent linux firmware update safe to ignore?

#6 2025-06-25 11:56:51

Re: [Solved] Warnings from recent linux firmware update safe to ignore?

#7 2025-06-25 12:13:00

Re: [Solved] Warnings from recent linux firmware update safe to ignore?

#8 2025-06-25 12:41:47

Re: [Solved] Warnings from recent linux firmware update safe to ignore?

#9 2025-06-25 13:01:57

Re: [Solved] Warnings from recent linux firmware update safe to ignore?

#10 2025-06-25 13:38:15

Re: [Solved] Warnings from recent linux firmware update safe to ignore?

#11 2025-06-25 13:42:46

Re: [Solved] Warnings from recent linux firmware update safe to ignore?

#12 2025-06-25 14:00:21

Re: [Solved] Warnings from recent linux firmware update safe to ignore?

#13 2025-06-25 14:08:13

Re: [Solved] Warnings from recent linux firmware update safe to ignore?

#14 2025-06-26 05:55:16

Re: [Solved] Warnings from recent linux firmware update safe to ignore?

#15 2025-06-26 12:42:25

Re: [Solved] Warnings from recent linux firmware update safe to ignore?

#16 2025-06-27 15:25:22

Re: [Solved] Warnings from recent linux firmware update safe to ignore?

#17 2025-06-27 15:43:48

Re: [Solved] Warnings from recent linux firmware update safe to ignore?

#18 2025-06-27 17:00:33

Re: [Solved] Warnings from recent linux firmware update safe to ignore?

#19 2025-06-27 17:09:37

Re: [Solved] Warnings from recent linux firmware update safe to ignore?

#20 2025-06-27 17:16:34

Re: [Solved] Warnings from recent linux firmware update safe to ignore?

#21 2025-06-27 17:59:10

Re: [Solved] Warnings from recent linux firmware update safe to ignore?

#22 2025-06-27 18:05:30

Re: [Solved] Warnings from recent linux firmware update safe to ignore?

#23 2025-06-27 18:07:15

Re: [Solved] Warnings from recent linux firmware update safe to ignore?

#24 2025-06-27 19:39:27

Re: [Solved] Warnings from recent linux firmware update safe to ignore?

Board footer