Re: CDMRW in 2.6

[Jens Axboe]

On Fri, Aug 13 2004, Chris Clayton wrote:
> > > I'll try a full (as opposed to quick) blank with cdrwtool plus a
> > > forced format with cdmrw and report back when that has finished.
> >
> > Yes please do that, if that doesn't work it's really screwed.
> 
> Ok, here's the results:
> 
> [chris:~]$ cdrwtool -t 10 -d /dev/hdc -b full
> setting speed to 10
> using device /dev/hdc
> full blank
> 1386KB internal buffer
> setting write speed to 10x
> 
> <<no new messages from dmesg>>
> 
> [chris:~]$ cdmrw -d /dev/hdc -f full -F
> not a mrw formatted disc
> LBA space: DMA
> 
> <<no new messages from dmesg>>
> 
> [chris:~]$ while cdmrw -d /dev/hdc -f full | grep "mrw format running" ; do 
> sleep 20; done
> mrw format running
> <snip>
> mrw format running
> 
> <<no new messages from dmesg>>
> 
> [chris:~]$ mkudffs --media-type=cdrw /dev/hdc
> start=0, blocks=16, type=RESERVED
> start=16, blocks=3, type=VRS
> start=19, blocks=237, type=USPACE
> start=256, blocks=1, type=ANCHOR
> start=257, blocks=31, type=USPACE
> start=288, blocks=32, type=PVDS
> start=320, blocks=32, type=LVID
> start=352, blocks=32, type=STABLE
> start=384, blocks=1024, type=SSPACE
> start=1408, blocks=256480, type=PSPACE
> start=257888, blocks=31, type=USPACE
> start=257919, blocks=1, type=ANCHOR
> start=257920, blocks=160, type=USPACE
> start=258080, blocks=32, type=STABLE
> start=258112, blocks=32, type=RVDS
> start=258144, blocks=31, type=USPACE
> start=258175, blocks=1, type=ANCHOR
> 
> <<the following new messages from dmesg>>
> 
> cdrom: hdc: mrw address space DMA selected
> cdrom open: mrw_status 'mrw complete'
> hdc: command error: status=0x51 { DriveReady SeekComplete Error }
> hdc: command error: error=0x54

Ok yes, same error. It's the drive doing something odd, I have no idea
what...

> I'll try the same process (except the blanking) with a brand new piece of 
> media and report when that is complete.

I doubt it'll help.

-- 
Jens Axboe

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/