scanimage -L needs the entries from /etc/sane.d/*.dll & *.conf .
After installing the epkowa backend -2.26.4dotPET and adjusting the entries in /etc/sane.d/dll.conf

epjitsu
#epson
#epson2
epkowa
fujitsu

and commenting all lines in epkowa.conf despite

#usb 0x04b8 0x084f
usb 0x04b8 0x0851
#usb 0x04b8 0x0854

nothing works :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).

The epkowa seemed to work nicely with iscan on other puppies but here i think i have to figure out how to unload the builtin kernel driver usb-storage .... [ something like "echo 0 > /sys/ / / /usb/file" ]

My problem might be also related to USB-1.1 ....

While xsane also refused to work continuously on some puppies with the usblp and usb-storage drivers inserted , it seems to work here despite it causes these error messages in dmesg also ....

Confusing , but xsane seems not to need or to use the xscanimage binary ; perhaps usees the "scanimage" binary .

But now after a successful "scanimage -T" the scanner hangs showing "Scanning..." in the display after "scanimage -v -T" ....

Since you have not yet named your printer model, I will assume that it is either a Stylus NX410 or SX410. SANE lists these models as being compatible with the epson2 backend, and we know that they work with Xsane.

However, many recent models, including your NX410, use the epkowa driver. So I don't understand why scanimage -L does not detect it.

I also don't understand why you are messing with the USB modules. I have yet to see a printer/scanner in any Puppy that required that. Unless it has something to do with your particular machine and USB 1.0.

Since iscan should also work with your model, there is something else going on here.

Yes , it is a SX415 on the outside of the chassis , but most detection tools say it would be a SX410 .
I don't know if that is related to the usb.ids file . I will cat /sys and /proc for this .

Nevertheless peasyscan will not work with the sane-backend 1.0.20 , too .

Removing usblp and usb-storage || boot with usb-storage.quirks=04b8:0851:i to ignore the usb-storage part of the
scanner did not help either : No error messages in dmesg but still the message-GUI with
Failed to open device `epson2:libusb:001:008' : Invalid argument .

So I will explore the sane|xsane versions more precisely , because with sane-backend-1.0.20 I have 'bin' for black&whiite
and with sane-backend-1.0.21 'lineart' and few other things like the 'Threshold' slider in xsane
not showing up at all '0996+0998' or if it vanishes , it does not reappear except closing and starting xsane again '0997' .

Independent of Peasyscan, Epson claims that your SX410/415 is designed for the epkowa backend and iscan. So "scanimage -L" should definitely detect it and iscan should work with it. So Xsane should be giving you two choices for the backend.

Since none of that is happening, I am sure that this is a hardware issue. Do you have another machine to test this on?

Also, I know for a fact that an NX415 does work with epkowa. So I am surprised that an SX415 does not.

Once you can get the epkowa backend detected, I am sure that Peasysan will work for you. But it definitely won't work with the epson2 backend.

I tested it myself and there were no problems. Lacking any specific info, here are some suggestions:

1. Has your printer changed its IP address?
2. Have you addressed the firewall issue?
3. Did you install the HPLIP scanner driver again?
4. Did you update your Peasyscan config file?
5. Is it working with USB?

I tested it myself and there were no problems. Lacking any specific info, here are some suggestions:

1. Has your printer changed its IP address?
2. Have you addressed the firewall issue?
3. Did you install the HPLIP scanner driver again?
4. Did you update your Peasyscan config file?
5. Is it working with USB?

Ha ha.. I put a bit more on the Slacko thread. IP address correct, firewall addressed, installed scanner driver (its a new install of Slacko RC, fresh save file), updated config file, yes, it works on USB. HP printer, wifi. My guess is its the same issue as Racy, so will try installing your patch in a short while.

I installed the hplip and hpscan packages from the first post of this thread on a fresh copy of Lucid 5.28-004. My printer is a wireless HP Photosmart D110. I am able to print a test page from CUPS. However I am not able to use the scanner on this model.

I installed Peasyscan 1.8. I renamed and copied the sample configuration file to the appropriate folder. Using your example from the first post I edited the device uri. Peasyscan will attempt to start a scan but will always fail. The error message is consistently "invalid argument" for the uri.

I am left to assume that I have used incorrect syntax. I listed the printer make/model and used the device uri from the above file. Can you make a suggestion regarding the device uri and how it is entered into the Peasyscan configuration file?

So presumably that is where the 60481 is coming from - do I have a means of changing that? I would at least like 600dpi to be available.

Thanks - Paul

I looked at this with my Epson NX625 and epkowa. Its --resolution numbers are 75,300,1200,2400. Its --x-resolution and --y-resolution numbers are both 75,150,300,600,1200,2400.

When I run regular Peasyscan, I just get the --resolution numbers. But if I enable Preferences > Advanced Options, I get access to the --x and --y numbers. When I pick the latter, Peasyscan appears to scan using those values.

Did you ever try downgrading to the older "epson" backend? It might give you more reliable numbers.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum