Epson SX535WD install on Kubuntu
Details of my recent installation of a MFP from Epson on Kubuntu wirelessly.
Epson – doing it right?
My last printer was an Epson. The one before that too. Indeed I’ve had a string of Epson printers going back possibly to the first dot matrix I used at primary school. I’ve been largely happy with my last one so Epson were certainly in the running when I was looking for an upgrade. But what clinched the deal? Linux drivers.
In the past CUPS, the every Linux distro’s choice of print system it seems, has taken quite a bit of finagling and finicking to get working. However this time I’ve been so pleased with how easy things worked I decided to blog about it. If you’re coming from a world where you use the market leaders software and everyone selling hardware already has drivers available via their install process then this may all sound a bit backward but here goes on the install process in all it’s [not so] gory detail.
Installing our Epson SX535WD
Let’s take a step back. Before buying I checked various guides – best of them seemed to be TrustedReviews.com, expertreviews.co.uk and testfreaks.co.uk (probably in that order); along with sundry others like Amazon, Ebuyer. Then I shortlisted a few printers and checked out how others were finding them for Linux installs. OpenPrinting.org confirmed that this Epson model was working for others.
So I looked for the drivers on the Epson website and they actually have a category in their drop down list for “Linux” drivers. What’s more they have several different packaged versions available. So I downloaded all the AMD64 files (and the regular i386 ones in case I needed them on some other system later).
Actually bought the printer from Argos (UK) after reserving it online as they had an ink offer on giving me a free (£40 usual cost) set of CMYK cartridges whilst still having the printer at less than the Amazon price. The printer comes with a quickstart guide, manual, driver CD but no cables other than the power cable. There were 5 pieces of blue tape to remove – check the quickstart guide for where!
The Epson driver page has a English language install guide userg_revP_e.pdf (the “j” version is the Japanese one).
Here’s how it went down (all these files downloaded from the driver page):
- Put printer on, insert cartridges following on[-printer]-screen guide.
- Input the network info, SSID was detected automatically, IP was taken from router by DHCP, directly input network “password”.
At this stage the printer is ready and waiting interaction from a computer.
- Install iscan-data by clicking on the downloaded package (gdebi-gtk does the work then and asks for admin password; you could install from CLI using dpkg or similar).
- Install iscan-$ver-ltdl$ver_$arch – I’m not sure that the ltdl stands for but gdebi required this before the regular iscan package.
- Install iscan itself.
- Install iscan-network-nt.
- Connect to 192.168.1.3 in my browser (Firefox 13); the IP is shown on the “network status” print out. Updated firmware using the interface – though this isn’t required at all and without details it’s hard to tell whether it was actually a good idea but I’ve a bit of an update fetish.
- Go to cups on http://localhost:631/ via my browser.
- Add discovered printer … but hang on, the driver isn’t present so should probably have installed …
- Installing ./epson-inkjet-printer-201106w_1.0.1-1lsb3.2_amd64.deb which required 25 additional [automatic] deps installed by gdebi.
- Also installed ./epson-inkjet-printer-escpr_1.2.0-1lsb3.2_amd64.deb but not sure if it was needed or not; think this is a basic driver used as an alternative.
- Chose the sx535fw (not sxs525 which was next closest alternative) and it works, test page prints well.
It all worked. Well, iscan wouldn’t open directly but “AcquireImages” in KDE (on Kubuntu 12.04) worked fine using [it seems] the iscan drivers to connect and scan an image. Scanning was faster than my old CX6600 and there were higher resolutions offered.
Printing worked too. In addition printing from LibreOffice and from Firefox worked without issue where previously there had been a problem. Not sure if this is related to the drivers or what.
At this stage I wasn’t sure to be happy or not. I’d set aside a few hours to conquer the intricacies of an unsupported install with the added complexity of wireless communication and everything was working after about 30 minutes. But it wasn’t all over …
Picking up the right IP address
We have a bit of a joke in our household that whenever F comes in any computer tech will stop working. That’s almost what happened. The printer had picked up the next IP address from the router which was 192.168.1.3 but this was the one that a second computer usually takes. When that computer was put on that IP was taken, putting the printer on and the router then assigned it 192.168.1.4 … this caused a problem and CUPS went in to overdrive spamming me with messages that the new printer “may not be connected”.
So I checked on the router’s “Ethernet” tab and saw that the printer had been issued a new IP. “Ah-ha!” quoth I and set to work handing out some fixed IP addresses based on MAC address via the router interface. Now with the printer set to 192.168.1.10 things still weren’t working so I also went in the printer menu system and set it’s IP acquisition to manual and give it the same address. Still not working.
So I restarted the computer, restarted the printer, manually restarted CUPS, tried various permutations of DHCP/manual settings for acquiring the address. The printer was reporting the correct address. CUPS was finding the printer, it seemed, but jobs weren’t going through. Then I noticed that the dialog “Document Print Status” – accessed via the printers tray icon – there’s a menu item for Settings > Printer Configuration.
CUPS or KDE bug or … ?
The “Printer Configuration — KDE Control Module” was reporting the same info as available via the localhost:631 CUPS interface but it appeared to have retained the original IP address of 192.168.1.3 instead of updating. So altering the setting to “lpd://192.168.1.10:515/PASSTHRU” and applying the change seemed to fix things.
One small gotcha but otherwise a smooth install, printer and scanner working well. Now off to report a potential KDE bug.