Hi Thanks for your advice. I sourced, downloaded and printed your handy howto. Followed the guidelines except that I used RH73, the latest promise drivers and kernel 2.4.19. All worked well and it seems that it's stable. What I'm a bit unsure of is that I copied the sample .686 config file from the 2.4.18-3 src as the 2.4.19's .config. And, out of paranoia I left out the Special UDMA/FastTrak Features unchecked. Funnily enough the make menuconfig did not list support for the 20276 but the chipset is listed in both the changelog and the c source. Thanks once again Brendon Caligari --- Murty Rompalli <murty@xxxxxxxxxxxxxxx> wrote: > > Hi > I conclude you are running Promise RAID using their proprietary > driver, > i.e. /dev/sda etc. Well, if everything works then ignore the error > you are > getting. The driver is already loading through initrd supplied in > lilo.conf. This initrd is created when you chose to install Promise > raid. So, even if the module version does not load, you can ignore. > > Regarding whether to rely on Promise raid or not, I chose to rely to > Linux > native ataraid because I can see the source and understand what its > doing. I did experience strange scsi timeout errors with Promise > raid. > > Murty Rompalli > > On Tue, 20 Aug 2002, Brendon Caligari wrote: > > > > > I have just been asked to install RH73 on a gigabyte P4 > > GA-81RXP motherboard sporting an onboard > > PDC20276 / MBFastTrak133 Lite adapter. The idea > > is to mirror two IDE disks (40Gb maxtors). > > > > I downloaded the drivers and followed the instructions, and > > RH73 installs well. However, during bootup (or any > > subsequent "depmod -a") laments with unresolved symbols: > > <quote> > > depmod: *** Unresolved symbols in /lib/modules/2.4. > > 18-3/kernel/drivers/scsi/FastTrak.o > > </quote> > > > > The same thing happens on RH72. > > > > I'm a bit confused here as besides this error everything > > else 'seems' to be working well (system installed on the > > raided (and only) hard disks). > > > > Should I just proceed and ignore the error? Should I > > trust the promise raid and filesystem? Is there a good > > reason and a solution? > > > > Getting any help from the vendors is close not really an > > option as promise say it's a third party product, and there > > isn't the slightest mention of linux on gigabyte's web sites. > > > > B. > > > > > >
