I reverted to v526 which appears to have the relevant files correctly packaged for the MIG installer for Video4Linux.
It’s still reporting that it cannot find that file. I reckon that the only way to successfully debug this problem would be if you had a Raspberry Pi with a camera module attached in front of you.
I do know that I had build the v4l2 driver when I got it working in Wheezy following Genes instructions from the old forum. That was necessary as the v4l2 driver hadn’t been fully integrated into the Linux kernel at that stage.
I have the bcm2835-v4l2 loading at boot in the /etc/modules file and it’s confirmed working with the dmesg command.
The only thing I can think of that may be causing the problem now is that the path that the system is looking for the file in is incorrect or possibly a permissions issue.
As I said if you have access to a Pi and a camera module it would be a lot easier to debug this problem.