From: Michel Dänzer <michdaen@iiic.ethz.ch>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Stefan Jeglinski <jeglin@4pi.com>, linuxppc-dev@lists.linuxppc.org
Subject: Re: continuing XF402 (atimisc) problems
Date: Wed, 31 Jan 2001 19:05:10 +0100 [thread overview]
Message-ID: <3A7853D6.5AE4CC71@iiic.ethz.ch> (raw)
In-Reply-To: 19341226073701.30276@mailhost.mipsys.com
Benjamin Herrenschmidt wrote:
>
> >I've been over this on the -user list and the YDL list, and cc-ed Ani
> >a few times with it (no response). No one seems to have a clue as to
> >the cause of the problem, which is described concisely at:
> >
> ><http://lists.linuxppc.org/listarcs/linuxppc-user/200101/msg00672.html>
> >
> >(more detail available if necessary)
> >
> >This is on a 6500 (on-board RageII) with a RagePro PCI card. I have
> >tried rolling my own XF402 build, with Ani's driver updates, and get
> >the exact same XFree log result. I've also tried several of kfukui's
> >402 rpms, including use of his "old drivers," again with exactly the
> >same result.
>
> Check that you have the correct fbdevhw module and that it's loaded in
> your XF86Config file.
The atimisc driver should load fbdevhw if it needs it. Look at the r128 or
glint, ... drivers on how to do it.
Anyway, this whole fbdevhw mess will hopefully soon go away for a clean
solution.
--
Earthling Michel Dänzer (MrCooper) \ Debian GNU/Linux (powerpc) developer
CS student, Free Software enthusiast \ XFree86 and DRI project member
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-01-31 18:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-31 7:04 continuing XF402 (atimisc) problems Stefan Jeglinski
2001-01-31 14:05 ` Benjamin Herrenschmidt
2001-01-31 18:05 ` Michel Dänzer [this message]
2001-02-01 5:41 ` Stefan Jeglinski
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=3A7853D6.5AE4CC71@iiic.ethz.ch \
--to=michdaen@iiic.ethz.ch \
--cc=benh@kernel.crashing.org \
--cc=jeglin@4pi.com \
--cc=linuxppc-dev@lists.linuxppc.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).