Linux Format forums

Re: Nova-HD-S2 faulty card or duff drivers

bobthebob1234 — Tue Nov 20, 2012 10:44 pm

Author: bobthebob1234

Posted: Tue Nov 20, 2012 10:44 pm

Right it has happened again. The channel 5* seems to be one of its triggers...
First signs of something going wrong are here

Code:

Nov 20 21:33:01 civo mythbackend[1804]: E DVBRead dvbstreamhandler.cpp:214 (RunTS) DVBSH(/dev/dvb/adapter0/frontend0): Device EOF detected

then some stuff about the previous recording which did work

Code:

Nov 20 21:33:01 civo mythbackend[1804]: E CoreContext mainserver.cpp:871 (customEvent) MainServer: PREVIEW_SUCCESS but no receivers.

then

Code:

Nov 20 21:33:13 civo mythbackend[1804]: I Scheduler scheduler.cpp:2080 (HandleReschedule) Reschedule interrupted, will retry
Nov 20 21:33:13 civo mythbackend[1804]: I Scheduler scheduler.cpp:2033 (HandleReschedule) Reschedule requested for id 0.
Nov 20 21:33:25 civo mythbackend[1804]: I Scheduler scheduler.cpp:2093 (HandleReschedule) Scheduled 750 items in 12.0 = 0.00 match + 12.00 place
Nov 20 21:33:46 civo mythbackend[1804]: I Metadata_3053 jobqueue.cpp:2151 (DoMetadataLookupThread) JobQueue: Metadata Lookup Starting for "New Girl":"Bad in Bed" recorded from channel 9305 at 2012-11-20T20:57:00
Nov 20 21:33:47 civo mythbackend[1804]: I ProcessRequest mainserver.cpp:1360 (HandleAnnounce) MainServer::ANN Monitor
Nov 20 21:33:47 civo mythbackend[1804]: I ProcessRequest mainserver.cpp:1362 (HandleAnnounce) adding: civo as a client (events: 0)
Nov 20 21:33:47 civo mythbackend[1804]: I ProcessRequest mainserver.cpp:1360 (HandleAnnounce) MainServer::ANN Monitor
Nov 20 21:33:47 civo mythbackend[1804]: I ProcessRequest mainserver.cpp:1362 (HandleAnnounce) adding: civo as a client (events: 1)

which may or may not be connected, then we get something more interesting

Code:

Nov 20 21:34:02 civo mythbackend[1804]: E DVBRead dtvsignalmonitor.cpp:321 (HandlePAT) DTVSM(/dev/dvb/adapter0/frontend0): Program #1413 not found in PAT!#012Program Association Section#012 PSIP tableID(0x0) length(81) extension(0x7e5)#012 version(27) current(1) section(0) last_section(0)#012 tsid(2021) programCount(18)#012 program number 0 has PID 0x0010#012 program number 4214 has PID 0x0101#012 program number 5515 has PID 0x010c#012 program number 1306 has PID 0x010f#012 program number 1307 has PID 0x0110#012 program number 4208 has PID 0x0100#012 program number 4219 has PID 0x0103#012 program number 4216 has PID 0x0102#012 program number 4511 has PID 0x0107#012 program number 4221 has PID 0x0104#012 program number 4513 has PID 0x0108#012 program number 5522 has PID 0x010e#012 program number 1403 has PID 0x0106#012 program number 6040 has PID 0x0113#012 program number 6036 has PID 0x0111#012 program number 5500 has PID 0x0105#012 program number 8015 has PID 0x0135#012 program number 8058 has PID 0x0109
Nov 20 21:34:03 civo mythbackend[1804]: E DVBRead mpeg/mpegstreamdata.cpp:819 (ProcessPAT) ProcessPAT: Program not found in PAT. Rescan your transports.
Nov 20 21:34:03 civo mythbackend[1804]: E DVBRead mpeg/mpegstreamdata.cpp:425 (CreatePATSingleProgram) Desired program #1413 not found in PAT.#012#011#011#011Cannot create single program PAT.

Then some houskeeping and handleannouce's then

Code:

Nov 20 21:50:31 civo mythbackend[1804]: E DVBRead dtvsignalmonitor.cpp:321 (HandlePAT) DTVSM(/dev/dvb/adapter0/frontend0): Program #7851 not found in PAT!#012Program Association Section#012 PSIP tableID(0x0) length(17) extension(0x7ef)#012 version(22) current(1) section(0) last_section(0)#012 tsid(2031) programCount(2)#012 program number 4009 has PID 0x0100#012 program number 4040 has PID 0x0101
Nov 20 21:50:32 civo mythbackend[1804]: E DVBRead mpeg/mpegstreamdata.cpp:819 (ProcessPAT) ProcessPAT: Program not found in PAT. Rescan your transports.
Nov 20 21:50:32 civo mythbackend[1804]: E DVBRead mpeg/mpegstreamdata.cpp:425 (CreatePATSingleProgram) Desired program #7851 not found in PAT.#012#011#011#011Cannot create single program PAT.
Nov 20 21:54:39 civo mythbackend[1804]: I HouseKeeping housekeeper.cpp:225 (RunHouseKeeping) Running housekeeping thread
Nov 20 21:55:00 civo mythbackend[1804]: N Expire autoexpire.cpp:263 (CalcParams) AutoExpire: CalcParams(): Max required Free Space: 3.0 GB w/freq: 14 min
Nov 20 21:56:00 civo mythbackend[1804]: E DVBRead dtvsignalmonitor.cpp:321 (HandlePAT) DTVSM(/dev/dvb/adapter0/frontend0): Program #3843 not found in PAT!#012Program Association Section#012 PSIP tableID(0x0) length(33) extension(0x7f0)#012 version(4) current(1) section(0) last_section(0)#012 tsid(2032) programCount(6)#012 program number 3803 has PID 0x0101#012 program number 3841 has PID 0x0103#012 program number 3842 has PID 0x0100#012 program number 3874 has PID 0x0102#012 program number 3879 has PID 0x0109#012 program number 4034 has PID 0x0104
Nov 20 21:56:01 civo mythbackend[1804]: E DVBRead mpeg/mpegstreamdata.cpp:819 (ProcessPAT) ProcessPAT: Program not found in PAT. Rescan your transports.
Nov 20 21:56:01 civo mythbackend[1804]: E DVBRead mpeg/mpegstreamdata.cpp:425 (CreatePATSingleProgram) Desired program #3843 not found in PAT.#012#011#011#011Cannot create single program PAT.

then we get

Code:

Nov 20 21:57:00 civo mythbackend[1804]: W TVRecEvent dvbchannel.cpp:347 (CheckFrequency) DVBChan(2:/dev/dvb/adapter0/frontend0): Your frequency setting (10964250) is out of range. (min/max:950000/2150000)

Hmmm 10964250 does seem to be bigger than 2150000...
Possibly a mis configuration? I'm pretty sure I followed http://parker1.co.uk/mythtv_freesat.php to the letter...

The EOF stuff brings http://ubuntuforums.org/showthread.php?t=1983887 up on google, with no solution...

Full log here

Re: Nova-HD-S2 faulty card or duff drivers

wyliecoyoteuk — Sat Nov 17, 2012 4:29 pm

Author: wyliecoyoteuk

Posted: Sat Nov 17, 2012 4:29 pm

/var/log/mythtv is the place to start looking

Re: Nova-HD-S2 faulty card or duff drivers

bobthebob1234 — Fri Nov 16, 2012 7:39 pm

Author: bobthebob1234

Posted: Fri Nov 16, 2012 7:39 pm

Also get this come up when running frontend on different computer when trying to watch live tv when freesat tuner has gone odd:

Code:

2012-11-16 19:32:11.604263 I TV: Creating TV object
2012-11-16 19:32:11.693161 N Resuming idle timer
2012-11-16 19:32:11.693175 N Suspending idle timer
2012-11-16 19:32:11.702178 I TV: Created TvPlayWindow.
2012-11-16 19:32:11.786406 I TV: Attempting to change from None to WatchingLiveTV
2012-11-16 19:32:11.786457 I MythCoreContext: Connecting to backend server: 192.168.1.10:6543 (try 1 of 1)
2012-11-16 19:32:11.788273 I Using protocol version 72
2012-11-16 19:32:11.935077 I MythCoreContext: Connecting to backend server: 192.168.1.10:6543 (try 1 of 1)
2012-11-16 19:32:11.936651 I Using protocol version 72
2012-11-16 19:32:11.937298 N TV: Spawning LiveTV Recorder -- begin
2012-11-16 19:32:18.942020 E MythSocket(1f2da10:92): readStringList: Error, timed out after 7000 ms.
2012-11-16 19:32:18.942092 E RemoteEncoder::SendReceiveStringList(): No response.
2012-11-16 19:32:18.942115 N TV: Spawning LiveTV Recorder -- end
2012-11-16 19:32:18.943896 E GetEntryAt(-1) failed.
2012-11-16 19:32:18.943986 E It appears that your backend may be misconfigured. Check your backend logs to determine whether your capture cards, lineups, channels, or storage configuration are reporting errors. This issue is commonly caused by failing to complete all setup steps properly. You may wish to review the documentation for mythtv-setup.
2012-11-16 19:32:18.944077 E EntryToProgram(0@Thu Jan 1 01:00:00 1970) failed to get pginfo
2012-11-16 19:32:18.944093 E TV: HandleStateChange(): LiveTV not successfully started
2012-11-16 19:32:18.944153 E TV: LiveTV not successfully started
2012-11-16 19:32:18.954270 I TV: Main UI disabled.
2012-11-16 19:32:18.955121 I TV: Entering main playback loop.
2012-11-16 19:32:18.963726 I ScreenSaverX11Private: DPMS Deactivated 1
2012-11-16 19:32:18.965326 I TV: Exiting main playback loop.
2012-11-16 19:32:19.001674 N Resuming idle timer
2012-11-16 19:32:20.450988 I TV: Creating TV object
2012-11-16 19:32:20.479917 N Resuming idle timer
2012-11-16 19:32:20.479952 N Suspending idle timer
2012-11-16 19:32:20.483275 I TV: Created TvPlayWindow.
2012-11-16 19:32:20.567432 I TV: Attempting to change from None to WatchingLiveTV
2012-11-16 19:32:20.567475 I MythCoreContext: Connecting to backend server: 192.168.1.10:6543 (try 1 of 1)
2012-11-16 19:32:20.569141 I Using protocol version 72
2012-11-16 19:32:20.683573 I MythCoreContext: Connecting to backend server: 192.168.1.10:6543 (try 1 of 1)
2012-11-16 19:32:20.684524 I Using protocol version 72
2012-11-16 19:32:20.684886 N TV: Spawning LiveTV Recorder -- begin
2012-11-16 19:32:27.685299 E MythSocket(1e85170:92): readStringList: Error, timed out after 7000 ms.
2012-11-16 19:32:27.685372 E RemoteEncoder::SendReceiveStringList(): No response.
2012-11-16 19:32:27.685396 N TV: Spawning LiveTV Recorder -- end
2012-11-16 19:32:27.687165 E GetEntryAt(-1) failed.
2012-11-16 19:32:27.687180 E It appears that your backend may be misconfigured. Check your backend logs to determine whether your capture cards, lineups, channels, or storage configuration are reporting errors. This issue is commonly caused by failing to complete all setup steps properly. You may wish to review the documentation for mythtv-setup.
2012-11-16 19:32:27.687252 E EntryToProgram(0@Thu Jan 1 01:00:00 1970) failed to get pginfo
2012-11-16 19:32:27.687267 E TV: HandleStateChange(): LiveTV not successfully started
2012-11-16 19:32:27.687298 E TV: LiveTV not successfully started
2012-11-16 19:32:27.699391 I TV: Main UI disabled.
2012-11-16 19:32:27.700318 I TV: Entering main playback loop.
2012-11-16 19:32:27.701971 I ScreenSaverX11Private: DPMS Reactivated 1
2012-11-16 19:32:27.702949 I ScreenSaverX11Private: DPMS Deactivated 1
2012-11-16 19:32:27.703673 I TV: Exiting main playback loop.
2012-11-16 19:32:27.717046 N Resuming idle timer

Re: Nova-HD-S2 faulty card or duff drivers

bobthebob1234 — Fri Nov 16, 2012 6:24 pm

Author: bobthebob1234

Posted: Fri Nov 16, 2012 6:24 pm

Ok this is getting silly.

I am hopefully speaking too soon, but I have had to reboot 3 times in the past 48hrs to reset or whatever to make my new tuner work (straight replacement for the old one).

It also seems to take MythTV down with it, as I cannot get onto the web interface and it doesn't even try and record other stuff.

I think the USB freeview tuner I have continues to work though.

Any logs, etc I could take a look at to shine any more light?

The computer is on a surge protector, but I do notice the light flicker sometimes, so maybe we are having mini brown outs. Perhaps I will invest in a UPS.

Tis getting a tad annoying

Re: Nova-HD-S2 faulty card or duff drivers

sledgehammer — Sun Sep 02, 2012 9:09 pm

Author: sledgehammer

Posted: Sun Sep 02, 2012 9:09 pm

wyliecoyoteuk wrote:

No. Have you actually read the article in the link?
The term waveguide is not limited to RF signals.
The signal effectively travels in the electrical field between the core and the shield, which is why it is referred to as a "type of waveguide".
Which is incidentally why crushing or bending the wire stops the signal.

In your original reply you stated that the coax 'functions almost like a waveguide' ie you are recognising there is a difference between coax and waveguide. Either coax is or isn't waveguide, which is it?

I would say that coax and 'empty box' waveguides are type of waveguide in the same way that petrol and diesel are forms of petroleum but you wouldn't want to get them confused.

Coax will attenuate more as the frequency increases and supports modes that 'waveguide' does not, Waveguide only works above the cut off frequency as described in the link you have given.

I apologise for picking you up on 'waveguide' and you may still of course disagree, its a minor point and probably doesn't warrant a thread hijack.

Regards

Re: Nova-HD-S2 faulty card or duff drivers

wyliecoyoteuk — Sun Sep 02, 2012 5:52 pm

Author: wyliecoyoteuk

Posted: Sun Sep 02, 2012 5:52 pm

sledgehammer wrote:

wyliecoyoteuk wrote:

If you read the link in my post, there is a pretty clear explanation there.
The signal travels between the core and the shield as an AC electrical signal, not as radio wave. That is how capacitance and AC work. Basic stuff really.

I think that means you agree with me

Re: Nova-HD-S2 faulty card or duff drivers

sledgehammer — Sun Sep 02, 2012 10:53 am

Author: sledgehammer

Posted: Sun Sep 02, 2012 10:53 am

wyliecoyoteuk wrote:

I think that means you agree with me

Re: Nova-HD-S2 faulty card or duff drivers

wyliecoyoteuk — Thu Aug 30, 2012 9:56 am

Author: wyliecoyoteuk

Posted: Thu Aug 30, 2012 9:56 am

sledgehammer wrote:

wyliecoyoteuk wrote:

The Coax functions almost as a waveguide.

To become almost like a waveguide at UHF the co-ax has got to be above 6" diameter. Not a problem for us with our pathetically narrow co-ax but can be a problem for the broadcasters whose larger feeders are about 6"

S

Re: Nova-HD-S2 faulty card or duff drivers

sledgehammer — Wed Aug 29, 2012 9:45 pm

Author: sledgehammer

Posted: Wed Aug 29, 2012 9:45 pm

wyliecoyoteuk wrote:

The Coax functions almost as a waveguide.

Re: Nova-HD-S2 faulty card or duff drivers

dandnsmith — Wed Aug 29, 2012 7:30 am

Author: dandnsmith

Posted: Wed Aug 29, 2012 7:30 am

bobthebob1234 wrote:

Well I gave it to the garage round the corner hopefully the collect+ people will come get it and give it to dabs. Dabs have made an order on the website for me and say it will be shipped as soon as they get the broken one, we shall have to wait and see

If collect+ works I think it is a great idea!

I returned a motherboard package in this way a year (?) back - there was a short delay, but then a new item was shipped which worked with no problems. Interestingly, the detail was slightly different from the original, which means that, either they'd had other problems with that deal, or the original stock had run out.

Re: Nova-HD-S2 faulty card or duff drivers

bobthebob1234 — Tue Aug 28, 2012 6:08 pm

Author: bobthebob1234

Posted: Tue Aug 28, 2012 6:08 pm

Bruno wrote:

On a serious note though, good luck with Dabs. I've had bad customer service from them in the (not recent) past re: returning faulty goods that are still under warranty. However, it was over 5 years ago and also since your purchase was made less than 6 months ago, your mileage may vary.

Re: Nova-HD-S2 faulty card or duff drivers

wyliecoyoteuk — Tue Aug 28, 2012 3:50 pm

Author: wyliecoyoteuk

Posted: Tue Aug 28, 2012 3:50 pm

Bruno wrote:

Hmmm, I'm not sure about your explanation here. I thought that once received by an antenna, the signal is no-longer a radio wave but an electrical current of radio frequency, no?

I'm pretty sure that the thick insulation between the core and the braid is to reduce the stray capacitance between the two, thus reducing attenuation in long cable runs, due to RC (or LC) losses.

The aerial and the cable are just a means of getting the RF signal to the tuner. whether it is a radio wave or an electrical current, it still operates at radio frequency, The Coax functions almost as a waveguide.
Unlike DC, AC exists within the dieletric, as a fluctuation between the shield and the core. That's how capacitance works.

http://en.wikipedia.org/wiki/Coaxial_cable#Signal_propagation

Re: Nova-HD-S2 faulty card or duff drivers

Ram — Tue Aug 28, 2012 3:44 pm

Author: Ram

Posted: Tue Aug 28, 2012 3:44 pm

Bruno wrote:

your mileage may vary.

Depends on the driver I suppose.

Re: Nova-HD-S2 faulty card or duff drivers

Bruno — Tue Aug 28, 2012 1:05 pm

Author: Bruno

Posted: Tue Aug 28, 2012 1:05 pm

No arguments, just discussions. It's difficult to establish that in print, I know

On a serious note though, good luck with Dabs. I've had bad customer service from them in the (not recent) past re: returning faulty goods that are still under warranty. However, it was over 5 years ago and also since your purchase was made less than 6 months ago, your mileage may vary.

Re: Nova-HD-S2 faulty card or duff drivers

bobthebob1234 — Tue Aug 28, 2012 12:52 pm

Author: bobthebob1234

Posted: Tue Aug 28, 2012 12:52 pm

Well whilst you to argue about how wires work, I have returned to dabs, hopefully I will get a new one soon and find it was the card not the drivers