Re: [SLE] epson rx620

On Fri December 30 2005 7:28 am, Johannes Meixner wrote:
> Hello,
>
> On Dec 30 07:15 Richard wrote (shortened):
> > I have the RX600: printing is fine, but woe to the scanner.
> > It is found and installed by YAST, but it not seen by Kooka, Sane.
>
> What do you mean with "It is found and installed by YAST"?
> What do you mean with "it not seen by Kooka, Sane"?
> I don't have a RX600 and I'm not sitting in front of your computer.
> I cannot know what you did and what messages you have seen.
>
> Verify if it is a duplicate of
> https://bugzilla.novell.com/show_bug.cgi?id=141079
>
> Regarding "Trouble-Shooting (Debugging)" see
> http://portal.suse.com/sdb/en/2004/10/jsmeix_scanner-setup-92.html
>
>
> Kind Regrads
> Johannes Meixner
> --
> SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@xxxxxxx
> 90409 Nuernberg, Germany WWW: http://www.suse.de/

Well, let's see: click on "K Menu", the little icon of the smiling green
SuSE, click on "System", click on "Control Center (YAST)", enter root
password at the prompt, (doing ok so far??). When YAST Control Center opens,
click on "Hardware", then click on "Scanner". Scanner configuration window
opens with first line reading "Not Configured" under Driver, and under
Scanner, the line: "USB Scanner (vendor=0x041e, product=0x401c) at
libusb:002:002". Now being only a simple student of the English language and
not fully versed (truth be known, only barely versed) in programming-speak, I
interpreted this to mean that YAST found a USB scanner that it could identify
by maker and model and location, so I reported earlier that YAST found it. I
understood the phrase "Not Configured" to mean that it could still not be
used yet, even though it was found. I clicked on the line and clicked on
"Edit" below. This, as I am sure you will verify, opens up a Scanner Model
Selection window. Descending through the list of models I located the line
"Epson Stylus Photo RX600 (which seemed hauntingly reminiscent of both the
model I purchased and the label on the front of the model) : Driver epkowa
(package iscan) provides complete functionality. [overseas version of the
PM-A850, all-in-one]" I highlight this entry, click on "Next" below, and am
then presented with a dialogue box stating, "Possibly Problematic Driver The
epkowa driver may cause problems on 64-bit architectures. See our support
base for details." I then click the "Ok" box, that being the only option
open. This continues with the window "Setting up the driver Epkowa " which
shows all six steps checked, the progress bar completely filled and
displaying "100%". So from this response I said earlier, "...and installed
by YAST." It looked to me like that was what had happened and, as I said, I
am only a simple student of basic English. I then clicked "Next", returning
to the "Scanner Configuration" window, to be presented with the original
entries, no changes, no change to the line indicating Not configured under
Driver. However, a second line appears now: under Driver, "epkowa", and
under scanner, "No active scanner for this driver". While it seemed strange
that all the setup lines were checked as completed and that a scanner had
been apparently found, that this should be so. I highlight the epkowa line,
click "Edit" and get the box, "Edit Not Possible It is only possible to
delete a driver without a matching scanner". Bummer. Seems the driver can't
be changed unless it does not have a scanner which it also does not have. At
this point I am beginning to think I am reading from 1040 tax form directions
and "explanations". Time to go. Click "OK" and "Finish". A "Setting up the
Scanner Configuration" window flashes with a single check at "Saving the
Environment". Does not feel good but I say, why not try to open anyway? I
return to "K Menu", "Graphics", "Scanning". This opens Kooka, apparently by
default, but no scanner dialogue. Click on "Settings", "Select Scan Device"
and the box only closes. So I reported, "It is not seen by Kooka..." That
seemed fairly evident, and probably to be expected from the equivocal results
of the YAST experience. So I opened a console window, entered, "xscanimage"
and received the reply, "[xscanimage] No scanners were identified. If you
were expecting something
different, check that the scanner is plugged in, turned on and
detected by sane-find-scanner (if appropriate). Please read
the documentation which came with this software (README, FAQ,
manpages)." So I had earlier reported, "...[not seen by]...sane".
I thought this was a reasonable deduction and supported by my middling use of
English.
Output of /usr/sbin/lsusb (suggested in YAST) does not list the scanner by
name so I can guess that recognizing it is still in doubt. For that matter
it does not list the same printer by name either and that works just fine.
While I appreciate what I suspect is a genuine desire to help, frankly I did
not ask for it and I was a little dismayed by the seeming tone of irritation
on your part. Perhaps I was reading too much into it. Had I been searching
for assistance I would have given all the info just supplied. I was merely
answering the original poster's request for another's experience. That was
mine. I do want to get my scanner working at some point and will pursue the
bugzilla and trouble-shooting suggestions you included and which I
appreciate. At the moment, installing a built-in dishwasher which I got my
wife for Christmas (an absolutely foolish move which my advanced years and
supposed wisdom should have warned me about) is a far higher priority. Or
maybe finding her "Mute" button would help and give me more time to do what I
want to do.

Richard

--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@xxxxxxxx