Hi Steve, with your files from Promise you got also a file it's called "ft.pat" this is a file to patch the kernel -> try this ! I haven't tested, but in the readme-file from Promise (shipped with the promise- drivers for Suse Linux 7.1) is described that you must patch the kernel if you want to recompile it to a new kernel ! if it doesn't work, write a message to the promise company, they have messed up that ! But if it works, than only with Kernel 2.4.2, if you install any other Kernel like 2.4.8 (the actually version) you are not in luck, there is no chance to bring up the drivers to work with other kernelversions ! Promise's support to Linux is very poor !! Only the C-Sourcecodes can allways solve that problem, but they don't want to publish the sources ! The promise company doesn't trust us, they think we are selling their mental property, but we are only want to run our systems with linux well ! If a company subordinates their customers something similar, then everything is already lost ! All linuxers they are "running" promise-products should write up an email ten times a day and send it to the promise support or better we throw all fasttracks into the trash can, then they will change there mind, maybe ! Best regards Matthias Noll (mn@xxxxxxxxx) -----Ursprüngliche Nachricht----- Von: "Steve Elliott" <steve@xxxxxxxxxxxxxxxxx> An: <ataraid-list@xxxxxxxxxx> Gesendet: Donnerstag, 16. August 2001 06:03 Betreff: Kernel Compile > G'day from Australia, > I have a promise fastrak 100, and 4 60 gig disk drives. > Currently i have several of these boxes configured as raid 0 with stock > red hat 7.1 > > I performed the install following the doc on > http://www.thedukeofurl.org/reviews/misc/promisehowtorh71/2.shtml > > The key to getting it to work and boot from the raid is the script ( > setup_ft )that needs to be run @ the end of the red hat install. It is > contained in the disk 2 of the promise drivers. > > # chroot /mnt/sysimage > # mount -t vfat /dev/fd0 /mnt/floppy > # cd /mnt/floppy > # ./setup-ft > > setup_ft contains > > > #!/bin/sh > > cp ./modules/ft.o /lib/modules/2.4.2-2/kernel/drivers/scsi/ > /sbin/mkinitrd --with ft -f /boot/initrd-ftup24.img 2.4.2-2 > > cp -f ./script/sed_script /tmp/sed_script > ROOT=`grep 'root=/dev/' /etc/lilo.conf | sed '1!d' ` > echo " "$ROOT"\\" >> /tmp/sed_script > echo " initrd=/boot/initrd-ftup24.img\\" >> /tmp/sed_script > echo " " >> /tmp/sed_script > > echo "Run LILO :" > sed '/default=linux/d' /etc/lilo.conf > /etc/tmp1.ft > sed -f /tmp/sed_script /etc/tmp1.ft > /etc/tmp.ft > mv /etc/lilo.conf /etc/lilo.conf.bak > mv /etc/tmp.ft /etc/lilo.conf > sync;sync;sync; > /sbin/lilo > > echo "***********************************************" > echo "* Promise FastTrak Series *" > echo "* Linux Driver v1.20 build 5 (2.4.2-2 UP) *" > echo "* has been installed completely *" > echo "***********************************************" > rm -f /lib/modules/2.4.2-2/kernel/drivers/scsi/ft.o > rm -f /tmp/sed_script /etc/tmp1.ft > sync;sync;sync; > > > > Now if i want to compile my own kernels ( i require firewire support ), > every time i compile and reconfigure the system for the new kernel, when > the machine reboots it does not see the raid and will not boot. > > As i am a fledgling in the world of kernel compiles, i require some > advices as to how i can compile my own kernel and still get the system > to boot from the raid ? I did have a play with initrd etc but to no > avail. :( > > Any help much appreciated. > > Steve > > > > _______________________________________________ > > Ataraid-list@xxxxxxxxxx > https://listman.redhat.com/mailman/listinfo/ataraid-list >
