Hallo everybody,
I'm not subscribed to this list! But I read the archive from time to time.
In my linux box is a teac IDE CD-Rom drive. This is only recognised when no audio cd is in the drive while booting.
Is this a drive failure, or a kernel failure?
I didn't find any other on the net with the same problem. So hopefully someone of you can explain?
............
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
NFORCE3-150: IDE controller at PCI slot 0000:00:08.0
NFORCE3-150: chipset revision 165
NFORCE3-150: not 100% native mode: will probe irqs later
NFORCE3-150: 0000:00:08.0 (rev a5) UDMA133 controller
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
libata version 1.02 loaded.
sata_sil version 0.54
ACPI: PCI interrupt 0000:01:07.0[A] -> GSI 11 (level, low) -> IRQ 11
............
best regards
Lars T?uber
On Wed, Sep 15 2004, Lars T?uber wrote:
> Hallo everybody,
>
> I'm not subscribed to this list! But I read the archive from time to time.
>
> In my linux box is a teac IDE CD-Rom drive. This is only recognised
> when no audio cd is in the drive while booting. Is this a drive
> failure, or a kernel failure?
>
> I didn't find any other on the net with the same problem. So hopefully
> someone of you can explain?
>
> ............
> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
> NFORCE3-150: IDE controller at PCI slot 0000:00:08.0
> NFORCE3-150: chipset revision 165
> NFORCE3-150: not 100% native mode: will probe irqs later
> NFORCE3-150: 0000:00:08.0 (rev a5) UDMA133 controller
> ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
> libata version 1.02 loaded.
> sata_sil version 0.54
> ACPI: PCI interrupt 0000:01:07.0[A] -> GSI 11 (level, low) -> IRQ 11
> ............
Did 2.6.7 work? The ide-probe isn't finding your drive, that's very odd.
I think this is an issue with your hardware, not Linux. Perhaps you can
use the drive if you add hdc=cdrom to your boot line.
--
Jens Axboe
Dear Jens,
the problem accours also under 2.6.7.
But the hdc=cdrom options solves this problem (under 2.6.8.1):
..............
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
NFORCE3-150: IDE controller at PCI slot 0000:00:08.0
NFORCE3-150: chipset revision 165
NFORCE3-150: not 100% native mode: will probe irqs later
NFORCE3-150: 0000:00:08.0 (rev a5) UDMA133 controller
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
hdc: ATAPI cdrom (?)
Using anticipatory io scheduler
ide1 at 0x170-0x177,0x376 on irq 15
hdc: ATAPI 48X DVD-ROM drive, 256kB Cache
Uniform CD-ROM driver Revision: 3.20
..............
As written bevore the drive is not recognised only with an audio cd in it.
Thanks
Lars
On Wed, 15 Sep 2004 10:59:39 +0200
Jens Axboe <[email protected]> wrote:
>
> Did 2.6.7 work? The ide-probe isn't finding your drive, that's very odd.
> I think this is an issue with your hardware, not Linux. Perhaps you can
> use the drive if you add hdc=cdrom to your boot line.
>
> --
> Jens Axboe
>
--
Sch?ne Gr??e
Lars T?uber
On Wed, 15 Sep 2004 19:15:32 +0200
Lars T?uber <[email protected]> wrote:
> ...
>
> As written bevore the drive is not recognised only with an audio cd in
> it.
>
I've seen Teac drives blocking the Windows XP boot process when
certain discs are inserted. There were even freezes when copying files to
hard disk that did not occur when a different drive was used.
(Wasn't my machine, can't test anything.)
Obviously Teac's firmware has some issues.
Regards
Salut,
On Wed, Sep 15, 2004 at 08:03:11PM +0200, Marc Ballarin wrote:
> I've seen Teac drives blocking the Windows XP boot process when
> certain discs are inserted. There were even freezes when copying files to
> hard disk that did not occur when a different drive was used.
> (Wasn't my machine, can't test anything.)
I've had some issues with an old TEAC SCSI CD writer which was
somewhat weird:
On bootup it would only read CDs if, after bootup had completed, one
switched off its power and booted it again. (SCSI RESET was not
sufficient.)
So yes.
Tonnerre