Using "linux debconf/priority=medium" I left everything default but just
turned off the "piix" module and everything works fine.
With the "piix" module, I found the following in dmesg output:
------------------
ide: late registration of driver.
PIIX4: IDE controller at PCI slot 00:07.1
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x0860-0x0867, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0x0868-0x086f, BIOS settings: hdc:DMA, hdd:pio
hda: IBM-DADA-26480, ATA DISK drive
blk: queue c8868a80, I/O limit 4095Mb (mask 0xffffffff)
hdc: TOSHIBA CD-ROM XM-1802B, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: attached ide-disk driver.
hda: 12685680 sectors (6495 MB) w/460KiB Cache, CHS=13424/15/63,
UDMA(33)
Partition check:
/dev/ide/host0/bus0/target0/lun0: [PTBL] [789/255/63] p1 p2 < p5 >
hdc: attached ide-cdrom driver.
hdc: ATAPI 24X CD-ROM drive, 128kB Cache, DMA
Uniform CD-ROM driver Revision: 3.12
cs: IO port probe 0x0100-0x04ff: excluding 0x210-0x217 0x220-0x22f
0x378-0x37f 0x388-0x38f 0x4d0-0x4d7
cs: IO port probe 0x0800-0x08ff: clean.
cs: IO port probe 0x0c00-0x0cff: clean.
cs: IO port probe 0x0a00-0x0aff: clean.
ISO 9660 Extensions: Microsoft Joliet Level 3
hdc: DMA interrupt recovery
hdc: lost interrupt
ISOFS: changing to secondary root
hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdc: status error: error=0x00
hdc: drive not ready for command
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: status timeout: status=0xd0 { Busy }
hdc: status timeout: error=0x04Aborted Command
hdc: DMA disabled
hdc: drive not ready for command
hdc: ATAPI reset complete
------------------
Without the "piix" module, the following is in dmesg output:
------------------
ide: late registration of driver.
hda: IBM-DADA-26480, ATA DISK drive
hdc: TOSHIBA CD-ROM XM-1802B, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: attached ide-disk driver.
hda: 12685680 sectors (6495 MB) w/460KiB Cache, CHS=13424/15/63
Partition check:
/dev/ide/host0/bus0/target0/lun0: [PTBL] [789/255/63] p1 p2 < p5 >
hdc: attached ide-cdrom driver.
hdc: ATAPI 24X CD-ROM drive, 128kB Cache
Uniform CD-ROM driver Revision: 3.12
cs: IO port probe 0x0100-0x04ff: excluding 0x210-0x217 0x220-0x22f
0x378-0x37f 0x388-0x38f 0x4d0-0x4d7
cs: IO port probe 0x0800-0x08ff: clean.
cs: IO port probe 0x0c00-0x0cff: clean.
cs: IO port probe 0x0a00-0x0aff: clean.
ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660 Extensions: RRIP_1991A
------------------
What's weird is that the installer can't recover from the CDROM DMA
error even though the kernel has (or at least it seems to). After the
CDROM error, I can open a console and list files on the CDROM.
Depending on what file I open, I can hear the CDROM spinning up and
accessing things.
Any ideas on how to get the installer to recover from this condition?
Thanks,
Will
> -----Original Message-----
> From: Frans Pop [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, January 12, 2005 12:31 AM
> To: Will Lentz
> Cc: [EMAIL PROTECTED]
> Subject: Re: (fwd) RE: ide troubles
>
> On Wednesday 12 January 2005 01:58, you wrote:
> > 2) Using "linux debconf/priority=medium", I _only_ loaded
> the following
> > modules when detecting my CDROM (because now it asked me...):
> > ide-detect
> > ide-disk
> > ide-cd
> > isofs
> > That works - problem solved!
>
> Sounds like a driver conflict. If you can find out what extra module
> causes the problem when it's loaded additionally, that might help the
> kernel people to locate te source of the problem.
> This is largely trial and error, but your best bet is your
> ide-driver or
> the scsi modules.
>
> Cheers,
> FJP
>
>
