Carlos Robinson <carlos.e.r(a)opensuse.org> changed:
What |Removed |Added
Info Provider|carlos.e.r(a)opensuse.org |
--- Comment #8 from Carlos Robinson <carlos.e.r(a)opensuse.org> 2009-12-17 13:33:20
(In reply to comment #7)
growisofs fail and wodim suceed?
Sure, it can. As I wrote before, while burning / ripping, the kernel and
driver just play a messenger role between the application and the drive. If
your drive is peculiar and unhappy with certain command sequence, different
apps can definitely make or break it.
I see. A solution for me, then, would be if the GUI frontends used wodim
instead of growisof. Or use the frontend for generating the iso, then burn it
with wodim in the command line, wich I do often, anyway; i'm just more used to
Another possibility is that your
previous blank media was just faulty but you tested it more than once, right?
Yes, twice. Once with brasero, another with growisof. See #0
A funny thing:
the just burned session is not mountable right after burning:
This too is expected. Many drives need reload after burning to recognize the
burned media. One of the reasons why so many burning apps eject the drive
after burning is complete.
Ah, ok. I had forgotten.
So, I think you'll need to retry with growisofs
and find out whether different
burning programs indeed make difference?
Growisofs indeed fails, see initial report, #0. I could try with debug enabled,
but the man page doesn't say how.
"debug" is only mentioned in this paragraph:
There are several undocumented options commonly denoted with
-use-the-force-luke prefix. Some of them serve debugging pur-
poses. Some require certain knowledge about recording process
or even OS kernel internals and as being such can induce con-
fusing behaviour. Some are to be used in very specific situa-
tions better recognized by front-ends or automated scripts.
Rationale behind leaving these options undocumented is that
those few users who would actually need to use them directly
can as well consult the source code or obtain specific
So if you know of a non documented -use-the-force-luke which produces the debug
output that can help solve this problem, I'll try. Otherwise, I won't burn
another coaster :-)
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.