From: backblue <backblue@netcabo.pt>
To: jeremy@rootservices.net, linux-kernel@vger.kernel.org
Subject: Re: nforce 2 chipset
Date: Thu, 11 Mar 2004 20:05:51 +0000 [thread overview]
Message-ID: <20040311200551.1eafb6fe.backblue@netcabo.pt> (raw)
In-Reply-To: <64805.24.50.227.119.1078963073.squirrel@24.50.227.119>
Please search about "nforce2" and "a7n8x-x" in the LKML before your ask, maybe someone allready have that problem!
On Wed, 10 Mar 2004 18:57:53 -0500 (EST)
"Jeremy D. May" <jeremy@rootservices.net> wrote:
> Not sure if this is the right place to go for this, but maybe someone
> could point me in the right direction.
>
> system:
>
> 2500+ Athlon XP (barton)
> NFource 2 Ultra 400 + MCP chipset (is a Shuttle AN35-Ultra400(latest bios
> flash))
> 1.5 gigs PC2700
> 40 Gig Maxtor HD
> 80 Gig Seagate HD
> CDRW
> DVD
> GF FX 5600XT
> SB Live 5.1Digital
>
>
> i installed debian and a fresh compile of 2.4.25, installed the backports
> collection for XF86/gnome2 and all my software i like. it goes fine for a
> bit. but then while playing any sound (mainly streaming mp3's and my own
> mp3's(in xmms)) the machine would lockup and i would have to reboot. i
> never had this problem in windows with the box so i was wondering if
> anyone had any incite into this.
>
> --jeremy
> -
> 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:[~2004-03-11 20:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-10 23:57 Jeremy D. May
2004-03-11 4:55 ` Niraj Kumar
2004-03-11 5:53 ` Jeremy D. May
2004-03-11 20:05 ` backblue [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=20040311200551.1eafb6fe.backblue@netcabo.pt \
--to=backblue@netcabo.pt \
--cc=jeremy@rootservices.net \
--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®