Mailing List archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[vdr] Re: vdr[3330]: ERROR: can't record MPEG1! - possible cause
werner@suse.de(Dr. Werner Fink) 24.09.01 12:02
Once upon a time Dr. Werner Fink shaped the electrons to say...
>On Sat, Sep 22, 2001 at 08:59:00PM +0200, Rainer Zocholl wrote:
>>
>>>which kernel version?
>>
>> Linux version 2.4.9 (root@msi) (gcc version 2.95.2 20000220 (Debian
>> 2.2)
>>
>> (kernel from kernel.org)
>IMHO plain 2.4.9 isn't very stable.
Because 2.4.10 was released yesterday i tried:
It is much better :-)
Not Oops (in the last 3 minutes :-))
"MPEG1" only occurs when i record on both card
simultanious, but only one per (some) minute(s).
But there are still "glitches" in audio,
the image contains sometimes artefacts
Video and audio runs/are outof sync (i assume
because frames are dropped/broken.)
A/V resync can't be forced with "pause", "rewind" is required.
kernel 2.4.10
dvb-20000923
vdr-0.96
lirc-0.6.4pre3
i2c-2.6.1
libc-2.1.3
gcc 2.95.2
(with kernel 2.4.9 simultanious recordings leads to
Kernel panic oops 002 , but not all ways)
recording with the primary card alone always works very
artefact free
recording with kernel 2.4.9 on a PIII 1000MHz 133FSB
fails on the second card (broken frames, half frames)
recording with a 700MHz 66MHz FSB works relatively good,
but artefacts are there too.
So:
There is still something wrong.
Maybe with faster CPUs
maybe with Intel CPUs
maybe with the i815 Chipset
maybe with the MSI MS-6351 MoBo?
Of cause i could place the 700 celeron into the MoBo, but...
i am sure that there still will be artfacts and async sound.
Is it required to x-mail this to the dvb-list?
I don't think that is really a (pure) VDR problem.
>> klogd 1.3-3#33.1, message.
>This should be done by the klogd using
>/System.map or /boot/System.map.
Hm, why he might did not do? :-)
Rainer---<=====> Vertraulich
//
//
<=====>--------------ocholl, Kiel, Germany ------------
Home |
Main Index |
Thread Index