Re: Print / Network Problem

[ABrady <kcsmart kc rr com>]

On Mon, 22 Oct 2001 12:06:35 -0400 Tom Kearns <tkea home com> imparted
to us:
> ABrady wrote:
> 
> > On Mon, 22 Oct 2001 11:29:47 -0400 Tom Kearns <tkea home com>
> imparted
> > to us:
> > > I'm a redhat novice.  I get the following error when lpd tries to
> > > start
> > > during initialization:
> > >      Starting lpd:  Get_local_host :  hostname '<myhostname>' bad
> > >
> > > I am also unable to get my ethernet (eth0) to start at init time,
> but
> > > can manually bring it up using dhcpcd -h <hostname> eth0   I can
> then
> > > start lpd, but still can't print.  Jobs go into the print queue
> OK.
> > > When I enter the lpq command, I see the following message as part
> of
> > > the
> > > display:
> > >
> > >    Status: IF filter 'mf_wrapper' filter msg - 'closed
> *main::KID3'
> > >
> >
> > After getting the ether up, type (as root):
> >
> > depmod -a
> >
> > See what that gets you. If that works lpd starting should be solved.
> If
> > it doesn't see if you have pump installed. If not, install it and
> try
> > again. If it is installed, remove it and try again. Some people have
> > problems if it exists, others (me) have problems if it doesn't.
> >
> > May not have anything to do with anything, but, what release and
> > printer? It all may magically work after the above, Then again, it
> might
> > not.
> >
> > --
> > Excuse my english. I went to US public school.
> >
> > _______________________________________________
> > Redhat-list mailing list
> > Redhat-list redhat com
> > https://listman.redhat.com/mailman/listinfo/redhat-list
> 
> I did the depmod -a   Also ran pump (was not running it before).  
> Same
> problems.  I'm running RedHat 7.1, kernel 2.4.2.2.  The printer is a
> Lexmark 5700.

Alright, let's try something else.

Do you have a hostname set in /etc/hosts for the machine? That should
get around the lpd part at least.

For the ether, you might have to do something a little more extreme.
There might be 2 ways to fix it. One lasts longer than the other, but
it's a kludge. The other is more proper, but it may fail on the next
kernel upgrade like it always did on me.

PROPER
Make sure kudzu is running, shut down, remove the NIC, boot and let
kudzu remove the config for the NIC, shut down, reinstall the card, boot
and let kudzu reconfigure. This (nearly) always worked for me, but it
only lasted until I added a new kernel. Then had to do the same all over
again.

WORKS (for me, anyway)
Turn off networking and anything that depends on it (i.e. network, smb,
lpd [unless the other thing fixed it], nfs, mail, anything else that
automatically comes up at boot that needs networking). Then add lines to
the end of rc.local to rmmod and insmod the module for the NIC. After
that start networking, followed by all of the other stuff you turned
off. This one worked every time I tried except with the 2.4.3 kernel,
which refused to work with any NIC I own.

-- 
99% of lawyers give the rest a bad name.