Autor Thema: Going insane, wierd driver/application behaviour?  (Gelesen 12798 mal)

Phr0z

  • Newbie
  • *
  • Beiträge: 6
    • Profil anzeigen
Going insane, wierd driver/application behaviour?
« am: Oktober 19, 2015, 02:56:17 Nachmittag »
Hi,

Okay, so Im facing this really wierd issue and Im not really sure where to begin so I hope you guys can help me.

I currently own the USB Sundtek MediaTV PRO (II) DVBC/DVBT version.

Im running it successfully on my Intel NUC DC3217IYE with the latest OpenELEC version (5.95.5) and TVHeadend, which downloaded through the Unofficial OpenELEC Repo. I SAN-boot into OpenELEC with iPXE/NFS.

I believe the versions installed to date is;
/storage/.kodi/addons/service.multimedia.tvheadend/changelog.txt -> 6.0.1
cat /storage/.kodi/addons/driver.dvb.sundtek-mediatv/version.used -> sundtek_installer_150907.163414.sh

So, everything is working fine and dandy while running OpenELEC. I can tune to my dvbc network channels without any problems at all.

Now, I purchased a SSD and decided to migrate to Kodibuntu while Im at it.

Said and done I downloaded the latest version of Kodibuntu from kodi.tv which is kodi14 helix.
root@htpc:/home/kodi# uname -a
Linux htpc 4.1.1-040101-generic #201507030635 SMP Fri Jul 3 10:38:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Distributor ID: Ubuntu
Description: Ubuntu 14.04.3 LTS
Release: 14.04
Codename: trusty

It installs and boot up fine from my SSD.

I've download your latest driver from http://sundtek.com/media/ (tried both "full" and netinst). And install it successfully.
Add the nightly build from official Tvheadend apt repo and install it. (4.1-647~g4f557c7).

root@htpc:/home/kodi# mediaclient -e
**** List of Media Hardware Devices ****
device 0: [Sundtek MediaTV Pro (USB 2.0)]  DVB-C, DVB-T, ANALOG-TV, FM-RADIO, REMOTE-CONTROL, OSS-AUDIO, RDS
  [INFO]:
     STATUS: STANDBY
  [BUS]:
     ID: 2-1.2.3
  [SERIAL]:
     ID: ---------------- (removed)
  [DVB-C]:
     FRONTEND: /dev/dvb/adapter0/frontend0
     DVR: /dev/dvb/adapter0/dvr0
     DMX: /dev/dvb/adapter0/demux0
  [DVB-T]:
     FRONTEND: /dev/dvb/adapter0/frontend0
     DVR: /dev/dvb/adapter0/dvr0
     DMX: /dev/dvb/adapter0/demux0
  [ANALOG-TV]:
     VIDEO0: /dev/video0
     VBI0: /dev/vbi0
  [FM-RADIO]:
     RADIO0: /dev/radio0
     RDS: /dev/rds0
  [REMOTECONTROL]:
     INPUT0: /dev/mediainput0
  [OSS]:
     OSS0: /dev/dsp0

root@htpc:/home/kodi# mediaclient --lc
**** List of Media Clients ****
/dev/dvb/adapter0/frontend0:
  859 ... tvheadend
/dev/dvb/adapter0/dvr0:
  No client connected
/dev/dvb/adapter0/demux0:
  No client connected
/dev/video0:
  No client connected
/dev/vbi0:
  No client connected
/dev/radio0:
  No client connected
/dev/rds0:
  No client connected
/dev/mediainput0:
  No client connected
/dev/dsp0:
  No client connected

It seems like everything is detected? I can see the adapter in TVheadend as well.

But Im not getting any signal?
2015-10-19 11:20:27.000 mpegts: 354MHz in CD - scan no data, failed

I've tried w_scan just to see if I can get any signals at all, but it fails to lock onto any muxes?

Running mediaclient -m DVBC -f (to known working mux) doesn't give me a lock just one .dot.

The fundamental problem seems to be that it's unable to get/detect any signals, which leads me to believe it's driver related.

Note that I do not do any changes but boot from my SSD instead off the network. (so no usb port switching etc.).

Now, to get even more confused, I own a Synology NAS (DS413). So I thought, hey, i'll try your driver and install it on my NAS instead.
.... It's not working. Tried sharing the tuner via network. No go.

Im going insane... I remember running Ubuntu 12.04 with this stick and Tvheadend about 2 years ago?

What has changed?


Please help, let me know what you need.

Thank you :-)



Sundtek

  • Administrator
  • Hero Member
  • *****
  • Beiträge: 8604
    • Profil anzeigen
Re:Going insane, wierd driver/application behaviour?
« Antwort #1 am: Oktober 19, 2015, 03:38:24 Nachmittag »
Hi,

we will test the latest tvheadend version today and update this post as soon as possible.
Failure is a good thing! I'll fix it

Phr0z

  • Newbie
  • *
  • Beiträge: 6
    • Profil anzeigen
Re:Going insane, wierd driver/application behaviour?
« Antwort #2 am: Oktober 19, 2015, 03:55:11 Nachmittag »
Hi,

we will test the latest tvheadend version today and update this post as soon as possible.

Hi,

That's great, but it won't help me.

I've tried 3.4.28~geb79aee~trusty, and I get the same error there.


ct 19 15:49:03.593 dvb: Adapter "Sundtek DVB-C" Enabled
Oct 19 15:49:06.683 dvb: Adapter /dev/dvb/adapter0 will run in full mux mode
Loglevel debug: enabled
Oct 19 15:49:46.000 dvb: "/dev/dvb/adapter0" tuning to "426,000 kHz" (Initial autoscan)
Oct 19 15:49:52.023 dvb: "426,000 kHz" on adapter "Sundtek DVB-C", status changed to No signal
Oct 19 15:50:06.000 dvb: "/dev/dvb/adapter0" tuning to "418,000 kHz" (Initial autoscan)
Oct 19 15:50:12.060 dvb: "418,000 kHz" on adapter "Sundtek DVB-C", status changed to No signal

The only difference I can see between Kodibuntu and OpenELEC is that when running mediaclient --lc.

On kodibuntu it shows.
root@htpc:/home/kodi# mediaclient --lc
**** List of Media Clients ****
/dev/dvb/adapter0/frontend0:
  4199 ... tvheadend
/dev/dvb/adapter0/dvr0:
  No client connected
/dev/dvb/adapter0/demux0:
  No client connected
/dev/video0:
  No client connected
/dev/vbi0:
  No client connected
/dev/radio0:
  No client connected
/dev/rds0:
  No client connected
/dev/mediainput0:
  No client connected
/dev/dsp0:
  No client connected

Whilst running the same command in OpenELEC gives a different result. (something like)
root@htpc:/home/kodi# mediaclient --lc
**** List of Media Clients ****
/dev/dvb/adapter0/frontend0:
  4199 ... tvheadend
/dev/dvb/adapter0/dvr0:
  No client connected <- tvheadend connects to dvr
/dev/dvb/adapter0/demux0:
  No client connected <- tvheadend connects to mux
/dev/video0:
  No client connected
/dev/vbi0:
  No client connected
/dev/radio0:
  No client connected
/dev/rds0:
  No client connected
/dev/mediainput0:
  No client connected
/dev/dsp0:
  No client connected

Thank you! :)
« Letzte Änderung: Oktober 19, 2015, 03:56:56 Nachmittag von Phr0z »

Phr0z

  • Newbie
  • *
  • Beiträge: 6
    • Profil anzeigen
Re:Going insane, wierd driver/application behaviour?
« Antwort #3 am: Oktober 19, 2015, 03:58:33 Nachmittag »
This is my sundtek.conf btw.

#
# sundtek.conf
#
autoupdate=on
dvb_api_version=5

# enable HW PID filter (default on for RPi)
use_hwpidfilter=on

# enable listening on network
enablenetwork=on

# Lowest adapter number to start with, e.g. /dev/dvb/adapter5/frontend0
first_adapter=0

# Infrared Control Support is disabled/enabled
ir_disabled=1

# trigger device_attach only once if more devices is used
bulk_notification=on


[xxxxxxxxxx]
initial_dvb_mode=DVBC

#[NETWORK]
#device=192.168.1.1:0
#device=192.168.1.1:1

root@htpc:/home/kodi# ls /dev/dvb/
adapter0
root@htpc:/home/kodi#

Sundtek

  • Administrator
  • Hero Member
  • *****
  • Beiträge: 8604
    • Profil anzeigen
Re:Going insane, wierd driver/application behaviour?
« Antwort #4 am: Oktober 19, 2015, 04:28:49 Nachmittag »
dvb_api_version=5
autoupdate=on
use_hwpidfilter=on

remove those options, only removing will not help you also need to restart the system and re-plug the device to reset the hwpid filter for example.


We have tested tvheadend (the latest git version) and everything works.
However we have seen your problem with a particular tvheadend version in the past on another customer's synology NAS. Updating tvheadend solved the problem for him.

We tested (latest Git version from 19th October 2015)
HTS Tvheadend 4.1-658~g1ca4f29

And the scan just works nicely.

could you set up google remote desktop and/or contact us via Skype (sundtek)?

Maybe it's just a bad setting somewhere on your side which causes this problem; As mentioned we have seen that but only with some particular Tvheadend version (which we already forgot about again).


This is what the scan looks like in the tvheadend logfile:
Zitat
2015-10-19 15:49:29.318 subscription: 004C: "scan" subscribing to mux "594MHz", weight: 5, adapter: "Sundtek DVB-C (III) : DVB-C #0", network: "Primacom", service: "Raw PID Subscription"
2015-10-19 15:49:43.000 mpegts: 594MHz in Primacom scan complete
2015-10-19 15:49:43.000 subscription: 004C: "scan" unsubscribing
2015-10-19 15:49:43.013 mpegts: 602MHz in Primacom - tuning on Sundtek DVB-C (III) : DVB-C #0
2015-10-19 15:49:43.382 opentv-skynz: registering mux 602MHz in Primacom
2015-10-19 15:49:43.386 subscription: 004E: "scan" subscribing to mux "602MHz", weight: 5, adapter: "Sundtek DVB-C (III) : DVB-C #0", network: "Primacom", service: "Raw PID Subscription"
2015-10-19 15:50:03.104 mpegts: 602MHz in Primacom scan complete
2015-10-19 15:50:03.104 subscription: 004E: "scan" unsubscribing
2015-10-19 15:50:03.112 mpegts: disabling service Primacom/602MHz/{PMT:105} [sid 0F03/3843] (missing in PAT/SDT)
2015-10-19 15:50:03.113 mpegts: 770MHz in Primacom - tuning on Sundtek DVB-C (III) : DVB-C #0
2015-10-19 15:50:03.471 opentv-skynz: registering mux 770MHz in Primacom
2015-10-19 15:50:03.475 subscription: 0050: "scan" subscribing to mux "770MHz", weight: 5, adapter: "Sundtek DVB-C (III) : DVB-C #0", network: "Primacom", service: "Raw PID Subscription"
2015-10-19 15:50:15.904 mpegts: 770MHz in Primacom scan complete
2015-10-19 15:50:15.904 subscription: 0050: "scan" unsubscribing
2015-10-19 15:50:15.916 mpegts: 778MHz in Primacom - tuning on Sundtek DVB-C (III) : DVB-C #0
2015-10-19 15:50:16.284 opentv-skynz: registering mux 778MHz in Primacom
2015-10-19 15:50:16.288 subscription: 0052: "scan" subscribing to mux "778MHz", weight: 5, adapter: "Sundtek DVB-C (III) : DVB-C #0", network: "Primacom", service: "Raw PID Subscription"
2015-10-19 15:50:26.859 bouquet: new bouquet 'ARD Digital'
2015-10-19 15:50:29.002 mpegts: 778MHz in Primacom scan complete
2015-10-19 15:50:29.002 subscription: 0052: "scan" unsubscribing
2015-10-19 15:50:29.013 mpegts: 786MHz in Primacom - tuning on Sundtek DVB-C (III) : DVB-C #0
2015-10-19 15:50:29.372 opentv-skynz: registering mux 786MHz in Primacom
2015-10-19 15:50:29.376 subscription: 0054: "scan" subscribing to mux "786MHz", weight: 5, adapter: "Sundtek DVB-C (III) : DVB-C #0", network: "Primacom", service: "Raw PID Subscription"
2015-10-19 15:50:34.000 mpegts: 786MHz in Primacom scan complete
2015-10-19 15:50:34.000 subscription: 0054: "scan" unsubscribing
2015-10-19 15:50:34.013 mpegts: 794MHz in Primacom - tuning on Sundtek DVB-C (III) : DVB-C #0
2015-10-19 15:50:34.372 opentv-skynz: registering mux 794MHz in Primacom
2015-10-19 15:50:34.376 subscription: 0056: "scan" subscribing to mux "794MHz", weight: 5, adapter: "Sundtek DVB-C (III) : DVB-C #0", network: "Primacom", service: "Raw PID Subscription"
2015-10-19 15:50:44.149 bouquet: new bouquet 'ARD Digital'
2015-10-19 15:50:46.003 mpegts: 794MHz in Primacom scan complete
2015-10-19 15:50:46.003 subscription: 0056: "scan" unsubscribing
« Letzte Änderung: Oktober 19, 2015, 04:35:09 Nachmittag von Sundtek »
Failure is a good thing! I'll fix it

Sundtek

  • Administrator
  • Hero Member
  • *****
  • Beiträge: 8604
    • Profil anzeigen
Re:Going insane, wierd driver/application behaviour?
« Antwort #5 am: Oktober 19, 2015, 04:39:03 Nachmittag »
Do you see the difference? We see everything in MHz, you see it in KHz?!

/opt/bin/mediaclient --readsignal=0 -d /dev/dvb/adapter0/frontend0

0 -> infinite, any other number means how many times the signal statistics should be read

will show up the signalstatistic of the tuner.

If it remains on "LOCKED: NO" then you really do not have any signal on the cable.
Better post the output of some lines and let me explain the result to you.

As mentioned you can still contact us via Skype (sundtek) to go over your issue quickly. The problem I see is that the way how to configure tvheadend changed a little bit.
« Letzte Änderung: Oktober 19, 2015, 06:42:47 Nachmittag von Sundtek »
Failure is a good thing! I'll fix it

Phr0z

  • Newbie
  • *
  • Beiträge: 6
    • Profil anzeigen
Re:Going insane, wierd driver/application behaviour?
« Antwort #6 am: Oktober 19, 2015, 07:53:21 Nachmittag »
I removed pidfilter, autoupdate and dvbapi setting. unplugged it for 5 minutes.

I'll try to contact you on Skype.

readsignal on kodibuntu installation.
root@htpc:/home/kodi# /opt/bin/mediaclient --readsignal=0 -d /dev/dvb/adapter0/frontend0
== reading digital TV signal ==
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 386000000  Hz LOCKED:  NO MER: 0 SYM: 6950000 MOD: QAM64
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 378000000  Hz LOCKED:  NO MER: 0 SYM: 6950000 MOD: QAM64
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 378000000  Hz LOCKED:  NO MER: 0 SYM: 6950000 MOD: QAM64
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 370000000  Hz LOCKED:  NO MER: 0 SYM: 6950000 MOD: QAM64
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 370000000  Hz LOCKED:  NO MER: 0 SYM: 6950000 MOD: QAM64
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 362000000  Hz LOCKED:  NO MER: 0 SYM: 6950000 MOD: QAM64
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 362000000  Hz LOCKED:  NO MER: 0 SYM: 6950000 MOD: QAM64
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 354000000  Hz LOCKED:  NO MER: 0 SYM: 6950000 MOD: QAM64
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 354000000  Hz LOCKED:  NO MER: 0 SYM: 6950000 MOD: QAM64
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 354000000  Hz LOCKED:  NO MER: 0 SYM: 6950000 MOD: QAM64
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 354000000  Hz LOCKED:  NO MER: 0 SYM: 6950000 MOD: QAM64
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 354000000  Hz LOCKED:  NO MER: 0 SYM: 6950000 MOD: QAM64
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 354000000  Hz LOCKED:  NO MER: 0 SYM: 6950000 MOD: QAM64
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 354000000  Hz LOCKED:  NO MER: 0 SYM: 6950000 MOD: QAM64
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 354000000  Hz LOCKED:  NO MER: 0 SYM: 6950000 MOD: QAM64
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 354000000  Hz LOCKED:  NO MER: 0 SYM: 6950000 MOD: QAM64
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 354000000  Hz LOCKED:  NO MER: 0 SYM: 6950000 MOD: QAM64
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 354000000  Hz LOCKED:  NO MER: 0 SYM: 6950000 MOD: QAM64
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 354000000  Hz LOCKED:  NO MER: 0 SYM: 6950000 MOD: QAM64
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 354000000  Hz LOCKED:  NO MER: 0 SYM: 6950000 MOD: QAM64
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 354000000  Hz LOCKED:  NO MER: 0 SYM: 6950000 MOD: QAM64
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 354000000  Hz LOCKED:  NO MER: 0 SYM: 6950000 MOD: QAM64
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 354000000  Hz LOCKED:  NO MER: 0 SYM: 6950000 MOD: QAM64
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 354000000  Hz LOCKED:  NO MER: 0 SYM: 6950000 MOD: QAM64
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 354000000  Hz LOCKED:  NO MER: 0 SYM: 6950000 MOD: QAM64
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 354000000  Hz LOCKED:  NO MER: 0 SYM: 6950000 MOD: QAM64


readsignal on openelec installation after tuning in to a channel.
root@kodi:/mediaclient --readsignal=0 -d /dev/dvb/adapter0/frontend0
== reading digital TV signal ==
SIGNAL: [.................................] (100%)  BER:      0 FREQ: 418000000                                                                                Hz LOCKED: YES MER: 359 SYM: 6950000 MOD: QAM256
SIGNAL: [.................................] (100%)  BER:      0 FREQ: 418000000                                                                                Hz LOCKED: YES MER: 358 SYM: 6950000 MOD: QAM256
SIGNAL: [.................................] (100%)  BER:      0 FREQ: 418000000                                                                                Hz LOCKED: YES MER: 356 SYM: 6950000 MOD: QAM256
SIGNAL: [.................................] (100%)  BER:      0 FREQ: 418000000                                                                                Hz LOCKED: YES MER: 354 SYM: 6950000 MOD: QAM256
SIGNAL: [.................................] (100%)  BER:      0 FREQ: 418000000                                                                                Hz LOCKED: YES MER: 354 SYM: 6950000 MOD: QAM256
SIGNAL: [.................................] (100%)  BER:      0 FREQ: 418000000                                                                                Hz LOCKED: YES MER: 354 SYM: 6950000 MOD: QAM256
SIGNAL: [.................................] (100%)  BER:      0 FREQ: 418000000                                                                                Hz LOCKED: YES MER: 356 SYM: 6950000 MOD: QAM256
SIGNAL: [.................................] (100%)  BER:      0 FREQ: 418000000                                                                                Hz LOCKED: YES MER: 356 SYM: 6950000 MOD: QAM256
SIGNAL: [.................................] (100%)  BER:      0 FREQ: 418000000  Hz LOCKED: YES MER: 357 SYM: 6950000 MOD: QAM256
SIGNAL: [.................................] (100%)  BER:      0 FREQ: 418000000  Hz LOCKED: YES MER: 357 SYM: 6950000 MOD: QAM256
SIGNAL: [.................................] (100%)  BER:      0 FREQ: 418000000  Hz LOCKED: YES MER: 353 SYM: 6950000 MOD: QAM256
SIGNAL: [.................................] (100%)  BER:      0 FREQ: 418000000  Hz LOCKED: YES MER: 356 SYM: 6950000 MOD: QAM256
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 450000000  Hz LOCKED: YES MER: 341 SYM: 6950000 MOD: QAM256
SIGNAL: [.............                    ] ( 39%)  BER:  41248 FREQ: 450000000  Hz LOCKED: YES MER: 302 SYM: 6950000 MOD: QAM256
SIGNAL: [.............                    ] ( 39%)  BER:     73 FREQ: 450000000  Hz LOCKED: YES MER: 301 SYM: 6950000 MOD: QAM256
SIGNAL: [..............................   ] ( 90%)  BER:     73 FREQ: 450000000  Hz LOCKED: YES MER: 301 SYM: 6950000 MOD: QAM256
SIGNAL: [.................................] ( 99%)  BER:     12 FREQ: 450000000  Hz LOCKED: YES MER: 338 SYM: 6950000 MOD: QAM256
SIGNAL: [.................................] ( 99%)  BER:     12 FREQ: 450000000  Hz LOCKED: YES MER: 300 SYM: 6950000 MOD: QAM256
SIGNAL: [...................              ] ( 57%)  BER:    305 FREQ: 450000000  Hz LOCKED: YES MER: 308 SYM: 6950000 MOD: QAM256
SIGNAL: [.............                    ] ( 40%)  BER:    305 FREQ: 450000000  Hz LOCKED: YES MER: 305 SYM: 6950000 MOD: QAM256
SIGNAL: [.............                    ] ( 40%)  BER:     32 FREQ: 450000000  Hz LOCKED: YES MER: 352 SYM: 6950000 MOD: QAM256
SIGNAL: [................................ ] ( 96%)  BER:     32 FREQ: 450000000  Hz LOCKED: YES MER: 348 SYM: 6950000 MOD: QAM256
SIGNAL: [................................ ] ( 96%)  BER:     32 FREQ: 450000000  Hz LOCKED: YES MER: 313 SYM: 6950000 MOD: QAM256
SIGNAL: [................                 ] ( 48%)  BER:    522 FREQ: 450000000  Hz LOCKED: YES MER: 307 SYM: 6950000 MOD: QAM256
SIGNAL: [.............                    ] ( 40%)  BER:    522 FREQ: 450000000  Hz LOCKED: YES MER: 351 SYM: 6950000 MOD: QAM256
SIGNAL: [.............                    ] ( 40%)  BER:     23 FREQ: 450000000  Hz LOCKED: YES MER: 341 SYM: 6950000 MOD: QAM256
SIGNAL: [................................ ] ( 97%)  BER:     23 FREQ: 450000000  Hz LOCKED: YES MER: 305 SYM: 6950000 MOD: QAM256
SIGNAL: [.....................            ] ( 63%)  BER:    262 FREQ: 450000000  Hz LOCKED: YES MER: 308 SYM: 6950000 MOD: QAM256
SIGNAL: [.............                    ] ( 40%)  BER:    262 FREQ: 450000000  Hz LOCKED: YES MER: 306 SYM: 6950000 MOD: QAM256
SIGNAL: [.............                    ] ( 40%)  BER:     27 FREQ: 450000000  Hz LOCKED: YES MER: 339 SYM: 6950000 MOD: QAM256
SIGNAL: [................................ ] ( 97%)  BER:     27 FREQ: 450000000  Hz LOCKED: YES MER: 302 SYM: 6950000 MOD: QAM256
SIGNAL: [......................           ] ( 68%)  BER:    228 FREQ: 450000000  Hz LOCKED: YES MER: 311 SYM: 6950000 MOD: QAM256
SIGNAL: [.............                    ] ( 40%)  BER:    228 FREQ: 450000000  Hz LOCKED: YES MER: 348 SYM: 6950000 MOD: QAM256
SIGNAL: [.............                    ] ( 40%)  BER:     39 FREQ: 450000000  Hz LOCKED: YES MER: 341 SYM: 6950000 MOD: QAM256
SIGNAL: [...............................  ] ( 95%)  BER:     39 FREQ: 450000000  Hz LOCKED: YES MER: 301 SYM: 6950000 MOD: QAM256
SIGNAL: [..............                   ] ( 43%)  BER:   1056 FREQ: 450000000  Hz LOCKED: YES MER: 313 SYM: 6950000 MOD: QAM256


Sundtek

  • Administrator
  • Hero Member
  • *****
  • Beiträge: 8604
    • Profil anzeigen
Re:Going insane, wierd driver/application behaviour?
« Antwort #7 am: Oktober 19, 2015, 08:49:15 Nachmittag »
Hi,

as far as I see this tuner is at least 4-5 years old; I guess we're able to help you out with this.
tvheadend is fine as far as I can see from your logfile.

Let's discuss the rest in Skype.
Failure is a good thing! I'll fix it

Phr0z

  • Newbie
  • *
  • Beiträge: 6
    • Profil anzeigen
Re:Going insane, wierd driver/application behaviour?
« Antwort #8 am: Oktober 19, 2015, 09:38:21 Nachmittag »
Oh my... I think I know what's going on now.  :D

It's my provider that has switched muxes.

I've always used the pre-defined no-oslo-CanalDigital list to discover muxes. It seems like that list is scanning on QAM64.

So adding that I just assumed TVheadend on my Kodibuntu installation would discover everything automatically.

Now checking my old OpenELEC install I can see that the muxes that works are on QAM256. I guess they had some sort of discovery activated while they migrated to the new muxes/network?? (guessing, have no real knowledge of dvb).

So it seems they simply are no longer broadcasting on QAM64 net.

So everything is in order, case closed and thank you for your time though! :)

Sundtek

  • Administrator
  • Hero Member
  • *****
  • Beiträge: 8604
    • Profil anzeigen
Re:Going insane, wierd driver/application behaviour?
« Antwort #9 am: Oktober 19, 2015, 09:46:34 Nachmittag »
Still something does not look right because the signal strength is jumping up and down, as mentioned just go over it with our direct Skype support for a few minutes.
Failure is a good thing! I'll fix it

Phr0z

  • Newbie
  • *
  • Beiträge: 6
    • Profil anzeigen
Re:Going insane, wierd driver/application behaviour?
« Antwort #10 am: Oktober 20, 2015, 09:39:00 Vormittag »
Hi,

Skype:ing won't be necessary.

After a new mux discovery everything looks fine. 100% signal strength.

Thank you :)