| 1 |
On 01/09/2017 10:15 PM, Meino.Cramer@×××.de wrote: |
| 2 |
> Corbin Bird <corbinbird@×××××××.net> [17-01-10 05:12]: |
| 3 |
>> On 01/09/2017 02:11 PM, Meino.Cramer@×××.de wrote: |
| 4 |
>>> Hi, |
| 5 |
>>> |
| 6 |
>>> I want to burn an iso image onto a rewritable |
| 7 |
>>> CD (CD-RW) with k3b. |
| 8 |
>>> |
| 9 |
>>> I loaded the empty CDRW medium into the burner. |
| 10 |
>>> |
| 11 |
>>> I started k3b. |
| 12 |
>>> |
| 13 |
>>> Top left it says: |
| 14 |
>>> |
| 15 |
>>> "Empty CDRW-medium" |
| 16 |
>>> |
| 17 |
>>> I pressed "Burn ISO". |
| 18 |
>>> |
| 19 |
>>> A dialog pops up, asking for a ISO image |
| 20 |
>>> which did select. |
| 21 |
>>> |
| 22 |
>>> Then it calculates the Hash and asked |
| 23 |
>>> me "Please insert an empty medium" |
| 24 |
>>> |
| 25 |
>>> "Okay", I thought, "may erasing helps!" |
| 26 |
>>> |
| 27 |
>>> I choosed "Erase CDRW". A dialog pops |
| 28 |
>>> up and offers "Start", which I pressed. |
| 29 |
>>> |
| 30 |
>>> Instantly another error dialog pop up, which |
| 31 |
>>> seems to be presented by another, foreign |
| 32 |
>>> OS...it looks so familiar, saying: |
| 33 |
>>> |
| 34 |
>>> "Found medium: Empty CD-RW medium |
| 35 |
>>> Please insert rewritable CD medium into drive." |
| 36 |
>>> |
| 37 |
>>> Lost? |
| 38 |
>>> |
| 39 |
>>> What went so badly here? |
| 40 |
>>> |
| 41 |
>>> Cheers |
| 42 |
>>> Meino |
| 43 |
>>> |
| 44 |
>>> |
| 45 |
>>> |
| 46 |
>>> |
| 47 |
>>> |
| 48 |
>> Question for you : |
| 49 |
>> |
| 50 |
>> Did you format the CD-RW media first? ( Yes, it must be formatted before |
| 51 |
>> anything gets written. ) |
| 52 |
>> |
| 53 |
>> |
| 54 |
>> |
| 55 |
>> |
| 56 |
> Answer for you: |
| 57 |
> Yes |
| 58 |
> |
| 59 |
> |
| 60 |
> |
| 61 |
> |
| 62 |
|
| 63 |
You would not believe how many do NOT know to do that first. :) |
| 64 |
|
| 65 |
That screwy error you got can very easily be from hardware not properly |
| 66 |
setting up. |
| 67 |
|
| 68 |
If you are willing to troubleshoot, there are some things to check. |
| 69 |
|
| 70 |
First check ... in the dmesg log, does the kernel see the burner? |
| 71 |
( it seems the SFF / ATAPI devices can have problems, |
| 72 |
with having to go communicate through the kernels ahci layer ) |
| 73 |
|
| 74 |
sample from my dmesg log : |
| 75 |
|
| 76 |
[ 2.027722] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) |
| 77 |
[ 2.031197] ata4: FORCE: cable set to sata |
| 78 |
[ 2.031332] ata4.00: FORCE: horkage modified (noncq) |
| 79 |
[ 2.031459] ata4.00: FORCE: horkage modified (atapi_dmadir) |
| 80 |
[ 2.031576] ata4.00: ATAPI: PIONEER BD-RW BDR-208M, 1.50, max |
| 81 |
UDMA/100, DMADIR |
| 82 |
[ 2.035319] ata4.00: configured for UDMA/100 |
| 83 |
[ 2.046988] scsi 4:0:0:0: CD-ROM PIONEER BD-RW BDR-208M |
| 84 |
1.50 PQ: 0 ANSI: 5 |
| 85 |
[ 2.089230] sr 4:0:0:0: [sr0] scsi3-mmc drive: 125x/125x writer |
| 86 |
dvd-ram cd/rw xa/form2 cdda tray |
| 87 |
[ 2.089422] cdrom: Uniform CD-ROM driver Revision: 3.20 |
| 88 |
[ 2.089656] sr 4:0:0:0: Attached scsi CD-ROM sr0 |
| 89 |
[ 2.089723] sr 4:0:0:0: Attached scsi generic sg3 type 5 |
| 90 |
|
| 91 |
NOTE : this is a BD-RW drive. The kernel has to be forced to recognize it. |
| 92 |
The kernel parameter : libata.force=4.00:sata,1.5,noncq,atapi_dmadir |
| 93 |
|
| 94 |
The reason I ask, is that if the kernel can't or hasn't recognized it, |
| 95 |
the wrong command sets are used. |
| 96 |
|
| 97 |
Hope this helps. |
Archives