Comment 21 for bug 87054

I'm on the latest intrepid updates, my webcam responds to lsusb, but skype doesn't see the camera, and using the ppa sources intel listed the driver fails to compile during installation. I get the following error:

------------------------------------------------------------------------------------------------
mlapaglia@amanda-laptop:~$ sudo apt-get install microdia-dkms
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  microdia-dkms
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/80.8kB of archives.
After this operation, 627kB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
  microdia-dkms
Install these packages without verification [y/N]? Y
Selecting previously deselected package microdia-dkms.
(Reading database ... 116746 files and directories currently installed.)
Unpacking microdia-dkms (from .../microdia-dkms_2008.09-0ubuntu1~ppa2i_all.deb) ...
Processing triggers for man-db ...
Setting up microdia-dkms (2008.09-0ubuntu1~ppa2i) ...
Loading new microdia-2008.09 DKMS files...

Creating symlink /var/lib/dkms/microdia/2008.09/source ->
                 /usr/src/microdia-2008.09

DKMS: add Completed.
Installing prebuilt kernel module binaries (if any)
Building module...

Kernel preparation unnecessary for this kernel. Skipping...

Building module:
cleaning build area....
make KERNELRELEASE=2.6.27-4-generic KVER=2.6.27-4-generic src=/var/lib/dkms/microdia/2008.09/build....(bad exit status: 2)

Error! Bad return status for module build on kernel: 2.6.27-4-generic (i686)
Consult the make.log in the build directory
/var/lib/dkms/microdia/2008.09/build/ for more information.
0
0
dpkg: error processing microdia-dkms (--configure):
 subprocess post-installation script returned error exit status 10
Errors were encountered while processing:
 microdia-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)
------------------------------------------------------------------------------------------------

is this because my kernel is too new, or because it's i686?
I had manually installed the drivers on Gutsy a few months ago, and it was working fine.