From: Henrik Størner <henrik@storner.dk>
To: linux-kernel@vger.kernel.org
Subject: 2.4.0-test12pre4: parport / lp problems
Date: Mon, 4 Dec 2000 21:33:48 +0100 [thread overview]
Message-ID: <20001204213348.A932@storner.dk> (raw)
I discovered yesterday that printing does not work in 2.4.0-test12-pre4.
This is a pretty stock PC system with a printer on the parallel port.
Both parport and lp is compiled into the kernel - and the parport
appears to be detected OK, but the lp driver for some reason refuses
to use it:
[snip /var/log/dmesg]
Starting kswapd v1.8
parport0: PC-style at 0x378 [PCSPP]
parport0: irq 7 detected
[later]
pty: 256 Unix98 ptys configured
parport0: no more devices allowed
lp: driver loaded but no devices found
In lilo, I have tried different configuration parameters. The current
setup has no parport or lp settings, but I have also tried
"parport=0x378,7 lp=parport0"
with no apparent effect. This setting used to work in earlier 2.4
configurations (cannot say exactly which worked and which didn't).
Kernel config:
#
# Parallel port support
#
CONFIG_PARPORT=y
CONFIG_PARPORT_PC=y
CONFIG_PARPORT_PC_FIFO=y
# CONFIG_PARPORT_PC_SUPERIO is not set
# CONFIG_PARPORT_AMIGA is not set
# CONFIG_PARPORT_MFC3 is not set
# CONFIG_PARPORT_ATARI is not set
# CONFIG_PARPORT_SUNBPP is not set
# CONFIG_PARPORT_OTHER is not set
# CONFIG_PARPORT_1284 is not set
[snip]
CONFIG_PRINTER=y
# CONFIG_LP_CONSOLE is not set
# CONFIG_PPDEV is not set
Suggestions ?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-12-04 21:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-04 20:33 Henrik Størner [this message]
2000-12-04 22:07 ` 2.4.0-test12pre4: parport / lp problems Henrik Størner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20001204213348.A932@storner.dk \
--to=henrik@storner.dk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.