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.
hrm, it says it cant open the scsi driver
do you need to add scsi support to your kernel?
also, where do you add the append="hdd=ide-scsi" line to your lilo.config? I added it to the very bottem. didnt think it would matter.
You probably will need to edit you /etc/rc.d/rc.modules file. there is a scsi emulator that you need to use an ide cdwriter. Remove the # sign at the front of the line that says #/sbin/modprobe/ide-scsi You also need to edit the /etc/fstab. You have to add a device such as /dev/sd0 in place of the /dev/hdb because you computer now sees the cdwriter as a scsi drive. Good Luck
If it is not a SCSI CD pay special attention to the portion about relinking the CD and the edits to LILO config. Also, if you don't have the SCSI drivers installed (like me) you'll have to recompile the kernel
If you try k3b, It should find the writer (as long as you have the cd tools installed). I use it and find it the best cd/dvd writing gui. Better than anything windows has to offer. And if you are using the 2.6 kernel you do not need to have scsi emulation.
You provided no information about your configuration. However, this is how I got everything to work on my box. I use Slackware 10.1 and KDE 3.3.2, K3B as my burner package, the 2.4.28 kernel, and I use GRUB as my boot loader.
In GRUB I added the kernel boot option of hdc=ide-scsi. My GRUB boot text looks like this:
title Slackware 10.1 - 2.4.28 - KDE 3.3.2
kernel (hd0,12)/vmlinuz-ide-2.4.28 root=/dev/hda23 ro hdc=ide-scsi vga=3 ide2=noprobe quiet
As mentioned above, you can do something similar if you are using LILO.
Because I still use the 2.4 x series of kernels, I am still using scsi emulation to run my cd-writer. Thus, in /etc/fstab, I ensure my cd-writer is configured appropriately:
I did not have to enable anything related in /etc/rc.d/rc.modules. However, I have played around with recompiling the kernel and possibly I enabled this directly in the kernel whereas the original packaged from PV might not have this. If so, you do not need to recompile the kernel, just enable the appropriate option in rc.modules as mentioned above.
In KDE I enabled the desktop icons for the CD devices (I also have a CD reader installed), as well as the floppy device. These handy icons allow me, when in KDE, to automatically mount and eject disks. Double-clicking on the CD Writer icon automatically mounts the device, opens the Konqueror file manager, and displays the disk contents. Upon closing Konqueror, and then double-clicking once again on the icon, KDE automatically unmounts the device and ejects the disk.
I am confused about the unhide option in the fstab line, what exactly is the effect of that?
I'm not using my Slack box right now, but IIRC, unhide merely shows hidden files on the CD. That is, all of those files with a dot in their file name as the first character.
Quote:
Also, do I have to do a ln -s /dev/hdd /dev/sr0 ? (my burner is at hdd)
No, I don't think you need sym link anything. Just revise the device numbers. I never installed a burner at hdd so some of the experienced users can correct me here if I'm wrong, but here is how I think things would look on my box if I swapped the drives:
GRUB:
title Slackware 10.1 - 2.4.28 - KDE 3.3.2
kernel (hd0,12)/vmlinuz-ide-2.4.28 root=/dev/hda23 ro hdd=ide-scsi vga=3 ide2=noprobe quiet
Actually I haven't burned a cd under linux yet, thats why I wanted to give it a go, ok, so I can just go ahead and try to burn now, but I just noticed something else, after following these steps, it 'broke' my drive, meaning, now I can't read my cds, cause I also use my cd burner as a reader, since my other drive just recently crapped out... now when I try to mount a cd to read I get this...
Code:
slackuser@slacker:~$ mount /dev/hdd
mount: wrong fs type, bad option, bad superblock on /dev/hdd,
or too many mounted file systems
(could this be the IDE device where you in fact use
ide-scsi so that sr0 or sda or so is needed?)
I have slack 10.2 on an external USB drive which has caused me no end of trouble following standard instructions for setting up for CD burning i.e ide-scsi in grub etc. I can burn but not read or without the ide-scsi in grub I can read but not burn.
As I only occasionally want to burn I've not included the ide-scsi option in grub and if i want to burn I use cdrecord dev=ATAPI:1,2,0 dsl-1.5.iso where the 1,2,0 is obtained from cdrecord dev=ATAPI -scanbus or something similar.
Aplogies for being a bit vague but not on my machine at present.
My desktop is fine I can burn/read in the standard way. The problem with slack on the USB drive is that I have an initrd that preloads some modules that possibly interfere with the standard configuration for burn/read. Maybe one day I will get it working as standard.
I use K3B exclusively to burn my CDs. Drag, drop, and I'm almost finished with the project.
K3B is written well as a front end to all of the related command line tools and provides a nice compatible KDE interface.
If you are using K3B then I'm guessing you also are using KDE. If so then you might consider the following:
1. Right-click on the desktop.
2. From the pop-up menu, select Configure Desktop.
3. From the General tab, verify that Show icons on desktop is enabled.
4. Select the Devices tab.
5. Select both the Mounted and unmounted devices for CD Writer, CD-ROM, and Floppy.
6. Select the OK button.
You now should have some icons on your desktop for the CD devices. To test, insert a non-blank CD into one of the drives. On the respective desktop icon, right-click and select Mount. Konqueror should open and display the disk contents. When finished browsing the disk, close Konqueror, or at least change the focused directory to something other than the CD. Then again right-click on the desktop icon. Select Eject.
If your boot loader (GRUB or LILO) and fstab are configured properly, K3B and the desktop icons will function automatically without hiccups. Because the fstab entry above specifies noauto, the device is made available but does not automatically try mounting any disks that do not yet physically exist in the drive. When you start K3B the program does the final mounting for you. Likewise with the KDE desktop device icons.
Quote:
and this is my fstab...
You previously wrote that your cd writer drive was located at hdd. Therefore, notice in your fstab that you have the cd writer configured read-only:
/dev/hdd /mnt/cdrw iso9660 noauto,users,ro
Modify that ro to rw.
You also have another entry for a burner:
/dev/sr0 /mnt/cdburner iso9660 noauto,users,rw
Is this the same drive? If so, then use one entry or the other, but not both. And consider modifying the sr0 to sr1 because the cd writer is located at hdd (hdc=sr0, hdd=sr1). Don't delete one line or the other, just add a hash mark at the beginning to comment out one line and test that way. If one entry fails then try the other.
Also ensure you have the ide-scsi option in your boot loader pointed to hdd and not hdc.
I hope this helps.
Regarding USB, I can't help there because I have no USB devices on my box.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.