I wrote:
> [Can't get Linux to boot with PDC20262 controller. One of disks is a
> Quantum Fireball Plus.]
Malcom Mallardi posted a note around the same time describing the same
problem. Wayne Whitney suggested that Malcom add his disk to the "problem
disk" list in pdc202xx.c, and Malcom reports that it worked. I did the
same thing for my disk, with the same results.
I enclose two patches against the 2.4.14 kernel. The first patch just adds
both problem disks to the list. The second assumes that all disks in the
appropriate Quantum families are a problem. My vote is for the second one.
Patch 1:
--- drivers/ide/pdc202xx.c.ori Wed Nov 14 18:22:27 2001
+++ drivers/ide/pdc202xx.c Wed Nov 14 20:57:13 2001
@@ -230,7 +230,9 @@
"QUANTUM FIREBALLP KA6.4",
"QUANTUM FIREBALLP LM20.4",
"QUANTUM FIREBALLP KX20.5",
+ "QUANTUM FIREBALLP KX27.3",
"QUANTUM FIREBALLP LM20.5",
+ "QUANTUM FIREBALLP LM30.0",
NULL
};
Patch 2:
--- drivers/ide/pdc202xx.c.ori Wed Nov 14 18:22:27 2001
+++ drivers/ide/pdc202xx.c Wed Nov 14 21:20:09 2001
@@ -225,12 +225,18 @@
byte pdc202xx_proc = 0;
+/*
+ * Problems have been reported with the following Quantum Fireball Plus drives:
+ * KA 6.4GB, KX 20.5GB, 27.3GB, LM 20.4GB, 20.5GB and 30.0GB. Quantum's
+ * datasheets suggest that all drives in a series (KA, KX and LM) have the
+ * same design. It seems prudent to identify them all here.
+ */
+
const char *pdc_quirk_drives[] = {
"QUANTUM FIREBALLlct08 08",
- "QUANTUM FIREBALLP KA6.4",
- "QUANTUM FIREBALLP LM20.4",
- "QUANTUM FIREBALLP KX20.5",
- "QUANTUM FIREBALLP LM20.5",
+ "QUANTUM FIREBALLP KA",
+ "QUANTUM FIREBALLP KX",
+ "QUANTUM FIREBALLP LM",
NULL
};
-
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/
This archive was generated by hypermail 2b29 : Thu Nov 15 2001 - 21:00:41 EST