http://qa.mandrakesoft.com/show_bug.cgi?id=1268
------- Additional Comments From [EMAIL PROTECTED] 2003-03-29 22:40 ------- Same problem here too with mdk 9.0 (final). I use the Promise FastTrak 133 Lite of my MSI 845 Ultra ARU motherbord. It use to work fine with mdk 9.0 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: This sorta works in 9.0, but not 9.1. I JUST bought an Asus A7V333 with onboad RAID, using the Promise Fasttrack 133 Lite - PDC20276 chip. When installing Mandrake 9.0, I can see both drives in the mirror, but not with MDK 9.1b3. Mandrake 9.0 dmesg during install shows: PDC20276: IDE controller on PCI bus 00 dev 30 PCI: Found IRQ 7 for ddevice 00:06.0 PCI: Sharing IRQ 7 with 00:09.0 PDC20276: chipset revision 1 PDC20276: (U)DMA Burst Bit ENABLES Primary MASTER Mode Secondary MASTER Mode With Mandrake 9.1b3, I get the following from dmesg during install: PDC20276: IDE controller at PCI slot 0:06.0 PDC20276: chipset revision 1 PDC20276: not 100% native mode: will probe irqs later PDC20276: neither IDE port enabled (BIOS) I moved the HD to the 'regular' onboard controller, and successfully installed Mandrake 9.1b3. I then downloaded the current cooker kernel source from rpmfind.net, linux-2.4.21pre4-1. I set CONFIG_PDC202XX_FORCE=y (which in the menu basically says "use FastTrack"), and built ATARAID into the kernel. I changed lilo/fstab to mount /dev/ataraid/disc0/part1 instead of /dev/hda1, rehooked /dev/hda1 to the RAID (It's just RAID 0), duped the disk to /dev/hdc within the FastTrak BIOS. I'm now booting off my Mirrored Array - Master 0 became /dev/hda when the driver recognized the drives on the PDC20276 controller - whew! (/dev/ataraid/disc0/part1). Is it possible to allow the user to choose ataraid (assuming the driver loads properly) for the root disk? Selecting the ataraid module in the Mandrake 9.0 install didn't produce a /dev/ataraid during install to install to, and ataraid didn't show up in lsmod (but I didn't spend more than a single boot looking at that) I'm not sure why the install kernel can't find the drives, while the kernel I compiled could. But here's your bug report :) If necessary, I can provide a diff of my kernel config, and the .config that came with the kernel-source rpm, but AFAICS, the only real change is the CONFIG_PDC202XX_FORCE=y. Rick
