On Thu, 15 Jun 2000, Miroslav Skoric wrote about, Re: RH 6.1 and printer ports =
how?:
> Richard Adams wrote:
>
> > Simply start kerneld.
> > /sbin/kerneld
> >
> > You may want to add that to one of your start scripts.
>
> After I did:
>
> /sbin/kerneld
>
> I got:
>
> Starting kerneld, version 2.1.121 (pid 678)
That is good, it means it is running nicly as a process.
>
> But, I haven't noticed anything happened to the printer (that was
> already on). Btw, recently before starting kerneld, it looks that I
> solved a boring continual beep sound coming from the printer (that was
> not only annoying but disabled the printer from feeding a sheet of
> paper). I have added two lines into /etc/rc.d/rc.local as Lawson
> suggested:
>
> /sbin/insmod parport
> /sbin/insmod parport_pc
>
> but, I haven't added the 3rd line /sbin/insmod lp
When one runs kerneld one does not need any insmod or modprobe statements,
all you need to do is have aliases in /etc/conf.modules or modules.conf
which ever your system has.
A typical conf.modules file for the lp module would be something like the
following.
alias parport_lowlevel parport_pc
options parport_pc io=0x378,0x278 irq=7,auto
alias lp0 lp
What does that mean.?
It means when kerneld is running it know knows what to do when you type;
cat filename >/dev/lp0
It will automaticly load all needed modules, print the file and after a
short time of 'no printer use' kerneld will automaticly unload the drivers
and free up the memory which was in use by the modules.
A small hint;
You can create a /etc/conf.modules file by doing the following.
cp /etc/conf.modules /etc/conf.modules.ORG
modprobe -c >new_modules.file
Modprobe will check your system for all known modules and aliases and write
them to the file new_modules.file.
You may now;
cp new_modules.file /etc/conf.modules
If you do the above while you have manually loaded all the modules you
normally use, then modprobe will detect all of them and make enteries into
the new file.
>
> and it looks like the printer is initialized somewhere at the end of
> linux start and just before the login screen (either text or graphical
> one).
The printer does not need to be initialized at bootime when you use the
above mentioned method.
Remove the symlink in /etc/rc.d/rc3.d for lp, that will stop it getting
initialised at bootime. Where rc3.d is the runlevel you use.
>
> Now, it looks to me that is one thing remained to solve: an 'offline'
> setup configuration by the printer itself. Maybe there is a
> misconfigured detail(s) that produces such a beep sound just after the
> printer is switched on (its actual default boot mode is Epson LQ2550
> compatible that worked here for years, but it didn't produce such beep.
> Because, there is a beep playing before LILO started either Linux or NT
> (in case of NT started, I noticed that there are two points where it
> initializes the printer: the first one is on the opening black screen
> where NT checks the hardware, the second is somewhere just before the
> login/password screen. Interesting is that Linux seems to initialize the
> printer only once: somewhere before the login checkpoint).
Even that is not needed.
>
> Misko
>
> Misko
--
Regards Richard
[EMAIL PROTECTED]
http://people.zeelandnet.nl/pa3gcu/
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
