| View previous topic :: View next topic |
| Author |
Message |
Decibels
Veteran
Joined: 16 Aug 2002
Posts: 1630
Location: U.S.A.
|
 Posted: Sun Jul 18, 2004 11:07 pm Post subject: |
 |
|
Out of time. but here is the list:
| Code: | bash-2.05b$ ls /usr/lib/sane
libsane-abaton.la libsane-matsushita.so.1.0.14
libsane-abaton.so libsane-microtek.la
libsane-abaton.so.1 libsane-microtek.so
libsane-abaton.so.1.0.14 libsane-microtek.so.1
libsane-agfafocus.la libsane-microtek.so.1.0.14
libsane-agfafocus.so libsane-microtek2.la
libsane-agfafocus.so.1 libsane-microtek2.so
libsane-agfafocus.so.1.0.14 libsane-microtek2.so.1
libsane-apple.la libsane-microtek2.so.1.0.14
libsane-apple.so libsane-mustek.la
libsane-apple.so.1 libsane-mustek.so
libsane-apple.so.1.0.14 libsane-mustek.so.1
libsane-artec.la libsane-mustek.so.1.0.14
libsane-artec.so libsane-mustek_pp.la
libsane-artec.so.1 libsane-mustek_pp.so
libsane-artec.so.1.0.14 libsane-mustek_pp.so.1
libsane-artec_eplus48u.la libsane-mustek_pp.so.1.0.14
libsane-artec_eplus48u.so libsane-mustek_usb.la
libsane-artec_eplus48u.so.1 libsane-mustek_usb.so
libsane-artec_eplus48u.so.1.0.14 libsane-mustek_usb.so.1
libsane-as6e.la libsane-mustek_usb.so.1.0.14
libsane-as6e.so libsane-nec.la
libsane-as6e.so.1 libsane-nec.so
libsane-as6e.so.1.0.14 libsane-nec.so.1
libsane-avision.la libsane-nec.so.1.0.14
libsane-avision.so libsane-net.la
libsane-avision.so.1 libsane-net.so
libsane-avision.so.1.0.14 libsane-net.so.1
libsane-bh.la libsane-net.so.1.0.14
libsane-bh.so libsane-pie.la
libsane-bh.so.1 libsane-pie.so
libsane-bh.so.1.0.14 libsane-pie.so.1
libsane-canon.la libsane-pie.so.1.0.14
libsane-canon.so libsane-plustek.la
libsane-canon.so.1 libsane-plustek.so
libsane-canon.so.1.0.14 libsane-plustek.so.1
libsane-canon630u.la libsane-plustek.so.1.0.14
libsane-canon630u.so libsane-plustek_pp.la
libsane-canon630u.so.1 libsane-plustek_pp.so
libsane-canon630u.so.1.0.14 libsane-plustek_pp.so.1
libsane-canon_pp.la libsane-plustek_pp.so.1.0.14
libsane-canon_pp.so libsane-qcam.la
libsane-canon_pp.so.1 libsane-qcam.so
libsane-canon_pp.so.1.0.14 libsane-qcam.so.1
libsane-coolscan.la libsane-qcam.so.1.0.14
libsane-coolscan.so libsane-ricoh.la
libsane-coolscan.so.1 libsane-ricoh.so
libsane-coolscan.so.1.0.14 libsane-ricoh.so.1
libsane-coolscan2.la libsane-ricoh.so.1.0.14
libsane-coolscan2.so libsane-s9036.la
libsane-coolscan2.so.1 libsane-s9036.so
libsane-coolscan2.so.1.0.14 libsane-s9036.so.1
libsane-dc210.la libsane-s9036.so.1.0.14
libsane-dc210.so libsane-sceptre.la
libsane-dc210.so.1 libsane-sceptre.so
libsane-dc210.so.1.0.14 libsane-sceptre.so.1
libsane-dc240.la libsane-sceptre.so.1.0.14
libsane-dc240.so libsane-sharp.la
libsane-dc240.so.1 libsane-sharp.so
libsane-dc240.so.1.0.14 libsane-sharp.so.1
libsane-dc25.la libsane-sharp.so.1.0.14
libsane-dc25.so libsane-snapscan.la
libsane-dc25.so.1 libsane-snapscan.so
libsane-dc25.so.1.0.14 libsane-snapscan.so.1
libsane-dll.la libsane-snapscan.so.1.0.14
libsane-dll.so libsane-sp15c.la
libsane-dll.so.1 libsane-sp15c.so
libsane-dll.so.1.0.14 libsane-sp15c.so.1
libsane-dmc.la libsane-sp15c.so.1.0.14
libsane-dmc.so libsane-st400.la
libsane-dmc.so.1 libsane-st400.so
libsane-dmc.so.1.0.14 libsane-st400.so.1
libsane-epson.la libsane-st400.so.1.0.14
libsane-epson.so libsane-tamarack.la
libsane-epson.so.1 libsane-tamarack.so
libsane-epson.so.1.0.14 libsane-tamarack.so.1
libsane-fujitsu.la libsane-tamarack.so.1.0.14
libsane-fujitsu.so libsane-teco1.la
libsane-fujitsu.so.1 libsane-teco1.so
libsane-fujitsu.so.1.0.14 libsane-teco1.so.1
libsane-gphoto2.la libsane-teco1.so.1.0.14
libsane-gphoto2.so libsane-teco2.la
libsane-gphoto2.so.1 libsane-teco2.so
libsane-gphoto2.so.1.0.14 libsane-teco2.so.1
libsane-gt68xx.la libsane-teco2.so.1.0.14
libsane-gt68xx.so libsane-teco3.la
libsane-gt68xx.so.1 libsane-teco3.so
libsane-gt68xx.so.1.0.14 libsane-teco3.so.1
libsane-hp.la libsane-teco3.so.1.0.14
libsane-hp.so libsane-test.la
libsane-hp.so.1 libsane-test.so
libsane-hp.so.1.0.14 libsane-test.so.1
libsane-hp5400.la libsane-test.so.1.0.14
libsane-hp5400.so libsane-u12.la
libsane-hp5400.so.1 libsane-u12.so
libsane-hp5400.so.1.0.14 libsane-u12.so.1
libsane-hpsj5s.la libsane-u12.so.1.0.14
libsane-hpsj5s.so libsane-umax.la
libsane-hpsj5s.so.1 libsane-umax.so
libsane-hpsj5s.so.1.0.14 libsane-umax.so.1
libsane-ibm.la libsane-umax.so.1.0.14
libsane-ibm.so libsane-umax1220u.la
libsane-ibm.so.1 libsane-umax1220u.so
libsane-ibm.so.1.0.14 libsane-umax1220u.so.1
libsane-leo.la libsane-umax1220u.so.1.0.14
libsane-leo.so libsane-umax_pp.la
libsane-leo.so.1 libsane-umax_pp.so
libsane-leo.so.1.0.14 libsane-umax_pp.so.1
libsane-ma1509.la libsane-umax_pp.so.1.0.14
libsane-ma1509.so libsane-v4l.la
libsane-ma1509.so.1 libsane-v4l.so
libsane-ma1509.so.1.0.14 libsane-v4l.so.1
libsane-matsushita.la libsane-v4l.so.1.0.14
libsane-matsushita.so libsane.so.1
libsane-matsushita.so.1 |
_________________
Support bacteria – they’re the only culture some people have.”
– Steven Wright |
|
| Back to top |
|
 |
schmeggahead
Guru
Joined: 25 Feb 2003
Posts: 314
Location: Columbus, Ohio
|
| Posted: Mon Jul 19, 2004 1:41 am Post subject: |
|
|
moved scanner to another usb port (the one that my keyboard works from) and it worked.
No kernel usb scanner support. However I enable scsi support.
commented out everything in the etc/sane.d/dll.conf except hp
/etc/sane.d/hp.conf contains:
| Code: | /dev/usb/scanner0
option connect-device
|
Not sure whether the other ports are not functioning or not supported.
acquired and image and printed.
going back to ensure all these settings are necessary. |
|
| Back to top |
|
|
Mekoryuk
Apprentice
Joined: 17 Sep 2003
Posts: 174
|
| Posted: Wed Aug 11, 2004 4:47 pm Post subject: |
|
|
For those with Epson scanners getting that strange USBFS_BULK whatnot error in their dmesg output:
Comment epson out of your /etc/sane.d/dll.conf file.
Worked for me (even without doing anything in this thread), and hopefully it will work for some of you. =) Apparently there's some weird bug in the epson backend. Commenting out epson most likely makes it revert to the plustek backend instead. Spotted this fix on a sane mailing list.
I'm kinda pissed that it was this easy for me to solve. I wasted DAYS trying to get my scanner to work, bounced around a few distros (Mandrake, SuSE) before coming back to Gentoo, determined to fix this damn problem. And then... all it involved was commenting out one line.
Oh well. I still love you, Linux. =P |
|
| Back to top |
|
|
Gentree
Watchman
Joined: 01 Jul 2003
Posts: 5350
Location: France, Old Europe
|
| Posted: Sun Sep 12, 2004 6:49 pm Post subject: |
|
|
OK here we go again.
Update a couple packages and a nice working , stable system starts to fall apart.
If I recall from earlier I updated libusb and udev (mad wreckless bastard that I am.)
I now have no scanner , no scanner device and hotplugging no longer works.
Let's have a quick sound off of who is in the same boat.
I wish this stuff would get tested before being committed to portage. I get really sick of this time-wasting.
_________________
Linux, because I'd rather own a free OS than steal one that's not worth paying for.
Gentoo because I'm a masochist
AthlonXP-M on A7N8X. Portage ~x86 |
|
| Back to top |
|
|
Gentree
Watchman
Joined: 01 Jul 2003
Posts: 5350
Location: France, Old Europe
|
| Posted: Sun Sep 12, 2004 7:28 pm Post subject: |
|
|
OK , update.
libusb was not altered at dev-libs/libusb-0.1.8
I now regressed to sys-fs/udev-030 did etc-update to revert the changes done earlier and I seems to have come back together.
Few. 
_________________
Linux, because I'd rather own a free OS than steal one that's not worth paying for.
Gentoo because I'm a masochist
AthlonXP-M on A7N8X. Portage ~x86
Last edited by Gentree on Thu Oct 28, 2004 10:24 pm; edited 1 time in total |
|
| Back to top |
|
|
Doogman
Apprentice
Joined: 24 Sep 2004
Posts: 244
|
| Posted: Fri Sep 24, 2004 2:16 pm Post subject: |
|
|
| Mekoryuk wrote: | For those with Epson scanners getting that strange USBFS_BULK whatnot error in their dmesg output:
Comment epson out of your /etc/sane.d/dll.conf file.
|
A thousand thank-you's! I don't care if your post is a month old or not, but it just saved me from pulling _all_ my hair out. Thank you Google search!  This fixed my last big hardware problem from my Fedora -> Gentoo migration. For others:
Keywords: Epson Perfection 1260 scanner gentoo
Walkthough:
Obviously, emerge all the sane goodies. You should see this:
doug@ghidorah doug $ sane-find-scanner
found USB scanner (vendor=0x04b8 [EPSON], product=0x011d [EPSON Scanner], chip=LM9832/3) at libusb:001:004
Add group "scanner" to your groups and log-back in again. You should see this:
doug@ghidorah doug $ groups
tty wheel audio users scanner <---
Edit /etc/sane.d/plustek.conf and add these:
[usb] 0x04b8 0x011d
device auto
And then comment-out this line in /etc/sane.d/dll.conf
dmc
#epson
fujitsu
You _must_ comment out the epson line to disable the epson driver or you will get these errors in the kernel log:
Sep 24 09:41:50 [kernel] usb 1-2: bulk timeout on ep2in
Sep 24 09:41:50 [kernel] usb 1-2: usbfs: USBDEVFS_BULK failed ep 0x82 len 4 ret
-110
And then you will put of your hair for a hour and wonder why!
Scanner works fine! No need to mess with the scripts. All the permissions are set correctly. |
|
| Back to top |
|
|
emanuelgreisen
n00b
Joined: 26 Apr 2004
Posts: 6
|
| Posted: Tue Oct 05, 2004 11:25 am Post subject: HP 5200C |
|
|
I have a HP 5200C scanner, and I keep getting the darn warnings every now and then. Sometimes my scanner works, sometimes it doesn't... if it starts giving the warnings, there is not chance it will start working though.
Here is some output from dmesg
| Code: |
hub 2-0:1.0: port 1, status 0101, change 0001, 12 Mb/s
hub 2-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x101
usb 2-1: new full speed USB device using address 8
usb 2-1: new device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-1: default language 0x0409
usb 2-1: Product: HP ScanJet 5200C
usb 2-1: control timeout on ep0in
usb 2-1: Manufacturer: Hewlett-Packard
usb 2-1: SerialNumber: SG02F170X2HT
usb 2-1: hotplug
usb 2-1: adding 2-1:1.0 (config #1, interface 0)
usb 2-1:1.0: hotplug
usb 2-1: bulk timeout on ep1in
usb 2-1: usbfs: USBDEVFS_BULK failed ep 0x81 len 4096 ret -110
usb 2-1: bulk timeout on ep1in
usb 2-1: usbfs: USBDEVFS_BULK failed ep 0x81 len 4096 ret -110
usb 2-1: bulk timeout on ep1in
usb 2-1: usbfs: USBDEVFS_BULK failed ep 0x81 len 4096 ret -110
usb 2-1: bulk timeout on ep1in
usb 2-1: usbfs: USBDEVFS_BULK failed ep 0x81 len 4096 ret -110
usb 2-1: bulk timeout on ep1in
usb 2-1: usbfs: USBDEVFS_BULK failed ep 0x81 len 4096 ret -110
|
To make it work (sometimes), I unplug the USB-cable, turn of the scanner, restart the machine, turn on the scanner and plug in the USB cable. Then (if I am lucky it works... very windowish).
I have just updated to the lates sane-(b/f), xsane and libusb. And my kernel-version is as follows.:
sane-frontends-1.0.12
sane-backends-1.0.14-r6
xsane-0.95
libusb-0.1.8
gentoo-dev-sources-2.6.8-r3
I tried disabling hotplug (as someone mentioned earlier i the thread) but without success, since then my scanner is not detected at all.
I tried to run xsane like this:
SANE_DEBUG_HP=127 xsane
This gives a lot of debug-messages, but does not fix the problem. (some one had this fix it for him, thinking maybe the debugging had some sideeffects).
When using xsane, if it does not work, I eventually get the "Error during read: Error during device I/O".
Any help, pointers, anything would be appreciated, I am stuck, and I have spend hours trying all kind of things.
_________________
./Emanuel |
|
| Back to top |
|
|
emanuelgreisen
n00b
Joined: 26 Apr 2004
Posts: 6
|
| Posted: Tue Oct 05, 2004 1:29 pm Post subject: Maybe found something |
|
|
Ok, now I found a way to force the scanner into scanning. Its not pretty... but it does the job (sooner or later).
Run xsane with the following environment-vars set:
| Code: |
SANE_DEBUG_SANEI_USB=8 SANE_HP_RDREDO=100 xsane
|
Not sure if the SANE_DEBUG_SANEI_USB-var is nessesary, but the retry-variable is !
An interesting thing though is that running with this much debug, I find two parts of the output that makes me wonder....
| Code: |
[sanei_debug] Setting debug level of sanei_usb to 8.
usb_set_debug: Setting debugging level to 255 (on)
usb_os_find_busses: Found 004
usb_os_find_busses: Found 003
usb_os_find_busses: Found 002
usb_os_find_busses: Found 001
usb_os_find_busses: Skipping non bus directory devices
usb_os_find_devices: Found 001 on 004
usb_os_find_devices: Found 016 on 003
usb_os_find_devices: Found 001 on 003
usb_os_find_devices: Found 001 on 002
usb_os_find_devices: Found 001 on 001
[sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like a root hub
[sanei_usb] sanei_usb_init: found libusb device (0x03f0/0x0401) interface 0 at
libusb:003:016
[sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like a root hub
[sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like a root hub
[sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like a root hub
[sanei_usb] sanei_usb_init: found 1 devices
[sanei_usb] sanei_usb_find_devices: vendor=0x03f0, product=0x0401, attach=0x4013
0f26
[sanei_usb] sanei_usb_open: trying to open device `libusb:003:016'
[sanei_usb] sanei_usb_open: found bulk-in endpoint (address 1)
[sanei_usb] sanei_usb_open: found bulk-out endpoint (address 2)
[sanei_usb] sanei_usb_open: found interupt-in endpoint (address 3)
[sanei_usb] sanei_usb_open: opened usb device `libusb:003:016' (*dn=0)
[sanei_usb] sanei_usb_write_bulk: trying to write 2 bytes
[sanei_usb] sanei_usb_write_bulk: wanted 2 bytes, wrote 2 bytes
[sanei_usb] sanei_usb_write_bulk: trying to write 7 bytes
...
(-- A lot more debug mess --)
...
[sanei_usb] sanei_usb_read_bulk: attempt read libusb 16 bytes ep=0x81 timeout=30000
[sanei_usb] sanei_usb_read_bulk: result 9
[sanei_usb] sanei_usb_read_bulk: wanted 16 bytes, got 9 bytes
[sanei_usb] sanei_usb_close: closing device 0
[sanei_usb] sanei_usb_open: trying to open device `libusb:003:016'
[sanei_usb] sanei_usb_open: found bulk-in endpoint (address 1)
[sanei_usb] sanei_usb_open: we already have a bulk-in endpoint (address: 129), ignoring the new one
[sanei_usb] sanei_usb_open: found bulk-out endpoint (address 2)
[sanei_usb] sanei_usb_open: we already have a bulk-out endpoint (address: 2), ignoring the new one
[sanei_usb] sanei_usb_open: found interupt-in endpoint (address 3)
[sanei_usb] sanei_usb_open: we already have a int-in endpoint (address: 131), ignoring the new one
[sanei_usb] sanei_usb_open: opened usb device `libusb:003:016' (*dn=0)
...
(-- Even more debug mess --)
|
Now does it not seem weird that it openes the device, says all kind of stuff to it, then closes it again, and becomes surpriced that it already has ep1/ep2/ep3 set...
_________________
./Emanuel |
|
| Back to top |
|
|
wendall911
n00b
Joined: 16 Jul 2003
Posts: 19
|
| Posted: Wed Oct 06, 2004 1:14 am Post subject: USB Scanner How-to |
|
|
First off, I got my inspiration for how to resolve the scanner issue from this thread, so thanks for beating up on things.
First of all, per the install documentation, you will need hotplug.
| Code: | emerge hotplug
rc-update add hotplug default |
2. Assuming you followed the install docs and your user isn't in the scanner group, stop hotplug.
| Code: | | /etc/init.d/hotplug stop |
3. Add your user to the scanner group. Hotplug sets the entry in the /proc file system to root:scanner 0660 so your user will need to be in the scanner group.
| Code: | | usermod -g scanner yourusername |
4. Emerge sane tools.
| Code: | | emerge sane-backends sane-frontends |
5. Plug in your usb scanner and plug it into power. Start hotplug.
| Code: | | /etc/init.d/hotplug start |
6. Create a launcher for xscanimage. Have fun!
The only problem I have with xscanimage is that it fails to do a damn thing if the scanner isn't plugged into a usb port, power, etc. Sucks for newb users since it doesn't even produce a popup to warn the user that the scanner isn't accessible.
I could rant about how easy it would be to make scanners just work, but that is an issue for the distribution to figure out. Guess this is why I use Gentoo, so I know exactly why things do what they do.
Wendall |
|
| Back to top |
|
|
emanuelgreisen
n00b
Joined: 26 Apr 2004
Posts: 6
|
| Posted: Wed Oct 06, 2004 6:45 am Post subject: Additional note about ownership |
|
|
Well, with "sane-backends-1.0.14-r6" on gentoo follows a file /etc/hotplug/usb/libusbscanner, in this file you find the followin lines:
| Code: |
chown root:scanner "$DEVICE"
chmod 0660 "$DEVICE"
|
this can be changed to
| Code: |
chown root:scanner "$DEVICE"
chmod 0666 "$DEVICE"
|
Or you can add an ownership modifying line too
| Code: |
chown youruser:yourgroup "$DEVICE"
chmod 0660 "$DEVICE"
|
Just makeing sure no one thought there were some woodoo going on around this hotplugging and ownership of scanners.
_________________
./Emanuel |
|
| Back to top |
|
|
simon_irl
Guru
Joined: 07 Oct 2004
Posts: 403
Location: New Zealand
|
| Posted: Wed Oct 27, 2004 2:49 am Post subject: found scanner under /proc/bus/usb |
|
|
| Thanks Elm0...your post was what I'd been looking for all over the Net for about an hour...I just wanted to find my scanner in the filesystem! I'm used to /dev/usb/, not /proc/bus/usb/, but with lsusb it's perfectly straightforward. Thanks again. |
|
| Back to top |
|
|
Doudou
Apprentice
Joined: 10 Jan 2003
Posts: 286
Location: Paris, France
|
| Posted: Sun Nov 07, 2004 4:01 pm Post subject: |
|
|
Hi,
I had a look on this post and other in the web but I couldn't find the solution of my problem...
In fact, whith a scanimage -L, I get a no scanner one time of two :
| Code: | doudou@gladiatux doudou $ scanimage -L
device `epson:libusb:002:005' is a Epson GT-7000 flatbed scanner
doudou@gladiatux doudou $ scanimage -L
device `epson:libusb:002:005' is a Epson GT-7000 flatbed scanner
doudou@gladiatux doudou $ scanimage -L
No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).
doudou@gladiatux doudou $ scanimage -L
device `epson:libusb:002:005' is a Epson GT-7000 flatbed scanner
doudou@gladiatux doudou $ scanimage -L
No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).
doudou@gladiatux doudou $ scanimage -L
device `epson:libusb:002:005' is a Epson GT-7000 flatbed scanner
doudou@gladiatux doudou $ scanimage -L
No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).
|
I have good right on USB :
| Code: | gladiatux root # ll /proc/bus/usb/002/005
-rw-rw---- 1 root scanner 50 nov 7 16:30 /proc/bus/usb/002/005
doudou@gladiatux doudou $ groups
audio ftp video games users portage scanner
|
I've already tried with 770 right but I've got the same result...
Do you know why it works one time of two? Do you think using EPSON driver should resolve the problem? |
|
| Back to top |
|
|
picklestix
n00b
Joined: 15 Jan 2005
Posts: 72
|
| Posted: Wed Jan 19, 2005 8:04 pm Post subject: Still fustrated.... |
|
|
Anyone else out there with a Epson 2450 Photo that has all but given up hope?
I'm going on weeks spent on this now.
Here is the summary of what I have. (~x86, gentoo-dev-sources,udev,libusb)
I've tried all the config settings in this forum.
With epson commented out, as suggested here, from dll.conf, dmesg shows
| Code: | | serial8250: too much work for irq11 |
Scanimage -L shows no scanner found(with changes also made to plustek.conf). I believe this scanner is not compatable with the plustek backend workaround.
With epson in, dmesg shows the infamous USBDEVFS_BULK fail.
Scanimage -L gives correct result every OTHER time, as so many others also seem to be getting.
Like everyone else, sane-find-scanner *always* shows the scanner.
I have tried multiple other configurations as listed on these forums, and all as regular and root user. I'm also in the scanner group.
I have also tried the epkowa backend, and epsons scanning utility. Same result.
I have posted a bug report to libusb project on sourceforge. Where to go from here? gentoo bugzilla bug reports for libusb? sane backend bug reports?
Any advice would be greatly appreciated. |
|
| Back to top |
|
|
Gentree
Watchman
Joined: 01 Jul 2003
Posts: 5350
Location: France, Old Europe
|
| Posted: Wed Jan 19, 2005 8:39 pm Post subject: |
|
|
dont bother scratching your head about what driver to use if sane cant even see the presence of the scanner.
I gave up on xsane last summer having wasted loads of time like you.
At that stage it did recognise my Epson 1670 photo but as soon as I tried to scan anything it locked up completely.
Now it does not even see the scanner , as you also report.
I now use vuescan . At that time there was a free-for-personal-use version for Linux but I'm not sure if that is still the case . I think there is a time limitted offer , o/w you may find something that works on p2p.
In any case vuescan is very effective , it still locks up if I use a usb2.0 port (probably a gentoo issue rather than the software) but it works perfectly on USB1.
Also make a very good job of neg scans.
HTH
_________________
Linux, because I'd rather own a free OS than steal one that's not worth paying for.
Gentoo because I'm a masochist
AthlonXP-M on A7N8X. Portage ~x86 |
|
| Back to top |
|
|
picklestix
n00b
Joined: 15 Jan 2005
Posts: 72
|
| Posted: Wed Jan 19, 2005 10:06 pm Post subject: |
|
|
Well, epson-find-scanner IS detecting the scanner...That is the only thing that's consistent.
Seems most people having difficulties with this all had no issues with the kernel scanning module. I just don't want to revert to devfs and a 2.4 kernel just to run my scanner...
It seems like many have gotten around this problem, but I think many more have given up......?
Will definatly check into viewscan though, thank you.
I still have scanner functionability in windoze, but this is the only thing I haven't been able to bring over to linux. I hate having the wasted space of an entire operating system on my hd just for a scanning driver............... |
|
| Back to top |
|
|
Gentree
Watchman
Joined: 01 Jul 2003
Posts: 5350
Location: France, Old Europe
|
| Posted: Thu Jan 20, 2005 8:41 pm Post subject: |
|
|
Yep, it seems xsane still is not upto speed on 2.6 kernels although this is not exactly cutting-edge technology any more.
BTW it vuescan not viewscan just incase you cant find it.
_________________
Linux, because I'd rather own a free OS than steal one that's not worth paying for.
Gentoo because I'm a masochist
AthlonXP-M on A7N8X. Portage ~x86 |
|
| Back to top |
|
|
Matteo Azzali
Retired Dev
Joined: 23 Sep 2004
Posts: 1133
|
| Posted: Mon Jan 24, 2005 8:10 pm Post subject: |
|
|
With the latests kernels,
from my experience: do not follow any tutorial, howto or similar.
Check the support (and in case the firmware file you will need)
here .
then with usb and gimp flags in make.conf do:
| Code: | emerge sane-backends sane-frontends
scanimage -L |
modify /etc/sane.d/XXX.conf (your backend) to point to the firmware file
and then enjoy!!!!
(after following 3 differents howto [none worked] I just did that and it
worked fine -epson perfection 1670- snapscan backend)
_________________
Every day a new distro comes to birth. Every day a distro "eats" another.
If you're born distro, no matter what, start to run.
---- http://www.linuxprinting.org/ ---- http://tuxmobil.org/ |
|
| Back to top |
|
|
Gentree
Watchman
Joined: 01 Jul 2003
Posts: 5350
Location: France, Old Europe
|
| Posted: Mon Jan 24, 2005 11:39 pm Post subject: |
|
|
Thanks , that's (fairly) good news. I'll check it out.
1600 dpi does not work acording to sane.org , so much for buying a hi-res scanner and of course no mention of photo scan capability but it is a generic use of the snapscan driver so not surprising.
Anyway, if it does something under sane I will be pleased.
BTW have you tried it on usb2 ?
I am not sure if that is a failing vuescan I am seeing or my PCI usb card or linux usb drivers.
Be nice if you had some input there.
Thx again.
_________________
Linux, because I'd rather own a free OS than steal one that's not worth paying for.
Gentoo because I'm a masochist
AthlonXP-M on A7N8X. Portage ~x86 |
|
| Back to top |
|
|
Matteo Azzali
Retired Dev
Joined: 23 Sep 2004
Posts: 1133
|
| Posted: Tue Jan 25, 2005 3:54 pm Post subject: |
|
|
I'm using 2.6.10-r6 kernel, a viaKt400 board with usb2 support.
I have both ehci and uhci usb modules directly compiled inside kernel.
I'm using udev. (hald, hotplug, etc.etc.)
check scanimage -L and then a scan with scanimage (from command line).
If them worked u can install sane-frontends wich contains xscanimage
(with "gimp" USE flag you get also the gimp plugin for scanning).
If all that worked you can test the scan features of other programs.
_________________
Every day a new distro comes to birth. Every day a distro "eats" another.
If you're born distro, no matter what, start to run.
---- http://www.linuxprinting.org/ ---- http://tuxmobil.org/ |
|
| Back to top |
|
|
Gentree
Watchman
Joined: 01 Jul 2003
Posts: 5350
Location: France, Old Europe
|
| Posted: Sun Jan 30, 2005 3:26 am Post subject: |
|
|
Thanks ,
two odd things here. I found I need the esfw30.bin firmware for the 1670 photo on snapscan.conf .
The sane site says it is in sanefront-ends but I dont find it anywhere on my system , I had to go and trawl the net for it.
I now find it with scanimage -L . fine.
I had to down grade to libusb 1.0.7-r1 since 1.0.8 left everthing broken .
However I still have a library issue with xscanimage
| Code: | -bash-3.00#xscanimage
xscanimage: error while loading shared libraries: libusb-0.1.4: cannot open shared object file: No such file or directory
|
These are the ONLY versions in portage now , are others not seeing these breakages?
Thx
_________________
Linux, because I'd rather own a free OS than steal one that's not worth paying for.
Gentoo because I'm a masochist
AthlonXP-M on A7N8X. Portage ~x86 |
|
| Back to top |
|
|
Matteo Azzali
Retired Dev
Joined: 23 Sep 2004
Posts: 1133
|
| Posted: Sun Jan 30, 2005 10:37 am Post subject: |
|
|
I'm using libusb 1.0.8 , all working like a charm (i can turn-on and off
scanner while in a session, etc.etc., 1600 dpi not tested).
esfw30.bin is a file provided in the 1670 drivers-CD , you can try to
extract from the cd or get it from a windows with 1670 drivers installed
(system[32] folder).
Dunno why your machine have these problems, but on my
~x86 tree they all working. Have you masked some dependency?
_________________
Every day a new distro comes to birth. Every day a distro "eats" another.
If you're born distro, no matter what, start to run.
---- http://www.linuxprinting.org/ ---- http://tuxmobil.org/ |
|
| Back to top |
|
|
Gentree
Watchman
Joined: 01 Jul 2003
Posts: 5350
Location: France, Old Europe
|
| Posted: Sun Jan 30, 2005 9:57 pm Post subject: |
|
|
Thanks,
I recently went all ~x86 figuring it could not be more unstable than running stable.
Went throughs serveral _days_ worth of emerge -e system... system... world... world.... phew.
I'm not sure its better but it sure aint less together, I still have a couple of outstanding issues. This is one of them.
Could you post a few version numbers for me so I can compare.
emerge -p udev baselayout libusb sane-backends sane xsane
TIA.
_________________
Linux, because I'd rather own a free OS than steal one that's not worth paying for.
Gentoo because I'm a masochist
AthlonXP-M on A7N8X. Portage ~x86 |
|
| Back to top |
|
|
Matteo Azzali
Retired Dev
Joined: 23 Sep 2004
Posts: 1133
|
| Posted: Mon Feb 07, 2005 5:54 pm Post subject: |
|
|
all the most recent:
[ebuild R ] sys-fs/udev-051
[ebuild R ] sys-apps/baselayout-1.11.9-r1
[ebuild R ] dev-libs/libusb-0.1.8
[ebuild R ] media-gfx/sane-backends-1.0.15
[ebuild R ] media-gfx/sane-frontends-1.0.13
no xsane, i just compiled sane-frontends with gimp use flag
(for gimp plugin AND xscanimage).
However, after some bad upgrade, now I'm getting
| Code: |
*** glibc detected *** corrupted double-linked list:
|
and I have to figure out what's that (glibc corrupted?)
_________________
Every day a new distro comes to birth. Every day a distro "eats" another.
If you're born distro, no matter what, start to run.
---- http://www.linuxprinting.org/ ---- http://tuxmobil.org/ |
|
| Back to top |
|
|
Dragonlord
Guru
Joined: 22 Aug 2004
Posts: 446
Location: Switzerland
|
| Posted: Mon Feb 07, 2005 7:42 pm Post subject: |
|
|
problem: HP ScanJet 4100C with f***ing linusb... result? does not work at all although the scanner is fully supported.
dmegs:
| Code: | | usb 3-1: new full speed USB device using uhci_hcd and address 5 |
good...
lsusb:
| Code: | | Bus 003 Device 005: ID 03f0:0101 Hewlett-Packard ScanJet 4100c |
very good.
hp.conf:
| Code: | scsi HP
usb 0x03f0 0x0101 |
let's go.
sane-find-scanner:
| Code: |
# No SCSI scanners found. If you expected something different, make sure that
# you have loaded a SCSI driver for your SCSI adapter.
# No USB scanners found. If you expected something different, make sure that
# you have loaded a driver for your USB host controller and have installed a
# kernel scanner module.
# Not checking for parallel port scanners.
# Most Scanners connected to the parallel port or other proprietary ports
# can't be detected by this program. |
WTF?!
scanimage -L:
| Code: | [sanei_debug] Setting debug level of dll to 255.
[dll] sane_init: SANE dll backend version 1.0.11 from sane-backends 1.0.15
[dll] sane_init: reading dll.conf
[dll] add_backend: adding backend `hp'
[dll] sane_get_devices
[dll] load: searching backend `hp' in `/usr/lib/sane'
[dll] load: trying to load `/usr/lib/sane/libsane-hp.so.1'
[dll] load: dlopen()ing `/usr/lib/sane/libsane-hp.so.1'
[dll] init: initializing backend `hp'
[sanei_debug] Setting debug level of hp to 255.
[hp] sane_init called
[hp] hp_init: global.is_up = 1
[hp] sane_init will finish with Success
[dll] init: backend `hp' is version 1.0.8
[hp] sane_get_devices called
[hp] hp_read_config: hp backend v1.06/$Revision: 1.21 $ starts reading config file
[hp] hp_read_config: processing line <#scsi HP>
[hp] hp_read_config: processing line <# Uncomment the following if you have "Error during device I/O" on SCSI>
[hp] hp_read_config: processing line <# option dumb-read>
[hp] hp_read_config: processing line <#>
[hp] hp_read_config: processing line <# The usual place for a SCSI-scanner on Linux>
[hp] hp_read_config: processing line <#/dev/scanner>
[hp] hp_read_config: processing line <#>
[hp] hp_read_config: processing line <# USB-scanners supported by the hp-backend>
[hp] hp_read_config: processing line <# HP ScanJet 4100C>
[hp] hp_read_config: processing line <#usb 0x03f0 0x0101 libusb:003:004>
[hp] hp_read_config: processing line <# HP ScanJet 5200C>
[hp] hp_read_config: processing line <#usb 0x03f0 0x0401>
[hp] hp_read_config: processing line <# HP ScanJet 62X0C>
[hp] hp_read_config: processing line <#usb 0x03f0 0x0201>
[hp] hp_read_config: processing line <# HP ScanJet 63X0C>
[hp] hp_read_config: processing line <#usb 0x03f0 0x0601>
[hp] hp_read_config: processing line <#>
[hp] hp_read_config: processing line <# Uncomment the following if your scanner is connected by USB,>
[hp] hp_read_config: processing line <# but you are not using libusb>
[hp] hp_read_config: processing line <# /dev/usb/scanner0>
[hp] hp_read_config: processing line <# option connect-device>
[hp] hp_read_config: processing line <#connect-scsi HP>
[hp] hp_read_config: processing line <#usb libusb:003:004>
[hp] hp_read_config: processing line <>
[hp] hp_read_config: processing line <scsi HP>
[hp] hp_read_config: processing line <usb 0x03f0 0x0101>
[hp] hp_attach_matching_devices: attach matching scsi HP
[hp] hp_read_config: attach usb 0x03f0 0x0101
[hp] hp_attach_matching_devices: usb attach matching "usb 0x03f0 0x0101"
[hp] hp_read_config: reset to default config
[hp] sane_get_devices will finish with Success
[dll] sane_get_devices: found 0 devices
No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).
[dll] sane_exit: exiting
[dll] sane_exit: calling backend `hp's exit function
[hp] sane_exit called
[hp] hp_destroy: global.is_up = 0
[hp] sane_exit will finish
[dll] sane_exit: finished |
WTF?! nothing found?!
why does it not find it? since the change to libusb i can not scan anymore... i read all i could... nothing helps.
it's up to you... somebody knows what the f*** is up there? (this libusb really starts to **** me off U_U ).
_________________
DragonDreams: Leader and Head Programmer |
|
| Back to top |
|
|
Gentree
Watchman
Joined: 01 Jul 2003
Posts: 5350
Location: France, Old Europe
|
| Posted: Mon Feb 07, 2005 11:38 pm Post subject: |
|
|
Could not have put it better myself 
I found libusb-0.1.8 messed thikngs up:
| Code: | bash-3.00#xscanimage
xscanimage: error while loading shared libraries: libusb-0.1.so.4: cannot open shared object file: No such file or directory
|
This sort of thing happens fairly often (yes even on 'stable' before someone shouts me down) .
Try masking 0.1.8 , 0.1.7-r1 does at least link the lib although the chances are your printer and/or scanner still wont work. sigh.
Here, scanner works , print not. 
_________________
Linux, because I'd rather own a free OS than steal one that's not worth paying for.
Gentoo because I'm a masochist
AthlonXP-M on A7N8X. Portage ~x86 |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
