Linux DVB driver = success

[tfylliv]

Just FYI. I might be confusing the terminology here a bit, I was thinking QAM = DVB-C = european. Which of course isn't true - QAM is just a modulation format.

I got confused because the source code in the linux kernel dvb subsytem talks about FE_QAM when they actually mean DVB-C. Ah well....

So r00st3r, I'm pretty sure I need to handle ATSC before you can get any further. Doesn't look like it is a big thing though, so stay tuned. Might be ready in the next hour or so - then I'm going to bed.

[tfylliv]

Ok,

Just committed a bit of code that should handle ATSC HDHomeRun's.

r00st3r: If you could give that a try that would be great (and thanks for the help so far!!).

If you haven't already checked out via CVS, please do that:

sudo apt-get install cvs

cvs -z3 -d:pserver:anonymous@dvbhdhomerun.cvs.sourceforge.net:/cvsroot/dvbhdhomerun co -P dvbhdhomerun

Which will create a dvbhdhomerun directory.


Stop tvheadend
kernel/do.sh
userhdhomerun, make run.

After that you will be able to run scan with the ATSC definitions. E.g. the:

Code: Select all

scan /usr/share/dvb/atsc/us-MA-Boston

Which failed before should work now.

Going to bed now, but will be back tomorrow.

[tfylliv]

I forgot.

Userhdhomerun will now print out: "Type of device:" which in your case should be: "hdhomerun_atsc".

And after starting tvheadend two new devices: "HDHomeRun ATSC".

But please try the scan cmd line first.

[r00st3r]

Just about to leave work..looks like your going to bed.. Ah Time Travel..

I will give this a shot a bit later when I'm home or maybe tomorrow. I will report back.

[r00st3r]

Ok, I grabbed the cvs and re-ran

/kernel//sudo dh.so

/userhdhomerun/sudo make run

I stopped it, and restarted tvheadend : sudo service tvheadend start

Went into tvheadend web interface http://xbmc:9981

Went to TV Adapters and the ATSC tuners where there.
Clicked on Add DVB Network by Location and selected:
United States-Cable-Standard_Center- Frequencies-QAM256

This put records into the multiplexes tab

The status on the tuner is:
Status
Currently tuned to:
315,012 kHz
Services:
0
Muxes:
124
Muxes awaiting initial scan:
87

So far I have no services, but I will wait till morning to see what happens when it scans all the Muxes...

going to bed..you're probably getting up.. haha

[tfylliv]

Hi r00st3r,

I hope you had luck finding some services/channels?

If not, I happened to stumble upon this nice little tool: http://www.linuxtv.org/wiki/index.php/W_scan

With it you can scan without the initial /usr/share/dvb/atsc/* file (in fact it can create those files). Basically it scans everything and reports afterwards. I tried it here and works like a charm, but it took almost ½ hour.....

sudo apt-get install w-scan

w_scan -fa -A2 -c US -x

[Rigolo]

w_scan is like a brute force attack on the cable frequencies. But can't you get the transponder details from the normal way of operating the hdhoemrun?

There must be some way of getting that data?

I suspect you can already use the HD Homerun with some other application?

Hein

[r00st3r]

Well TVHeadEnd didn't find anything even though it found the Muxes, and the scan doesn't work either.

The HDHomeRun picks up the FIOS QAM (clear) channels and I have the .strm files on the XBMC, but do not work consistently.

[tfylliv]

Ok, I must be missing something for ATSC HDHomeRun's to work. I'll put my thinking hat on when I get back from work.

A quick question for the ATSC people out there: When you have tuned a channel and view it - what does your HDHomeRun Config (GUI) say the "physical channel" is?

HDHomeRun Config (GUI) -> Tuner -> Status -> Physical Channel

I have something like this:

"a8qam256-9600:56"
"a8qam256-9600:514000000"

[r00st3r]

Here's what mine says.

Using Verizon FIOS pulling in clear QAM channels using US-Cable.

[nickk]

If you use "auto" as the modulation type the HDHomeRun will auto-detect.

[tfylliv]

Hey nickk,

"auto:" is what I am using. The dvb subsystem in linux basically gives you this for tuning.

FE_SET_FRONTEND, freq: 346000000, inv: 2, symb rate: 6900000, fec: 0, mod: 3

From which I use the frequency like so: "auto:346000000" for the hdhomerun. Works like a charm for the european hdhomerun.

I'm most likely missing some minor detail with regards to setting up ATSC in the linux dvb subsystem - haven't found it yet though.

[tfylliv]

Hi r00st3r, Still there?

I've been looking a bit at the other ATSC dvb drivers in the linux kernel and can't really see that they are doing anything other than what I am.

So, a basic sanity check is in order. I've comitted a bit debug information so we hopefully can see where it fails.

1) In the directory where you checked out the source via CVS:

cvs update

(two files will be updated).

2) Stop tvheadend

3) The usual:

kernel/do.sh
cd userhdhomerun; make run

4) Now run this scan again: scan /usr/share/dvb/atsc/us-MA-Boston

In the cmd prompt where userhdhomerun runs (not where scan runs) you will get output like this:

FE_SET_FRONTEND, freq: 274000000, inv: 2, symb rate: 6900000, fec: 0, mod: 5
hdhomerun_device_set_tuner_channel: 1
hdhomerun_tuner_status_t: 1
FE_READ_STATUS

Please copy/paste say 30 lines of that and paste here.

[Mac The Knife]

Has there been any progress on the ATSC issue?

[tfylliv]

Hi Mac,

I haven't heard from anyone having success with an ATSC yet, no. But as far as I know only r00st3r from this thread has yet to try it on an ATSC HDHomeRun.

(I have a couple of positive reports on european HDHomeRun's).

Right now I'm in the process of making Ubuntu/Debian packages for the driver, so as to make much easier to install/test.

Should have something wrapped up during the week.