/opt/vc/sbin/vcfiled: error while loading shared libraries: libvchiq_arm.so: cannot open shared object file: No such file or directory

[colszowka]

Hey, not sure what this means, but on my update (the Debian image from April) run I got the error message above. Here's the full log:

root@raspberrypi:/opt/rpi-update# ./rpi-update 
Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS
Performing self-update
Autodetecting memory split
Using ARM/GPU memory split of 192MB/64MB
We're running for the first time
Setting up firmware (this will take a few minutes)
Using SoftFP libraries
/opt/vc/sbin/vcfiled: error while loading shared libraries: libvchiq_arm.so: cannot open shared object file: No such file or directory
If no errors appeared, your firmware was successfully setup
A reboot is needed to activate the new firmware

After reboot however, the update tool now says the firmware is already up to date, so I was just wondering what this error meant?

Thanks for the effort of building and maintaining this!

[S0litaire]

Getting the same error.

Think it's something to do with the 3D graphics, seen this file mentioned in a few discussions regarding GLXdemo testing

[asayler]

I also had this issue. It is documented here: http://www.raspberrypi.org/phpBB3/viewtopic.php?f=26&t=6857.

As in that thread, running 'ldconfig' prior to running 'rpi-update' seems to have fixed it for me, although than another issue occurred: #8.

[asayler]

Also, I was able to force 'rpi-update' to re-run the update despite the "firmware is already up to date" message by removing the /boot/.firmware_revision file from my /boot directory. This allowed me to re-run 'rpi-update' after running 'ldconfig' to resolve the initial error.

Adding a "force update" option to 'rpi-update' that ignores the value of the .firmware_revision file might be desirable for situations such as this. Or maybe just make it so that 'rpi-update' doesn't generate the .firmware_revision file unless it verifies that the update completed without error.

[ganey]

Thanks, running ldconfig and removing .firmware_revision solved this issue for me. Maybe in the update process, ldconfig could be inserted before the update process, preventing any further possible library errors?

[mikebranderhorst]

I had the same error, after (run as root) swapon -a before running rpi-update the update had no errors but #8. The rpi-update still bricks the sd card.

Found out that folder boot is empty and folder boot.bak is not. Copied contents to boot and still not booting.

Tried replacing start.elf with arm224_start.elf and arm192_start.elf and still not booting.

Did not try (yet) running ldconfig before running rpi-update.

[gdevacc12]

I didn't see the suggestions re ldconfig before running and got this following error after the line "Using SoftFP libraries" ... is there a recovery fix?

/opt/vc/sbin/vcfailed: error while loading shared libraries: libvchiq_arm.so: cannot open shared object file: No such file or directory

Now my Wifi adapter no longer works, so I have no access to internet from the Pi.
dmesg reports: 8192cu: disagrees about version of symbol module_layout
Pi using debian9-19-04-12 and the latest 8192 driver
:-(

[gdevacc12]

Following my post above:
I restored the boot config of the SD card by copying from a folder on my PC.
Rebooted.
Followed the post link by asayler above: http://www.raspberrypi.org/phpBB3/viewtopic.php?f=26&t=6857.
so my steps were:

sudo -s
apt-get install ca-certificates
apt-get install git-core (in Debian) in Arch do: pacman -S git
apt-get update
apt-get upgrade
wget http://goo.gl/1BOfJ -O /usr/bin/rpi-update && chmod +x /usr/bin/rpi-update
ldconfig
rpi-update

rpi-update reported: firmware already up to date.
My pi seems to work fine and the WiFi works are before.

[JanStevens]

I also had a problem with config.txt (could not change it) they mentioned on the RaspPi forum that something was wrong with the current kernel.

A quote: "This is a known bug, probably rooted in the SDHCI driver, and I'm currently investigating it. The FAT filesystem causes single block writes, and these appear to be problematic (i.e. the writes silently don't succeed) with some SD cards. Dataloss bugs are not acceptable."

More on this issue (I feel they are related, rpi-update is unabel to write on some SD cards):
http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=13033
http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=11810&start=25

The problem seems to be fixed now, but people are unable to update (using the original distro).