I own an old printer, Canon LBP-350. It has both parallel port and USB port, but I never have been able to use it through USB port regardless of several trials.
Because my one-year-old main desktop PC with Debian Jessie does not have a parallel port and direct USB connection seems hopeless, I recently bought a USB to Paralell-port convertor. How wonderful, it IS a cable. It has no extra power supply input nor a box at the intermediate location of the cable.
I connect the printer and the PC with a little bit peculiar feeling and booted the printer and the PC.
Then I opened the system-config-printer panel on the XFCE4 desktop. LBP-350 had already appeared. But the printer was set to inactive state. I couldn't figure out the reason, but I went on.
I opened the URL http://lcoalhost:631 and looked into the CUPS administrative page. Yes, the printer was there. I changed the status of the printer to active and pushed the test-page button and the printer printed it.
It was not a perfect process, but was very easy!
For reminder, I copy the log entries related to this device configuration:
I don't know what they mean, but the device's entering the initial inactive state seems to be reported by systemd.
Because my one-year-old main desktop PC with Debian Jessie does not have a parallel port and direct USB connection seems hopeless, I recently bought a USB to Paralell-port convertor. How wonderful, it IS a cable. It has no extra power supply input nor a box at the intermediate location of the cable.
I connect the printer and the PC with a little bit peculiar feeling and booted the printer and the PC.
Then I opened the system-config-printer panel on the XFCE4 desktop. LBP-350 had already appeared. But the printer was set to inactive state. I couldn't figure out the reason, but I went on.
I opened the URL http://lcoalhost:631 and looked into the CUPS administrative page. Yes, the printer was there. I changed the status of the printer to active and pushed the test-page button and the printer printed it.
It was not a perfect process, but was very easy!
For reminder, I copy the log entries related to this device configuration:
Feb 7 23:04:30 dossiri kernel: [ 504.546074] usb 1-3: new full-speed USB device number 6 using xhci_hcd
Feb 7 23:04:31 dossiri kernel: [ 504.674872] usb 1-3: New USB device found, idVendor=067b, idProduct=2305
Feb 7 23:04:31 dossiri kernel: [ 504.674874] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Feb 7 23:04:31 dossiri kernel: [ 504.674875] usb 1-3: Product: IEEE-1284 Controller
Feb 7 23:04:31 dossiri kernel: [ 504.674876] usb 1-3: Manufacturer: Prはlific Technology Inc.
Feb 7 23:04:31 dossiri mtp-probe: checking bus 1, device 6: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3"
Feb 7 23:04:31 dossiri mtp-probe: bus: 1, device: 6 was not an MTP device
Feb 7 23:04:31 dossiri kernel: [ 504.729303] usblp 1-3:1.0: usblp0: USB Bidirectional printer dev 6 if 0 alt 1 proto 2 vid 0x067B pid 0x2305
Feb 7 23:04:31 dossiri kernel: [ 504.729323] usbcore: registered new interface driver usblp
Feb 7 23:04:31 dossiri udev-configure-printer: add usb-001-006
Feb 7 23:04:31 dossiri udev-configure-printer: device devpath is /devices/pci0000:00/0000:00:14.0/usb1/1-3
Feb 7 23:04:31 dossiri systemd[1]: configure-printer@usb-001-006.service: main process exited, code=exited, status=1/FAILURE
Feb 7 23:04:31 dossiri systemd[1]: Unit configure-printer@usb-001-006.service entered failed state.
I don't know what they mean, but the device's entering the initial inactive state seems to be reported by systemd.
Comments
Post a Comment