-
Notifications
You must be signed in to change notification settings - Fork 232
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vchiq_lib: Very incompatible VCHIQ library - cannot retrieve driver version #8
Comments
This isn't an issue with rpi-update. As the thread you linked describes, you'll see this error when you use an application compiled against an older version of the VC libs this tool updates. |
Noted. I mainly posted this here in case others that use rpi-update encounter it. Is there a fix that you know of? Is it even really an issue that I should be concerned about? |
The "fix" is to recompile the application that complains against a new version of the libraries. The app probably won't work until you do. |
Subsequent runs if rpi-update (removing /boot/.firmware_revision between each) do not produce the error. It appears that it's only the first run of rpi-update on an un-updated board lead to the error. The "application" that was complaining was the rpi-updater itself (or since it is a script, one of the utilities that it calls, maybe whatever uses the SoftFP libraries). But since it seems to resolve itself after one run, it seems to be a non issue. |
Probleme can be reproduced with any first run of rpi-update against a fresh "install" on the stock 20120419 Debian Squeeze image. Sequence :
Could it be something in the rpi-update logic around the sdk update that occurs but is not roll-backed after a ldconfig error ? |
Before running rpi-update you should: or rpi-update should be changed to be asking/doing it for you |
As mentioned in my OP, I ran both apt-get update and apt-get upgrade prior to experiencing this error. The error XavM describes still occurs even after the upgrade (unless the issue has been fixed via a package upgrade in the last week). |
In my case, running upgrade fixed it and did it just yesterday. I don't have another sdcard at the moment to try from scratch but I will to confirm it. |
The steps above to upgrade and |
The updater prints this error even after the first update, for me |
It seems to be vcfiled throwing this error |
Fresh Debian 20120419 image
|
Same here. |
(somehow related) http://www.raspberrypi.org/archives/1139
vchiq_lib: Very incompatible VCHIQ library Hexxeh: #8 (comment)
Are there any new versions of |
Running 'rpi-update' on a recently shipped (6/6/12) Raspberry Pi using the standard 4/19/12 RPI Debain Squeeze image results in the following error:
2282281000: vchiq_lib: Very incompatible VCHIQ library - cannot retrieve driver version
The rpi-update run then completes, and the RPi seems to boot and function correctly. I have not verified whether or not the firmware was actually updated, but it appears to have been given that the time stamps for the files in the /boot directory were updated.
Prior to running 'rpi-update', I ran 'apt-get update; apt-get upgrade' in order to update the OS to the latest version of all packages. I also had to run 'ldconfig' prior to running 'rpi-update' to fix the issue discussed here: #7.
It seems this may be related to the very similar issue discussed in basn's Jun 05, 2012 5:59pm post here: http://www.raspberrypi.org/phpBB3/viewtopic.php?t=5037&p=92585.
The text was updated successfully, but these errors were encountered: