I think my confusion came from the fact that i didn't need to reference a
specific device before the kernel upgrade. As for telling it to use
/dev/sg1 or sg0 ... I cant really tell anymore, i'm no longer using that
kernel. It probably was an incorrect usage of cdrecord, so i'm sorry for
the post
safemode said once upon a time (Sun, 15 Oct 2000):
> Everything seems to be working great now... i'm using a patch Andre
> Hedrick gave me and everything works like normal again. Thanks again for
> everyone's help. Back to burning cds.
The error you were getting is the error I get on my syste
On Sun, 15 Oct 2000, safemode wrote:
>
> Unfortunally i compile in all the scsi stuff and make ide-cd modular, so i
> dont know what was compiled in anymore since that kernel tree is gone. I
> did however recieve a patch to test10-pre3 which seems to be working, will
> test the actual record pa
Everything seems to be working great now... i'm using a patch Andre
Hedrick gave me and everything works like normal again. Thanks again for
everyone's help. Back to burning cds.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTEC
Unfortunally i compile in all the scsi stuff and make ide-cd modular, so i
dont know what was compiled in anymore since that kernel tree is gone. I
did however recieve a patch to test10-pre3 which seems to be working, will
test the actual record part in a bit (and this kernel i know for a fact h
safemode said once upon a time (Sun, 15 Oct 2000):
> Alright, first off let me say that this cdrecord was working fine with
> 2.4.0-test8. The recorder is on /dev/scd0 and also on /dev/sr0. maybe
> this has something to do with it? i'm not sure, but cdrecord keeps saying
Make sure you have SC
Hrm.. last time I checked, cdrecord wanted to use the scsi generic (sg)
interface. Is that loaded (or available as a module)?
Matt
On Sun, Oct 15, 2000 at 02:24:40AM -0400, safemode wrote:
> this is cdrecord -v -debug -scanbus
> note that i symlinked pg0 to scd0 since the device didn't exist an
this is cdrecord -v -debug -scanbus
note that i symlinked pg0 to scd0 since the device didn't exist anyway and
cdrecord insists that is the /dev equivilant to 0,0,0. well
dev: (NULL POINTER) speed: -1 fs: -1
Cdrecord 1.10a04 (i686-pc-linux-gnu) Copyright (C) 1995-2000 Jörg Schilling
TOC Type:
I just did and it told me it wanted /dev/pg0 which did not exist. The
problem is /dev/scd0 is the device and cdrecord refuses to believe it's a
CDR, it continues to say that it's read-only
On Sun, 15 Oct 2000 02:09:39 Matthew Dharm wrote:
> Have you tried using the dev=0,0,0 instead of the dev
Have you tried using the dev=0,0,0 instead of the dev=/dev/ form? I'm
told by the cdrecord maintainer that it's more reliable that way, and that
the /dev/ format should not be used.
What does cdrecord -scanbus show?
Matt
On Sun, Oct 15, 2000 at 01:57:24AM -0400, safemode wrote:
> Alrig
Oops on one thing, /dev/sr0 is merely a symlink to /dev/scd0, sorry it's
pretty late. these are the attributes of /dev/scd0
brw-rw1 root cdrom 11, 0 Sep 10 01:02 /dev/scd0
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [
Alright, first off let me say that this cdrecord was working fine with
2.4.0-test8. The recorder is on /dev/scd0 and also on /dev/sr0. maybe
this has something to do with it? i'm not sure, but cdrecord keeps saying
the stats for it are -2,-2,-2when it should be 0,0,0. Does anyone
know wha
12 matches
Mail list logo