Re: usb scanner

2008-03-04 Thread Warren Block

On Tue, 4 Mar 2008, Wojciech Puchar wrote:


tried plustek  opticpro st12

got:

ugen0: vendor 0x07b3 product 0x0600, rev 1.10/0.00, addr 2
ugen0: setting configuration index 0 failed
device_attach: ugen0 attach returned 6
ugen0: at uhub0 port 1 (addr 2) disconnected


and even /dev/ugen* doesn't exist so sane-find-scanner is unable to find 
anything


Usually that means the USB vendor and product IDs need to be added to 
uscanner.c (/usr/src/sys/dev/usb).  Scanners that require a firmware 
download may be different.


There are two variants of the ST12, and unfortunately, the 0x0600 
version is not currently supported by SANE:


http://www.sane-project.org/unsupported/plustek-opticpro-st12.html
http://www.meier-geinitz.de/sane/gt68xx-backend/

-Warren Block * Rapid City, South Dakota USA
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: usb scanner

2008-03-04 Thread Predrag Punosevac

Wojciech Puchar wrote:

tried plustek  opticpro st12

got:

ugen0: vendor 0x07b3 product 0x0600, rev 1.10/0.00, addr 2
ugen0: setting configuration index 0 failed
device_attach: ugen0 attach returned 6
ugen0: at uhub0 port 1 (addr 2) disconnected


and even /dev/ugen* doesn't exist so sane-find-scanner is unable to 
find anything


FreeBSD usually uses /dev/uscanner0  as a device node for scanners (and 
driver uscanner)unless you are using HPLIP driver.
It is true though that in OpenBSD some scanners has to be seen as 
/dev/ugen0 since uscanner driver for OpenBSD

does not support receiving vendor name and product.

Are you sure you have right permissions? Also for plustek backend you 
have to add your-self into _saned group.

Did you reboot (I hope not server:- the thing after you plug the scanner

What is the output of sane-find-scanner ? Which version of SANE-backends 
do you have. They came up 2 weeks ago with 1.19 release which I use on 
4.3 beta OpenBSD but on my FreeBSD machines the version is 1.17.


Did you check if the scanner is listed in the sane data base.

Cheers,

Predrag



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to 
[EMAIL PROTECTED]


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: usb scanner

2008-03-04 Thread Wojciech Puchar
Usually that means the USB vendor and product IDs need to be added to 
uscanner.c (/usr/src/sys/dev/usb).  Scanners that require a firmware download 
may be different.


thank you very much i will test it



There are two variants of the ST12, and unfortunately, the 0x0600 version is 
not currently supported by SANE:


http://www.sane-project.org/unsupported/plustek-opticpro-st12.html
http://www.meier-geinitz.de/sane/gt68xx-backend/

-Warren Block * Rapid City, South Dakota USA



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: usb scanner

2008-03-04 Thread Wojciech Puchar

ugen0: setting configuration index 0 failed
device_attach: ugen0 attach returned 6
ugen0: at uhub0 port 1 (addr 2) disconnected


and even /dev/ugen* doesn't exist so sane-find-scanner is unable to find 
anything


FreeBSD usually uses /dev/uscanner0  as a device node for scanners (and 
driver uscanner)unless you are using HPLIP driver.
It is true though that in OpenBSD some scanners has to be seen as /dev/ugen0 
since uscanner driver for OpenBSD

does not support receiving vendor name and product.


this device is not detected as uscanner, and attaching ugen fails - no 
/dev/.. for it exist.


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: USB scanner

2004-08-14 Thread Marc Fonvieille
On Sat, Aug 14, 2004 at 01:32:17PM +0400, Fractal wrote:
 Does uscanner driver on FreeBSD 4.8-stable support USB 2.0 interface?
 It seems that my scanner (EPSON Perfection 2400) does not work at 
 maximum speed. Besides this, it becomes inaccessible via scanimage 
 (sane-find-scanner also cannot find it) in several time interval 
 after system startup if it was not used during this time, and to 
 work with it again it's necessary to completely restart computer. 


4.8-STABLE is a bit old, could you try on a 4.10 please?

Marc
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: usb scanner won't work

2003-01-14 Thread chip wiegand
On Tue, 14 Jan 2003 20:19:33 -0700 (MST)
Warren Block [EMAIL PROTECTED] wrote:

 On Mon, 13 Jan 2003, chip wiegand wrote:
 
  Okay, I've checked the previous messages on the subject in the
  archives, still doesn't work. The handbook apparently has no info on
  setting up flat-bed scanners. There's nothing in the FAQ or other
  documents part of freebsd.org. I did read the xsane man page. I'm
  still stuck. Is there a tutorial of other doc available somewhere?
  My scanner - Umax 1220usb. My kernel does load uhci on boot up, usb
  does work, my usb mouse works. I installed xsane, backends and
  frontends. I edited umax1220u.conf like this:
 
  # Options for the umax1220u backend
  # Autodetect the UMAX Astra 1220U
  #usb 0x1606 0x0010
  usb 0x03F0 0x0605
 
 Does this apply to FreeBSD?

Yes

  # The following line enables autodetection for the
  # Astra 2000U. However, this driver isn't entirely
  # compatible, so expect color problems :)
  #usb 0x1606 0x0030
  # device list for non-linux-systems (enable if autodetect fails):
  #/dev/scanner
  /dev/uscanner0
 
 For my (working) Epson, I have
 
 usb /dev/uscanner0

Well, I'll give it a try...
--
Chip
 
 -Warren Block * Rapid City, South Dakota USA
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-questions in the body of the message
 

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message