From: Christian Burger <christian.burger@edb.ericsson.se>
To: linux-kernel@vger.kernel.org
Subject: Re: fonts corruption with 3dfx drm module
Date: Thu, 09 May 2002 14:47:22 +0300 [thread overview]
Message-ID: <3CDA61CA.498991DF@edb.ericsson.se> (raw)
I've seen a much more serious problem which seems to be related to this:
I have AMD Athlon K7 650MHz, Via chipset, Voodoo5 5500AGP, MTTR enabled.
What is happening here is that when switching back from init 5 to init 3 for
instance, the system hangs completely and a blinking character appears in a
black screen. There's no other way other than to power cycle the system. It
seems to be a kernel panic.
Kernel version is 2.4.18, and it happens with or without DRM support, with and
without FB support. There's no way I can have this version of the kernel to work
here.
Thanks,
Christian Burger
On Mon, Jan 28, 2002 at 04:12:34PM +0200, Zwane Mwaikambo wrote:
> On Mon, 28 Jan 2002, Zwane Mwaikambo wrote:
>
> > Do you guys have CONFIG_MTRR and/or CONFIG_FB_VESA enabled? Also which
> > motherboard chipset?
MTRR, of course (do you like 2D and even 3D hardware accelerated without
MTRR?), FB, no, chipset is a AMD 750 (Irongate C4), using X 4.1.99.1 DRI CVS.
I am with the DRI devel team and saw it occasionally with XFree86 DRI CVS
trunk and the latest mesa-4-0-branch. At that time I had FB enabled as I
remember right.
The current DRI stuff is "only" missing the latest XFree86 4.2.0 release 2D
code. Update is under way.
I can _NOT_ see it without FB and currently running
2.4.18-pre7-J6-VM-23-preempt-lock.
/home/nuetzel> cat /proc/mtrr
reg00: base=0x00000000 ( 0MB), size= 512MB: write-back, count=1
reg01: base=0x20000000 ( 512MB), size= 128MB: write-back, count=1
reg02: base=0xec103000 (3777MB), size= 4KB: write-combining, count=1
reg03: base=0xe0000000 (3584MB), size= 64MB: write-combining, count=2
Voodoo5 5500 AGP.
Regards,
Dieter
--
Dieter Nützel
Graduate Student, Computer Science
University of Hamburg
Department of Computer Science
@home: Dieter.Nuetzel@hamburg.de
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2002-05-09 17:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-09 11:47 Christian Burger [this message]
2002-05-09 20:35 ` fonts corruption with 3dfx drm module Jussi Laako
2002-05-10 6:28 ` Christian Burger
2002-05-09 21:07 ` Diego Calleja
-- strict thread matches above, loose matches on Subject: below --
2002-01-30 19:10 Marek Kassur
2002-01-30 19:56 ` Jurriaan on Alpha
[not found] <20020128203706.24AC0FB8D@netfinity.realnet.co.sz>
2002-01-30 10:14 ` Zwane Mwaikambo
2002-01-31 21:03 ` Diego Calleja
[not found] <20020129143209.2AE68FB85@netfinity.realnet.co.sz>
2002-01-29 14:40 ` Zwane Mwaikambo
[not found] <20020128182427.11F20FB8D@netfinity.realnet.co.sz>
2002-01-29 6:45 ` Zwane Mwaikambo
2002-01-29 14:32 ` Dieter Nützel
2002-01-28 16:39 Dieter Nützel
2002-01-28 14:11 Zwane Mwaikambo
2002-01-28 14:12 ` Zwane Mwaikambo
2002-01-28 15:56 ` Mark Zealey
2002-01-28 20:41 ` Diego Calleja
2002-01-28 21:31 ` Chris Meadors
2002-01-27 11:36 Diego Calleja
2002-01-27 12:25 ` Mark Zealey
2002-01-27 13:00 ` Daniel J Blueman
2002-01-27 13:33 ` Mark Zealey
2002-01-27 14:35 ` thunder7
2002-01-27 17:35 ` Diego Calleja
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=3CDA61CA.498991DF@edb.ericsson.se \
--to=christian.burger@edb.ericsson.se \
--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