I've exactly the same problem here. Anyone have a solution yet?Quote:> I am not sure if there is something wrong with the ataraid in 2.4.19 (I am
> successfully using the ataraid/fastrak in the 2.4.18 kernel - custom
> compiled).
I've exactly the same problem here. Anyone have a solution yet?Quote:> I am not sure if there is something wrong with the ataraid in 2.4.19 (I am
> successfully using the ataraid/fastrak in the 2.4.18 kernel - custom
> compiled).
HTH
--
Sylpheed-claws/Win32: http://claws-w32.sf.net
---
# 20265_offboard.patch for linux kernel 2.4.19
# This is free software, licensed under the same version
# of GPL that is used by the rest of the linux-kernel.
#
# treat pdc20265 controllers (incorrectly;) as offboard,
# i.e. use /dev/ide2+3 rather than /dev/ide0+1
#
# 1. copy patch to /usr/src
# 2. cd to /usr/src/linux
# 3. apply with "patch -p1 < ../20265_offboard.patch"
#
diff -ur linux-2.4.19-org/Documentation/Configure.help linux-2.4.19/Documentation/Configure.help
--- linux-2.4.19-org/Documentation/Configure.help Fri Aug 16 11:56:18 2002
CONFIG_PDC202XX_FORCE
For FastTrak enable overriding BIOS.
+FastTrak Offboard Compatibility Setting
+CONFIG_PDC20265_OFFBOARD
+ Force treatment as offboard controller, i.e. keep the order of
+ /dev/ide devices as in 2.4.18 and prior.
+ Enable this option, if your controller isnt detect anymore after
+ updating to kernel 2.4.19.
+ Also disable the "Special FastTrak Feature"
+
SiS5513 chipset support
CONFIG_BLK_DEV_SIS5513
This driver ensures (U)DMA support for SIS5513 chipset family based
diff -ur linux-2.4.19-org/drivers/ide/Config.in linux-2.4.19/drivers/ide/Config.in
--- linux-2.4.19-org/drivers/ide/Config.in Fri Aug 16 11:56:27 2002
dep_bool ' PROMISE PDC202{46|62|65|67|68|69|70} support' CONFIG_BLK_DEV_PDC202XX $CONFIG_BLK_DEV_IDEDMA_PCI
dep_bool ' Special UDMA Feature' CONFIG_PDC202XX_BURST $CONFIG_BLK_DEV_PDC202XX
dep_bool ' Special FastTrak Feature' CONFIG_PDC202XX_FORCE $CONFIG_BLK_DEV_PDC202XX
+ dep_bool ' FastTrak Offboard Compatibility Setting' CONFIG_PDC20265_OFFBOARD $CONFIG_BLK_DEV_PDC202XX
dep_bool ' ServerWorks OSB4/CSB5 chipsets support' CONFIG_BLK_DEV_SVWKS $CONFIG_BLK_DEV_IDEDMA_PCI $CONFIG_X86
dep_bool ' SiS5513 chipset support' CONFIG_BLK_DEV_SIS5513 $CONFIG_BLK_DEV_IDEDMA_PCI $CONFIG_X86
dep_bool ' SLC90E66 chipset support' CONFIG_BLK_DEV_SLC90E66 $CONFIG_BLK_DEV_IDEDMA_PCI $CONFIG_X86
diff -ur linux-2.4.19-org/drivers/ide/ide-pci.c linux-2.4.19/drivers/ide/ide-pci.c
--- linux-2.4.19-org/drivers/ide/ide-pci.c Fri Aug 16 11:56:27 2002
#ifndef CONFIG_PDC202XX_FORCE
{DEVID_PDC20246,"PDC20246", PCI_PDC202XX, NULL, INIT_PDC202XX, NULL, {{0x00,0x00,0x00}, {0x00,0x00,0x00}}, OFF_BOARD, 16 },
{DEVID_PDC20262,"PDC20262", PCI_PDC202XX, ATA66_PDC202XX, INIT_PDC202XX, NULL, {{0x00,0x00,0x00}, {0x00,0x00,0x00}}, OFF_BOARD, 48 },
+#ifdef CONFIG_PDC20265_OFFBOARD
+ {DEVID_PDC20265,"PDC20265", PCI_PDC202XX, ATA66_PDC202XX, INIT_PDC202XX, NULL, {{0x00,0x00,0x00}, {0x00,0x00,0x00}}, OFF_BOARD, 48 },
+#else
{DEVID_PDC20265,"PDC20265", PCI_PDC202XX, ATA66_PDC202XX, INIT_PDC202XX, NULL, {{0x00,0x00,0x00}, {0x00,0x00,0x00}}, ON_BOARD, 48 },
+#endif
{DEVID_PDC20267,"PDC20267", PCI_PDC202XX, ATA66_PDC202XX, INIT_PDC202XX, NULL, {{0x00,0x00,0x00}, {0x00,0x00,0x00}}, OFF_BOARD, 48 },
#else /* !CONFIG_PDC202XX_FORCE */
{DEVID_PDC20246,"PDC20246", PCI_PDC202XX, NULL, INIT_PDC202XX, NULL, {{0x50,0x02,0x02}, {0x50,0x04,0x04}}, OFF_BOARD, 16 },
1. Fix for promise RAID controllers not working as IDE controllers in 2.4.19
When an a promise raid 20267 (and probably others) is used as an IDE device
in 2.4.19 it won't detect using the non-raid driver as it would in 2.4.18.
(So it can be used as a high performance ide controller).
The problem lies in the addition of some ifdefs checking the status of
CONFIG_PDC202XX_FORCE in ide-pci.c. On line 672 an ifdef needed to be
changed
to an ifndef, a bug found way back in RC2, but when it was changed the ifdef
on line 405 got changed instead.
To get everthing working properly change
#ifndef CONFIG_PDC202XX_FORCE
on line 405 to
#ifdef CONFIG_PDC202XX_FORCE
and change
#ifdef CONFIG_PDC202XX_FORCE
on line 672 to
#ifdef CONFIG_PDC202XX_FORCE
I'd quote the origional posts by my entire network just went down.
TTYlater
David Hinkle
Chief Engineer
Derbyworks Systems
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
2. kill all processes belonging to a single user
3. Linux Kernel 2.4.18 and 2.4.19 problems
4. Changing delete key for emacs
5. Problem with 2.4.19 multiple root floppy disks- 2.4.18 works.
7. Kernel Panic 2.4.18 - 2.4.19-rc3 when using iptables
9. kernel 2.4.18 + 2.4.19-pre10 patch
10. Announce: kdb v2.3 i386 updates for kernels 2.4.18 and 2.4.19
11. OOPS with kernels 2.4.18 2.4.19 2.4.20
12. Compilation problem: SiS 630 dri driver (2.4.18 and 2.4.19-rc3)
13. strange file corruption problem with 2.4.18 & 2.4.19