linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jurgen Kramer <gtm.kramer@inter.nl.net>
To: Alan Cox <alan@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.22-ac1 - VIA C3 cpufreq probs
Date: Fri, 29 Aug 2003 21:25:34 +0200	[thread overview]
Message-ID: <1062185134.1488.9.camel@paragon.slim> (raw)
In-Reply-To: <200308291237.h7TCbYc12849@devserv.devel.redhat.com>

Hi,

I have just tried 2.4.22-ac1 on my VIA C3 EPIA 800 system. Cpufreq
(longhaul) fails both while compiled as a module and compiled in.

I first tried to build it as a module but somehow the module isn't build
at all. Next thing I tried was building it straight in the
kernel....with a direct oops when booting as a result.

The system doesn't have a keyboard or monitor..it did cost me some
fiddling to get it back up running...that's life for a tester...

There also seems to be some problem with the longhaul detection. Normaly
it would print something like:
longhaul: VIA CPU detected. Longhaul version 2 supported
longhaul: CPU currently at 798MHz (133 x 6.0)
longhaul: MinMult(x10)=30 MaxMult(x10)=60
longhaul: Lowestspeed=399000 Highestspeed=798000

But 2.4.22-ac1 printed MinMult and MaxMult to be 0.

Greetings,

Jurgen


  parent reply	other threads:[~2003-08-29 19:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-29 12:37 Linux 2.4.22-ac1 Alan Cox
2003-08-29 12:49 ` Bas Mevissen
2003-08-29 12:58   ` Alan Cox
2003-08-29 13:24     ` Bas Mevissen
2003-08-29 13:24       ` Alan Cox
2003-09-01 13:51         ` Bill Davidsen
2003-09-01 16:38           ` Alan Cox
2003-08-29 21:31       ` Erik Andersen
2003-08-30 17:14         ` Martin List-Petersen
2003-08-30 18:01           ` Erik Andersen
2003-08-29 18:15 ` Gerardo Exequiel Pozzi
2003-08-29 19:25 ` Jurgen Kramer [this message]
2003-08-30  0:51   ` Linux 2.4.22-ac1 - VIA C3 cpufreq probs Dave Jones
2003-08-30  9:02 ` Linux 2.4.22-ac1 Ralf Hildebrandt
2003-08-30  9:20   ` Martin List-Petersen
2003-08-30 14:59     ` Ralf Hildebrandt
2003-08-30  9:53   ` Willy Tarreau
2003-08-30 15:03     ` Ralf Hildebrandt
2003-08-30 15:36       ` Kurt Wall
2003-08-30 21:51   ` Ralf Hildebrandt

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=1062185134.1488.9.camel@paragon.slim \
    --to=gtm.kramer@inter.nl.net \
    --cc=alan@redhat.com \
    --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;
as well as URLs for NNTP newsgroup(s).