I replaced my CD-ROM writer with a DVD-ROM writer, and now automounting of either CD-ROMs or DVD-ROMs no longer takes place. Instead, the CD-Creator gets started up, as it does for a blank writable CD-ROM.
I can force a mount by hand, which works. All the files show up and the disc is usable. However, the label on the disc is not recognized, and the mounted icon on the desktop simply shows it as CDROM.
I replaced the DVD writer with a Memorex 48x CD-ROM drive I have lying around, and the auto mount and label recognition both work. Putting the DVD writer back in made the symptoms return. Kudzu didn't report anything about the change whatever.
Hardware: Compaq Presario 2.7GHz Celeron (i386 build) Sony DRU-V200A[-BR] (shows symptoms) Memorex CD-482E (does not show symptoms) Software: $ uname -a Linux Presario-1 2.6.10-1.771_FC2 #1 Mon Mar 28 00:50:14 EST 2005 i686 i686 i386 GNU/Linux Gnome
I am aware that FC2 is very old, no need to comment.
I checked
Red Hat->Preferences->CD and DVD
and under Data Discs both "Mount discs when inserted" and "Start auto run programs when present" are checked.
Someone please advise me on how to proceed to get this drive to work for me the way I would like.
Mike
On Thu, 2008-08-21 at 18:18 -0500, Mike McCarty wrote:
I replaced my CD-ROM writer with a DVD-ROM writer, and now automounting of either CD-ROMs or DVD-ROMs no longer takes place. Instead, the CD-Creator gets started up, as it does for a blank writable CD-ROM.
I can force a mount by hand, which works. All the files show up and the disc is usable. However, the label on the disc is not recognized, and the mounted icon on the desktop simply shows it as CDROM.
I replaced the DVD writer with a Memorex 48x CD-ROM drive I have lying around, and the auto mount and label recognition both work. Putting the DVD writer back in made the symptoms return. Kudzu didn't report anything about the change whatever.
Hardware: Compaq Presario 2.7GHz Celeron (i386 build) Sony DRU-V200A[-BR] (shows symptoms) Memorex CD-482E (does not show symptoms) Software: $ uname -a Linux Presario-1 2.6.10-1.771_FC2 #1 Mon Mar 28 00:50:14 EST 2005 i686 i686 i386 GNU/Linux Gnome
I am aware that FC2 is very old, no need to comment.
I checked
Red Hat->Preferences->CD and DVD
and under Data Discs both "Mount discs when inserted" and "Start auto run programs when present" are checked.
Someone please advise me on how to proceed to get this drive to work for me the way I would like.
Mike
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);} Oppose globalization and One World Governments like the UN. This message made from 100% recycled bits. You have found the bank of Larn. I speak only for myself, and I am unanimous in that!
Same problem here...
On Thu, 21 Aug 2008 18:18:11 -0500 Mike McCarty Mike.McCarty@sbcglobal.net wrote:
Someone please advise me on how to proceed to get this drive to work for me the way I would like.
Well, FC2 probably predates udev, but I know when I replaced a DVD drive I found a rules.d/70-persistent-cd.rules file which was apparently generated on first boot. I had to modify the file to remove the pointers to the old drive and make the new drive show up as the 1st device.
Wouldn't surprise me if there is something similar stashed under /etc somewhere in FC2.
Tom Horsley wrote:
On Thu, 21 Aug 2008 18:18:11 -0500 Mike McCarty Mike.McCarty@sbcglobal.net wrote:
Someone please advise me on how to proceed to get this drive to work for me the way I would like.
Well, FC2 probably predates udev, but I know when I replaced a DVD drive I found a rules.d/70-persistent-cd.rules file which was apparently generated on first boot. I had to modify the file to remove the pointers to the old drive and make the new drive show up as the 1st device.
Wouldn't surprise me if there is something similar stashed under /etc somewhere in FC2.
Your suggestion makes sense, except that the Memorex drive is not the original, either. I don't have the original drive here for test; it's at a friend's house. I installed both the Sony and the Memorex on the same cable etc.; physically the installations are identical.
After a manual mount, I have...
/dev/hdc on /mnt/cdrom type iso9660 (ro,nosuid,nodev,user=jmccarty)
My /etc/fstab entry looks like this:
/dev/cdrom /mnt/cdrom udf,iso9660 noauto,owner,kudzu,ro 0 0
[spaces removed for clarity of reading]
I wonder if this is different? It shows /dev/hdc mounted, not /dev/cdrom.
$ ls -l /dev/cdrom lrwxrwxrwx 1 root root 8 Aug 21 18:08 /dev/cdrom -> /dev/hdc
Maybe I should look at the /dev/cdrom device when it's working.
I don't run udev...
$ man udev No manual entry for udev
I had considered using udev, but after I read the documentation by the author carefully, I decided that the solution he proposed was worse than the problems I experienced, so I haven't pursued it further.
Anyway, thanks for the reply!
Mike
Mike McCarty wrote:
After a manual mount, I have...
/dev/hdc on /mnt/cdrom type iso9660 (ro,nosuid,nodev,user=jmccarty)
My /etc/fstab entry looks like this:
/dev/cdrom /mnt/cdrom udf,iso9660 noauto,owner,kudzu,ro 0 0
[spaces removed for clarity of reading]
I wonder if this is different? It shows /dev/hdc mounted, not /dev/cdrom.
$ ls -l /dev/cdrom lrwxrwxrwx 1 root root 8 Aug 21 18:08 /dev/cdrom -> /dev/hdc
Maybe I should look at the /dev/cdrom device when it's working.
You may want to run ls -l /dev/cdrom to see where it points to. If this was the only device on the secondary IDE controller, and you are not using cable select, then it is possible that the old drive was jumpered as a slave drive, and the new on is jumpered as either master or cable select. That would mess up the cdrom symlink.
Mikkel
Mikkel L. Ellertson wrote:
Mike McCarty wrote:
After a manual mount, I have...
/dev/hdc on /mnt/cdrom type iso9660 (ro,nosuid,nodev,user=jmccarty)
My /etc/fstab entry looks like this:
/dev/cdrom /mnt/cdrom udf,iso9660 noauto,owner,kudzu,ro 0 0
[spaces removed for clarity of reading]
I wonder if this is different? It shows /dev/hdc mounted, not /dev/cdrom.
$ ls -l /dev/cdrom lrwxrwxrwx 1 root root 8 Aug 21 18:08 /dev/cdrom -> /dev/hdc
Maybe I should look at the /dev/cdrom device when it's working.
You may want to run ls -l /dev/cdrom to see where it points to. If
Yes, that's what I did just up above. I guess you missed that. Anyway, here's what it shows with the Memorex (which works)
$ ls -l /dev/cdrom lrwxrwxrwx 1 root root 8 Aug 21 19:02 /dev/cdrom -> /dev/hdd
The drive which isn't working the way I want is jumpered as Master. The drive is on the end, however, so even if jumpered as CS it would be Master. Well, I just pulled it, and it's jumpered as Slave. That may well be the whole problem. Time for another reboot and check.
this was the only device on the secondary IDE controller, and you are not using cable select, then it is possible that the old drive was jumpered as a slave drive, and the new on is jumpered as either master or cable select. That would mess up the cdrom symlink.
Thanks for the idea!
Mike
Mikkel L. Ellertson wrote:
You may want to run ls -l /dev/cdrom to see where it points to. If this was the only device on the secondary IDE controller, and you are not using cable select, then it is possible that the old drive was jumpered as a slave drive, and the new on is jumpered as either master or cable select. That would mess up the cdrom symlink.
To recap: the DVD drive which does not work was jumpered as Master, while the CD drive which does work was jumpered as Slave.
Ok, I rejumpered the DVD drive to be Slave, and installed, and the symptoms are as before, though the /dev/cdrom entry now corresponds to the one which works with the CD drive. I also rejumpered the CD drive as master, and reinstalled it, and noted that the /dev/cdrom entry changed to match the one which does not work with the DVD drive, and yet it works properly with the CD reader.
So, while a good idea to try, it is not the answer. The CD drive works as either Master or Slave, while the DVD drive works as neither Master nor Slave. The symptoms follow the drive. Do I perhaps need to make a device /dev/dvdrom? I thought the protocols were identical.
Mike
Mikkel L. Ellertson wrote:
You may want to run ls -l /dev/cdrom to see where it points to. If this was the only device on the secondary IDE controller, and you are not using cable select, then it is possible that the old drive was jumpered as a slave drive, and the new on is jumpered as either master or cable select. That would mess up the cdrom symlink.
Ok, I put both of them on the cable, jumpered as CS, with the CD on the Master, and the DVD on the slave location. I rebooted, and got an entry in my fstab...
/dev/cdrom /mnt/cdrom udf,iso9660 noauto,owner,kudzu,ro 0 0 /dev/cdrom1 /mnt/cdrom1 udf,iso9660 noauto,owner,kudzu,ro 0 0
[spaces edited]
Also,
$ ls -l /dev/cd* lrwxrwxrwx 1 root root 8 Aug 21 19:26 /dev/cdrom -> /dev/hdc lrwxrwxrwx 1 root root 8 Aug 21 19:44 /dev/cdrom1 -> /dev/hdd brw-rw---- 1 root disk 15, 0 Feb 23 2004 /dev/cdu31a brw-rw---- 1 root disk 24, 0 Feb 23 2004 /dev/cdu535 lrwxrwxrwx 1 root root 8 Aug 21 19:44 /dev/cdwriter -> /dev/hdd
The CD drive works as expected. The DVD does not. When I put a written CD into the CD drive, it mounts, and shows the label. When I put the same disc into the DVD drive, it brings up the CD Creator box, like it was blank. Closing that, and doing a mount causes the disc to mount and be usable, but the label is not noticed, it mounts just as cdrom1.
Mike
On Thu, 2008-08-21 at 18:18 -0500, Mike McCarty wrote:
I replaced my CD-ROM writer with a DVD-ROM writer, and now automounting of either CD-ROMs or DVD-ROMs no longer takes place. Instead, the CD-Creator gets started up, as it does for a blank writable CD-ROM.
Bad drive? Does it work anywhere else?
Tim wrote:
On Thu, 2008-08-21 at 18:18 -0500, Mike McCarty wrote:
I replaced my CD-ROM writer with a DVD-ROM writer, and now automounting of either CD-ROMs or DVD-ROMs no longer takes place. Instead, the CD-Creator gets started up, as it does for a blank writable CD-ROM.
Bad drive? Does it work anywhere else?
Well, that's what I've been wondering. It mounts. It writes CDs and DVDs. The CDs look ok on another machine. The DVDs I dunno. I can mount them and look around using the same drive. I don't have another machine with Linux to test with, however.
Mike
Mike McCarty wrote:
The CD drive works as expected. The DVD does not. When I put a written CD into the CD drive, it mounts, and shows the label. When I put the same disc into the DVD drive, it brings up the CD Creator box, like it was blank. Closing that, and doing a mount causes the disc to mount and be usable, but the label is not noticed, it mounts just as cdrom1.
I didn't run FC2, so I am nt sure about this. Could it be that the DVD-ROM drive is reporting that there is a disk in the drive, but taking too long to report the rest of the information, so that the system is assuming that it is a blank disk? (Or reporting error like it is trying to read a blank disk...)
Mikkel
Mikkel L. Ellertson wrote:
Mike McCarty wrote:
The CD drive works as expected. The DVD does not. When I put a written CD into the CD drive, it mounts, and shows the label. When I put the same disc into the DVD drive, it brings up the CD Creator box, like it was blank. Closing that, and doing a mount causes the disc to mount and be usable, but the label is not noticed, it mounts just as cdrom1.
I didn't run FC2, so I am nt sure about this. Could it be that the DVD-ROM drive is reporting that there is a disk in the drive, but taking too long to report the rest of the information, so that the system is assuming that it is a blank disk? (Or reporting error like it is trying to read a blank disk...)
That's a good supposition.
I suppose that's possible. What I really need is to be able to know that others use DVD-ROM drives and don't have this problem. I want to narrow it down to either the DVD-ROM drive itself, settings in FC2, or what. Until I know what the incompatibility is, I can't go about fixing it. I don't want to return the drive, only to have the replacement behave the same way. Perhaps I can put a CD-ROM in there as well, and boot CentOS or similar LiveCD and see what it thinks. If the drive works as expected with CentOS, then perhaps that's the way to go. I really should be using a supported OS anyway.
If it does not work with a LiveCD, then perhaps there actually is a problem with the drive itself.
Thanks for the reply!
Mike
Mikkel L. Ellertson wrote:
Mike McCarty wrote:
The CD drive works as expected. The DVD does not. When I put a written CD into the CD drive, it mounts, and shows the label. When I put the same disc into the DVD drive, it brings up the CD Creator box, like it was blank. Closing that, and doing a mount causes the disc to mount and be usable, but the label is not noticed, it mounts just as cdrom1.
I didn't run FC2, so I am nt sure about this. Could it be that the DVD-ROM drive is reporting that there is a disk in the drive, but taking too long to report the rest of the information, so that the system is assuming that it is a blank disk? (Or reporting error like it is trying to read a blank disk...)
You know, that really is an idea. I wonder how one would configure Gnome (or whatever is waiting) to wait longer.
Mike
Mike McCarty wrote:
Mikkel L. Ellertson wrote:
I didn't run FC2, so I am not sure about this. Could it be that the DVD-ROM drive is reporting that there is a disk in the drive, but taking too long to report the rest of the information, so that the system is assuming that it is a blank disk? (Or reporting error like it is trying to read a blank disk...)
That's a good supposition.
I suppose that's possible. What I really need is to be able to know that others use DVD-ROM drives and don't have this problem. I want to narrow it down to either the DVD-ROM drive itself, settings in FC2, or what. Until I know what the incompatibility is, I can't go about fixing it. I don't want to return the drive, only to have the replacement behave the same way. Perhaps I can put a CD-ROM in there as well, and boot CentOS or similar LiveCD and see what it thinks. If the drive works as expected with CentOS, then perhaps that's the way to go. I really should be using a supported OS anyway.
If it does not work with a LiveCD, then perhaps there actually is a problem with the drive itself.
Thanks for the reply!
Mike
Well, I am running 2 DVD-RW - I forget the brands, but they show up in dmesg as: TSSTcorp CDDVDW SH-S202G DVDRW DRW-5S163
They will both auto-mount CDs and DVDs. But this is with F8, so I do not know if that helps with FC2.
One other thing to keep in mind when testing - some systems will not boot from CD if there are 2 CD/DVD drives in the system at the same time. I think it is getting kind of rare now, but I do run into it once in a while.
I hope this helps...
Mikkel
Mikkel L. Ellertson wrote:
Well, I am running 2 DVD-RW - I forget the brands, but they show up in dmesg as: TSSTcorp CDDVDW SH-S202G DVDRW DRW-5S163
dmesg shows:
[...] hdc: SONY DVD RW DRU-V200A, ATAPI CD/DVD-ROM drive [...] hdc: ATAPI 48X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache, UDMA(33) Uniform CD-ROM driver Revision: 3.20 [...]
They will both auto-mount CDs and DVDs. But this is with F8, so I do not know if that helps with FC2.
One other thing to keep in mind when testing - some systems will not boot from CD if there are 2 CD/DVD drives in the system at the same time. I think it is getting kind of rare now, but I do run into it once in a while.
Worth bearing in mind. My BIOS looks pretty savvy, but I'll watch for that.
I hope this helps...
Well, you're being helpful, anyway. Thanks!
Mike