Re: Re: Re: plextor px-708uf: cannot get disk type
Joerg, I removed magicdev (rpm -e magicdev) and I *still* got this
error. (Lourens, I also saw this on Google; thanks for the suggestion.)
I removed the file Autorun.desktop from .kde/autostart and this
stopped the kernel/module message. (I probably should have mentioned I
use KDE, not GNOME.)
Anyway, here is the bad news. After all that, I still get the following:
====================
[root@reganlinux magliery]# dvdrecord -atip dev=0,0,0
dvdrtools v0.1.3
Portions (c) 2002 Red Hat, Inc.
Based on:
Cdrecord 1.11a15 (i386-redhat-linux-gnu) Copyright (C) 1995-2001 Jörg
Schilling
scsidev: '0,0,0'
scsibus: 0 target: 0 lun: 0
Linux sg driver version: 3.1.24
Using libscg version 'schily-0.5'
dvdrecord: Warning: using inofficial libscg transport code version
(schily-RH-scsi-linux-sg.c-1.69-RH-O_EXCL '@(#)scsi-linux-sg.c
1.69 02/01/18 Copyright 1997 J. Schilling').
Device type : Removable CD-ROM
Version : 2
Response Format: 1
Vendor_info : 'PLEXTOR '
Identifikation : 'DVDR PX-708A '
Revision : '1.04'
Device seems to be: Generic mmc2 DVD.
dvdrecord: Input/output error. get configuration: scsi sendcmd: no error
CDB: 46 00 00 21 00 00 00 01 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 00 00 00 00 00 0A 00 00 00 00 00 00 00 00
Sense Key: 0x0 No Additional Sense, Segment 0
Sense Code: 0x00 Qual 0x00 (no additional sense information) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.001s timeout 40s
Using generic SCSI-3/mmc CD-R driver (mmc_cdr).
Driver flags : SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
dvdrecord: Input/output error. read disk info: scsi sendcmd: no error
CDB: 51 00 00 00 00 00 00 00 24 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 00 00 00 00 00 0A 00 00 00 00 00 00 00 00
Sense Key: 0x0 No Additional Sense, Segment 0
Sense Code: 0x00 Qual 0x00 (no additional sense information) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.002s timeout 240s
dvdrecord: Cannot get disk type.
=============================
Apparently, the KDE automounter was not the (only) problem. Now what...?
Tom
Reply to: