re: help w/ cdrw recog + few observations from a newbie
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.
My problem is that I don't know what my cdrw is in /dev, so I cannot mount it.
It's ludicrous to have to wipe out a hdd and reinstall just so I can have a cdrw. I think it sucks, and certainly is a drawback for linux (hopefully newer versions have fixed this snafu).
The instruction in grub;
kernel /vmlinuz-2.4.18-3 ro root=/dev/hda2 hdc=ide-scsi
is telling the system to use scsi emulation for the cdrw so hdc is no longer /dev/hdc but probably /dev/scd0.
If you check /var/log/syslog it will probably tell you what it device name it has allocated. You should then amend your fstab so that it mounts at boot time. Mine looks like this;
/dev/scd0 /cdrom auto ro,noauto,user,exec 0 0
and put a # next to /dev/cdrom
Have a look at your syslog as root. There will be an entry for your cd along with the identification of the cd drive type. The entries under /etc are for creating the log during boot. If you only have one cdrw in your system then it's likely it is configured as /dev/scd0. You can also do from root cdrecord -scanbus which will return a value of 0,0,0 for the cd if it's /dev/scd0. You can then create the entry for fstab as above.
Your comments are quite interesting because if you installed a cdrw under M$ you likely have to buy software to write to cd's whereas linux is already capable from the command line. I seldom use a gui interface to write cd's prefering to use cdrecord.
Distribution: RH 6.2, Gen2, Knoppix,arch, bodhi, studio, suse, mint
Posts: 3,304
Rep:
you don't need an entry in fstab to mount something.
mount /dev/scd0 <mountpoint> such as
mount /dev/scd0 /mnt/cdrom
cd /mnt/cdrom
ls
umount /mnt/cdrom
for your fstab entry, change the /dev/hdc to /dev/scd0
Distribution: RH 6.2, Gen2, Knoppix,arch, bodhi, studio, suse, mint
Posts: 3,304
Rep:
Quote:
Originally posted by ergo_sum Sorry, I got a little carried away.
re: fstab:
should I amend /dev/cdrom to /dev/scd0?
ergo_sum
no, just replace. or you can leave it the same, if you do the following
you can use /dev/cdrom as the device if you make a symbolic link
in /dev to /dev/scd0
rm /dev/cdrom
ln -s /dev/scd0 /dev/cdrom
then when you refer to /dev/cdrom, you will be referring to /dev/scd0
when a cdburning program asks you what the device is for burning, you
will still usually have to put 0,0,0 as cdrecord refers to scsi devices this
way. the command line would actually take dev=0,0,0
Well that'd work if I'm not planning on adding a cdrom. I've got the burner, but w/o the cdrom then I'd be limiting myself. I'd like to add a cdrom.
So, with all of that, what do I do?
ergo_sum
PS: I've managed to 'mount' and 'eject', and I've placed a cd on the tray. How do I get the tray to close?
Distribution: RH 6.2, Gen2, Knoppix,arch, bodhi, studio, suse, mint
Posts: 3,304
Rep:
eject -t
your current /dev/cdrom is pointing at /dev/hdc isn't it.
if you add a cdrom drive as a slave to the burner, it will be /dev/hdd.
/dev/cdrom as it is would be useless.
I've got the burner, that's it. I DID have a cdrom, but it's disconnected. It started scatching all my cd's, so I installed the cdrw and disconnected the cdrom.
Distribution: RH 6.2, Gen2, Knoppix,arch, bodhi, studio, suse, mint
Posts: 3,304
Rep:
the only thing special abou the /dev/cdrom link is that lots of software uses
that link for the cdrom drive. it doesn't matter whether it's a burner or dvd
or cdrom drive. there's nothing special about the mount points name either.
you can make it whatever you want. you can have it where ever you wish
also.
the fstab entries are for setting defaults. if it is set up correctly, you can just
type mount /dev/cdrom or mount /mnt/cdrom and mount will take the rest
from the matching line in fstab.
Maybe either of you can help me. I just (re)installed a version of Knoppix, WFTL Knoppix. The previous version absolutely refused to recognize my NIC, even though it would do so when run entirely from the CD.
I too have a CDRW that refuses to mount. My ect/fstab reads as follows:
Nov 4 20:41:41 main_box kernel: SCSI subsystem driver Revision: 1.00
Nov 4 20:41:41 main_box kernel: scsi0 : SCSI host adapter emulation for IDE ATAPI devices
This seems to refer to the cdrw being set up as scsi emulation, i.e. scsi0 instead of cdrom
What do I need to type in bash to mount my cdrw? What do I need to change in /ect/fstab to mount it automatically when I log in, and keep it on the desktop?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.