All of lore.kernel.org
 help / color / mirror / Atom feed
From: Francesco Poli <frx@firenze.linux.it>
To: cpufreq@www.linux.org.uk
Subject: Re: Acer Aspire 1300 buggy BIOS - hardcoded patch
Date: Tue, 1 Jul 2003 00:59:46 +0200	[thread overview]
Message-ID: <20030701005946.5e659273.frx@firenze.linux.it> (raw)
In-Reply-To: <200306301436.29188.lbelli@crema.unimi.it>

On Mon, 30 Jun 2003 14:36:29 +0200 Luigi Belli wrote:

> I'm one of the owners of an Acer Aspire 1300 series with a buggy BIOS,
> so I decided to hardcode a patch with the correct PST table for my
> mobile Athlon XP 1800+.

BTW, I have just installed a 2.4.21 + cpufreq patch 3 kernel on an Acer
Aspire 1302XV (AMD Mobile Athlon XP 1600+. It seems to work (the back
fan has stopped spinning so often and the case temperature looks lower).

Does anybody know a simple method to check if the BIOS is buggy or not?
Can I run some quick diagnostics?

-- 
    Francesco Poli       <frx AT firenze.linux.it>
======================================================
You're compiling a program and, all of a sudden, boom!
  -- from APT HOWTO, version 1.8.0

  parent reply	other threads:[~2003-06-30 22:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-30 12:36 Acer Aspire 1300 buggy BIOS - hardcoded patch Luigi Belli
2003-06-30 15:14 ` Ducrot Bruno
2003-07-01 10:51   ` Ducrot Bruno
2003-07-04 17:04     ` Ducrot Bruno
2003-06-30 19:14 ` Stefan Gehn
2003-06-30 22:59 ` Francesco Poli [this message]
2003-06-30 23:20   ` Luigi Belli
2003-07-01 21:43     ` Francesco Poli
2003-07-01 10:12   ` Morrowind
  -- strict thread matches above, loose matches on Subject: below --
2003-07-01  0:44 Alex Young
2003-07-01  5:34 ` Adachi, Kenichi
2003-07-01 12:24 davidendless
2003-07-01 13:34 ` Luigi Belli
2003-07-01 14:20   ` Stefan Hoppe

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=20030701005946.5e659273.frx@firenze.linux.it \
    --to=frx@firenze.linux.it \
    --cc=cpufreq@www.linux.org.uk \
    /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.