From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.29.1: kernel/console beep no longer available, audio problems too
Date: Sun, 5 Apr 2009 08:55:27 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.00.0904050852240.22989@p34.internal.lan> (raw)
In-Reply-To: <alpine.DEB.2.00.0904050756050.20631@p34.internal.lan>
On Sun, 5 Apr 2009, Justin Piszcz wrote:
> Hello,
>
> After upgrading from 2.6.28.2, I noticed 2.6.29.1 (the config option moved
> around too for the PC-speaker) that the audio for my sound card does not
> start working for 1-2 minutes after trying to play various sounds.
> Eventually, it starts to work, but the PC speaker no longer functions.
>
> http://home.comcast.net/~jpiszcz/20090405/2.6.29.1-cfg.txt
> http://home.comcast.net/~jpiszcz/20090405/2.6.28.2-cfg.txt
>
> Is this a kernel/configuration issue or a bug since it appears the audio
> hw/configuration has been re-worked?
>
> Justin.
>
Pardon the noise:
2009-04-05 06:05:39 configure xterm 242-1 242-1
2009-04-05 06:05:39 status unpacked xterm 242-1
2009-04-05 06:05:39 status unpacked xterm 242-1
2009-04-05 06:05:39 status unpacked xterm 242-1
2009-04-05 06:05:39 status unpacked xterm 242-1
2009-04-05 06:05:39 status unpacked xterm 242-1
2009-04-05 06:05:39 status half-configured xterm 242-1
2009-04-05 06:05:40 status installed xterm 242-1
The problem is the new xterm in debian testing, it has a bug, reporting it
now, all seems good so far with 2.6.29.1.
(going back to xterm 235_2 fixes the beep problem):
http://debian.oregonstate.edu/debian/pool/main/x/xterm/xterm_235-2_i386.deb
Justin.
prev parent reply other threads:[~2009-04-05 12:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-05 11:59 Justin Piszcz
2009-04-05 12:55 ` Justin Piszcz [this message]
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=alpine.DEB.2.00.0904050852240.22989@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®