I can't blame the drivers, I think most probably it's just enigma2 getting older.... it needs to know more API v5 ...
You can install dvbsnoop to get the data following in order to reproduce and understand what is going on.
Image boot, drivers are loaded, (before enigma2 starts), tuner is initialized as DVB-S.
Code:
root@osmio4kplus:~# dvbsnoop -frontend /dev/dvb/adapter0/frontend1 -s feinfo
dvbsnoop V1.4.55 -- https://github.com/OpenVisionE2/dvbsnoop
---------------------------------------------------------
FrontEnd Info...
---------------------------------------------------------
Device: /dev/dvb/adapter0/frontend1
Basic capabilities:
Name: "Availink AVL6862"
Frontend-type: QPSK (DVB-S)
Frequency (min): 43.000 MHz
Frequency (max): 2150.000 MHz
Frequency stepsiz: 0.166 MHz
Frequency tolerance: 5.000 MHz
Symbol rate (min): 0.000000 MSym/s
Symbol rate (max): 55.000000 MSym/s
Symbol rate tolerance: 0 ppm
Notifier delay: 0 ms
Frontend capabilities:
auto inversion
FEC 1/2
FEC 2/3
FEC 3/4
FEC 4/5
FEC 5/6
FEC 6/7
FEC 7/8
FEC 8/9
FEC AUTO
QPSK
QAM 16
QAM 32
QAM 64
QAM 128
QAM 256
QAM AUTO
auto transmission mode
auto guard interval
auto hierarchy
FE_CAN_2G_MODULATION
FE_CAN_RECOVER
Current parameters:
Frequency: 0.000 MHz
Inversion: OFF
Symbol rate: 0.000000 MSym/s
FEC: FEC AUTO
When enigma2 starts, it get's the tuner information using API (v3 or older most probably).
You can switch to DVB-S, you can switch to DVB-T. All work fine.
Then you switch to DVB-T.
Code:
root@osmio4kplus:~# dvbsnoop -frontend /dev/dvb/adapter0/frontend1 -s feinfo
dvbsnoop V1.4.55 -- https://github.com/OpenVisionE2/dvbsnoop
---------------------------------------------------------
FrontEnd Info...
---------------------------------------------------------
Device: /dev/dvb/adapter0/frontend1
Basic capabilities:
Name: "Availink AVL6862"
Frontend-type: OFDM (DVB-T)
Frequency (min): 43000.000 kHz
Frequency (max): 2150000.000 kHz
Frequency stepsiz: 166.666 kHz
Frequency tolerance: 5000.000 kHz
Symbol rate (min): 0.000000 MSym/s
Symbol rate (max): 55.000000 MSym/s
Symbol rate tolerance: 0 ppm
Notifier delay: 0 ms
Frontend capabilities:
auto inversion
FEC 1/2
FEC 2/3
FEC 3/4
FEC 4/5
FEC 5/6
FEC 6/7
FEC 7/8
FEC 8/9
FEC AUTO
QPSK
QAM 16
QAM 32
QAM 64
QAM 128
QAM 256
QAM AUTO
auto transmission mode
auto guard interval
auto hierarchy
FE_CAN_2G_MODULATION
FE_CAN_RECOVER
Current parameters:
Frequency: 474000.000 kHz
Inversion: AUTO
Bandwidth: 8 MHz
Stream code rate (hi prio): FEC 2/3
Stream code rate (lo prio): FEC AUTO
Modulation: QAM 64
Transmission mode: 8k mode
Guard interval: 1/4
Hierarchy: none
As you can see above, tuner frequency now reports the ranges for DVB-T.
Also enigma2 when you press the info button on tuner list!
Now if you restart the enigma2, the DVB-S channels don't work any more!
Why?
Because tuner priority is dropping to zero......
Code:
[eDVBResourceManager] allocate channel.. 03f2:0001
[eDVBSatelliteEquipmentControl] direct_connected 1
[eDVBSatelliteEquipmentControl] canTune 2
[eDVBSatelliteEquipmentControl] lnb 0 found
[eDVBSatelliteEquipmentControl] sat 192 found
[eDVBSatelliteEquipmentControl] ret1 10000
[eDVBSatelliteEquipmentControl] ret5 10000
[eDVBSatelliteEquipmentControl] ret 0, score old 0
[eDVBSatelliteEquipmentControl] score new 0
[eDVBSatelliteEquipmentControl] final score 0
[eDVBServicePMTHandler] allocate Channel: res -7
[eDVBServicePlay] DVB service failed to tune - error 10
Why?
Because the enigma2 is checking that code:
https://github.com/OpenPLi/enigma2/b....cpp#L220-L229
Code:
eSecDebugNoSimulate("[eDVBSatelliteEquipmentControl] ret5 %d", ret);
if (ret && !is_unicable)
{
int lof = sat.frequency > lnb_param.m_lof_threshold ?
lnb_param.m_lof_hi : lnb_param.m_lof_lo;
unsigned int tuner_freq = absdiff(sat.frequency, lof);
if (tuner_freq < fe_info.frequency_min || tuner_freq > fe_info.frequency_max)
ret = 0;
}
Why?
It's a check to verify that tuner supports the frequency range... and things seem to go wrong there.
Code:
Frequency (min): 43.000 MHz
Frequency (max): 2150.000 MHz
vs
Frequency (min): 43000.000 kHz
Frequency (max): 2150000.000 kHz
Huh?
Yeah.... In both cases the dvbsnoop returns the same value. 43 MHz is equal to 43000 kHz (assuming that kilo is 1000....).
Enigma2 on the other hand, doesn't seem to be aware of that...