Hi,
For a few month now my OpenSUSE Tumbleweed system (last checked on 20190902) has more and more problems reading Video DVDs. For some time I was able to read the first layer of a double layer DVD, and I blamed and changed my DVD drive (twice). But now I am able to read only about 1GB from the the disk. Out of desperation I even set the region code for my drive, which I did not do for 12 years. libdvdcss2 is able to determine the first two keys for a given disk only.
Is this a problem for me only, or could there be changes in libraries or kernel leading to this problem?
Kind regards Berthold
Op woensdag 4 september 2019 16:51:42 CEST schreef Berthold Höl lmann:
Hi,
For a few month now my OpenSUSE Tumbleweed system (last checked on 20190902) has more and more problems reading Video DVDs. For some time I was able to read the first layer of a double layer DVD, and I blamed and changed my DVD drive (twice). But now I am able to read only about 1GB from the the disk. Out of desperation I even set the region code for my drive, which I did not do for 12 years. libdvdcss2 is able to determine the first two keys for a given disk only.
Is this a problem for me only, or could there be changes in libraries or kernel leading to this problem?
Kind regards Berthold
DId you also replace the ( sata ) cable, the connectors on the motherboard. Some years ago something like this took me a couple of days to find out the sata connector was the culprit. All drives worked normally on another connector ( 1st one already dumped ... ).
Knurpht-openSUSE knurpht@opensuse.org writes:
Op woensdag 4 september 2019 16:51:42 CEST schreef Berthold Höl lmann:
Hi,
For a few month now my OpenSUSE Tumbleweed system (last checked on 20190902) has more and more problems reading Video DVDs. For some time I was able to read the first layer of a double layer DVD, and I blamed and changed my DVD drive (twice). But now I am able to read only about 1GB from the the disk. Out of desperation I even set the region code for my drive, which I did not do for 12 years. libdvdcss2 is able to determine the first two keys for a given disk only.
Is this a problem for me only, or could there be changes in libraries or kernel leading to this problem?
Kind regards Berthold
DId you also replace the ( sata ) cable, the connectors on the motherboard. Some years ago something like this took me a couple of days to find out the sata connector was the culprit. All drives worked normally on another connector ( 1st one already dumped ... ).
I did replace the cable now, but that did not fix the problem. I guess it has to do with libdvdread4 or libdvdcss2, I can burn DVD+RW and successfully read the burned data with the same drive.
Am 04.09.19 um 18:17 schrieb Berthold Höllmann:
Knurpht-openSUSE knurpht@opensuse.org writes:
Op woensdag 4 september 2019 16:51:42 CEST schreef Berthold Höl lmann:
Hi,
For a few month now my OpenSUSE Tumbleweed system (last checked on 20190902) has more and more problems reading Video DVDs. For some time I was able to read the first layer of a double layer DVD, and I blamed and changed my DVD drive (twice). But now I am able to read only about 1GB from the the disk. Out of desperation I even set the region code for my drive, which I did not do for 12 years. libdvdcss2 is able to determine the first two keys for a given disk only.
Is this a problem for me only, or could there be changes in libraries or kernel leading to this problem?
Kind regards Berthold
DId you also replace the ( sata ) cable, the connectors on the motherboard. Some years ago something like this took me a couple of days to find out the sata connector was the culprit. All drives worked normally on another connector ( 1st one already dumped ... ).
I did replace the cable now, but that did not fix the problem. I guess it has to do with libdvdread4 or libdvdcss2, I can burn DVD+RW and successfully read the burned data with the same drive.
Have you enabled packman repo and all what packman provide and you have already installed, used from packman?
simoN
-- www.becherer.de
On Wednesday 2019-09-04 18:17, Berthold Höllmann wrote:
I did replace the cable now, but that did not fix the problem. I guess it has to do with libdvdread4 or libdvdcss2, I can burn DVD+RW and successfully read the burned data with the same drive.
Well if that is your guess, then you can just copy the DVD with /usr/bin/readcd or /usr/bin/ddrescue to a file, and then the same problem should occur with said file.
Jan Engelhardt jengelh@inai.de writes:
On Wednesday 2019-09-04 18:17, Berthold Höllmann wrote:
I did replace the cable now, but that did not fix the problem. I guess it has to do with libdvdread4 or libdvdcss2, I can burn DVD+RW and successfully read the burned data with the same drive.
Well if that is your guess, then you can just copy the DVD with /usr/bin/readcd or /usr/bin/ddrescue to a file, and then the same problem should occur with said file.
Good point. So it is not the libraries, I can open images of DVD Video disks and view the content using vlc and mplayer.
Trying to generate the images on this machine aborts dd_rescue finds only 1073 MBytes, but I can read 4.3GB from DVD+RW disks. What else could be wrong here?
On 04/09/2019 23.16, Berthold Höllmann wrote:
Jan Engelhardt jengelh@inai.de writes:
On Wednesday 2019-09-04 18:17, Berthold Höllmann wrote:
I did replace the cable now, but that did not fix the problem. I guess it has to do with libdvdread4 or libdvdcss2, I can burn DVD+RW and successfully read the burned data with the same drive.
Well if that is your guess, then you can just copy the DVD with /usr/bin/readcd or /usr/bin/ddrescue to a file, and then the same problem should occur with said file.
Good point. So it is not the libraries, I can open images of DVD Video disks and view the content using vlc and mplayer.
Trying to generate the images on this machine aborts dd_rescue finds only 1073 MBytes, but I can read 4.3GB from DVD+RW disks. What else could be wrong here?
I'm not sure you can use ddrescue to copy a "purchased" video dvd. :-?
On Wednesday 2019-09-04 23:16, Berthold Höllmann wrote:
Jan Engelhardt jengelh@inai.de writes:
On Wednesday 2019-09-04 18:17, Berthold Höllmann wrote:
I did replace the cable now, but that did not fix the problem. I guess it has to do with libdvdread4 or libdvdcss2, I can burn DVD+RW and successfully read the burned data with the same drive.
Well if that is your guess, then you can just copy the DVD with /usr/bin/readcd or /usr/bin/ddrescue to a file, and then the same problem should occur with said file.
Good point. So it is not the libraries, I can open images of DVD Video disks and view the content using vlc and mplayer.
Trying to generate the images on this machine aborts dd_rescue finds only 1073 MBytes, but I can read 4.3GB from DVD+RW disks. What else could be wrong here?
1073741824 = 1024^3
This value does not appear in the CHS and LBA limitations of bygone generations of computer hardware.
But it is a value that .VOB files on DVDs generally do not exceed. In other words, it does not appear you are copying the disc as a whole entity; instead, you are erroneously copying just one file that contains only part of the entire feature.
Jan Engelhardt jengelh@inai.de writes:
On Wednesday 2019-09-04 23:16, Berthold Höllmann wrote:
Jan Engelhardt jengelh@inai.de writes:
On Wednesday 2019-09-04 18:17, Berthold Höllmann wrote:
I did replace the cable now, but that did not fix the problem. I guess it has to do with libdvdread4 or libdvdcss2, I can burn DVD+RW and successfully read the burned data with the same drive.
Well if that is your guess, then you can just copy the DVD with /usr/bin/readcd or /usr/bin/ddrescue to a file, and then the same problem should occur with said file.
Good point. So it is not the libraries, I can open images of DVD Video disks and view the content using vlc and mplayer.
Trying to generate the images on this machine aborts dd_rescue finds only 1073 MBytes, but I can read 4.3GB from DVD+RW disks. What else could be wrong here?
1073741824 = 1024^3
This value does not appear in the CHS and LBA limitations of bygone generations of computer hardware.
But it is a value that .VOB files on DVDs generally do not exceed. In other words, it does not appear you are copying the disc as a whole entity; instead, you are erroneously copying just one file that contains only part of the entire feature.
OK, this is somehow consistent with the fact that libdvdcss2 is only able to determine keys for the first, or first few VOB(s), and fails for the remaining. The DVD player software (or dd*) are only able to read the unlocked VOB(s).
But this happens only if I use libdvdcss2 on the physical DVD, when I create an ISO file from the DVD on another workstation, transfer it this, and use [mplayer,vlc] on the ISO file, keys for all VOBs are determined.
I had success using "readcd" for generating a ISO image from the video DVD and using mplayder with the generated file.
On Thursday 2019-09-05 22:37, Berthold Höllmann wrote:
Jan Engelhardt jengelh@inai.de writes:
On Wednesday 2019-09-04 23:16, Berthold Höllmann wrote:
Jan Engelhardt jengelh@inai.de writes:
On Wednesday 2019-09-04 18:17, Berthold Höllmann wrote:
I did replace the cable now, but that did not fix the problem. I guess it has to do with libdvdread4 or libdvdcss2, I can burn DVD+RW and successfully read the burned data with the same drive.
Well if that is your guess, then you can just copy the DVD with /usr/bin/readcd or /usr/bin/ddrescue to a file, and then the same problem should occur with said file.
Good point. So it is not the libraries, I can open images of DVD Video disks and view the content using vlc and mplayer.
Trying to generate the images on this machine aborts dd_rescue finds only 1073 MBytes, but I can read 4.3GB from DVD+RW disks. What else could be wrong here?
1073741824 = 1024^3
This value does not appear in the CHS and LBA limitations of bygone generations of computer hardware.
But it is a value that .VOB files on DVDs generally do not exceed. In other words, it does not appear you are copying the disc as a whole entity; instead, you are erroneously copying just one file that contains only part of the entire feature.
OK, this is somehow consistent with the fact that libdvdcss2 is only able to determine keys for the first, or first few VOB(s), and fails for the remaining. The DVD player software (or dd*) are only able to read the unlocked VOB(s).
That must simply be untrue. dd* does not care whether the files are locked or not. Unless you have a serious hardware defect (but I more think of it as a layer-7 problem), there is more than 1 GB to be extracted. If the tools are used, properly.
Jan Engelhardt jengelh@inai.de writes:
On Thursday 2019-09-05 22:37, Berthold Höllmann wrote:
Jan Engelhardt jengelh@inai.de writes:
On Wednesday 2019-09-04 23:16, Berthold Höllmann wrote:
Jan Engelhardt jengelh@inai.de writes:
On Wednesday 2019-09-04 18:17, Berthold Höllmann wrote:
I did replace the cable now, but that did not fix the problem. I guess it has to do with libdvdread4 or libdvdcss2, I can burn DVD+RW and successfully read the burned data with the same drive.
Well if that is your guess, then you can just copy the DVD with /usr/bin/readcd or /usr/bin/ddrescue to a file, and then the same problem should occur with said file.
Good point. So it is not the libraries, I can open images of DVD Video disks and view the content using vlc and mplayer.
Trying to generate the images on this machine aborts dd_rescue finds only 1073 MBytes, but I can read 4.3GB from DVD+RW disks. What else could be wrong here?
1073741824 = 1024^3
This value does not appear in the CHS and LBA limitations of bygone generations of computer hardware.
But it is a value that .VOB files on DVDs generally do not exceed. In other words, it does not appear you are copying the disc as a whole entity; instead, you are erroneously copying just one file that contains only part of the entire feature.
OK, this is somehow consistent with the fact that libdvdcss2 is only able to determine keys for the first, or first few VOB(s), and fails for the remaining. The DVD player software (or dd*) are only able to read the unlocked VOB(s).
That must simply be untrue. dd* does not care whether the files are locked or not. Unless you have a serious hardware defect (but I more think of it as a layer-7 problem), there is more than 1 GB to be extracted. If the tools are used, properly.
But I think the DVD drive does. I insert a video DVD in the drive and call
LC_ALL=C dd if=/dev/sr0 of=out.iso
dd: error reading '/dev/sr0': Input/output error 2352+0 records in 2352+0 records out 1204224 bytes (1.2 MB, 1.1 MiB) copied, 0.384053 s, 3.1 MB/s
mplayer dvd://
... (lots of keys on this DVD found, lots more of them not found using libdvdcss2) ...
dd if=/dev/sr0 of=~/ISOs/Hanna.iso
2097151+0 Datensätze ein 2097151+0 Datensätze aus 1073741312 bytes (1,1 GB, 1,0 GiB) copied, 127,892 s, 8,4 MB/s
sudo readcd f=test.iso
No target specified, trying to find one... Using dev=4,0,0. Read speed: 16620 kB/s (CD 94x, DVD 12x, BD 3x). Write speed: 4234 kB/s (CD 24x, DVD 3x, BD 0x). Capacity: 3005491 Blocks = 6010982 kBytes = 5870 MBytes = 6155 prMB Sectorsize: 2048 Bytes Copy from SCSI (4,0,0) disk to file 'test.iso' end: 3005491 addr: 3005491 cnt: 51 Time total: 549.278sec Read 6010982,00 kB at 10943,4 kB/sec.
ls -lh test.iso
-rw-r--r-- 1 root root 5,8G 6. Sep 00:57 test.iso
This is the actual sequence of the commands. So in some way libdvdcss2 unlocked the DVD drive in some way, and dd did not read the whole disk.
On 05/09/2019 22:37, Berthold Höllmann wrote:
Jan Engelhardt jengelh@inai.de writes:
On Wednesday 2019-09-04 23:16, Berthold Höllmann wrote:
Jan Engelhardt jengelh@inai.de writes:
On Wednesday 2019-09-04 18:17, Berthold Höllmann wrote:
I did replace the cable now, but that did not fix the problem. I guess it has to do with libdvdread4 or libdvdcss2, I can burn DVD+RW and successfully read the burned data with the same drive.
Well if that is your guess, then you can just copy the DVD with /usr/bin/readcd or /usr/bin/ddrescue to a file, and then the same problem should occur with said file.
Good point. So it is not the libraries, I can open images of DVD Video disks and view the content using vlc and mplayer.
Trying to generate the images on this machine aborts dd_rescue finds only 1073 MBytes, but I can read 4.3GB from DVD+RW disks. What else could be wrong here?
1073741824 = 1024^3
This value does not appear in the CHS and LBA limitations of bygone generations of computer hardware.
But it is a value that .VOB files on DVDs generally do not exceed. In other words, it does not appear you are copying the disc as a whole entity; instead, you are erroneously copying just one file that contains only part of the entire feature.
OK, this is somehow consistent with the fact that libdvdcss2 is only able to determine keys for the first, or first few VOB(s), and fails for the remaining. The DVD player software (or dd*) are only able to read the unlocked VOB(s).
But this happens only if I use libdvdcss2 on the physical DVD, when I create an ISO file from the DVD on another workstation, transfer it this, and use [mplayer,vlc] on the ISO file, keys for all VOBs are determined.
I had success using "readcd" for generating a ISO image from the video DVD and using mplayder with the generated file.
Try using dd_rhelp on the dvd, it is a persistent form of dd_rescue and doesn't give up, it also logs the beginning and end of the dvd to the console. It's the only thing that can get around (can't remember the name offhand) security in the form of deliberate bad sectors. A normal dvd machine simply skips the bad sectors but a computer chokes on them. Be warned, using dd_rhelp on these disks puts a strain on the dvd drive.
Regards Dave P
On Friday 2019-09-06 09:17, Dave Plater wrote:
Try using dd_rhelp on the dvd, it is a persistent form of dd_rescue and doesn't
ddrescue is GNU ddrescue and does not have the problems of dd_rescue that the bolt-on solution dd_rhelp tries to work around ;-)
On 06/09/2019 09:19, Jan Engelhardt wrote:
On Friday 2019-09-06 09:17, Dave Plater wrote:
Try using dd_rhelp on the dvd, it is a persistent form of dd_rescue and doesn't
ddrescue is GNU ddrescue and does not have the problems of dd_rescue that the bolt-on solution dd_rhelp tries to work around ;-)
But it does display the start and endpoints of the dvd.
Dave
On Friday 2019-09-06 09:24, Dave Plater wrote:
On 06/09/2019 09:19, Jan Engelhardt wrote:
On Friday 2019-09-06 09:17, Dave Plater wrote:
Try using dd_rhelp on the dvd, it is a persistent form of dd_rescue and doesn't
ddrescue is GNU ddrescue and does not have the problems of dd_rescue that the bolt-on solution dd_rhelp tries to work around ;-)
But it does display the start and endpoints of the dvd.
What is that even supposed to mean? As far as /dev/sr0 is concerned, is starts at 0KB and ends at whatever the kernel interface makes it to be; from this, both dd_rescue and ddrescue can show the size (not that that's useful when the block device yields 1GB while a raw read yields 6GB)
maybe i have not seen (read here) and you have already tested this:
is it only on one (this) specific dvd or more than one tested dvd?
have you tested the same with a live system? i use for test systemrescuecd http://www.system-rescue-cd.org/ if it is the same, you could be sure opensuse is not the problem.
have you checked for a bios update of your system? i have had in past strange behavior with old bios versions, and new kernels. updating bios solved it in !!one!! case
simoN
Simon Becherer simon@becherer.de writes:
maybe i have not seen (read here) and you have already tested this:
is it only on one (this) specific dvd or more than one tested dvd?
I tested several DVDs.
have you tested the same with a live system? i use for test systemrescuecd http://www.system-rescue-cd.org/ if it is the same, you could be sure opensuse is not the problem.
I will try a live system later.
have you checked for a bios update of your system? i have had in past strange behavior with old bios versions, and new kernels. updating bios solved it in !!one!! case
My system is quite oldisch (AMD Athlon(tm) II X3 445 Processor on ASUSTeK M5A88-V EVO) and could not find a new BIOS for ages (the current one is installed for years, and the process worked with the current HW setting previously, except the DVD drive i exchanged recently, trying to fix the DVD read problems).
simoN
-- www.becherer.de
Jan Engelhardt jengelh@inai.de writes:
On Friday 2019-09-06 09:24, Dave Plater wrote:
On 06/09/2019 09:19, Jan Engelhardt wrote:
On Friday 2019-09-06 09:17, Dave Plater wrote:
Try using dd_rhelp on the dvd, it is a persistent form of dd_rescue and doesn't
ddrescue is GNU ddrescue and does not have the problems of dd_rescue that the bolt-on solution dd_rhelp tries to work around ;-)
But it does display the start and endpoints of the dvd.
What is that even supposed to mean? As far as /dev/sr0 is concerned, is starts at 0KB and ends at whatever the kernel interface makes it to be; from this, both dd_rescue and ddrescue can show the size (not that that's useful when the block device yields 1GB while a raw read yields 6GB)
I prefer watching video DVDs by first creating an ISO file (UDF filesystem data (version 1.5)) on disk and using the ISO file with mplayer.
For some time I simply used 'cat'. Because I do this quite often, and sometimes the discs are scratched I wrote a script the first uses 'mplayer' to unlock the DVD drive for reading the encrypted and then uses 'ddrescue -b 2048 -r 1 -v /dev/sr0 out.iso mapfile' and more forward and backward scans of the disc utilizing 'mapfile' in an attempt to rescue more of the content from scratched discs. It did work quite nice for some time (I think the script is from 2015) for lots of discs, but got worse and worse in the last few months. And no, ddrescue does not work on encrypted discs prior to using libdvdcss2 on the disc (mplayer has to run every time the DVD drive slide has closed, before any kind of success is achieved using dd, readcd, or ddrescue).
Am 06.09.19 um 11:16 schrieb Berthold Höllmann:
Jan Engelhardt jengelh@inai.de writes:
On Friday 2019-09-06 09:24, Dave Plater wrote:
On 06/09/2019 09:19, Jan Engelhardt wrote:
On Friday 2019-09-06 09:17, Dave Plater wrote:
Try using dd_rhelp on the dvd, it is a persistent form of dd_rescue and doesn't
ddrescue is GNU ddrescue and does not have the problems of dd_rescue that the bolt-on solution dd_rhelp tries to work around ;-)
But it does display the start and endpoints of the dvd.
What is that even supposed to mean? As far as /dev/sr0 is concerned, is starts at 0KB and ends at whatever the kernel interface makes it to be; from this, both dd_rescue and ddrescue can show the size (not that that's useful when the block device yields 1GB while a raw read yields 6GB)
I prefer watching video DVDs by first creating an ISO file (UDF filesystem data (version 1.5)) on disk and using the ISO file with mplayer.
For some time I simply used 'cat'. Because I do this quite often, and sometimes the discs are scratched I wrote a script the first uses 'mplayer' to unlock the DVD drive for reading the encrypted and then uses 'ddrescue -b 2048 -r 1 -v /dev/sr0 out.iso mapfile' and more forward and backward scans of the disc utilizing 'mapfile' in an attempt to rescue more of the content from scratched discs. It did work quite nice for some time (I think the script is from 2015) for lots of discs, but got worse and worse in the last few months. And no, ddrescue does not work on encrypted discs prior to using libdvdcss2 on the disc (mplayer has to run every time the DVD drive slide has closed, before any kind of success is achieved using dd, readcd, or ddrescue).
only as a hint:
ok, its maybe very unusual but: you wrote you have tested 2 dvd-drives, and exchanged also cable. ok so could it be possible that you have 2 bad drives? have you tested the drives in another computer? you know murphy? i have had last month different broken parts at same time. i gave up and spend a lot of money >2500€ to by complete new hardware. after new hardware arrived, with this new hardware i figured out what was really the problem. one external video converter for 25€ AND a harddrive for 85€ (it was a little more complex because there where 2 harddrives involved and its a special-closed-linux-system, without access to the system for users/customers) :-((((((
simoN
On 06/09/2019 11.16, Berthold Höllmann wrote:
I prefer watching video DVDs by first creating an ISO file (UDF filesystem data (version 1.5)) on disk and using the ISO file with mplayer.
For some time I simply used 'cat'. Because I do this quite often, and sometimes the discs are scratched I wrote a script the first uses 'mplayer' to unlock the DVD drive for reading the encrypted and then uses 'ddrescue -b 2048 -r 1 -v /dev/sr0 out.iso mapfile' and more forward and backward scans of the disc utilizing 'mapfile' in an attempt to rescue more of the content from scratched discs. It did work quite nice for some time (I think the script is from 2015) for lots of discs, but got worse and worse in the last few months. And no, ddrescue does not work on encrypted discs prior to using libdvdcss2 on the disc (mplayer has to run every time the DVD drive slide has closed, before any kind of success is achieved using dd, readcd, or ddrescue).
I don't have a freshly purchased DVD to try, but what about using a tool such as "dvdrip"? Or HandBrakeGUI?
"Carlos E. R." robin.listas@telefonica.net writes:
On 06/09/2019 11.16, Berthold Höllmann wrote:
I prefer watching video DVDs by first creating an ISO file (UDF filesystem data (version 1.5)) on disk and using the ISO file with mplayer.
For some time I simply used 'cat'. Because I do this quite often, and sometimes the discs are scratched I wrote a script the first uses 'mplayer' to unlock the DVD drive for reading the encrypted and then uses 'ddrescue -b 2048 -r 1 -v /dev/sr0 out.iso mapfile' and more forward and backward scans of the disc utilizing 'mapfile' in an attempt to rescue more of the content from scratched discs. It did work quite nice for some time (I think the script is from 2015) for lots of discs, but got worse and worse in the last few months. And no, ddrescue does not work on encrypted discs prior to using libdvdcss2 on the disc (mplayer has to run every time the DVD drive slide has closed, before any kind of success is achieved using dd, readcd, or ddrescue).
I don't have a freshly purchased DVD to try, but what about using a tool such as "dvdrip"? Or HandBrakeGUI?
readcd does work.
Berthold Höllmann berthold-tumbleweed@xn--hllmanns-n4a.de wrote:
readcd does work.
Did you read the whole DVD using readcd?
Some of the sectors are readable in case that the encryption has not yet been set up.
Jörg
Joerg Schilling Joerg.Schilling@fokus.fraunhofer.de writes:
Berthold Höllmann berthold-tumbleweed@xn--hllmanns-n4a.de wrote:
readcd does work.
Did you read the whole DVD using readcd?
Yes, the whole DVD, at least I can watch the DVD content via the generated fileusing vlc or mplayer without problems.
Some of the sectors are readable in case that the encryption has not yet been set up.
I "unlock" the DVD using "mplayer dvd://" just before calling "readcd". Strangely enough, calling "mplayer" on the DVD device libdvdread is not able to get all keys, but when I call
mplayer -dvd-device <generated file> dvd://
All (or at least most) of the keys are calculated.
Jörg
Berthold
Hi Berthold,
On Wed, 04 Sep 2019, 16:51:42 +0200, Berthold Höllmann wrote:
Hi,
For a few month now my OpenSUSE Tumbleweed system (last checked on 20190902) has more and more problems reading Video DVDs. For some time I was able to read the first layer of a double layer DVD, and I blamed and changed my DVD drive (twice). But now I am able to read only about 1GB from the the disk. Out of desperation I even set the region code for my drive, which I did not do for 12 years. libdvdcss2 is able to determine the first two keys for a given disk only.
Is this a problem for me only, or could there be changes in libraries or kernel leading to this problem?
I followed this thread for some time, but I haven't seen an answer to this yet:
Did this particular DVD work for you at _any_ time?
I own some DVDs (mostly Disney crap) which are really difficult to work with...
Kind regards Berthold
HTH, cheers.
l8er manfred
Manfred Hollstein mhollstein@t-online.de writes:
Hi Berthold,
On Wed, 04 Sep 2019, 16:51:42 +0200, Berthold Höllmann wrote:
Hi,
For a few month now my OpenSUSE Tumbleweed system (last checked on 20190902) has more and more problems reading Video DVDs. For some time I was able to read the first layer of a double layer DVD, and I blamed and changed my DVD drive (twice). But now I am able to read only about 1GB from the the disk. Out of desperation I even set the region code for my drive, which I did not do for 12 years. libdvdcss2 is able to determine the first two keys for a given disk only.
Is this a problem for me only, or could there be changes in libraries or kernel leading to this problem?
I followed this thread for some time, but I haven't seen an answer to this yet:
Did this particular DVD work for you at _any_ time?
I own some DVDs (mostly Disney crap) which are really difficult to work with...
Kind regards Berthold
HTH, cheers.
l8er manfred
Yes they did work, and they do work using readcd.
-
berthold-tumbleweed＠xn--hllmanns-n4a.de -
Carlos E. R. -
Dave Plater -
Jan Engelhardt -
Joerg Schilling -
Knurpht-openSUSE -
Manfred Hollstein -
Simon Becherer