Hi,
I was getting VDSB errors on my 2 VDRs (1.3.15, one on SUSE 9.0, the other on 9.2) when recording (only). I followed the hint in http://www.vdr-portal.de/board/thread.php?threadid=25233&sid= by adding the "-5" in remux.c. Now I am getting lots of buffer overrun errors on the slow machine (VIA C3 533), resulting in broken MPEG streams. The recordings are not very usable afterwards.
What I can do?
Harald Milz wrote:
Hi,
I was getting VDSB errors on my 2 VDRs (1.3.15, one on SUSE 9.0, the other on 9.2) when recording (only). I followed the hint in http://www.vdr-portal.de/board/thread.php?threadid=25233&sid= by adding the "-5" in remux.c. Now I am getting lots of buffer overrun errors on the slow machine (VIA C3 533), resulting in broken MPEG streams. The recordings are not very usable afterwards.
What I can do?
Install kernel 2.6.11.
Carsten.
Carsten Koch Carsten.Koch@icem.com wrote:
Harald Milz wrote:
the "-5" in remux.c. Now I am getting lots of buffer overrun errors on the slow machine (VIA C3 533), resulting in broken MPEG streams. The recordings are not very usable afterwards.
Install kernel 2.6.11.
A stock kernel isn't really an option for a SUSE system (unfortunately). Methinks the 9.3 kernel would work, right?
Just "install kernel 2.6.11" sounds like a piece of advice for a newbie - what exactly would this kernel's added value be?
Harald Milz hm@seneca.muc.de wrote:
Carsten Koch Carsten.Koch@icem.com wrote:
Install kernel 2.6.11.
A stock kernel isn't really an option for a SUSE system (unfortunately). Methinks the 9.3 kernel would work, right?
Just "install kernel 2.6.11" sounds like a piece of advice for a newbie - what exactly would this kernel's added value be?
Carsten?
Harald Milz wrote:
Carsten Koch Carsten.Koch@icem.com wrote:
Harald Milz wrote:
the "-5" in remux.c. Now I am getting lots of buffer overrun errors on the slow machine (VIA C3 533), resulting in broken MPEG streams. The recordings are not very usable afterwards.
Install kernel 2.6.11.
A stock kernel isn't really an option for a SUSE system (unfortunately). Methinks the 9.3 kernel would work, right?
Just "install kernel 2.6.11" sounds like a piece of advice for a newbie - what exactly would this kernel's added value be?
It may be related to your problem or not, but here is my experience with the SuSE 9.2 and SuSE 9.3 kernels on my vdr system:
The kernel level used in SuSE 9.2 still contained a problem in the DVB drivers which caused VDSB errors if you have a FF card and a budget card. Not SuSE-related, just "DVB drivers in kernel < 2.6.11"-related. I believe it was Oliver who has has found and fixed the problem, so you can either install newer DVB drivers or kernel 2.6.11, which contains the fixed drivers. Search the mailing list archives for VDSB or "video data stream broken" for details.
The SuSE 9.3 kernel contains a bug that SuSE built in, which is not in the DVB drivers nor in the standard 2.6.11 kernel. At least on my VDR system (1 FF card, 2 budget cards), it caused "irq 7: nobody cared!" kernel errors, which were gone the moment I installed the standard 2.6.11.7 from kernel.org on my SuSE 9.3 system.
So, in summary:
Install kernel 2.6.11. :-)
Carsten.
P.S.: I agree that it is not as easy as it should be to install a standard kernel under SuSE 9.3. On my vdr system I also had to download and install the lirc drivers and I had do insert a modprobe command into /etc/init.d/network to make the system boot properly with networking. People using subfs might have to install that, too. Especially the networking thing I found annoying and unnecessary.
Carsten Koch Carsten.Koch@icem.com wrote:
The kernel level used in SuSE 9.2 still contained a problem in the DVB drivers which caused VDSB errors if you have a FF card and a budget card.
Hmmm - my SUSE 9.0 VDR has only the FF card while the 9.2 system has 2 budget cards (FSC Activy and a Skystar2). On the 9.0 system I use the linuxtv-1.1.1 DVB drivers. Since I could not get these to compile on the 9.2 system I'm using the DVB drivers that come with the SUSE 9.2 kernel (latest YOU one).
so you can either install newer DVB drivers or kernel 2.6.11, which contains the fixed drivers.
I suppose the 1.1.1 drivers are at least as recent as the ones in the 2.6.11 kernel?
Search the mailing list archives for VDSB or "video data stream broken" for details.
Which I did, and found very little except the "-5" trick in remux.c. BTW I am _still_ getting VSDBs now.
Shame. I wanted to record Episode II tonight, and I'm still getting the VDSBs. :-( Good news is it is repeated tomorrow afternoon.
Hi Harald,
On Sun, 24 Apr 2005, Harald Milz wrote:
so you can either install newer DVB drivers or kernel 2.6.11, which contains the fixed drivers.
I suppose the 1.1.1 drivers are at least as recent as the ones in the 2.6.11 kernel?
No. 1.1.1 are for 2.6.4 (or 3) and won't work with higher kernels, you have to use dvb-kernel from CVS for >= 2.6.9 .
Shame. I wanted to record Episode II tonight, and I'm still getting the VDSBs. :-( Good news is it is repeated tomorrow afternoon.
Sorry if I ask something already answered, but it was not obvious for me.
Do the VSDB errors happen with the skystar2 card? If so, it's is a known problem, but unfortunately not entirely solved yet.
The problem is, that suddenly no interrupts are created anymore. The only solution (but a very rude one) is to reset the flexcop-chip by reloading the drivers.
If the skystar is the problematic card, I suggest you to use dvb-kernel CVS. There is a new driver for the Technisat/B2C2 cards (b2c2-flexcop-pci). The VSDB-error still happens with that driver in some cases though, but maybe it helps in your case.
best regards Patrick.
-- Mail: patrick.boettcher@desy.de WWW: http://www.wi-bw.tfh-wildau.de/~pboettch/
Patrick Boettcher wrote:
Do the VSDB errors happen with the skystar2 card? If so, it's is a known problem, but unfortunately not entirely solved yet.
The problem is, that suddenly no interrupts are created anymore. The only solution (but a very rude one) is to reset the flexcop-chip by reloading the drivers.
When does this problem happen? I'm asking because I have a skystar 2 and a pretty old driver (checked out about a year ago) and only have this problem after heavy (or not so heavy) zapping, and it's cured by reloading the driver. I never experienced this problem if staying on the same channel, even for many hours.
Bye
On Sun, 24 Apr 2005, Luca Olivetti wrote:
Patrick Boettcher wrote:
Do the VSDB errors happen with the skystar2 card? If so, it's is a known problem, but unfortunately not entirely solved yet.
The problem is, that suddenly no interrupts are created anymore. The only solution (but a very rude one) is to reset the flexcop-chip by reloading the drivers.
When does this problem happen? I'm asking because I have a skystar 2 and a pretty old driver (checked out about a year ago) and only have this problem after heavy (or not so heavy) zapping, and it's cured by reloading the driver. I never experienced this problem if staying on the same channel, even for many hours.
In both cases the problem happens: One user reports no irqs occure during a recording. I saw it dying during vdr's pidscan in the background.
Problem is, not all systems are affected: It's not limited to - a specific revision of the card - a specific version of the flexcop (II and IIb) - if IRQ is shared with another device or not - mainboard chipset in use
Just for testing, please try a recent dvb-kernel. Maybe your problem have nothing to do with this problem. (TM) :)
regards Patrick.
-- Mail: patrick.boettcher@desy.de WWW: http://www.wi-bw.tfh-wildau.de/~pboettch/
-
Carsten Koch -
Harald Milz -
Luca Olivetti -
Patrick Boettcher