On Mon, Jan 24, 2011 at 4:27 PM, Jose Juan Montiel <
josejuan.montiel@???> wrote:
> <snip>
>
> a hard problem
>
>
>
>
I don't usually contribute to these kinds of conversations but... one of my
warm spare machines happens to have an Asus M2A-VM motherboard with
integrated ATI Radeon X1250-based graphics. So, I thought... even though I
use mplayer and not vlc I'd take half an hour and see if I could offer some
insight.
I installed vlc:
me@machine:~$ sudo aptitude install vlc
....
Setting up libdvbpsi4 (0.1.5-3.1) ...
Setting up libebml0 (0.7.7-3.1) ...
Setting up libmatroska0 (0.8.1-1.1) ...
Setting up libmpeg2-4 (0.4.1-3) ...
Setting up libsdl-image1.2 (1.2.6-3) ...
Setting up libtar (1.2.11-5) ...
Setting up libvlc0 (0.8.6.h-4+lenny2.3) ...
Setting up libxosd2 (2.2.14-1.6) ...
Setting up vlc-nox (0.8.6.h-4+lenny2.3) ...
Setting up vlc (0.8.6.h-4+lenny2.3) ...
....
I went ahead and downloaded a test video, specifically this one:
http://www-eng-x.llnl.gov/documents/a_movie2.mpeg
I played it:
me@machine:~$ vlc a_movie2.mpeg
Both sound and video looked good.
I have to wonder... what video driver are you using? And, just how badly
have your packages and repositories been mucked with (i.e. switching back
and forth from experimental, installing 3rd-party debs, etc). In addition,
what *specific* video are you trying to play and how... (i.e. can you create
a more formal test case)?
Assuming my very simple test wasn't flawed, I'd have to point the finger at
either the video driver you're using or your installed packages. BTW, I'm
using "fglrx" (personally, I've had rather poor luck with Lenny's "radeon"
and "radeonhd"):
fglrx-atieventsd/lenny uptodate 1:8-12-4
fglrx-driver/lenny uptodate 1:8-12-4
fglrx-glx/lenny uptodate 1:8-12-4
fglrx-modules-2.6.26-2-686/lenny uptodate 2.6.26+8-12-2+lenny1
Maybe try removing and re-installing the appropriate dependent packages so
that the binary interfaces can match appropriately. My machine is basically
a vanilla Lenny install and doesn't really have any changes to
/etc/apt/sources.list except the addition of non-free and "deb
http://www.debian-multimedia.org lenny main non-free".
Last but not least... it could always be your hardware. Is it dusty in the
computer's case - did you spill fruit juice on the motherboard? ;-) If
you're pretty sure that the hardware is okay and you don't use the machine
in a production process... heck, I'd just do some backups and then
re-install everything from scratch... as they say, premature optimization is
the root of all evil. That is, why bother tracing a nasty problem if what's
on the machine isn't actually that important?
Ultimately do what you think is best in your judgment - but keep in mind
that determining the problem could be quite painful without a more formal
procedure and test case.
Best of luck.
