public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andreas Karlsson <hermes@home.se>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] AMD X2 timings
Date: Thu, 20 Oct 2005 22:36:54 +0200	[thread overview]
Message-ID: <200510202236.56336.hermes@home.se> (raw)

[-- Attachment #1: Type: text/plain, Size: 1343 bytes --]

Hi,

After comming to termis with various  make.conf issues after upgrading CPU to 
K8 I now find myself struggeling with another problem, or rather two. First I 
found this http://bugzilla.kernel.org/show_bug.cgi?id=5105. It seems that a 
timing issue with TSC timings in the kernel makes the the kernel clock lose 
sync (or something like that). According to the changelog for 2.6.13-r4 
( http://www.gentoo.org/cgi-bin/viewcvs.cgi/*checkout*/sys-kernel/gentoo-sources/ChangeLoghttp://www.gentoo.org/cgi-bin/viewcvs.cgi/*checkout*/sys-kernel/gentoo-sources/ChangeLog) 
this bug is fixed, but I still have problems with the keyboard repeating 
keystrokes, like thiiiiiiiiiiiiiiiiiiiiiiiiiiis (just pressing ´i´ once), 
after upgrading to 2.6.13-r4.
A suggested fix is to pass 'notsc' to the kernel at boottime. I tried this, 
but can´t disable TSC when compiling the kernel. I tried to change 
CONFIG_X86_TSC=y to CONFIG_X86_TSC=n, but when starting the make-process, it 
is changed back to CONFIG_X86_TSC=y automaticly. What am I doing wrong?

Second I have an overall impression that X is slower than before. It doesn´t 
feel as "snappy" as it used to with my old AMD Athlon XP 3200+. Theoretilcy 
it should run faster, right?

Any inputs on the issues would be most welcome.

Best regards,
Andreas Karlsson
Sweden

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

                 reply	other threads:[~2005-10-20 20:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200510202236.56336.hermes@home.se \
    --to=hermes@home.se \
    --cc=gentoo-user@lists.gentoo.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