The line was missing , I added it.
Now it shows up in the list:
=======================
[root@oldpc polaroid]# ldd /usr/local/bin/gphoto2
        libpthread.so.0 => /lib/libpthread.so.0 (0x4001c000)
        libreadline.so.4 => /usr/lib/libreadline.so.4 (0x4006e000)
        libncurses.so.5 => /usr/lib/libncurses.so.5 (0x4009a000)
        libgphoto2.so.2 => /usr/local/lib/libgphoto2.so.2 (0x400d9000)
        libgphoto2_port.so.0 => /usr/local/lib/libgphoto2_port.so.0 
(0x40151000)
        libm.so.6 => /lib/libm.so.6 (0x40158000)
        libpopt.so.0 => /usr/lib/libpopt.so.0 (0x40179000)
        libc.so.6 => /lib/libc.so.6 (0x40182000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
        libdl.so.2 => /lib/libdl.so.2 (0x402a7000)
=======================

So now I 'm back to the original condition, where I'm getting this:

Why would I be getting the message:
 >>> 2.195469 context(0): An error occurred in the io-library ('Bad 
parameters'): The supplied vendor or product id (0x0,0x0) is not valid.

when I added it to the source file, 
/libgphoto2-2.1.6/camlibs/polaroid/pdc640.c and make / make install again?

        /*  Added sept13,2005 - MJH - to get Clever CAM 360 working */
        {"Clever CAM 360", 0x797, 0x8001, {
                        jd350e,
                        BAYER_TILE_BGGR,
                        &jd350e_postprocessing_and_flip,
                        "scope%04i.ppm"
                }
        },
                                                                                
                                            


[root@oldpc root]# env LANG=C gphoto2 --debug --debug --camera "Polaroid 
PDC 640" --capture-image --port "usb:"

*******************************************************
0.002768 main(2): ALWAYS INCLUDE THE FOLLOWING LINE WHEN SENDING DEBUG 
MESSAGES TO THE MAILING LIST:
0.003323 main(2): gphoto2 2.1.0
0.003447 main(2): Setting port to 'usb:'...
0.003613 main(2): Setting camera model to 'Polaroid PDC 640'...
0.004123 gphoto2-filesystem(2): Internally appending folder /...
0.004571 gphoto2-port(2): Creating new device...
0.005044 gphoto2-abilities-list(2): Loading camera libraries in 
'/usr/lib/gphoto2/2.1.0'...
0.005301 gphoto2-abilities-list(2): Note that failing to load *.a and 
*.la is NOT an error!
0.008013 gphoto2-abilities-list(2): Trying to load 
'/usr/lib/gphoto2/2.1.0/libgphoto2_barbie.so'...
<snip>
1.391992 gp-port-info-list(2): Loading io-drivers from 
'/usr/lib/gphoto2_port/0.5.0'...
1.394710 gphoto2-port-serial(2): Trying to lock '/dev/ttyS0'...
1.418621 gphoto2-port-serial(2): Trying to lock '/dev/ttyS1'...
<snip>
2.135533 gphoto2-port-core(2): Loaded 'Serial Port 0' 
(serial:/dev/ttyS0) from 'libgphoto2_port_serial.so'
2.136482 gphoto2-port-core(2): Loaded 'Serial Port 1' 
(serial:/dev/ttyS1) from 'libgphoto2_port_serial.so'
<snip>
2.169005 gphoto2-port-core(2): Loaded '' (^serial) from 
'libgphoto2_port_serial.so'
2.173646 gphoto2-port-core(2): Loaded 'Universal Serial Bus' (usb:) from 
'libgphoto2_port_usb.so'
2.175443 gphoto2-camera(2): Setting abilities ('Polaroid PDC 640')...
2.176363 setting/gphoto2-setting.c(2): Creating $HOME/.gphoto
2.178246 setting/gphoto2-setting.c(2): Loading settings from file 
"/root/.gphoto/settings"
2.179376 gphoto2-setting(2): Setting key 'model' to value 'Polaroid PDC 
640' (gphoto2)
2.180274 gphoto2-setting(2): Saving 2 setting(s) to file 
"/root/.gphoto/settings"
2.182198 gphoto2-port-info-list(2): Looking for path 'usb:' (34 entries 
available)...
2.183101 gphoto2-port-info-list(2): Getting info of entry 32 (34 
available)...
2.183902 gphoto2-camera(2): Setting port info for port 'Universal Serial 
Bus' at 'usb:'...
2.189318 gphoto2-port(2): Setting timeout to 5000 millisecond(s)...
2.189979 gphoto2-port(2): Setting settings...
2.190849 gphoto2-setting(2): Setting key 'port' to value 'usb:' (gphoto2)
2.191555 gphoto2-setting(2): Saving 2 setting(s) to file 
"/root/.gphoto/settings"
2.193950 gphoto2-camera(2): Initializing camera...
2.194862 gphoto2-port(0): The supplied vendor or product id (0x0,0x0) is 
not valid.
2.195469 context(0): An error occurred in the io-library ('Bad 
parameters'): The supplied vendor or product id (0x0,0x0) is not valid.

*** Error ***
An error occurred in the io-library ('Bad parameters'): The supplied 
vendor or product id (0x0,0x0) is not valid.
ERROR: Could not capture.
*** Error ('Bad parameters') ***

*******************************************************

Stefan Leichter wrote:

>Hi Martin,
>
>do you have the line /usr/local/lib in you /etc/ld.so.conf file ? If not enter 
>it and rerun ldconfig.
>
>Bye Stefan
>
>  
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20050916/ecdf98c3/attachment.html
From belga...@gmx.de  Fri Sep 16 13:37:54 2005
From: belga...@gmx.de (Belgabor)
Date: Fri Sep 16 13:38:21 2005
Subject: [sane-devel] Epson Perfection 3490 -> included bugfix makes it
        work
References: <m38xxx5v1d....@pacbell.net>
Message-ID: <23539.1126877...@www58.gmx.net>

> 
> > Hi!
> > Good news for all you with an Epson Perfection 3490 USB scanner.
> 
> > Here is a bugfix to get the 'Epson Perfection 3490' scanner working.
> > It now makes perfect color *.pnm scans, at full A4 size.
> 
> > The details: I've been looking over some usbmon dumps and scanimage
> > debug logs, and the Perfection 3490 should just read 120 bytes even
> > when firmware isn't loaded yet.
> 
> > The fix is in snapscan-scsi.c.
> > Here are two kinds of diffs, I'm not sure which format is mandatory.
> > The diffs are against CVS snapshot sane-backends-2005-09-15.
> 
> I applied the diffs against the latest CVS source (locally, I don't have
> write access to the CVS), and I can confirm that it works for scanning
> the whole page.  (I haven't done any tests for other options yet.)
> 
I also have to thank for this patch (it came on the day I boght the scanner
without knowing about the issues). It is almost perfect as it works nice for
resolutions up to 1200 dpi. At 2400 and 3200 I get a combing effect. Every
other pixel column is offset by several pixels. It looks a bit like an
interlaced PAL TV picture (only the combing is vertical rather than
horizontal). 
Hints appreciated (also if someone could confirm this. The error isn't there
in windoze, so it doesn't seem to be a hardware problem).

Some final questions:
- Is there any way to make use of the buttons on the scanner? I tried
scannerbuttond, but it didn't work.
- Does scanimage/xscanimage scan with 24bit or 48bit depth? If the first is
the case, is there a way to scan with 48bit?

Cheers
Tobias

-- 
5 GB Mailbox, 50 FreeSMS http://www.gmx.net/de/go/promail
+++ GMX - die erste Adresse für Mail, Message, More +++

Reply via email to