content-class: urn:content-classes:message
Subject: New model of SanDisk compact flash not working
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Date: Mon, 24 Nov 2003 10:32:23 +0200
Message-ID: <0887314A0D67E14C8C255BEF09FC3D99501157@x-plor-mail.jhb-xplor>
Thread-Topic: New model of SanDisk compact flash not working
Thread-Index: AcOyZXu+E05GJyzBQGyEo41mlMM0Ng==
From: "gmlinux" <gmlinux@x-plor.com>
To: <linux-kernel@vger.kernel.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1253
Lines: 30

All,

I am running a SanDisk Compact Flash disk under linux 2.4.21. The
compact flash SDCFB-256-101-80 works 100%. The problem is this model has
been discontinued and replaced with an SDCFB-256-201-80. This has a new
internal controller it would seem. During kernel boot it will attempt to
detect the partitions on the drive, and hang at this point. The new
controller seems to support DMA, while the old one didn't. If I disable
DMA (ide=nodma), then the kernel will not hang, and will boot up
correctly. However, the drives are unusable. You cannot read/write from
them. Even an fdisk fails, it displays the partition table but when you
press 'q' to quit it hangs, and then begins sending kernel debug "hdc
lost interrupt".

I also get the following boot messages, which were not present on the
old model:
hdc: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: task_no_data_intr: error=0x04 { DriveStatusError }

I am running a stock standard 2.4.21.

Any ideas?

Regards
  Garth Marran
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/