SlackwareThis Forum is for the discussion of Slackware 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 am having a heck of a time trying to get a cdrom and cdrw working on my new Slack installation. I have been pouring over posts and trying to get things configured right to no avail for some time now. Before I started fooling around with this, I was able to use my cdrom, however, with my tinkering I have messed things up. Any thoughts or ideas would be greatly appreciated.
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
message = /boot/boot_message.txt
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# VESA framebuffer console @ 1024x768x256
vga = 773
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA fBefore I started fooling around with this, I was able to use my cdrom, however, with my tinkering I have messed things up.ramebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# DOS bootable partition config begins
other = /dev/hda1
label = DOS
table = /dev/hda
# DOS bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hdb3
label = Linux
read-only
#append="hdc=ide-scsi"
append="hdd=ide-scsi"
# Linux bootable partition config ends
You need to uncomment the append line you have commented (mine's up near the top, rather than the bottom - doesn't seem to matter on one of your devices, so I guess it's fine) and I'd make a symlink 'dev/cdrw' - or something like - pointing at one 'scsi' device and make sure /dev/cdrom points to the other one. The question is (and I've never understood why) what cdrecord is calling your stuff. Some people have 'scd' but mine are 'sr'. However, you'll need to reboot (ugh, shades of Windows) to make the append line take effect (I think) and when you do that, you can 'dmesg | grep -i hd' and it'll show what your devices are being translated to. That should let you hook up the links and that should do it. Then you have to tell all your apps which ones to use. If I'm wrong or being an idiot, somebody correct me.
Great post, btw.
-- Oh, and current cdrtools apparently don't require scsi-emulation anymore, though I still have mine set up that way. Don't know which versions are different.
Hi digiot.... thanks for the response. I am curious about my fstab. Should this be uncommented as well:
#/dev/scd1 /mnt/cdrw iso9660 noauto,user, ro 0 0
As well, would the symlink to the cdrw be as follows:
ln -s scd1 cdwr
Please forgive me. I am a recent convert from Mandrake... essentially because I didn't find myself learning anything. I have picked up more knowledge in the past week cruising this forum and tinkering with Slack than I did in the previous year with Mandrake. Just as a comment, the speed differential on my system from Mandrake to Slack is incredible... I shall not be returning.
Yeah, I meant to say that the fstab line should be uncommented.
But uh oh. Did you check what was in /dev with an ls -l? The symlink thing was an example. I haven't seen that with mount before but I'm guessing maybe you pointed your new cdrw symlink at an old symlink rather than the actual device file or something and mount doesn't like it. You don't want to be overwriting symlinks or pointing them to other symlinks.
? This looks to be the second or third time I've been completely stumped today. Aside from the cd's actually *working* or not , I can't imagine why mount would have a problem with that setup.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.