Skip to main content

Using Canon LBP-350 printer with Debian Jessie

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:

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

Popular posts from this blog

Configuring Network Manager for PPPoE connection

When I'm home, I use fiber-optic line with a dedicated old small router (YAMAHA RT107e) for access to the Internet. But I recently became anxious about the router. If it fails, how can I survive until I get another one? So, I tried to connect my Debian desktop PC to the fiber-optic line without the router. The PC have to talk to the other side of the line with PPPoE but I did not know how. In my PC, the Network Manager manages network configuration. So, I had to configure the Network Manager to utilize the pppoe like : nmcli connection add ifname eth0 connection.type pppoe username USERNAME password PASSWORD
Post a Comment
Read more

Xen on Squeeze failed to start up the X server with an Intel graphics controller

I recently tried to set up Xen on my Squeeze box, with intel 945GM graphics controller. I followed the instruction on Xen - Debian Wiki . I installed the Xen hypervisor, kernel, xen-tools and other stuff, then created a domU image of Ubuntu natty. After that, I rebooted the system. But when X server was about to be launched, the screen became black out,  both keyboard and mouse don't work anymore. I reread the article on the wiki, and figured out the Xorg driver for Intel graphics controller  is suspicious. So, I changed the Xorg driver 'intel' to 'fbdev' wrting /etc/X11/xorg.conf , and rebooted.  This workaround works out! The drawback of the workaround is, 'intel' driver specific features, including DRI and XvMC, are disabled.
1 comment
Read more

Sharing one home directory between the Linux machines with the different display resolutions and different pointing devices, keeping $HOME/.config data for each machine

 Back in 1990's, it was common practice to share one home directory between many UNIX servers using NFS. But it is not in these days. But I have become to want to share my home directory between two different Linux machines: One is  a Debian GNU/Linux installed as a primary OS of a dual boot machine,  and the other is a virtualized Linux box within the Virtualbox running under the Windows 10, a secondary OS of the dual-boot. They have different display resolutions and pointing devices. These differences led me to an annoying problem: if you open GNOME desktop environment, display and pointing device setting became broken. Today's GNOME desktop environment stores most of the settings to the files under $HOME/.config directory. But if you share $HOME/.config between two machines, the stored configuration for a particular machine may become incompatible with other machines with different display resolutions and pointing devices. Indeed, my GNOME desktop has become unusable. To ove
Post a Comment
Read more