l i n u x - u s e r s - g r o u p - o f - d a v i s
Next Meeting:
July 7: Social gathering
Next Installfest:
Latest News:
Jun. 14: June LUGOD meeting cancelled
Page last updated:
2004 Dec 02 17:09

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox-tech] Slack 10 print problem solved
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox-tech] Slack 10 print problem solved

On Thursday 02 December 2004 12:54 am, Shwaine wrote:
> On Wed, 1 Dec 2004, Bill Wells wrote:
> > #### PC parallel port support ###
> > tupport ###
> Bad paste? If not, remove this line
line removed
> <snip>
> > #### Parallel printer support ###
> > if cat /proc/ksyms | grep "\[lp\]" 1> /dev/null 2> /dev/null ; then
> >  echo "lp support built-in, not loading module" > /dev/null
> > else
> >  if [ -r /lib/modules/$RELEASE/misc/lp.o \
> >       -o -r /lib/modules/$RELEASE/misc/lp.o.gz \
> >       -o -r /lib/modules/$RELEASE/kernel/drivers/char/lp.o \
> >       -o -r /lib/modules/$RELEASE/kernel/drivers/char/lp.o.gz \
> >       -o -r /lib/modules/$RELEASE/kernel/drivers/char/lp.ko \
> >       -o -r /lib/modules/$RELEASE/kernel/drivers/char/lp.ko.gz ]; then
> >    /sbin/modprobe lp
> >  fi
> > fi
> Have you tried removing the if statements entirely and just directly
> replacing it with "/sbin/modprobe lp" and so on for the other modules?
> Not the most elegant solution, but certainly the most direct since these
> sections of rc.modules are very 2.4.x series kernel specific. If it works
> in rc.local, it should work in rc.modules and that will solve your CUPS
> issue as well (ie the module will load before CUPS so CUPS will see the
> interface when it loads). I cannot emphasize enough that rc.local is NOT
> the place to be loading kernel modules, due to both its position in the
> boot sequence and the fact it does not get called in single user mode.
> It's perfectly acceptable to add new modprobe lines to rc.modules. Just
> remember what you did so you can redo it if you reinstall.
I commented out all of the if statements in both modules leaving only 
the /sbin/modprobe lp and /sbin/modprobe/parport_pc remaining active.
that works.

I have removed everything I added to rc.local.

All of this got me to looking around a little bit more.  In retrospect, 
should I have renamed rc.modules > rc.modules.old and made a new rc.modules 
using the rc.modules-2.6.7 as a base?  Nevermind . . .
Thanks again to everyone for your help.  

Bill Wells
> ______________________________________________ 
> vox-tech mailing list
> vox-tech@lists.lugod.org
> http://lists.lugod.org/mailman/listinfo/vox-tech
vox-tech mailing list

LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
Sunset Systems
Who graciously hosts our website & mailing lists!