[SOLVED]Failure to print to iP90 after upgrade of OS

Questions on certain printers and applications
Post Reply
tarazed
Posts: 8
Joined: Fri Dec 03, 2010 10:55 am

[SOLVED]Failure to print to iP90 after upgrade of OS

Post by tarazed »

For two years my Canon iP90 has served me well on a 32bit system running Magaeia 2. Time
to move up to Mageia 4 I thought. The printer was working fine yesterday on Mageia 2 but
after the installation of Mageia 4 I have had no luck with either CUPS or Turboprint.
Both insisted that the printer was switched off or not connected. I even tried the
latest version of Turboprint without a key and succeeded once in getting a test page.
After a reboot the ip90 was incommunicado again. I tried removing and plugging in cables
but to no avail. After 12 solid hours of this I have to admit defeat. Any thoughts?

I have specified 'other' for the printer connection and a URI of
usb://Canon/iP90?serial=107B08. Using the Gutenprint IP90 driver.

Tailend of dmesg:

Code: Select all

[ 5776.148514] usbcore: registered new interface driver usblp
[ 6128.000139] usb 2-1: USB disconnect, device number 2
[ 6150.367067] usb 2-1: new full-speed USB device number 3 using uhci_hcd
[ 6150.528110] usb 2-1: New USB device found, idVendor=04a9, idProduct=109d
[ 6150.528120] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 6150.528128] usb 2-1: Product: iP90
[ 6150.528134] usb 2-1: Manufacturer: Canon
[ 6150.528141] usb 2-1: SerialNumber: 107B08
[ 6150.535215] usblp 2-1:1.0: usblp1: USB Bidirectional printer dev 3 if 0 alt 0 proto 2 vid 0x04A9 pid 0x109D
[ 6155.934611] usblp1: removed
[ 6155.956065] usblp 2-1:1.0: usblp1: USB Bidirectional printer dev 3 if 0 alt 0 proto 2 vid 0x04A9 pid 0x109D
Last edited by tarazed on Thu Feb 20, 2014 9:46 pm, edited 1 time in total.
zedonet
Site Admin
Posts: 2156
Joined: Fri Oct 06, 2006 8:02 am

Re: Failure to print to iP90 after upgrade of OS

Post by zedonet »

Hello tarazed,

was your printer connection detected automatically by TurboPrint? When adding a printer in TurboPrint Control, all connected USB printers should be listed - please just select your printer from that list, do not enter the URI (usb://...) manually as minimal faults in the URI would lead to a "printer not connected" message.
If the printer is not listed, there might be some problems with the usblp or libusb libraries on your system.

If you still have printing problems, you can try the following to switch from using libusb to usblp (only if you have some experiences with a text editor and altering system files as superuser):
Edit the file

/etc/turboprint/system.cfg

and add the line "USB_MODE=0". In case this line was already present (e.g. USB_MODE=1) just alter it.

Please reboot after this change or disconnect and reconnect your printer.
tarazed
Posts: 8
Joined: Fri Dec 03, 2010 10:55 am

Re: Failure to print to iP90 after upgrade of OS

Post by tarazed »

I first reported these problems on a Mageia forum because CUPS was unable to see any USB printers except my HP 6520 which had already been configured through HPLIP. I went back to Turboprint in the hope that it would see the iP90 but no, nothing in the list. That is when I resorted to trying a URI. I am interested to note your qualification regarding the effect of a possibly malformed URI.

At one point I blacklisted usblp when someone pointed out that it has a history of causing trouble with printer drivers. That did not help but I shall try configuring Turboprint directly as you suggest. I am out of time just now but expect a report from me later.

Thanks for your help.
tarazed
Posts: 8
Joined: Fri Dec 03, 2010 10:55 am

Re: Failure to print to iP90 after upgrade of OS

Post by tarazed »

Success! system.cfg had no USB entry so I tried USB_MODE=0/1. Neither value had any effect so I had a look at the other parameters; most of them have the prefix TP_ . Using TP_USB_MODE=1 had an immediate effect (after switching the printer off and on). The iP90 was listed and succeeded in printing a testpage in A5 format as requested. One peculiarity though. The queue name changed automatically from the specified ip90 to ip90.1 (another ip90 hanging around in the system maybe?). Command line printing worked fine as well;

Code: Select all

 lpr -Pip90.1 <some text file> 
So, many thanks. Time to pick up a new licence.
Post Reply