Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi guys,
I removed the faulty line in my fstab file, replacing it with nothing.
I deleted the 70-persistent-cd.rules file (as instructed) and rebooted. The DVD-RW is still not recognized. However, I am able to boot using a live cd from the DVD-RW drive, again showing that there is nothing wrong with the drive itself. The problem is only evident when the Computer is booted into Ubuntu 9.04 (64) then the drive becomes invisible.
This is a copy of my 70-persistent-cd.rules file;
---------------------------------------------------------------
# This file was automatically generated by the /lib/udev/write_cd_rules
# program, run by the cd-aliases-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and set the $GENERATED variable.
Hi guys,
I removed the faulty line in my fstab file, replacing it with nothing.
I deleted the 70-persistent-cd.rules file (as instructed) and rebooted. The DVD-RW is still not recognized. However, I am able to boot using a live cd from the DVD-RW drive, again showing that there is nothing wrong with the drive itself. The problem is only evident when the Computer is booted into Ubuntu 9.04 (64) then the drive becomes invisible.
This is a copy of my 70-persistent-cd.rules file;
---------------------------------------------------------------
# This file was automatically generated by the /lib/udev/write_cd_rules
# program, run by the cd-aliases-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and set the $GENERATED variable.
As you can see Ubuntu 9.04 (64) is just not picking the drive up and recording it in the file.
gael.
And carrying on from there, here is a copy of my fstab file now;
# /etc/fstab: static file system information.
#
# Use 'vol_id --uuid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# / was on /dev/sda5 during installation
UUID=7b97ab2c-9d9a-48ca-8179-a9e9ded21578 / ext3 relatime,errors=remount-ro 0 1
# swap was on /dev/sda6 during installation
UUID=a6d61985-7f20-4aa0-8ba9-2f2b3076260a none swap sw 0 0
/dev/scd0 /media/cdrom udf,iso9660 user,noauto,exec,utf8 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0
I hope all this information helps ...
Thanks,
gael.
Could you check for me which devices are created by udev?
Your fstab contains a line /dev/scd0 - can you check if this exists, also if /dev/cdrom and /dev/dvd exist (they should be symbolic links the real device)
Also, do you have a USB memory stick at all? If you plug that it, does it automatically get mounted on the desktop, or does nothing happen?
If nothing happens with a USB stick, it may be that you don't have a problem with the CD per se, but with the automounter.
To check this out as well, try putting the live cd into the drive after booting (and as you say, nothing will happen). then run the following command
Code:
mount -t iso9660 /dev/scd0 /mnt
Then cd into /mnt and see if it's the live cd
to eject the CD you will have to cd out of /mnt and run
Could you check for me which devices are created by udev?
Your fstab contains a line /dev/scd0 - can you check if this exists, also if /dev/cdrom and /dev/dvd exist (they should be symbolic links the real device)
Also, do you have a USB memory stick at all? If you plug that it, does it automatically get mounted on the desktop, or does nothing happen?
If nothing happens with a USB stick, it may be that you don't have a problem with the CD per se, but with the automounter.
To check this out as well, try putting the live cd into the drive after booting (and as you say, nothing will happen). then run the following command
Code:
mount -t iso9660 /dev/scd0 /mnt
Then cd into /mnt and see if it's the live cd
to eject the CD you will have to cd out of /mnt and run
Code:
umount /mnt
eject /dev/scd0
Try that, see how it goes.
Okay, I did as you suggested and the command told me that the drive was mounted, that is the DVDROM which I have no trouble. The PC has recognized this drive from my upgrade. However, the DVD-RW was not recognizes in the udev file (70-persistent-cd.rules) but now it is
Here is a copy of my file;
# This file was automatically generated by the /lib/udev/write_cd_rules
# program, run by the cd-aliases-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and set the $GENERATED variable.
Right, for some reason I thought you only had a single drive.
OK. Please run the following commands and see what you get:
Code:
dmesg | grep sr
This searches the kernel ring buffer for the text sr. If you have a modern SATA or PATA CD/DVD writer and if the kernel is loading the correct modules, you should get lines looking something like this:
I've edited the lines somewhat from my output, yours will be slightly different (the timestemp, the description) but what is important is that it's using the sr driver. Don't worry that it says scsi CD-ROM.
Then within the /dev directory, I would expect to see the following:
Now within your fstab file, I would not expect to see any entries for the cd-rom drives.
Your entry - /dev/hda0 - is most definately wrong and should be removed. The CD-ROM driver is no longer the old IDE CD-DROM driver (which would give you hda) but is the new ATA CD-ROM driver, which should give you sr1.
I would remove the enties for /dev/scd0 and /dev/hda0 - assuming that those are the entries that you have chosen for your DVD / DVDRW. Once doing that I would reboot and see if the automounting works.
When you put a disk in either drive, Ubuntu should automount it under /media.
If you need to specify the device for the DVD-writer (for dvd writer programs etc) then you should use the device /dev/dvdrw1, although strictly speaking any one of /dev/sr1, /dev/cdrom1, /dev/cdrw1, /dev/dvd1 would do.
If you feel you must have an entry within fstab for your DVD/DVD-RW, (which I do not recommend) then the devices that you should use are /dev/scd0 (or /dev/sr0, /dev/cdrom, /dev/dvd) and /dev/scd1 (or /dev/sr1, /dev/cdrom1, /dev/cdrw1, /dev/dvd1, /dev/dvdrw1, /dev/sr1)
Right, for some reason I thought you only had a single drive.
OK. Please run the following commands and see what you get:
Code:
dmesg | grep sr
This searches the kernel ring buffer for the text sr. If you have a modern SATA or PATA CD/DVD writer and if the kernel is loading the correct modules, you should get lines looking something like this:
I've edited the lines somewhat from my output, yours will be slightly different (the timestemp, the description) but what is important is that it's using the sr driver. Don't worry that it says scsi CD-ROM.
I followed your instructions and the PC produced this entry ... hopefully this will tell you something.
gael.
[QUOTE=gzunk;3720535]Right, for some reason I thought you only had a single drive.
Quote:
Now within your fstab file, I would not expect to see any entries for the cd-rom drives.
Your entry - /dev/hda0 - is most definately wrong and should be removed. The CD-ROM driver is no longer the old IDE CD-DROM driver (which would give you hda) but is the new ATA CD-ROM driver, which should give you sr1.
I would remove the enties for /dev/scd0 and /dev/hda0 - assuming that those are the entries that you have chosen for your DVD / DVDRW. Once doing that I would reboot and see if the automounting works.
Are you saying that I should remove those fstab file entries completely?
OK, your DVD-ROM (GDRH10N) should have the following files associated with it: /dev/dvd and /dev/cdrom. They should both be symbolic links to /dev/sr0
Okay, all of this is a little confusing because I am unaware of the tech phraseology ... could we take it one step at a time please.
You talk of 'symbolic links', unfortunately I have no idea as to what they are. Where and how do I replace what is written into my system with the new figures and numbers that you have written above? Which files do they have to be written into?
(I cannot thank you enough for all the time you are giving, I am very grateful).
The "l" at the start indicates that it's a link, and it tells you what it's pointing to as well - in this case, sr0
Now, if you have two DVD's plugged in, then I would expect udev (which is the part of Linux that automatically creates devices) to detect them and create the appropriate files within the /dev directory, including the symbolic links to make them easier to use.
What I mean by easier to use is that it's easier to remember /dev/dvd rather than /dev/sr0.
How have you got the DVD's plugged in? Are they both ATAPI/IDE devices (i.e. are plugged in via a ribbon cable to the motherboard) Are they SATA devices? (i.e. plugged in using the small SATA connector that you get) or are they USB devices?
To be honest, if you could send me the output of the following commands it would help in trying to track down the problems that you're having:
Code:
ls -l /dev
and
Code:
dmesg
i.e. type something like this:
Code:
ls -l /dev/ > ~/device.txt
and
Code:
dmesg > ~/dmesg.txt
Then attach the two files (device.txt and dmesg.txt) to the message (there's a button called "Manage Attachments" in the additional options when you're posting a reply)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
