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.
i posted this in the newbie forum but no one replied so i'm hoping this might be a more appropriate forum.
i have a cd-rw drive (as well as a separate cdrom drive) that was working fine until just the other day. I was using xcdroast which i had just installed. I was performing a dummy burn and the app hung and i ended up killing it. now my cd-rw drive has "dissapeared" (my cdrom drive is still fine however). the line from my fstab has dissapeared and everytime i add it back it gets erased when i reboot, along with the mnt/cdrw directory and the symbolic link in the /dev/ directory.
when i run: cdrecord -scanbus i get the following:
Cdrecord 2.0 (i686-pc-linux-gnu) Copyright (C) 1995-2002 J�g Schilling
cdrecord: No such file or directory. Cannot open '/dev/pg*'. Cannot open SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root.
cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
and running dmesg only lists my cdrom drive, not my cd-rw.
I hope that is enough info. i am running redhat 9, kernel 2.4.20-8. my fstab looks like this right now:
first, check your hardware is reporting correctly in whatever hardware manager you use - it's possible that something physical happened during that last test burn, causing the burning software to hang.
my setup is as follows - how much different is yours ?
append="quiet devfs=mount hdc=ide-scsi"
in /etc/lilo.conf
my symlinks for the /dev entries for my writer are:
[root@Petrata caysho]# ls /dev/cdrw -l
lr-xr-xr-x 1 root root 6 Oct 11 01:03 /dev/cdrw -> cdrom1
[root@Petrata caysho]# ls /dev/cdrom1 -l
lr-xr-xr-x 1 root root 13 Oct 10 17:03 /dev/cdrom1 -> cdroms/cdrom1
[root@Petrata caysho]# ls /dev/cdroms/cdrom1 -l
lr-xr-xr-x 1 root root 34 Jan 1 1970 /dev/cdroms/cdrom1 -> ../scsi/host0/bus0/target2/lun0/cd
[root@Petrata caysho]# ls /dev/scd0 -l
lr-xr-xr-x 1 root root 31 Oct 10 17:03 /dev/scd0 -> scsi/host0/bus0/target2/lun0/cd
(this is probably not the cleanest symlinking)
and my fstab entry is:
[root@Petrata caysho]# cat /etc/fstab | grep cdrw
/dev/scd0 /mnt/cdrw auto user,iocharset=iso8859-1,codepage=850,ro,umask=0 0 0
aside all this, what is listed in the kernal message log (/var/log/messages) ?
assuming most things are in order, maybe there are some references in there during the boot up.
I'm guessing that kudzu is the equivalent to SuperMount in Mandrake (which sucks in v9.0 - did a test burn by accident and then went to access the disk in the burner; SuperMount spun it up and down for 20 minutes before giving up)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.