From: gaxt <gaxt@rogers.com>
To: linux-kernel@vger.kernel.org
Subject: DVD Problems 2.6.0-test3 & 2.6.0-test2-mm5
Date: Sat, 09 Aug 2003 11:19:32 -0400 [thread overview]
Message-ID: <3F351104.4070302@rogers.com> (raw)
In-Reply-To: <Pine.LNX.4.56.0308091036190.16795@filesrv1.baby-dragons.com>
DVDs play fine in 2.4.21 but will not play in 2.6.0-test2-mm5 or
2.6.0-test3. With ogle, this is what spits out:
dave@localhost dave $ ogle
libdvdread: Using libdvdcss version 1.2.6 for DVD access
libdvdread: Using libdvdcss version 1.2.6 for DVD access
libdvdread: Attempting to retrieve all CSS keys
libdvdread: This can take a _long_ time, please be patient
libdvdread: Get key for /VIDEO_TS/VTS_01_0.VOB at 0x00000182
libdvdread: Error cracking CSS key for /VIDEO_TS/VTS_01_0.VOB (0x00000182)
libdvdread: Elapsed time 0
libdvdread: Get key for /VIDEO_TS/VTS_01_1.VOB at 0x00020316
libdvdread: Error cracking CSS key for /VIDEO_TS/VTS_01_1.VOB (0x00020316)!!
libdvdread: Elapsed time 0
libdvdread: Found 1 VTS's
libdvdread: Elapsed time 0
FATAL[ogle_mpeg_ps]: dvdreadblocks failed
dave@localhost dave $
I tried several DVDs and three gave the above error and one worked but I
suspect the working one had no copy-protection encoding (low budget
release unlike the two others: Jeeves & Wooster and Blackadder and Dirty
Harry).
Unfortunately, I never tested DVD with the other 2.6.0 kernel releases.
next prev parent reply other threads:[~2003-08-09 15:06 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-09 10:46 2.6.0-test3 cannot mount root fs gaxt
2003-08-09 10:40 ` Norbert Preining
2003-08-09 11:56 ` Herbert Pötzl
2003-08-09 9:07 ` Norbert Preining
[not found] ` <20030809130641.A8174@electric-eye.fr.zoreil.com>
[not found] ` <01a201c35e65$0536ef60$ee52a450@theoden>
2003-08-09 11:58 ` Henrik Storner
2003-08-09 13:48 ` Felipe Alfaro Solana
2003-08-09 14:32 ` Mr. James W. Laferriere
2003-08-09 14:48 ` gaxt
2003-08-09 14:38 ` Mr. James W. Laferriere
2003-08-09 15:19 ` gaxt [this message]
2003-08-09 15:01 ` Henrik Ræder Clausen
2003-08-10 21:17 ` Norbert Preining
2003-08-10 22:43 ` Andrew Morton
2003-08-11 5:34 ` Norbert Preining
2003-08-11 14:59 ` Herbert Pötzl
2003-08-11 15:40 ` Norbert Preining
2003-08-11 18:53 ` Herbert Pötzl
2003-08-11 21:50 ` Norbert Preining
2003-08-11 22:21 ` Herbert Pötzl
2003-08-12 1:52 ` Mark W. Alexander
2003-08-12 6:28 ` Norbert Preining
2003-08-12 5:39 ` Norbert Preining
2003-08-12 12:26 ` Herbert Pötzl
2003-08-12 12:31 ` Norbert Preining
2003-08-12 12:44 ` jeff millar
2003-08-12 23:52 ` Thomas Molina
2003-08-13 16:59 ` Paul Dickson
2003-08-14 4:09 ` jeff millar
2003-08-13 6:15 ` SOLUTION " Norbert Preining
2003-08-13 6:27 ` "Andrey Borzenkov"
2003-08-13 6:30 ` Norbert Preining
2003-08-13 12:07 ` jeff millar
2003-08-13 12:30 ` Herbert Pötzl
[not found] ` <00bb01c36198$51cba650$6401a8c0@wa1hco>
2003-08-13 13:24 ` Herbert Pötzl
[not found] ` <009b01c362d5$13838b90$6401a8c0@wa1hco>
[not found] ` <20030815030013.GA9587@www.13thfloor.at>
[not found] ` <00a401c3632a$80dd2a20$6401a8c0@wa1hco>
[not found] ` <20030815132619.GB3695@www.13thfloor.at>
2003-08-16 0:34 ` 2.6.0-test3 _still_ " jeff millar
2003-08-16 15:00 ` Herbert Pötzl
2003-08-13 13:24 ` SOLUTION Re: 2.6.0-test3 " Christian Mautner
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=3F351104.4070302@rogers.com \
--to=gaxt@rogers.com \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).