From: Craig Schlenter <craig@webtelecoms.co.za>
To: Ben Pfaff <pfaffben@msu.edu>
Cc: Jani Monoses <jani@virtualro.ic.ro>, linux-kernel@vger.kernel.org
Subject: Re: Rage Mobility P/M
Date: Thu, 19 Apr 2001 08:40:05 +0200 [thread overview]
Message-ID: <20010419084005.B8937@webtelecoms.co.za> (raw)
In-Reply-To: <Pine.LNX.4.10.10104182114340.1604-100000@virtualro.ic.ro> <874rvmrraa.fsf@pfaffben.user.msu.edu>
In-Reply-To: <874rvmrraa.fsf@pfaffben.user.msu.edu>
On Wed, Apr 18, 2001 at 02:34:05PM -0400, Ben Pfaff wrote:
> Jani Monoses <jani@virtualro.ic.ro> writes:
>
> > does the atyfb or aty128fb support this chip?
> > Device id of 4c4d.
> > Using 2.4.3-ac7.
>
> I have a Rage Mobility with the same device ID on my laptop
> (Compaq Armada M700) but haven't been able to get it working with
> framebuffer. At any rate, atyfb is the proper one to use. Let
> me know if you get it working, I'd like to use it too.
Tried a late model ac kernel and 2.4.4pre3. The ac kernel seems to
have a somewhat re-organised atyfb driver. Both fail dismally - I
see 'flashes' on the screen when typing stuff but the screen is
essentially blank. vesafb worked for the minute or two during which
I tested it but I couldn't get x running on top of the framebuffer
so I've gone back to normal vga console stuff and using a ati X
driver. Interestingly, the atyfb driver reported my card as 'PCI'
instead of AGP. Device ID is 4c4d. Machine is a Dell latitude CPt S600Gt.
I'd be keen to hear if anyone gets it working ...
--Craig
prev parent reply other threads:[~2001-04-19 6:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-18 18:17 Rage Mobility P/M Jani Monoses
2001-04-18 18:34 ` Ben Pfaff
2001-04-18 18:38 ` Jani Monoses
2001-04-19 6:40 ` Craig Schlenter [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=20010419084005.B8937@webtelecoms.co.za \
--to=craig@webtelecoms.co.za \
--cc=jani@virtualro.ic.ro \
--cc=linux-kernel@vger.kernel.org \
--cc=pfaffben@msu.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.