This one time, at band camp, Eduard Bloch said: > #include <hallo.h> > * Stephen Gran [Tue, Apr 26 2005, 09:59:45PM]: > > > Sorry, I see many nearly related bugs but I do not see this one in > > particular. If I have missed one that adresses the same issue, please > > feel free to close or merge this one as you see fit. > > > > The issue is that while running 2.6.10, cdrecord -prcap fails with > > > > cdrecord: Cannot allocate memory. SG I/O error > > > > This is with an ATAPI drive, and an /etc/default/cdrecord with > > CDR_DEVICE=ATA:1,0,0 > > (for /dev/hdc - I believe this is right, and earlier kernels don't > > complain) > > Believe it or not, better use "-scanbus dev=ATA:"
[EMAIL PROTECTED]:~$ cdrecord -scanbus dev=ATA:
Cdrecord-Clone 2.01.01a01 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Joerg
Schilling
NOTE: this version of cdrecord is an inofficial (modified) release of cdrecord
and thus may have bugs that are not present in the original version.
Please send bug reports and support requests to <[EMAIL PROTECTED]>.
The original author should not be bothered with problems of this version.
cdrecord: Warning: Running on Linux-2.6.8-2-686-smp
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: Warning: Linux-2.6.8 introduced incompatible interface changes.
cdrecord: Warning: SCSI transport does no longer work for suid root programs.
cdrecord: Warning: if cdrecord fails, try to run it from a root account.
scsidev: 'ATA:'
devname: 'ATA'
scsibus: -1 target: -1 lun: -1
Warning: Using badly designed ATAPI via /dev/hd* interface.
Error trying to open /dev/hda exclusively (Device or resource busy)... retrying
in 1 second.
Error trying to open /dev/hda exclusively (Device or resource busy)... retrying
in 1 second.
Error trying to open /dev/hda exclusively (Device or resource busy)... retrying
in 1 second.
Error trying to open /dev/hda exclusively (Device or resource busy)... retrying
in 1 second.
Error trying to open /dev/hda exclusively (Device or resource busy)... retrying
in 1 second.
Error trying to open /dev/hda exclusively (Device or resource busy)... retrying
in 1 second.
Error trying to open /dev/hda exclusively (Device or resource busy)... retrying
in 1 second.
Error trying to open /dev/hda exclusively (Device or resource busy)... retrying
in 1 second.
Error trying to open /dev/hda exclusively (Device or resource busy)... retrying
in 1 second.
Error trying to open /dev/hda exclusively (Device or resource busy)... retrying
in 1 second.
cdrecord: Device or resource busy. Cannot open '/dev/hda'. Cannot open SCSI
driver.
cdrecord: For possible targets try 'cdrecord -scanbus'.
cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
cdrecord:
cdrecord: For more information, install the cdrtools-doc
cdrecord: package and read /usr/share/doc/cdrecord/README.ATAPI.setup .
hda is where my / lives, so of course it's going to be a little busy.
The same happens when run as root.
> > So burning a disk also fails, although of course it works as root.
> > I am of course in group cdrom and have been for some time. The
> > permissions on all the cdrecord* executables are correct.
>
> What does that mean? Is it suid-root?
[EMAIL PROTECTED]:~$ ll /usr/bin/cdrecord*
-rwsr-xr-- 1 root cdrom 133 2005-04-26 05:06 /usr/bin/cdrecord
-rwsr-xr-- 1 root cdrom 351404 2005-04-26 05:06 /usr/bin/cdrecord.mmap
-rwsr-xr-- 1 root cdrom 351436 2005-04-26 05:06 /usr/bin/cdrecord.shm
> > This is similar to what is mentioned at the tail end of README.Debian,
> > but not the same, so I am not sure it is the same problem. On the
> > off-chance it was, I tried to rebuild cdrecord, as the advice said,
> > and it happily failed on patch 17 :(
>
> What does that mean? Exact error message sounds says ...
Oddly, this time it applies. I will try the locally built version and
see what happens.
> > The very strange thing about all of this is that run under strace to
>
> Where is the strace log? Store it somewhere online (on gluck or alioth,
> for example), otherwise we can only guess.
I will have to reboot into the newer kernel to make you a log. I am
unable to do so today, but will this weekend if need be.
> > debug it, it happily runs just fine - does strace intercept a bad
> > syscall and translate it? That seems like odd behavior for strace if
> > so.
>
> Huch, different behaviour with strace is a possible sign for NOT having
> the right permissions (suid).
See above.
--
-----------------------------------------------------------------
| ,''`. Stephen Gran |
| : :' : [EMAIL PROTECTED] |
| `. `' Debian user, admin, and developer |
| `- http://www.debian.org |
-----------------------------------------------------------------
pgpFSxrddUxeZ.pgp
Description: PGP signature
