On 09/27/2012 02:21 PM, Colin Guthrie wrote:
'
Does your dmesg report anything interesting going on with the device?
Sort of, by omission.
At 10 seconds in, we have
[ 10.744514] usblp 1-1:1.0: usblp0: USB Bidirectional printer dev 3 if
0 alt 1 proto 2 vid 0x03F0 pid 0x1817
[ 10.744529] usbcore: registered new interface driver usblp
then, at 12 seconds
[ 12.582770] systemd[1]: Enqueued job printer.target/start as 175
Now if the kernel were "losing" the printer every 5 seconds, I'd expect
to see some indication of it around 15 seconds, but nothing. In fact,
[ 28.874663] device-mapper: multipath: version 1.4.0 loaded
[ 29.076321] systemd[1]: Forked /usr/sbin/cupsd as 9332
[ 29.076402] systemd[1]: Job cups.service/start finished, result=done
[ 29.076550] systemd[1]: printer.target changed dead -> active
[ 29.076555] systemd[1]: Job printer.target/start finished, result=done
and then suddenly
[ 34.241942] usblp0: removed
[ 34.258926] usblp 1-1:1.0: usblp0: USB Bidirectional printer dev 3 if
0 alt 1 proto 2 vid 0x03F0 pid 0x1817
[ 38.843836] lp: driver loaded but no devices found
[ 39.547619] usblp0: removed
[ 39.564331] usblp 1-1:1.0: usblp0: USB Bidirectional printer dev 3 if
0 alt 1 proto 2 vid 0x03F0 pid 0x1817
[ 39.710816] ppdev: user-space parallel port driver
[ 44.851351] usblp0: removed
[ 44.867689] usblp 1-1:1.0: usblp0: USB Bidirectional printer dev 3 if
0 alt 1 proto 2 vid 0x03F0 pid 0x1817
[ 50.157199] usblp0: removed
[ 50.174091] usblp 1-1:1.0: usblp0: USB Bidirectional printer dev 3 if
0 alt 1 proto 2 vid 0x03F0 pid 0x1817
[ 52.499738] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 55.459678] usblp0: removed
[ 55.476467] usblp 1-1:1.0: usblp0: USB Bidirectional printer dev 3 if
0 alt 1 proto 2 vid 0x03F0 pid 0x1817
and so it goes, at 5-second intervals.
