[Debburn-devel] Problem with Samsung CDRW/DVD SM-308B
John Talbut
john at dpets.demon.co.uk
Fri May 11 06:41:34 UTC 2007
Thanks for your response, Eduard.
You Bloch wrote:
<snip>
>
> I have few ideas, but only fuzzy ones:
>
> - try setting the magic CDR_NODMATEST variable to something.
I have
CDR_NODMATEST=true
in /etc/environment
and set lists :CDR_NODMATEST=true
> - try the same drive with the same media on an USB2.0 adapter.
I want to avoid going in to the hardware.
>
> - something is wrong with your IDE driver. Maybe there is no native
> driver for your chipset at all? I would expect messages like in the
> example below, but there are none. I assume that the generic PCIIDE
> driver is used instead, not sure.
>
> VP_IDE: IDE controller at PCI slot 0000:00:0f.1
> ACPI: PCI Interrupt Link [ALKA] enabled at IRQ 20
> ACPI: PCI Interrupt 0000:00:0f.1[A] -> Link [ALKA] -> GSI 20 (level, low) -> IRQ 20
> VP_IDE: chipset revision 6
> VP_IDE: not 100%% native mode: will probe irqs later
> VP_IDE: VIA vt8237 (rev 00) IDE UDMA133 controller on pci0000:00:0f.1
> ide0: BM-DMA at 0xd400-0xd407, BIOS settings: hda:DMA, hdb:DMA
> ide1: BM-DMA at 0xd408-0xd40f, BIOS settings: hdc:DMA, hdd:pio
I presume these would be in dmesg.
The drive is on ide1
My dmesg has the lines:
Probing IDE interface ide0...
hda: ST320413A, ATA DISK drive
Probing IDE interface ide1...
hdc: SAMSUNG CDRW/DVD SM-308B, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 39102336 sectors (20020 MB) w/512KiB Cache, CHS=38792/16/63
hda: cache flushes not supported
hda: hda1 hda2 < hda5 > hda3
hdc: ATAPI 32X DVD-ROM CD-R/RW drive, 2048kB Cache
Uniform CD-ROM driver Revision: 3.20
I use all in kernel drivers. In my kernel configuration I have:
CONFIG_GENERIC_ISA_DMA=y
CONFIG_ISA_DMA_API=y
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
CONFIG_BLK_DEV_CMD640=y
# CONFIG_BLK_DEV_CMD640_ENHANCED is not set
# CONFIG_BLK_DEV_IDEPNP is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
# CONFIG_BLK_DEV_GENERIC is not set
# CONFIG_BLK_DEV_OPTI621 is not set
CONFIG_BLK_DEV_RZ1000=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_ATIIXP is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
CONFIG_BLK_DEV_CS5520=y
CONFIG_BLK_DEV_CS5530=y
# CONFIG_BLK_DEV_CS5535 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_JMICRON is not set
# CONFIG_BLK_DEV_SC1200 is not set
# CONFIG_BLK_DEV_PIIX is not set
# CONFIG_BLK_DEV_IT821X is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
# CONFIG_IDE_ARM is not set
CONFIG_IDE_CHIPSETS=y
#
# Note: most of these also require special kernel boot parameters
#
# CONFIG_BLK_DEV_4DRIVES is not set
# CONFIG_BLK_DEV_ALI14XX is not set
# CONFIG_BLK_DEV_DTC2278 is not set
# CONFIG_BLK_DEV_HT6560B is not set
# CONFIG_BLK_DEV_QD65XX is not set
# CONFIG_BLK_DEV_UMC8672 is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_BLK_DEV_HD is not set
Is there anything else I should be looking for?
> - you should really make sure that DMA mode works. I know about at
> least some Benq drives that confuse the kernel by returning answers
> which are not appropriate for non-DMA mode _while_ running in non-DMA
> mode.
How can I check this?
Can we take a diagnostic approach?
When I try to burn a disk I get these messages (see
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=416388 ):
Mar 27 10:38:23 localhost kernel: hdc: irq timeout: status=0xd0 { Busy }
Mar 27 10:38:23 localhost kernel: ide: failed opcode was: unknown
Mar 27 10:38:23 localhost kernel: hdc: ATAPI reset complete
Mar 27 10:39:03 localhost kernel: hdc: irq timeout: status=0x80 { Busy }
Mar 27 10:39:03 localhost kernel: ide: failed opcode was: unknown
etc., for ever. There seems to be two problems, the initial failure then the
going into a loop. I am interested in the first, since presumably if that could
be solved Wodim would work for me and the second problem would not occur.
However, I guess that others should be concerned about the second since
something going wrong here should not cause a loop with the potential to bring
the whole system down.
So going back to the first problem, what do these lines mean? i.e. "hdc: irq
timeout: status=0xd0 { Busy }" and "ide: failed opcode was: unknown"
How can I find out more about what is going on?
Regards
John
More information about the Debburn-devel
mailing list