Same errors here, I have given up on getting this stuff to work. Promise is not helping us, the GPL piece of the driver that should compile an ft.o module does not compile at all. RedHat is not really any help either, so we are stuck. I wanted to use this system as a development server for my Intranet. We are currently developing some simulation software that is being ported to Linux. I have no ports free on the normal IDE channels as they are taken by two cd/dvd burners a dvd reader and another device. I was hoping to drive my hard disks of the "raid" controllers. I am going to file a request with RH, we are paying for support, but am afraid it will most likely not result in a solution before the end of the month. Only other option is to go SCSI on this mother board. Aldert E. van der Laan London, Ontario Canada -----Original Message----- From: Eric Christensen [mailto:eric@xxxxxxxxxxxxxxxxxxx] Sent: December 29, 2002 12:20 AM To: ataraid-list@xxxxxxxxxx Subject: read_intr / DriveStatusError errors with Promise FT 100 Hello, I am following Murty's helpful HOW-TO to install a SMP system over a FastTrak 100 Lite on-board RAID. Rather than a mirror, though, I am trying a stripe set with 2 drives. These are the only drives on the system other than a CD-ROM on the second regular IDE channel. Everything goes well to start: 7.3 base installation goes well and I can boot with the FastTrak module and ramdisk. Build of a 2.4.19 kernel is fine, I based mine on the config provided by Murty. New .19 kernel is self contained using the ataraid and Promise support, no need for ramdisk or Promise module. It boots and seems to function ok but a slew of drive errors occur on boot.. >> Dec 28 22:22:12 localhost kernel: ead_intr: error=0x04 { DriveStatusError } Dec 28 22:22:12 localhost kernel: hde: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error } Dec 28 22:22:12 localhost kernel: hde: read_intr: error=0x04 { DriveStatusError } Dec 28 22:22:12 localhost kernel: hde: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error } Dec 28 22:22:12 localhost kernel: hde: read_intr: error=0x04 { DriveStatusError } Dec 28 22:22:12 localhost kernel: ide2: reset: success << etc. etc. etc. Using Murty's formula and after looking at the /proc/pci, I had to config my lilo as follows: >> image=/boot/vmlinuz-2.4.19 label=my19 read-only root=/dev/ataraid/d0p2 append="ide2=0xa400,0xa802,10 ide3=0xac00,0xb002,10" (BTW, I also tried ide0 and ide1 and errors reflect hda rather than hde) << I have not yet updated my lilo binaries as Murty prescribes. I want to first make sure I am not doing something wrong or heading into trouble. When I boot with my old .18-3 kernel with the FastTrak module, I get no errors. These are new IBM drives and even though the error messages above often indicate impending doom, I think they are fine. Thanks for any help. Happy New Year. -esc _______________________________________________ Ataraid-list@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/ataraid-list
