CD/DVD Combo drive problem (Was: DVD playing problem)
On Wednesday 12 November 2003 03:07, Rohit wrote:
I was playing DVD on Linux using mplayer which is home-built using libdvdnav and libdvdread [not libdvdcss]. The playabck starts, and then becomes jittery, and then pauses intermittently and finally hangs after two minutes of play.
Do you have your drive set to us DMA? This is typical behaviour when not useing dma. Set this in YAST not via hdparms. Yast does it at the right time, hdparms is after idescsi, and often fails.
Two questions: 1> In attempting to set up for DMA (not knowing what it was (or is) I went into YASY hardware config / CD Drives, and saw that my CD/DVD drive, while listed, wasn't selected. So I selected it. This caused things to break, and I don't know how to fix 'em... I'll explain in a moment. 2> Before I get too far off the topic, exactly what is DMA, and how do you set it up? Okay. Back to my new problem. Now the CD-RW/DVD (combo) drive works as a CD-ROM only. Well, probably a CD-RW as well, but I havn't tested it out yet. And it reads DVDs. But when a DVD is in the drive, I no longer see the nifty CD-Recordable icon change to read "DVD" -- which implies that this is a system problem. When I go into Xine to try to play the DVD, it can't find /dev/dvd. Until now, I have had no problem accessing the DVDs through xine. (Well, not completely true, I was getting very jerky feedback, which is what caused me to seach the archives and find the above message from a few days ago.) So I go back in remove it. Now I've lost the entire drive -- Linux can't see it at all! It appears that some bizzare half-setting is the correct setting for my CD/DVD drive, but I only have "Add" and "Remove" as options. I don't see a way to manually edit things. (For that matter, I'm not sure what they should be set to... But I am willing to play around and guess...) I'm running SuSE 9.0 on a fresh install, and have loaded the patches available from the website. I've removed xine from the system, and loaded a non-crippled version that was working smoothly (aside from the aforementioned problem). I'm at a loss here. Any ideas/suggestions/thoughts on how to get my DVD functionallity back? Thanks in advance! Krikket
#1 has been solved -- see below #2 is still a major problem. Also see below. (If I can't figure this out be next week, I'll probably just reinstall SuSE from scratch. Hate to do it, but...) On Fri, 14 Nov 2003, Krikket wrote:
On Wednesday 12 November 2003 03:07, Rohit wrote:
I was playing DVD on Linux using mplayer which is home-built using libdvdnav and libdvdread [not libdvdcss]. The playabck starts, and then becomes jittery, and then pauses intermittently and finally hangs after two minutes of play.
Do you have your drive set to us DMA? This is typical behaviour when not useing dma. Set this in YAST not via hdparms. Yast does it at the right time, hdparms is after idescsi, and often fails.
Two questions:
1> In attempting to set up for DMA (not knowing what it was (or is) I went into YASY hardware config / CD Drives, and saw that my CD/DVD drive, while listed, wasn't selected. So I selected it. This caused things to break, and I don't know how to fix 'em... I'll explain in a moment.
2> Before I get too far off the topic, exactly what is DMA, and how do you set it up?
Duh. The answer is YAST -> Hardware Config -> DMA mode. Sometimes you need to use a flashing billboard to get my attention, it seems. *Sigh*
Okay. Back to my new problem. Now the CD-RW/DVD (combo) drive works as a CD-ROM only. Well, probably a CD-RW as well, but I havn't tested it out yet. And it reads DVDs. But when a DVD is in the drive, I no longer see the nifty CD-Recordable icon change to read "DVD" -- which implies that this is a system problem. When I go into Xine to try to play the DVD, it can't find /dev/dvd. Until now, I have had no problem accessing the DVDs through xine. (Well, not completely true, I was getting very jerky feedback, which is what caused me to seach the archives and find the above message from a few days ago.)
So I go back in remove it. Now I've lost the entire drive -- Linux can't see it at all! It appears that some bizzare half-setting is the correct setting for my CD/DVD drive, but I only have "Add" and "Remove" as options. I don't see a way to manually edit things. (For that matter, I'm not sure what they should be set to... But I am willing to play around and guess...)
I'm running SuSE 9.0 on a fresh install, and have loaded the patches available from the website. I've removed xine from the system, and loaded a non-crippled version that was working smoothly (aside from the aforementioned problem).
I'm at a loss here. Any ideas/suggestions/thoughts on how to get my DVD functionallity back?
Since then I've done more tinkering... I figured that if I removed and reinstalled the CD/DVD drive, it should work right, yes? Nope. YAST is smart enough to see the drive gone (when it's not plugged in). I saved those settings anyway. Just in case. Reconnect the CD/DVD, and I'm back to square one. So I did it *again* only this time shutting off YASTs "integration" of the CD-ROM to my desktop. Maybe some setting was kept... And the same results. So I'm finally stumped. Any pointers / suggestions / comments / flashing billboards / etc out there? Krikket
On Saturday 15 November 2003 04:22, Krikket wrote: <snip>
I'm at a loss here. Any ideas/suggestions/thoughts on how to get my DVD functionallity back?
Thanks in advance!
Krikket
If you are using a combo drive emulating a scsi drive, the device will be set as /drv/srX, where X=0,1 or another integer. On a Toshiba laptop which has a combo drive, /dev/dvd was set up a symbolic link pointing to the /dev/srX device. For example, assume that the combo drive is set to /dev/sr0. This can be checked by running the "Hardware Information" icon in YaST2. Run the following command on a shell command line : ln -s /dev/sr0 /dev/dvd After this the software dvd players should recognise the drive and play dvd. This solution worked on the PC here. LW999
On Sat, 15 Nov 2003, LinuxWorld999 wrote:
On Saturday 15 November 2003 04:22, Krikket wrote: <snip>
I'm at a loss here. Any ideas/suggestions/thoughts on how to get my DVD functionallity back?
Thanks in advance!
Krikket
If you are using a combo drive emulating a scsi drive, the device will be set as /drv/srX, where X=0,1 or another integer. On a Toshiba laptop which has a combo drive, /dev/dvd was set up a symbolic link pointing to the /dev/srX device.
For example, assume that the combo drive is set to /dev/sr0. This can be checked by running the "Hardware Information" icon in YaST2. Run the following command on a shell command line :
ln -s /dev/sr0 /dev/dvd
After this the software dvd players should recognise the drive and play dvd. This solution worked on the PC here.
It worked. Will I need to do this after every login, or need to place it in a global .config or .profile somewhere? Or is that all that needs to be done? I was getting all prepared to email you back and say, "Nope. Not it. I should have said earlier, I have a Memorex drive hooked up via IDE." Then I thought better of it, and checked anyway. Even though I was *completely* certain there's no SCSI anywhere in my system. It *does* emulate a SCSI drive after all... That was the last thing I was expecting! I still don't get the nifty words "DVD" appearing on the icon for the CD-R when a DVD is in the drive, but in all honesty, I don't care about that. And now, I have another minor question, that's related to the save drive (but this time in RW function)... Does anyone know how to shut off the "feature" that tells K3b to run anytime a blank CD is placed into the drive? Thanks again! Krikket
On Saturday 15 November 2003 11:05, Krikket wrote:
On Sat, 15 Nov 2003, LinuxWorld999 wrote: <snip>
For example, assume that the combo drive is set to /dev/sr0. This can be checked by running the "Hardware Information" icon in YaST2. Run the following command on a shell command line :
ln -s /dev/sr0 /dev/dvd
After this the software dvd players should recognise the drive and play dvd. This solution worked on the PC here.
It worked. Will I need to do this after every login, or need to place it in a global .config or .profile somewhere? Or is that all that needs to be done?
The link can should be created as user "root" and should be permanent. There is no need to amend any other setting.
I was getting all prepared to email you back and say, "Nope. Not it. I should have said earlier, I have a Memorex drive hooked up via IDE."
Then I thought better of it, and checked anyway. Even though I was *completely* certain there's no SCSI anywhere in my system.
It *does* emulate a SCSI drive after all... That was the last thing I was expecting!
<snip> Regards. LW999
On Saturday 15 November 2003 11:05, Krikket wrote:
On Sat, 15 Nov 2003, LinuxWorld999 wrote:
On Saturday 15 November 2003 04:22, Krikket wrote: <snip>
I'm at a loss here. Any ideas/suggestions/thoughts on how to get my DVD functionallity back?
Thanks in advance!
Krikket
If you are using a combo drive emulating a scsi drive, the device will be set as /drv/srX, where X=0,1 or another integer. On a Toshiba laptop which has a combo drive, /dev/dvd was set up a symbolic link pointing to the /dev/srX device.
For example, assume that the combo drive is set to /dev/sr0. This can be checked by running the "Hardware Information" icon in YaST2. Run the following command on a shell command line :
ln -s /dev/sr0 /dev/dvd
<snip>
The symbolic link above is necessary, in my experience, if the DVD drive is setup as anything other than "/dev/dvd" by SuSE. On the desktop PC here, the DVD drive is setup as "/dev/hdb". The symbolic link had to setup as shown below to play DVDs. ln -s /dev/hdb /dev/dvd In the command above replace /dev/hdb with whatever device the DVD drive is allocated by SuSE. This information is available under Yast as explained above. Regards. LW999
I'm having to problems with these programs... (I'm using the version of
K3b abd kscd that came with SuSE 9.0, on a freshly installed dual boot
system (W98SE). Even W98SE was a fresh install...)
First, the one that happens ith both of them -- for some truly annoying
reason, whenever I put a blank CD in the drive, K3b starts up. And
whenever a blank CD is put in the drive, kscd starts up.
Anyone know how to stop this unwanted behavior? I always did hate that
aspect of Windows, and I thought I would be free of it by switching to
Linux...
Second problem, I used K3b succesfully to copy a couple of data CDs. All
well and good so far. Since that point (and with no changes to anything,
I only hit the "Copy" and "Start CD Copy" buttons) I've been getting:
Starting reading...
cdrao returned an unknown error (code 1).
Operation not permitted.
Please send me an email with the last output
(At first, this happened most of the way through the copy, then the
middle, and now the first thing, before it get's anywhere. Cloning a CD
has the same problem.)
And the debugger log; (Errors are hand marked with > at the begining)
System
-----------------------
K3b Version: 0.10
KDE Version: 3.1.4
QT Version: 3.2.1
cdrdao
-----------------------
Cdrdao version 1.1.7-suse - (C) Andreas Mueller
cmd finished after 0.000s timeout 20s ERROR: Inquiry command failed on 'ATAPI:/dev/hdc'. ATAPI:/dev/hdc: Rev: Using driver: Generic SCSI-3/MMC - Version 2.0 (options 0x0000) Reading toc and track data... Track Mode Flags Start Length
1 AUDIO 2 00:00:01( 1) 30:22:03(136653) 2 AUDIO 2 30:22:04(136654) 29:42:49(133699) Leadout AUDIO 2 60:04:53(270353) Raw P-W sub-channel reading (audio track) is supported.
ERROR: Cannot open "/tmp/kde-krikket/k3b_image.img/k3b_0.img" for writing: No such file or directory
cdrdao comand: ----------------------- /usr/bin/cdrdao read-cd --device ATAPI:/dev/hdc --driver generic-mmc --paranoia-mode 3 -n -v 2 --eject --remote 22 --datafile /tmp/kde-krikket/k3b_image.img/k3b_0.img /tmp/kde-krikket/k3b_image.img/k3b_0.toc And the file ends there. Any thoughts/comments/suggestions? Thanks again, Krikket
On Saturday 15 November 2003 03:58 pm, Krikket wrote:
I'm having to problems with these programs... (I'm using the version of K3b abd kscd that came with SuSE 9.0, on a freshly installed dual boot system (W98SE). Even W98SE was a fresh install...)
First, the one that happens ith both of them -- for some truly annoying reason, whenever I put a blank CD in the drive, K3b starts up. And whenever a blank CD is put in the drive, kscd starts up.
Anyone know how to stop this unwanted behavior? I always did hate that aspect of Windows, and I thought I would be free of it by switching to Linux... ================= Krikket, Unless SuSE has changed something in 9.0 that I am not aware of yet, check your /etc/fstab for the cd drives and the specs. Here is a line from mine in 8.2 for a cdrom drive: /dev/cdrom /media/cdrom auto ro,noauto,user,exec 0 0
Notice the "noauto" part? If you have just "auto" there, then edit the file to make the change. I believe that is where you'll find the automounting is coming from. -------------------------
Second problem, I used K3b succesfully to copy a couple of data CDs. All well and good so far. Since that point (and with no changes to anything, I only hit the "Copy" and "Start CD Copy" buttons) I've been getting: [...] (At first, this happened most of the way through the copy, then the middle, and now the first thing, before it get's anywhere. Cloning a CD has the same problem.) [...] Any thoughts/comments/suggestions?
Thanks again,
Krikket ====================
The second problem could stem from your settings, either for your cdrom or in k3b for your drives. To use cdrdao, both drives have to emulate scsi and quite likely only your cdrw is setup for that. The best thing to do is when making a copy is use only one drive. Let the process copy an image to the hard drive, then write from the hd to the cdr. Trying to copy from one drive to another on an IDE chain is haphazard and likely to produce more coasters than good copies. That's not to say it can't be done, as I have and probably many others here have as well, but it's still not a good idea with IDE. Another program that doesn't use cdrdao for copying is XCDroast. It will use cdrecord for copying and will allow cd to cd copying. You might want to try that too. Lee -- --- KMail v1.5.4 --- SuSE Linux Pro v8.2 --- Registered Linux User #225206 On any other day, that might seem strange...
On Sat, 15 Nov 2003, BandiPat wrote:
Unless SuSE has changed something in 9.0 that I am not aware of yet, check your /etc/fstab for the cd drives and the specs. Here is a line from mine in 8.2 for a cdrom drive: /dev/cdrom /media/cdrom auto ro,noauto,user,exec 0 0
Notice the "noauto" part? If you have just "auto" there, then edit the file to make the change. I believe that is where you'll find the automounting is coming from.
Actually, I like the auto mounting, and have even installed the automounting software. But this is going a step further than just mounting -- it's starting software. It's that last step (starting of software) that I want to stop. I suppose it may mean that I need to d/l and install another copy of the programs...
-------------------------
Second problem, I used K3b succesfully to copy a couple of data CDs. All well and good so far. Since that point (and with no changes to anything, I only hit the "Copy" and "Start CD Copy" buttons) I've been getting: [...] (At first, this happened most of the way through the copy, then the middle, and now the first thing, before it get's anywhere. Cloning a CD has the same problem.) [...] Any thoughts/comments/suggestions?
Thanks again,
Krikket ====================
The second problem could stem from your settings, either for your cdrom or in k3b for your drives. To use cdrdao, both drives have to emulate scsi and quite likely only your cdrw is setup for that. The best thing to do is when making a copy is use only one drive. Let the process copy an image to the hard drive, then write from the hd to the cdr. Trying to copy from one drive to another on an IDE chain is haphazard and likely to produce more coasters than good copies. That's not to say it can't be done, as I have and probably many others here have as well, but it's still not a good idea with IDE.
Another program that doesn't use cdrdao for copying is XCDroast. It will use cdrecord for copying and will allow cd to cd copying. You might want to try that too.
Yeah, I've heard of that problem before. Although, when I was running a Windoze machine (and Nero software), I made 50+ CD's with that combination, with 0 coasters. So I know it doesn't *have* to be that way. Still, I'll give XCDRoast a try and see what happens. What I find really curious, is that it was working at first, and then stopped after 2 CDs, with the problem getting more severe the more CDs I attemped to copy. At least it never got around to trying to burn them, so I didn't create coasters in the process. (Although I did set the blanks aside, just in case I'm wrong about that...) Krikket
On Saturday 15 November 2003 09:41 pm, Krikket wrote:
Actually, I like the auto mounting, and have even installed the automounting software. But this is going a step further than just mounting -- it's starting software. It's that last step (starting of software) that I want to stop.
I suppose it may mean that I need to d/l and install another copy of the programs...
-------------------------
Actually that may mean that there is a setting in the KDE control center or YaST2 that you can change to stop the autoplaying of music cds or starting k3b for a blank cdr. There is no real need for these to be automounted anyway as KSCD will play an audio cd without mounting and k3b doesn't need a cdr mounted. ==============
Yeah, I've heard of that problem before. Although, when I was running a Windoze machine (and Nero software), I made 50+ CD's with that combination, with 0 coasters. So I know it doesn't *have* to be that way.
Still, I'll give XCDRoast a try and see what happens.
What I find really curious, is that it was working at first, and then stopped after 2 CDs, with the problem getting more severe the more CDs I attemped to copy. At least it never got around to trying to burn them, so I didn't create coasters in the process. (Although I did set the blanks aside, just in case I'm wrong about that...)
Krikket =================
What you might not be aware of is that Nero was doing the same thing for safety purposes. You just didn't see it doing the copy to hard drive and write to cdr. As I mentioned, you can do it and XCDRoast will do it, so no, it doesn't have to be that way, but it's always iffy on IDE. SCSI drives are no problem, but few of us use SCSI cd drives these days. :o) Lee -- --- KMail v1.5.4 --- SuSE Linux Pro v8.2 --- Registered Linux User #225206 On any other day, that might seem strange...
On Saturday 15 November 2003 03:58 pm, Krikket wrote:
I'm having to problems with these programs... (I'm using the version of K3b abd kscd that came with SuSE 9.0, on a freshly installed dual boot system (W98SE). Even W98SE was a fresh install...)
First, the one that happens ith both of them -- for some truly annoying reason, whenever I put a blank CD in the drive, K3b starts up. And whenever a blank CD is put in the drive, kscd starts up.
Anyone know how to stop this unwanted behavior? I always did hate that aspect of Windows, and I thought I would be free of it by switching to Linux...
Thanks again for all of the responces people! The answer that worked for me for this particular problem was to uninstall K3b, and install a version that I downloaded off the net. Also, I ended up decided to go with xcdroast. K3b had some oddball config things going on, that I wasn't able to quickly figure out. Xcdroast was much more user-friendly in that regard. (Although, I would prefer to use a program where I can just put the cds in the drives, hit one button, walk away from the computer, and come back to find a freshly burnt CD. As is, I now have to be present for the step where I switch from reading to writing. On the plus side, making multiple copies is simpler.) Krikket
participants (3)
-
BandiPat -
Krikket -
LinuxWorld999