Messages in this thread | | | Date | Mon, 2 Aug 2004 10:36:34 -0400 (EDT) | From | "Richard B. Johnson" <> | Subject | Re: HPT 366 - Why does HPT's driver freeze the kernel (2.4.26)? |
| |
On Mon, 2 Aug 2004, war wrote:
> # make > gcc -DHIGHPOINT -DDRIVER_VERSION=\"1.31\" -DMODVERSIONS -DMODULE -DLINUX > -D__KER > NEL__=1 -DCONFIG_PCI -D__BOOT_KERNEL_SMP=0 -D__BOOT_KERNEL_UP=1 > -D__MODULE_KERNE > L_i686=1 -DDPLL_SWITCH -DFORCE_133 -DDRIVER_REBUILD -DSUPPORT_ARRAY > -DSUPPORT_ > IOCTL -DSUPPORT_ALARM -O2 -I/usr/src/linux/include > -I/usr/src/linux/include/asm- > i386 -I/usr/src/linux/drivers/scsi -Wall -Wstrict-prototypes > -fomit-frame-pointe > r -c hpt.c > hpt.c: In function `hpt_copy_array_info': > hpt.c:2948: warning: int format, long unsigned int arg (arg 3) > as -o baseproc.o baseproc.s > ld -m elf_i386 -r hpt37x2lib.o hpt.o baseproc.o -o hpt37x2.o > > # insmod hpt37x2.o > hpt37x2.o: unresolved symbol scsi_unregister_module > hpt37x2.o: unresolved symbol scsi_register > hpt37x2.o: unresolved symbol scsi_register_module > hpt37x2.o: unresolved symbol scsi_unregister > hpt37x2.o: > Hint: You are trying to load a module without a GPL compatible license > and it has unresolved symbols. The module may be trying to access > GPLONLY symbols but the problem is more likely to be a coding or > user error. Contact the module supplier for assistance, only they > can help you. > > # modprobe scsi_mod > # insmod hpt37x2.o > <freeze> > > Read from remote host testhpt: Operation timed out > Connection to testhpt closed. > > Any ideas? > If I load the kernel's driver for the HPT3xxx card, it loads, but then it > does not see any drives. > > The card and driver(s) included with RedHat 7.3 worked perfectly, but it > seems that any other distribution (current) has serious problem. > > Can anyone suggest what is going wrong? > > Must it be booted ONLY with an initrd to properly setup the drives, or? > What is the problem with this card?
I think you are using a library:
> ld -m elf_i386 -r hpt37x2lib.o hpt.o baseproc.o -o hpt37x2.o ^^^^^^^^^^^^ ... that was compiled with another kernel version. You can't bypass the normal steps in module building. At the very least, remove all the '*.o' files before rebuilding, better yet, enable the driver in the .config file, do make clean; make oldconfig; make dep; make bzImage; make modules; make modules_install..... Use the resulting object in /lib/modules/`uname -r`/....
Cheers, Dick Johnson Penguin : Linux version 2.4.26 on an i686 machine (5570.56 BogoMips). Note 96.31% of all statistics are fiction.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |