[vdr] Re: Try to fix "unknown picture error"

[Harald Bernlochner <list@bernlochner.de>]

> As I said above: I had an errorfree system with vdr 1.1.26 and DVB from
> mid-june. That's exactly the combination which I try at the moment. And
> until now, there are no "unknown picture error". It's not clear, why the
> driver from 27.4.03 produces the "unknown picture error", even with 1.1.26.

I'll try this combination on my system too.

> Absolutely right. But it's also a fact, that an upgrade of vdr (or DVB as
> we had learnt) changes this behaviour.
>
> > [...]
> > So my conclusion, lets compare our systems and libraries that are loaded
> > by
> > vdr.
> > ldd ./vdr1.2.25pre2 gives on my suse 8.2:
> >         libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0x40025000)
> >         libpthread.so.0 => /lib/libpthread.so.0 (0x40044000)
> >         libdl.so.2 => /lib/libdl.so.2 (0x40095000)
> >         libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x40098000)
> >         libm.so.6 => /lib/libm.so.6 (0x40150000)
> >         libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x40172000)
> >         libc.so.6 => /lib/libc.so.6 (0x4017a000)
> >         /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
> > Maybe some of you know, how to show the libs loaded by the driver too.
>
> Good idea, I have this (and also an unstable system :-( ):
> 	libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0x4001e000)
> 	libpthread.so.0 => /lib/i686/libpthread.so.0 (0x4003f000)
> 	libdl.so.2 => /lib/libdl.so.2 (0x4008f000)
> 	libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x40092000)
> 	libm.so.6 => /lib/i686/libm.so.6 (0x40144000)
> 	libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x40167000)
> 	libc.so.6 => /lib/i686/libc.so.6 (0x40170000)
> 	/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
Is there someone with this libs a stable system?
Anybody else tried a "ldd vdr"?

Harald


-- 
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe vdr" as subject.