Often unresolved symbols can mean you are running the wrong version kernel for the driver. You might need to recompile the driver for the kernel you are using.
That means pointing the ld.so.conf file at the correct kernel libraries then compiling the source of the drivers (assuming the driver came as source) Marcus Liddle wrote: > > Hi all > > Is it bad in my boot.log file I read: > > <date> <host> depmod: *** unresolved symbols in > /lib/modules/2.4.7-10/kernel/driver..... > <date> <host> rc.sysinit: finding module dependencies: succeeded > > Yesterday I talked about getting IDE RAID motherboards working > > - we found a driver in the most obvious place ...the manufacture web site > ...this is after we searched the entire internet ;) > > The driver basicly fakes SCSI stuff -- thus making ide raid possible > <smoke and mirrors> > > It installs with grub paramaters and it does boot. > > Am I correct in thinking the boot log line talking about unresolved symbols > is bad ??? ...or is the saving grace in the next line ?? > > cheers > Marcus > -- > Tutor Assistant [mailto:[EMAIL PROTECTED]] > Dept. of Computer Science University of Canterbury > Phone: +64 3 366-7001 ext: 7871 Office: 323 > [ http://www.cosc.canterbury.ac.nz/~marcus/index.html ] -- Zane Gilmore, Analyst / Programmer Information Services Section, Information Technology Dept, University of Canterbury Private Bag 4800 Christchurch New Zealand phone +64-3-364 2987 extn 7895 Fax 3642222
