Bob Schwier on 28 Sep 2010 20:41:03 -0700

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: [PLUG] 10.04 install problems

  • From: Bob Schwier <>
  • To: Philadelphia Linux User's Group Discussion List <>
  • Subject: Re: [PLUG] 10.04 install problems
  • Date: Tue, 28 Sep 2010 20:40:58 -0700 (PDT)
  • Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=s1024; t=1285731658; bh=aCxAXBQn5m6P4KDQy82kER2FQs4mkqej4Q3c+WTQmvw=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=PwZjYVw+0vqssYFEHMwaLq28cmji7iDCSAwe4CRIm2WRgafw4p6wbVJuSAcb1bJ6fswY+2ZbrVvRCJtp2AYd/WDSedqzBxi/2FSQYPt9oduPdyDOByqzfcJVYBjF/PotE44u0/jvdOCek8BeIejAC2t3SmE+U2c/1J5LGL0V6+s=
  • Reply-to: Philadelphia Linux User's Group Discussion List <>
  • Sender:

Lucid is making me miss Heron and even SUSE 7.0.
Okay, the machine now recognizes that it has a nine pin printer but only if I go in
the terminal and sudo /etc/init.d/cups start.  Meanwhile,  I still have to tell it that it's
failsafeX in recovery mode each time.
It looks like I have to do something for the first time that many of you seem capable
of doing in your sleep, to wit, rewrite the kernel.  As I said previously, the sys/admin
controls in the GUI don't seem to do anything as the buttons I need are grayed out.

--- On Sun, 9/26/10, Bob Schwier <> wrote:

From: Bob Schwier <>
Subject: Re: [PLUG] 10.04 install problems
To: "Philadelphia Linux User's Group Discussion List" <>
Date: Sunday, September 26, 2010, 12:16 PM

--- On Sat, 9/25/10, Jason Stelzer <> wrote:

> From: Jason Stelzer <>
> Subject: Re: [PLUG] 10.04 install problems
> To: "Philadelphia Linux User's Group Discussion List" <>
> Date: Saturday, September 25, 2010, 12:36 PM
> You may want to check out the
> following:
> On Sat, Sep 25, 2010 at 11:22 AM, Bob Schwier <>
> 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

> > /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.

> --
> J.
> ____________________________________________________________

-----Inline Attachment Follows-----

Philadelphia Linux Users Group         --
Announcements -
General Discussion  --

Philadelphia Linux Users Group         --
Announcements -
General Discussion  --