Tvheadend

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...

This is my output..

ryan@mhts:/dev$ ls -la vid*
crw-rw----+ 1 root video 81, 0 Apr 18 06:33 video0

ryan@mhts:/dev$ ls -la /dev/dvb
total 0
drwxr-xr-x  3 root root   60 Apr 18 06:32 .
drwxr-xr-x 17 root root 4160 Apr 18 06:33 ..
drwxr-xr-x  2 root root  120 Apr 18 06:33 adapter0

ryan@mhts:/dev$ ps -eaf | grep tvheadend
ryan      3653  3405  0 18:31 pts/0    00:00:00 grep --color=auto tvheadend

The only difference I see from your output to my output is the your last line output ( hts 10562 1 2 Apr15 ? 01:52:31 tvheadend -f -u hts -g video)

How do I correct this ?

That suggests that tvheadend isn't even running, otherwise it'd show up in the process list. Can you do a sudo service tvheadend restart and check again?

Also, dig into syslog, that should tell you something about what tvheadend sees in the way of your adapters as it starts. So the restart will trigger those messages into the logfile.

1 thing i can't find is and if you point where it is.
I'm looking for the tvheadend log files. where is it located ?

I'm restarting everything from scratch and I need to know where the log file is located.

Thanks

On an Ubuntu system, tvheadend outputs its activities to /var/log/syslog.

This file gets cycled regularly, so yesterday's will be /var/log/syslog.1 and earlier ones are then compressed, so previous files are /var/log/syslog.xxx.gz where xxx is the sequence number (2, 3, 4...).

You can extract all tvheadend message from this with grep tvheadend syslog. I get lines like the following:

Apr 19 10:41:38 Server tvheadend[25220]: dvb: Found adapter /dev/dvb/adapter0 (DiBcom 7000PC) via USB (480 Mbit/s)
Apr 19 10:41:38 Server tvheadend[25220]: dvb: Found adapter /dev/dvb/adapter1 (NXP TDA10071) via USB (480 Mbit/s)
Apr 19 10:41:38 Server tvheadend[25220]: dvb: Adapter /dev/dvb/adapter0 will run in filtered mode
Apr 19 10:41:38 Server tvheadend[25220]: dvb: Adapter /dev/dvb/adapter1 will run in filtered mode
Apr 19 10:41:41 Server tvheadend[25220]: v4l: /dev/video0: em28xx PCTV DVB-S2 Stick (460e) usb-0000:00:14.0-4 capabilities: 0x05000041

... it's probably best if you dump all your tvheadend output to a file and pastebin it somewhere - xbmclogs.com, for example.

When you switch debugging on in tvheadend (the gear icon on the web interface), it increases the number of entries written to the log file - but it's the same log file. You can also switch on more debugging by editing the file /etc/default/tvheadend, and changing the line DEBUG=0 to DEBUG=1 - and then restarting tvheadend with sudo service tvheadend restart. Try that to get an even more informative log, and then paste that.

Note that this will tell us what tvheadend is seeing, not what the OS is seeing. You'll still get "loading firmware..." messages in syslog, but let's see what tvheadend is complaining about first.

Thanks..
I will post my syslog when I have everything setup from clean install.

BTW: Do you know if this wiki still valid for tvheadend 3.0 ? https://tvheadend.org/projects/tvheadend/wiki/Tvheadend_NTSC

Pass, I'm afraid - tvheadend itself hasn't changed much in terms of structure, but I can't comment on anything NTSC-specific.

[email protected] wrote:

https://tvheadend.org/boards/5/topics/8321?r=8333#message-8333
Ryan Baray

Thanks..
I will post my syslog when I have everything setup from clean install.

BTW: Do you know if this wiki still valid for tvheadend 3.0 ?
https://tvheadend.org/projects/tvheadend/wiki/Tvheadend_NTSC

--
You have received this notification because you have either subscribed
to it, or are involved in it.
To change your notification preferences, please click here:
https://tvheadend.org/my/account

This is what I'm getting on the log.

v4l: /dev/video0: Device lacks MPEG encoder, device skipped

Anyway to resolve this or is it really the hardware?
If it's the hardware.. Why would it work on mplayer with no problem? I mean running $mplayer /dev/video0

I got the /dev/video0 now set.
BUT I don't have an option to scan the channels.

Would you or anyone know a way for me to scan the channels?
In the services tab I can simply enter the Hz, but again I don't know the Hz for each channels I want to add.

I used scantv and it works perfect.

http://imageshack.us/photo/my-images/688/video0.png/