Hmmm… take a look at this (French I’m afraid):
http://doc.ubuntu-fr.org/em28xx_generique
or
Same page through Google Translate
First of all…YES, I do realise thats a D60 not a D60+, but bear with me…
After reading that, I decided to have a second look at what was in the newer em28xx-cards.c
(BTW, it is now slightly different, so a direct copy isn’t possible)
So I downloaded the latest v4l-dvb by following the instructions in the “Tarball download from a mercurial repository” section here:
http://www.linuxtv.org/repo/
After unpacking and opening the /v4l-dvb-3724e93f7af5/linux/drivers/media/video/em28xx/em28xx-cards.c file in gedit, I noticed that towards the bottom of the file your cards device ID:
{ USB_DEVICE(0xeb1a, 0x2861),
.driver_info = EM2820_BOARD_UNKNOWN },
points back up the file to the section:
[EM2820_BOARD_UNKNOWN] = {
.name = "Unknown EM2750/28xx video grabber",
.tuner_type = TUNER_ABSENT,
.is_webcam = 1, /* To enable sensor probe */
},
now if you compare that to all the other sections for (TUNER_ABSENT) grabber cards, you’ll notice it doesn’t contain a section relating to input (and in particular amux)… I reckon that section needs changing to:
[EM2820_BOARD_UNKNOWN] = {
.name = "Unknown EM2750/28xx video grabber",
.tuner_type = TUNER_ABSENT,
.is_webcam = 1, /* To enable sensor probe */
.input = { {
.type = EM28XX_VMUX_COMPOSITE1,
.vmux = 0,
.amux = EM28XX_AMUX_VIDEO,
} },
},
Then the driver recompiling/reinstalling
BTW, the added input part came from the:
[EM2820_BOARD_VIDEOLOGY_20K14XUSB] = {
.name = "Videology 20K14XUSB USB2.0",
.valid = EM28XX_BOARD_NOT_VALIDATED,
.tuner_type = TUNER_ABSENT,
.is_webcam = 1,
[b].input = { {[/b]
[b].type = EM28XX_VMUX_COMPOSITE1,[/b]
[b].vmux = 0,[/b]
[b].amux = EM28XX_AMUX_VIDEO,[/b]
[b]} },[/b]
},
section a little further down.
Does that make sense, and what do you reckon ??
It may be a better idea just to wait for the cable, but I thought I’d post it anyway… even if it’s only something to try if the cable doesn’t work…
BTW, have you ever tested the mic input socket on your built-in soundcard ? … the reason I ask is that it’s an Intel HD audio device, so that may need a little tweaking to make work too… that should be a fairly easy fix though, if it’s necessary at all 
[EDIT]
Thinking about it… maybe just changing the sudo modprobe em28xx card=(n) to whatever the Videology 20K14XUSB USB2.0 is, would do the trick ?