libata - DMA problems ICH7 rev 02
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 6 lines · Jan Niklas Hasse
Quoted 3 lines · Jan Niklas Hasse
Quoted 2 lines
It looks like you have the hard drive and the burner on the same IDE channel? Such problems are unavoidable in this setup since commands to one device on the channel can't execute while the other device is busy (especially for long commands like finalizing the disc). It would be better to move the drives onto separate channels.
As I have a notebook, I think I can't do that, can I?
This is the exact situation cdrecord's -immed option was designed for. "wodim"/cdrkit should have inherited it. It sets a flag in the commands to avoid blocking, though the documentation I read said it was slightly experimental.
Quoted 6 lines · Jan Niklas Hasse
Quoted 3 lines · Jan Niklas Hasse
Quoted 2 lines
It looks like you have the hard drive and the burner on the same IDE channel? Such problems are unavoidable in this setup since commands to one device on the channel can't execute while the other device is busy (especially for long commands like finalizing the disc). It would be better to move the drives onto separate channels.
As I have a notebook, I think I can't do that, can I?
This is the exact situation cdrecord's -immed option was designed for. "wodim"/cdrkit should have inherited it. It sets a flag in the commands to avoid blocking, though the documentation I read said it was slightly experimental.