plustek@linuxhacker.org

Dave Croal wrote:
> 
> 
> I checked that parport_pc is loaded.
> Proc fs is enabled and mounted too.
> 
> I don't get unresolved symbols today, now I get:
> 
> [root@croalnotebook plustek_driver]# make load
> /sbin/modprobe pt_drv || exit 1
> /lib/modules/2.4.3-20mdk-win4lin/misc/pt_drv.o: init_module: Success
> Hint: insmod errors can be caused by incorrect module parameters,
> including invalid IO or IRQ parameters
> /lib/modules/2.4.3-20mdk-win4lin/misc/pt_drv.o: insmod
> /lib/modules/2.4.3-20mdk-win4lin/misc/pt_drv.o failed
> /lib/modules/2.4.3-20mdk-win4lin/misc/pt_drv.o: insmod pt_drv failed
> make: *** [load] Error 1
> 
> IIRC it is after a reboot that the  unresolved symbols happen. BTW I did
> update my modules.conf and did run depmod.
> 
> I also noticed that make load fails to create the /dev/pt_drv* nodes,
> guess it doesn't make it that far.
> 
> Are you willing to send me a copy of your pt_drv.o to try? I am running
> gcc 2.96,  kernel 2.4.3mdk stock on an AMD K6-450 (i586).
> 
> Am willing to try any and all legal suggestions. Thanks for your help.
> 
> Dave Croal


I will send it to you if you want, but I have the debug turned on
so it is large (~2 MB). I will first rebuild it with debug off so
it is smaller and check that that works. The other thing you could
check is in the ../h/plustek_scan.h file, near the beginning. Just
before the

 #define _OUTB_CTRL..      outb_p... 

statements there is an 

#if 1 or #if 0 statement. 

If it is 0, change it to 1 and rebuild the driver. I would also be
sure the outb (lower case on right hand side of statement) is
outb_p (same for inb -> inb_p). There seem to be timing issues
involved here; I have only had consistent success with the outb_p
statements (they put in a slight delay). Since the /dev/pt_drv do
not seem to be created by the install, you might want to create
them by hand (mknod /dev/pt_drv c 40 0 at least).

	Kevin