Re: [PLUG] 10.04 install problems

--- On Sat, 9/25/10, Jason Stelzer <jason.stelzer@gmail.com> wrote:

> From: Jason Stelzer <jason.stelzer@gmail.com>
> Subject: Re: [PLUG] 10.04 install problems
> To: "Philadelphia Linux User's Group Discussion List" <plug@lists.phillylinux.org>
> Date: Saturday, September 25, 2010, 12:36 PM
> You may want to check out the
> following:
>
> https://wiki.ubuntu.com/DebuggingPrintingProblems
>
> On Sat, Sep 25, 2010 at 11:22 AM, Bob Schwier <schwepes2002@yahoo.com>
> wrote:
> > dpkg --configure --all
>
> You want "dpkg --configure -a"
> --all isn't valid. The man page has the details.

dpkg --configure -a got back a response that there was no -o switch.
I had typed everything correctly and simple --configure got the same response.

aptitude looks very interesting. Wish I knew more about it as it seems that what
I need is somewhere in there.

>
>
> > Which usually fix things if the upgrade didn't
> complete correctly.
> >
>
> All that does is finish unpacking debs and execute pending
> scripts. If
> things are in a state where modules aren't being loaded,
> then it may
> not fix much of anything. But, it's going to at least get
> the system
> back into a state where apt-get can be used to install
> additional
> things.
>
>
> > The printer has no work around like that. There is
> no lp0 or
> > lp anything in /dev and various commands offered on
> the cups
> > site simply don't do anything.
>
> Check that the kernel has loaded the right modules. See the
> wiki page
> above for details.
>

Followed instructions on wiki page, the attachment tells what I got.
I seem to be missing ppdev. Merely adding it to /etc/modules was mentioned in
the article but that did not fix it. I don't know if I have a copy of ppdev on the machine
to work with.

> Once you get the correct device drivers loaded into the
> kernel,
> restart cups via the /etc/init.d script. Cups is the
> printing system,
> if it isn't starting, invoking commands that query it is
> premature.
>
Child exited on signal 15. Whatever that means except that I still don't have a
printer.

>
> > /proc/sys/dev/parport/parport0/autoprobe gets back no
> such
> > command even after painfully tracking down that the
> file exists
>
> Stuff under /proc is generally a file or directory, not a
> command to execute.
>
> > and nor does autoprobe's numbered variations.
>
> I'm not sure what autoprobe is in this context.

I was just following the advice in one of the articles I found on line.

>
> > lp info -v says that the connection is refused.
Still sadly true.

>
> That suggests that cups isn't running. Ensure the kernel
> modules you
> need are loaded, then try manually launching cups via the
> /etc/init.d/cupsd (or whatever cups uses). You could check
> via netstat
> -pn to see if it's running.

Netstat -pn gave me several pages of items that were "connected." I did not find
a single item that failed.

>
> I'd start by ensuring that the appropriate modules are
> loaded by the
> kernel. Once you get those loaded, I'd (re)start the cups
> daemon. If
> that gets things into a saner state, then I'd probably go
> about
> ensuring that the modules you identify get loaded on boot.
> Perhaps it
> will be as simple as adding them to /etc/modules (one per
> line).
>
> The relative merits of usb vs lp is lost on me but this
> should get you
> on your way.
>
I was just guessing that the upgrade presumed like it has with the monitor that all
equipment would be using only the most modern parameters. I wonder if I can
simply tell the /etc/modules to load failsafeX right at the beginning and not have
to figure out how to rewrite the kernel to buy my older monitor settings.
Thanks
bs

>
>
> --
> J.
> ____________________________________________________________