From: Batmensch <hcaley@loomer.com>
To: "G. Laurès" <laures@hp1.esiea.fr>
Cc: "Dev @ LinuXppc" <linuxppc-dev@lists.linuxppc.org>
Subject: Re: PBG3Series and pre-R5:a lot further
Date: Tue, 09 Mar 1999 07:49:35 -0500 (EST) [thread overview]
Message-ID: <XFMail.990309074935.hcaley@loomer.com> (raw)
In-Reply-To: <36E4E107.9C0DC589@mail.esiea.fr>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 1857 bytes --]
Doesn't work; I get the "psychedelic death screen". Strangely, if I set the
mclk to 43, the display is still messed up but I can hear the machine continue
to boot.
I don't think I've heard of anyone using atyfb successfully on a 300mhz PB G3
Series.
Hugh
On 09-Mar-99 G. Laurès wrote:
>
>
> Batmensch a *crit :
>>
>> I tried this XF86Config on my PB G3 Series, and although it starts up, it is
>> still running in Open Firmware (non-accelerated mode).
> Does the XFBDev out specifies it's using the ATY Rage PRO device, with
> acceleration enabled ?
>
> If not, try video=atyfb:vmode:14,cmode:8,mclk:83 as a kernel argument,
> with unchecked "no video driver" box.
>
> If you not see atyfb;ATY RageLT PRO in the boot sequence (and later in
> /var/log/dmesg) then there is a problem.
> If you do see it, then XFBDev should report it's using the ATY chip, in
> acccelerated mode and things should go... lightning.
>
>>
>> Did you try running fbset -i while the Xserver is up?
> I don't have fbset unfortunately, I think I have to grab it from G.U.
> site, yeah ?
>
>>
>> I could be wrong, but it seems to me I remember reading somewhere that you
>> can't run XF68_FBDev in accelerated mode when the console is running Ofb.
> Sure.
>
>>
>> Xpmac is much faster than Ofb; try moving an open window around.
> I wasn't able to make some use of Xpmac
>
>
> --
> GoM
----------------------------------
E-Mail: Batmensch <hcaley@loomer.com>
Date: 09-Mar-99
Time: 07:47:47
This message was sent by XFMail
----------------------------------
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-03-09 12:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199903080559.XAA25812@lists.linuxppc.org>
1999-03-08 12:58 ` PBG3Series and pre-R5:a lot further Batmensch
1999-03-09 8:51 ` G. Laurès
1999-03-09 12:49 ` Batmensch [this message]
[not found] <XFMail.990307023826.hcaley@loomer.com>
1999-03-07 15:38 ` PBG3Series and pre-R5: a little bit further G. Laurès
1999-03-07 22:17 ` PBG3Series and pre-R5: a lot further G. Laurès
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=XFMail.990309074935.hcaley@loomer.com \
--to=hcaley@loomer.com \
--cc=laures@hp1.esiea.fr \
--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).