failed to install packages

Mar 06, 2015 6 Replies

Trying to install video for linux on my pi2:



root@picam1:~# apt-get install uv4l uv4l-raspicam Reading package lists... Done Building dependency tree Reading state information... Done uv4l is already the newest version. The following NEW packages will be installed: uv4l-raspicam



0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed. Need to get 0 B/1,377 kB of archives. After this operation, 3,666 kB of additional disk space will be used. Do you want to continue [Y/n]? Selecting previously unselected package uv4l-raspicam. (Reading database ... 77141 files and directories currently installed.) Unpacking uv4l-raspicam (from .../uv4l-raspicam_1.9.27_armhf.deb) ... Processing triggers for man-db ... Setting up uv4l (1.9.5-1) ... libkmod: ERROR ../libkmod/libkmod.c:554 kmod_search_moddep: could not open moddep file '/lib/modules/3.18.5-v7+/modules.dep.bin' dpkg: error processing uv4l (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of uv4l-raspicam: uv4l-raspicam depends on uv4l (>= 1.9.5); however: Package uv4l is not configured yet.

dpkg: error processing uv4l-raspicam (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: uv4l uv4l-raspicam E: Sub-process /usr/bin/dpkg returned an error code (1)


Any suggestions on how to fix, please?


# apt-get update ; apt-get upgrade

and if you've not done it:

# apt-get dist-upgrade

then re-run the install

Essentially the package you want depends on newer versions of something else.

Gordon

Have you installed a new kernel, but not rebooted yet?

Does the file /lib/modules/3.18.5-v7+/modules.dep.bin exist?

If it does, what are the permissions on it (ls -l)?

Thanks, Gordon, but sadly not.

I'd done the first two, but not the dist-upgrade. I've now done that, and nothing was upgraded. Still getting the error. Guess there's a problem with the repository. Bah!

Indeed! Is there anywhere to report such things?

No, frequent reboots

No; the modules directory contains 3.18.7-v7+, as I'd expect from root@picam1:~# uname -a Linux picam1 3.18.7-v7+ #755 SMP PREEMPT Thu Feb 12 17:20:48 GMT 2015 armv7l GNU/Linux

I guess there's a repo problem.

On the forums...

Only other thing I can think is to run

# rpi-update

to bring in the latest foundation kernel & modules...

Gordon

Thanks, Gordon; that seems to have fixed it.

Cheers, Tony

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required