public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: dth@ncc1701.cistron.net (Danny ter Haar)
To: linux-kernel@vger.kernel.org
Subject: Re: [ACPI] Where do I send APIC victims?
Date: Wed, 3 Sep 2003 10:30:49 +0000 (UTC)	[thread overview]
Message-ID: <bj4fsp$9j4$1@news.cistron.nl> (raw)
In-Reply-To: 20030903093808.GA28594@k3.hellgate.ch

Roger Luethi  <rl@hellgate.ch> wrote:
>> Are these VIA KT333/KT400 chipsets? If so, there's a known bug in many BIOSes 
>Yes, at least some of them are. I often don't know, since the reports just
>say "Rhine ethernet broke in the new kernel" (VIA based boards typically
>come with Rhine ethernet integrated into the south bridge).

I posted that i use a mini-itx VIA C3 with integrated via-rhine.
Only difference is the CPU speed (533/800/1000 Mhz) i believe.

Danny

-- 
I think so Brain, but why does a forklift 
have to be so big if all it does is lift forks?


  reply	other threads:[~2003-09-03 10:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-03  8:08 Where do I send APIC victims? Roger Luethi
2003-09-03 10:23 ` [ACPI] " Andrew de Quincey
2003-09-03 10:23 ` Andrew de Quincey
2003-09-03  9:38   ` Roger Luethi
2003-09-03 10:30     ` Danny ter Haar [this message]
2003-09-03 10:48     ` Andrew de Quincey
2003-09-03 11:40       ` Alan Cox
2003-09-03 12:53         ` Stephan von Krawczynski
2003-09-03 13:04           ` Vladimir Lazarenko
2003-09-03 14:14             ` Stefan Smietanowski
2003-09-03 16:10               ` Andrew de Quincey
2003-09-03 16:09             ` Andrew de Quincey
2003-09-04  0:28               ` Mike Fedyk
2003-09-03 18:13         ` Marcelo Tosatti
2003-09-03 18:15           ` Marcelo Tosatti
2003-09-03 22:44           ` Sérgio Monteiro Basto
2003-09-03 11:05   ` Matthias Andree
  -- strict thread matches above, loose matches on Subject: below --
2003-09-03 11:18 Nicolas Mailhot

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='bj4fsp$9j4$1@news.cistron.nl' \
    --to=dth@ncc1701.cistron.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