| View previous topic :: View next topic |
| Author |
Message |
yanos
Tux's lil' helper
Joined: 11 Sep 2003
Posts: 149
Location: montreal, canada
|
 Posted: Tue Jan 15, 2008 3:16 am Post subject: [SOLVED] Problems with my new Pioneer burner |
 |
|
Hello.
I recently purchase a new burner and suddenly I can't seem to be able to burn anything. I tried various brand of media (sony, fujifilm, maxell plus) so I don't think it's that. I am also unable to read dvd (video or data), while cds are fine somehow (for reading, that is). DVDs are recognized though, I just can't read/write data on them.
Here's what k3b has to say about my burner: | Code: |
Blockdevice: /dev/hdc
Generic device:
Vendor: PIONEER
Description: DVD-RW DVR-115D
Version: 1.13
Write speed: 27700
Profiles: DVD-ROM, DVD-R Sequential, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW
Read Cap: DVD-ROM, DVD-R, DVD-R Sequential, DVD-R Dual Layer, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RW, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+RW Dual Layer, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW
Write Cap: DVD-R, DVD-R Sequential, DVD-R Dual Layer, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RW, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-R, CD-RW
Writing modes: SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite, Layer Jump
Reader aliases: /dev/hdc
|
And here what it says when I simulate a burning operation: | Code: |
(K3bDevice::Device) /dev/hdc: GET CONFIGURATION length det failed.
(K3bDevice::Device) /dev/hdc: GET CONFIGURATION length det failed.
(K3bDevice::Device) /dev/hdc: GET CONFIGURATION length det failed.
(K3bDevice::Device) /dev/hdc: GET CONFIGURATION length det failed.
(K3bDevice::Device) /dev/hdc: GET CONFIGURATION length det failed.
(K3bDevice::Device) /dev/hdc: GET CONFIGURATION length det failed.
First sec data area: 43:41:33 (LBA 196608) (402653184
Last sec data area: 00:00:00 (LBA 0) (0 Bytes)
Last sec layer 1: 00:00:00 (LBA 0) (0 Bytes)
Layer 1 length: 00:00:01 (LBA 1) (2048 Bytes)
Layer 2 length: 00:00:00 (LBA 0) (0 Bytes)
(K3bDevice::Device) /dev/hdc: GET CONFIGURATION length det failed.
(K3bDevice::Device) /dev/hdc: GET PERFORMANCE dataLen = 72
(K3bDevice::Device) /dev/hdc: GET PERFORMANCE successful with reported length: 68
(K3bDevice::Device) /dev/hdc: Number of supported write speeds via GET PERFORMANCE: 4
(K3bDevice::Device) /dev/hdc : 16620 KB/s
(K3bDevice::Device) /dev/hdc : 11080 KB/s
(K3bDevice::Device) /dev/hdc : 8310 KB/s
(K3bDevice::Device) /dev/hdc : 5540 KB/s
(K3bDevice::HalConnection) lock queued for /org/freedesktop/Hal/devices/storage_model_PIONEER_DVD_RW_DVR_115D
(K3bDevice::HalConnection) unlock queued for /org/freedesktop/Hal/devices/storage_model_PIONEER_DVD_RW_DVR_115D
(K3bDevice::ScsiCommand) failed:
command: PREVENT ALLOW MEDIUM REMOVAL (1e)
errorcode: 0
sense key: NO SENSE (2)
asc: 0
ascq: 0
(K3bDevice::ScsiCommand) failed:
command: START STOP UNIT (1b)
errorcode: 70
sense key: NOT READY (2)
asc: 4
ascq: 7
(K3bDevice::ScsiCommand) failed:
command: START STOP UNIT (1b)
errorcode: 70
sense key: NOT READY (2)
asc: 4
ascq: 7
First sec data area: 43:41:33 (LBA 196608) (402653184
Last sec data area: 43:41:48 (LBA 196623) (402683904 Bytes)
Last sec layer 1: 00:00:00 (LBA 0) (0 Bytes)
Layer 1 length: 00:00:01 (LBA 1) (2048 Bytes)
Layer 2 length: 43:41:48 (LBA 196623) (402683904 Bytes)
DiskInfo:
Mediatype: DVD-R Sequential
Current Profile: DVD-R Sequential
Disk state: incomplete
Empty: 0
Rewritable: 0
Appendable: 1
Sessions: 1
Tracks: 1
Layers: 1
Capacity: 510:38:38 (LBA 2297888) (4706074624 Bytes)
Remaining size: 510:38:22 (LBA 2297872) (4706041856 Bytes)
Used Size: 00:00:16 (LBA 16) (32768 Bytes)
(K3bDevice::Device) /dev/hdc: GET PERFORMANCE dataLen = 72
(K3bDevice::Device) /dev/hdc: GET PERFORMANCE successful with reported length: 68
(K3bDevice::Device) /dev/hdc: Number of supported write speeds via GET PERFORMANCE: 4
(K3bDevice::Device) /dev/hdc : 16620 KB/s
(K3bDevice::Device) /dev/hdc : 11080 KB/s
(K3bDevice::Device) /dev/hdc : 8310 KB/s
(K3bDevice::Device) /dev/hdc : 5540 KB/s
|
And then I got a couple of these: | Code: |
(K3bDevice::ScsiCommand) failed:
command: READ (10) (28)
errorcode: 70
sense key: BLANK CHECK (8)
asc: 0
ascq: 0
(K3bDevice::Device) /dev/hdc: READ 10 failed!
|
I seem to remember removing that scsi emulation affair a loooong time ago, so why is k3b issuing scsi command? I tried searching the web and didn't really find anything convincing, save for a post suggesting that I have a non-mmc drive... The ramifications of this supposition are beyond my current knowledge 
Oh, and:
| Code: |
$ uname -a
Linux marko 2.6.20-gentoo-r8 #9 Sat Jun 30 16:16:52 EDT 2007 x86_64 AMD Athlon(tm) 64 Processor 3000+ AuthenticAMD GNU/Linux
|
Last edited by yanos on Wed Jan 16, 2008 6:07 pm; edited 1 time in total |
|
| Back to top |
|
 |
yanos
Tux's lil' helper
Joined: 11 Sep 2003
Posts: 149
Location: montreal, canada
|
| Posted: Wed Jan 16, 2008 1:12 am Post subject: |
|
|
I found out by reading some post that cdrkit replaced cdrtools and that the former was deprecated for some reasons. I made the switch but it doesn't solve my problem. So I'm back to square one and don't know what to try next. Could it be a kernel issue? Any help would be greatly appreciated!
| Code: |
# hdparm -I /dev/hdc
/dev/hdc:
ATAPI CD-ROM, with removable media
Model Number: PIONEER DVD-RW DVR-115D
Serial Number: GKDP274958WL
Firmware Revision: 1.13
Standards:
Likely used CD-ROM ATAPI-1
Configuration:
DRQ response: 50us.
Packet size: 12 bytes
Capabilities:
LBA, IORDY(can be disabled)
Buffer size: 64.0kB
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 *udma4
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=240ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* Power Management feature set
* PACKET command feature set
* DEVICE_RESET command
HW reset results:
CBLID- above Vih
Device num = 0 determined by the jumper
|
|
|
| Back to top |
|
|
paulbiz
Guru
Joined: 01 Feb 2004
Posts: 508
Location: St. Louis, Missouri, USA
|
| Posted: Wed Jan 16, 2008 2:07 am Post subject: |
|
|
Hi,
you probably already tried this, but... is it a permissions problem? What happens when you login as root and try to use the burner? |
|
| Back to top |
|
|
yanos
Tux's lil' helper
Joined: 11 Sep 2003
Posts: 149
Location: montreal, canada
|
| Posted: Wed Jan 16, 2008 4:58 pm Post subject: [SOLVED] Problems with my new Pioneer burner |
|
|
| paulbiz wrote: | Hi,
you probably already tried this, but... is it a permissions problem? What happens when you login as root and try to use the burner? |
Yeah, I verified that already. Thanks for your help but I just found what the problem was. I went to check the jumper of the drive to see if I accidently put two master device on the same bus or something similar. Turns out that no, I hadn't screw up like that, but after I repluged everything the drive started to work properly. So I think it was simply a matter of the ide cable not properly connected. All that head scratching for a stupid thing like that! Oh well... |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
