LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Sawatzky <brad+linuxppc@lamorak.phys.virginia.edu>
To: linuxppc-dev@lists.linuxppc.org
Subject: Mach64-GX using fbdev problem
Date: Mon, 3 Feb 2003 14:01:43 -0500	[thread overview]
Message-ID: <20030203190143.GB20673@lamorak.phys.virginia.edu> (raw)


Hi all,

If anyone has managed to get this card to work I would appreciate an email
with the relevant ModeLine and/or kernel arguments.  I would like to get
this thing to run in at least 800x600x24.  A configuration for 1024x768x16
would also be nice.

I have gotten to the stage where I can see a mangled X screen (ie. the kind
of thing you see when you are using a bogus mode for the monitor).  I have
tried quite few different (stock) resolution/depth combos as well as
explicitly defining some reasonable looking ModeLines taken from successful
'fbset -x' commands.  The monitor (NEC XV17" CRT) works fine at all of the
refresh rates, geometries and depths under OSX.  (Is there a tool
comparable to 'fbset -i' in OSX?)  I've also tested with my 21" Apple CRT
without success so I don't think the problem is monitor related.

Some relevant info:
  Blue&White G3, kernel 2.4.20-ben1

  XFree86 Version 4.2.1.1 (Debian 4.2.1-5 20030121181741 branden@debian.org)/ X Window System
  (protocol Version 11, revision 0, vendor release 6600)
  Release Date: 18 October 2002

>From lspci:
  01:03.0 VGA compatible controller: ATI Technologies Inc 210888GX [Mach64 GX] (rev 03)

>From /proc/fb:
  0 ATY Rage128
  1 ATY Mach64

>From 'fbset -fb /dev/fb1 -i' (right after a reboot, X hasn't fired up)
Frame buffer device information:
    Name        : ATY Mach64
    Address     : 0x81800000
    Size        : 1048576
    Type        : PACKED PIXELS
    Visual      : PSEUDOCOLOR
    XPanStep    : 8
    YPanStep    : 1
    YWrapStep   : 0
    LineLength  : 640
    MMIO Address: 0x817ffc00
    MMIO Size   : 1024
    Accelerator : ATI Mach64GX

>From XF86Config
Section "Device"
        Identifier      "Mach64-GX"
        Driver          "fbdev"
        BusID           "PCI:1:3:0"
        Option          "UseFBDev"              "true"
        Option          "fbdev"                 "/dev/fb1"
EndSection

--
Brad Sawatzky <bds9e@virginia.edu>
University of Virginia Physics Department
Ph: (434) 924-6580    Fax: (434) 924-4576

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2003-02-03 19:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-03 19:01 Brad Sawatzky [this message]
2003-02-03 19:14 ` Mach64-GX using fbdev problem Kevin B. Hendricks
2003-02-03 20:11 ` vinai

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=20030203190143.GB20673@lamorak.phys.virginia.edu \
    --to=brad+linuxppc@lamorak.phys.virginia.edu \
    --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