[gl-como] masterizzazione

[fabio]

stai masterizzando come root?
se no prova da root e vedi se dà quegli errori di operazione non 
permessa lo stesso...
se non và prova alla "bruta maniera": rimuovi il pacchetto cdrecord e 
tutte le sue configurazioni e re-installa...

Raysiel wrote:

>non so bene per quale motivo accada e men che meno come rimedioare quindi mi 
>appello alla saggezza della collettività.
>masterizzando con k3b ottengo una sfilza di warning allucinante che riporto 
>qui di seguito:
>
>/usr/bin/cdrecord: Warning: Running on Linux-2.6.10-gentoo-r4Prova
>/usr/bin/cdrecord: There are unsettled issues with Linux-2.5 and newer.
>/usr/bin/cdrecord: If you have unexpected problems, please try Linux-2.4 or 
>Solaris.
>/usr/bin/cdrecord: Cannot allocate memory. WARNING: Cannot do mlockall(2).
>/usr/bin/cdrecord: WARNING: This causes a high risk for buffer underruns.
>/usr/bin/cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler
>/usr/bin/cdrecord: Permission denied. WARNING: Cannot set priority using 
>setpriority().
>/usr/bin/cdrecord: WARNING: This causes a high risk for buffer underruns.
>[cut]
>/usr/bin/cdrecord: WARNING: Data may not fit on current disk. //e vabbè questo 
>lo conosco
>/usr/bin/cdrecord: Notice: Overburning active. Trying to write more than the 
>official disk capacity.
>/usr/bin/cdrecord: Operation not permitted. WARNING: Cannot set 
>RR-scheduler //questi no però
>/usr/bin/cdrecord: Permission denied. WARNING: Cannot set priority using 
>setpriority().
>/usr/bin/cdrecord: WARNING: This causes a high risk for buffer underruns.
>[cut]
>/usr/bin/cdrecord: Success. write_g1: scsi sendcmd: no error
>CDB:  2A 00 00 05 4F 28 00 00 1F 00
>status: 0x2 (CHECK CONDITION)
>Sense Bytes: 70 00 03 00 00 00 00 12 00 00 00 00 0C 00 00 00
>Sense Key: 0x3 Medium Error, Segment 0
>Sense Code: 0x0C Qual 0x00 (write error) Fru 0x0
>Sense flags: Blk 0 (not valid) 
>resid: 63488
>cmd finished after 7.011s timeout 200s
>/usr/bin/cdrecord: A write error occured.
>/usr/bin/cdrecord: Please properly read the error message above.
>write track data: error after 712589312 bytes
>
>;_;
>
>  
>