From: backblue <backblue@netcabo.pt>
To: Craig Bradney <cbradney@zip.com.au>, linux-kernel@vger.kernel.org
Subject: Re: a7n8x-x & i2c
Date: Thu, 11 Mar 2004 20:04:00 +0000 [thread overview]
Message-ID: <20040311200400.37337424.backblue@netcabo.pt> (raw)
In-Reply-To: <1078953283.8828.24.camel@athlonxp.bradney.info>
If i run sensors-detect, it doesn't detect any chips, does a7n8x-x should work?
On Wed, 10 Mar 2004 22:14:43 +0100
Craig Bradney <cbradney@zip.com.au> wrote:
> Ok, thought you might have had the nForce2 bug issue as well. Perhaps
> you haave already patched for that.
>
> Craig
>
> On Wed, 2004-03-10 at 20:56, backblue wrote:
> > It only crashes with i2c, the kernel it's working nicelly, at the moment, but without i2c, if i compile it with i2c build in, it crashes.
> >
> > On Wed, 10 Mar 2004 20:05:00 +0100
> > Craig Bradney <cbradney@zip.com.au> wrote:
> >
> > > Hi,
> > >
> > > > I have compiled 2.6.3, with i2c suporte for my chipset "nforce2" to the board asus a7n8x-x, but, it crashes my box all the time, dont know why!
> > > > But it only crashes after login and a couple of minutes working...
> > > > any one know womething about this?
> > >
> > > Is the crash only with i2c or are you just trying linux on this board?
> > >
> > > Craig
> > >
> > -
> > 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/
> >
>
next prev parent reply other threads:[~2004-03-11 20:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-10 18:50 a7n8x-x & i2c backblue
2004-03-10 19:05 ` Craig Bradney
2004-03-10 19:56 ` backblue
2004-03-10 21:14 ` Craig Bradney
2004-03-11 20:04 ` backblue [this message]
2004-03-12 0:31 ` Greg KH
2004-03-12 20:00 ` backblue
2004-03-12 21:05 ` Greg KH
2004-03-12 22:23 ` Craig Bradney
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=20040311200400.37337424.backblue@netcabo.pt \
--to=backblue@netcabo.pt \
--cc=cbradney@zip.com.au \
--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