Comment 7 for bug 371002

Well, it is unclear how brasero gets the write speed.....

Wodim is known to be broken, so in case brasero calls wodim
an incorrectly reported speed is expected. This could be verified
by removing wodim and installing cdrecord instead.

Cdrecord knows workarounds for firmware bugs in most drives
and retrieves the correct write speed. This should visible be in the
cdrecord output.

If the brasero printout stays wrong, this is a brasero bug.
Brasero is written in a non-portable way and tries to send own SCSI commands.
Brasero should rather call cdrecord and parse the output as cdrecord works
on any recent OS.