From: Sean Middleditch <elanthis@awesomeplay.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Via onboard audio
Date: 03 Nov 2001 11:21:33 -0500 [thread overview]
Message-ID: <1004804493.8567.7.camel@stargrazer> (raw)
In-Reply-To: <1004723462.4883.12.camel@smiddle>
In-Reply-To: <E15zh4S-0002oT-00@the-village.bc.nu> <1004723462.4883.12.camel@smiddle>
Hmm, OK, I downloaded 2.4.13-0.3 RPMs from Rawhide (ya, I'm a wuss, oh
well) and it didn't like my laptop at all.
Sound did work somewhat better... XMMS didn't skip and freeze, and
cat'ing a wav to /dev/dsp didn't finish immediately (looked like it was
taking time to play, actually), but I still heard no sound. I *did*
check the mixer, and all the relevant devices are right on up there.
HOwever, 2.4.13 started freaking on me. My project I was working on
ceased to compile (gcc kept crashing, which it didn't do on 2.4.12), and
when I shut down the machine to reboot into 2.4.12, I saw a bunch of
kernel oops error message, the first of which was the VM, which had
decided to kill "sh".
In any event, I have no clue how to debug a kernel properly properly, so
I don't know what more to say. Perhaps someone can give me some
pointers? Or this is a known issue that has aready been rectified?
BTW, I won't be on the list much longer, the traffic is killer. ~,^ So
please make sure CC's or whatnot have me in them.
Thanks,
Sean Etc.
On Fri, 2001-11-02 at 12:51, Sean Middleditch wrote:
> OK, will do that. RedHat uses your kernel trees, right? I'll download
> new RPM's from rawhide if they're there (I'm in no hurry.)
>
> Thanks!
> Sean Etc.
>
> On Fri, 2001-11-02 at 11:21, Alan Cox wrote:
> > Try the current 2.4.13-ac ones - there are some via audio updates there
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-11-03 16:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-02 16:01 Via onboard audio Sean Middleditch
2001-11-02 16:14 ` Jeff Garzik
2001-11-02 17:52 ` Sean Middleditch
2001-11-02 17:55 ` Jeff Garzik
2001-11-02 16:21 ` Alan Cox
2001-11-02 17:51 ` Sean Middleditch
2001-11-02 18:06 ` Alan Cox
2001-11-02 18:03 ` Sean Middleditch
2001-11-02 18:51 ` David Weinehall
2001-11-03 16:21 ` Sean Middleditch [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=1004804493.8567.7.camel@stargrazer \
--to=elanthis@awesomeplay.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