SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Cdrecord 2.0 (i686-pc-linux-gnu) Copyright (C) 1995-2002 J?rg 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'.
I think I might have to compile scsi generic support into my kernel
I am running Slackware 9.0 and i installed the bare kernel if this is the problem how do I do it.
Last edited by monkeymartin; 04-09-2003 at 02:09 AM.
The sg device support is part of the bare.i kernel. It does require a kernel module to be loaded though. (ide-scsi) If that module has loaded, use "lsmod" to determine if it is listed, then the problem is back to the lilo config. (append="hdc=ide-scsi") And the hdc device needs to be the proper device for the CDRW drive. After changing, run "lilo" and then reboot. Chekc for the module "ide-scsi" and if loaded then "cdrecord -scanbus" should report the scsi bus and the drive, probably on device 0,0,0.
The ide-scsi module should be configured to load from boot in the rc.modules.
Just a quick note.
Slack always comes (as any respected linux distribution) with a set of recent HOWTO documentation files (that I belive you have installed). Check out /usr/doc/Linux-HOWTOs/CD-Writing-HOWTO. It contains pretty extencive information on how to create iso images, burn CD's and what modules are required to do that.
If you are still able to mount a CD using /dev/hdc as the device drive then the append statement is not correct. Check it, change as required and run lilo again. Then reboot. The /dev/hdc should no longer work. The drive would /dev/scd0 after the module ide-scsi is loaded to support the drive. As long as the native IDE driver support is controlling the drive it prevents the ide-scsi module from functioning. Also, make sure your CDR drive is actually hdc. Use the value that is correct for your drive.
hdc is definetly the correct drive as it was listed in dmesg before any alterations (plus it is master on second ide), so I believe that the append statement is OK. I am using the bare.i kernal, and believe that kmod is running most things at boot.
Is it better to turn of hotplugging and just uncomment things in rc.modules? Woruld this be grabbing the cdrw before ide-scsi can get it?