plustek: Thread: Device or resource busy

Hi,
I have tried to set up the driver for my 9636P with sane-1.0.1, however
I always get this error message:

[root@Alfred plustek_driver]# make load
/sbin/modprobe pt_drv || exit 1
/lib/modules/2.2.14/misc/pt_drv.o: init_module: Device or resource busy
parport: Device or resource busy
make: *** [load] Error 1

As suggested in a previous post I have enbled the debug switch in the
makefile. Attached see the relevant output part of dmesg. The
distribution is RedHat6.1.
What am I doing wrong?
Suggestions anyone? 

TIA,
Michael


*********************************************
pt_drv: init_module()
ptdrvInit(0)
Init settings done
ScanData = 0xc3bb8000
Requested port at 0x378
Requested port (0x378) found
Port mode reported: (0x0079)
Port registered
ptdrvOpen(port=0x378)
Try to claim the parport
Using SPP-mode
Attempting to set EPP from ECP mode.
Port is set to (ECP) EPP mode.
Starting Scanner-Autodetection
************ DETECTP48xx ************
ModelSet4800()
modelInitPageSettings()
A4 set
ModelSet4800() done.
P48xxInitAsic()
DacInitialize()
ImageInitialize()
IOInitialize()
MotorInitialize()
Test 0x55
Test 0xAA
Compare data=0xde and status=0x5e, port=0x378
p48xxReadWriteTest()
Can't find your model, asic = 0x5a
detectScannerConnection() returns -9020.
************ DETECTP9636 ************
ModelSet9636()
ModelSet9360()
modelInitPageSettings()
A4 set
ModelSet9630() done.
modelInitPageSettings()
A4 set
ModelSet9636() done.
P9636InitAsic()
DacInitialize()
ImageInitialize()
IOInitialize()
MotorInitialize()
AsicID = 0x81
Test 0x55
Test 0xAA
Compare data=0xde and status=0x1e, port=0x378
p9636ReadWriteTest()
Error in memory test at pos 72 (72 != 76)
detectScannerConnection() returns -9020.
ptdrvClose()
MiscRestorePort()
Releasing parport
ptdrvShutdown()
pt_drv: init failed - ret = -9020
---------------------------------------------

Hi Michael,

it seems there's a problem with the parallel port.
Try to set this port (in the BIOS) to EPP or SPP
and test again.

When looking at the debug-messages, your
scanner has been found, but the memory
test fails. So there are two possibilities:

- The parallelport settings are not ok.
- The scanner is out of order

One question: Is the scanner an OP9636P Turbo?

Gerhard

----------------------------------------
####@####.####
----------------------------------------

Hi Gerhard,

"G. Jaeger" wrote:
> 
> Hi Michael,
> 
> it seems there's a problem with the parallel port.
> Try to set this port (in the BIOS) to EPP or SPP
> and test again.

I set it to EPP/SPP and thereafter to SPP only, no go. Same error occurs
both ways.

> When looking at the debug-messages, your
> scanner has been found, but the memory
> test fails. So there are two possibilities:
> 
> - The parallelport settings are not ok.
> - The scanner is out of order

I just crosschecked with Windows, the scanner works fine.
 
> One question: Is the scanner an OP9636P Turbo?

Not that I know of. It's a used one, so I'm not perfectly sure, but it
doesn't say Turbo anywhere on it. The scan speed (in Windows) doesn't
imply it's a Turbo either... :-)

Is there anything else I can do?

Regards,
Michael

On Fre, 11 Aug 2000, you wrote:
[snip]
> 
> > One question: Is the scanner an OP9636P Turbo?
> 
> Not that I know of. It's a used one, so I'm not perfectly sure, but it
> doesn't say Turbo anywhere on it. The scan speed (in Windows) doesn't
> imply it's a Turbo either... :-)
> 
Hi Michael,

Turbo does not mean, that the scanner is faster ;-)
There are currently three OpticPro9636P Scanners.
OP9636P
OP9636P+
OP9636PTurbo
The + and the Turbo models are quite the same and
the difference between the Turbo and the non-Turbo
is the scan-sensor. The Turbo uses the same like
the newer OP9636T/12000T while the non-Turbo
uses the older ones from the OP9630....

But this should have no effect on the other stuff. There's
one thing you can do. Comment out two lines in the
memory test in file src/p9636.c in function p9636ReadWriteTest
a line 407/408 or so:
retval = _E_NO_DEV;
break.
Simply put // before these lines and recompile and reinstall
the driver.
After loading, please check the debug output for other
"Error in memory test..." messages.
After this patch you're might able to scan, but it is not
guaranteed that this will work.
I think this error is a problem in communication with
the scanner...
Have you tested with Windows on the same machine?

Let me know what happend
Gerhard

"Jaeger, Gerhard" wrote:
> 
> There's one thing you can do. Comment out two lines in the
> memory test in file src/p9636.c in function p9636ReadWriteTest
> a line 407/408 or so:
> retval = _E_NO_DEV;
> break.
> Simply put // before these lines and recompile and reinstall
> the driver.
> After loading, please check the debug output for other
> "Error in memory test..." messages.

I tried this and got many more memory test errors, but the driver was
loaded anyway and the light turned on.

> After this patch you're might able to scan, but it is not
> guaranteed that this will work.
> I think this error is a problem in communication with
> the scanner...

Something with my sane installation was wrong too; scanimage exited
because it didn't find the libraries.

> Have you tested with Windows on the same machine?

Yes, works fine in Windows.
 
> Let me know what happend

Easy enough: I installed sane-1.0.3 and it worked right out of the box
:-), although I still get memory error messages when loading the module.
Thank you for your good work.
There is only one thing left to improve. The scans seem to have a bluish
tint, maybe there is a problem with the white balance? I tried changing
the warmup time, but that didn't help.
Is this a known problem?

Thank you,
Michael

On Son, 20 Aug 2000, you wrote:
> Thank you for your good work.
> There is only one thing left to improve. The scans seem to have a bluish
> tint, maybe there is a problem with the white balance? I tried changing
> the warmup time, but that didn't help.
> Is this a known problem?
> 
Hi Michael,

I recognized this on my OP9636P Turbo last week when I
only scanned the cover (which should be white!).
But white parts in scanned pictures were not affected?!!
If I have some spare time left, I'll try to find the problem.

If you didn't like the error messages, simply uncomment
the printk statement. I still can't explain why there are such
memory problems. Maybe there are some other OP9636 users
out there with similar problems, You are the first user who
gave me a feedback on the OP9636.

Thanks for that...
Gerhard

I've just compiled sane 1.0.4 and pt_drv 0.37-24
bur the driver don't seem to load whith  modprobe.
I have these error messages :


Jan 24 02:13:19 CHOUPI kernel: parport0: PC-style at 0x278 [SPP]
Jan 24 02:13:20 CHOUPI kernel: parport_probe: failed
Jan 24 02:13:20 CHOUPI kernel: parport0: no IEEE-1284 device present.
Jan 24 02:13:20 CHOUPI kernel: lp0: using parport0 (polling).
Jan 24 02:15:27 CHOUPI kernel:
*********************************************
Jan 24 02:15:27 CHOUPI kernel: pt_drv: init_module()
Jan 24 02:15:27 CHOUPI kernel: pt_drv : driver version 0.37-24
Jan 24 02:15:27 CHOUPI kernel: ptdrvInit(0)
Jan 24 02:15:27 CHOUPI kernel: Init settings done
Jan 24 02:15:27 CHOUPI kernel: ScanData = 0xc05e4000
Jan 24 02:15:27 CHOUPI kernel: Requested port at 0x378
Jan 24 02:15:27 CHOUPI kernel: ptdrvShutdown()
Jan 24 02:15:27 CHOUPI kernel: cleanup device 0
Jan 24 02:15:27 CHOUPI kernel: Lamp-Timer stopped !
Jan 24 02:15:27 CHOUPI kernel: Try to claim the parport
Jan 24 02:15:27 CHOUPI kernel: Unable to handle kernel NULL pointer
dereference at virtual address 00000004
Jan 24 02:15:27 CHOUPI kernel: current->tss.cr3 = 02340000, %%cr3 =
02340000
Jan 24 02:15:27 CHOUPI kernel: *pde = 00000000
Jan 24 02:15:27 CHOUPI kernel: Oops: 0000
Jan 24 02:15:27 CHOUPI kernel: CPU:    0
Jan 24 02:15:27 CHOUPI kernel: EIP:   
0010:[3c59x:__insmod_3c59x_S.bss_L4+22342/3554974]
Jan 24 02:15:27 CHOUPI kernel: EFLAGS: 00010282
Jan 24 02:15:27 CHOUPI kernel: eax: 00000000   ebx: c05e4000   ecx:
00000006   edx: c3898000
Jan 24 02:15:27 CHOUPI kernel: esi: 00000000   edi: c4dd5c64   ebp:
00000000   esp: c23bfe7c
Jan 24 02:15:27 CHOUPI kernel: ds: 0018   es: 0018   ss: 0018
Jan 24 02:15:27 CHOUPI kernel: Process modprobe (pid: 963, process nr:
50, stackpage=c23bf000)
Jan 24 02:15:27 CHOUPI kernel: Stack: c4dd5c64 00000019 c05e4000
00000000 c4dd5c64 c4dc7c40 00000000 00000001
Jan 24 02:15:27 CHOUPI kernel:        c02710d8 00000015 c05e4000
c05e4000 00000000 c4dceb80 c4dd415f 00000001
Jan 24 02:15:27 CHOUPI kernel:        c02710d4 c4dcefc7 c05e4000
00000001 c4dc004f c4dcefbe c05e4000 00000000
Jan 24 02:15:27 CHOUPI kernel: Call Trace:
[3c59x:__insmod_3c59x_S.bss_L4+343496/3233820] [3c59x:__insmod_3c59x_S
.bss_L4+343496/3233820] [3c59x:__insmod_3c59x_S.bss_L4+286116/3291200]
[3c59x:__insmod_3c59x_S.bss_L4+314596/3262
720] [3c59x:__insmod_3c59x_S.bss_L4+336579/3240737]
[3c59x:__insmod_3c59x_S.bss_L4+315691/3261625] [3c59x:__insmo
d_3c59x_S.bss_L4+254387/3322929]
Jan 24 02:15:27 CHOUPI kernel:       
[3c59x:__insmod_3c59x_S.bss_L4+315682/3261634]
[3c59x:__insmod_3c59x_S.bss_
L4+254387/3322929] [3c59x:__insmod_3c59x_S.bss_L4+315209/3262107]
[3c59x:__insmod_3c59x_S.bss_L4+343496/3233820]
[3c59x:__insmod_3c59x_S.bss_L4+254308/3323008]
[3c59x:__insmod_3c59x_S.bss_L4+254387/3322929] [3c59x:__insmod_3c5
9x_S.bss_L4+319003/3258313]
[3c59x:__insmod_3c59x_S.bss_L4+254308/3323008]
Jan 24 02:15:27 CHOUPI kernel:       
[3c59x:__insmod_3c59x_S.bss_L4+254387/3322929]
[3c59x:__insmod_3c59x_S.bss_
L4+254380/3322936] [3c59x:__insmod_3c59x_S.bss_L4+254308/3323008]
[3c59x:__insmod_3c59x_S.bss_L4+254387/3322929]
[3c59x:__insmod_3c59x_S.bss_L4+254380/3322936]
[sys_init_module+1095/1208] [3c59x:__insmod_3c59x_S.bss_L4+57700/3
519616] [3c59x:__insmod_3c59x_S.bss_L4+254380/3322936]
Jan 24 02:15:27 CHOUPI kernel:        [error_code+45/64]
[system_call+52/64]
Jan 24 02:15:27 CHOUPI kernel: Code: 8b 5e 04 39 73 1c 75 1a 83 c4 fc 8b
06 50 8b 43 08 50 68 02

when i use depmod -e, i have this message :
depmod: *** Unresolved symbols in
/lib/modules/2.2.17-21mdk/misc/pt_drv.o
depmod:         proc_register
depmod:         __generic_copy_from_user
depmod:         parport_unregister_device
depmod:         get_fast_time
depmod:         schedule
depmod:         __udelay
depmod:         parport_enumerate
depmod:         kmalloc
depmod:         unregister_chrdev
depmod:         register_chrdev
depmod:         vfree
depmod:         parport_register_device
depmod:         proc_unregister
depmod:         del_timer
depmod:         kfree
depmod:         vmalloc
depmod:         parport_claim
depmod:         parport_release
depmod:         proc_root
depmod:         sprintf
depmod:         jiffies
depmod:         printk
depmod:         add_timer
depmod:         __const_udelay
depmod:         __generic_copy_to_user

So any idea about what's going wrong ?
Thanks
François

Hi,

indeed, you have found a bug, BUT please make sure, that you
tell the driver the correct port, where your scanner is attached!!!

Your parport is located at 0x278 but the driver has been told to look
at 0x378!!!!

Gerhard


On Wed, 24 Jan 2001 02:41:55 +0100, François Münch wrote:

>I've just compiled sane 1.0.4 and pt_drv 0.37-24
>bur the driver don't seem to load whith  modprobe.
>I have these error messages :
>
>
>Jan 24 02:13:19 CHOUPI kernel: parport0: PC-style at 0x278 [SPP]
>Jan 24 02:13:20 CHOUPI kernel: parport_probe: failed
>Jan 24 02:13:20 CHOUPI kernel: parport0: no IEEE-1284 device present.
>Jan 24 02:13:20 CHOUPI kernel: lp0: using parport0 (polling).
>Jan 24 02:15:27 CHOUPI kernel:
>*********************************************
>Jan 24 02:15:27 CHOUPI kernel: pt_drv: init_module()
>Jan 24 02:15:27 CHOUPI kernel: pt_drv : driver version 0.37-24
>Jan 24 02:15:27 CHOUPI kernel: ptdrvInit(0)
>Jan 24 02:15:27 CHOUPI kernel: Init settings done
>Jan 24 02:15:27 CHOUPI kernel: ScanData = 0xc05e4000
>Jan 24 02:15:27 CHOUPI kernel: Requested port at 0x378
>Jan 24 02:15:27 CHOUPI kernel: ptdrvShutdown()
>Jan 24 02:15:27 CHOUPI kernel: cleanup device 0
>Jan 24 02:15:27 CHOUPI kernel: Lamp-Timer stopped !
>Jan 24 02:15:27 CHOUPI kernel: Try to claim the parport
>Jan 24 02:15:27 CHOUPI kernel: Unable to handle kernel NULL pointer
>dereference at virtual address 00000004
>Jan 24 02:15:27 CHOUPI kernel: current->tss.cr3 = 02340000, %%cr3 =
>02340000
>Jan 24 02:15:27 CHOUPI kernel: *pde = 00000000
>Jan 24 02:15:27 CHOUPI kernel: Oops: 0000
>Jan 24 02:15:27 CHOUPI kernel: CPU:    0
>Jan 24 02:15:27 CHOUPI kernel: EIP:   
>0010:[3c59x:__insmod_3c59x_S.bss_L4+22342/3554974]
>Jan 24 02:15:27 CHOUPI kernel: EFLAGS: 00010282
>Jan 24 02:15:27 CHOUPI kernel: eax: 00000000   ebx: c05e4000   ecx:
>00000006   edx: c3898000
>Jan 24 02:15:27 CHOUPI kernel: esi: 00000000   edi: c4dd5c64   ebp:
>00000000   esp: c23bfe7c
>Jan 24 02:15:27 CHOUPI kernel: ds: 0018   es: 0018   ss: 0018
>Jan 24 02:15:27 CHOUPI kernel: Process modprobe (pid: 963, process nr:
>50, stackpage=c23bf000)
>Jan 24 02:15:27 CHOUPI kernel: Stack: c4dd5c64 00000019 c05e4000
>00000000 c4dd5c64 c4dc7c40 00000000 00000001
>Jan 24 02:15:27 CHOUPI kernel:        c02710d8 00000015 c05e4000
>c05e4000 00000000 c4dceb80 c4dd415f 00000001
>Jan 24 02:15:27 CHOUPI kernel:        c02710d4 c4dcefc7 c05e4000
>00000001 c4dc004f c4dcefbe c05e4000 00000000
>Jan 24 02:15:27 CHOUPI kernel: Call Trace:
>[3c59x:__insmod_3c59x_S.bss_L4+343496/3233820] [3c59x:__insmod_3c59x_S
>.bss_L4+343496/3233820] [3c59x:__insmod_3c59x_S.bss_L4+286116/3291200]
>[3c59x:__insmod_3c59x_S.bss_L4+314596/3262
>720] [3c59x:__insmod_3c59x_S.bss_L4+336579/3240737]
>[3c59x:__insmod_3c59x_S.bss_L4+315691/3261625] [3c59x:__insmo
>d_3c59x_S.bss_L4+254387/3322929]
>Jan 24 02:15:27 CHOUPI kernel:       
>[3c59x:__insmod_3c59x_S.bss_L4+315682/3261634]
>[3c59x:__insmod_3c59x_S.bss_
>L4+254387/3322929] [3c59x:__insmod_3c59x_S.bss_L4+315209/3262107]
>[3c59x:__insmod_3c59x_S.bss_L4+343496/3233820]
>[3c59x:__insmod_3c59x_S.bss_L4+254308/3323008]
>[3c59x:__insmod_3c59x_S.bss_L4+254387/3322929] [3c59x:__insmod_3c5
>9x_S.bss_L4+319003/3258313]
>[3c59x:__insmod_3c59x_S.bss_L4+254308/3323008]
>Jan 24 02:15:27 CHOUPI kernel:       
>[3c59x:__insmod_3c59x_S.bss_L4+254387/3322929]
>[3c59x:__insmod_3c59x_S.bss_
>L4+254380/3322936] [3c59x:__insmod_3c59x_S.bss_L4+254308/3323008]
>[3c59x:__insmod_3c59x_S.bss_L4+254387/3322929]
>[3c59x:__insmod_3c59x_S.bss_L4+254380/3322936]
>[sys_init_module+1095/1208] [3c59x:__insmod_3c59x_S.bss_L4+57700/3
>519616] [3c59x:__insmod_3c59x_S.bss_L4+254380/3322936]
>Jan 24 02:15:27 CHOUPI kernel:        [error_code+45/64]
>[system_call+52/64]
>Jan 24 02:15:27 CHOUPI kernel: Code: 8b 5e 04 39 73 1c 75 1a 83 c4 fc 8b
>06 50 8b 43 08 50 68 02
>
>when i use depmod -e, i have this message :
>depmod: *** Unresolved symbols in
>/lib/modules/2.2.17-21mdk/misc/pt_drv.o
>depmod:         proc_register
>depmod:         __generic_copy_from_user
>depmod:         parport_unregister_device
>depmod:         get_fast_time
>depmod:         schedule
>depmod:         __udelay
>depmod:         parport_enumerate
>depmod:         kmalloc
>depmod:         unregister_chrdev
>depmod:         register_chrdev
>depmod:         vfree
>depmod:         parport_register_device
>depmod:         proc_unregister
>depmod:         del_timer
>depmod:         kfree
>depmod:         vmalloc
>depmod:         parport_claim
>depmod:         parport_release
>depmod:         proc_root
>depmod:         sprintf
>depmod:         jiffies
>depmod:         printk
>depmod:         add_timer
>depmod:         __const_udelay
>depmod:         __generic_copy_to_user
>
>So any idea about what's going wrong ?
>Thanks
>François
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: ####@####.####
>For additional commands, e-mail: ####@####.####
>


----------------------------------------
####@####.####
----------------------------------------