Bug#2032: 2036. Printer stuck #3.
Bug: 2032 & 2036. Printer stuck #3.
_____________________________________________________________________________
"the problem reports system" sent me THIS:
Your message didn't have a Package: line at the start (in the
pseudo-header following the real mail header), or didn't have a
psuedo-header at all.
This makes it much harder for us to categorise and deal with your
problem report; please ensure that you say which package(s) and
version(s) the problem is with next time. Some time in the future the
problem reports system may start rejecting such messages.
Ian Jackson
(maintainer, debian-bugs)
---------
My reply:
Package: 0, NULL, N/A, EMPTY SET, NONE
So what would make some dumb "problem reports system" think I don't have a
bunch of problems here? Don't it believe that there are bugs with MORE than
just the Packages? You can TELL it hasn't had to endure booting and installing
a system without a FUNCTIONAL "PRINT SCREEN" BUTTON, for example numero uno.
Perhaps you are implying you may set up 2 reporting systems:
1. Package problems.
2. Non-package problems.
and that the above scary message would apply only to system #1. True???
_____________________________________________________________________________
Bruce Perens <Bruce@Pixar.com> Pixar Animation Studios
sent me THIS:
You must have the "lp" module in your /etc/modules file.
Try "insmod lp" and see if the printer wakes up.
I know my printer doesn't move until that module gets loaded, so I'd guess
that's what is wrong with your system.
If that's the problem, please tell us so that we can close out the bug.
We don't have all of the drivers in the kernel when it starts because they
don't fit.
---------
My reply:
"Try "insmod lp"": I WAS wondering how to figure out how to do that! Thanks.
---
"my printer doesn't move until that module gets loaded": eh?
With OR WITHOUT "that module":
Does it print the screen when you press the PRINT SCREEN button during
booting, installation and forever afterwards? Mine (HP Deskjet 500) doesn't.
Does it RESET when you press its RESET button? Mine (HP Deskjet 500) doesn't.
Does it RESET when you cycle its POWER? Mine (HP Deskjet 500) doesn't.
Does it RESET and print when you boot MS-DOS with CTRL-ALT-DEL after running
Debian? Mine (HP Deskjet 500) doesn't.
Does it RESET and print ONLY when you press the COMPUTER'S RESET button and
then boot MS-DOS after running Debian? Mine (HP Deskjet 500) DOES.
Plus, I've booted and installed Debian at least 3 times, now, both with and
without "line printer support" selected. No difference.
And, in my post #2 I showed how I did the "insmod" thing.
So, no, it does NOT appear that "that's the problem".
---
"We don't have all of the drivers in the kernel when it starts":
Could THIS be, or be a part of, "the problem"?
_____________________________________________________________________________
Mike sent me:
On Fri, 15 Dec 1995, Eddie Maddox wrote:
> After booting Debian GNU/Linux the printer will not print,
> the printer's own RESET button does nothing,
> and the Power On Reset doesn't happen when cycling the printer power
> switch.
My guess would be that you don't have printer support loaded. Does your
/etc/modules file have a line for 'lp' and/or have you
compiled lp support into a custom kernel?
It is also helpful if,
before posting things to debian-bugs,
you try debian-user---
every message to debian-bugs has to be disposed of by someone,
meaning extra hassle
if it's something likely to be a simple misconfiguration like this.
---------
My reply:
"My guess ...": See below.
---
"compiled ... into a custom kernel?": This is not for me.
---
"try debian-user---":
I subscribed for 2 days.
I had to unsubscribe to slow the flow.
---
"every message to debian-bugs has to be disposed of by someone":
Precisely.
---
"meaning extra hassle":
like what I'm having, too?
---
"likely to be a simple misconfiguration":
That would be nice.
_____________________________________________________________________________
Susan Kleinmann, sgk@sgk.tiac.net, sent me:
What kind of printer do you have? Have you tried /dev/lp1 ?
---------
My reply:
HP Deskjet 500. Yes. And ...2, also.
_____________________________________________________________________________
Bruce Perens <Bruce@Pixar.com> Pixar Animation Studios
sent me:
Try /dev/lp0, /dev/lp1, and /dev/lp2 .
I don't think the print screen button works,
but you can print any of the virtual screens
(the ones that you access by pressing Alt-F1 through Alt-F12)
with the command (as root) "cat /dev/vcs0 >/dev/lp0" .
Change the vcs and lp numbers as appropriate.
---------
My reply:
"but you can print ...":
A VERY useful tip. I use it below. I wouldn't have thought it up all by
myself for quite a while. Putting "2 & 2" together is as easy as putting a
thousand piece puzzle together all alone, 2 pieces at a time.
Very time conSUMing. Doing it together, on line like this, helps.
It does NOT replace the PRINT SCREEN button, though.
So, it is NOT a work-around.
---
"I don't think the print screen button works,":
So, did YOU, or SOMEONE YOU KNOW, report it as a bug already?
So, WILL IT BE ANIALATED in the next "bug fix" release?
---
"Try /dev/lp0, /dev/lp1, and /dev/lp2 .": Done. See below.
_____________________________________________________________________________
Mike, sent me:
Looking at the perms on my system, it looks like you also have to be a
member of group 'lp' before you'll be able to get anywhere.
---------
My reply:
What was all that about "extra hassle" all about?
Stuff like this?
_____________________________________________________________________________
Susan Kleinmann, sgk@sgk.tiac.net, sent me:
> 3. lsmod >/dev/lp0
> returns: "bash: /dev/lp0: No such device"
> and I was logged in as root, too.
>
> Using lp1 or lp2 is no help.
Possible hints:
Do you have entries of this form in your /dev/directory?
crw-rw---- 1 root lp 6, 0 Dec 31 1969 lp0
crw-rw---- 1 root lp 6, 1 Dec 31 1969 lp1
crw-rw---- 1 root lp 6, 2 Dec 31 1969 lp2
I have an HPLJ IV.
It requires a Control-D after I send it some plain text.
This is done through an executable filter
which is named in the printcap entry for my printer.
But before getting my filter set up,
I can at least test that the printer is receving data from the computer
using a command such as you used;
all I do is look for a blinking light on the printer
just after I press ENTER at the end of the lsmod > /dev/lp1 command.
Is there a blinking light indicator on you DeskJet, and does it not blink?
Have you tried power cycling?
---------
My reply:
"Have you tried power cycling?": Yes.
---
"Is there a blinking light indicator on you DeskJet, and does it not blink?":
Yes, there is.
Yes, it does NOT blink. (It's labeled, "BUSY".)
(And, yes, the "ON LINE" light HAS been lit in all cases,
including when pressing the PRINT SCREEN button.)
---
"Do you have entries of this form in your /dev/directory?":
A little session snippet:
# lsmod
Module: #pages: Used by:
lp 2
slip 2
ppp 5
slhc 2 [ppp]
dummy 1
umsdos 5
nfs 11
# ls -ls lp*
0 crw-rw-rw- 1 root lp 6, 0 Dec 10 04:04 lp0
0 crw-rw-rw- 1 root lp 6, 1 Dec 10 04:04 lp1
0 crw-rw-rw- 1 root lp 6, 2 Dec 10 04:04 lp2
# ls -ls lp* >/dev/lp0
bash: /dev/lp0: No such device
# ls -ls lp* >/dev/lp1
bash: /dev/lp1: No such device
# ls -ls lp* >/dev/lp2
bash: /dev/lp2: No such device
# who am i
Dawntreader!root tty1 Dec 18 05:51
# who
root tty1 Dec 18 05:51
# cat /dev/vcs0 >/mnt/l/bug/vcs0d
_____________________________________________________________________________
Susan Kleinmann, sgk@sgk.tiac.net, sent me:
I agree that the use of the term "line printer" is an anachronism. It would
probably be impossible to eradicate it from *nix internal use, but if
it's possible to remove it from any installation scripts, I think that would
be a good idea.
---------
My reply:
You would only find all that true, Susan, if there were no such thing as
"line printers" any more. I don't follow the industry that much, but I
suspect there is still a "line printer" industry, of sorts.
What you DO want is to call a "line printer", RATHER THAN SOMETHING ELSE,
a "line printer". For a "character/graphics printer", or just general,
catch-all usage, the term "printer" works fine.
---
"it's possible to remove it from any installation scripts":
so does this mean the terminology will be corrected in the NEXT RELEASE
for that one installation screen, at least?
_____________________________________________________________________________
{([|])}-{([|])}-{([|])}-{([|])}-{([|])}-{([|])}-{([|])}-{([|])}-{([|])}-{([|])}
The above reflects the observations of myself only, unless stated otherwise.
Eddie Maddox, Amateur Lobbyist "Great spirits have always encountered
maddo005@gold.tc.umn.edu violent opposition from mediocre minds."
P.O. Box 75321
St Paul MN 55175-0321 Albert Einstein
USA
Reply to: