https://bugs.kde.org/show_bug.cgi?id=376556
Mauro Carvalho Chehab <mchehab+...@kernel.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Ever confirmed|0 |1
--- Comment #4 from Mauro Carvalho Chehab <mchehab+...@kernel.org> ---
As the problem doesn't seem to be related with the DVB-T adapter 0, I'm doing
some tests here with another device that supports DVB-T/T2/C on the same
frontend.
With this device, I was able to reproduce the issue ;)
The problem is actually unrelated to DVB-T2 tuning, but, instead, with the
automatic scan.
Here, I set Kaffeine to use the "co-All" frequencies:
[dvb-t/co-All]
T2 473000000 6MHz AUTO AUTO AUTO AUTO AUTO AUTO 0
...
and I set my RF generator to modulate at 473 MHz with 6MHz bandwidth, in order
to match the first channel there. With such settings, Kaffeine worked fine.
However, the automatic scan logic is setting the device to DVB-T, instead of
DVB-T2, with causes the frontend to not tune.
I'll work on a patch fixing the automatic scan logic for DVB-T2. In the mean
time, if you set the adapter to use an existing entry that matches your city
frequencies, you should be able to make it work.
--
You are receiving this mail because:
You are watching all bug changes.
