All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Walrond <andrew@walrond.org>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: ATI Rage XL on x86_64
Date: Thu, 27 Jan 2005 14:54:03 +0000	[thread overview]
Message-ID: <200501271454.03706.andrew@walrond.org> (raw)
In-Reply-To: <200501261209.46735.andrew@walrond.org>

[-- Attachment #1: Type: text/plain, Size: 1006 bytes --]

On Wednesday 26 January 2005 12:09, Andrew Walrond wrote:
>
> When I try video=atyfb:1024x768-8@60, I get even less output:
>
>  atyfb: using auxiliary register aperture
>  atyfb: 3D RAGE XL (Mach64 GR, PCI-33MHz) [0x4752 rev 0x27]
>  atyfb: 8M SDRAM (2:1) (32-bit) 29.498928 MHz XTAL, 230MHz PLL, 83 MHz MCLK
> 63MHz XCLK
>  atyfb: fb0: ATY Mach64 frame buffer device on PCI
>
> In all cases, the screen blanks for a moment during boot, then reppears in
> original 80x25 format.

FYI I have resolved this issue.

I had CONFIG_FRAMEBUFFER_CONSOLE=m

in the kernel config. I think the frambuffer code was working fine (explaining 
the screen blanking during boot), but then the console subsystem 
reconfiguring the display back to text mode.

Changing to CONFIG_FRAMEBUFFER_CONSOLE=y fixed this.

This is obviously a 'gotcha' to remember for the future, but perhaps also a 
candidate for further thought, since all subsequent use of the fb device (for 
graphics) produced a corrupt display.

Andrew Walrond

[-- Attachment #2: Type: text/html, Size: 1343 bytes --]

      reply	other threads:[~2005-01-27 14:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-26  9:10 ATI Rage XL on x86_64 Andrew Walrond
2005-01-26  9:39 ` Andrew Walrond
2005-01-26 10:54   ` Ville Syrjälä
2005-01-26 12:09     ` Andrew Walrond
2005-01-27 14:54       ` Andrew Walrond [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=200501271454.03706.andrew@walrond.org \
    --to=andrew@walrond.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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.