All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Petermair <black666@inode.at>
To: linux-kernel@vger.kernel.org
Subject: Re: Problem with via82cxxx and vt8235
Date: Sat, 30 Nov 2002 22:27:23 +0100	[thread overview]
Message-ID: <200211302227.23253.black666@inode.at> (raw)
In-Reply-To: <1038667380.17209.2.camel@irongate.swansea.linux.org.uk>

Alan Cox:
> On Sat, 2002-11-30 at 00:29, Patrick Petermair wrote:
> > Hi!
> >
> > I have a MSI KT3Ultra2 Motherboard with a VT8235 southbridge. I'm
> > currently running kernel 2.4.19 - unfortunately it doesn't detect the
> > southbridge, so I cannot enable dma.
> > I tried the patch from Vojtech Pavlik (via82cxxx), but then it hangs
> > at boot:
>
> Try the -ac tree firstly

Thanks Alan, now dma works perfect!
How come this code isn't in the official 2.4.20 kernel?

The only strange thing now is that uname doesn't know my cpu:

starbase:/# uname -a
Linux starbase 2.4.20-ac1 #1 Sam Nov 30 18:43:15 CET 2002 i686 unknown 
unknown GNU/Linux
starbase:/#

But it gets recognized during boot:

starbase:/# dmesg | grep -i AMD
CPU: AMD Athlon(tm) XP 2200+ stepping 00
starbase:/#

starbase:/# cat /proc/cpuinfo | grep -i AMD
vendor_id       : AuthenticAMD
model name      : AMD Athlon(tm) XP 2200+
starbase:/#


But hey, I can live with that - I have dma now :-)
Just curious, what's causing this.

Thanks so much...
Patrick





  reply	other threads:[~2002-11-30 21:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-30  0:29 Problem with via82cxxx and vt8235 Patrick Petermair
2002-11-30 14:43 ` Alan Cox
2002-11-30 21:27   ` Patrick Petermair [this message]
2002-11-30 21:36     ` Sean Neakums
2002-11-30 21:45       ` Patrick Petermair
2002-12-01  2:47     ` Alan Cox
2002-12-01 10:00       ` PDC20268 in current -ac [Re: Problem with via82cxxx and vt8235] Tomas Szepe

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=200211302227.23253.black666@inode.at \
    --to=black666@inode.at \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.