Re: DVB-S PCI card regression on 4.19 / 4.20
Hi Takashi,
Em Mon, 19 Nov 2018 16:13:29 +0100
Takashi Iwai escreveu:
> Hi,
>
> we've got a regression report on openSUSE Bugzilla regarding DVB-S PCI
> card:
> https://bugzilla.opensuse.org/show_bug.cgi?id=1116374
>
> According to the reporter (Stakanov, Cc'ed), the card worked fine on
> 4.18.15, but since 4.19, it doesn't give any channels, sound nor
> picture, but only EPG is received.
Receiving just EPG is weird.
>
> The following errors might be relevant:
>
>
> [4.845180] b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV receiver
> chip loaded successfully
> [4.869703] b2c2-flexcop: MAC address = xx:xx:xx:xx:xx:xx
> [5.100318] b2c2-flexcop: found 'ST STV0299 DVB-S' .
> [5.100323] b2c2_flexcop_pci :06:06.0: DVB: registering adapter 0
> frontend 0 (ST STV0299 DVB-S)...
> [5.100370] b2c2-flexcop: initialization of 'Sky2PC/SkyStar 2 DVB-S rev
> 2.6' at the 'PCI' bus controlled by a 'FlexCopIIb' complete
> [ 117.513086] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0
> frequency 1549000 out of range (95..2150)
> [ 124.905222] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0
> frequency 188 out of range (95..2150)
> [ 127.337079] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0
> frequency 1353500 out of range (95..2150)
That indicates that it is trying to tune to an unsupported frequency. For
DVB-S, all frequencies above should be in kHz.
It is very weird that the low frequency is bigger than the higher one.
I suspect that this could be the root cause of the issue.
Yet, the entry at stv0299 (with apparently is the used frontend)
seems correct, as both min and max frequencies are in MHz:
static const struct dvb_frontend_ops stv0299_ops = {
.delsys = { SYS_DVBS },
.info = {
.name = "ST STV0299 DVB-S",
.frequency_min_hz = 950 * MHz,
.frequency_max_hz = 2150 * MHz,
.frequency_stepsize_hz = 125 * kHz,
.symbol_rate_min= 100,
.symbol_rate_max= 4500,
.symbol_rate_tolerance = 500, /* ppm */
.caps = FE_CAN_FEC_1_2 | FE_CAN_FEC_2_3 | FE_CAN_FEC_3_4 |
FE_CAN_FEC_5_6 | FE_CAN_FEC_7_8 |
FE_CAN_QPSK |
FE_CAN_FEC_AUTO
},
It could be some mistake at the tuner (if this driver loads a
separate tuner).
From the code, it seems that this specific board uses this tuner
from dvb-pll:
static const struct dvb_pll_desc dvb_pll_samsung_tbmu24112 = {
.name = "Samsung TBMU24112",
.min= 95,
.max= 215, /* guesses */
.iffreq = 0,
.count = 2,
.entries = {
{ 150, 125, 0x84, 0x18 },
{ 999, 125, 0x84, 0x08 },
}
};
Here, frequencies are in kHz. The code should be converting them to Hz
if the TV standard is satellite.
>
>
> The lspci shows:
>
> 06:06.0 Network controller: Techsan Electronics Co Ltd B2C2 FlexCopII DVB
> chip / Technisat SkyStar2 DVB card (rev 02)
> Subsystem: Techsan Electronics Co Ltd B2C2 FlexCopII DVB chip /
> Technisat SkyStar2 DVB card
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B- DisINTx-
> Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort-
> SERR- Latency: 32
> Interrupt: pin A routed to IRQ 20
> NUMA node: 0
> Region 0: Memory at fe50 (32-bit, non-prefetchable) [size=64K]
> Region 1: I/O ports at b040 [size=32]
> Kernel driver in use: b2c2_flexcop_pci
> Kernel modules: b2c2_flexcop_pci
>
>
> Other details can be found in the bugzilla entry above.
>
> If any fix is known, please let me know. I'll build a test kernel for
> openSUSE to confirm it.
>
>
> Thanks!
>
> Takashi
Thanks,
Mauro
--
Could you ask the user to apply the enclosed patch and provide us
the results of those prints?
diff --git a/Documentation/media/uapi/mediactl/media-ioc-request-alloc.rst
b/Documentation/media/uapi/mediactl/media-ioc-request-alloc.rst
index 0f8b31874002..60874a1f3d89 100644
--- a/Documentation/media/uapi/mediactl/media-ioc-request-alloc.rst
+++ b/Documentation/media/uapi/mediactl/media-ioc-request-alloc.rst
@@ -1,4 +1,15 @@
-.. SPDX-License-Identifier: GPL-2.0 OR GFDL-1.1-or-later WITH
no-invariant-sections
+.. SPDX License for this file: GPL-2.0 OR GFDL-1.1-or-later
+..
+.. For GPL-2.0, see LICENSES/preferred/GPL-2.0
+..
+.. For GFDL-1.1-or-later, see:
+..
+.. Permission is granted to copy, distribute and/or modify this document
+.. under the terms of the GNU Free Documentation License, Version 1.1 or
+.. any later version published by the Free Software Foundation, with no
+.. Invariant Sections, no Front-Cover Texts and no Back
Re: DVB-S PCI card regression on 4.19 / 4.20
Hi On 19/11/2018 17:53, Mauro Carvalho Chehab wrote: > Hi Takashi, > > Em Mon, 19 Nov 2018 16:13:29 +0100 > Takashi Iwai escreveu: > >> Hi, >> >> we've got a regression report on openSUSE Bugzilla regarding DVB-S PCI >> card: >> https://bugzilla.opensuse.org/show_bug.cgi?id=1116374 >> >> According to the reporter (Stakanov, Cc'ed), the card worked fine on >> 4.18.15, but since 4.19, it doesn't give any channels, sound nor >> picture, but only EPG is received. > > Receiving just EPG is weird. > >> >> The following errors might be relevant: >> >> >> [4.845180] b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV receiver >> chip loaded successfully >> [4.869703] b2c2-flexcop: MAC address = xx:xx:xx:xx:xx:xx >> [5.100318] b2c2-flexcop: found 'ST STV0299 DVB-S' . >> [5.100323] b2c2_flexcop_pci :06:06.0: DVB: registering adapter 0 >> frontend 0 (ST STV0299 DVB-S)... >> [5.100370] b2c2-flexcop: initialization of 'Sky2PC/SkyStar 2 DVB-S rev >> 2.6' at the 'PCI' bus controlled by a 'FlexCopIIb' complete > > >> [ 117.513086] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0 >> frequency 1549000 out of range (95..2150) >> [ 124.905222] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0 >> frequency 188 out of range (95..2150) >> [ 127.337079] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0 >> frequency 1353500 out of range (95..2150) > > That indicates that it is trying to tune to an unsupported frequency. For > DVB-S, all frequencies above should be in kHz. Kaffeine reports the wrong LNB frequency ranges for universal Europe... I just use Astra 1E settings instead which I am pretty sure is the same? I am using the stv0299 / dvb_pll(opera1) combi and not reporting any problems other than the streaming issue with dvb-usb-v2 which I don't think this uses? Regards Malcolm
Re: DVB-S PCI card regression on 4.19 / 4.20
On Mon, 19 Nov 2018 18:53:26 +0100, Mauro Carvalho Chehab wrote: > > Could you ask the user to apply the enclosed patch and provide us > the results of those prints? OK, I built a test kernel in OBS home:tiwai:bsc1116374 repo. Now it's available at https://download.opensuse.org/repositories/home:/tiwai:/bsc1116374/standard/ Stakanov, could you test it and give the kernel messages? Thanks! Takashi
Re: DVB-S PCI card regression on 4.19 / 4.20
In data lunedì 19 novembre 2018 20:47:19 CET, Takashi Iwai ha scritto: > On Mon, 19 Nov 2018 18:53:26 +0100, > > Mauro Carvalho Chehab wrote: > > Could you ask the user to apply the enclosed patch and provide us > > the results of those prints? > > OK, I built a test kernel in OBS home:tiwai:bsc1116374 repo. Now it's > available at > > https://download.opensuse.org/repositories/home:/tiwai:/bsc1116374/standard > / > > Stakanov, could you test it and give the kernel messages? > > > Thanks! > > Takashi Here we go, I did saw your mail only late, sorry. Result of proposed fix (rc3): card has still no function, does not sync, EPG works. No sound no picture. entropy@silversurfer:~> uname -a Linux silversurfer 4.20.0-rc3-1.g7e16618-default #1 SMP PREEMPT Mon Nov 19 18:54:15 UTC 2018 (7e16618) x86_64 x86_64 x86_64 GNU/Linux output of entropy@silversurfer:~> sudo dmesg | grep -i b2c2 [4.831163] b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV receiver chip loaded successfully [4.862648] b2c2-flexcop: MAC address = xx:xx:xx:xx:xx:xx [5.094173] b2c2-flexcop: found 'ST STV0299 DVB-S' . [5.094177] b2c2_flexcop_pci :06:06.0: DVB: registering adapter 0 frontend 0 (ST STV0299 DVB-S)... [5.094248] b2c2-flexcop: initialization of 'Sky2PC/SkyStar 2 DVB-S rev 2.6' at the 'PCI' bus controlled by a 'FlexCopIIb' complete [ 121.789236] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0 frequency 188 out of range (95..2150) [ 128.817325] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0 frequency 1944750 out of range (95..2150) sudo lspci -vvv 06:06.0 Network controller: Techsan Electronics Co Ltd B2C2 FlexCopII DVB chip / Technisat SkyStar2 DVB card (rev 02) Subsystem: Techsan Electronics Co Ltd B2C2 FlexCopII DVB chip / Technisat SkyStar2 DVB card Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- SERR- https://www.eclipso.de
Re: DVB-S PCI card regression on 4.19 / 4.20
Em Mon, 19 Nov 2018 23:59:39 +0100 stakanov escreveu: > In data lunedì 19 novembre 2018 20:47:19 CET, Takashi Iwai ha scritto: > > On Mon, 19 Nov 2018 18:53:26 +0100, > > > > Mauro Carvalho Chehab wrote: > > > Could you ask the user to apply the enclosed patch and provide us > > > the results of those prints? > > > > OK, I built a test kernel in OBS home:tiwai:bsc1116374 repo. Now it's > > available at > > > > https://download.opensuse.org/repositories/home:/tiwai:/bsc1116374/standard > > / > > > > Stakanov, could you test it and give the kernel messages? > > > > > > Thanks! > > > > Takashi > Here we go, I did saw your mail only late, sorry. > > > Result of proposed fix (rc3): card has still no function, does not sync, EPG > works. No sound no picture. This is not a fix. It just adds some new messages that should help to explain why the frequency range seems wrong. > > entropy@silversurfer:~> uname -a > Linux silversurfer 4.20.0-rc3-1.g7e16618-default #1 SMP PREEMPT Mon Nov 19 > 18:54:15 UTC 2018 (7e16618) x86_64 x86_64 x86_64 GNU/Linux > > output of > entropy@silversurfer:~> sudo dmesg | grep -i b2c2 > [4.831163] b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV receiver > chip > loaded successfully > [4.862648] b2c2-flexcop: MAC address = xx:xx:xx:xx:xx:xx > [5.094173] b2c2-flexcop: found 'ST STV0299 DVB-S' . > [5.094177] b2c2_flexcop_pci :06:06.0: DVB: registering adapter 0 > frontend 0 (ST STV0299 DVB-S)... > [5.094248] b2c2-flexcop: initialization of 'Sky2PC/SkyStar 2 DVB-S rev > 2.6' at the 'PCI' bus controlled by a 'FlexCopIIb' complete > [ 121.789236] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0 > frequency 188 out of range (95..2150) > [ 128.817325] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0 > frequency 1944750 out of range (95..2150) Are you sure you booted the right Kernel? I'm not seeing the new messages here that should be printing the tuner and frontend frequency ranges. > > sudo lspci -vvv > 06:06.0 Network controller: Techsan Electronics Co Ltd B2C2 FlexCopII DVB > chip > / Technisat SkyStar2 DVB card (rev 02) > Subsystem: Techsan Electronics Co Ltd B2C2 FlexCopII DVB chip / > Technisat SkyStar2 DVB card > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- > Stepping- SERR- FastB2B- DisINTx- > Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- > SERR- Latency: 32 > Interrupt: pin A routed to IRQ 20 > NUMA node: 0 > Region 0: Memory at fe50 (32-bit, non-prefetchable) [size=64K] > Region 1: I/O ports at b040 [size=32] > Kernel driver in use: b2c2_flexcop_pci > Kernel modules: b2c2_flexcop_pci > > > > > _ > > Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte > E-Mail-Adresse mitnehmen! https://www.eclipso.de > > Thanks, Mauro
Re: DVB-S PCI card regression on 4.19 / 4.20
In data martedì 20 novembre 2018 00:08:45 CET, Mauro Carvalho Chehab ha scritto: > uname -a > > > Linux silversurfer 4.20.0-rc3-1.g7e16618-default #1 SMP PREEMPT Mon Nov 19 > > 18:54:15 UTC 2018 (7e16618) x86_64 x86_64 x86_64 GNU/Linux uname -a > Linux silversurfer 4.20.0-rc3-1.g7e16618-default #1 SMP PREEMPT Mon Nov 19 > 18:54:15 UTC 2018 (7e16618) x86_64 x86_64 x86_64 GNU/Linux from https://download.opensuse.org/repositories/home:/tiwai:/bsc1116374/ standard/x86_64/ So I booted this one, should be the right one. sudo dmesg | grep -i b2c2 should give these additional messages? If Takashi is still around, he could confirm. _ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de
Re: DVB-S PCI card regression on 4.19 / 4.20
Em Tue, 20 Nov 2018 00:19:54 +0100 stakanov escreveu: > In data martedì 20 novembre 2018 00:08:45 CET, Mauro Carvalho Chehab ha > scritto: > > uname -a > > > > > Linux silversurfer 4.20.0-rc3-1.g7e16618-default #1 SMP PREEMPT Mon Nov 19 > > > 18:54:15 UTC 2018 (7e16618) x86_64 x86_64 x86_64 GNU/Linux > > uname -a > > Linux silversurfer 4.20.0-rc3-1.g7e16618-default #1 SMP PREEMPT Mon Nov 19 > > 18:54:15 UTC 2018 (7e16618) x86_64 x86_64 x86_64 GNU/Linux > > from https://download.opensuse.org/repositories/home:/tiwai:/bsc1116374/ > standard/x86_64/ > > So I booted this one, should be the right one. > sudo dmesg | grep -i b2c2 should give these additional messages? > > If Takashi is still around, he could confirm. Well, if the patch got applied, you should now be getting messages similar (but not identical) to: dvb_frontend_get_frequency_limits: frequencies: tuner: 915...215, frontend: 915...215 dvb_pll_attach: delsys: 5, frequency range: 915..215 > > > > _ > > Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte > E-Mail-Adresse mitnehmen! https://www.eclipso.de > > Thanks, Mauro
Re: DVB-S PCI card regression on 4.19 / 4.20
On Tue, 20 Nov 2018 00:19:54 +0100, stakanov wrote: > > In data martedì 20 novembre 2018 00:08:45 CET, Mauro Carvalho Chehab ha > scritto: > > uname -a > > > > > Linux silversurfer 4.20.0-rc3-1.g7e16618-default #1 SMP PREEMPT Mon Nov 19 > > > 18:54:15 UTC 2018 (7e16618) x86_64 x86_64 x86_64 GNU/Linux > > uname -a > > Linux silversurfer 4.20.0-rc3-1.g7e16618-default #1 SMP PREEMPT Mon Nov 19 > > 18:54:15 UTC 2018 (7e16618) x86_64 x86_64 x86_64 GNU/Linux > > from https://download.opensuse.org/repositories/home:/tiwai:/bsc1116374/ > standard/x86_64/ The kernel must be correct (7e16618 contains the patch, I confirmed). > So I booted this one, should be the right one. > sudo dmesg | grep -i b2c2 should give these additional messages? Avoid grep but look around the whole lines. The added debug print is no dev_info() or such but just a plain printk(), hence it won't give any prefix. thanks, Takashi
Re: DVB-S PCI card regression on 4.19 / 4.20
In data martedì 20 novembre 2018 00:58:41 CET, Mauro Carvalho Chehab ha scritto: > Em Tue, 20 Nov 2018 00:19:54 +0100 > > stakanov escreveu: > > In data martedì 20 novembre 2018 00:08:45 CET, Mauro Carvalho Chehab ha > > > > scritto: > > > uname -a > > > > > > > Linux silversurfer 4.20.0-rc3-1.g7e16618-default #1 SMP PREEMPT Mon > > > > Nov 19 > > > > 18:54:15 UTC 2018 (7e16618) x86_64 x86_64 x86_64 GNU/Linux > > > > uname -a > > > > > Linux silversurfer 4.20.0-rc3-1.g7e16618-default #1 SMP PREEMPT Mon Nov > > > 19 > > > 18:54:15 UTC 2018 (7e16618) x86_64 x86_64 x86_64 GNU/Linux > > > > from https://download.opensuse.org/repositories/home:/tiwai:/bsc1116374/ > > standard/x86_64/ > > > > So I booted this one, should be the right one. > > sudo dmesg | grep -i b2c2 should give these additional messages? > > > > If Takashi is still around, he could confirm. > > Well, if the patch got applied, you should now be getting messages similar > (but not identical) to: > > dvb_frontend_get_frequency_limits: frequencies: tuner: > 915...215, > frontend: 915...215 dvb_pll_attach: delsys: 5, frequency range: > 915..215 > > > _ > > > > Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und > > alte E-Mail-Adresse mitnehmen! https://www.eclipso.de > Thanks, > Mauro My bad. With just dmesg: [ 89.399887] dvb_frontend_get_frequency_limits: frequencies: tuner: 95...215, frontend: 95000...215000 [ 95.020149] dvb_frontend_get_frequency_limits: frequencies: tuner: 95...215, frontend: 95000...215000 [ 95.152049] dvb_frontend_get_frequency_limits: frequencies: tuner: 95...215, frontend: 95000...215000 [ 95.152058] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0 frequency 188 out of range (95..2150) [ 98.356539] dvb_frontend_get_frequency_limits: frequencies: tuner: 95...215, frontend: 95000...215000 [ 98.480372] dvb_frontend_get_frequency_limits: frequencies: tuner: 95...215, frontend: 95000...215000 [ 98.480381] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0 frequency 1587500 out of range (95..2150) [ 100.016823] dvb_frontend_get_frequency_limits: frequencies: tuner: 95...215, frontend: 95000...215000 [ 100.140619] dvb_frontend_get_frequency_limits: frequencies: tuner: 95...215, frontend: 95000...215000 [ 100.140629] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0 frequency 1353500 out of range (95..2150) [ 105.361166] dvb_frontend_get_frequency_limits: frequencies: tuner: 95...215, frontend: 95000...215000 [ 105.492972] dvb_frontend_get_frequency_limits: frequencies: tuner: 95...215, frontend: 95000...215000 [ 105.492977] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0 frequency 1944750 out of range (95..2150) Which is, I guess the info you need? _ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de
Re: DVB-S PCI card regression on 4.19 / 4.20
Em Tue, 20 Nov 2018 09:07:57 +0100
stakanov escreveu:
> In data martedì 20 novembre 2018 00:58:41 CET, Mauro Carvalho Chehab ha
> scritto:
> > Em Tue, 20 Nov 2018 00:19:54 +0100
> >
> > stakanov escreveu:
> > > In data martedì 20 novembre 2018 00:08:45 CET, Mauro Carvalho Chehab ha
> > >
> > > scritto:
> > > > uname -a
> > > >
> > > > > Linux silversurfer 4.20.0-rc3-1.g7e16618-default #1 SMP PREEMPT Mon
> > > > > Nov 19
> > > > > 18:54:15 UTC 2018 (7e16618) x86_64 x86_64 x86_64 GNU/Linux
> > >
> > > uname -a
> > >
> > > > Linux silversurfer 4.20.0-rc3-1.g7e16618-default #1 SMP PREEMPT Mon Nov
> > > > 19
> > > > 18:54:15 UTC 2018 (7e16618) x86_64 x86_64 x86_64 GNU/Linux
> > >
> > > from https://download.opensuse.org/repositories/home:/tiwai:/bsc1116374/
> > > standard/x86_64/
> > >
> > > So I booted this one, should be the right one.
> > > sudo dmesg | grep -i b2c2 should give these additional messages?
> > >
> > > If Takashi is still around, he could confirm.
> >
> > Well, if the patch got applied, you should now be getting messages similar
> > (but not identical) to:
> >
> > dvb_frontend_get_frequency_limits: frequencies: tuner:
> > 915...215,
> > frontend: 915...215 dvb_pll_attach: delsys: 5, frequency range:
> > 915..215
> >
> > > _
> > >
> > > Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und
> > > alte E-Mail-Adresse mitnehmen! https://www.eclipso.de
> > Thanks,
> > Mauro
>
>
> My bad.
> With just dmesg:
>
> [ 89.399887] dvb_frontend_get_frequency_limits: frequencies: tuner:
> 95...215, frontend: 95000...215000
> [ 95.020149] dvb_frontend_get_frequency_limits: frequencies: tuner:
> 95...215, frontend: 95000...215000
> [ 95.152049] dvb_frontend_get_frequency_limits: frequencies: tuner:
> 95...215, frontend: 95000...215000
> [ 95.152058] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0
> frequency 188 out of range (95..2150)
> [ 98.356539] dvb_frontend_get_frequency_limits: frequencies: tuner:
> 95...215, frontend: 95000...215000
> [ 98.480372] dvb_frontend_get_frequency_limits: frequencies: tuner:
> 95...215, frontend: 95000...215000
> [ 98.480381] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0
> frequency 1587500 out of range (95..2150)
> [ 100.016823] dvb_frontend_get_frequency_limits: frequencies: tuner:
> 95...215, frontend: 95000...215000
> [ 100.140619] dvb_frontend_get_frequency_limits: frequencies: tuner:
> 95...215, frontend: 95000...215000
> [ 100.140629] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0
> frequency 1353500 out of range (95..2150)
> [ 105.361166] dvb_frontend_get_frequency_limits: frequencies: tuner:
> 95...215, frontend: 95000...215000
> [ 105.492972] dvb_frontend_get_frequency_limits: frequencies: tuner:
> 95...215, frontend: 95000...215000
> [ 105.492977] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0
> frequency 1944750 out of range (95..2150)
>
>
> Which is, I guess the info you need?
Yes, partially. Clearly, the problem is coming from the tuner, with is
not reporting the frequency in Hz, but I was hoping to see another
message from the tuner driver, in order for me to be sure about what's
happening there.
Didn't you get any message that starts with "dvb_pll_attach"?
The thing with Flexcop is that there are several variations, each one
with a different tuner driver.
Anyway, I guess I found the trouble: it is trying to use the DVB
cache to check the delivery system too early (at attach time).
I suspect that the enclosed patch will fix the issue. Could you please
test it?
Thanks!
Mauro
diff --git a/drivers/media/dvb-frontends/dvb-pll.c
b/drivers/media/dvb-frontends/dvb-pll.c
index 6d4b2eec67b4..390ecc915096 100644
--- a/drivers/media/dvb-frontends/dvb-pll.c
+++ b/drivers/media/dvb-frontends/dvb-pll.c
@@ -80,8 +80,8 @@ struct dvb_pll_desc {
static const struct dvb_pll_desc dvb_pll_thomson_dtt7579 = {
.name = "Thomson dtt7579",
- .min = 17700,
- .max = 85800,
+ .min = 177 * MHz,
+ .max = 858 * MHz,
.iffreq= 3617,
.sleepdata = (u8[]){ 2, 0xb4, 0x03 },
.count = 4,
@@ -102,8 +102,8 @@ static void thomson_dtt759x_bw(struct dvb_frontend *fe, u8
*buf)
static const struct dvb_pll_desc dvb_pll_thomson_dtt759x = {
.name = "Thomson dtt759x",
- .min = 17700,
- .max = 89600,
+ .min = 177 * MHz,
+ .max = 896 * MHz,
.set = thomson_dtt759x_bw,
.iffreq= 3617,
.sleepdata = (u8[]){ 2, 0x84, 0x03 },
@@ -126,8 +126,8 @@ static void thomson_dtt7520x_bw(struct dvb_frontend *fe, u8
Re: DVB-S PCI card regression on 4.19 / 4.20
In data martedì 20 novembre 2018 10:18:10 CET, Mauro Carvalho Chehab ha
scritto:
> Em Tue, 20 Nov 2018 09:07:57 +0100
>
> stakanov escreveu:
> > In data martedì 20 novembre 2018 00:58:41 CET, Mauro Carvalho Chehab ha
> >
> > scritto:
> > > Em Tue, 20 Nov 2018 00:19:54 +0100
> > >
> > > stakanov escreveu:
> > > > In data martedì 20 novembre 2018 00:08:45 CET, Mauro Carvalho Chehab
> > > > ha
> > > >
> > > > scritto:
> > > > > uname -a
> > > > >
> > > > > > Linux silversurfer 4.20.0-rc3-1.g7e16618-default #1 SMP PREEMPT
> > > > > > Mon
> > > > > > Nov 19
> > > > > > 18:54:15 UTC 2018 (7e16618) x86_64 x86_64 x86_64 GNU/Linux
> > > >
> > > > uname -a
> > > >
> > > > > Linux silversurfer 4.20.0-rc3-1.g7e16618-default #1 SMP PREEMPT Mon
> > > > > Nov
> > > > > 19
> > > > > 18:54:15 UTC 2018 (7e16618) x86_64 x86_64 x86_64 GNU/Linux
> > > >
> > > > from
> > > > https://download.opensuse.org/repositories/home:/tiwai:/bsc1116374/
> > > > standard/x86_64/
> > > >
> > > > So I booted this one, should be the right one.
> > > > sudo dmesg | grep -i b2c2 should give these additional messages?
> > > >
> > > > If Takashi is still around, he could confirm.
> > >
> > > Well, if the patch got applied, you should now be getting messages
> > > similar
> > >
> > > (but not identical) to:
> > > dvb_frontend_get_frequency_limits: frequencies: tuner:
> > > 915...215,
> > >
> > > frontend: 915...215 dvb_pll_attach: delsys: 5, frequency range:
> > > 915..215
> > >
> > > > _
> > > >
> > > > Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln
> > > > und
> > > > alte E-Mail-Adresse mitnehmen! https://www.eclipso.de
> > >
> > > Thanks,
> > > Mauro
> >
> > My bad.
> > With just dmesg:
> >
> > [ 89.399887] dvb_frontend_get_frequency_limits: frequencies: tuner:
> > 95...215, frontend: 95000...215000
> > [ 95.020149] dvb_frontend_get_frequency_limits: frequencies: tuner:
> > 95...215, frontend: 95000...215000
> > [ 95.152049] dvb_frontend_get_frequency_limits: frequencies: tuner:
> > 95...215, frontend: 95000...215000
> > [ 95.152058] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0
> > frequency 188 out of range (95..2150)
> > [ 98.356539] dvb_frontend_get_frequency_limits: frequencies: tuner:
> > 95...215, frontend: 95000...215000
> > [ 98.480372] dvb_frontend_get_frequency_limits: frequencies: tuner:
> > 95...215, frontend: 95000...215000
> > [ 98.480381] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0
> > frequency 1587500 out of range (95..2150)
> > [ 100.016823] dvb_frontend_get_frequency_limits: frequencies: tuner:
> > 95...215, frontend: 95000...215000
> > [ 100.140619] dvb_frontend_get_frequency_limits: frequencies: tuner:
> > 95...215, frontend: 95000...215000
> > [ 100.140629] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0
> > frequency 1353500 out of range (95..2150)
> > [ 105.361166] dvb_frontend_get_frequency_limits: frequencies: tuner:
> > 95...215, frontend: 95000...215000
> > [ 105.492972] dvb_frontend_get_frequency_limits: frequencies: tuner:
> > 95...215, frontend: 95000...215000
> > [ 105.492977] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0
> > frequency 1944750 out of range (95..2150)
> >
> >
> > Which is, I guess the info you need?
>
> Yes, partially. Clearly, the problem is coming from the tuner, with is
> not reporting the frequency in Hz, but I was hoping to see another
> message from the tuner driver, in order for me to be sure about what's
> happening there.
>
> Didn't you get any message that starts with "dvb_pll_attach"?
>
> The thing with Flexcop is that there are several variations, each one
> with a different tuner driver.
>
> Anyway, I guess I found the trouble: it is trying to use the DVB
> cache to check the delivery system too early (at attach time).
>
> I suspect that the enclosed patch will fix the issue. Could you please
> test it?
>
> Thanks!
> Mauro
>
>
> diff --git a/drivers/media/dvb-frontends/dvb-pll.c
> b/drivers/media/dvb-frontends/dvb-pll.c index 6d4b2eec67b4..390ecc915096
> 100644
> --- a/drivers/media/dvb-frontends/dvb-pll.c
> +++ b/drivers/media/dvb-frontends/dvb-pll.c
> @@ -80,8 +80,8 @@ struct dvb_pll_desc {
>
> static const struct dvb_pll_desc dvb_pll_thomson_dtt7579 = {
> .name = "Thomson dtt7579",
> - .min = 17700,
> - .max = 85800,
> + .min = 177 * MHz,
> + .max = 858 * MHz,
> .iffreq= 3617,
> .sleepdata = (u8[]){ 2, 0xb4, 0x03 },
> .count = 4,
> @@ -102,8 +102,8 @@ static void thomson_dtt759x_bw(struct dvb_frontend *fe,
> u8 *buf)
>
> static const struct dvb_pll_desc dvb_pll_thomson_dtt759x = {
>
Re: DVB-S PCI card regression on 4.19 / 4.20
On Tue, 20 Nov 2018 10:51:59 +0100,
stakanov wrote:
>
> In data martedì 20 novembre 2018 10:18:10 CET, Mauro Carvalho Chehab ha
> scritto:
> > Em Tue, 20 Nov 2018 09:07:57 +0100
> >
> > stakanov escreveu:
> > > In data martedì 20 novembre 2018 00:58:41 CET, Mauro Carvalho Chehab ha
> > >
> > > scritto:
> > > > Em Tue, 20 Nov 2018 00:19:54 +0100
> > > >
> > > > stakanov escreveu:
> > > > > In data martedì 20 novembre 2018 00:08:45 CET, Mauro Carvalho Chehab
> > > > > ha
> > > > >
> > > > > scritto:
> > > > > > uname -a
> > > > > >
> > > > > > > Linux silversurfer 4.20.0-rc3-1.g7e16618-default #1 SMP PREEMPT
> > > > > > > Mon
> > > > > > > Nov 19
> > > > > > > 18:54:15 UTC 2018 (7e16618) x86_64 x86_64 x86_64 GNU/Linux
> > > > >
> > > > > uname -a
> > > > >
> > > > > > Linux silversurfer 4.20.0-rc3-1.g7e16618-default #1 SMP PREEMPT Mon
> > > > > > Nov
> > > > > > 19
> > > > > > 18:54:15 UTC 2018 (7e16618) x86_64 x86_64 x86_64 GNU/Linux
> > > > >
> > > > > from
> > > > > https://download.opensuse.org/repositories/home:/tiwai:/bsc1116374/
> > > > > standard/x86_64/
> > > > >
> > > > > So I booted this one, should be the right one.
> > > > > sudo dmesg | grep -i b2c2 should give these additional messages?
> > > > >
> > > > > If Takashi is still around, he could confirm.
> > > >
> > > > Well, if the patch got applied, you should now be getting messages
> > > > similar
> > > >
> > > > (but not identical) to:
> > > > dvb_frontend_get_frequency_limits: frequencies: tuner:
> > > > 915...215,
> > > >
> > > > frontend: 915...215 dvb_pll_attach: delsys: 5, frequency range:
> > > > 915..215
> > > >
> > > > > _
> > > > >
> > > > > Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln
> > > > > und
> > > > > alte E-Mail-Adresse mitnehmen! https://www.eclipso.de
> > > >
> > > > Thanks,
> > > > Mauro
> > >
> > > My bad.
> > > With just dmesg:
> > >
> > > [ 89.399887] dvb_frontend_get_frequency_limits: frequencies: tuner:
> > > 95...215, frontend: 95000...215000
> > > [ 95.020149] dvb_frontend_get_frequency_limits: frequencies: tuner:
> > > 95...215, frontend: 95000...215000
> > > [ 95.152049] dvb_frontend_get_frequency_limits: frequencies: tuner:
> > > 95...215, frontend: 95000...215000
> > > [ 95.152058] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0
> > > frequency 188 out of range (95..2150)
> > > [ 98.356539] dvb_frontend_get_frequency_limits: frequencies: tuner:
> > > 95...215, frontend: 95000...215000
> > > [ 98.480372] dvb_frontend_get_frequency_limits: frequencies: tuner:
> > > 95...215, frontend: 95000...215000
> > > [ 98.480381] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0
> > > frequency 1587500 out of range (95..2150)
> > > [ 100.016823] dvb_frontend_get_frequency_limits: frequencies: tuner:
> > > 95...215, frontend: 95000...215000
> > > [ 100.140619] dvb_frontend_get_frequency_limits: frequencies: tuner:
> > > 95...215, frontend: 95000...215000
> > > [ 100.140629] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0
> > > frequency 1353500 out of range (95..2150)
> > > [ 105.361166] dvb_frontend_get_frequency_limits: frequencies: tuner:
> > > 95...215, frontend: 95000...215000
> > > [ 105.492972] dvb_frontend_get_frequency_limits: frequencies: tuner:
> > > 95...215, frontend: 95000...215000
> > > [ 105.492977] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0
> > > frequency 1944750 out of range (95..2150)
> > >
> > >
> > > Which is, I guess the info you need?
> >
> > Yes, partially. Clearly, the problem is coming from the tuner, with is
> > not reporting the frequency in Hz, but I was hoping to see another
> > message from the tuner driver, in order for me to be sure about what's
> > happening there.
> >
> > Didn't you get any message that starts with "dvb_pll_attach"?
> >
> > The thing with Flexcop is that there are several variations, each one
> > with a different tuner driver.
> >
> > Anyway, I guess I found the trouble: it is trying to use the DVB
> > cache to check the delivery system too early (at attach time).
> >
> > I suspect that the enclosed patch will fix the issue. Could you please
> > test it?
> >
> > Thanks!
> > Mauro
> >
> >
> > diff --git a/drivers/media/dvb-frontends/dvb-pll.c
> > b/drivers/media/dvb-frontends/dvb-pll.c index 6d4b2eec67b4..390ecc915096
> > 100644
> > --- a/drivers/media/dvb-frontends/dvb-pll.c
> > +++ b/drivers/media/dvb-frontends/dvb-pll.c
> > @@ -80,8 +80,8 @@ struct dvb_pll_desc {
> >
> > static const struct dvb_pll_desc dvb_pll_thomson_dtt7579 = {
> > .name = "Thomson dtt7579",
> > - .min = 17700,
> > - .max = 85800,
> > + .
Re: DVB-S PCI card regression on 4.19 / 4.20
Em Tue, 20 Nov 2018 10:54:22 +0100 Takashi Iwai escreveu: > On Tue, 20 Nov 2018 10:51:59 +0100, > stakanov wrote: > > > > In data martedì 20 novembre 2018 10:18:10 CET, Mauro Carvalho Chehab ha > > scritto: > > > Em Tue, 20 Nov 2018 09:07:57 +0100 > > > > > > stakanov escreveu: > > > > In data martedì 20 novembre 2018 00:58:41 CET, Mauro Carvalho Chehab ha > > > > > > > > scritto: > > > > > Em Tue, 20 Nov 2018 00:19:54 +0100 > > > > > > > > > > stakanov escreveu: > > > > > > In data martedì 20 novembre 2018 00:08:45 CET, Mauro Carvalho Chehab > > > > > > ha > > > > > > > > > > > > scritto: > > > > > > > uname -a > > > > > > > > > > > > > > > Linux silversurfer 4.20.0-rc3-1.g7e16618-default #1 SMP PREEMPT > > > > > > > > Mon > > > > > > > > Nov 19 > > > > > > > > 18:54:15 UTC 2018 (7e16618) x86_64 x86_64 x86_64 GNU/Linux > > > > > > > > > > > > uname -a > > > > > > > > > > > > > Linux silversurfer 4.20.0-rc3-1.g7e16618-default #1 SMP PREEMPT > > > > > > > Mon > > > > > > > Nov > > > > > > > 19 > > > > > > > 18:54:15 UTC 2018 (7e16618) x86_64 x86_64 x86_64 GNU/Linux > > > > > > > > > > > > from > > > > > > https://download.opensuse.org/repositories/home:/tiwai:/bsc1116374/ > > > > > > standard/x86_64/ > > > > > > > > > > > > So I booted this one, should be the right one. > > > > > > sudo dmesg | grep -i b2c2 should give these additional messages? > > > > > > > > > > > > If Takashi is still around, he could confirm. > > > > > > > > > > Well, if the patch got applied, you should now be getting messages > > > > > similar > > > > > > > > > > (but not identical) to: > > > > > dvb_frontend_get_frequency_limits: frequencies: tuner: > > > > > 915...215, > > > > > > > > > > frontend: 915...215 dvb_pll_attach: delsys: 5, frequency > > > > > range: > > > > > 915..215 > > > > > > > > > > > _ > > > > > > > > > > > > Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln > > > > > > und > > > > > > alte E-Mail-Adresse mitnehmen! https://www.eclipso.de > > > > > > > > > > Thanks, > > > > > Mauro > > > > > > > > My bad. > > > > With just dmesg: > > > > > > > > [ 89.399887] dvb_frontend_get_frequency_limits: frequencies: tuner: > > > > 95...215, frontend: 95000...215000 > > > > [ 95.020149] dvb_frontend_get_frequency_limits: frequencies: tuner: > > > > 95...215, frontend: 95000...215000 > > > > [ 95.152049] dvb_frontend_get_frequency_limits: frequencies: tuner: > > > > 95...215, frontend: 95000...215000 > > > > [ 95.152058] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0 > > > > frequency 188 out of range (95..2150) > > > > [ 98.356539] dvb_frontend_get_frequency_limits: frequencies: tuner: > > > > 95...215, frontend: 95000...215000 > > > > [ 98.480372] dvb_frontend_get_frequency_limits: frequencies: tuner: > > > > 95...215, frontend: 95000...215000 > > > > [ 98.480381] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0 > > > > frequency 1587500 out of range (95..2150) > > > > [ 100.016823] dvb_frontend_get_frequency_limits: frequencies: tuner: > > > > 95...215, frontend: 95000...215000 > > > > [ 100.140619] dvb_frontend_get_frequency_limits: frequencies: tuner: > > > > 95...215, frontend: 95000...215000 > > > > [ 100.140629] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0 > > > > frequency 1353500 out of range (95..2150) > > > > [ 105.361166] dvb_frontend_get_frequency_limits: frequencies: tuner: > > > > 95...215, frontend: 95000...215000 > > > > [ 105.492972] dvb_frontend_get_frequency_limits: frequencies: tuner: > > > > 95...215, frontend: 95000...215000 > > > > [ 105.492977] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0 > > > > frequency 1944750 out of range (95..2150) > > > > > > > > > > > > Which is, I guess the info you need? > > > > > > Yes, partially. Clearly, the problem is coming from the tuner, with is > > > not reporting the frequency in Hz, but I was hoping to see another > > > message from the tuner driver, in order for me to be sure about what's > > > happening there. > > > > > > Didn't you get any message that starts with "dvb_pll_attach"? > > > > > > The thing with Flexcop is that there are several variations, each one > > > with a different tuner driver. > > > > > > Anyway, I guess I found the trouble: it is trying to use the DVB > > > cache to check the delivery system too early (at attach time). > > > > > > I suspect that the enclosed patch will fix the issue. Could you please > > > test it? > > > > > > Thanks! > > > Mauro > > > > > > > > > diff --git a/drivers/media/dvb-frontends/dvb-pll.c > > > b/drivers/media/dvb-frontends/dvb-pll.c index 6d4b2eec67
Re: DVB-S PCI card regression on 4.19 / 4.20
On Tue, 20 Nov 2018 11:26:04 +0100, Mauro Carvalho Chehab wrote: > > Em Tue, 20 Nov 2018 10:54:22 +0100 > Takashi Iwai escreveu: > > > On Tue, 20 Nov 2018 10:51:59 +0100, > > stakanov wrote: > > > > > > In data martedì 20 novembre 2018 10:18:10 CET, Mauro Carvalho Chehab ha > > > scritto: > > > > Em Tue, 20 Nov 2018 09:07:57 +0100 > > > > > > > > stakanov escreveu: > > > > > In data martedì 20 novembre 2018 00:58:41 CET, Mauro Carvalho Chehab > > > > > ha > > > > > > > > > > scritto: > > > > > > Em Tue, 20 Nov 2018 00:19:54 +0100 > > > > > > > > > > > > stakanov escreveu: > > > > > > > In data martedì 20 novembre 2018 00:08:45 CET, Mauro Carvalho > > > > > > > Chehab > > > > > > > ha > > > > > > > > > > > > > > scritto: > > > > > > > > uname -a > > > > > > > > > > > > > > > > > Linux silversurfer 4.20.0-rc3-1.g7e16618-default #1 SMP > > > > > > > > > PREEMPT > > > > > > > > > Mon > > > > > > > > > Nov 19 > > > > > > > > > 18:54:15 UTC 2018 (7e16618) x86_64 x86_64 x86_64 GNU/Linux > > > > > > > > > > > > > > uname -a > > > > > > > > > > > > > > > Linux silversurfer 4.20.0-rc3-1.g7e16618-default #1 SMP PREEMPT > > > > > > > > Mon > > > > > > > > Nov > > > > > > > > 19 > > > > > > > > 18:54:15 UTC 2018 (7e16618) x86_64 x86_64 x86_64 GNU/Linux > > > > > > > > > > > > > > from > > > > > > > https://download.opensuse.org/repositories/home:/tiwai:/bsc1116374/ > > > > > > > standard/x86_64/ > > > > > > > > > > > > > > So I booted this one, should be the right one. > > > > > > > sudo dmesg | grep -i b2c2 should give these additional messages? > > > > > > > > > > > > > > If Takashi is still around, he could confirm. > > > > > > > > > > > > Well, if the patch got applied, you should now be getting messages > > > > > > similar > > > > > > > > > > > > (but not identical) to: > > > > > > dvb_frontend_get_frequency_limits: frequencies: tuner: > > > > > > 915...215, > > > > > > > > > > > > frontend: 915...215 dvb_pll_attach: delsys: 5, frequency > > > > > > range: > > > > > > 915..215 > > > > > > > > > > > > > _ > > > > > > > > > > > > > > Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt > > > > > > > wechseln > > > > > > > und > > > > > > > alte E-Mail-Adresse mitnehmen! https://www.eclipso.de > > > > > > > > > > > > Thanks, > > > > > > Mauro > > > > > > > > > > My bad. > > > > > With just dmesg: > > > > > > > > > > [ 89.399887] dvb_frontend_get_frequency_limits: frequencies: tuner: > > > > > 95...215, frontend: 95000...215000 > > > > > [ 95.020149] dvb_frontend_get_frequency_limits: frequencies: tuner: > > > > > 95...215, frontend: 95000...215000 > > > > > [ 95.152049] dvb_frontend_get_frequency_limits: frequencies: tuner: > > > > > 95...215, frontend: 95000...215000 > > > > > [ 95.152058] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend > > > > > 0 > > > > > frequency 188 out of range (95..2150) > > > > > [ 98.356539] dvb_frontend_get_frequency_limits: frequencies: tuner: > > > > > 95...215, frontend: 95000...215000 > > > > > [ 98.480372] dvb_frontend_get_frequency_limits: frequencies: tuner: > > > > > 95...215, frontend: 95000...215000 > > > > > [ 98.480381] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend > > > > > 0 > > > > > frequency 1587500 out of range (95..2150) > > > > > [ 100.016823] dvb_frontend_get_frequency_limits: frequencies: tuner: > > > > > 95...215, frontend: 95000...215000 > > > > > [ 100.140619] dvb_frontend_get_frequency_limits: frequencies: tuner: > > > > > 95...215, frontend: 95000...215000 > > > > > [ 100.140629] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend > > > > > 0 > > > > > frequency 1353500 out of range (95..2150) > > > > > [ 105.361166] dvb_frontend_get_frequency_limits: frequencies: tuner: > > > > > 95...215, frontend: 95000...215000 > > > > > [ 105.492972] dvb_frontend_get_frequency_limits: frequencies: tuner: > > > > > 95...215, frontend: 95000...215000 > > > > > [ 105.492977] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend > > > > > 0 > > > > > frequency 1944750 out of range (95..2150) > > > > > > > > > > > > > > > Which is, I guess the info you need? > > > > > > > > Yes, partially. Clearly, the problem is coming from the tuner, with is > > > > not reporting the frequency in Hz, but I was hoping to see another > > > > message from the tuner driver, in order for me to be sure about what's > > > > happening there. > > > > > > > > Didn't you get any message that starts with "dvb_pll_attach"? > > > > > > > > The thing with Flexcop is that there are several variations, each one > > > > with a different tuner driver. > > > > > > > > Anyway, I guess I
Re: DVB-S PCI card regression on 4.19 / 4.20
Em Tue, 20 Nov 2018 12:11:03 +0100 Takashi Iwai escreveu: > On Tue, 20 Nov 2018 11:26:04 +0100, > Mauro Carvalho Chehab wrote: > > > > Em Tue, 20 Nov 2018 10:54:22 +0100 > > Takashi Iwai escreveu: > > > > > On Tue, 20 Nov 2018 10:51:59 +0100, > > > stakanov wrote: > > > > > > > > In data martedì 20 novembre 2018 10:18:10 CET, Mauro Carvalho Chehab ha > > > > scritto: > > > > > Em Tue, 20 Nov 2018 09:07:57 +0100 > > > > > > > > > > stakanov escreveu: > > > > > > In data martedì 20 novembre 2018 00:58:41 CET, Mauro Carvalho > > > > > > Chehab ha > > > > > > > > > > > > scritto: > > > > > > > Em Tue, 20 Nov 2018 00:19:54 +0100 > > > > > > > > > > > > > > stakanov escreveu: > > > > > > > > In data martedì 20 novembre 2018 00:08:45 CET, Mauro Carvalho > > > > > > > > Chehab > > > > > > > > ha > > > > > > > > > > > > > > > > scritto: > > > > > > > > > uname -a > > > > > > > > > > > > > > > > > > > Linux silversurfer 4.20.0-rc3-1.g7e16618-default #1 SMP > > > > > > > > > > PREEMPT > > > > > > > > > > Mon > > > > > > > > > > Nov 19 > > > > > > > > > > 18:54:15 UTC 2018 (7e16618) x86_64 x86_64 x86_64 GNU/Linux > > > > > > > > > > > > > > > > > > > > > > > > > > uname -a > > > > > > > > > > > > > > > > > Linux silversurfer 4.20.0-rc3-1.g7e16618-default #1 SMP > > > > > > > > > PREEMPT Mon > > > > > > > > > Nov > > > > > > > > > 19 > > > > > > > > > 18:54:15 UTC 2018 (7e16618) x86_64 x86_64 x86_64 GNU/Linux > > > > > > > > > > > > > > > > from > > > > > > > > https://download.opensuse.org/repositories/home:/tiwai:/bsc1116374/ > > > > > > > > standard/x86_64/ > > > > > > > > > > > > > > > > So I booted this one, should be the right one. > > > > > > > > sudo dmesg | grep -i b2c2 should give these additional > > > > > > > > messages? > > > > > > > > > > > > > > > > If Takashi is still around, he could confirm. > > > > > > > > > > > > > > Well, if the patch got applied, you should now be getting > > > > > > > messages > > > > > > > similar > > > > > > > > > > > > > > (but not identical) to: > > > > > > > dvb_frontend_get_frequency_limits: frequencies: tuner: > > > > > > > 915...215, > > > > > > > > > > > > > > frontend: 915...215 dvb_pll_attach: delsys: 5, frequency > > > > > > > range: > > > > > > > 915..215 > > > > > > > > > > > > > > > _ > > > > > > > > > > > > > > > > Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt > > > > > > > > wechseln > > > > > > > > und > > > > > > > > alte E-Mail-Adresse mitnehmen! https://www.eclipso.de > > > > > > > > > > > > > > Thanks, > > > > > > > Mauro > > > > > > > > > > > > My bad. > > > > > > With just dmesg: > > > > > > > > > > > > [ 89.399887] dvb_frontend_get_frequency_limits: frequencies: > > > > > > tuner: > > > > > > 95...215, frontend: 95000...215000 > > > > > > [ 95.020149] dvb_frontend_get_frequency_limits: frequencies: > > > > > > tuner: > > > > > > 95...215, frontend: 95000...215000 > > > > > > [ 95.152049] dvb_frontend_get_frequency_limits: frequencies: > > > > > > tuner: > > > > > > 95...215, frontend: 95000...215000 > > > > > > [ 95.152058] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 > > > > > > frontend 0 > > > > > > frequency 188 out of range (95..2150) > > > > > > [ 98.356539] dvb_frontend_get_frequency_limits: frequencies: > > > > > > tuner: > > > > > > 95...215, frontend: 95000...215000 > > > > > > [ 98.480372] dvb_frontend_get_frequency_limits: frequencies: > > > > > > tuner: > > > > > > 95...215, frontend: 95000...215000 > > > > > > [ 98.480381] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 > > > > > > frontend 0 > > > > > > frequency 1587500 out of range (95..2150) > > > > > > [ 100.016823] dvb_frontend_get_frequency_limits: frequencies: > > > > > > tuner: > > > > > > 95...215, frontend: 95000...215000 > > > > > > [ 100.140619] dvb_frontend_get_frequency_limits: frequencies: > > > > > > tuner: > > > > > > 95...215, frontend: 95000...215000 > > > > > > [ 100.140629] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 > > > > > > frontend 0 > > > > > > frequency 1353500 out of range (95..2150) > > > > > > [ 105.361166] dvb_frontend_get_frequency_limits: frequencies: > > > > > > tuner: > > > > > > 95...215, frontend: 95000...215000 > > > > > > [ 105.492972] dvb_frontend_get_frequency_limits: frequencies: > > > > > > tuner: > > > > > > 95...215, frontend: 95000...215000 > > > > > > [ 105.492977] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 > > > > > > frontend 0 > > > > > > frequency 1944750 out of range (95..2150) > > > > > > > > > > > > > > > > > > Which is, I guess the info you need? > > > > > > > > > > Yes, pa
Re: DVB-S PCI card regression on 4.19 / 4.20
Em Tue, 20 Nov 2018 14:20:01 +0100 stakanov escreveu: > In data martedì 20 novembre 2018 13:42:17 CET, Mauro Carvalho Chehab ha > scritto: > > Em Tue, 20 Nov 2018 13:11:58 +0100 > > > > "Stakanov Schufter" escreveu: > > > Sorry for the delay. Apparently my smtp exits are blocking me (for > > > whatever reason). I am trying now via web mailer. > > > > > > > > > In short, no it does not work. Only EPG, no pic no sound. > > > But the error message in dmesg is gone I think. > > > > > > uname -a > > > Linux silversurfer 4.20.0-rc3-2.gfe5d771-default #1 SMP PREEMPT Tue Nov 20 > > > 09:35:04 UTC 2018 (fe5d771) x86_64 x86_64 x86_64 GNU > > > > > > dmesg: > > > > > > [6.412792] b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV receiver > > > chip loaded successfully > > > [6.416645] flexcop-pci: will use the HW PID filter. > > > [6.416648] flexcop-pci: card revision 2 > > > [6.423749] scsi host10: usb-storage 9-3.1:1.0 > > > [6.423842] usbcore: registered new interface driver usb-storage > > > [6.426029] usbcore: registered new interface driver uas > > > [6.439251] dvbdev: DVB: registering new adapter (FlexCop Digital TV > > > device) > > > [6.440845] b2c2-flexcop: MAC address = 00:d0:d7:11:8b:58 > > > > > > [6.694999] dvb_pll_attach: delsys: 0, frequency range: > > > 95000..215000 > > > [6.695001] b2c2-flexcop: found 'ST STV0299 DVB-S' . > > > [6.695004] b2c2_flexcop_pci :06:06.0: DVB: registering adapter 0 > > > frontend 0 (ST STV0299 DVB-S)... > > > [6.695050] b2c2-flexcop: initialization of 'Sky2PC/SkyStar 2 DVB-S rev > > > 2.6' at the 'PCI' bus controlled by a 'FlexCopIIb' complete > > > > Well, the Kernel bug is probably gone. I don't see any other recent > > changes that would be affecting the b2c2 flexcop driver. > > > > If you're successfully getting EPG data from the transponders, then it > > should also be receiving audio and video channels too, as, for the Kernel, > > there's no difference if a given program ID (PID) contains EPG, audio or > > video. > > > > At the BZ, you're saying that you're using Kaffeine, right? > > > > There are a few reasons why you can't watch audio/video, but you're > > able to get EPG tables: > > > > - the audio/video PID had changed; > > - the audio/video is now encrypted; > > - too weak signal (or bad cabling). > > > > The EPG data comes several times per second on well known PIDs, via a low > > bandwidth PID and it is not encrypted. So, it is usually trivial to get > > it. > > > > I suggest you to re-scan your channels on Kaffeine, in order to force > > it to get the new PIDs. Also, please check that the channels you're > > trying to use are Free to the Air (FTA). > > > > You can also use libdvbv5 tools in order to check if you're not > > losing data due to weak signal/bad cabling. The newer versions > > of dvbv5-zap have a logic with detects and report data loses, when > > started on monitor mode (-m command line option). It also prints > > the transponder bandwidth, and check what PIDs are received. > > > > It is very useful to debug problems. > > > > Thanks, > > Mauro > > I checked again and: > [sudo] password di root: > [6.412792] b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV receiver > chip > loaded successfully > [6.440845] b2c2-flexcop: MAC address = 00:d0:d7:11:8b:58 > [6.695001] b2c2-flexcop: found 'ST STV0299 DVB-S' . > [6.695004] b2c2_flexcop_pci :06:06.0: DVB: registering adapter 0 > frontend 0 (ST STV0299 DVB-S)... > [6.695050] b2c2-flexcop: initialization of 'Sky2PC/SkyStar 2 DVB-S rev > 2.6' at the 'PCI' bus controlled by a 'FlexCopIIb' complete > [ 6265.403360] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0 > frequency 10719000 out of range (95..215) > [ 6265.405702] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0 > frequency 10723000 out of range (95..215) > [ 6265.407120] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0 > frequency 10757000 out of range (95..215) > [ 6265.408556] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0 > frequency 10775000 out of range (95..215) > [ 6265.409754] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0 > frequency 10795000 out of range (95..215) > [ 6399.837806] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0 > frequency 12713000 out of range (95..215) > [ 6399.839144] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0 > frequency 12731000 out of range (95..215) Ok. Now, min/max frequencies are at the same scale. For DVB-S, dvb_frontend_get_frequency_limits() returns both in kHz, so the frequency range is now OK. The tuning frequency is wrong through. 10,719,000 kHz - e. g. 10,719 MHz seems to be the transponder frequency you're trying to tune, and not the intermediate frequency used at the DVB-S board. That sounds to me either a wrong LNBf setting or a bug at libdvbv5
Re: DVB-S PCI card regression on 4.19 / 4.20
On 20/11/2018 16:08, Mauro Carvalho Chehab wrote: > Em Tue, 20 Nov 2018 14:20:01 +0100 > Ok. Now, min/max frequencies are at the same scale. For DVB-S, > dvb_frontend_get_frequency_limits() returns both in kHz, so the frequency > range is now OK. > > The tuning frequency is wrong through. 10,719,000 kHz - e. g. 10,719 MHz > seems to be the transponder frequency you're trying to tune, and not the > intermediate frequency used at the DVB-S board. > > That sounds to me either a wrong LNBf setting or a bug at libdvbv5 or > at Kaffeine's side. What happens is that the typical European LNBFs are: > > 1) the "old" universal one: > > UNIVERSAL > Universal, Europe > Freqs : 10800 to 11800 MHz, LO: 9750 MHz > Freqs : 11600 to 12700 MHz, LO: 10600 MHz I am pretty certain this type is obsolete it doesn't look right for 9750Mhz oscillator. I am sure it was 1Mhz or 96?? or something like that for old analogue transmissions of 20 years ago > > 2) the "new" universal one, with seems to be used by most modern > satellite dishes in Europe nowadays: > > EXTENDED > Astra 1E, European Universal Ku (extended) This needs renaming as 1E has long gone. Certainly this type is used for Astra 19.2 and 28.2. Ideally we should use a default LNB type for each Satellite either in libdvbv5, Kaffeine or respective tables. Regards Malcolm
Re: DVB-S PCI card regression on 4.19 / 4.20
Em Wed, 21 Nov 2018 21:20:35 + Malcolm Priestley escreveu: > On 20/11/2018 16:08, Mauro Carvalho Chehab wrote: > > Em Tue, 20 Nov 2018 14:20:01 +0100 > > > > Ok. Now, min/max frequencies are at the same scale. For DVB-S, > > dvb_frontend_get_frequency_limits() returns both in kHz, so the frequency > > range is now OK. > > > > The tuning frequency is wrong through. 10,719,000 kHz - e. g. 10,719 MHz > > seems to be the transponder frequency you're trying to tune, and not the > > intermediate frequency used at the DVB-S board. > > > > That sounds to me either a wrong LNBf setting or a bug at libdvbv5 or > > at Kaffeine's side. What happens is that the typical European LNBFs are: > > > > 1) the "old" universal one: > > > > UNIVERSAL > > Universal, Europe > > Freqs : 10800 to 11800 MHz, LO: 9750 MHz > > Freqs : 11600 to 12700 MHz, LO: 10600 MHz > I am pretty certain this type is obsolete it doesn't look right for 9750Mhz > oscillator. > > I am sure it was 1Mhz or 96?? or something like that for old analogue > transmissions of > 20 years ago This is the first LNBf entry at dvb-tools. I'm pretty sure people used it for years, but yeah, I won't doubt that this is an obsolete entry. Yet, people may still be using old antennas somewhere, so we can't simply remove it or replace. Maybe we could change its description to say that this is the old universal standard. > > > > 2) the "new" universal one, with seems to be used by most modern > > satellite dishes in Europe nowadays: > > > > EXTENDED > > Astra 1E, European Universal Ku (extended) > This needs renaming as 1E has long gone. Agreed. > > Certainly this type is used for Astra 19.2 and 28.2. > > Ideally we should use a default LNB type for each Satellite either in > libdvbv5, Kaffeine or respective tables. Neither libdvbv5 nor Kaffeine has a concept of "default". The default varies from the region of the globe where you're sitting, and the actual satellite to where an antenna system is pointed. Also, it changes over time. Thanks, Mauro
Re: DVB-S PCI card regression on 4.19 / 4.20
Stakanov, Em Tue, 20 Nov 2018 14:08:55 -0200 Mauro Carvalho Chehab escreveu: > Em Tue, 20 Nov 2018 14:20:01 +0100 > stakanov escreveu: > > > In data martedì 20 novembre 2018 13:42:17 CET, Mauro Carvalho Chehab ha > > scritto: > > > Em Tue, 20 Nov 2018 13:11:58 +0100 > > > > > > "Stakanov Schufter" escreveu: > > > > Sorry for the delay. Apparently my smtp exits are blocking me (for > > > > whatever reason). I am trying now via web mailer. > > > > > > > > > > > > In short, no it does not work. Only EPG, no pic no sound. > > > > But the error message in dmesg is gone I think. > > > > > > > > uname -a > > > > Linux silversurfer 4.20.0-rc3-2.gfe5d771-default #1 SMP PREEMPT Tue Nov > > > > 20 > > > > 09:35:04 UTC 2018 (fe5d771) x86_64 x86_64 x86_64 GNU > > > > > > > > dmesg: > > > > > > > > [6.412792] b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV > > > > receiver > > > > chip loaded successfully > > > > [6.416645] flexcop-pci: will use the HW PID filter. > > > > [6.416648] flexcop-pci: card revision 2 > > > > [6.423749] scsi host10: usb-storage 9-3.1:1.0 > > > > [6.423842] usbcore: registered new interface driver usb-storage > > > > [6.426029] usbcore: registered new interface driver uas > > > > [6.439251] dvbdev: DVB: registering new adapter (FlexCop Digital TV > > > > device) > > > > [6.440845] b2c2-flexcop: MAC address = 00:d0:d7:11:8b:58 > > > > > > > > [6.694999] dvb_pll_attach: delsys: 0, frequency range: > > > > 95000..215000 > > > > [6.695001] b2c2-flexcop: found 'ST STV0299 DVB-S' . > > > > [6.695004] b2c2_flexcop_pci :06:06.0: DVB: registering adapter 0 > > > > frontend 0 (ST STV0299 DVB-S)... > > > > [6.695050] b2c2-flexcop: initialization of 'Sky2PC/SkyStar 2 DVB-S > > > > rev > > > > 2.6' at the 'PCI' bus controlled by a 'FlexCopIIb' complete > > > > > > Well, the Kernel bug is probably gone. I don't see any other recent > > > changes that would be affecting the b2c2 flexcop driver. > > > > > > If you're successfully getting EPG data from the transponders, then it > > > should also be receiving audio and video channels too, as, for the Kernel, > > > there's no difference if a given program ID (PID) contains EPG, audio or > > > video. > > > > > > At the BZ, you're saying that you're using Kaffeine, right? > > > > > > There are a few reasons why you can't watch audio/video, but you're > > > able to get EPG tables: > > > > > > - the audio/video PID had changed; > > > - the audio/video is now encrypted; > > > - too weak signal (or bad cabling). > > > > > > The EPG data comes several times per second on well known PIDs, via a low > > > bandwidth PID and it is not encrypted. So, it is usually trivial to get > > > it. > > > > > > I suggest you to re-scan your channels on Kaffeine, in order to force > > > it to get the new PIDs. Also, please check that the channels you're > > > trying to use are Free to the Air (FTA). > > > > > > You can also use libdvbv5 tools in order to check if you're not > > > losing data due to weak signal/bad cabling. The newer versions > > > of dvbv5-zap have a logic with detects and report data loses, when > > > started on monitor mode (-m command line option). It also prints > > > the transponder bandwidth, and check what PIDs are received. > > > > > > It is very useful to debug problems. > > > > > > Thanks, > > > Mauro > > > > I checked again and: > > [sudo] password di root: > > [6.412792] b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV receiver > > chip > > loaded successfully > > [6.440845] b2c2-flexcop: MAC address = 00:d0:d7:11:8b:58 > > [6.695001] b2c2-flexcop: found 'ST STV0299 DVB-S' . > > [6.695004] b2c2_flexcop_pci :06:06.0: DVB: registering adapter 0 > > frontend 0 (ST STV0299 DVB-S)... > > [6.695050] b2c2-flexcop: initialization of 'Sky2PC/SkyStar 2 DVB-S rev > > 2.6' at the 'PCI' bus controlled by a 'FlexCopIIb' complete > > [ 6265.403360] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0 > > frequency 10719000 out of range (95..215) > > [ 6265.405702] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0 > > frequency 10723000 out of range (95..215) > > [ 6265.407120] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0 > > frequency 10757000 out of range (95..215) > > [ 6265.408556] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0 > > frequency 10775000 out of range (95..215) > > [ 6265.409754] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0 > > frequency 10795000 out of range (95..215) > > [ 6399.837806] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0 > > frequency 12713000 out of range (95..215) > > [ 6399.839144] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0 > > frequency 12731000 out of range (95..215) > > Ok. Now, min/max frequencies are at the same scale. For DVB-S, > dvb_frontend_get_frequency_limits()
Re: DVB-S PCI card regression on 4.19 / 4.20
Hi Mauro! In data giovedì 22 novembre 2018 17:19:08 CET, Mauro Carvalho Chehab ha scritto: > Stakanov, > > Em Tue, 20 Nov 2018 14:08:55 -0200 > > Mauro Carvalho Chehab escreveu: > > Em Tue, 20 Nov 2018 14:20:01 +0100 > > > > stakanov escreveu: > > > In data martedì 20 novembre 2018 13:42:17 CET, Mauro Carvalho Chehab ha > > > > > > scritto: > > > > Em Tue, 20 Nov 2018 13:11:58 +0100 > > > > > > > > "Stakanov Schufter" escreveu: > > > > > Sorry for the delay. Apparently my smtp exits are blocking me (for > > > > > whatever reason). I am trying now via web mailer. > > > > > > > > > > > > > > > In short, no it does not work. Only EPG, no pic no sound. > > > > > But the error message in dmesg is gone I think. > > > > > > > > > > uname -a > > > > > Linux silversurfer 4.20.0-rc3-2.gfe5d771-default #1 SMP PREEMPT Tue > > > > > Nov 20 > > > > > 09:35:04 UTC 2018 (fe5d771) x86_64 x86_64 x86_64 GNU > > > > > > > > > > dmesg: > > > > > > > > > > [6.412792] b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV > > > > > receiver > > > > > chip loaded successfully > > > > > [6.416645] flexcop-pci: will use the HW PID filter. > > > > > [6.416648] flexcop-pci: card revision 2 > > > > > [6.423749] scsi host10: usb-storage 9-3.1:1.0 > > > > > [6.423842] usbcore: registered new interface driver usb-storage > > > > > [6.426029] usbcore: registered new interface driver uas > > > > > [6.439251] dvbdev: DVB: registering new adapter (FlexCop Digital > > > > > TV > > > > > device) > > > > > [6.440845] b2c2-flexcop: MAC address = 00:d0:d7:11:8b:58 > > > > > > > > > > [6.694999] dvb_pll_attach: delsys: 0, frequency range: > > > > > 95000..215000 > > > > > [6.695001] b2c2-flexcop: found 'ST STV0299 DVB-S' . > > > > > [6.695004] b2c2_flexcop_pci :06:06.0: DVB: registering > > > > > adapter 0 > > > > > frontend 0 (ST STV0299 DVB-S)... > > > > > [6.695050] b2c2-flexcop: initialization of 'Sky2PC/SkyStar 2 > > > > > DVB-S rev > > > > > 2.6' at the 'PCI' bus controlled by a 'FlexCopIIb' complete > > > > > > > > Well, the Kernel bug is probably gone. I don't see any other recent > > > > changes that would be affecting the b2c2 flexcop driver. > > > > > > > > If you're successfully getting EPG data from the transponders, then it > > > > should also be receiving audio and video channels too, as, for the > > > > Kernel, > > > > there's no difference if a given program ID (PID) contains EPG, audio > > > > or > > > > video. > > > > > > > > At the BZ, you're saying that you're using Kaffeine, right? > > > > > > > > There are a few reasons why you can't watch audio/video, but you're > > > > > > > > able to get EPG tables: > > > > - the audio/video PID had changed; > > > > - the audio/video is now encrypted; > > > > - too weak signal (or bad cabling). > > > > > > > > The EPG data comes several times per second on well known PIDs, via a > > > > low > > > > bandwidth PID and it is not encrypted. So, it is usually trivial to > > > > get > > > > it. > > > > > > > > I suggest you to re-scan your channels on Kaffeine, in order to force > > > > it to get the new PIDs. Also, please check that the channels you're > > > > trying to use are Free to the Air (FTA). > > > > > > > > You can also use libdvbv5 tools in order to check if you're not > > > > losing data due to weak signal/bad cabling. The newer versions > > > > of dvbv5-zap have a logic with detects and report data loses, when > > > > started on monitor mode (-m command line option). It also prints > > > > the transponder bandwidth, and check what PIDs are received. > > > > > > > > It is very useful to debug problems. > > > > > > > > Thanks, > > > > Mauro > > > > > > I checked again and: > > > [sudo] password di root: > > > [6.412792] b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV > > > receiver chip loaded successfully > > > [6.440845] b2c2-flexcop: MAC address = 00:d0:d7:11:8b:58 > > > [6.695001] b2c2-flexcop: found 'ST STV0299 DVB-S' . > > > [6.695004] b2c2_flexcop_pci :06:06.0: DVB: registering adapter 0 > > > frontend 0 (ST STV0299 DVB-S)... > > > [6.695050] b2c2-flexcop: initialization of 'Sky2PC/SkyStar 2 DVB-S > > > rev > > > 2.6' at the 'PCI' bus controlled by a 'FlexCopIIb' complete > > > [ 6265.403360] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0 > > > frequency 10719000 out of range (95..215) > > > [ 6265.405702] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0 > > > frequency 10723000 out of range (95..215) > > > [ 6265.407120] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0 > > > frequency 10757000 out of range (95..215) > > > [ 6265.408556] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0 > > > frequency 10775000 out of range (95..215) > > > [ 6265.409754] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0 > > > frequency 10795000 out of range (95..215) > > > [ 6399.83780
Re: DVB-S PCI card regression on 4.19 / 4.20
Em Thu, 22 Nov 2018 19:58:19 +0100 stakanov escreveu: > Hi Mauro! > > In data giovedì 22 novembre 2018 17:19:08 CET, Mauro Carvalho Chehab ha > scritto: > > Stakanov, > > > > Em Tue, 20 Nov 2018 14:08:55 -0200 > > > > Mauro Carvalho Chehab escreveu: > > > Em Tue, 20 Nov 2018 14:20:01 +0100 > > > > > > stakanov escreveu: > > > > In data martedì 20 novembre 2018 13:42:17 CET, Mauro Carvalho Chehab ha > > > > > > > > scritto: > > > > > Em Tue, 20 Nov 2018 13:11:58 +0100 > > > > > > > > > > "Stakanov Schufter" escreveu: > > > > > > Sorry for the delay. Apparently my smtp exits are blocking me (for > > > > > > whatever reason). I am trying now via web mailer. > > > > > > > > > > > > > > > > > > In short, no it does not work. Only EPG, no pic no sound. > > > > > > But the error message in dmesg is gone I think. > > > > > > > > > > > > uname -a > > > > > > Linux silversurfer 4.20.0-rc3-2.gfe5d771-default #1 SMP PREEMPT Tue > > > > > > Nov 20 > > > > > > 09:35:04 UTC 2018 (fe5d771) x86_64 x86_64 x86_64 GNU > > > > > > > > > > > > dmesg: > > > > > > > > > > > > [6.412792] b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV > > > > > > receiver > > > > > > chip loaded successfully > > > > > > [6.416645] flexcop-pci: will use the HW PID filter. > > > > > > [6.416648] flexcop-pci: card revision 2 > > > > > > [6.423749] scsi host10: usb-storage 9-3.1:1.0 > > > > > > [6.423842] usbcore: registered new interface driver usb-storage > > > > > > [6.426029] usbcore: registered new interface driver uas > > > > > > [6.439251] dvbdev: DVB: registering new adapter (FlexCop Digital > > > > > > TV > > > > > > device) > > > > > > [6.440845] b2c2-flexcop: MAC address = 00:d0:d7:11:8b:58 > > > > > > > > > > > > [6.694999] dvb_pll_attach: delsys: 0, frequency range: > > > > > > 95000..215000 > > > > > > [6.695001] b2c2-flexcop: found 'ST STV0299 DVB-S' . > > > > > > [6.695004] b2c2_flexcop_pci :06:06.0: DVB: registering > > > > > > adapter 0 > > > > > > frontend 0 (ST STV0299 DVB-S)... > > > > > > [6.695050] b2c2-flexcop: initialization of 'Sky2PC/SkyStar 2 > > > > > > DVB-S rev > > > > > > 2.6' at the 'PCI' bus controlled by a 'FlexCopIIb' complete > > > > > > > > > > Well, the Kernel bug is probably gone. I don't see any other recent > > > > > changes that would be affecting the b2c2 flexcop driver. > > > > > > > > > > If you're successfully getting EPG data from the transponders, then it > > > > > should also be receiving audio and video channels too, as, for the > > > > > Kernel, > > > > > there's no difference if a given program ID (PID) contains EPG, audio > > > > > or > > > > > video. > > > > > > > > > > At the BZ, you're saying that you're using Kaffeine, right? > > > > > > > > > > There are a few reasons why you can't watch audio/video, but you're > > > > > > > > > > able to get EPG tables: > > > > > - the audio/video PID had changed; > > > > > - the audio/video is now encrypted; > > > > > - too weak signal (or bad cabling). > > > > > > > > > > The EPG data comes several times per second on well known PIDs, via a > > > > > low > > > > > bandwidth PID and it is not encrypted. So, it is usually trivial to > > > > > get > > > > > it. > > > > > > > > > > I suggest you to re-scan your channels on Kaffeine, in order to force > > > > > it to get the new PIDs. Also, please check that the channels you're > > > > > trying to use are Free to the Air (FTA). > > > > > > > > > > You can also use libdvbv5 tools in order to check if you're not > > > > > losing data due to weak signal/bad cabling. The newer versions > > > > > of dvbv5-zap have a logic with detects and report data loses, when > > > > > started on monitor mode (-m command line option). It also prints > > > > > the transponder bandwidth, and check what PIDs are received. > > > > > > > > > > It is very useful to debug problems. > > > > > > > > > > Thanks, > > > > > Mauro > > > > > > > > I checked again and: > > > > [sudo] password di root: > > > > [6.412792] b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV > > > > receiver chip loaded successfully > > > > [6.440845] b2c2-flexcop: MAC address = 00:d0:d7:11:8b:58 > > > > [6.695001] b2c2-flexcop: found 'ST STV0299 DVB-S' . > > > > [6.695004] b2c2_flexcop_pci :06:06.0: DVB: registering adapter 0 > > > > frontend 0 (ST STV0299 DVB-S)... > > > > [6.695050] b2c2-flexcop: initialization of 'Sky2PC/SkyStar 2 DVB-S > > > > rev > > > > 2.6' at the 'PCI' bus controlled by a 'FlexCopIIb' complete > > > > [ 6265.403360] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0 > > > > frequency 10719000 out of range (95..215) > > > > [ 6265.405702] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0 > > > > frequency 10723000 out of range (95..215) > > > > [ 6265.407120] b2c2_flexcop_pci :06:06.0: DVB: adapter 0 frontend 0 > > > > frequency 10757000 out of range (95..215)
Re: DVB-S PCI card regression on 4.19 / 4.20
Hello Mauro. Thank you so much, for this fast reply and especially for the detailed indications. I expected to have a lack of knowledge. Well, I am replying to the question as of below: (for convenience I did cut the before text, if you deem it useful for the list I can then correct that in the next posts). In data giovedì 22 novembre 2018 21:06:11 CET, Mauro Carvalho Chehab ha scritto: > Are you sure that the difference is just the Kernel version? Perhaps you > also updated some other package. To be clear: I had the same system(!) with all three kernel 4.18.15-1, 4.19.1 (when the problem did arise) and 4.20.2 rc3 from Takashi's repo) installed. In this very configuration: if one booted in 4.18 (that is in perfect parity with all other packages) the card worked. 4.19.1 no. And the last kernel the same. So whatever might be different, forcefully it has to be in the kernel. (Which is not really a problem if I manage to make it work, so settings will be known to others or, if not, we will find out what is different, and all will be happy. As you see I am still optimist). I will proceed as indicated and report back here tomorrow. Regards. _ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de
Re: DVB-S PCI card regression on 4.19 / 4.20
Em Thu, 22 Nov 2018 21:19:49 +0100 stakanov escreveu: > Hello Mauro. > > Thank you so much, for this fast reply and especially for the detailed > indications. I expected to have a lack of knowledge. > > Well, I am replying to the question as of below: (for convenience I did cut > the before text, if you deem it useful for the list I can then correct that > in > the next posts). > > In data giovedì 22 novembre 2018 21:06:11 CET, Mauro Carvalho Chehab ha > scritto: > > Are you sure that the difference is just the Kernel version? Perhaps you > > also updated some other package. > > To be clear: I had the same system(!) with all three kernel 4.18.15-1, 4.19.1 > > (when the problem did arise) and 4.20.2 rc3 from Takashi's repo) installed. Ok, so rebooting to 4.18.15-1 solves the issue? Also, what GPU driver are you using? In any case, by using the old "Universal" LNBf, you're likely missing some transponders, and missing several channels. > In this very configuration: if one booted in 4.18 (that is in perfect parity > with all other packages) the card worked. 4.19.1 no. And the last kernel the > same. So whatever might be different, forcefully it has to be in the kernel. > (Which is not really a problem if I manage to make it work, so settings will > be known to others or, if not, we will find out what is different, and all > will be happy. As you see I am still optimist). Well, we don't want regressions in Kernel. If there's an issue there, it should be fixed. However, I can't think on any other changes since 4.18 that would be causing troubles for b2c2 driver. See, the only change at the driver itself is just a simple API replacement that wouldn't cause this kind of problems: $ git log --oneline v4.18.. drivers/media/common/b2c2/ c0decac19da3 media: use strscpy() instead of strlcpy() There were a few changes at the DVB core: $ git log --no-merges --oneline v4.18.. drivers/media/dvb-core/ f3efe15a2f05 media: dvb: use signal types to discover pads b5d3206112dd media: dvb: dmxdev: move compat_ioctl handling to dmxdev.c cc1e6315e83d media: replace strcpy() by strscpy() c0decac19da3 media: use strscpy() instead of strlcpy() fd89e0bb6ebf media: videobuf2-core: integrate with media requests db6e8d57e2cd media: vb2: store userspace data in vb2_v4l2_buffer 6a2a1ca34ca6 media: dvb_frontend: ensure that the step is ok for both FE and tuner f1b1eabff0eb media: dvb: represent min/max/step/tolerance freqs in Hz a3f90c75b833 media: dvb: convert tuner_info frequencies to Hz 6706fe55af6f media: dvb_ca_en50221: off by one in dvb_ca_en50221_io_do_ioctl() 4d1e4545a659 media: mark entity-intf links as IMMUTABLE But, on a first glance, the only ones that has potential to cause issues were the ones addressed that the patch I wrote (merged by Takashi). If you're really receiving data from EPG (you may just have it cached), it means that the DVB driver is doing the right thing. Btw, to be sure that you're not just seeing the old EPG data, you should move or remove this file: ~/.local/share/kaffeine/epgdata.dvb Kaffeine will generate a new one again once it tunes into a TV channel. > I will proceed as indicated and report back here tomorrow. Ok. Thanks, Mauro
Re: DVB-S PCI card regression on 4.19 / 4.20
In data giovedì 22 novembre 2018 21:35:49 CET, Mauro Carvalho Chehab ha scritto: > Em Thu, 22 Nov 2018 21:19:49 +0100 > > stakanov escreveu: > > Hello Mauro. > > > > Thank you so much, for this fast reply and especially for the detailed > > indications. I expected to have a lack of knowledge. > > > > Well, I am replying to the question as of below: (for convenience I did > > cut the before text, if you deem it useful for the list I can then > > correct that in the next posts). > > > > In data giovedì 22 novembre 2018 21:06:11 CET, Mauro Carvalho Chehab ha > > > > scritto: > > > Are you sure that the difference is just the Kernel version? Perhaps you > > > also updated some other package. > > > > To be clear: I had the same system(!) with all three kernel 4.18.15-1, > > 4.19.1 (when the problem did arise) and 4.20.2 rc3 from Takashi's repo) > > installed. > Ok, so rebooting to 4.18.15-1 solves the issue? > > Also, what GPU driver are you using? > > In any case, by using the old "Universal" LNBf, you're likely missing some > transponders, and missing several channels. > > > In this very configuration: if one booted in 4.18 (that is in perfect > > parity with all other packages) the card worked. 4.19.1 no. And the last > > kernel the same. So whatever might be different, forcefully it has to be > > in the kernel. (Which is not really a problem if I manage to make it > > work, so settings will be known to others or, if not, we will find out > > what is different, and all will be happy. As you see I am still > > optimist). > > Well, we don't want regressions in Kernel. If there's an issue there, > it should be fixed. However, I can't think on any other changes since > 4.18 that would be causing troubles for b2c2 driver. > > See, the only change at the driver itself is just a simple API > replacement that wouldn't cause this kind of problems: > > $ git log --oneline v4.18.. drivers/media/common/b2c2/ > c0decac19da3 media: use strscpy() instead of strlcpy() > > There were a few changes at the DVB core: > > $ git log --no-merges --oneline v4.18.. drivers/media/dvb-core/ > f3efe15a2f05 media: dvb: use signal types to discover pads > b5d3206112dd media: dvb: dmxdev: move compat_ioctl handling to dmxdev.c > cc1e6315e83d media: replace strcpy() by strscpy() > c0decac19da3 media: use strscpy() instead of strlcpy() > fd89e0bb6ebf media: videobuf2-core: integrate with media requests > db6e8d57e2cd media: vb2: store userspace data in vb2_v4l2_buffer > 6a2a1ca34ca6 media: dvb_frontend: ensure that the step is ok for both FE > and tuner f1b1eabff0eb media: dvb: represent min/max/step/tolerance freqs > in Hz a3f90c75b833 media: dvb: convert tuner_info frequencies to Hz > 6706fe55af6f media: dvb_ca_en50221: off by one in > dvb_ca_en50221_io_do_ioctl() 4d1e4545a659 media: mark entity-intf links as > IMMUTABLE > > But, on a first glance, the only ones that has potential to cause issues > were the ones addressed that the patch I wrote (merged by Takashi). > > If you're really receiving data from EPG (you may just have it > cached), it means that the DVB driver is doing the right thing. > > Btw, to be sure that you're not just seeing the old EPG data, you > should move or remove this file: > > ~/.local/share/kaffeine/epgdata.dvb > > Kaffeine will generate a new one again once it tunes into a TV channel. > > > I will proceed as indicated and report back here tomorrow. > > Ok. > > Thanks, > Mauro Further the question: >Also, what GPU driver are you using? Hope that this responding to what you ask for: silversurfer:~ # lspci | grep VGA 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] silversurfer:~ # lsmod | grep "kms\|drm" drm_kms_helper204800 1 radeon syscopyarea16384 1 drm_kms_helper sysfillrect16384 1 drm_kms_helper sysimgblt 16384 1 drm_kms_helper fb_sys_fops16384 1 drm_kms_helper drm 491520 16 drm_kms_helper,radeon,ttm silversurfer:~ # find /dev -group video /dev/dvb/adapter2/net0 /dev/dvb/adapter2/dvr0 /dev/dvb/adapter2/demux0 /dev/dvb/adapter2/frontend0 /dev/dvb/adapter1/net0 /dev/dvb/adapter1/dvr0 /dev/dvb/adapter1/demux0 /dev/dvb/adapter1/frontend0 /dev/dvb/adapter0/frontend0 /dev/dvb/adapter0/net0 /dev/dvb/adapter0/dvr0 /dev/dvb/adapter0/demux0 /dev/fb0 /dev/dri/card0 silversurfer:~ # cat /proc/cmdline BOOT_IMAGE=/vmlinuz-4.20.0-rc3-2.gfe5d771-default root=UUID=30e41f49-6c35-4381-9274-10491d5004ef resume=/dev/disk/by-uuid/ e20f311b-d45c-49ea-846f-8eac8aaa0d85 splash=silent quiet showopts iommu=soft silversurfer:~ # find /etc/modprobe.d/ /etc/modprobe.d/ /etc/modprobe.d/firewalld-sysctls.conf /etc/modprobe.d/truescale.conf /etc/modprobe.d/50-ipw2200.conf /etc/modprobe.d/50-yast.conf /etc/modprobe.d/50-yast.conf.YaST2save /etc/modprobe.d/tuned.conf /etc/modprobe.d/50-a
Re: DVB-S PCI card regression on 4.19 / 4.20
In data giovedì 22 novembre 2018 21:35:49 CET, Mauro Carvalho Chehab ha scritto: > Em Thu, 22 Nov 2018 21:19:49 +0100 > > stakanov escreveu: > > Hello Mauro. > > > > Thank you so much, for this fast reply and especially for the detailed > > indications. I expected to have a lack of knowledge. > > > > Well, I am replying to the question as of below: (for convenience I did > > cut the before text, if you deem it useful for the list I can then > > correct that in the next posts). > > > > In data giovedì 22 novembre 2018 21:06:11 CET, Mauro Carvalho Chehab ha > > > > scritto: > > > Are you sure that the difference is just the Kernel version? Perhaps you > > > also updated some other package. > > > > To be clear: I had the same system(!) with all three kernel 4.18.15-1, > > 4.19.1 (when the problem did arise) and 4.20.2 rc3 from Takashi's repo) > > installed. > Ok, so rebooting to 4.18.15-1 solves the issue? > > Also, what GPU driver are you using? > > In any case, by using the old "Universal" LNBf, you're likely missing some > transponders, and missing several channels. > > > In this very configuration: if one booted in 4.18 (that is in perfect > > parity with all other packages) the card worked. 4.19.1 no. And the last > > kernel the same. So whatever might be different, forcefully it has to be > > in the kernel. (Which is not really a problem if I manage to make it > > work, so settings will be known to others or, if not, we will find out > > what is different, and all will be happy. As you see I am still > > optimist). > > Well, we don't want regressions in Kernel. If there's an issue there, > it should be fixed. However, I can't think on any other changes since > 4.18 that would be causing troubles for b2c2 driver. > > See, the only change at the driver itself is just a simple API > replacement that wouldn't cause this kind of problems: > > $ git log --oneline v4.18.. drivers/media/common/b2c2/ > c0decac19da3 media: use strscpy() instead of strlcpy() > > There were a few changes at the DVB core: > > $ git log --no-merges --oneline v4.18.. drivers/media/dvb-core/ > f3efe15a2f05 media: dvb: use signal types to discover pads > b5d3206112dd media: dvb: dmxdev: move compat_ioctl handling to dmxdev.c > cc1e6315e83d media: replace strcpy() by strscpy() > c0decac19da3 media: use strscpy() instead of strlcpy() > fd89e0bb6ebf media: videobuf2-core: integrate with media requests > db6e8d57e2cd media: vb2: store userspace data in vb2_v4l2_buffer > 6a2a1ca34ca6 media: dvb_frontend: ensure that the step is ok for both FE > and tuner f1b1eabff0eb media: dvb: represent min/max/step/tolerance freqs > in Hz a3f90c75b833 media: dvb: convert tuner_info frequencies to Hz > 6706fe55af6f media: dvb_ca_en50221: off by one in > dvb_ca_en50221_io_do_ioctl() 4d1e4545a659 media: mark entity-intf links as > IMMUTABLE > > But, on a first glance, the only ones that has potential to cause issues > were the ones addressed that the patch I wrote (merged by Takashi). > > If you're really receiving data from EPG (you may just have it > cached), it means that the DVB driver is doing the right thing. > > Btw, to be sure that you're not just seeing the old EPG data, you > should move or remove this file: > > ~/.local/share/kaffeine/epgdata.dvb > > Kaffeine will generate a new one again once it tunes into a TV channel. > > > I will proceed as indicated and report back here tomorrow. > > Ok. > > Thanks, > Mauro So, I confirm that: a) 4.18.15-1 this card worked flawlessly. b) above that, included the kernel with correction, it does not work any more. c) downloading and copying the respective firmware from openelec does not change, the card stays dead. d) astra: no search of channels, search interrupted after seconds. e) hotbird: search without finding any channel - only noise f) lnbf setting was to "Astra E" as indicated. g) after erasing the file in local/share it is clear that EPG data does NOT work either. When using the channels as they were recorded before, the signal strength is 0 but the fictional led is green (as if it would receive). No picture, no tone, no channel sync, no EPG. A brick. So, with 4.18 that worked, only that now (due to an error I lost access to the 4.18.15-1 driver of TW, so if Takashi has a link, I can reinstall it and we can check if, parity all packages this is still the case. I assure you that it was, but that would be a perfect proof. Firmware downloaded and installed in /lib/firmware was: https://www.linuxtv.org/wiki/index.php/TechniSat_SkyStar_S2 following the link to open Elec: https://github.com/OpenELEC/dvb-firmware/blob/master/firmware/dvb-fe-cx24120-1.20.58.2.fw _ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://
Re: DVB-S PCI card regression on 4.19 / 4.20
Hi Stakarov, Em Fri, 23 Nov 2018 16:55:35 +0100 stakanov escreveu: > In data giovedì 22 novembre 2018 21:35:49 CET, Mauro Carvalho Chehab ha > scritto: > > Em Thu, 22 Nov 2018 21:19:49 +0100 > > > > stakanov escreveu: > > > Hello Mauro. > > > > > > Thank you so much, for this fast reply and especially for the detailed > > > indications. I expected to have a lack of knowledge. > > > > > > Well, I am replying to the question as of below: (for convenience I did > > > cut the before text, if you deem it useful for the list I can then > > > correct that in the next posts). > > > > > > In data giovedì 22 novembre 2018 21:06:11 CET, Mauro Carvalho Chehab ha > > > > > > scritto: > > > > Are you sure that the difference is just the Kernel version? Perhaps you > > > > also updated some other package. > > > > > > To be clear: I had the same system(!) with all three kernel 4.18.15-1, > > > 4.19.1 (when the problem did arise) and 4.20.2 rc3 from Takashi's repo) > > > installed. > > Ok, so rebooting to 4.18.15-1 solves the issue? > > > > Also, what GPU driver are you using? > > > > In any case, by using the old "Universal" LNBf, you're likely missing some > > transponders, and missing several channels. > > > > > In this very configuration: if one booted in 4.18 (that is in perfect > > > parity with all other packages) the card worked. 4.19.1 no. And the last > > > kernel the same. So whatever might be different, forcefully it has to be > > > in the kernel. (Which is not really a problem if I manage to make it > > > work, so settings will be known to others or, if not, we will find out > > > what is different, and all will be happy. As you see I am still > > > optimist). > > > > Well, we don't want regressions in Kernel. If there's an issue there, > > it should be fixed. However, I can't think on any other changes since > > 4.18 that would be causing troubles for b2c2 driver. > > > > See, the only change at the driver itself is just a simple API > > replacement that wouldn't cause this kind of problems: > > > > $ git log --oneline v4.18.. drivers/media/common/b2c2/ > > c0decac19da3 media: use strscpy() instead of strlcpy() > > > > There were a few changes at the DVB core: > > > > $ git log --no-merges --oneline v4.18.. drivers/media/dvb-core/ > > f3efe15a2f05 media: dvb: use signal types to discover pads > > b5d3206112dd media: dvb: dmxdev: move compat_ioctl handling to dmxdev.c > > cc1e6315e83d media: replace strcpy() by strscpy() > > c0decac19da3 media: use strscpy() instead of strlcpy() > > fd89e0bb6ebf media: videobuf2-core: integrate with media requests > > db6e8d57e2cd media: vb2: store userspace data in vb2_v4l2_buffer > > 6a2a1ca34ca6 media: dvb_frontend: ensure that the step is ok for both FE > > and tuner f1b1eabff0eb media: dvb: represent min/max/step/tolerance freqs > > in Hz a3f90c75b833 media: dvb: convert tuner_info frequencies to Hz > > 6706fe55af6f media: dvb_ca_en50221: off by one in > > dvb_ca_en50221_io_do_ioctl() 4d1e4545a659 media: mark entity-intf links as > > IMMUTABLE > > > > But, on a first glance, the only ones that has potential to cause issues > > were the ones addressed that the patch I wrote (merged by Takashi). > > > > If you're really receiving data from EPG (you may just have it > > cached), it means that the DVB driver is doing the right thing. > > > > Btw, to be sure that you're not just seeing the old EPG data, you > > should move or remove this file: > > > > ~/.local/share/kaffeine/epgdata.dvb > > > > Kaffeine will generate a new one again once it tunes into a TV channel. > > > > > I will proceed as indicated and report back here tomorrow. > > > > Ok. > > > > Thanks, > > Mauro > So, I confirm that: > a) 4.18.15-1 this card worked flawlessly. > b) above that, included the kernel with correction, it does not work any more. > c) downloading and copying the respective firmware from openelec does not > change, the card stays dead. > d) astra: no search of channels, search interrupted after seconds. > e) hotbird: search without finding any channel - only noise > f) lnbf setting was to "Astra E" as indicated. > g) after erasing the file in local/share it is clear that EPG data does NOT > work either. > When using the channels as they were recorded before, the signal strength is > 0 > but the fictional led is green (as if it would receive). > > > > No picture, no tone, no channel sync, no EPG. A brick. > So, with 4.18 that worked, only that now (due to an error I lost access to > the > 4.18.15-1 driver of TW, so if Takashi has a link, I can reinstall it and we > can check if, parity all packages this is still the case. I assure you that > it > was, but that would be a perfect proof. > Firmware downloaded and installed in /lib/firmware was: > https://www.linuxtv.org/wiki/index.php/TechniSat_SkyStar_S2 following the > link > to open Elec: > > https://github.com/OpenELEC/dvb-firmwar
Re: DVB-S PCI card regression on 4.19 / 4.20
On Fri, 23 Nov 2018 18:26:25 +0100, Mauro Carvalho Chehab wrote: > > Takashi, > > Could you please produce a Kernel for Stakanov to test > with the following patches: > > https://patchwork.linuxtv.org/patch/53044/ > https://patchwork.linuxtv.org/patch/53045/ > https://patchwork.linuxtv.org/patch/53046/ > https://patchwork.linuxtv.org/patch/53128/ Sorry for the late reaction. Now it's queued to OBS home:tiwai:bsc1116374-2 repo. It'll be ready in an hour or so. It's based on 4.20-rc4. Stakanov, please give it a try later. thanks, Takashi
Re: DVB-S PCI card regression on 4.19 / 4.20
Hi Stakanov, Em Tue, 27 Nov 2018 11:02:57 +0100 stakanov escreveu: > In data lunedì 26 novembre 2018 14:31:09 CET, Takashi Iwai ha scritto: > > On Fri, 23 Nov 2018 18:26:25 +0100, > > > > Mauro Carvalho Chehab wrote: > > > Takashi, > > > > > > Could you please produce a Kernel for Stakanov to test > > > with the following patches: > > > > > > https://patchwork.linuxtv.org/patch/53044/ > > > https://patchwork.linuxtv.org/patch/53045/ > > > https://patchwork.linuxtv.org/patch/53046/ > > > https://patchwork.linuxtv.org/patch/53128/ > > > > Sorry for the late reaction. Now it's queued to OBS > > home:tiwai:bsc1116374-2 repo. It'll be ready in an hour or so. > > It's based on 4.20-rc4. > > > > Stakanov, please give it a try later. > > > > > > thanks, > > > > Takashi > > O.K. this unbricks partially the card. From the logs, the Kernel is now working as expected. > Now hotbird does search and does sync > on all channels. Quality is very good. Astra still does interrupt the search > immediately and does not receive a thing. So it is a 50% brick still, but it > is a huge progress compared to before. As I said before, you need to tell Kaffeine what's the LNBf that you're using. The LNBf is a physical device[1] that it is installed on your satellite dish. There's no way to auto-detect the model you actually have, so you need to provide this information to the digital TV software you're using. [1] It looks like this: https://upload.wikimedia.org/wikipedia/commons/thumb/8/8c/Astra_lnb.jpg/240px-Astra_lnb.jpg The "Universal" one is for an old universal model sold in Europe about 15 years ago. It doesn't support all transponders found on an Astra satellite. For those, you need to use the LNBf that it is known as "Astra 1E"[2]. [2] The name is there just for historical reasons. The actual Astra 1E satellite was retired, but another satellite occupies the same orbital position (19.2°E), and they keep adding/retiring satellites there as needed (https://en.wikipedia.org/wiki/Astra_19.2%C2%B0E). As I pointed you on a past e-mail, when you set the DVB-S board on Kaffeine, you should have explicitly set it. If you start Kaffeine in English: $ LANG=C kaffeine You'll see it at the following menu: Television -> Configure Television -> Device 0 (assuming that your device is device 0) There, you need to tell that you'll be using a DiSEqC swith. It will then allow you to select up to 4 satellite sources. Once you set a source, it will allow you to edit the LNB Settings (where will be 1 to 4). Clicking there, it will present you a menu with all known LNBf models. Astra 1E is the third option[3]. [3] yeah, on a separate discussion, we should likely rename "Astra 1E" to just "Astra", and place it as the first option. I'll do such change, but it will be at v4l-utils package (libdvbv5) and it will probably take some time until distros start packaging the new version, even if we add it to the stable branch. > I paste the output of the directory below, unfortunately the opensuse paste > does not work currently so I try here, sorry if this is long. > > Content of the directory 99-media.conf created following the indications > (please bear in mind that I have also another card installed (Hauppauge 5525) > although it was not branched to the sat cable and i did change the settings > in > Kaffeine to use only the technisat. But my understanding is limited if this > may give "noise" in the output, so I thought to underline it, just FYI. > Output: Looks ok to me. > [ 649.009548] cx23885 :03:00.0: invalid short VPD tag 01 at offset 1 > [ 649.011439] r8169 :06:00.0: invalid short VPD tag 00 at offset 1 Those two above are weird... It seems to be related to some issue that the PCI core detected: drivers/pci/vpd.c: pci_warn(dev, "invalid %s VPD tag %02x at offset %zu", I've no idea what they mean, nor if you'll face any issues related to it. Thanks, Mauro
Re: DVB-S PCI card regression on 4.19 / 4.20
In data martedì 27 novembre 2018 13:49:46 CET, Mauro Carvalho Chehab ha scritto: > Hi Stakanov, > > Em Tue, 27 Nov 2018 11:02:57 +0100 > > stakanov escreveu: > > In data lunedì 26 novembre 2018 14:31:09 CET, Takashi Iwai ha scritto: > > > On Fri, 23 Nov 2018 18:26:25 +0100, > > > > > > Mauro Carvalho Chehab wrote: > > > > Takashi, > > > > > > > > Could you please produce a Kernel for Stakanov to test > > > > with the following patches: > > > > > > > > https://patchwork.linuxtv.org/patch/53044/ > > > > https://patchwork.linuxtv.org/patch/53045/ > > > > https://patchwork.linuxtv.org/patch/53046/ > > > > https://patchwork.linuxtv.org/patch/53128/ > > > > > > Sorry for the late reaction. Now it's queued to OBS > > > home:tiwai:bsc1116374-2 repo. It'll be ready in an hour or so. > > > It's based on 4.20-rc4. > > > > > > Stakanov, please give it a try later. > > > > > > > > > thanks, > > > > > > Takashi > > > > O.K. this unbricks partially the card. > > From the logs, the Kernel is now working as expected. > > > Now hotbird does search and does sync > > on all channels. Quality is very good. Astra still does interrupt the > > search immediately and does not receive a thing. So it is a 50% brick > > still, but it is a huge progress compared to before. > > As I said before, you need to tell Kaffeine what's the LNBf that you're > using. The LNBf is a physical device[1] that it is installed on your > satellite dish. There's no way to auto-detect the model you actually have, > so you need to provide this information to the digital TV software you're > using. > > [1] It looks like this: > https://upload.wikimedia.org/wikipedia/commons/thumb/8/8c/Astra_lnb.jpg/ 240 > px-Astra_lnb.jpg > > The "Universal" one is for an old universal model sold in Europe about > 15 years ago. It doesn't support all transponders found on an Astra > satellite. > > For those, you need to use the LNBf that it is known as "Astra 1E"[2]. > > [2] The name is there just for historical reasons. The actual Astra 1E > satellite was retired, but another satellite occupies the same orbital > position (19.2°E), and they keep adding/retiring satellites there as > needed (https://en.wikipedia.org/wiki/Astra_19.2%C2%B0E). > > As I pointed you on a past e-mail, when you set the DVB-S board on > Kaffeine, you should have explicitly set it. > > If you start Kaffeine in English: > > $ LANG=C kaffeine > > You'll see it at the following menu: > > Television -> Configure Television -> Device 0 > > (assuming that your device is device 0) > > There, you need to tell that you'll be using a DiSEqC swith. It > will then allow you to select up to 4 satellite sources. Once you > set a source, it will allow you to edit the LNB Settings > (where will be 1 to 4). Clicking there, it will present you > a menu with all known LNBf models. Astra 1E is the third option[3]. > > [3] yeah, on a separate discussion, we should likely rename "Astra 1E" > to just "Astra", and place it as the first option. I'll do such change, > but it will be at v4l-utils package (libdvbv5) and it will probably > take some time until distros start packaging the new version, even > if we add it to the stable branch. > > > I paste the output of the directory below, unfortunately the opensuse > > paste > > does not work currently so I try here, sorry if this is long. > > > > Content of the directory 99-media.conf created following the indications > > (please bear in mind that I have also another card installed (Hauppauge > > 5525) although it was not branched to the sat cable and i did change the > > settings in Kaffeine to use only the technisat. But my understanding is > > limited if this may give "noise" in the output, so I thought to underline > > it, just FYI. > > Output: > Looks ok to me. > > > [ 649.009548] cx23885 :03:00.0: invalid short VPD tag 01 at offset 1 > > [ 649.011439] r8169 :06:00.0: invalid short VPD tag 00 at offset 1 > > Those two above are weird... It seems to be related to some issue that > the PCI core detected: > > drivers/pci/vpd.c: pci_warn(dev, "invalid %s VPD tag > %02x at offset %zu", > > I've no idea what they mean, nor if you'll face any issues related to it. > > Thanks, > Mauro The two are known annoyances especially the cx23885 complaining in the logs about a "wrong revision". But as they AFAIK do not cause major issues or havoc, it is not a problem, at least for me. Now, the card suddenly works. The only thing you have to do (limited to this technisat PCI card, not applicable to the Hauppauge PCI-e mounted on the same machine) is to set the "square" to high voltage, limited for Astra. Hotbird scans better without this, with "no setting send" as I do for the Hauppauge as well. This must be something weird related to our sat dish. But the GOOD news is: yes now you made it! The card works. And yes, you should really rename ASTRA E setting. Maybe also be more clear or give some
Re: DVB-S PCI card regression on 4.19 / 4.20
On Tue, 27 Nov 2018 16:58:58 +0100, stakanov wrote: > > In data martedì 27 novembre 2018 13:49:46 CET, Mauro Carvalho Chehab ha > scritto: > > Hi Stakanov, > > > > Em Tue, 27 Nov 2018 11:02:57 +0100 > > > > stakanov escreveu: > > > In data lunedì 26 novembre 2018 14:31:09 CET, Takashi Iwai ha scritto: > > > > On Fri, 23 Nov 2018 18:26:25 +0100, > > > > > > > > Mauro Carvalho Chehab wrote: > > > > > Takashi, > > > > > > > > > > Could you please produce a Kernel for Stakanov to test > > > > > with the following patches: > > > > > > > > > > https://patchwork.linuxtv.org/patch/53044/ > > > > > https://patchwork.linuxtv.org/patch/53045/ > > > > > https://patchwork.linuxtv.org/patch/53046/ > > > > > https://patchwork.linuxtv.org/patch/53128/ > > > > > > > > Sorry for the late reaction. Now it's queued to OBS > > > > home:tiwai:bsc1116374-2 repo. It'll be ready in an hour or so. > > > > It's based on 4.20-rc4. > > > > > > > > Stakanov, please give it a try later. > > > > > > > > > > > > thanks, > > > > > > > > Takashi > > > > > > O.K. this unbricks partially the card. > > > > From the logs, the Kernel is now working as expected. > > > > > Now hotbird does search and does sync > > > on all channels. Quality is very good. Astra still does interrupt the > > > search immediately and does not receive a thing. So it is a 50% brick > > > still, but it is a huge progress compared to before. > > > > As I said before, you need to tell Kaffeine what's the LNBf that you're > > using. The LNBf is a physical device[1] that it is installed on your > > satellite dish. There's no way to auto-detect the model you actually have, > > so you need to provide this information to the digital TV software you're > > using. > > > > [1] It looks like this: > > https://upload.wikimedia.org/wikipedia/commons/thumb/8/8c/Astra_lnb.jpg/ > 240 > > px-Astra_lnb.jpg > > > > The "Universal" one is for an old universal model sold in Europe about > > 15 years ago. It doesn't support all transponders found on an Astra > > satellite. > > > > For those, you need to use the LNBf that it is known as "Astra 1E"[2]. > > > > [2] The name is there just for historical reasons. The actual Astra 1E > > satellite was retired, but another satellite occupies the same orbital > > position (19.2°E), and they keep adding/retiring satellites there as > > needed (https://en.wikipedia.org/wiki/Astra_19.2%C2%B0E). > > > > As I pointed you on a past e-mail, when you set the DVB-S board on > > Kaffeine, you should have explicitly set it. > > > > If you start Kaffeine in English: > > > > $ LANG=C kaffeine > > > > You'll see it at the following menu: > > > > Television -> Configure Television -> Device 0 > > > > (assuming that your device is device 0) > > > > There, you need to tell that you'll be using a DiSEqC swith. It > > will then allow you to select up to 4 satellite sources. Once you > > set a source, it will allow you to edit the LNB Settings > > (where will be 1 to 4). Clicking there, it will present you > > a menu with all known LNBf models. Astra 1E is the third option[3]. > > > > [3] yeah, on a separate discussion, we should likely rename "Astra 1E" > > to just "Astra", and place it as the first option. I'll do such change, > > but it will be at v4l-utils package (libdvbv5) and it will probably > > take some time until distros start packaging the new version, even > > if we add it to the stable branch. > > > > > I paste the output of the directory below, unfortunately the opensuse > > > paste > > > does not work currently so I try here, sorry if this is long. > > > > > > Content of the directory 99-media.conf created following the indications > > > (please bear in mind that I have also another card installed (Hauppauge > > > 5525) although it was not branched to the sat cable and i did change the > > > settings in Kaffeine to use only the technisat. But my understanding is > > > limited if this may give "noise" in the output, so I thought to underline > > > it, just FYI. > > > Output: > > Looks ok to me. > > > > > [ 649.009548] cx23885 :03:00.0: invalid short VPD tag 01 at offset 1 > > > [ 649.011439] r8169 :06:00.0: invalid short VPD tag 00 at offset 1 > > > > Those two above are weird... It seems to be related to some issue that > > the PCI core detected: > > > > drivers/pci/vpd.c: pci_warn(dev, "invalid %s VPD tag > > %02x at offset %zu", > > > > I've no idea what they mean, nor if you'll face any issues related to it. > > > > Thanks, > > Mauro > The two are known annoyances especially the cx23885 complaining in the logs > about a "wrong revision". But as they AFAIK do not cause major issues or > havoc, it is not a problem, at least for me. > Now, the card suddenly works. The only thing you have to do (limited to this > technisat PCI card, not applicable to the Hauppauge PCI-e mounted on the same > machine) is to set the "square" to high voltage, limited for Astra. Hotbird >
Re: DVB-S PCI card regression on 4.19 / 4.20
Em Tue, 27 Nov 2018 17:03:22 +0100 Takashi Iwai escreveu: > On Tue, 27 Nov 2018 16:58:58 +0100, > stakanov wrote: > > > > In data martedì 27 novembre 2018 13:49:46 CET, Mauro Carvalho Chehab ha > > scritto: > > > Hi Stakanov, > > > > > > Em Tue, 27 Nov 2018 11:02:57 +0100 > > > > > > stakanov escreveu: > > > > In data lunedì 26 novembre 2018 14:31:09 CET, Takashi Iwai ha scritto: > > > > > On Fri, 23 Nov 2018 18:26:25 +0100, > > > > > > > > > > Mauro Carvalho Chehab wrote: > > > > > > Takashi, > > > > > > > > > > > > Could you please produce a Kernel for Stakanov to test > > > > > > with the following patches: > > > > > > > > > > > > https://patchwork.linuxtv.org/patch/53044/ > > > > > > https://patchwork.linuxtv.org/patch/53045/ > > > > > > https://patchwork.linuxtv.org/patch/53046/ > > > > > > https://patchwork.linuxtv.org/patch/53128/ > > > > > > > > > > Sorry for the late reaction. Now it's queued to OBS > > > > > home:tiwai:bsc1116374-2 repo. It'll be ready in an hour or so. > > > > > It's based on 4.20-rc4. > > > > > > > > > > Stakanov, please give it a try later. > > > > > > > > > > > > > > > thanks, > > > > > > > > > > Takashi > > > > > > > > O.K. this unbricks partially the card. > > > > > > From the logs, the Kernel is now working as expected. > > > > > > > Now hotbird does search and does sync > > > > on all channels. Quality is very good. Astra still does interrupt the > > > > search immediately and does not receive a thing. So it is a 50% brick > > > > still, but it is a huge progress compared to before. > > > > > > As I said before, you need to tell Kaffeine what's the LNBf that you're > > > using. The LNBf is a physical device[1] that it is installed on your > > > satellite dish. There's no way to auto-detect the model you actually have, > > > so you need to provide this information to the digital TV software you're > > > using. > > > > > > [1] It looks like this: > > > > > > https://upload.wikimedia.org/wikipedia/commons/thumb/8/8c/Astra_lnb.jpg/ > > 240 > > > px-Astra_lnb.jpg > > > > > > The "Universal" one is for an old universal model sold in Europe about > > > 15 years ago. It doesn't support all transponders found on an Astra > > > satellite. > > > > > > For those, you need to use the LNBf that it is known as "Astra 1E"[2]. > > > > > > [2] The name is there just for historical reasons. The actual Astra 1E > > > satellite was retired, but another satellite occupies the same orbital > > > position (19.2°E), and they keep adding/retiring satellites there as > > > needed (https://en.wikipedia.org/wiki/Astra_19.2%C2%B0E). > > > > > > As I pointed you on a past e-mail, when you set the DVB-S board on > > > Kaffeine, you should have explicitly set it. > > > > > > If you start Kaffeine in English: > > > > > > $ LANG=C kaffeine > > > > > > You'll see it at the following menu: > > > > > > Television -> Configure Television -> Device 0 > > > > > > (assuming that your device is device 0) > > > > > > There, you need to tell that you'll be using a DiSEqC swith. It > > > will then allow you to select up to 4 satellite sources. Once you > > > set a source, it will allow you to edit the LNB Settings > > > (where will be 1 to 4). Clicking there, it will present you > > > a menu with all known LNBf models. Astra 1E is the third option[3]. > > > > > > [3] yeah, on a separate discussion, we should likely rename "Astra 1E" > > > to just "Astra", and place it as the first option. I'll do such change, > > > but it will be at v4l-utils package (libdvbv5) and it will probably > > > take some time until distros start packaging the new version, even > > > if we add it to the stable branch. > > > > > > > I paste the output of the directory below, unfortunately the opensuse > > > > paste > > > > does not work currently so I try here, sorry if this is long. > > > > > > > > Content of the directory 99-media.conf created following the indications > > > > (please bear in mind that I have also another card installed (Hauppauge > > > > 5525) although it was not branched to the sat cable and i did change the > > > > settings in Kaffeine to use only the technisat. But my understanding is > > > > limited if this may give "noise" in the output, so I thought to > > > > underline > > > > it, just FYI. > > > > Output: > > > Looks ok to me. > > > > > > > [ 649.009548] cx23885 :03:00.0: invalid short VPD tag 01 at offset > > > > 1 > > > > [ 649.011439] r8169 :06:00.0: invalid short VPD tag 00 at offset 1 > > > > > > > > > > Those two above are weird... It seems to be related to some issue that > > > the PCI core detected: > > > > > > drivers/pci/vpd.c: pci_warn(dev, "invalid %s VPD tag > > > %02x at offset %zu", > > > > > > I've no idea what they mean, nor if you'll face any issues related to it. > > > > > > Thanks, > > > Mauro > > The two are known annoyances especially the cx23885 complaining in the logs > > about
Re: DVB-S PCI card regression on 4.19 / 4.20
Em Tue, 27 Nov 2018 16:58:58 +0100 stakanov escreveu: > In data martedì 27 novembre 2018 13:49:46 CET, Mauro Carvalho Chehab ha > scritto: > > Hi Stakanov, > > > > Em Tue, 27 Nov 2018 11:02:57 +0100 > > > > stakanov escreveu: > > > In data lunedì 26 novembre 2018 14:31:09 CET, Takashi Iwai ha scritto: > > > > On Fri, 23 Nov 2018 18:26:25 +0100, > > > > > > > > Mauro Carvalho Chehab wrote: > > > > > Takashi, > > > > > > > > > > Could you please produce a Kernel for Stakanov to test > > > > > with the following patches: > > > > > > > > > > https://patchwork.linuxtv.org/patch/53044/ > > > > > https://patchwork.linuxtv.org/patch/53045/ > > > > > https://patchwork.linuxtv.org/patch/53046/ > > > > > https://patchwork.linuxtv.org/patch/53128/ > > > > > > > > Sorry for the late reaction. Now it's queued to OBS > > > > home:tiwai:bsc1116374-2 repo. It'll be ready in an hour or so. > > > > It's based on 4.20-rc4. > > > > > > > > Stakanov, please give it a try later. > > > > > > > > > > > > thanks, > > > > > > > > Takashi > > > > > > O.K. this unbricks partially the card. > > > > From the logs, the Kernel is now working as expected. > > > > > Now hotbird does search and does sync > > > on all channels. Quality is very good. Astra still does interrupt the > > > search immediately and does not receive a thing. So it is a 50% brick > > > still, but it is a huge progress compared to before. > > > > As I said before, you need to tell Kaffeine what's the LNBf that you're > > using. The LNBf is a physical device[1] that it is installed on your > > satellite dish. There's no way to auto-detect the model you actually have, > > so you need to provide this information to the digital TV software you're > > using. > > > > [1] It looks like this: > > https://upload.wikimedia.org/wikipedia/commons/thumb/8/8c/Astra_lnb.jpg/ > 240 > > px-Astra_lnb.jpg > > > > The "Universal" one is for an old universal model sold in Europe about > > 15 years ago. It doesn't support all transponders found on an Astra > > satellite. > > > > For those, you need to use the LNBf that it is known as "Astra 1E"[2]. > > > > [2] The name is there just for historical reasons. The actual Astra 1E > > satellite was retired, but another satellite occupies the same orbital > > position (19.2°E), and they keep adding/retiring satellites there as > > needed (https://en.wikipedia.org/wiki/Astra_19.2%C2%B0E). > > > > As I pointed you on a past e-mail, when you set the DVB-S board on > > Kaffeine, you should have explicitly set it. > > > > If you start Kaffeine in English: > > > > $ LANG=C kaffeine > > > > You'll see it at the following menu: > > > > Television -> Configure Television -> Device 0 > > > > (assuming that your device is device 0) > > > > There, you need to tell that you'll be using a DiSEqC swith. It > > will then allow you to select up to 4 satellite sources. Once you > > set a source, it will allow you to edit the LNB Settings > > (where will be 1 to 4). Clicking there, it will present you > > a menu with all known LNBf models. Astra 1E is the third option[3]. > > > > [3] yeah, on a separate discussion, we should likely rename "Astra 1E" > > to just "Astra", and place it as the first option. I'll do such change, > > but it will be at v4l-utils package (libdvbv5) and it will probably > > take some time until distros start packaging the new version, even > > if we add it to the stable branch. > > > > > I paste the output of the directory below, unfortunately the opensuse > > > paste > > > does not work currently so I try here, sorry if this is long. > > > > > > Content of the directory 99-media.conf created following the indications > > > (please bear in mind that I have also another card installed (Hauppauge > > > 5525) although it was not branched to the sat cable and i did change the > > > settings in Kaffeine to use only the technisat. But my understanding is > > > limited if this may give "noise" in the output, so I thought to underline > > > it, just FYI. > > > Output: > > Looks ok to me. > > > > > [ 649.009548] cx23885 :03:00.0: invalid short VPD tag 01 at offset 1 > > > [ 649.011439] r8169 :06:00.0: invalid short VPD tag 00 at offset 1 > > > > Those two above are weird... It seems to be related to some issue that > > the PCI core detected: > > > > drivers/pci/vpd.c: pci_warn(dev, "invalid %s VPD tag > > %02x at offset %zu", > > > > I've no idea what they mean, nor if you'll face any issues related to it. > > > > Thanks, > > Mauro > The two are known annoyances especially the cx23885 complaining in the logs > about a "wrong revision". But as they AFAIK do not cause major issues or > havoc, it is not a problem, at least for me. Ok, good! > Now, the card suddenly works. The only thing you have to do (limited to this > technisat PCI card, not applicable to the Hauppauge PCI-e mounted on the same > machine) is to set the "square" to high voltage, limited for Astr
