plustek: Thread: Plustek OpticPro 12000T

Good Afternoon,

I am fighting for some days with installation of kernel module pt_drv on 
Debian with kernel 2.6.18-5.686.
I have unpacked sources first 43.10, then overwritten with v. 43.12 as was 
advised in mailing list ####@####.#### compilation of module was 
without errors, problems started with attempt to load module and in 
general, with creation of devices:

----
Should I try and load the module?
If this step fails, check the kernel-log.
Press <ENTER> to continue or <CTRL><C> to cancel.

make: Entering directory `/usr/src/plustek/doc/plustek/build'
/sbin/modprobe pt_drv || exit 1
rm -f /dev/pt_drv*
mknod: missing operand after `0'
Try `mknod --help' for more information.
mknod: missing operand after `0'
Try `mknod --help' for more information.
mknod: missing operand after `1'
Try `mknod --help' for more information.
mknod: missing operand after `2'
Try `mknod --help' for more information.
mknod: missing operand after `3'
Try `mknod --help' for more information.
chgrp: cannot access `/dev/pt_drv*': No such file or directory
chmod: cannot access `/dev/pt_drv*': No such file or directory
make: *** [load] Error 1
make: Leaving directory `/usr/src/plustek/doc/plustek/build'
done.
Should I remove the build directory?
Press <ENTER> to continue or <CTRL><C> to cancel.
---

Manual creation of the /dev/pt_drv* has not succeded.
Attempt to work without driver, by setting options in /etc/sane/dll.conf 
and plustek_pp.conf has also not succeded. Scanimage -L sees no scanner.

I have seen in mailing list message from june 2007, that v.43.12 does not 
work with kernels over 2.6.15. In my case it is true.
Regret, internet information about current drivers is outdated and full of 
contradictions.

Do You have any idea, what to do? Buy a new scanner?

Thanks in advance
Best Regards
Basia

               Have a Happy and Prosperous New Year
      __ /\ __       __ /\ __       __ /\ __       __ /\ __
      \_`\/`_/ .\'/. \_`\/`_/ .\'/. \_`\/`_/ .\'/. \_`\/`_/
      <_>()<_>-=>*<=-<_>()<_>-=>*<=-<_>()<_>-=>*<=-<_>()<_>
      /_,/\,_\ '/.\' /_,/\,_\ '/.\' /_,/\,_\ '/.\' /_,/\,_\
         \/             \/             \/             \/

Hi,

On Thursday 17 January 2008 19:29:15 Jastra wrote:
[SNIPSNAP]
> I have seen in mailing list message from june 2007, that v.43.12 does not
> work with kernels over 2.6.15. In my case it is true.
> Regret, internet information about current drivers is outdated and full of
> contradictions.
>
> Do You have any idea, what to do? Buy a new scanner?

Buying a new scanner might be a good idea, but before doing
that go and download the latest SANE-snapshot from www.sane-project.org

Unpack and dive into the sane-backends/doc/plustek directory.
When the call ./MakeModule.sh (as root user), then the module
should be built...

- Gerhard

>> Do You have any idea, what to do? Buy a new scanner?
>
> Buying a new scanner might be a good idea, but before doing
> that go and download the latest SANE-snapshot from www.sane-project.org
>
> Unpack and dive into the sane-backends/doc/plustek directory.
> When the call ./MakeModule.sh (as root user), then the module
> should be built...

Thanks for fast reply

Stable Debian package is listed as from Sarge (there is Etch now) and 
leads to 404 error not found.

stable sane-backend source first have error in file

   CC [M]  /usr/src/plustek/doc/plustek/build/plustek-pp_ptdrv.o
/usr/src/plustek/doc/plustek/build/plustek-pp_ptdrv.c:178: error: expected 
) before string constant
/usr/src/plustek/doc/plustek/build/plustek-pp_ptdrv.c:181: error: expected 
) before string constant
/usr/src/plustek/doc/plustek/build/plustek-pp_ptdrv.c:184: error: expected 
) before string constant
/usr/src/plustek/doc/plustek/build/plustek-pp_ptdrv.c:187: error: expected 
) before string constant
/usr/src/plustek/doc/plustek/build/plustek-pp_ptdrv.c:190: error: expected 
) before string constant
/usr/src/plustek/doc/plustek/build/plustek-pp_ptdrv.c:193: error: expected 
) before string constant
/usr/src/plustek/doc/plustek/build/plustek-pp_ptdrv.c:196: error: expected 
) before string constant

  I have found solution to this by Google, it means replace all 
MODULE_PARM( with MODULE_PARM_DESC( in all lines 
listed with error in /backend/plustek-pp_ptdrv.c

However, after compilation, device /dev/pt_drv* could not be created as 
before.

The same error started in 18.01.2008 snapshoot, after editing the lines 
with errors, it has compiled with some warnings as

/usr/src/plustek/doc/plustek/build/plustek-pp_ptdrv.c:1138: warning: 
ignoring return value of copy_from_user, declared with attribute 
warn_unused_result


and at the end

make: Entering directory `/usr/src/plustek/doc/plustek/build'
/sbin/modprobe pt_drv || exit 1
rm -f /dev/pt_drv*
mknod: missing operand after `0'
Try `mknod --help' for more information.
mknod: missing operand after `0'
Try `mknod --help' for more information.
mknod: missing operand after `1'
Try `mknod --help' for more information.
mknod: missing operand after `2'
Try `mknod --help' for more information.
mknod: missing operand after `3'
Try `mknod --help' for more information.
chgrp: cannot access `/dev/pt_drv*': No such file or directory
chmod: cannot access `/dev/pt_drv*': No such file or directory
make: *** [load] Error 1
make: Leaving directory `/usr/src/plustek/doc/plustek/build'
done.

In general - no better result

Do You have any idea, what to do?
Thanks in advance
Best Regards
Basia

               Have a Happy and Prosperous New Year
      __ /\ __       __ /\ __       __ /\ __       __ /\ __
      \_`\/`_/ .\'/. \_`\/`_/ .\'/. \_`\/`_/ .\'/. \_`\/`_/
      <_>()<_>-=>*<=-<_>()<_>-=>*<=-<_>()<_>-=>*<=-<_>()<_>
      /_,/\,_\ '/.\' /_,/\,_\ '/.\' /_,/\,_\ '/.\' /_,/\,_\
         \/             \/             \/             \/

On Friday 18 January 2008 10:54:49 Jastra wrote:
[SNIPSNAP]
> chgrp: cannot access `/dev/pt_drv*': No such file or directory
> chmod: cannot access `/dev/pt_drv*': No such file or directory
> make: *** [load] Error 1
> make: Leaving directory `/usr/src/plustek/doc/plustek/build'
> done.
>
> In general - no better result
>
> Do You have any idea, what to do?

Make sure parport drivers are correctly loaded 
(parport_pc, parport and ppdev)
Make sure parport is set to either SPP, or EPP 
No ECP mode!!! (check in BIOS)

Make and load modules via ./MakeModule.sh DEBUG=y
and after loading check (and show us) the output of
dmesg, probably we'll find the problem

- Gerhard

> Make sure parport drivers are correctly loaded
> (parport_pc, parport and ppdev)

yes, it seems OK - see lsmod.txt

> Make sure parport is set to either SPP, or EPP
> No ECP mode!!! (check in BIOS)

checked, it is correct

> Make and load modules via ./MakeModule.sh DEBUG=y
> and after loading check (and show us) the output of
> dmesg, probably we'll find the problem

I see no trace of the operation in dmesg - see dmesg.txt
(copy of /var/log/dmesg)

Or, should it be in any other place?

Greetings :-)
Basia

> - Gerhard
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
>

Module                  Size  Used by
nfs                   202828  0 
nfsd                  197936  17 
exportfs                5600  1 nfsd
lockd                  54344  3 nfs,nfsd
nfs_acl                 3584  2 nfs,nfsd
sunrpc                138812  13 nfs,nfsd,lockd,nfs_acl
lp                     11012  0 
button                  6672  0 
ac                      5188  0 
battery                 9636  0 
ipv6                  226272  8 
dm_snapshot            15552  0 
dm_mirror              19152  0 
dm_mod                 50232  2 dm_snapshot,dm_mirror
ide_pnp                 2560  0 
ide_generic             1408  0 [permanent]
ide_floppy             16256  0 
sermouse                5440  0 
isofs                  32540  0 
ppdev                   8676  0 
ioatdma                 9088  0 [unsafe]
raw                     8608  0 
drm                    61332  0 
paride                  8224  0 
nbd                    20800  0 
smbfs                  57400  0 
vfat                   11872  0 
msdos                   8736  0 
fat                    46684  2 vfat,msdos
loop                   15048  0 
parport_pc             32132  1 
parport                33256  4 lp,ppdev,paride,parport_pc
psmouse                35016  0 
serio_raw               6660  0 
i2c_piix4               8268  0 
pcspkr                  3072  0 
i2c_core               19680  1 i2c_piix4
intel_agp              22204  1 
agpgart                29896  2 drm,intel_agp
shpchp                 33024  0 
pci_hotplug            28704  1 shpchp
evdev                   9088  1 
ext3                  119240  2 
jbd                    52456  1 ext3
mbcache                 8356  1 ext3
ide_cd                 36064  0 
cdrom                  32544  1 ide_cd
ide_disk               14848  4 
generic                 4868  0 [permanent]
8139too                25120  0 
8139cp                 21920  0 
mii                     5344  2 8139too,8139cp
piix                    9444  0 [permanent]
uhci_hcd               21164  0 
usbcore               112644  2 uhci_hcd
ide_core              110504  7 ide_pnp,ide_generic,ide_floppy,ide_cd,ide_disk,generic,piix
thermal                13608  0 
processor              28840  1 thermal
fan                     4804  0 

Linux version 2.6.18-5-686 (Debian 2.6.18.dfsg.1-17) ####@####.#### (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Mon Dec 24 16:41:07 UTC 2007
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 0000000009ff0000 (usable)
 BIOS-e820: 0000000009ff0000 - 0000000009ff3000 (ACPI NVS)
 BIOS-e820: 0000000009ff3000 - 000000000a000000 (ACPI data)
 BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
0MB HIGHMEM available.
159MB LOWMEM available.
On node 0 totalpages: 40944
  DMA zone: 4096 pages, LIFO batch:0
  Normal zone: 36848 pages, LIFO batch:7
DMI not present or invalid.
ACPI: RSDP (v000 PCPART                                ) @ 0x000f6370
ACPI: RSDT (v001 AWARD  AWRDACPI 0x30302e31 AWRD 0x00000000) @ 0x09ff3000
ACPI: FADT (v001 AWARD  AWRDACPI 0x30302e31 AWRD 0x00000000) @ 0x09ff3040
ACPI: DSDT (v001 PCPART AWRDACPI 0x00001000 MSFT 0x0100000a) @ 0x00000000
ACPI: PM-Timer IO Port: 0x4008
Allocating PCI resources starting at 10000000 (gap: 0a000000:f5ff0000)
Detected 273.648 MHz processor.
Built 1 zonelists.  Total pages: 40944
Kernel command line: root=/dev/hda1 ro 
Local APIC disabled by BIOS -- you can enable it with "lapic"
mapped APIC to ffffd000 (01149000)
Initializing CPU#0
PID hash table entries: 1024 (order: 10, 4096 bytes)
Console: colour VGA+ 80x25
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 154688k/163776k available (1541k kernel code, 8552k reserved, 576k data, 196k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 548.05 BogoMIPS (lpj=1096115)
Security Framework v1.0.0 initialized
SELinux:  Disabled at boot.
Capability LSM initialized
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 0080f9ff 00000000 00000000 00000000 00000000 00000000 00000000
CPU: After vendor identify, caps: 0080f9ff 00000000 00000000 00000000 00000000 00000000 00000000
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 512K
CPU: After all inits, caps: 0080f9ff 00000000 00000000 00000040 00000000 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Compat vDSO mapped to ffffe000.
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 12k freed
ACPI: Core revision 20060707
ACPI: setting ELCR to 0200 (from 1c00)
CPU0: Intel Pentium II (Klamath) stepping 04
SMP motherboard not detected.
Local APIC not detected. Using dummy APIC emulation.
Brought up 1 CPUs
migration_cost=0
checking if image is initramfs... it is
Freeing initrd memory: 4397k freed
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xfb3d0, last bus=1
PCI: Using configuration type 1
Setting up standard PCI resources
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
ACPI: Assume root bridge [\_SB_.PCI0] bus is 0
* Found PM-Timer Bug on the chipset. Due to workarounds for a bug,
* this clock source is slow. Consider trying other clock sources
PCI quirk: region 4000-403f claimed by PIIX4 ACPI
PCI quirk: region 5000-500f claimed by PIIX4 SMB
Boot video device is 0000:00:0f.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 11 *12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: Power Resource [PFAN] (on)
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
pnp: PnP ACPI: found 11 devices
PnPBIOS: Disabled by ACPI PNP
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
PCI: Bridge: 0000:00:01.0
  IO window: d000-dfff
  MEM window: disabled.
  PREFETCH window: disabled.
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 4096)
TCP reno registered
audit: initializing netlink socket (disabled)
audit(1200914465.700:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Limiting direct PCI/PCI transfers.
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
serial8250: ttyS3 at I/O 0x2e8 (irq = 3) is a 16550A
00:08: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:09: ttyS3 at I/O 0x2e8 (irq = 3) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
PNP: No PS/2 controller found. Probing ports directly.
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
mice: PS/2 mouse device common for all mice
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 8
NET: Registered protocol family 20
Using IPI No-Shortcut mode
ACPI: (supports S0 S1<6>Time: tsc clocksource has been installed.
 S5)
Freeing unused kernel memory: 196k freed
input: AT Translated Set 2 keyboard as /class/input/input0
ACPI: Fan [FAN] (on)
ACPI: CPU0 (power states: C1[C1] C2[C2])
ACPI: Processor [CPU0] (supports 8 throttling states)
ACPI: Thermal Zone [THRM] (22 C)
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
usbcore: registered new driver usbfs
usbcore: registered new driver hub
USB Universal Host Controller Interface driver v3.0
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
ACPI: PCI Interrupt 0000:00:07.2[D] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
uhci_hcd 0000:00:07.2: UHCI Host Controller
uhci_hcd 0000:00:07.2: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:07.2: irq 11, io base 0x0000e000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
8139cp: 10/100 PCI Ethernet driver v1.2 (Mar 22, 2004)
8139cp 0000:00:10.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible chip
8139cp 0000:00:10.0: Try the "8139too" driver instead.
PIIX4: IDE controller at PCI slot 0000:00:07.1
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:pio, hdb:pio
    ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:pio, hdd:pio
Probing IDE interface ide0...
8139too Fast Ethernet driver 0.9.27
hda: Nikimi NIK-XR205A, ATA DISK drive
Time: acpi_pm clocksource has been installed.
hdb: CRD-8160B, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hda: max request size: 128KiB
hda: 40132503 sectors (20547 MB) w/1900KiB Cache, CHS=39813/16/63, UDMA(33)
hda: cache flushes not supported
 hda:ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 12
PCI: setting IRQ 12 as level-triggered
ACPI: PCI Interrupt 0000:00:10.0[A] -> Link [LNKB] -> GSI 12 (level, low) -> IRQ 12
eth0: RealTek RTL8139 at 0xe800, 00:00:00:00:00:00, IRQ 12
eth0:  Identified 8139 chip type 'RTL-8101'
 hda1 hda2 < hda5 hda6 >
hdb: ATAPI 16X CD-ROM drive, 128kB Cache, DMA
Uniform CD-ROM driver Revision: 3.20
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected an Intel 440LX Chipset.
agpgart: AGP aperture is 64M @ 0xe0000000
input: PC Speaker as /class/input/input1
piix4_smbus 0000:00:07.3: Found 0000:00:07.3 device
parport: PnPBIOS parport detected.
parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE,EPP]
Adding 248968k swap on /dev/hda5.  Priority:-1 extents:1 across:248968k
EXT3 FS on hda1, internal journal
loop: loaded (max 8 devices)
nbd: registered device at major 43
[drm] Initialized drm 1.0.1 20051102
Module ioatdma cannot be unloaded due to unsafe usage in drivers/dma/ioatdma.c:829
ppdev: user-space parallel port driver
ide-floppy driver 0.99.newide
Probing IDE interface ide1...
device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: ####@####.####
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
eth0: link up, 10Mbps, half-duplex, lpa 0x0000

On Monday 21 January 2008 10:00:27 Jastra wrote:
> > Make sure parport drivers are correctly loaded
> > (parport_pc, parport and ppdev)
> 
> yes, it seems OK - see lsmod.txt
> 
> > Make sure parport is set to either SPP, or EPP
> > No ECP mode!!! (check in BIOS)
> 
> checked, it is correct
> 
> > Make and load modules via ./MakeModule.sh DEBUG=y
> > and after loading check (and show us) the output of
> > dmesg, probably we'll find the problem

Have you done this step? /MakeModule.sh DEBUG=y ????

> I see no trace of the operation in dmesg - see dmesg.txt
> (copy of /var/log/dmesg)
> 
> Or, should it be in any other place?

/var/log/messages


As examples, the build step and dmesg looks here as follows:

sudo ./MakeModule.sh DEBUG=y
This script will try and build a suitable kernel-module for your system.
If you'd like to make the module WITH debug output, restart this script
with as follows:
./MakeModule.sh DEBUG=y
Press <ENTER> to continue or <CTRL><C> to cancel.

Check for root - done.

Check for kernelversion:
Using makefile for kernel 2.6.x
Build-directory:
/home/gja/Privat/scanner/devel/usb/sane-backends/doc/plustek/build
Removing build-directory - done.
Creating build-directory - done.

Linking source files - done.
Copying Makefile to build-directory - done.
Making the module...
make: Entering directory `/usr/src/linux-2.6.22.13-0.3-obj/i386/default'
make -C ../../../linux-2.6.22.13-0.3 O=../linux-2.6.22.13-0.3-obj/i386/default modules
  CC [M]  /home/gja/Privat/scanner/devel/usb/sane-backends/doc/plustek/build/plustek-pp_dac.o
  CC [M]  /home/gja/Privat/scanner/devel/usb/sane-backends/doc/plustek/build/plustek-pp_detect.o
  CC [M]  /home/gja/Privat/scanner/devel/usb/sane-backends/doc/plustek/build/plustek-pp_genericio.o
  CC [M]  /home/gja/Privat/scanner/devel/usb/sane-backends/doc/plustek/build/plustek-pp_image.o
  CC [M]  /home/gja/Privat/scanner/devel/usb/sane-backends/doc/plustek/build/plustek-pp_map.o
  CC [M]  /home/gja/Privat/scanner/devel/usb/sane-backends/doc/plustek/build/plustek-pp_misc.o
  CC [M]  /home/gja/Privat/scanner/devel/usb/sane-backends/doc/plustek/build/plustek-pp_models.o
  CC [M]  /home/gja/Privat/scanner/devel/usb/sane-backends/doc/plustek/build/plustek-pp_io.o
  CC [M]  /home/gja/Privat/scanner/devel/usb/sane-backends/doc/plustek/build/plustek-pp_procfs.o
  CC [M]  /home/gja/Privat/scanner/devel/usb/sane-backends/doc/plustek/build/plustek-pp_motor.o
  CC [M]  /home/gja/Privat/scanner/devel/usb/sane-backends/doc/plustek/build/plustek-pp_p9636.o
  CC [M]  /home/gja/Privat/scanner/devel/usb/sane-backends/doc/plustek/build/plustek-pp_ptdrv.o
  CC [M]  /home/gja/Privat/scanner/devel/usb/sane-backends/doc/plustek/build/plustek-pp_scale.o
  CC [M]  /home/gja/Privat/scanner/devel/usb/sane-backends/doc/plustek/build/plustek-pp_tpa.o
  CC [M]  /home/gja/Privat/scanner/devel/usb/sane-backends/doc/plustek/build/plustek-pp_p48xx.o
  CC [M]  /home/gja/Privat/scanner/devel/usb/sane-backends/doc/plustek/build/plustek-pp_p12.o
  CC [M]  /home/gja/Privat/scanner/devel/usb/sane-backends/doc/plustek/build/plustek-pp_p12ccd.o
  LD [M]  /home/gja/Privat/scanner/devel/usb/sane-backends/doc/plustek/build/pt_drv.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /home/gja/Privat/scanner/devel/usb/sane-backends/doc/plustek/build/pt_drv.mod.o
  LD [M]  /home/gja/Privat/scanner/devel/usb/sane-backends/doc/plustek/build/pt_drv.ko
make: Leaving directory `/usr/src/linux-2.6.22.13-0.3-obj/i386/default'
done.
Should I install the module?
Press <ENTER> to continue or <CTRL><C> to cancel.

make: Entering directory `/home/gja/Privat/scanner/devel/usb/sane-backends/doc/plustek/build'
mkdir -p /lib/modules/2.6.22.13-0.3-default/kernel/drivers/parport
install -c -m "644" pt_drv.ko /lib/modules/2.6.22.13-0.3-default/kernel/drivers/parport
/sbin/depmod -a

make: Leaving directory `/home/gja/Privat/scanner/devel/usb/sane-backends/doc/plustek/build'
Should I try and load the module?
If this step fails, check the kernel-log.
Press <ENTER> to continue or <CTRL><C> to cancel.
make: Entering directory `/home/gja/Privat/scanner/devel/usb/sane-backends/doc/plustek/build'
/sbin/modprobe pt_drv || exit 1
FATAL: Error inserting pt_drv (/lib/modules/2.6.22.13-0.3-default/kernel/drivers/parport/pt_drv.ko): Success
make: *** [load] Fehler 1
make: Leaving directory `/home/gja/Privat/scanner/devel/usb/sane-backends/doc/plustek/build'
done.
Should I remove the build directory?
Press <ENTER> to continue or <CTRL><C> to cancel.

done.

# dmesg
.
.
.
*********************************************
pt_drv: init_module()
pt_drv : driver version 0.43-13
ProcFsInitialize()
ptdrvInit(0)
Init settings done
ScanData = 0xcd0d0000
Using fast I/O
Requested port at 0x378
misc_attach
Requested port (0x378) found
Port mode reported: (0x0047)
Port for device 0 registered
ptdrvOpen(port=0x378)
Try to claim the parport
parport-modi: SPP PS/2 EPP EPP(ECP) PS/2(ECP)
Using EPP-mode
Starting Scanner-Autodetection
************ DETECTP48xx ************
ModelSet4800()
modelInitPageSettings()
A4 set
ModelSet4800() done.
P48xxInitAsic()
DacInitialize()
ImageInitialize()
IOFuncInitialize()
IOInitialize()
* using readfunction >fnEPPRead<
MotorInitialize()
Dataport = 0x0378
Ctrlport = 0x037a
ResetPort()
Test 0x55
Test 0xAA
Compare data=0x7e and status=0x7e, port=0x378
detectScannerConnection() returns -9021.
************* ASIC9800x *************
ResetPort()
IOInitialize()
* using readfunction >fnEPPRead<
ASIC = 0x77
Unknown ASIC-ID
*** DETECTION DONE, result: -9020 ***
ptdrvClose()
MiscRestorePort()
- no need to restore portmode !
Releasing parport
ptdrvShutdown()
cleanup device 0
Port unregistered
misc_detach
ProcFsShutdown()
pt_drv: proc del 'info' root='pt_drv'
pt_drv: proc del 'pt_drv' root='/proc'
pt_drv : no device(s) detected, (-9020)
---------------------------------------------

>>> Make and load modules via ./MakeModule.sh DEBUG=y
>>> and after loading check (and show us) the output of
>>> dmesg, probably we'll find the problem
>
> Have you done this step? /MakeModule.sh DEBUG=y ????

yes, with debug

>> I see no trace of the operation in dmesg - see dmesg.txt
>> (copy of /var/log/dmesg)
>>
>> Or, should it be in any other place?
>
> /var/log/messages

I have checked it too - there is nothing

> As examples, the build step and dmesg looks here as follows:
>
> sudo ./MakeModule.sh DEBUG=y

I made it in root console, shouldn't it be the same?

> make: Entering directory `/home/gja/Privat/scanner/devel/usb/sane-backends/doc/plustek/build'
> /sbin/modprobe pt_drv || exit 1
> FATAL: Error inserting pt_drv (/lib/modules/2.6.22.13-0.3-default/kernel/drivers/parport/pt_drv.ko): Success
> make: *** [load] Fehler 1
> make: Leaving directory `/home/gja/Privat/scanner/devel/usb/sane-backends/doc/plustek/build'
> done.

> *********************************************
> pt_drv: init_module()
> pt_drv : driver version 0.43-13

No message similar to this in any kernel.log, system log messages or dmesg
Could it be blocked anywhere? It is very fresh Debian stable installation 
of January 2008

Any idea?

Many thanks for your time to help

Best Regards
Barbara Glowacka

On Monday 21 January 2008 14:48:35 Jastra wrote:
> >>> Make and load modules via ./MakeModule.sh DEBUG=y
> >>> and after loading check (and show us) the output of
> >>> dmesg, probably we'll find the problem
> >
> > Have you done this step? /MakeModule.sh DEBUG=y ????
> 
> yes, with debug
> 
> >> I see no trace of the operation in dmesg - see dmesg.txt
> >> (copy of /var/log/dmesg)
> >>
> >> Or, should it be in any other place?
> >
> > /var/log/messages
> 
> I have checked it too - there is nothing
> 
> > As examples, the build step and dmesg looks here as follows:
> >
> > sudo ./MakeModule.sh DEBUG=y
> 
> I made it in root console, shouldn't it be the same?

that's fine, no problem.

> > make: Entering directory `/home/gja/Privat/scanner/devel/usb/sane-backends/doc/plustek/build'
> > /sbin/modprobe pt_drv || exit 1
> > FATAL: Error inserting pt_drv (/lib/modules/2.6.22.13-0.3-default/kernel/drivers/parport/pt_drv.ko): Success
> > make: *** [load] Fehler 1
> > make: Leaving directory `/home/gja/Privat/scanner/devel/usb/sane-backends/doc/plustek/build'
> > done.
> 
> > *********************************************
> > pt_drv: init_module()
> > pt_drv : driver version 0.43-13
> 
> No message similar to this in any kernel.log, system log messages or dmesg
> Could it be blocked anywhere? It is very fresh Debian stable installation 
> of January 2008
> 
> Any idea?

Nope, clueless. It makes me wonder, why the module won't get loaded...

You might send a log of all steps including the screenoutput of what
you've done so far...

- Gerhard

>>> 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"?

Then, the last step, the loading step:
first I see
/sbin/modprobe pt_drv || exit 1   ## I understand, attempt to load module

then
rm -f /dev/pt_drv* ## I understand device files are removed. Is it to 
clean an old installation, if exists?

then
mknod complains about missing operands; what does it mean?

then
chgrp: cannot access `/dev/pt_drv*': No such file or directory
chmod: cannot access `/dev/pt_drv*': No such file or directory

device files do not exist.


If I try to make the device files manually:

mknod -m 0664 /dev/pt_drv c 40 0
mknod -m 0664 /dev/pt_drv0 c 40 0
mknod -m 0664 /dev/pt_drv1 c 40 1
mknod -m 0664 /dev/pt_drv2 c 40 2
mknod -m 0664 /dev/pt_drv3 c 40 3

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
debian:/home/jastra
debian:/home/jastra modprobe pt_drv
debian:/home/jastra

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..

Do you understand, what is going on?
Disk is not overfilled...

Best greetings
Basia

debian:/usr/src/plustek/doc/plustek# ./MakeModule.sh DEBUG=y
This script will try and build a suitable kernel-module for your system.
If you'd like to make the module WITH debug output, restart this script
with as follows:
./MakeModule.sh DEBUG=y
Press <ENTER> to continue or <CTRL><C> to cancel.

Check for root - done.

Check for kernelversion:
Using makefile for kernel 2.6.x
Build-directory:
/usr/src/plustek/doc/plustek/build
Removing build-directory - done.
Creating build-directory - done.

Linking source files - done.
Copying Makefile to build-directory - done.
Making the module...
make: Entering directory `/usr/src/linux-headers-2.6.18-5-686'
  CC [M]  /usr/src/plustek/doc/plustek/build/plustek-pp_dac.o
  CC [M]  /usr/src/plustek/doc/plustek/build/plustek-pp_detect.o
  CC [M]  /usr/src/plustek/doc/plustek/build/plustek-pp_genericio.o
  CC [M]  /usr/src/plustek/doc/plustek/build/plustek-pp_image.o
  CC [M]  /usr/src/plustek/doc/plustek/build/plustek-pp_map.o
  CC [M]  /usr/src/plustek/doc/plustek/build/plustek-pp_misc.o
  CC [M]  /usr/src/plustek/doc/plustek/build/plustek-pp_models.o
  CC [M]  /usr/src/plustek/doc/plustek/build/plustek-pp_io.o
  CC [M]  /usr/src/plustek/doc/plustek/build/plustek-pp_procfs.o
  CC [M]  /usr/src/plustek/doc/plustek/build/plustek-pp_motor.o
  CC [M]  /usr/src/plustek/doc/plustek/build/plustek-pp_p9636.o
  CC [M]  /usr/src/plustek/doc/plustek/build/plustek-pp_ptdrv.o
/usr/src/plustek/doc/plustek/build/plustek-pp_ptdrv.c: In function ‘getUserPtr’:/usr/src/plustek/doc/plustek/build/plustek-pp_ptdrv.c:317: warning: ignoring return value of ‘copy_from_user’, declared with attribute warn_unused_result
/usr/src/plustek/doc/plustek/build/plustek-pp_ptdrv.c: In function ‘putUserPtr’:/usr/src/plustek/doc/plustek/build/plustek-pp_ptdrv.c:352: warning: ignoring return value of ‘copy_to_user’, declared with attribute warn_unused_result
/usr/src/plustek/doc/plustek/build/plustek-pp_ptdrv.c: In function ‘ptdrvIoctl’:/usr/src/plustek/doc/plustek/build/plustek-pp_ptdrv.c:984: warning: ignoring return value of ‘copy_from_user’, declared with attribute warn_unused_result
/usr/src/plustek/doc/plustek/build/plustek-pp_ptdrv.c:1035: warning: ignoring return value of ‘copy_from_user’, declared with attribute warn_unused_result
/usr/src/plustek/doc/plustek/build/plustek-pp_ptdrv.c:1074: warning: ignoring return value of ‘copy_from_user’, declared with attribute warn_unused_result
/usr/src/plustek/doc/plustek/build/plustek-pp_ptdrv.c:1109: warning: ignoring return value of ‘copy_from_user’, declared with attribute warn_unused_result
/usr/src/plustek/doc/plustek/build/plustek-pp_ptdrv.c:1127: warning: ignoring return value of ‘copy_from_user’, declared with attribute warn_unused_result
/usr/src/plustek/doc/plustek/build/plustek-pp_ptdrv.c:1138: warning: ignoring return value of ‘copy_from_user’, declared with attribute warn_unused_result
/usr/src/plustek/doc/plustek/build/plustek-pp_ptdrv.c:1156: warning: ignoring return value of ‘copy_from_user’, declared with attribute warn_unused_result
/usr/src/plustek/doc/plustek/build/plustek-pp_ptdrv.c:1179: warning: ignoring return value of ‘copy_to_user’, declared with attribute warn_unused_result
/usr/src/plustek/doc/plustek/build/plustek-pp_ptdrv.c:1204: warning: ignoring return value of ‘copy_to_user’, declared with attribute warn_unused_result
/usr/src/plustek/doc/plustek/build/plustek-pp_ptdrv.c:1214: warning: ignoring return value of ‘copy_from_user’, declared with attribute warn_unused_result
/usr/src/plustek/doc/plustek/build/plustek-pp_ptdrv.c: In function ‘ptdrvRead’:
/usr/src/plustek/doc/plustek/build/plustek-pp_ptdrv.c:1471: warning: ignoring return value of ‘copy_to_user’, declared with attribute warn_unused_result
/usr/src/plustek/doc/plustek/build/plustek-pp_ptdrv.c:1474: warning: ignoring return value of ‘copy_to_user’, declared with attribute warn_unused_result
  CC [M]  /usr/src/plustek/doc/plustek/build/plustek-pp_scale.o
  CC [M]  /usr/src/plustek/doc/plustek/build/plustek-pp_tpa.o
  CC [M]  /usr/src/plustek/doc/plustek/build/plustek-pp_p48xx.o
  CC [M]  /usr/src/plustek/doc/plustek/build/plustek-pp_p12.o
  CC [M]  /usr/src/plustek/doc/plustek/build/plustek-pp_p12ccd.o
  LD [M]  /usr/src/plustek/doc/plustek/build/pt_drv.o
  Building modules, stage 2.
  MODPOST
  CC      /usr/src/plustek/doc/plustek/build/pt_drv.mod.o
  LD [M]  /usr/src/plustek/doc/plustek/build/pt_drv.ko
make: Leaving directory `/usr/src/linux-headers-2.6.18-5-686'
done.
Should I install the module?
Press <ENTER> to continue or <CTRL><C> to cancel.

make: Entering directory `/usr/src/plustek/doc/plustek/build'
mkdir -p /lib/modules/2.6.18-5-686/kernel/drivers/parport
install -c -m "644" pt_drv.ko /lib/modules/2.6.18-5-686/kernel/drivers/parport
/sbin/depmod -a
make: Leaving directory `/usr/src/plustek/doc/plustek/build'
Should I try and load the module?
If this step fails, check the kernel-log.
Press <ENTER> to continue or <CTRL><C> to cancel.
make: Entering directory `/usr/src/plustek/doc/plustek/build'
/sbin/modprobe pt_drv || exit 1
rm -f /dev/pt_drv*
mknod: missing operand after `0'
Try `mknod --help' for more information.
mknod: missing operand after `0'
Try `mknod --help' for more information.
mknod: missing operand after `1'
Try `mknod --help' for more information.
mknod: missing operand after `2'
Try `mknod --help' for more information.
mknod: missing operand after `3'
Try `mknod --help' for more information.
chgrp: cannot access `/dev/pt_drv*': No such file or directory
chmod: cannot access `/dev/pt_drv*': No such file or directory
make: *** [load] Error 1
make: Leaving directory `/usr/src/plustek/doc/plustek/build'
done.
Should I remove the build directory?
done.
debian:/usr/src/plustek/doc/plustek#

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