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've got a little problem trying to install my cd-writer. Yes, I've read the CD-Writing HOWTO @ ldp.org but still....
I'me using RH 7.3, my kernel version is 2.4.18-10 and my cd-writer is a TEAC W516EB.
I've recompiled my kernel with SCSI emulation support, SCSI support, SCSI CD-ROM support and SCSI generic support all enabled.
I've added hdd=ide-scsi in grub.conf.
I've added theses lines into modules.conf:
options ide-cd ignore=hdd
alias scd0 sr_mod
pre-install sg modprobe ide-scsi
pre-install sg_mod modprobe ide-scsi
pre-install ide-scsi modprobe ide-cd
The sg and scd files exists in /dev/ but no sign of a scsi folder.
When I try cdrecord -scanbus, it gets me a message saying something like there's no scsi driver available.
And on boot, I get this message:
kmod failed to exec /sbin/modprobe -s -k scsi_hostadapter errno=2
I've checked but It seems that whether people really have scsi's in their machines or the command cdrecord -scanbus gives them a result which it doesn't for me probably because of the message I get when I boot.
I have exact the same message and my burner is dead, so I can't really tell if it relates to it, and I am still looking forward to resolving this issue, maybe next week I'll get a new burner (mine was dead for a couple of months already ), and the message doesn't really bothers me, 'cause my SCSI scanner works fine.
can you mount your cd-rw?, because it doesn't matter whether you have the scsi emulation working or not, you can still mount the drive and play cd audios. The only thing that you won't be able to do is burn with a software which strictly supports scsi emulation drives. Today, as a matter of fact I bought the Yamaha CRW3200SZ, which by the way is capable of doing Ultra scsi connection or simple E-IDE connection. Since this computer only has IDE then that's what I'm using. Anyway, I just plugged the driver, and since I used to have the 2.4.18 kernel I decided to recompile the kernel right before I openned my computer and plugged the driver in. So, I recompiled with all the scsi support, blah, blah, blah. Connect the driver, boot up my box and voila!, Linux picked up the driver with no problems, then I logged in. After that I downloaded Xcdroast, and after I installed it I ran it as root and the thing said that I didn't have scsi emulation on, and thus Xcdroast would not see any of my drives. Ok, so I go to the kernel menu config because I thought I remembered choosing all the scsi options. Then I read the Help section while selecting SCSI emulation, and I saw that I'm supposed to insert a kernel parameter at boot time...so I'm like "how the heck do I do that??", considering had never inserted a parameter into the kernel. Anyway, I went into the Xcdroast website, which I will post, www.xcdroast.org, and there is a Manual on making Xcdroast work, so I looked at it, and the instructions pretty much begin a adding two lines, one in lilo.conf and one in modules.conf. So I added them, re ran lilo, booted, and voila!, Xcdroast detected my DVD and my CDRW. Isn't beautiful?, and I burnt for the first time on this computer a 700 meg cd in 2.5 minutes, heheheh, gotta love it.
So, my question, as asked before, can you even mount the drive?
And you might want to download 2.4.19 and install it, it has LOTS of great upgrades starting with USB!, also you have a Redhat compiled kernel...usually those kernels don't like some hardware...so I suggest you upgrade soon.
Yes, it is an IDE drive and I don't have any SCSI adapters in my PC.
On boot, just after the line corresponding to SCSI, this message appears:
kmod failed to exec /sbin/modprobe -s -k scsi_hostadapter errno=2
How could I force recognition for a SCSI emulation ?
Thank you for your time.
Yes, my drive can be mounted correctly. But, it's burning stuff I wan't to do
I find your two suggestions quite interesting;
I'll read the install instructions of xcdroast and I'll download the patch kernel 2.4.19 for RH 7.3, hoping that I will be able to burn afterwards.
Thank you very much.
have you change any hardware since ?
Have you try under root ?
I strongly suggest you compile a new kernel to get ride of the 'proprietory functions' that distrobutions includes in their 'modified kernel' (the -number following your kernel version).
I, too, thought that I would lose my GUI access and other configurations but everything went sweet as candy.
***Don't forget to enable all scsi support in your kernel config.
The number after the kernel in a RedHat, SuSe, or Mandrake kernel is what build number they were working under. For instance, before releasing RedHat 7.3 they had 10 kernel builds they worked with before settling on which one to release with.
Proprietary extensions would mean that they add source to the kernel that makes it different than the one found at www.kernel.org. I am certain that RedHat doesn't do this, and am pretty certain that Mandrake and SuSe don't either (all that Nvidia crap makes me wonder, but I don't run those distros much anymore, and I don't have a Nvidia card anywhere in my house... coincidence for the most part, nothing against Nvidia). Deb and Slack don't; Gentoo sometimes releases under weird patch levels, but nothing that isn't GPL.
If you don't believe me, RPM out the RedHat kernel source for 2.4.18, download a tarball from kernel.org, run a "make mrproper" on both of them, and then "diff" both trees. This will take a while, get a cup of coffee, or five.
What RedHat and Mandy and SuSe and even Deb and Slack sometimes do is choose really stupid, annoying, or infuriating kernel options. Also, almost without a doubt all of their stock kernels are compiled using "make config". Then, when you use their default .config file, its really easy to create dependancy errors when you then reconfigure the same .config with a "make menuconfig" or "make xconfig".
If you take distro release source, run a "make mrproper" first, then their .config file goes away.
This is one of the primary reasons most people get bum compiles with distro source trees.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.