public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: Andreas Haumer <andreas@xss.co.at>
Cc: andrew@walrond.org, linux-kernel@vger.kernel.org
Subject: Re: ACPI: problem on ASUS PR-DLS533
Date: Wed, 7 Jan 2004 11:37:51 +0100	[thread overview]
Message-ID: <20040107113751.1da9b288.skraw@ithnet.com> (raw)
In-Reply-To: <3FE85D67.1010707@xss.co.at>

On Tue, 23 Dec 2003 16:21:11 +0100
Andreas Haumer <andreas@xss.co.at> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi!
> 
> Andrew Walrond wrote:
> > On Tuesday 23 Dec 2003 12:04 pm, Andreas Haumer wrote:
> >
> >>Hi!
> >>
> >>There are some ACPI-related problems w/ an ASUS PR-DLS5333
> >>Dual Xeon motherboard. I already reported this back in June
> >>for Linux-2.4.21-ac and since then I've tested several kernel
> >
> >
> > See http://bugme.osdl.org/show_bug.cgi?id=1662
> >
> > Len and co are working through the list, one bug at a time, so hopefully
> > they'll get to this soonish. I've also notified Asus about their bogus
> > bios, but little response so far :(
> >
> Thanks for the info. Your problem looks quite similar,
> but not completely identical. It's a different board,
> mine (the PR-DLS533) is the 533MHz FSB version of yours
> (the PR-DLS), I think.
> 
> Anyway, I'll try to add as much info as I can get
> to your bugzilla entry.

You are not alone ;-)

I have some TRL-DLS here (P-III). They have dual AIC onboard which are not
recognised under 2.4.24 but work flawlessly with ACPI in 2.4.23.

Regards,
Stephan

  reply	other threads:[~2004-01-07 10:38 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-23 12:04 ACPI: problem on ASUS PR-DLS533 Andreas Haumer
2003-12-23 14:48 ` Andrew Walrond
2003-12-23 15:21   ` Andreas Haumer
2004-01-07 10:37     ` Stephan von Krawczynski [this message]
2004-01-07 14:30       ` Andrew Walrond
  -- strict thread matches above, loose matches on Subject: below --
2004-01-07 10:50 Yu, Luming
2004-01-07 12:35 ` Stephan von Krawczynski
2004-01-07 22:58   ` Marcelo Tosatti
2004-01-12  5:14 Yu, Luming
2004-01-15 18:14 ` Andrew Walrond
2004-01-16 10:30   ` Marcelo Tosatti
2004-01-16 11:25     ` Stephan von Krawczynski
2004-01-16 13:14       ` Andreas Haumer
2004-01-16 13:22         ` Stephan von Krawczynski
2004-01-16 12:07     ` Andrew Walrond
2004-01-18  4:18 Yu, Luming
2004-01-18  9:01 ` Andrew Walrond
2004-01-18  4:23 Yu, Luming
2004-01-18 11:42 ` Andreas Haumer
2004-01-18 16:01   ` Andrew Walrond
2004-01-18 17:00     ` Stephan von Krawczynski
     [not found] <BF1FE1855350A0479097B3A0D2A80EE0020ADE84@hdsmsx402.hd.intel.com>
2004-01-18 18:19 ` Len Brown

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=20040107113751.1da9b288.skraw@ithnet.com \
    --to=skraw@ithnet.com \
    --cc=andreas@xss.co.at \
    --cc=andrew@walrond.org \
    --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