Re: New Terratec Cinergy S2 Box usb-id
On 08/31/2015 01:19 PM, Maximilian Imgrund wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Dear all,
>
> I am currently figuring out how to get the Terratec Cinergy S2 USB Box
> up and running. I already modified a patch to previous version (see
> attachment) to include the new ID in the device driver, module is also
> loading with the ds3000 firmware. However, when using w_scan, the
> reported frequency range is .95GHz ... 2.15Ghz which is roughly a
> factor of 10 lower than I expected (Astra is 12.515Ghz e.g.). Since
> the tuner seems to tune in correctly but in the wrong frequency range,
> I feel that is the reason for me not getting in any channels.
>
> Can you help me with what to change in the driver to get this working
> ? I feel like an additional .frequency_div should do the job, however
> I am unable to find further informaion on that...
>
> Best
> Maximilian Imgrund
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2
>
> iF4EAREIAAYFAlXkOFIACgkQR/X5cR0fI/6sfAD+OVauTyLw0oWSMr8ONzmrguF+
> Ci/vg4uO9mxZwzjgGXkA/ipgQ/IuX+8n2CSScHg6CFjt9tIBbFOAVzStuUrOpwx2
> =AAXS
> -END PGP SIGNATURE-
>
The driver has to tune to the intermediate frequency
that's output by the LNB. (There is a local oscillator+downmixer in there...)
This is what the one here has
info = {
name = "ST STV0299 DVB-S", '\000' , type = FE_QPSK,
frequency_min = 95, frequency_max = 215,
frequency_stepsize = 125, frequency_tolerance = 0,
symbol_rate_min = 100, symbol_rate_max = 4500,
symbol_rate_tolerance = 500, notifier_delay = 0,
caps = (FE_CAN_INVERSION_AUTO | 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_FEC_AUTO |
FE_CAN_QPSK)},
Frequency_min and max match yours.
Try a different scan tool, and make sure you get a signal out of your LNB.
Proper DISH ALIGNMENT is important,
and don't forget a grounding bloc.
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] media: dvb-core: Don't force CAN_INVERSION_AUTO in oneshot mode.
Why not just remove the line? info->caps |= FE_CAN_INVERSION_AUTO; The capabilities call interacting with the oneshot setting is rather weird and maybe unexpected. -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [BUG] STV0299 has bogus CAN_INVERSION_AUTO flag
On 08/30/2015 11:53 AM, Malcolm Priestley wrote:
On 24/08/15 16:19, Johann Klammer wrote:
from gdb dump:
[...]
info = {
name = ST STV0299 DVB-S, '\000' repeats 111 times, type = FE_QPSK,
frequency_min = 95, frequency_max = 215,
frequency_stepsize = 125, frequency_tolerance = 0,
symbol_rate_min = 100, symbol_rate_max = 4500,
symbol_rate_tolerance = 500, notifier_delay = 0,
caps = (FE_CAN_INVERSION_AUTO | 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_FEC_AUTO |
FE_CAN_QPSK)},
[...]
when tuning:
[...]
Hi
..
[331020.207352] stv0299 does not support auto-inversion
[331020.507480] stv0299 does not support auto-inversion
[331020.807610] stv0299 does not support auto-inversion
[331021.107747] stv0299 does not support auto-inversion
[...]
(but how the heck should I know?)
I am using the stv0299 with no problems at all, the code hasn't changed much
in years. I am using linux 4.2-rc6
boot/vmlinuz-4.1.0-1-586
Something must have changed. I updated kernel and got those messages.
I did not get then before. The vmlinuz.old
points to: boot/vmlinuz-3.14.15
vmlinuz points to: boot/vmlinuz-4.1.0-1-586
(debian testing binary .deb)
You shouldn't be getting that message as dvb core does the auto inversion for
the driver.
It may have been exposed by trying oneshot tuning mode... not sure...
I had to try that 'coz I only got about 50% success on any tuning attempt on
this card
(has always been like that).
got rid of that, it tunes reliably now if I set INVERSION to 0.
and retry a few times instead of uning once, then polling for LOCK
(which often won't happen).
It's entirely possible the bug was in there for a while.
I looked through the code and can't find any fault.
They explicitly set the CAN_INVERSION_AUTO flag in the FE_GET_INFO ioctl,
then fail -EINVAL when you try to tune with INVERSION_AUTO.
At least that's where the error message comes from.
Regards
Malcolm
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [BUG] STV0299 has bogus CAN_INVERSION_AUTO flag
It breaks tuning, you know. IT BREAKS TUNING. -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [BUG] STV0299 has bogus CAN_INVERSION_AUTO flag
Pls fix this!!! Either by fixing. https://github.com/torvalds/linux/blob/master/drivers/media/dvb-frontends/stv0299.c around line 583. or https://github.com/torvalds/linux/blob/master/drivers/media/dvb-core/dvb_frontend.c line 2319 but there it's problematic coz they tried to be `smart' with this in the tuning functions... And don't start nagging around that I'm supposed to use the `unlimited' capabilities API, coz IT IS NOT IMPLEMENTED AND I AM NOT GONNA WRITE IT. https://github.com/torvalds/linux/search?utf8=%E2%9C%93q=DTV_FE_CAPABILITY peace -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[BUG] STV0299 has bogus CAN_INVERSION_AUTO flag
from gdb dump:
[...]
info = {
name = ST STV0299 DVB-S, '\000' repeats 111 times, type = FE_QPSK,
frequency_min = 95, frequency_max = 215,
frequency_stepsize = 125, frequency_tolerance = 0,
symbol_rate_min = 100, symbol_rate_max = 4500,
symbol_rate_tolerance = 500, notifier_delay = 0,
caps = (FE_CAN_INVERSION_AUTO | 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_FEC_AUTO |
FE_CAN_QPSK)},
[...]
when tuning:
[...]
[331012.238617] stv0299 does not support auto-inversion
[331012.538760] stv0299 does not support auto-inversion
[331012.838898] stv0299 does not support auto-inversion
[331014.192121] stv0299 does not support auto-inversion
[331014.492257] stv0299 does not support auto-inversion
[331014.792391] stv0299 does not support auto-inversion
[331015.092571] stv0299 does not support auto-inversion
[331015.392692] stv0299 does not support auto-inversion
[331015.692825] stv0299 does not support auto-inversion
[331015.992964] stv0299 does not support auto-inversion
[331016.293106] stv0299 does not support auto-inversion
[331019.306883] stv0299 does not support auto-inversion
[331019.607024] stv0299 does not support auto-inversion
[331019.907166] stv0299 does not support auto-inversion
[331020.207352] stv0299 does not support auto-inversion
[331020.507480] stv0299 does not support auto-inversion
[331020.807610] stv0299 does not support auto-inversion
[331021.107747] stv0299 does not support auto-inversion
[...]
(but how the heck should I know?)
kernel:
[...]
uname -a
Linux tivi 4.1.0-1-586 #1 Debian 4.1.3-1 (2015-08-03) i686 GNU/Linux
[...]
hardware[boot msg]:
[...]
[ 12.785499] saa7146: register extension 'budget_av'
[ 12.786359] saa7146: found saa7146 @ mem cf83e000 (revision 1, irq 10)
(0x153b,0x1154)
[ 12.786472] saa7146 (0): dma buffer size 192512
[ 12.786533] DVB: registering new adapter (TerraTec Cinergy 1200 DVB-S)
[ 12.828641] adapter failed MAC signature check
[ 12.828721] encoded MAC from EEPROM was
ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff
[ 13.096516] budget_av: KNC1-0: MAC addr = 00:0a:ac:01:8d:a1
[ 13.604381] budget_av :00:14.0: DVB: registering adapter 0 frontend 0
(ST STV0299 DVB-S)...
[ 13.621283] budget_av: ci interface initialised
[...]
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
[PATCH] Turn bothersome error into a debug message
Once again...
On 09/30/2014 07:21 PM, Johann Klammer wrote:
Hello,
After updating the kernel to 3.14.15 I am seeing these messages:
[273684.964081] saa7146: saa7146 (0): saa7146_wait_for_debi_done_sleep
timed out while waiting for registers getting programmed
[273690.020061] saa7146: saa7146 (0): saa7146_wait_for_debi_done_sleep
timed out while waiting for registers getting programmed
[273695.076082] saa7146: saa7146 (0): saa7146_wait_for_debi_done_sleep
timed out while waiting for registers getting programmed
[273700.132077] saa7146: saa7146 (0): saa7146_wait_for_debi_done_sleep
timed out while waiting for registers getting programmed
[273705.188070] saa7146: saa7146 (0): saa7146_wait_for_debi_done_sleep
timed out while waiting for registers getting programmed
[273710.244066] saa7146: saa7146 (0): saa7146_wait_for_debi_done_sleep
timed out while waiting for registers getting programmed
[273715.300187] saa7146: saa7146 (0): saa7146_wait_for_debi_done_sleep
timed out while waiting for registers getting programmed
[273720.356068] saa7146: saa7146 (0): saa7146_wait_for_debi_done_sleep
timed out while waiting for registers getting programmed
[273725.412188] saa7146: saa7146 (0): saa7146_wait_for_debi_done_sleep
timed out while waiting for registers getting programmed
[273730.468094] saa7146: saa7146 (0): saa7146_wait_for_debi_done_sleep
timed out while waiting for registers getting programmed
[273735.524070] saa7146: saa7146 (0): saa7146_wait_for_debi_done_sleep
timed out while waiting for registers getting programmed
[273740.580176] saa7146: saa7146 (0): saa7146_wait_for_debi_done_sleep
timed out while waiting for registers getting programmed
filling up the logs(one about every 5 seconds).
The TV card is a Terratec Cinergy 1200 DVBS (I believe.. it's rather old).
I can not observe any erratic behavior, just those pesky messages...
I see there was an earlier post here in 2008 about a similar
problem...(Cinergy 1200 DVB-C... a coincidence?)
What does it mean?
Do I need to be worried?
I am using a debian testing on a 32 bit box.
The previous kernel was linux-image-3.12-1-486.
It did not show those messages, but maybe due to some configure
options... I built this one from linux-source-3.14...
Answering my own question:
Other posts suggests that it is not actually an error on cards without a
CI interface. Here's a patch that turns it into a debug message, so it
does not clobber the logs.
--- linux-source-3.14/drivers/media/common/saa7146/saa7146_core.c.orig
2014-07-31 23:51:43.0 +0200
+++ linux-source-3.14/drivers/media/common/saa7146/saa7146_core.c
2014-10-06 18:57:54.0 +0200
@@ -71,7 +71,7 @@ static inline int saa7146_wait_for_debi_
if (saa7146_read(dev, MC2) 2)
break;
if (err) {
- pr_err(%s: %s timed out while waiting for registers getting
programmed\n,
+ pr_debug(%s: %s timed out while waiting for registers getting
programmed\n,
dev-name, __func__);
return -ETIMEDOUT;
}
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
saa7146_wait_for_debi_done_sleep timed out
Hello, After updating the kernel to 3.14.15 I am seeing these messages: [273684.964081] saa7146: saa7146 (0): saa7146_wait_for_debi_done_sleep timed out while waiting for registers getting programmed [273690.020061] saa7146: saa7146 (0): saa7146_wait_for_debi_done_sleep timed out while waiting for registers getting programmed [273695.076082] saa7146: saa7146 (0): saa7146_wait_for_debi_done_sleep timed out while waiting for registers getting programmed [273700.132077] saa7146: saa7146 (0): saa7146_wait_for_debi_done_sleep timed out while waiting for registers getting programmed [273705.188070] saa7146: saa7146 (0): saa7146_wait_for_debi_done_sleep timed out while waiting for registers getting programmed [273710.244066] saa7146: saa7146 (0): saa7146_wait_for_debi_done_sleep timed out while waiting for registers getting programmed [273715.300187] saa7146: saa7146 (0): saa7146_wait_for_debi_done_sleep timed out while waiting for registers getting programmed [273720.356068] saa7146: saa7146 (0): saa7146_wait_for_debi_done_sleep timed out while waiting for registers getting programmed [273725.412188] saa7146: saa7146 (0): saa7146_wait_for_debi_done_sleep timed out while waiting for registers getting programmed [273730.468094] saa7146: saa7146 (0): saa7146_wait_for_debi_done_sleep timed out while waiting for registers getting programmed [273735.524070] saa7146: saa7146 (0): saa7146_wait_for_debi_done_sleep timed out while waiting for registers getting programmed [273740.580176] saa7146: saa7146 (0): saa7146_wait_for_debi_done_sleep timed out while waiting for registers getting programmed filling up the logs(one about every 5 seconds). The TV card is a Terratec Cinergy 1200 DVBS (I believe.. it's rather old). I can not observe any erratic behavior, just those pesky messages... I see there was an earlier post here in 2008 about a similar problem...(Cinergy 1200 DVB-C... a coincidence?) What does it mean? Do I need to be worried? I am using a debian testing on a 32 bit box. The previous kernel was linux-image-3.12-1-486. It did not show those messages, but maybe due to some configure options... I built this one from linux-source-3.14... -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: PROBLEM: EHCI disconnects DVB HDD
Alan Stern wrote: Can you put the usbmon trace on a web server like pastebin.com? Pastebin chickens out with: `413 Request Entity Too Large` The dump is around 2.5 Mib. Most of it probably the dvb stream. Have now recompiled the kernel with more debug output and will try to reproduce the problem. From what I see by now, the HDD behaves flaky too. -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: PROBLEM: EHCI disconnects DVB HDD
Alan Stern wrote: This is probably a low-level hardware error. Interference between the two ports of some kind. This is quite possible. Have been able to produce a more verbose logfile snippet. [25045.734288] af9013_update_ber_unc: err bits:1286 total bits:1632 abort count:0 [25045.734355] 21 65 38 d3 85 03 03 01 10 [25045.750125] 65 00 [25045.750197] 21 66 38 d3 86 03 03 01 27 [25045.766121] 66 00 [25045.766195] 20 67 38 d3 91 00 03 01 [25045.782147] 67 00 11 [25045.782218] 21 68 38 d3 91 03 03 01 11 [25045.798202] 68 00 [25047.489434] 20 69 38 d5 07 00 03 01 [25047.502162] 69 00 72 [25047.502235] af9013_update_signal_strength [25047.502271] 20 6a 38 d0 7c 00 03 01 [25047.518083] 6a 00 a8 [25047.518154] 20 6b 38 d0 7d 00 03 01 [25047.534080] 6b 00 47 [25047.534151] 20 6c 38 d2 e1 00 03 01 [25047.550076] 6c 00 08 [25047.550146] 20 6d 38 d2 e3 00 03 01 [25047.566079] 6d 00 0e [25047.566146] 20 6e 38 d2 e4 00 03 01 [25047.582140] 6e 00 93 [25047.582207] 20 6f 38 d2 e5 00 03 01 [25047.598075] 6f 00 0b [25047.598146] 20 70 38 d3 c1 00 03 01 [25047.614080] 70 00 58 [25047.614153] 21 71 38 d2 e2 03 03 01 01 [25047.630138] 71 00 [25047.645438] 20 72 38 d2 e6 00 03 01 [25047.654097] 72 00 f0 [25047.654169] 20 73 38 d2 e1 00 03 01 [25047.670158] 73 00 08 [25047.670230] 21 74 38 d2 e1 03 03 01 08 [25047.686083] 74 00 [25047.686153] 20 75 38 d3 91 00 03 01 [25047.702087] 75 00 11 [25047.702163] 20 76 38 d3 8a 00 03 01 [25047.718158] 76 00 00 [25047.718232] 20 77 38 d3 8b 00 03 01 [25047.734083] 77 00 00 [25047.734162] 20 78 38 d3 87 00 03 01 [25047.750080] 78 00 53 [25047.750150] 20 79 38 d3 88 00 03 01 [25047.766142] 79 00 03 [25047.766214] 20 7a 38 d3 89 00 03 01 [25047.782061] 7a 00 00 [25047.782148] 20 7b 38 d3 85 00 03 01 [25047.798063] 7b 00 10 [25047.798143] 20 7c 38 d3 86 00 03 01 [25047.814130] 7c 00 27 [25047.814216] af9013_update_ber_unc: err bits:851 total bits:1632 abort count:0 [25047.814279] 21 7d 38 d3 85 03 03 01 10 [25047.830052] 7d 00 [25047.830125] 21 7e 38 d3 86 03 03 01 27 [25047.846069] 7e 00 [25047.846130] 20 7f 38 d3 91 00 03 01 [25047.862066] 7f 00 11 [25047.862136] 21 80 38 d3 91 03 03 01 11 [25047.878084] 80 00 [25049.527925] hub 1-0:1.0: state 7 ports 6 chg evt 000a [25049.527990] ehci_hcd :00:10.3: GetStatus port:1 status 00100a 0 ACK POWER sig=se0 PEC CSC [25049.528039] hub 1-0:1.0: port 1, status 0100, change 0003, 12 Mb/s [25049.528062] usb 1-1: USB disconnect, device number 2 [25049.528111] usb 1-1: unregistering device [25049.528130] usb 1-1: unregistering interface 1-1:1.0 [25049.528374] usb-storage: storage_disconnect() called [25049.541186] usb-storage: -- usb_stor_release_resources [25049.541204] usb-storage: -- sending exit command to thread [25049.541232] usb-storage: *** thread awakened. [25049.541246] usb-storage: -- exiting [25049.541299] usb-storage: -- dissociate_dev [25049.541424] usb 1-1: usb_disable_device nuking all URBs [25049.543935] ehci_hcd :00:10.3: GetStatus port:1 status 001803 0 ACK POWER sig=j CSC CONNECT [25049.569580] 20 81 38 d5 07 00 03 01 [25049.669642] hub 1-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x501 [25049.725674] ehci_hcd :00:10.3: port 1 high speed [25049.725718] ehci_hcd :00:10.3: GetStatus port:1 status 001005 0 ACK POWER sig=se0 PE CONNECT [25049.781694] usb 1-1: new high speed USB device number 4 using ehci_hcd [25051.581718] usb 1-3: kdvb-ad-1-fe-0 timed out on ep2out len=0/8 [25051.581748] af9015: bulk message failed:-110 (8/0) [25051.581802] af9013: I2C read failed reg:d507 [25052.565761] 20 82 38 d5 07 00 03 01 [25054.577928] usb 1-3: kdvb-ad-1-fe-0 timed out on ep2out len=0/8 [25054.577956] af9015: bulk message failed:-110 (8/0) [25054.578012] af9013: I2C read failed reg:d507 [25054.794039] usb 1-1: khubd timed out on ep0in len=0/64 [25055.425927] 20 83 38 d5 07 00 03 01 [25057.438083] usb 1-3: kdvb-ad-1-fe-0 timed out on ep2out len=0/8 [25057.438110] af9015: bulk message failed:-110 (8/0) [25057.438163] af9013: I2C read failed reg:d507 [25058.238115] 20 84 38 d5 07 00 03 01 [25059.806230] usb 1-1: khubd timed out on ep0in len=0/64 [25060.250263] usb 1-3: kdvb-ad-1-fe-0 timed out on ep2out len=0/8 [25060.250289] af9015: bulk message failed:-110 (8/0) [25060.250342] af9013: I2C read failed reg:d507 [25061.058269] 20 85 38 d5 07 00 03 01 [25063.070487] usb 1-3: kdvb-ad-1-fe-0 timed out on ep2out len=0/8 [25063.070512] af9015: bulk message failed:-110 (8/0) [25063.070565] af9013: I2C read failed reg:d507 [25063.922457] 20 86 38 d5 07 00 03 01 [25064.818955] usb 1-1: khubd timed out on ep0in len=0/64 [25064.874603] ehci_hcd :00:10.3: port 1 high speed [25064.874648] ehci_hcd :00:10.3: GetStatus port:1 status 00100f 0 ACK POWER sig=se0 PEC PE CSC CONNECT [25064.874761] hub 1-0:1.0: unable to enumerate USB device on port 1 [25064.874849] ehci_hcd
Re: PROBLEM: EHCI disconnects DVB HDD
Alan Stern wrote: This could be the result of an electrical glitch or power fluctuation. Are these devices bus-powered? The DVB Stick is. The HDD is not. Or it could simply be something wrong with your EHCI controller. Possible. The power supply is old, too and there's a telephone in the same room. -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
