linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Kern <alex.kern@gmx.de>
To: leandro@inforagro.com.br
Cc: fbdev <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: ATI problems.
Date: Sat, 8 Nov 2003 19:03:13 +0100	[thread overview]
Message-ID: <200311081903.14332.alex.kern@gmx.de> (raw)
In-Reply-To: <1067871410.3fa66cb249228@www.inforagro.com.br>

Am Montag, 3. November 2003 15:56 schrieb leandro@inforagro.com.br:
> Hi all!
>
> I`ve tried to use framebuffer on my machine against 2.6.0-testX kernel
> since some days ago.
>
> Hardware:
>
>    - Intel® Pentium III de 700 MHZ
>    - ATI Range - Chipset ATI Range Mobility M1 Graphics
>    - screen TFT 13,3" (LCD)
>
> I already tried using aty, aty128fb, vesafb, but nothing was ok. I also
> tried to use vga=xxx paramter but it didn`t work.I used vesa framebuffer in
> 2.4.xx perfectly.
>
> I`m waint your answer.
>
> Leandro Dorileo

Great one more mach64 user.
So, first, you do not need aty128fb, vesafb should work!
But ATI Rage Mobility M1 will be covered by atyfb driver.

You must get the last fbdev patch from J. Simmons.
Be sure it is the last version, it only includes atyfb change for Mobility.

Applay it on your kernel, I use 2.6.0-test9 

my .config 
#
# Graphics support
#
CONFIG_FB=y
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
# CONFIG_FB_VESA is not set
# CONFIG_VIDEO_SELECT is not set
# CONFIG_FB_HGA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_I810 is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
CONFIG_FB_ATY=y
CONFIG_FB_ATY_CT=y
CONFIG_FB_ATY_GENERIC_LCD=y
# CONFIG_FB_ATY_XL_INIT is not set
# CONFIG_FB_ATY_GX is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_VIRTUAL is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_PCI_CONSOLE=y
CONFIG_FONTS=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
# CONFIG_FONT_6x11 is not set
# CONFIG_FONT_PEARL_8x8 is not set
# CONFIG_FONT_ACORN_8x8 is not set
# CONFIG_FONT_MINI_4x6 is not set
# CONFIG_FONT_SUN8x16 is not set
# CONFIG_FONT_SUN12x22 is not set

#
# Logo configuration
#
CONFIG_LOGO=y
CONFIG_LOGO_LINUX_MONO=y
CONFIG_LOGO_LINUX_VGA16=y
CONFIG_LOGO_LINUX_CLUT224=y

kernel paramater line should be video=atyfb:1024x768 if 1024x768 your 
resolution is.

If You have any troubles,  switches DEBUG macro in drivers/video/aty/
atyfb_base.c on, and post your dmesg and lspci.

Good luck
Alex



-------------------------------------------------------
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
developments in Apache, PHP, Perl, XML, Java, MySQL,
WebDAV, and more! http://www.apachecon.com/

      reply	other threads:[~2003-11-08 15:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-03 14:56 ATI problems leandro
2003-11-08 18:03 ` Alexander Kern [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=200311081903.14332.alex.kern@gmx.de \
    --to=alex.kern@gmx.de \
    --cc=leandro@inforagro.com.br \
    --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 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).