From: Denis Vlasenko <vda.linux@googlemail.com>
To: mplayer-users@mplayerhq.hu
Cc: "Marcin 'Rambo' Roguski" <rambo@id.uw.edu.pl>,
linux-kernel@vger.kernel.org
Subject: Re: [MPlayer-users] Weird behaviour in ide-scsi driven dvd playback with 2.6.17.x
Date: Sat, 19 Aug 2006 20:25:58 +0200 [thread overview]
Message-ID: <200608192025.58331.vda.linux@googlemail.com> (raw)
In-Reply-To: <20060819193408.10a5297a.rambo@id.uw.edu.pl>
On Saturday 19 August 2006 19:34, Marcin 'Rambo' Roguski wrote:
> Because of USB camera requirements, I'm currently running double-kernel
> setup (2.4.32-old, 2.6.17.9-new), and ide-scsi driven CD-ROM/DVD drives.
>
> While on 2.4.32 mplayer (version doesn't matter happens with svn and
> pre8- libdvdread compiled as default) plays DVDs perfectly well, on 2.6.17.[6|9] I'm
> getting such messages from kernel while trying to open them:
>
> Aug 19 18:06:33 beethoven kernel: Buffer I/O error on device sr1, logical block 4496
> Aug 19 18:06:33 beethoven kernel: Buffer I/O error on device sr1, logical block 4497
> Aug 19 18:06:33 beethoven kernel: Buffer I/O error on device sr1, logical block 4498
> [...]
> and so on...
>
> The only workaround for now is to use ide-cd, and then it works like a charm, but I'd preffer "unified" setup (unless mplayer can use conditional statements in its config...
Sounds like kernel-side problem. ide-scsi says it have problem reding data
from the media, whereas ide-cd does not have the problem.
Does this happen while you just copy the file with cp?
[adding linux-kernel@vger.kernel.org to CC:]
--
vda
next parent reply other threads:[~2006-08-19 18:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060819193408.10a5297a.rambo@id.uw.edu.pl>
2006-08-19 18:25 ` Denis Vlasenko [this message]
2006-08-19 18:52 ` [MPlayer-users] Weird behaviour in ide-scsi driven dvd playback with 2.6.17.x Marcin 'Rambo' Roguski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200608192025.58331.vda.linux@googlemail.com \
--to=vda.linux@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mplayer-users@mplayerhq.hu \
--cc=rambo@id.uw.edu.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.