From: Bruno Ducrot <ducrot@poupinou.org>
To: jy <jy454@yahoo.fr>
Cc: cpufreq@www.linux.org.uk
Subject: Re: Acer Aspire 1350 broken PST
Date: Fri, 16 Apr 2004 20:20:13 +0200 [thread overview]
Message-ID: <20040416182013.GZ8953@poupinou.org> (raw)
In-Reply-To: <c5p3e0$6js$1@sea.gmane.org>
On Fri, Apr 16, 2004 at 06:59:43PM +0200, jy wrote:
> Bruno Ducrot wrote:
> >On Fri, Apr 16, 2004 at 05:19:56PM +0200, jy wrote:
> >
> >Ok. I expected that BIOS will put the frequency at max at POST stage.
> >That is not true for your laptop indeed. Can you try that patch:
>
> Yes, when I bought the laptop the speed was always 800Mhz without any
> powernow driver in windows. Maybe the bios here is useful :
> ftp://ftp.support.acer-euro.com/notebook/aspire_1350/bios/zp13a18.zip
> the changelog in the zip talks about a low speed patch
I don't know if that bios will help you. Latest bios for Acer Aspire
1310 do give weird result both with PSB/PST method and ACPI (ACPI is
less buggy)..
See http://bugme.osdl.org/show_bug.cgi?id=2025
> with the patch :
>
> Linux version 2.6.5 (root@jy-portable) (version gcc 3.3.3 (Debian
> 20040401)) #1 SMP Fri Apr 16 18:00:18 CEST 2004
^^^
> powernow: PowerNOW! Technology present. Can scale: frequency and voltage.
> powernow: FSB: 132.755 MHz
> powernow: Found PSB header at c00f06f0
> powernow: Table version: 0x12
> powernow: Flags: 0x0 (Mobile voltage regulator)
> powernow: Settling Time: 100 microseconds.
> powernow: Has 8 PST tables. (Only dumping ones relevant to this CPU).
> powernow: No PST tables match this cpuid (0x7a0)
> powernow: This is indicative of a broken BIOS.
> powernow: Trying ACPI perflib
> powernow: acpi: P0: 2200 MHz 75000 mW 125 uS control 00d058fb SGTC 13334
> powernow: FID: 0x1b (16.5x [2190MHz]) VID: 0x7 (1.650V)
> powernow: acpi: P1: 1800 MHz 55000 mW 125 uS control 00d05935 SGTC 13334
> powernow: FID: 0x15 (13.5x [1792MHz]) VID: 0x9 (1.550V)
> powernow: acpi: P2: 1467 MHz 32000 mW 125 uS control 00d059c0 SGTC 13334
> powernow: FID: 0x0 (11.0x [1460MHz]) VID: 0xe (1.300V)
> powernow: acpi: P3: 1064 MHz 30000 mW 125 uS control 00d059ca SGTC 13334
> powernow: FID: 0xa (8.0x [1062MHz]) VID: 0xe (1.300V)
> powernow: acpi: P4: 800 MHz 26000 mW 125 uS control 00d059c6 SGTC 13334
> powernow: FID: 0x6 (6.0x [796MHz]) VID: 0xe (1.300V)
> powernow: Minimum speed 796 MHz. Maximum speed 2190 MHz.
> Losing too many ticks!
> TSC cannot be used as a timesource. <4>Possible reasons for this are:
> You're running with Speedstep,
> You don't have DMA enabled for your hard disk (see hdparm),
> Incorrect TSC synchronization on an SMP system (see dmesg).
> Falling back to a sane timesource now.
Try with UP kernel. At that time, cpufreq break TSC timer on SMP
kernels. Or alternatively use the ACPI-timer.
Cheers,
--
Bruno Ducrot
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
next prev parent reply other threads:[~2004-04-16 18:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-15 22:00 Acer Aspire 1350 broken PST jy
2004-04-16 12:05 ` Bruno Ducrot
2004-04-16 15:00 ` jy
2004-04-16 15:11 ` Bruno Ducrot
2004-04-16 15:19 ` jy
2004-04-16 15:24 ` Bruno Ducrot
2004-04-16 16:59 ` jy
2004-04-16 18:20 ` Bruno Ducrot [this message]
2004-04-16 21:27 ` jy
2004-04-17 9:32 ` Dominik Brodowski
2004-04-17 13:00 ` Bruno Ducrot
2004-04-17 16:58 ` Dominik Brodowski
2004-04-19 9:26 ` Bruno Ducrot
2004-04-19 11:54 ` Dominik Brodowski
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=20040416182013.GZ8953@poupinou.org \
--to=ducrot@poupinou.org \
--cc=cpufreq@www.linux.org.uk \
--cc=jy454@yahoo.fr \
/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