To anyone who made the mistake of installing RH6.1, a printer (does not
matter which make/model) connected to the parallel port will not work
without a two step work around.
1. Edit your /etc/conf.modules and add:
alias parport_lowlevel parport_pc
2. Then log in as root and run:
modprobe ppa
I also encounterred another show stopper w. the Gnome "rp3" utility for
configuring dial up Internet access. The "rp3" utility hangs. The fix is
to download the updated .rpm for "rp3" or maybe use KDE instead.
Maybe the easiest solution is to change to a different distribution.
Rodney
I installed RH6.1 and my parallel printer wasn't working. I found some
errata about it on the RedHat web site(some probe command, one time setup.
Seemed like a major show stopper to me).
I tried to retrace my steps, could not find the exact info again.
But http://www.redhat.com/support/docs/faqs/rhl_general_faq/FAQ-7.html
has some parallel zip drive info:
In Red Hat Linux 6.1, there are a few extra steps needed to get a parallel
port Zip drive to work:
Edit your /etc/conf.modules and add:
alias parport_lowlevel parport_pc
alias scsi_hostadapter ppa
Then log in as root and run:
modprobe ppa
Some people have had problems if they daisy chain a Zip drive off of a chain
with a printer on it. Currently, we recommend that
you use either the printer or the Zip drive.
For more information, check www.torque.net/paraport
Maybe this is the silver bullet you were looking for.
Rodney
Omer J Hickman wrote:
> I've been trying to get my parallel port ZIP100 up. The RH6.0 install
> program will not detect it.
> But 'paraprot_lowlevel' shows up in the kernel configurator in control
> panel.
> (I can't find a lot of information about paraport, except that it is for
> allowing
> dasy-chaining of parallel port devices)
>
> #insmod ppa.o
>
> results in 'unresolved symbol' errors, most of these being to functions
> named
> 'paraport_???'. So ppa.o depends on paraport_lowlevel?
>
> Also, since I tried to install my ZIP100 I can't print (yes I double
> checked the
> settings in printcap) But I looked in the paraport sources and it says
> that it
> displaces part of the default printing system.
>
> So am I to assume that install tried to install the paraport module and
> failed to
> get it working, but still disabled the default printing driver?
>
> If this sounds right, does anyone know more about setting up the
> paraport
> module correctly?
>
> I also followed the directions in the ZIP HOWTO and recompiled my kernel
>
> but it had no effect.
>
> Thanks in advance.
