Has anybody any experience of the Epson RX620 printer/scanner? It's pretty new so it doesn't show in the linuxprinting d/b. Suse d/b shows rx600 as problematic. Google shows some pages saying it's fine. So it would be nice to hear from somebody with personal experience :) Oh, I'm running Suse 9.3 on an Athlon64 if it's relevant. Thanks, Dave
On Fri December 30 2005 5:31 am, Dave Howorth wrote:
Has anybody any experience of the Epson RX620 printer/scanner?
It's pretty new so it doesn't show in the linuxprinting d/b. Suse d/b shows rx600 as problematic. Google shows some pages saying it's fine. So it would be nice to hear from somebody with personal experience :)
Oh, I'm running Suse 9.3 on an Athlon64 if it's relevant.
Thanks, Dave
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. So far I have not had to crying need to make it work but I know the time is coming. What is an annoyance now will be a crisis then. No help beyond this. I am running 10.0, Athlon 64. Richard
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@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
On Fri, 2005-12-30 at 16:28 +0100, 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.
Hey Johannes, that was pretty harsh on a poor guy who was only trying to give information to help me. I do agree that if he would like some help to fix his scanner, it would be sensible to post more information. Richard, thanks for letting me know your experience. I appreciate it. Anyway, I've bought an RX620 so I'll no doubt be back to ask for help and/or let you all know that it worked :) Cheers, Dave
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@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
* Dave Howorth <Dave.Howorth@acm.org> [12-30-05 13:54]:
Hey Johannes, that was pretty harsh on a poor guy who was only trying to give information to help me. I do agree that if he would like some help to fix his scanner, it would be sensible to post more information.
You berate a *knowledgable* individual (a suse employe) who is making an effort (on HIS own time) to help and full quote including old sigs. Best you accept help graciously and remain quiet with the rest until YOU learn the ways, yourself. http://www.netmeister.org/news/learn2quote.html -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2
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@suse.de 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
On Saturday 31 December 2005 00:54, Richard wrote:
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.
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-se tup-92.html
Well, let's see: click on "K Menu", the little icon of the smiling green SuSE, click on "System",
Don't know whether this is the main bit of the thread but there are Epson drivers here: http://www.avasys.jp/english/linux_e/DL1_spc_e.html
Hello, On Dec 30 15:54 Richard wrote (shortened):
When YAST Control Center opens ... 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".
The vendor ID is strange. If you have an "Epson" scanner, the vendor ID should be 0x04b8 (see below). I don't know which vendor 0x041e is.
I interpreted this to mean that YAST found a USB scanner that it could identify by maker and model and location ... I understood the phrase "Not Configured" to mean that it could still not be used yet, even though it was found.
Exactly. The reason is that any USB device can be identified on the USB (there are USB strandards which are used to do this), but this does neither mean that there exists a suitable driver for this device nor does it mean that even if there exists a suitable driver, the driver can be automatically activated.
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.
This shows one example why USB device detection neither means that there exists a suitable driver for this device nor that a suitable driver can be automatically activated. The "Epson Stylus Photo RX600" may be internally different than your scanner so that the RX600 driver may not work at all for your scanner.
... presented with a dialogue box stating, "Possibly Problematic Driver The epkowa driver may cause problems on 64-bit architectures.
Do you have a 64-bit architecture (e.g. an AMD 64-bit CPU)? If yes, see http://portal.suse.com/sdb/en/2005/03/jsmeix_scanner-setup-93.html http://portal.suse.com/sdb/en/2005/09/jsmeix_scanner-setup-100.html
... continues with the window "Setting up the driver Epkowa " which shows all six steps checked, the progress bar completely filled and displaying "100%".
This shows that "Setting up the driver Epkowa" was successful. This does neither mean that this driver will work for your scanner nor does it mean that it will actually work even for a RX600 - the usual example for this case are problems in the USB system - see http://portal.suse.com/sdb/en/2004/10/jsmeix_scanner-setup-92.html which other layers have to work so that an activated driver will actually work.
... returning to the "Scanner Configuration" window ... 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".
This shows exactly what actually had happened on your system. The driver "epkowa" was successfully activated but this driver cannot find your scanner and therefore your scanner is still not ready to be used. If the driver cannot find your scanner, it is normally useless to try any normal scanning frontend like scanimage, xscanimage, xsane or kooka - except you use the epkowa driver on a 64-bit architecture, see http://portal.suse.com/sdb/en/2005/03/jsmeix_scanner-setup-93.html
Output of /usr/sbin/lsusb (suggested in YAST) does not list the scanner by name
Don't care too much about the USB model name strings. Those depend on what the manufacturer has built-in into the model. Sometimes the built-in model name strings are more or less meaningless like "Epson scanner". Therefore the crucial information is the hexadecimal USB manufacturer and model IDs (something like vendor=0x041e, product=0x401c). If your scanner is really compatible with the RX600 (or with any other model which works with the epkowa driver), it should be sufficient to explicitely tell the epkowa driver that it should recognize your scannre's USB IDs. See http://portal.suse.com/sdb/en/2004/10/jsmeix_scanner-setup-92.html "SANE Backends" ------------------------------------------------------------------- Normally, a backend automatically detects the USB scanners it supports. If this does not happen, it should be possible to add a line such as the following in /etc/sane.d/backend.conf: usb 0xVVVV 0xMMMM Based on the output of "lsusb", enter the hexadecimal vendor ID for 0xVVVV and the hexadecimal model ID for 0xMMMM. For certain backends the syntax "usb 0xVVVV 0xMMMM" may be different or not available at all, see the man page for the respective backend. ------------------------------------------------------------------- See "man sane-epkowa" and in particular see /etc/sane.d/epkowa.conf ------------------------------------------------------------------- # For any USB scanner not known to the backend (yet), you may, # at your own peril(!!), force the backend to recognise and use # it via libusb. # You can do so by the following configuration command: # # usb <USB vendor ID> <USB product ID> # # SEIKO EPSON's USB vendor ID is '0x04b8' (without quotes). ------------------------------------------------------------------- Note the "at your own peril(!!)" above! According to http://www.sane-project.org/cgi-bin/driver.pl?manu=epson&model=620&bus=any the RX620 works with the epkowa driver since version 1.1.17. On the Suse Linux 10.0 CDs there is version 1.1.15. If the above entry in /etc/sane.d/epkowa.conf doesn't work, you would neeed the iscan (or iscan-free) package version 1.1.17, see http://portal.suse.com/sdb/en/2005/09/jsmeix_scanner-setup-100.html and ftp://ftp.suse.com/pub/people/jsmeix/unsupported/iscan/10.0/RPMS/ Note the "unsupported" and read the README in the directory.
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.
My reply was not meant harsh. But it is always short and straightforward. I think it is the typical German way of communication ;-) I sift through a few hundred mails each day (regardless that I use additionally automated mail scanning "procmail" rules) and therefore I must answer either straightforward or I would have to unsubscribe from some mailing-lists. Because of this I often do not follow a whole mail thread but when I pick up a mail which is interesting for me, I answer this one mail. I hope the difference in my answer has become obvious depending on how much hard facts are provided in a mail. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
On Mon, 2006-01-02 at 11:03 +0100, Johannes Meixner wrote:
On Dec 30 15:54 Richard wrote (shortened):
When YAST Control Center opens ... 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".
The vendor ID is strange. If you have an "Epson" scanner, the vendor ID should be 0x04b8 (see below). I don't know which vendor 0x041e is.
according to http://www.linux-usb.org/usb.ids 041e = Creative 401c = WebCam NX Ultra ?! I think Richard must have misread the list. FYI, my RX620 shows up like this at present: T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 17 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=04b8 ProdID=0811 Rev= 1.00 S: Manufacturer=EPSON S: Product=USB2.0 MFP(Hi-Speed) S: SerialNumber=L72030505281007210 C:* #Ifs= 3 Cfg#= 1 Atr=c0 MxPwr= 2mA I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms I: If#= 1 Alt= 0 #EPs= 2 Cls=07(print) Sub=01 Prot=02 Driver=usblp E: Ad=04(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=85(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms I: If#= 2 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage E: Ad=07(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=88(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
According to http://www.sane-project.org/cgi-bin/driver.pl?manu=epson&model=620&bus=any the RX620 works with the epkowa driver since version 1.1.17. On the Suse Linux 10.0 CDs there is version 1.1.15. If the above entry in /etc/sane.d/epkowa.conf doesn't work, you would neeed the iscan (or iscan-free) package version 1.1.17,
FWIW, the scanner files I downloaded from Avasys for the RX620's scanner appear to be much later (or is there a numbering change?): iscan-1.17.0-1.c2.i386.rpm iscan-1.17.0-1.c2.tar.gz userg_revG_e.pdf Thanks very much for this posting Johannes. It will be very useful to me when I come to set up the scanner. Chees, Dave
Hello, On Jan 2 11:45 Dave Howorth wrote (shortened):
On Mon, 2006-01-02 at 11:03 +0100, Johannes Meixner wrote:
According to http://www.sane-project.org/cgi-bin/driver.pl?manu=epson&model=620&bus=any the RX620 works with the epkowa driver since version 1.1.17. On the Suse Linux 10.0 CDs there is version 1.1.15.
FWIW, the scanner files I downloaded from Avasys for the RX620's scanner appear to be much later (or is there a numbering change?): iscan-1.17.0-1.c2.i386.rpm iscan-1.17.0-1.c2.tar.gz
Oops! A typo of mine. The right version numbers are 1.15.x and 1.17.x Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
Just to let you know that I have got the scanner on my RX620 working without much trouble. This mail is mainly ... a BIG thank you to Johannes Meixner ... for his help on the list and for the excellent printing and scanning guides on the Suse portal. For the record here's what I did. I'm running Suse 9.3 on an Athlon 64: uname -a Linux piglet 2.6.11.4-21.10-default #1 Tue Nov 29 14:32:49 UTC 2005 x86_64 x86_64 x86_64 GNU/Linux I Checked in YaST that sane was installed (packman 1.0.17-0.pm.0) and sane-32 (SUSE 9.3-7) I checked that the scanner could be detected: sane-find-scanner -v -v which said (amongst lots of other stuff): found USB scanner (vendor=0x04b8 [EPSON], product=0x0811 [USB2.0 MFP(Hi-Speed)]) at libusb:001:003 I installed Johanne's test iscan from ftp://ftp.suse.com/pub/people/jsmeix/unsupported/iscan/9.3/RPMS/: rpm -i iscan-free-1.17.0.1-1.1.x86_64.rpm I uncommented "epkowa" in /etc/sane.d/dll.conf. And it worked! At this point scanimage could see the scanner: scanimage -L device `epkowa:libusb:001:002' is a Epson Stylus Photo RX620/RX630 flatbed scanner And I'm able to access the scanner with xsane. Once again, huge thanks, Johannes. Cheers, Dave
I wrote:
Anyway, I've bought an RX620 so I'll no doubt be back to ask for help and/or let you all know that it worked :)
I thought I'd give an update of what I've found so far: PRINTING PHOTOS --------------- The first thing I did was to try printing from the SD-card from my Nikon Coolpix 7900. The good news is that I succeeded in printing a photo. The bad news is that it didn't show me all the pictures on the card and it did show me some that I'd deleted! Plus the colour wasn't very good. I looked on the Epson web site but didn't find a solution, so I've asked Epson about the missing pictures and will reserve judgment on the colour until I've got everything set up. Later note. Once the printer is connected to the computer, the SD card is automounted by Suse when I put it in the printer's slot and I see the correct photos on the computer but still the wrong ones on the printer. So my SWAG is that there's something wrong with Epson's filesystem implementation. PRINTING FROM SUSE ------------------ (1) There's a nice link here: http://www.linuxforum.com/forums/index.php?s=90bded507a9d366a0bf15abe733140ca&showtopic=155538&st=0&#entry675463 (2) Epson provide Linux drivers via Avasys: http://www.avasys.jp/english/linux_e/dl_spc.html and here's a link to a list of OS versions they've tested: http://www.avasys.jp/english/linux_e/spc_match_e.html (3) Epson has a support site with specific Linux FAQs and tutorials. Search the support section of their local site or perhaps try http://esupport.epson-europe.com/ if you live in the UK. (The FAQ and Tutorials are the same thing!) What I've done so far: (1) Download the avasys CUPS drivers (2) Check CUPS was installed (3) Install the avasys rpm: rpm -i pips-sprx620_630s-cups-2.6.2-1.i386.rpm (4) Go into YAST printers. Select printer type SPRX620_630S from Epson list. (5) Test print failed (printer does nothing). Exit YAST printer page. (6) kill -HUP `pidof cupsd` (7) cups died! So /etc/init.d/cups restart (8) Repeat steps 4 & 5 :( (9) Try to add printer via CUPS web page following Epson's readme-sprx620_630s-cups (man lppasswd if you can't remember how to login to CUPS :) (10) "EPSON Inkjet Printer #1 (Photo Image Print System)" doesn't appear as an option for "device", so I chose "USB Printer #1 (EPSON Stylus Photo RX620)" instead. (11) CUPS says printer is successfully added. (12) Try to print test page. Same result as YaST - nothing happens. (13) Use the CUPS web page to delete the printer (13) Try Epson's recommended lpadmin command-line: /usr/sbin/lpadmin -p sprx620_630s -E -v ekplp:/var/ekpd/ekplp0 -m eksprx620_630s.ppd Result is: lpadmin: add-printer (set device) failed: client-error-not-possible (14) Look on Epson web site. There's a 'tutorial' called 'Why when I tried to test my Epson printer by ‘cat. cshrc > /dev/lp0' nothing prints?' but the command they suggest doesn't terminate. I do discover /etc/ekpdrc and the ekpd process along the way... (15) ... and when I try cat .bashrc > /dev/usb/lp0 IT ACTUALLY PRINTS !!! (16) BUT I STILL CAN'T PRINT FROM ANY APPLICATION. I haven't given up yet (I've been recovering from a New Year party today :) but if anybody has any thoughts, they'd be welcome. I tried the scanner stand-alone (to copy a page) but haven't tried it with Suse yet. Oh, yeah, Suse 9.3 + packman. Athlon64, MSI K8M Neo-V. Happy New Year, Dave
On Sun, 2006-01-01 at 19:08 +0000, Dave Howorth wrote:
I wrote:
Anyway, I've bought an RX620 so I'll no doubt be back to ask for help and/or let you all know that it worked :)
I thought I'd give an update of what I've found so far:
I've tried again today to make it work but have made no progress. The basic situation is that both Yast and CUPS claim the printer is configured and I can print raw text to it (cat some-file > /dev/usb/lp0) but when I try to print from an application or use Yast or CUPS test print they all think the print has finished but the printer does nothing. I won't repeat all the info from my post yesterday but if anybody has any suggestions on how to debug CUPS/USB printers/Epson printers I'd really appreciate any hints. Thanks, Dave
On Mon January 2 2006 8:26 am, Dave Howorth wrote:
On Sun, 2006-01-01 at 19:08 +0000, Dave Howorth wrote:
I wrote:
Anyway, I've bought an RX620 so I'll no doubt be back to ask for help and/or let you all know that it worked :)
I thought I'd give an update of what I've found so far:
I've tried again today to make it work but have made no progress.
The basic situation is that both Yast and CUPS claim the printer is configured and I can print raw text to it (cat some-file > /dev/usb/lp0) but when I try to print from an application or use Yast or CUPS test print they all think the print has finished but the printer does nothing.
I won't repeat all the info from my post yesterday but if anybody has any suggestions on how to debug CUPS/USB printers/Epson printers I'd really appreciate any hints.
Thanks, Dave
At the risk of putting my neck on the chopping block...I seem to recall some problems with this some time back, not necessarily with this printer. Seems there was a problem with having both lp and CUPS running at the same time, and isn't there a message at install about not having both lprng and CUPS running at once?, that only one will run? Perhaps someone with more knowledge of this possible "conflict" can clear this up. Richard
On Mon, 2006-01-02 at 14:15 -0800, Richard wrote:
At the risk of putting my neck on the chopping block...I seem to recall some problems with this some time back, not necessarily with this printer. Seems there was a problem with having both lp and CUPS running at the same time, and isn't there a message at install about not having both lprng and CUPS running at once?, that only one will run? Perhaps someone with more knowledge of this possible "conflict" can clear this up.
I don't think this is it. I can't see any sign of lp or lprng. Thanks anyway, Dave
* Dave Howorth <Dave.Howorth@acm.org> [01-02-06 18:47]:
On Mon, 2006-01-02 at 14:15 -0800, Richard wrote:
At the risk of putting my neck on the chopping block...I seem to recall some problems with this some time back, not necessarily with this printer. Seems there was a problem with having both lp and CUPS running at the same time, and isn't there a message at install about not having both lprng and CUPS running at once?, that only one will run? Perhaps someone with more knowledge of this possible "conflict" can clear this up.
I don't think this is it. I can't see any sign of lp or lprng.
You should. lp is installed by cups-client and necessary. lprng *is* a different printing system and would conflict with cups, or bsdlp... -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2
On Mon, 2006-01-02 at 18:51 -0500, Patrick Shanahan wrote:
* Dave Howorth <Dave.Howorth@acm.org> [01-02-06 18:47]:
I don't think this is it. I can't see any sign of lp or lprng.
You should. lp is installed by cups-client and necessary. lprng *is* a different printing system and would conflict with cups, or bsdlp...
Sorry it's late and I'm not writing clearly again. You mean that /usr/bin/lp should be there? Yes, it is. I meant that when I grep running processes I don't see anything lp related (e.g. lpd), so I don't think there's an install conflict with daemons. Cheers, Dave
On Mon, 2006-01-02 at 16:26 +0000, Dave Howorth wrote:
On Sun, 2006-01-01 at 19:08 +0000, Dave Howorth wrote:
I wrote:
Anyway, I've bought an RX620 so I'll no doubt be back to ask for help and/or let you all know that it worked :)
I thought I'd give an update of what I've found so far:
I've tried again today to make it work but have made no progress.
The basic situation is that both Yast and CUPS claim the printer is configured and I can print raw text to it (cat some-file > /dev/usb/lp0) but when I try to print from an application or use Yast or CUPS test print they all think the print has finished but the printer does nothing.
Hmm, Murphy's been busy, or I'm getting frazzled. I just looked in the CUPS error log again and there is some output when Yast tries to do a test print: I [02/Jan/2006:16:31:46 +0000] Listening to 0:631 I [02/Jan/2006:16:31:46 +0000] Loaded configuration file "/etc/cups/cupsd.conf" I [02/Jan/2006:16:31:46 +0000] Configured for up to 100 clients. I [02/Jan/2006:16:31:46 +0000] Allowing up to 100 client connections per host. I [02/Jan/2006:16:31:46 +0000] Full reload is required. I [02/Jan/2006:16:31:48 +0000] LoadPPDs: Read "/etc/cups/ppds.dat", 3514 PPDs...I [02/Jan/2006:16:31:48 +0000] LoadPPDs: No new or changed PPDs... I [02/Jan/2006:16:31:48 +0000] Full reload complete. I [02/Jan/2006:16:31:50 +0000] Setting y2test device-uri to "usb://EPSON/Stylus%20Photo%20RX620" (was "file:/dev/null".) I [02/Jan/2006:16:31:50 +0000] Setting y2test printer-is-accepting-jobs to 1 (was 0.) I [02/Jan/2006:16:31:50 +0000] Setting y2test printer-state to 3 (was 5.) I [02/Jan/2006:16:31:50 +0000] Saving printers.conf... I [02/Jan/2006:16:31:50 +0000] New printer 'y2test' added by 'root'. I [02/Jan/2006:16:31:51 +0000] Adding start banner page "none" to job 17. I [02/Jan/2006:16:31:51 +0000] Adding end banner page "none" to job 17. I [02/Jan/2006:16:31:51 +0000] Job 17 queued on 'y2test' by 'root'. I [02/Jan/2006:16:31:51 +0000] Started filter /usr/lib64/cups/filter/texttops (PID 20231) for job 17. I [02/Jan/2006:16:31:51 +0000] Started filter /usr/lib64/cups/filter/pstops (PID 20232) for job 17. I [02/Jan/2006:16:31:51 +0000] Started filter /usr/lib64/cups/filter/pstoraster (PID 20233) for job 17. I [02/Jan/2006:16:31:51 +0000] Started filter /usr/lib64/cups/filter/rastertopips (PID 20234) for job 17. I [02/Jan/2006:16:31:51 +0000] Started backend /usr/lib64/cups/backend/usb (PID 20235) for job 17. E [02/Jan/2006:16:31:51 +0000] PID 20234 stopped with status 22! I [02/Jan/2006:16:31:51 +0000] Hint: Try setting the LogLevel to "debug" to find out more. I [02/Jan/2006:16:32:05 +0000] Printer 'y2test' deleted by 'root'. I [02/Jan/2006:16:32:05 +0000] Saving printers.conf... When I turn debug on, the resulting file is over 32000 lines, so I won't post it here :) But here's the section just before the error: ... I [02/Jan/2006:18:56:31 +0000] Job 17 queued on 'y2test' by 'root'. D [02/Jan/2006:18:56:31 +0000] Job 17 hold_until = 0 D [02/Jan/2006:18:56:31 +0000] StartJob(17, 0x77d860) D [02/Jan/2006:18:56:31 +0000] StartJob() id = 17, file = 0/1 D [02/Jan/2006:18:56:31 +0000] job-sheets=none,none D [02/Jan/2006:18:56:31 +0000] banner_page = 0 D [02/Jan/2006:18:56:31 +0000] StartJob: argv = "y2test","17","root","testpg.ascii","1","","/var/spool/cups/d00017-001" D [02/Jan/2006:18:56:31 +0000] StartJob: envp[0]="PATH=/usr/lib64/cups/filter:/bin:/usr/bin" D [02/Jan/2006:18:56:31 +0000] StartJob: envp[1]="SOFTWARE=CUPS/1.1" D [02/Jan/2006:18:56:31 +0000] StartJob: envp[2]="USER=root" D [02/Jan/2006:18:56:31 +0000] StartJob: envp[3]="CHARSET=iso-8859-15" D [02/Jan/2006:18:56:31 +0000] StartJob: envp[4]="LANG=en" D [02/Jan/2006:18:56:31 +0000] StartJob: envp[5]="PPD=/etc/cups/ppd/y2test.ppd" D [02/Jan/2006:18:56:31 +0000] StartJob: envp[6]="CUPS_SERVERROOT=/etc/cups" D [02/Jan/2006:18:56:31 +0000] StartJob: envp[7]="RIP_MAX_CACHE=8m" D [02/Jan/2006:18:56:31 +0000] StartJob: envp[8]="TMPDIR=/var/spool/cups/tmp" D [02/Jan/2006:18:56:31 +0000] StartJob: envp[9]="CONTENT_TYPE=text/plain" D [02/Jan/2006:18:56:31 +0000] StartJob: envp[10]="DEVICE_URI=usb://EPSON/Stylus%20Photo%20RX620" D [02/Jan/2006:18:56:31 +0000] StartJob: envp[11]="PRINTER=y2test" D [02/Jan/2006:18:56:31 +0000] StartJob: envp[12]="CUPS_DATADIR=/usr/share/cups"D [02/Jan/2006:18:56:31 +0000] StartJob: envp[13]="CUPS_FONTPATH=/usr/share/cups/fonts" D [02/Jan/2006:18:56:31 +0000] StartJob: envp[14]="CUPS_SERVER=localhost" D [02/Jan/2006:18:56:31 +0000] StartJob: envp[15]="IPP_PORT=631" D [02/Jan/2006:18:56:31 +0000] StartJob: statusfds = [ 14 17 ] D [02/Jan/2006:18:56:31 +0000] StartJob: filterfds[1] = [ 18 -1 ] D [02/Jan/2006:18:56:31 +0000] StartJob: filter = "/usr/lib64/cups/filter/texttops" D [02/Jan/2006:18:56:31 +0000] StartJob: filterfds[0] = [ 19 20 ] D [02/Jan/2006:18:56:31 +0000] start_process("/usr/lib64/cups/filter/texttops", 0x7ffffffec830, 0x7ffffffeba10, 18, 20, 17) I [02/Jan/2006:18:56:31 +0000] Started filter /usr/lib64/cups/filter/texttops (PID 9468) for job 17. D [02/Jan/2006:18:56:31 +0000] StartJob: filter = "/usr/lib64/cups/filter/pstops" D [02/Jan/2006:18:56:31 +0000] StartJob: filterfds[1] = [ 18 21 ] D [02/Jan/2006:18:56:31 +0000] start_process("/usr/lib64/cups/filter/pstops", 0x7ffffffec830, 0x7ffffffeba10, 19, 21, 17) I [02/Jan/2006:18:56:31 +0000] Started filter /usr/lib64/cups/filter/pstops (PID 9469) for job 17. D [02/Jan/2006:18:56:31 +0000] StartJob: filter = "/usr/lib64/cups/filter/pstoraster" D [02/Jan/2006:18:56:31 +0000] StartJob: filterfds[0] = [ 19 20 ] D [02/Jan/2006:18:56:31 +0000] start_process("/usr/lib64/cups/filter/pstoraster", 0x7ffffffec830, 0x7ffffffeba10, 18, 20, 17) I [02/Jan/2006:18:56:31 +0000] Started filter /usr/lib64/cups/filter/pstoraster (PID 9470) for job 17. D [02/Jan/2006:18:56:31 +0000] StartJob: filter = "/usr/lib64/cups/filter/rastertopips" D [02/Jan/2006:18:56:31 +0000] StartJob: filterfds[1] = [ 18 21 ] D [02/Jan/2006:18:56:31 +0000] start_process("/usr/lib64/cups/filter/rastertopips", 0x7ffffffec830, 0x7ffffffeba10, 19, 21, 17) I [02/Jan/2006:18:56:31 +0000] Started filter /usr/lib64/cups/filter/rastertopips (PID 9471) for job 17. D [02/Jan/2006:18:56:31 +0000] StartJob: backend = "/usr/lib64/cups/backend/usb"D [02/Jan/2006:18:56:31 +0000] StartJob: filterfds[0] = [ -1 19 ] D [02/Jan/2006:18:56:31 +0000] start_process("/usr/lib64/cups/backend/usb", 0x7ffffffec830, 0x7ffffffeba10, 18, 19, 17) I [02/Jan/2006:18:56:31 +0000] Started backend /usr/lib64/cups/backend/usb (PID 9472) for job 17. D [02/Jan/2006:18:56:31 +0000] ProcessIPPRequest: 11 status_code=0 E [02/Jan/2006:18:56:31 +0000] PID 9471 stopped with status 22! ... Haven't had time to look at this yet. Two things strike me as perhaps odd, but I don't know how the system works well enough to know whether they're significant: (1) /usr/lib64 everywhere but isn't some of the driver software 32-bit? (2) No mention of anything that looks like an Epson-specific filter or back-end? Also, I've rebooted in the meantime and notice that ekpd is no longer running. Thanks, Dave
Hello, On Jan 3 00:01 Dave Howorth wrote (shortened):
I've bought an RX620 ... The basic situation is that both Yast and CUPS claim the printer is configured and I can print raw text to it (cat some-file > /dev/usb/lp0) but when I try to print from an application or use Yast or CUPS test print they all think the print has finished but the printer does nothing.
When you do cat some-file > /dev/usb/lp0 you don't use the printing system at all. If the printer prints this way, it shows that the basic low-level data transfer via USB works. I.e. you know then that your USB system can send data to your printer (for example this would fail if wrong USB kernel modules are loaded or if USB kernel modules are missing). When you print from an application or do the YaST or CUPS test print, you use the full printing system. See http://portal.suse.com/sdb/en/2004/05/jsmeix_print-cups-in-a-nutshell.html how the CUPS printing system works.
CUPS error log ... I [02/Jan/2006:16:31:51 +0000] Started filter /usr/lib64/cups/filter/rastertopips (PID 20234) for job 17. ... E [02/Jan/2006:16:31:51 +0000] PID 20234 stopped with status 22!
I.e. the filter /usr/lib64/cups/filter/rastertopips stopped with an error. This filter is not included in any of the Suse Linux packages. As fas as I know this filter is part of the Epson Avasys driver. Because of "lib64" you have a 64-bit architecture. Does the Epson Avasys driver really work on 64-bit architectures? What does the Epson Avasys documentation say about non-i386 architectures? See for example http://portal.suse.com/sdb/en/2005/03/jsmeix_scanner-setup-93.html for an example about problems with a not-100%-free driver (iscan) on non-i386 architectures. I tested one Epson Avasys printer driver once on a i386 system and it shows that this software is somewhat broken-by-design: I set up a CUPS queue to print into a file but this nice proprietary driver didn't care how I had set up the queue. It simply spits out its printer specific binary stuff directly on my first USB printer (a real good PostScript printer) which printed tons of sheets with nonsense characters. On the other hand this indicates that their driver may work if the first USB printer is the right printer for their driver (e.g. when only one printer is connected to the system). Since a long time I had desribed in detail in http://portal.suse.com/sdb/en/2003/11/jsmeix_print-info-for-manufacturers.ht... which conditions a driver software must meet so that we can integrate it into our products and the HP drivers show how successful such drivers can be. But we can neither itegrate the Epson Avasys printer driver into our products nor do we support broken-by-design software. Therefore you can only ask those who made this software how to use it on your (non-i386) system.
(1) /usr/lib64 everywhere but isn't some of the driver software 32-bit?
Right! As far as I know their proprietary library (which includes all what is really interesting of this driver) is only 32-bit and therefore it may not work in a 64-bit environment. Some details (assuming you have an AMD 64-bit (x86_64) system): On the one hand on x86_64 hardware 32-bit i386 software can work. But on the other hand 32-bit software requires 32-bit libraries. Only the kernel on x86_64 has a special interface to accept both 64-bit and 32-bit system calls. On x86_64 from user application down to the kernel interface (but excluding the actual kernel which is of course the same) 64-bit software and 32-bit software are totally seperated: 64-bit application -> 64-bit library -> 64-bit kernel interface 32-bit application -> 32-bit library -> 32-bit kernel interface Therefore you must either ask Epson Avasys for a 64-bit version of their driver or you must try to compile and link their driver only with 32-bit libraries. I don't know how their driver is linked with other libraries. If their 32-bit driver runs as a stand-alone 32-bit application it should work even on a 64-bit system. You can get rid of all 32-bit/64-bit problems when you simply install the 32-bit version of Suse Linux on your 64-bit system. This would be the same as if you install 32-bit Windows on your 64-bit system. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
On Tue, 2006-01-03 at 10:18 +0100, Johannes Meixner wrote:
Hello,
On Jan 3 00:01 Dave Howorth wrote (shortened):
I've bought an RX620 ... The basic situation is that both Yast and CUPS claim the printer is configured and I can print raw text to it (cat some-file > /dev/usb/lp0) but when I try to print from an application or use Yast or CUPS test print they all think the print has finished but the printer does nothing.
When you do cat some-file > /dev/usb/lp0 you don't use the printing system at all. If the printer prints this way, it shows that the basic low-level data transfer via USB works. I.e. you know then that your USB system can send data to your printer (for example this would fail if wrong USB kernel modules are loaded or if USB kernel modules are missing).
OK
When you print from an application or do the YaST or CUPS test print, you use the full printing system. See http://portal.suse.com/sdb/en/2004/05/jsmeix_print-cups-in-a-nutshell.html how the CUPS printing system works.
This looks useful - an expanded version of what's in the manual.
CUPS error log ... I [02/Jan/2006:16:31:51 +0000] Started filter /usr/lib64/cups/filter/rastertopips (PID 20234) for job 17. ... E [02/Jan/2006:16:31:51 +0000] PID 20234 stopped with status 22!
I.e. the filter /usr/lib64/cups/filter/rastertopips stopped with an error.
This filter is not included in any of the Suse Linux packages.
OK, that's useful information.
As fas as I know this filter is part of the Epson Avasys driver.
Because of "lib64" you have a 64-bit architecture. Does the Epson Avasys driver really work on 64-bit architectures? What does the Epson Avasys documentation say about non-i386 architectures?
I'll check tonight (I'm at work now).
See for example http://portal.suse.com/sdb/en/2005/03/jsmeix_scanner-setup-93.html for an example about problems with a not-100%-free driver (iscan) on non-i386 architectures.
I tested one Epson Avasys printer driver once on a i386 system and it shows that this software is somewhat broken-by-design: I set up a CUPS queue to print into a file but this nice proprietary driver didn't care how I had set up the queue. It simply spits out its printer specific binary stuff directly on my first USB printer (a real good PostScript printer) which printed tons of sheets with nonsense characters. On the other hand this indicates that their driver may work if the first USB printer is the right printer for their driver (e.g. when only one printer is connected to the system).
This would drive me mad if I was using it at work (I always go for netwok printers there), but you're right it's the only printer on my home PC.
Since a long time I had desribed in detail in http://portal.suse.com/sdb/en/2003/11/jsmeix_print-info-for-manufacturers.ht... which conditions a driver software must meet so that we can integrate it into our products and the HP drivers show how successful such drivers can be. But we can neither itegrate the Epson Avasys printer driver into our products nor do we support broken-by-design software.
Therefore you can only ask those who made this software how to use it on your (non-i386) system.
OK, I'll do that. And I'll ask the place where I bought it since they're the ones that will have to refund the money if it doesn't work! It sounds like a made a poor decision again. I'm throwing out an old HP Laserjet 3100 because it's a Linux paperweight. Epson appeared to be the optimal choice (http://www.linuxprinting.org/suggested.html). It sounds like you're not fond of them; would you recommend anything else? Or is it worth trying Gutenprint?
(1) /usr/lib64 everywhere but isn't some of the driver software 32-bit?
Right! As far as I know their proprietary library (which includes all what is really interesting of this driver) is only 32-bit and therefore it may not work in a 64-bit environment.
Some details (assuming you have an AMD 64-bit (x86_64) system):
Yes, I mentioned previously that I have an Athlon64, but I should have restated it so the message is freestanding.
On the one hand on x86_64 hardware 32-bit i386 software can work. But on the other hand 32-bit software requires 32-bit libraries. Only the kernel on x86_64 has a special interface to accept both 64-bit and 32-bit system calls. On x86_64 from user application down to the kernel interface (but excluding the actual kernel which is of course the same) 64-bit software and 32-bit software are totally seperated: 64-bit application -> 64-bit library -> 64-bit kernel interface 32-bit application -> 32-bit library -> 32-bit kernel interface
I understand this.
Therefore you must either ask Epson Avasys for a 64-bit version of their driver or you must try to compile and link their driver only with 32-bit libraries. I don't know how their driver is linked with other libraries. If their 32-bit driver runs as a stand-alone 32-bit application it should work even on a 64-bit system.
I guess I'm going to have to get to understand yet more infrastructure that I'll really like to be able to treat as a black box. It seems obvious that with the current mix of 32-bit and 64-bit systems, it makes sense to design a process boundary in between components with different origins. Isn't CUPS designed that way? Running multiple incompatible versions of libraries on systems is by no means a new problem. And I thought the whole point of having /usr/lib and /usr/lib64 was that dumb 32-bit software would automatically link to the right libraries. Now I guess I need to understand the build system.
You can get rid of all 32-bit/64-bit problems when you simply install the 32-bit version of Suse Linux on your 64-bit system. This would be the same as if you install 32-bit Windows on your 64-bit system.
That's a depressing thought. I'd like a box where my printer just works and my videos just play :) Thanks again, Dave
Hello, On Jan 3 14:55 Dave Howorth wrote (shortened):
is it worth trying Gutenprint?
Gutenprint is the successor of Gimp-Print but Gutenprint is not yet released (still in beta state). Now I did read what you posted in your earlier mail: http://www.linuxforum.com/forums/index.php?s=90bded507a9d366a0bf15abe733140ca&showtopic=155538&st=0&#entry675463 Therefore is seems the RX620 is compatible regarding printing (and perhaps even regarding scanning - see my other mail) with the RX600. If it is really compatible, you should be able to print with Gimp-Print in Suse Linux 9.3 out of the box with one of the following PPDs: /usr/share/cups/model/Epson/Stylus_Photo_RX600-gimp-print.ppd.gz "Epson Stylus Photo RX600 Foomatic/gimp-print (recommended)" /usr/share/cups/model/stp/escp2-rx600.ppd.gz "EPSON Stylus Photo RX600 - CUPS+Gimp-Print v4.2.7" Select the model RX600 in YaST and then you may have to use the [Edit] button to change the preselected PPD. The Gimp-Print driver may not produce the best possible photo quality but for normal printing it should be o.k. Additionally see http://www.linuxprinting.org/show_printer.cgi?recnum=Epson-Stylus_Photo_RX60...
64-bit application -> 64-bit library -> 64-bit kernel interface 32-bit application -> 32-bit library -> 32-bit kernel interface ... It seems obvious that with the current mix of 32-bit and 64-bit systems, it makes sense to design a process boundary in between components with different origins. Isn't CUPS designed that way? Running multiple incompatible versions of libraries on systems is by no means a new problem.
In fact there is no such problem. The linker knows whether to look for the libraries in ...lib... (for 32-bit applications) or in ...lib64... (for 64-bit applications). The only problem on 64-bit architecture is to have all necessary 32-bit libraries available in ...lib... so that the linker can link a 32-bit application with its required 32-bit libraries.
And I thought the whole point of having /usr/lib and /usr/lib64 was that dumb 32-bit software would automatically link to the right libraries.
Normally this works automatically. For example the proprietary binary-only 32-bit application "acroread" (the Adobe PDF Reader) runs well on the 64-bit AMD platform. It looks wrong when the Epson Avasys rastertopips filter is a 32-bit application but is stored in a ...lib64... directory on your system.
You can get rid of all 32-bit/64-bit problems when you simply install the 32-bit version of Suse Linux on your 64-bit system.
That's a depressing thought.
It was only meant as a possible test to prove that it is really a 32-bit versus 64-bit problem and/or as a last resource to get it working with the 32-bit Epson Avasys driver. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
On Tue, 2006-01-03 at 16:48 +0100, Johannes Meixner wrote:
Hello,
On Jan 3 14:55 Dave Howorth wrote (shortened):
is it worth trying Gutenprint?
Gutenprint is the successor of Gimp-Print but Gutenprint is not yet released (still in beta state).
Now I did read what you posted in your earlier mail: http://www.linuxforum.com/forums/index.php?s=90bded507a9d366a0bf15abe733140ca&showtopic=155538&st=0&#entry675463
Aah. Thanks for reminding me about that link :) I'd forgotten it :( And it was one of the factors in my decision to buy the RX620. Doh!
Therefore is seems the RX620 is compatible regarding printing (and perhaps even regarding scanning - see my other mail) with the RX600.
The link above says: "It's supported by Gutenprint, the driver name is "escp2-rx620". It's equivalent to the R300. There's also an RX600 driver in Gimp-Print 4.2.7." and the Avasys site has one print driver for Stylus Photo RX600/RX610 and a different one for Stylus Photo RX620/RX630. So I guess there's some difference but I don't know how much.
If it is really compatible, you should be able to print with Gimp-Print in Suse Linux 9.3 out of the box with one of the following PPDs: <snip details>
I'll give these a try, thanks. And maybe the Gutenprint RC. I'd prefer to use open software if it works reliably.
The only problem on 64-bit architecture is to have all necessary 32-bit libraries available in ...lib... so that the linker can link a 32-bit application with its required 32-bit libraries.
OK. I don't think there can be a missing library here otherwise I'd expect to see a link error at install or runtime (depending on whether the library is static).
It looks wrong when the Epson Avasys rastertopips filter is a 32-bit application but is stored in a ...lib64... directory on your system.
I'll see if I can find out whether it really is 32 or 64 bits, and whether there's something wrong with the install script.
It was only meant as a possible test to prove that it is really a 32-bit versus 64-bit problem and/or as a last resource to get it working with the 32-bit Epson Avasys driver.
Aah, OK. That's sensible if the other alternatives don't work quickly. You had me worried there for a time - I thought you were suggesting 64-bit wasn't ready for prime time :( Thanks, Dave
On Tue, 2006-01-03 at 00:01 +0000, Dave Howorth wrote:
I [02/Jan/2006:16:31:46 +0000] Listening to 0:631 I [02/Jan/2006:16:31:46 +0000] Loaded configuration file "/etc/cups/cupsd.conf" I [02/Jan/2006:16:31:46 +0000] Configured for up to 100 clients. I [02/Jan/2006:16:31:46 +0000] Allowing up to 100 client connections per host. I [02/Jan/2006:16:31:46 +0000] Full reload is required. I [02/Jan/2006:16:31:48 +0000] LoadPPDs: Read "/etc/cups/ppds.dat", 3514 PPDs...I [02/Jan/2006:16:31:48 +0000] LoadPPDs: No new or changed PPDs... I [02/Jan/2006:16:31:48 +0000] Full reload complete. I [02/Jan/2006:16:31:50 +0000] Setting y2test device-uri to "usb://EPSON/Stylus%20Photo%20RX620" (was "file:/dev/null".) I [02/Jan/2006:16:31:50 +0000] Setting y2test printer-is-accepting-jobs to 1 (was 0.) I [02/Jan/2006:16:31:50 +0000] Setting y2test printer-state to 3 (was 5.) I [02/Jan/2006:16:31:50 +0000] Saving printers.conf... I [02/Jan/2006:16:31:50 +0000] New printer 'y2test' added by 'root'. I [02/Jan/2006:16:31:51 +0000] Adding start banner page "none" to job 17. I [02/Jan/2006:16:31:51 +0000] Adding end banner page "none" to job 17. I [02/Jan/2006:16:31:51 +0000] Job 17 queued on 'y2test' by 'root'. I [02/Jan/2006:16:31:51 +0000] Started filter /usr/lib64/cups/filter/texttops (PID 20231) for job 17. I [02/Jan/2006:16:31:51 +0000] Started filter /usr/lib64/cups/filter/pstops (PID 20232) for job 17. I [02/Jan/2006:16:31:51 +0000] Started filter /usr/lib64/cups/filter/pstoraster (PID 20233) for job 17. I [02/Jan/2006:16:31:51 +0000] Started filter /usr/lib64/cups/filter/rastertopips (PID 20234) for job 17. I [02/Jan/2006:16:31:51 +0000] Started backend /usr/lib64/cups/backend/usb (PID 20235) for job 17. E [02/Jan/2006:16:31:51 +0000] PID 20234 stopped with status 22! I [02/Jan/2006:16:31:51 +0000] Hint: Try setting the LogLevel to "debug" to find out more. I [02/Jan/2006:16:32:05 +0000] Printer 'y2test' deleted by 'root'. I [02/Jan/2006:16:32:05 +0000] Saving printers.conf...
I've just taken another look. There is *no* /usr/lib64/cups/filter/rastertopips. There is a /usr/lib/cups/filter/rastertopips. The PPD file doesn't specify a path to the filter. How does CUPS decide whether a filter is 32-bit or 64-bit? It looks like CUPS reported that it's started a program that doesn't exist?! Also, I can't see any explicit exit from rastertopips.c that would return 22, so perhaps it's an EINVAL system error or a CUPS error code. What actually produces the debug messages? I'm beginning to suspect it must be a CUPS wrapper around the actual filter. Does cupsd fork and then exec the filter, perhaps? So it says it has started the filter when it actually hasn't? But if the exec failed, then EINVAL apparently means "An ELF executable had more than one PT_INTERP segment (i.e., tried to name more than one interpreter)", which doesn't sound right. I'd expect an ENOENT. Have I lost the plot? I'll poke around some more and see if I can answer my own questions. Cheers, Dave PS Epson aren't being at all helpful.
Hello, didn't it work with the included GimpPrint when you set it up as a RX600? On Jan 3 23:01 Dave Howorth wrote (shortened):
I [02/Jan/2006:16:31:51 +0000] Started filter /usr/lib64/cups/filter/rastertopips (PID 20234) for job 17. ... E [02/Jan/2006:16:31:51 +0000] PID 20234 stopped with status 22! ... I've just taken another look. There is *no* /usr/lib64/cups/filter/rastertopips. There is a /usr/lib/cups/filter/rastertopips. The PPD file doesn't specify a path to the filter.
Either add the full path to the filter in the cupsFilter line in the PPD file in /etc/cups/ppd/ or create a link /usr/lib64/cups/filter/rastertopips -> /usr/lib/cups/filter/rastertopips When the PPD doesn't specify the full path to the filter, cupsd assumes it is located in the CUPS default path. In any case make sure the user "lp" (this user runs the filters and the backend) can execute them.
How does CUPS decide whether a filter is 32-bit or 64-bit?
CUPS doesn't care which kind of executable a filter is. It can be a bash script or any other kind of executable file. The cupsd simply starts a process to execute it. If it is a dynamically linked binary then it is the linker which cares whether it is 32-bit or 64-bit.
PS Epson aren't being at all helpful.
Even if they are not helpful at the moment, it is crucial that many Linux users contact the manufacturers directly. Otherwise nothing changes, see http://portal.suse.com/sdb/en/2000/08/jsmeix_print-kompatibel.html "If your printer is not supported" By the way: See http://lists.suse.com/archive/suse-linux-e/2006-Jan/0392.html At least you are not the only one with problems on 64bit AMD with proprietary 32-bit-only drivers from manufacturers which claim to provide Linux support. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
On Wed, 2006-01-04 at 10:24 +0100, Johannes Meixner wrote:
didn't it work with the included GimpPrint when you set it up as a RX600?
I haven't had time to try GimpPrint yet. I'll see if Epson's driver works first - I think it almost does. Then I can compare them :)
On Jan 3 23:01 Dave Howorth wrote (shortened):
I [02/Jan/2006:16:31:51 +0000] Started filter /usr/lib64/cups/filter/rastertopips (PID 20234) for job 17. ... E [02/Jan/2006:16:31:51 +0000] PID 20234 stopped with status 22! ... I've just taken another look. There is *no* /usr/lib64/cups/filter/rastertopips. There is a /usr/lib/cups/filter/rastertopips. The PPD file doesn't specify a path to the filter.
Either add the full path to the filter in the cupsFilter line in the PPD file in /etc/cups/ppd/ or create a link /usr/lib64/cups/filter/rastertopips -> /usr/lib/cups/filter/rastertopips
OK, I'll try that. Hopefully that will fix it.
When the PPD doesn't specify the full path to the filter, cupsd assumes it is located in the CUPS default path.
Hmm, it seems like CUPS could be improved by allowing more than one default path. I think it would be difficult for the PPD as shipped to include the path since that will potentially vary on different systems (e.g. Windows). And requiring every installation script to be able to discover the default path on the particular machine and either edit the PPD or make a symlink also seems quite complicated. So IMHO it would be better if CUPS searched both /usr/lib64/cups/filter/ and /usr/lib/cups/filter/ to find filters.
In any case make sure the user "lp" (this user runs the filters and the backend) can execute them.
I'll check that.
PS Epson aren't being at all helpful.
Even if they are not helpful at the moment, it is crucial that many Linux users contact the manufacturers directly. Otherwise nothing changes, see http://portal.suse.com/sdb/en/2000/08/jsmeix_print-kompatibel.html "If your printer is not supported"
I've been asking them (Seiko Epson) to provide support. They already provide a Linux FAQ on their web site but their support line claims not to know about it. So I think there is probably some debate within the company already. If we make this driver work I'll also feed the info back to Epson Avasys.
By the way: See http://lists.suse.com/archive/suse-linux-e/2006-Jan/0392.html At least you are not the only one with problems on 64bit AMD with proprietary 32-bit-only drivers from manufacturers which claim to provide Linux support.
I think there was some confusion in that thread. Samsung don't claim that the 510N supports PS, only that the 550N does, AFAIK. As to why the 32-bit driver doesn't run, who knows :) Cheers, Dave
On Wed, 2006-01-04 at 11:21 +0000, Dave Howorth wrote:
On Wed, 2006-01-04 at 10:24 +0100, Johannes Meixner wrote:
didn't it work with the included GimpPrint when you set it up as a RX600?
I haven't had time to try GimpPrint yet. I'll see if Epson's driver works first - I think it almost does. Then I can compare them :)
BTW. I should just be able to set up another queue for GimpPrint with YaST, shouldn't I? That won't break an existing (hopefully) working driver. Thanks, Dave
Hello, On Jan 4 11:39 Dave Howorth wrote (shortened):
On Wed, 2006-01-04 at 11:21 +0000, Dave Howorth wrote:
On Wed, 2006-01-04 at 10:24 +0100, Johannes Meixner wrote:
didn't it work with the included GimpPrint when you set it up as a RX600?
I haven't had time to try GimpPrint yet. I'll see if Epson's driver works first - I think it almost does. Then I can compare them :)
BTW. I should just be able to set up another queue for GimpPrint with YaST, shouldn't I? That won't break an existing (hopefully) working driver.
Exactly. Setting up as many queues as you like or removing them does not change anything regarding how the software is installed. If you like to use different drivers for the same printer, you must set up several queues for the same printer. The usual examples are: - Use an older but small and fast working monochrome-only driver for fast black-and-white printouts and a modern driver-monster for best quality printouts. - Use an additional PCL driver for a PostScript+PCL printer because producing PCL on the host (with GHz CPU and GB memory) and then print the PCL raster-data results the printout much faster than let the printer itrself interpret complicated PostScript files. See for example: http://portal.suse.com/sdb/en/2003/06/jsmeix_print-cups-filters.html "Optional PCL Printing on PostScript+PCL Printers" Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
Hello, On Jan 4 11:21 Dave Howorth wrote (shortened):
On Wed, 2006-01-04 at 10:24 +0100, Johannes Meixner wrote:
didn't it work with the included GimpPrint when you set it up as a RX600?
I haven't had time to try GimpPrint yet.
If you did a standard installation, the Gimp-Print driver was installed by default (packages libgimpprint and cups-drivers-stp). Simply use YaST, the RX620 should be autodetected as USB printer, select in YaST the model RX600, perhaps you may have to use the [Edit] button to choose another PPD file and/or another model and then do the test-print in YaST. Note that when the wrong default media size (letter versus A4) is specified in the PPD, the imageable area on the test-print may be wrong. Use the [Edit] button to choose the correct media size setting. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
On Wed, 2006-01-04 at 12:51 +0100, Johannes Meixner wrote:
If you did a standard installation, the Gimp-Print driver was installed by default (packages libgimpprint and cups-drivers-stp). Simply use YaST, the RX620 should be autodetected as USB printer, select in YaST the model RX600, perhaps you may have to use the [Edit] button to choose another PPD file and/or another model and then do the test-print in YaST.
Good news: IT WORKS! Yeehaa! Took me about 30 seconds to set it up. Quality looks pretty good and printout almost exactly covers the entire page. Bad news: On the Avasys front, adding the symlink caused rastertopips to burst into life. But now it says: E [04/Jan/2006:20:18:32 +0000] PID 28499 stopped with status 1! D [04/Jan/2006:20:18:32 +0000] [Job 17] PPD file is broken. Cannot get option of PIPS.START 0 1584392 268444 1305920 20148 true 515 3 <0> I discovered cupstestppd (which doesn't seem to be documented?) and it says the PPD is valid (after a couple of what look like insignificant changes to me). So I guess I'll have to add some printfs to rastertopips to find out what it really thinks is wrong. But that seems less important than getting the scanner working now :) Big Thanks for your help Johannes! Dave
On Wed, 2006-01-04 at 11:21 +0000, Dave Howorth wrote:
Hmm, it seems like CUPS could be improved by allowing more than one default path.
I think it would be difficult for the PPD as shipped to include the path since that will potentially vary on different systems (e.g. Windows). And requiring every installation script to be able to discover the default path on the particular machine and either edit the PPD or make a symlink also seems quite complicated.
So IMHO it would be better if CUPS searched both /usr/lib64/cups/filter/ and /usr/lib/cups/filter/ to find filters.
Just a little more information on this topic, since I've dug a little deeper. The rpm defaulted to /usr/lib/cups/filter/ - I haven't looked at how it decided that. But I have now looked at what happens when you try to recompile the source package. It tries to discover the correct path using cups-config. That causes a problem because cups-config isn't installed by default; it's part of the cups-devel package. That's a fair enough requirement if you're recompiling the source, but IMHO it's unreasonable to require the devel package to be installed in order for a binary package to be able to install itself properly. So FWIW, I'm even more convinced that this is an issue that SUSE and/or CUPS ought to address rather than the driver supplier. Cheers, Dave
Hello, On Jan 5 17:19 Dave Howorth wrote (shortened):
... tries to discover the correct path using cups-config. That causes a problem because cups-config isn't installed by default
I filed an enhancement request for next Suse Linux version: https://bugzilla.novell.com/show_bug.cgi?id=142004 By the way: If you install a RPM, paths are fixed in the RPM archive. Either there is preinstall or postinstall script magic, or there must be different RPMs for different architectures. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
participants (6)
-
Dave Howorth -
Dave Howorth -
Johannes Meixner -
Patrick Shanahan -
Richard -
steve