I see you folks are struggling with the same issue I had for over two months. I do not want to discourage you, actually encourage you to keep posting your progress. It is important that RedHat will get native support for this in later releases. The only solution at this moment is to boot with a hard drive attached to your normal IDE channel and compile the new kernel with the ATA raid. There are many things that can go wrong as you have already discovered, even with the standard kernels in place..... I have been installing Phoebe (the Beta version of 8.1) and it is still not re-solved. For maybe all the wrong reasons I started looking for a version of Linux that does support the Promise 'raid' stuff out of the box. I have tested Debian with bf2.4 and no luck. I tried Suse and still no luck, all I got from user groups is to go back to previous versions. Last Friday I took a day off to focus on this issue in my lab. I installed a total different version of Linux called FreeBSD that does support the controller without going through all this hassle. True, it is not as clean and does not have the simple rpm installs, but it is stable. I have installed Apache and MySql on and backup software. Right now this server is sitting in my lab for further testing and is holding up perfect. I just wish.... You know... that my beloved RedHat would support this hardware. Looking at the new hardware at www.tomshardware.com I see a lot of motherboard manufacturers are using the Promise chipsets. This can not become an all Windows world!??? Aldert E. van der Laan London, Ontario Canada -----Original Message----- From: Alon Weinstein [mailto:alon@xxxxxxxx] Sent: February 19, 2003 10:37 AM To: ataraid-list@xxxxxxxxxx Subject: RE: Can't get Promise PDC20276 to go with ataraid > My lilo.conf now looks like this. > > > prompt . . > boot=/dev/sda . . > image=/boot/vmlinuz-2.4.20 > label=2.4.20 > read-only > root=/dev/ataraid/d0p2 > append="ide2=0xb400,0xb002,9 ide3=0xa800,0xa402,9 console=ttyS0,57600 console=tty0" > > > image=/boot/vmlinuz-2.4.18-14 > initrd=/boot/initrd-2.4.18-14.img > label=linux > read-only > append="ide0=0x1f0,0x3f6,14 ide1=0x170,0x376,15 ide2=0 ide3=0 ide4=0 ide5=0 ide6=0 ide7=0 ide8=0 ide9=0 hdc=ide-scsi root=LABEL=/" I can't tell much from the Kernel output. I bet some more experienced user could help with that. Some thoughts -- 1. Login to your computer using your old kernel and do "df -k" -- make sure your "/" (root partition) is mounted to /dev/sda2 -- if it's mounted to some other "sda", like /dev/sda1 then you should change the "root=" part in the new kernel's section in lilo.conf to reflect that number -- i.e: /dev/sda1 --> "root=/dev/ataraid/d0p1" 2. Are you sure you compiled the ATARAID module statically, i.e not as a module? just a long shot. That's about it -- I'm out of ideas :-) Good luck. Alon. _______________________________________________ Ataraid-list@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/ataraid-list
