Fwd: xine Problem

[Lawrence Tilly]

D'oh.  Sent this to Ben only.  Silly gmail.

---------- Forwarded message ----------
From: Lawrence Tilly <mail.list.tilly at gmail.com>
Date: Feb 16, 2006 9:33 AM
Subject: Re: xine Problem
To: Ben Scott <dragonhawk at gmail.com>


Thanks for the extra tips, Ben.  I have seen some complaints about
kernal patches killing xine ( libdvd actually ) but I haven't applied
one recently.

For grins, late last night I rebooted the box for the first time since
I uninstalled and reinstalled the xine RPMs and...it's working again!
Mostly.  There is a slight ghost of a vertical bar running down the
xine window in the right third of the image.  I will have to play with
other sources to see if it's specific to only certain DVDs, all DVDs,
or all media xine is playing for me. I'm also going to try burning
some sample DVD stuff and play it elsewhere to see how that looks.

One final thing I thought about was that when I installed the unit, I
left the master / slave jumper on the device in the position where the
role should be auto-detected ( can't remember the official term
here...sorry ).  This was the same setting that the CD burner that was
in that spot initially was using and I had no problem with that
device.  However, it was also the only device on that connection.
When I swapped in the DVD burner I also added a spare basic CD drive (
also using the "auto" jumper setting ).  I think I'll pop the box and
set those to Master / Slave manually just in case that's impacting
this.

Anyway, thianks again and if anyone thinks of anything else please post!!!
-Lawrence

On 2/15/06, Ben Scott <dragonhawk at gmail.com> wrote:
> On 2/15/06, Lawrence Tilly <mail.list.tilly at gmail.com> wrote:
> > Any suggestions??????
>
>   DTVZ is right in that things like "Can't seek to block" and "Invalid
> IFO for title" do sound like low-level trouble.  For example, bad
> media, or a bad drive.  But it could also be a problem in a driver or
> subsystem in the kernel.  Have you updated your kernel since it worked
> last?  Also, check the kernel log (dmesg) to see if it's trying to
> tell you something.
>
> -- Ben