Hi ;)
Both commands turn on my printer. I remember having this problem some
months ago and it was resolved by an upgrade. It reappeared recently :)
Thanks you for your intention ;)
KnuX.
Here is the hp-info output :
[01mHP Linux Imaging and Printing System (ver. 0.9.10)[0m
[01mDevice Information Utility ver. 3.4[0m
Copyright (c) 2003-6 Hewlett-Packard Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.
[01mUsing device: hp:/usb/deskjet_5100?serial=MY41A4K3X57A[0m
[01mDevice Parameters (dynamic data):[0m
[1m Parameter
Value(s) [0m
----------------------------
----------------------------------------------------------
3bit-status-code
24
3bit-status-name
NoFault
agent1-ack
False
agent1-desc Black
cartridge
agent1-dvc
0
agent1-health
0
agent1-health-desc
Good/OK
agent1-hp-ink
False
agent1-id
9
agent1-kind
3
agent1-known
False
agent1-level
85
agent1-level-trigger
0
agent1-sku 56
(C6656A)
agent1-type
1
agent1-virgin
False
agent2-ack
False
agent2-desc Tri-color
cartridge
agent2-dvc
0
agent2-health
0
agent2-health-desc
Good/OK
agent2-hp-ink
False
agent2-id
10
agent2-kind
3
agent2-known
False
agent2-level
17
agent2-level-trigger
0
agent2-sku 57
(C6657A)
agent2-type
2
agent2-virgin
False
agent3-ack
False
agent3-desc Photo
cartridge
agent3-dvc
0
agent3-health
1
agent3-health-desc Not
installed
agent3-hp-ink
False
agent3-id
0
agent3-kind
3
agent3-known
False
agent3-level
0
agent3-level-trigger
7
agent3-sku 58
(C6658A)
agent3-type
3
agent3-virgin
False
back-end
hp
cups-printer
hpdeskjet5150
cups-uri
hp:/usb/deskjet_5100?serial=MY41A4K3X57A
dev-file
device-state
1
device-uri
hp:/usb/deskjet_5100?serial=MY41A4K3X57A
deviceid
MFG:hp;MDL:deskjet
5100;CMD:MLC,PCL,PML,DW-PCL,DESKJET,DYN;CLS:PRINTER;DES:51
50;SN:MY41A4K3X57A;S:0380008084001021002c1480055c2500011;J
:
;Z:0102;
duplexer
0
error-state
0
host
in-tray1
True
in-tray2
False
is-hp
True
media-path
3
panel
0
panel-line1
panel-line2
photo-tray
0
port
1
r
0
revision
3
rg
000
rr
000000
rs
000000000
serial
MY41A4K3X57A
status-code
1000
status-desc The printer is
idle.
supply-door
0
top-door
1
[01m
Model Parameters (static data):[0m
[1m Parameter
Value(s) [0m
----------------------------
----------------------------------------------------------
align-type
1
clean-type
1
color-cal-type
3
copy-type
0
embedded-server-type
0
fax-type
0
icon
deskjet_5100.png
io-control
0
io-mfp-mode
2
io-mode
1
io-scan-port
0
io-support
2
linefeed-cal-type
0
model
deskjet_5100
model-ui HP Deskjet
5100
panel-check-type
0
pcard-type
0
pq-diag-type
0
r0-agent1-kind
3
r0-agent1-sku 56
(C6656A)
r0-agent1-type
1
r0-agent2-kind
3
r0-agent2-sku 57
(C6657A)
r0-agent2-type
2
r0-agent3-kind
3
r0-agent3-sku 58
(C6658A)
r0-agent3-type
3
scan-type
0
status-type
2
support-type
2
tech-class
DJGenericVIP
tech-type
2
[01m
Status History (most recent first):[0m
[1m Date/Time Code Status
Description User Job ID [0m
-------------------- ----- ----------------------------------------
-------- --------
31.05.2006 23:39:19 1000 The printer is idle.
root
31.05.2006 23:39:03 1000 The printer is idle.
root
31.05.2006 23:39:00 1000 The printer is idle.
root
Henrique de Moraes Holschuh wrote:
On Sun, 28 May 2006, KnuX wrote:
However, I found an annoying behaviour... When I boot my Debian, the printer is
turned on, what is not really necessary.
Also, each night, the printer is turned on too... I found these messages in
/var/log/messages:
Does any of the following commands (as root) turn your printer on? Which?
/etc/init.d/cupsys restart
/etc/init.d/hplip restart
Is it possible to disable this "auto-booting" of the printer ? I notice
that only the power led was turned on, I have never eared the printer's
mecanism.
This is bogosity in the printer firmware, which turns it fully online when
inquired about its model. It is an upstream problem I have no idea how to
fix.
OTOH, as soon as we make sure exactly when your printer is being turned on,
and you give me the output of hp-info for the printer, I will forward this
bug upstream. Maybe they can fix the problem, in fact I thought they had
done so.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
