From: Daniel Robbins <drobbins@gentoo.org>
To: gentoo-user@gentoo.org
Cc: gentoo-dev@chiba.3jane.net
Subject: [gentoo-dev] Re: [gentoo-user] Don't use Athlon/Duron/K7 kernels!
Date: Sat, 22 Dec 2001 00:03:35 -0600 [thread overview]
Message-ID: <20011222000335.A9376@chiba.3jane.net> (raw)
In-Reply-To: <1008967696.4194.0.camel@Q.neidt.net>
On Fri, Dec 21, 2001 at 08:48:14PM +0000, Tod M. Neidt wrote:
> Ahhh!
>
> I have been bangin my head against the wall trying to figure out what
> was going on. I didn't encounter any major problems, but whenever I
> would logout out of gnome my console fonts would be all garbled. ( I
> didn't have this problem on my PII at work, only the Athlon at home)
> Recompiling the kernel as PPro fixes the problem. I was looking in the
> wrong places for this one.
Can you test something for me? I have a new binutils-2.11.90.0.31 ebuild ready
for testing. I used it here and recompiled my kernel with "Athlon/Duron/K7"
set and nvidia along with nvagp worked fine. Here's what I'd like you to try.
emerge =sys-devel/binutils-2.11.90.0.31
cd /usr/src/linux
cp .config /tmp
make clean
cp /tmp/.config .
(configure kernel for Athlon/Duron/K7)
make dep && make bzImage && make modules && make modules_install
(install kernel for booting)
(reboot)
(remerge media-gfx/nvidia if you are using the nvidia driver)
start GNOME
..And then see if you *still* have those problems. It's possible that the new
binutils resolves them.
Best Regards,
--
Daniel Robbins <drobbins@gentoo.org>
Chief Architect/President http://www.gentoo.org
Gentoo Technologies, Inc.
prev parent reply other threads:[~2001-12-22 6:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-22 1:27 [gentoo-dev] Don't use Athlon/Duron/K7 kernels! Daniel Robbins
[not found] ` <1008967696.4194.0.camel@Q.neidt.net>
2001-12-22 6:03 ` Daniel Robbins [this message]
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=20011222000335.A9376@chiba.3jane.net \
--to=drobbins@gentoo.org \
--cc=gentoo-dev@chiba.3jane.net \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-user@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