plustek: Plustek OpticPro 12000T
Subject:
Re: Plustek OpticPro 12000T
From:
Gerhard Jaeger ####@####.####
Date:
23 Jan 2008 07:44:54 -0000
Message-Id: <200801230844.18929.gerhard@gjaeger.de>
On Tuesday 22 January 2008 11:29:38 Jastra wrote:
> >>> Have you done this step? /MakeModule.sh DEBUG=y ????
> >>
> >> yes, with debug
>
> I am just wondering, if the DEBUG works here. Is it normal, the script
> invoked with "DEBUG=yes" suggests to be started with "DEBUG=yes"?
yes it works, I don't get the pointer sorry.
> Then, the last step, the loading step:
> first I see
> /sbin/modprobe pt_drv || exit 1 ## I understand, attempt to load module
yes
> then
> rm -f /dev/pt_drv* ## I understand device files are removed. Is it to
> clean an old installation, if exists?
yes
> then
> mknod complains about missing operands; what does it mean?
the driver has not been loaded correctly and therefore
the nodes are not there.
> mknod -m 0664 /dev/pt_drv c 40 0
the would help if the driver has been loaded correctly.
> and then load module manually it is getting strange:
>
> debian:/home/jastra insmod pt_drv
> insmod: can't read 'pt_drv' no such file or directory
either do a modprobe or tell insmod the complete path
to pt_drv.ko module
> debian:/home/jastra
> debian:/home/jastra modprobe pt_drv
> debian:/home/jastra
Yeap, and what is then the output of dmesg???
> Device files are kept until next reboot, then they are removed
>
> Is it possible there is conflict between device files? It seems tty40 uses
> major number 40 too..
maybe. But i could only see that after you've build the module
correctly with DEBUG=y AND send me then the output of dmesg!!!!
Gerhard
