From: Martin Schlemmer <azarah@gentoo.org>
To: Andreas Haumer <andreas@xss.co.at>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: system clock speed too high?
Date: 04 Jun 2003 07:44:06 +0200 [thread overview]
Message-ID: <1054705445.5270.76.camel@workshop.saharacpt.lan> (raw)
In-Reply-To: <3EDCBF64.6060807@xss.co.at>
On Tue, 2003-06-03 at 17:31, Andreas Haumer wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Martin Schlemmer wrote:
> > On Tue, 2003-06-03 at 16:23, Andreas Haumer wrote:
> >
> >
> >>The "USB legacy support" settings slipped through when
> >>I was preparing the system. I was too much concentrated
> >>on the ACPI/Fusion MPT problems...
> >>
> >>But something must be wrong in this area, as the kernel prints
> >>this "..MP-BIOS bug: 8254 timer not connected to IO-APIC"
> >>message when USB legacy support is disabled.
> >>
> [...]
> >
> > What about contacting the manufacturer to fix the bios ?
> >
> It's on my TODO list, but I want to do some more tests first.
>
> The Asus AP1700-S5 does officially list Linux as supported OS,
> (and it's a really nice piece of server hardware, too), so they
> should be definitely interested in fixing this. It might be not
> so clear who's to blame for this problem, though.
>
I am assuming you have not tried another OS just to verify if
it is a linux only problem ?
> Is anyone from ASUSTeK Computers Inc. around here on this list?
>
I might know a email or two, but I do not know if I am allowed ....
If you can get more info (also maybe if its a linux only problem),
Drop me a mail ... maybe I can just forward it if you list all the
info.
Also ... have you tried to look if there is a BIOS update out yet?
Regards,
--
Martin Schlemmer
next prev parent reply other threads:[~2003-06-04 5:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-02 19:40 system clock speed too high? Andreas Haumer
2003-06-02 19:36 ` Alan Cox
2003-06-03 9:54 ` Andreas Haumer
2003-06-03 12:00 ` Andreas Haumer
2003-06-03 12:17 ` Zephaniah E. Hull
2003-06-03 12:39 ` Andreas Haumer
2003-06-03 13:00 ` Alan Cox
2003-06-03 14:23 ` Andreas Haumer
2003-06-03 14:49 ` Martin Schlemmer
2003-06-03 15:31 ` Andreas Haumer
2003-06-04 5:44 ` Martin Schlemmer [this message]
2003-06-04 8:49 ` Andreas Haumer
2003-06-03 15:17 ` venom
2003-06-03 15:38 ` Andreas Haumer
2003-06-03 15:43 ` venom
2003-06-03 15:47 ` Randy.Dunlap
2003-06-03 16:12 ` venom
2003-06-02 20:33 ` george anzinger
2003-06-03 10:04 ` Andreas Haumer
2003-06-03 19:12 ` system clock speed too high? hyperthread problem? george anzinger
2003-06-04 9:47 ` system clock speed too high? Herbert Xu
2003-06-04 13:02 ` Herbert Xu
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=1054705445.5270.76.camel@workshop.saharacpt.lan \
--to=azarah@gentoo.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andreas@xss.co.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox