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'll start this off with a quick rundown of my system config right now:
hda - Maxtor HDD
hdb - Maxtor HDD
hdc - Liteon 52x32x52x cdrw
hdd - LG 16x DVD
hde - Quantum Fireball HDD
In short, the problem is that during K3b setup, the program doesn't see my Liteon as a cdrw. Interestingly I can read CD's off it but when I try to setup K3b it sees it only as a CD drive.
Now, I read someplace that the version of K3b distributed with SuSE is "crippled" somehow, so I've already downloaded the new rpm and I'm ready to uninstall the SuSE distributed version and reinstall the version from K3b.
rpm -e k3b
and then rpm -ihv k3b.whatever.rpm
Next I read that CDRW's have to be emulated as SCSI devices - yes?
How is this so and where would I make the change for the system to see it as SCSI? /dev/fstab? would I need erase the current fstab entry for /dev/hdd (cdrw)?
Here's the result when I run (as root): cdrecord -scanbus
linux:~ # cdrecord -scanbus
Cdrecord 2.0 (i686-suse-linux) Copyright (C) 1995-2002 Jörg Schilling
cdrecord: No such file or directory. Cannot open '/dev/sg*'. 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'.
Since I'm running GRUB, here's the config file (menu.lst):
color white/blue black/light-gray
default 0
gfxmenu (hd1,0)/message
timeout 8
title Linux yay
kernel (hd1,0)/vmlinuz root=/dev/hdb6 vga=0x317 splash=silent showopts
initrd (hd1,0)/initrd
yes you need scsi emulation
so show the output of:
lsmod |grep ide-scsi
if nothing you can simply start off by typing (as root):
modprobe ide-scsi
if that works, you can append to the end of this line:
kernel (hd1,0)/vmlinuz root=/dev/hdb6 vga=0x317 splash=silent showopts hdc=ide-scsi
so add bootup it will initialize that..
The reason your CDRW drive isn't detected as CDRW drive is usually because SCSI emulation hasn't been turned on. (unless you use a 2.6 kernel).
In order to turn on SCSI emulation on a drive you'll have to add a kernel boot option "hdX=ide-scsi", where X is the drive letter.
In your case: "hdc=ide-scsi".
However, for this to work, generic scsi and scsi-cdrom support has to be enabled in your kernel.
I've never used GRUB, but from the looks of your config, I'd say you'd have to change "kernel (hd1,0)/vmlinuz root=/dev/hdb6 vga=0x317 splash=silent showopts", so it says:
"kernel (hd1,0)/vmlinuz root=/dev/hdb6 vga=0x317 splash=silent showopts hdc=ide-scsi"
Note that afterwards your drive will probably be called scdX in stead of hdX
'k great, thanks, I'll try that. So I wouldn't have to change anything in /etc/fstab then? Would that line /dev/cdrom/ in fstab just interfere at all - should I erase it?
BTW, sorry for the dumb question, but what's the reason behind SCSI emulation for cdrw's?
The devices /dev/cdrom and /dev/dvd are probably just symlinks to the real device nodes. Therefore you might want to change those.
The reason for SCSI emulation? Probably because SCSI is easy to code for
I keep getting an error at K3b setup - must be run as root.
I'm looking at the boot.msg now to see if there's anything in there.
Somethin weird goin on.
just to retrace my steps:
1) added "hdc=ide-scsi" (no quotes) to Grub
2) md /mnt/cdrw
3) added /dev/scd0 /mnt/cdrw auto ro,noauto,user,exec 0 0 to /etc/fstab
4) removed /dev/cdrom /mount/cdrom auto ro,nauto,user,exec 0 0 from /etc/fstab
5) made symlink ln -s scd0 cdrom in /dev
re-booted ... I get a couple of icons on my desktop (CDROM and CD Recorder (scd0 not mounted)) and I now I can't get at either.
OK I'm in root now and started the K3b setup and I don't even see the drive at all. When I try to "add device" and specify /dev/scd0 I get an error "Could not find attached device at /dev/scd0".
Seems to me your kernel doesn't have scsi support...
So you might have to recompile your kernel with the options "scsi" [CONFIG_SCSI], "scsi-cdrom support" [CONFIG_BLK_DEV_SR] and "generic scsi" support [CONFIG_CHR_DEV_SG] enabled.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.