From: Ismail Donmez <ismail@pardus.org.tr>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: Rakhesh Sasidharan <rakhesh@rakhesh.com>,
rakheshster@yahoo.com, linux-kernel@vger.kernel.org
Subject: Re: VCD not readable under 2.6.18
Date: Sat, 9 Dec 2006 16:15:21 +0200 [thread overview]
Message-ID: <200612091615.22435.ismail@pardus.org.tr> (raw)
In-Reply-To: <20061209132120.7af3ce66@localhost.localdomain>
09 Ara 2006 Cts 15:21 tarihinde, Alan şunları yazmıştı:
> > I didn't see any responses after the post linked to above, so I'd like to
> > add that I too get this problem and that I've tried with various VCDs and
> > players. In previous versions of these distros I could just mount the VCD
> > and copy the *.DAT files across; but in the current versions I can't even
> > mount! dmesg gets flooded with errors such as the below:
> >
> >
> >
> > hdc: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdc: command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
> > ide: failed opcode was: unknown
> > ATAPI device hdc:
> > Error: Illegal request -- (Sense key=0x05)
> > Illegal mode for this track or incompatible medium -- (asc=0x64,
> > ascq=0x00) The failed "Read 10" packet command was:
> > "28 00 00 00 73 f2 00 00 01 00 00 00 00 00 00 00 "
>
> Your system tried to read a Video data block. The usual cure for this
> problem is to remove Gnome, or at least kill all the Gnome stuff and flip
> to init level 3 then mount the cd from the command line.
Well my bet is xine-lib is buggy somehow as I can reproduce this bug with
kaffeine ( KDE media player ).
Regards,
ismail
next prev parent reply other threads:[~2006-12-09 14:15 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-09 6:06 VCD not readable under 2.6.18 Rakhesh Sasidharan
2006-12-09 8:14 ` Ismail Donmez
2006-12-09 13:21 ` Alan
2006-12-09 14:15 ` Ismail Donmez [this message]
2006-12-09 14:36 ` Alan
2006-12-09 14:31 ` Ismail Donmez
2006-12-09 16:09 ` S.Çağlar Onur
-- strict thread matches above, loose matches on Subject: below --
2006-12-12 19:21 Rakhesh Sasidharan
2006-12-11 17:58 Rakhesh Sasidharan
2006-12-10 4:33 Rakhesh Sasidharan
2006-12-10 4:27 Rakhesh Sasidharan
2006-12-09 17:23 Rakhesh Sasidharan
2006-12-09 19:46 ` Bill Davidsen
2006-12-10 0:50 ` Alan
2006-12-09 23:19 ` S.Çağlar Onur
2006-12-10 0:44 ` Alan
2006-12-09 13:33 Rakhesh Sasidharan
2006-12-09 8:48 Rakhesh Sasidharan
2006-10-16 18:53 wixor
2006-10-16 23:12 ` Alan Cox
2006-10-17 18:16 ` wixor
2006-10-17 22:38 ` Alan Cox
2006-10-17 22:21 ` Prakash Punnoor
2006-10-17 22:45 ` Olivier Galibert
2006-10-19 16:35 ` wixor
2006-10-19 16:42 ` Alan Cox
2006-10-19 17:39 ` wixor
2006-10-20 13:05 ` Alan Cox
2006-10-24 16:06 ` wixor
2006-10-29 19:23 ` S.Çağlar Onur
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=200612091615.22435.ismail@pardus.org.tr \
--to=ismail@pardus.org.tr \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rakhesh@rakhesh.com \
--cc=rakheshster@yahoo.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox