DVB T2/C tuner not finding any channels.

[abu baniaz]

Thanks. Lamedb file after an ABM run will be good too.

[deggsy999]

Lamedb Files attached as requested.

[abu baniaz]

Test 1 on Gigablue.

Transfer this file to /usr/lib/enigma2/python/Plugins/SystemPlugins/AutoBouquetsMaker/providers
Delete providers.cache in same location
In ABM, disable Virgin. Enable degsy999

Run ABM and check if it works.

[abu baniaz]

Test 2 on Gigablue

Transfer this cables.xml file to /etc/enigma2/
Ensure debug logs are on
Restart GUI. (Your tuner config will change automatically)
Perform a non-abm scan

Menu > Setup > Tuner config > Manual scan > select dvb-c tuner >
Type of scan = complete

It should not be too long as only the frequencies from your area are listed

Does it find channels during a scan?

If not, please attach debug log. Default location is /home/root /logs
We will have to try another image to confirm if it is a driver issue

[deggsy999]

Test 1 done , still get error, question, why is this file for 41048 (Manchester) when the area I am in is 41018 (Preston)?

[deggsy999]

Again, just took a quick look at the xml file for test 2 and this file is for 41048 also, don't want to try it if it is for the wrong area.

[abu baniaz]

Bother! Need more sleep. I basically changed frequency to 595000. Can you amend the official file and try again.

Test 2 should be fine to do. E2 scanning ignores net ID for UK.

[deggsy999]

Ok,Test 1, modified file and re-tested, still fails.


Test 2 this found somthing but no usable channels, please see attached log.

[abu baniaz]

Forget ABM for now, the frequency in the file is correct. The Tiviar works fine too.

You are getting this error

< 11814.629> [eDVBFrontend] (2)tune
< 11814.629> [eDVBFrontend] tuning to 531000 khz, sr 6952000, fec 3, modulation 5, inversion 2
< 11814.629> [eDVBChannel] OURSTATE: tuning
< 11814.630> [eDVBFrontend] startTuneTimeout 5000
< 11814.631> [eDVBFrontend] setFrontend 1
< 11814.631> [eDVBFrontend] setting frontend 2
< 11814.631> [eDVBFrontend] (2)fe event: status 0, inversion off, m_tuning 1
< 11814.859> [eDVBFrontend] (2)fe event: status 10, inversion off, m_tuning 2
< 11814.859> [eDVBChannel] OURSTATE: ok
< 11814.859> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
< 11814.859> [eDVBSectionReader] DMX_SET_FILTER pid=0
< 11814.859> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
< 11814.860> [eDVBSectionReader] DMX_SET_FILTER pid=16
< 11818.860> [eDVBScan] got pat, err -1
< 11818.860> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
< 11818.860> [eDVBSectionReader] DMX_SET_FILTER pid=17
< 11821.361> [eDVBScan] got sdt -1
< 11826.861> [eDVBScan] got nit, err -1
< 11826.861> [eDVBScan] channel done!
< 11826.861> [eDVBScan] the current channel's ID was not corrected - not adding channel.

Please continue testing with the cables.xml file I uploaded.

Can you try the following:
Flash Team blue image, ensure it has the same driver date as the one on Vix.

http://images.teamblue.tech/6.1-release/index.php

I don't believe they have debug logs like us, so start Enigma2 in console mode, then perform a manual scan as above. Attach the log please

init 4
ENIGMA_DEBUG_LVL=4 /usr/bin/enigma2

If that fails, I think you will have to flash an image with older drivers until it is fixed. We'll send details to one of the guys with contacts at Gigablue

[ccs]

Worth another mention....

I then did a full factory reset on my box and installed the latest copy of the Vix Image that I downloaded and put on a pen drive. At this point I was happy to find that the cards worked and detected a full set of channels on both the TV areal and VM Cbl.

My guess is that the image never flashed (based on later posts), so maybe the latest image/drivers really is the problem.

[ccs]

I then did a full factory reset on my box and installed the latest copy of the Vix Image that I downloaded and put on a pen drive.....

Everything was well for a while then unfortunately yesterday I had to power off my Box and when switching it back I must have caught something as it decided to begin the flashing process from a really old image I had forgotten was installed on a memory card in the back of the box. I let it complete (don’t want to brick it) and then downloaded the latest image and again re-flashed the box to the latest image.

Another theory, maybe the old image was flashed the first time round, not the "latest" copy.

[deggsy999]

Hi, A quick update, I tried the Team Blue image, I couldn't really get my head round it but I did manage to do a full scan and it found all the channels but not of them would actually produce any kind of video.

I then decided to go drastic, I downloaded and flashed the box with image 5.1.002 (the earliest image I could find in this branch) this worked straight away and all the channels were found and were viewable.

I then decided to flash the box with 5.1.031 (one down from current) on this image it found all the channels straight away but none of them worked, same with 5.1.030.

At this point I flashed the box with 5.1.020, figured I would skip a few. this image works perfectly, finds all the channels and each one is viewable.

And this is where I am now, somthing changes between 020 and 030. I will (at some point) find out the exact point it stops working by trying 025 next and then working up or down until I find the image where it goes wrong. But for now, it is working and I am having a few days break from it, I now have flashing and re-setting up of the box down to a fine art which is not really a skill I desperately need :-)


Thanks for everybody's help with this especially you Abu thanks for your patience and persistence, it has been appreciated.


I will update you when I have the precise point when it goes wrong, hopefully you can then feed this information back to the developers and sort it out for future images.

[ccs]

There were driver updates in 5.1.024

[deggsy999]

Maybe thats a good place for me to start, if 024 doesn't work and 023 does. What I don't understand is why I haven't spotted this earlier, as soon as a stable update is available I tend to download it (flashing green dot) and 024 was release on the 8th April. I have certainly done updates since then, its all very strange.

[abu baniaz]

The driver updates for your receiver were on 30th of March, so I am sure problem will start in 5.1 024.

Can you also try OpenATV 6.2 to confirm the issue please?