The Samsung is almost certainly the chipset in your Hauppauge card, so that's fine.
Have a look in syslog and see what tvheadend says as it initialises... it should tell you that it can find the adapter and what it's calling it (so, in this case, I'd expect /dev/dvb/adapter0).
If that's there and appears well, the next thing to check is permissions: what user are you running tvheadend under, what user is the adapter file owned by, does one have access to the other, etc.
I'd check /dev/video0 as well. This is what mine looks like (Precise):
ian@Server:/dev$ ls -la vid*
crw-rw----+ 1 root video 81, 0 Apr 9 13:58 video0
ian@Server:/dev$ ls -la /dev/dvb
total 0
drwxr-xr-x 4 root root 80 Apr 15 12:25 .
drwxr-xr-x 17 root root 4400 Apr 18 17:19 ..
drwxr-xr-x 2 root root 120 Apr 15 12:25 adapter0
drwxr-xr-x 2 root root 120 Apr 9 13:58 adapter1
ian@Server:/dev$ ps -eaf | grep tvheadend
ian 8404 8264 0 20:24 pts/2 00:00:00 grep --color=auto tvheadend
hts 10562 1 2 Apr15 ? 01:52:31 tvheadend -f -u hts -g video
You can see that I'm running tvheadend as hts/video, which means it has r-x access to the adapters and rw- to /dev/video0.
In tvheadend (Configuration -> DVB Inputs -> TV Adapters, though that might change if you're on a different release), then, I have my two adapters:
Hardware
Device path:
/dev/dvb/adapter0
Device name:
DiBcom 7000PC
Hardware
Device path:
/dev/dvb/adapter1
Device name:
NXP TDA10071
See if that helps point you in the right direction at all...
