Epson Perfection Scan V350 not recognized. (SOLVED)

[Snapshot]

I recently had to re-install PCLOS and now I can't get my scanner recognized. I've installed the current packages from the repository with no luck and I've downloaded and installed all of the current software from Epson. No matter what I try or do the scanner isn't recognized. This was and or has been a problem before but the last time it happened the problem was fixed by installing Epson software iscan-data-1.9.0-1.noarch which is now v. 1.15.0-2.noarch.rpm. I got no errors after installation and both of the two required Epson packages are installed. I've tried previous and current versions of the packages and my scanner is plugged in to power and USB port. I even switched USB ports to make sure it wasn't the port.

My system is a AMD dual core 64bit processor with 4GB ram and a Nvidia GForce 9400 graphics card and 32 bit PCLOS which is up to date.

Thanks.

[djohnston]

Did you get a drivers CD with that scanner? You may need a firmware file. I don't know for sure. Please see this post about an Epson Perfection 660.

If you don't have a CD, I'm not sure where to get the drivers. The file you need is very small. But, I don't see your scanner model # listed on Epson's support page.

[Snapshot]

I don't have the scanner cd but all the software is available for free download at the Epson/Avasys/Seiko website and I've obtained the required drivers and miscellaneous software that Epson states that you need. This problem has occurred every time I've installed or re-installed PCLOS but I've always been able to overcome it after much time and effort until now. I'll check out the post about the Perfection 660 and see if I can get help there. Thanks.

[Snapshot]

In the thread on the Epson 660, it was recognized from the beginning but my V350 isn't even recognized by PCC. If I do "lsusb" I get the following result:

root@localhost snapshot]# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser

The scanner simply isn't there. Unlike the post about the Epson 660, I can run XSane but I get the message that no device found. I've tried every version of the Epson software that I had a year ago and the current versions yet the scanner isn't recognized. I've used the IScan packages in Synaptic (tried that first) yet still nothing.

Thanks for your reply.

[Snapshot]

Did you get a drivers CD with that scanner? You may need a firmware file. I don't know for sure. Please see this post about an Epson Perfection 660.

If you don't have a CD, I'm not sure where to get the drivers. The file you need is very small. But, I don't see your scanner model # listed on Epson's support page.

I found the scanner CD but since it's for Windows how can it be applied here?  Thanks.

[djohnston]

I found the scanner CD but since it's for Windows how can it be applied here?  Thanks.

Don't know if I can help you without a link to the CD you found.

[Snapshot]

That's disappointing but thanks anyway.

[djohnston]

Are you saying you cannot provide a link to the CD?

EDIT: Backing up towards the front of this thread, I overlooked something. If lsusb doesn't show the scanner, that's a key point. The device has to be registered on the bus, or fiddling with drivers and configuration won't solve anything. You might try disconnecting the USB cord, powering off the scanner, powering it back on, then reinserting the USB cable. You say you've tried all your USB ports. If still nothing, I would suspect a faulty USB cable.

[Snapshot]

DJ you have a good point but in the past the scanner has never been "seen" by the usb port it's plugged in to until everything is configured. I'd always get the same message that no scanner was recognized. I tried switching cables with one that works and I powered down the scanner then powered up and plugged in the usb cable but still nothing. Although it has been awhile since I last used the scanner it worked before re-installing PCLOS this time. Opening PCC and trying to set up the scanner gave me the message that no device was found on this system. I found a configuration/installation from Epson that I'm going to attempt to use before I give up. For the amount of time and trouble I've had to endure I'm at a point where it's becoming too frustrating to continue. If my next attempt fails I'm going to forget it and eventually buy something that will work. As far as a link to the CD goes, I'm not sure what you mean. I have the CD and I've downloaded all the necessary/required files that are needed to install the scanner. The CD is far outdated by 3 or more years whereas the d/l software is current and specifically for Linux and the CD is Windows only. I'm not trying to negate your suggestions I'm merely stating what I've done without success. I knew that when I had to re-install PCLOS I was going to have this problem and put off doing it as long as I could. Thanks .

[djohnston]

DJ you have a good point but in the past the scanner has never been "seen" by the usb port it's plugged in to until everything is configured. I'd always get the same message that no scanner was recognized. I tried switching cables with one that works and I powered down the scanner then powered up and plugged in the usb cable but still nothing. Although it has been awhile since I last used the scanner it worked before re-installing PCLOS this time. Opening PCC and trying to set up the scanner gave me the message that no device was found on this system.

Okay, I understand that PCC and Xsane may give an error message that there is no scanner. That is a setup and configuration thing. lsusb could show the scanner attached to a USB port, and PCC and Xsane say there is no recognized scanner, because the manufacturer name and model number are not in the configuration list. But, the lsusb command has nothing to do with whether or not the scanner is set up and ready to use. The lsusb command simply lists the hardware that is plugged into the bus. It doesn't make sense that the device will suddenly show up on the USB data bus after applying a driver. The driver has to have a recognized device already on the data bus to configure. If you're sure that the hardware is not at fault, then there is some other reason why the scanner doesn't show up as a hardware device. Do you have other USB devices you can plug into those ports to rule out the ports and the software that's installed to detect what's plugged into the ports?

I have the CD and I've downloaded all the necessary/required files that are needed to install the scanner. The CD is far outdated by 3 or more years whereas the d/l software is current and specifically for Linux and the CD is Windows only. I'm not trying to negate your suggestions I'm merely stating what I've done without success. I knew that when I had to re-install PCLOS I was going to have this problem and put off doing it as long as I could. Thanks.

Okay, you evidently found the CD that came with the scanner or you got one from somewhere other than the internet. You had originally said you have no drivers CD. The software mentioned in the other Epson scanner thread also came from a "Windows only" installation package. But, if you found newer drivers, specifically for Linux, then so much the better. What I'm getting at is that the hardware, regardless of whether it has available drivers yet, has to be recognized on the USB data bus before it can be set up. An analogy would be like trying to format a hard drive that the system doesn't show as being attached.

[Snapshot]

I understand your analogy but what I'm saying is that previous attempts to recognize this scanner have resulted in exactly the same problem; the scanner isn't recognized until I've gotten the software installed. While I know this defies logic or technology it's a fact. This scanner has never been recognized as a USB device as soon as it's plugged in. How this can be is beyond my understanding or ability to explain. Right now I'm shopping for a suitable replacement. As much as I hate to admit defeat I'm getting nowhere with this scanner and I think it's time to cut my losses and move on. Having said that should I mark this topic SOLVED, delete it or leave it open?

Thank you for the time you've put into it and for trying to solve this problem. If you have any other ideas in the next day or two, tell me. I probably won't order a new one until I've found a good one for Linux.

[djohnston]

No, really no other ideas unless you've got a link to the newer Linux drivers you downloaded. Or do you already know how to install them?

[Snapshot]

I know how to and have installed rpm packages before including all of the current Epson packages necessary for this device. I think this scanner doesn't like me or at least it doesn't like PCLOS as I've stated before this is an ongoing problem. None of this makes any sense at all and is obviously stressing me out. Here is the link for the current drivers and related files:  http://www.avasys.jp/lx-bin2/linux_e/scan/DL1.do

[djohnston]

Snapshot,

Believe me, I understand your frustration. Went through a similar situation a couple of years ago with an HP scanner that was previously supported. Found a temporary (unorthodox) workaround. Another forum member pointed out a slight discrepancy with some symlinks when the PCLinuxOS scanner software was installed. Texstar made a note of it and fixed the problem on the next round of updates.

1. On that page you're pointing to, have you clicked the Test Result for scanner drivers link? What were the results?
2. I picked PCLinuxOS - 2010 - USA. What did you pick for the last option? Individuals(Documents) or Individuals(Graphic/Image)?

 

[Snapshot]

I did the same as you did but I think I used documents instead of graphics. In the drivers test results I don't see PCLOS being tested. Right now I'm going back and installing the packages all over again because I had 1.15 instead of 1.13 installed and it appears that one of the required packages wasn't installed. When I tried to install I got a conflict message and had to uninstall that file from Synaptic. It is now installing. I'll report back when done.