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've just compiled 2.6.15.6, and having spent a bit getting alsa to work, I'm now testing my scsi cd burner. cdrecord in slack 10.2 doesn't seem to like 2.6, and won't see my drive. device nodes cdrecord looks for don't exist in /dev, and cdrecord doesn't permit naming devices by name (/dev/sr0 is the only device for scsi cdrom when I mount a data cd on it). Overall I havent been impressed with the whole udev thing, and having always used a 2.4 kernel previously, I had to enable all kinds of things in init scripts that I didn't need/use in 2.4 JUST to make alsa work, and now this with cdrecord. Never used devfs either.
Anyway, when I specify the device for cdrecord dev=0,4,0, I get an error about using a 2.6 kernel, and /dev/pg4 not existing, tried dev=sg, no go.
cdrecord -scanbus
Cdrecord-Clone 2.01 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling
cdrecord: Warning: Running on Linux-2.6.15.6
cdrecord: There are unsettled issues with Linux-2.5 and newer.
cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris.
cdrecord: No such file or directory. Cannot open '/dev/pg*'. Cannot open SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'.
cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
it is not like that since 2.6 is testing, this message wil b there, hope, not the problem with cdrecord in slack
Quote:
I'm now testing my scsi cd burner
so u have a scsi burner, not an atapi device
can u please go through the "dmesg" output, and post "dmesg |grep CD"
for an atapi cdrom this error appears, if u havent enabled the scsi emulation.
since it s a custom made kernel u may missing something with scsi support
are u sure u enabled the scsi cdrom support in scsi device support while u compile ur kernel
go through the "device driver and filesystem" sections while compiling kernel
Welcome to LQ and slack forum
it is not like that since 2.6 is testing, this message wil b there, hope, not the problem with cdrecord in slack
so u have a scsi burner, not an atapi device
can u please go through the "dmesg" output, and post "dmesg |grep CD"
for an atapi cdrom this error appears, if u havent enabled the scsi emulation.
since it s a custom made kernel u may missing something with scsi support
are u sure u enabled the scsi cdrom support in scsi device support while u compile ur kernel
go through the "device driver and filesystem" sections while compiling kernel
The problem was simply a case of the sg module not being loaded. Curious, why didn't it autoload when a syscall to scsi generic was made, this was how it worked in 2.4.
I've noticed this behaviour with a few other modules, they dont autoload as they did in 2.4. And the lack of syslog reporting by said syscalls makes it more difficult to know WHAT module was called for....I'll have to poke around modprobe.conf I guess....thanks anyway!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.