Tvheadend

No - /dev/dvb/adapterXX is the normal path.

What version of tvh? Adapter enabled? Muxes added from <pick a network> or by hand? And are they right - many countries have moved things around and the databases are frequently behind...?

Prof,

Thanks for reply, I'll have to check TV Headend version later as Pi running off portable power supply which is now dead

Adapter enabled? I assume so, from the config page I select the only available adapter.

Muxes, tried both. Use the UK Crystal Palace database which appear correct and I have truid manually using frequencies obtained from my TV signal page.

Geffers

I've heard many tales of Pis having issues with USB power, so check that you've got a decent power supply feeding both system and USB hub if relevant. Check your cables as well.

Re: enabling the tuner, just because it's showing doesn't mean it's enabled: there's a specific checkbox on each tuner to enable it before it can be used. Post some screenshots if you want and I'll see if there's anything untoward.

Was hoping your suggestion about PSU was my problem as I was running the Pi off a portable PSU but alas no, used a 2amp PSUapparently designed for the Pi.

No need for hub as Pi has 4 USB ports and only a low powered wifi adapter using one.

TH Headend version is HTS Tvheadend 3.4~wheezy

Found the box for enabling adapter and yes, it was enabled.

Two image files attached from the configuration page.

Geffers

Yes, you have it enabled. It was an idiot suggestion, but you'd be surprised how often it's gone unnoticed...

While you have muxes defined, tvh hasn't found any DVB signals on them - hence the lack of NetworkID and MuxID in your 'Multiplexes' tab. Looking at ukfree.tv, only some of the frequencies seem to make sense, so I'd suggest deleting the mux definitions you have and adding them as per the details here (assuming there's only one Crystal Palace transmitter):

http://www.ukfree.tv/transmitters/tv/Crystal_Palace

It's been a while since I've added anything to 3.4, so this may be slightly out - apologies in advance if it is - but you should be able to add them by only specifying a couple of parameters. Try adding the muxes from that page as (e.g.) frequency = 490000 kHz, bandwidth = 8MHz, QAM64, everything else auto. HD muxes (e.g. PSB3) (if your tuner supports them) are QAM256.

Prof,

Thanks for suggestion, tried the first one, restarted TV Headend and the scan produced nothing.

I know on the Raspberry-Pi compatibility page some TV tuners seem to work only with a powered hub although this Hauppage is not specifically mentioned.

I'll get hold of a powered hub and give that a try as at the moment I am not sure what else to do.

Geffers

If you want to give it a whirl, you can always eliminate tvh by trying w_scan and similar to see if that can find channels.

You could also look into upgrading to a newer (pre-release) version of the software - 3.4 is looking kind of old now. There are later ARM builds for Wheezy in the unstable repo, although they're a couple of months out of date. It's easy enough to build your own, though (or it should be), assuming someone on #hts doesn't have a build to hand for you.

Prof,

I tried TV headend in my Laptop Ubuntu version 14.04 and still it didn't find anything. I think that eliminates the power problem with the Pi and I am thinking it could be a firmware problem and not a TV headend problem.

That leaves me a bit stuck as I am not sure how to proceed with that.

Geffers

What does syslog say when you plug the tuner in - if the firmware is valid, you should get a message along the lines of 'found XYZ in a warm state, loading firmware...'. That said, I wouldn't expect it to appear in the webUI if the firmware was bad, but it's worth a check.

lsusb might give you some more info on the tuner itself. lsmod should tell you what drivers it's using, if any.

It's a hybrid analogue/digital device, isn't it? I wonder if that's relevant.

You could try a later version of tvheadend as well, see if that's happier given the change in the way in which the tuner:network relationship is handled - that's easy to install on your laptop, at least (just add the unstable PPA and apt-get update).