From: "Alan E. Davis" <lngndvs@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: new system, printing suddenly fails for all printers
Date: Sat, 4 Jul 2009 01:48:57 +1000 [thread overview]
Message-ID: <7bef1f890907030848o4683fb32r9b9cfc1142cc21d3@mail.gmail.com> (raw)
In-Reply-To: <h2l31f$ip7$1@ger.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2058 bytes --]
Thank you Walt:
On Sat, Jul 4, 2009 at 12:02 AM, walt <w41ter@gmail.com> wrote:
>
> I've had both problems several times in the past, always caused by dumb
> things that, of course, should never happen but often do anyway.
>
Me too. Maybe so this time as well, at least I hope so.
>
> First the sound. I still don't know why but often when rebooting with
> a different kernel (I do it often) the sound mixer will wind up with
> certain channels either muted or turned down all the way. Because these
> channels are not visible on my gnome volume control I have to use the
> alsamixer to find the problem and restore the proper settings until
> the next reboot. Dumb, but that's the way it is.
There is no PCM channel in alsamixer! Maybe I will try alsamixergui, where
I saw switches once.
>
>
> You should definitely *not* unload your kernel sound modules when shutting
> down -- it's silly and causes problems. Turn this 'feature' off in your
> /etc/conf.d/alsasound by setting UNLOAD_ON_STOP="no" and KILLPROC_ON_STOP=
> "no".
Duly noted and exorcized.
>
>
> Printing. Usually my printing problems come from having the wrong printing
> "device" set in the cups Modify Printer section (localhost:631 as you
> said).
>
> Usually the problem is that I didn't have the printer connected and turned
> on when setting the 'printer device' and therefore the proper choice didn't
> appear in the menu. Really dumb.
>
Two printers are connected, and turned on. One printer, the deskjet,
started one job, a testpage, got to 17% and stayed there a good long while.
>
> Anyway, start by going back through that printer setup menu system and try
> every choice until you find one that works -- and make sure the printer is
> turned on :o)
>
Thank you again. I earnestly hope they both iron out quickly. I'm starting
to grow fond of this install.
Alan Davis
"...can the human soul be glimpsed through a microscope? Maybe, but you'd
definitely need one of those very good ones with two eyepieces."
-- Woody Allen, quoted by B. A. Palevitz
[-- Attachment #2: Type: text/html, Size: 3195 bytes --]
next prev parent reply other threads:[~2009-07-03 15:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-03 0:46 [gentoo-user] new system, printing suddenly fails for all printers Alan E. Davis
2009-07-03 14:02 ` [gentoo-user] " walt
2009-07-03 15:48 ` Alan E. Davis [this message]
2009-07-03 16:03 ` Alan E. Davis
2009-07-03 16:47 ` walt
2009-07-03 20:20 ` eamjr56
2009-07-04 0:36 ` Alan E. Davis
2009-07-04 18:21 ` [gentoo-user] " Mark Shields
2009-07-05 2:22 ` Alan E. Davis
-- strict thread matches above, loose matches on Subject: below --
2009-07-06 12:42 [gentoo-user] " Roland Puntaier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7bef1f890907030848o4683fb32r9b9cfc1142cc21d3@mail.gmail.com \
--to=lngndvs@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox