From: Ray Olszewski <ray@comarre.com>
To: linux <linux-newbie@vger.kernel.org>
Subject: Re: No Printing with Kernel 2.6.14.4
Date: Sat, 18 Mar 2006 23:02:55 -0800 [thread overview]
Message-ID: <441D021F.1060705@comarre.com> (raw)
In-Reply-To: <200603190543.k2J5hmPC001185@skyinet.net>
Peter wrote:
> Hi,
>
> Slackware 10.2
>
> When I change from kernel 2.4.31 to kernel 2.6.14.4 by installing
> kernel-generic-2.6.14.4-i686-2sh.tgz and kernel-modules-2.6.14.4-i686-2sh.tgz
> I cannot print anymore since apparently there is no provision for a parallel
> port which my printer Epson LQ 300 is using. At least when configuring the
> printer using gnome-cups-manager with kernel 2.6.14.4 it only shows serial and
> usb ports.
>
> How would I go about getting a parallel port into the 2.6.14.4 kernel. Could I
> copy it from the 2.4.31 modules and which one?
>
> In /usr/src I have no linux-2.6.14 directory only one for linux-2.4.31.
>
> Thanks & regards
I just checked the kernel source I have handy (2.6.11, Debian package)
and it appears to offer parallel port support. The relevant modules are
parport and parport_pc (the same as 2.4.x, I think ... it's been some
years since I used a parallel port). You might try modprobe'ing these
modules and see what results. If Slackware left them out of its standard
modules package, I can't imagine why.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2006-03-19 7:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-19 5:43 No Printing with Kernel 2.6.14.4 Peter
2006-03-19 7:02 ` Ray Olszewski [this message]
2006-03-19 15:22 ` Hal MacArgle
2006-03-20 1:25 ` Peter
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=441D021F.1060705@comarre.com \
--to=ray@comarre.com \
--cc=linux-newbie@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox