From: "J.A. Magallon" <jamagallon@able.es>
To: Bill Davidsen <davidsen@tmr.com>
Cc: "J.A. Magallon" <jamagallon@able.es>,
Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: cd burning, capabilities and available modes
Date: Wed, 01 Dec 2004 22:58:55 +0000 [thread overview]
Message-ID: <1101941935l.7651l.0l@werewolf.able.es> (raw)
In-Reply-To: <41AE47F3.7090502@tmr.com> (from davidsen@tmr.com on Wed Dec 1 23:38:43 2004)
On 2004.12.01, Bill Davidsen wrote:
> J.A. Magallon wrote:
> > Hi...
> >
> > Following my little oddisey to let cd-burning easy for my users,
> > I think I have found another problem.
> >
> > It looks like the formats available to cdrecord depend on being root
> > (cdrecord is not suid, if it is it complains it cant reserve some
> > buffers).
> >
> > As root:
...
> > Driver flags : MMC-3 SWABAUDIO BURNFREE
> > Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
> >
> > As user:
> > Driver flags : MMC-3 SWABAUDIO BURNFREE
> > Supported modes:
...
>
> I get that all the time, because one of my drives doesn't support TAO
> burning. I suspect your firmware sucks, and you will have to use session
> at a time rather than track at a time, option "-sao" works for me. Are
> you running standard cdrecord or one of the hacks?
>
Look at what I quoted above. It is the same box, just running cdrecord
as root or as user. The 'Supported modes:' line is empty.
What has the firmware to do with that ?
A guess: perhaps the problem is:
WARNING ! Cannot gain SYS_RAWIO capability !
: Operation not permitted
as user, so system does not allow the user to query the drive at low
level via some ioctl() or the liketo get the supported modes.
BTW, using the LSM realtime module for group cdwriter (80 in my box)
killed this messages:
cdrecord: Cannot allocate memory. WARNING: Cannot do mlockall(2).
cdrecord: WARNING: This causes a high risk for buffer underruns.
cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler
cdrecord: Permission denied. WARNING: Cannot set priority using setpriority().
cdrecord: WARNING: This causes a high risk for buffer underruns.
so at least this is good (TM).
--
J.A. Magallon <jamagallon()able!es> \ Software is like sex:
werewolf!able!es \ It's better when it's free
Mandrakelinux release 10.2 (Cooker) for i586
Linux 2.6.10-rc2-jam4 (gcc 3.4.1 (Mandrakelinux 10.1 3.4.1-4mdk)) #2
next prev parent reply other threads:[~2004-12-01 23:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-01 13:40 cd burning, capabilities and available modes J.A. Magallon
2004-12-01 16:36 ` Daniel Drake
2004-12-01 15:00 ` J.A. Magallon
2004-12-01 17:05 ` Lee Revell
2004-12-01 22:38 ` Bill Davidsen
2004-12-01 22:58 ` J.A. Magallon [this message]
2004-12-02 7:57 ` Frank Steiner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1101941935l.7651l.0l@werewolf.able.es \
--to=jamagallon@able.es \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.