linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Amit Shah <shahamit@gmx.net>
To: linux-kernel@vger.kernel.org
Cc: jsimmons@infradead.org
Subject: Re: 2.6.0-test1: Framebuffer problem
Date: Wed, 16 Jul 2003 11:07:40 +0530	[thread overview]
Message-ID: <200307161107.40159.shahamit@gmx.net> (raw)
In-Reply-To: <200307151117.55804.shahamit@gmx.net>

On Tuesday 15 Jul 2003 11:17, I wrote:
> I have a Riva TNT2 display card. On compiling in framebuffer support and
>  the other options (like the fonts, vga16 support, etc, relevant part of
>  .config pasted below), the kernel doesn't proceed after some messages
>  (where it initializes the frame buffer)... I just see the grub screen
>  again with some stripes and there's no disk activity thereafter.

the lspci output is:
01:00.0 VGA compatible controller: nVidia Corporation Vanta [NV6] (rev 15)
00:01.0 PCI bridge: Intel Corp. 82850 850 (Tehama) Chipset AGP Bridge (rev 
04)

also, with CONFIG_FB disabled, in X, (using the "nv" driver), I get random 
images thrown all over the screen... if an html page is loading in the 
background, I'll portions of gifs/jpegs all over my screen, or the 
toolbars, scroll bars, etc...

> #
> # Graphics support
> #
> CONFIG_FB=y
> # CONFIG_FB_CIRRUS is not set
> # CONFIG_FB_PM2 is not set
> # CONFIG_FB_CYBER2000 is not set
> # CONFIG_FB_IMSTT is not set
> CONFIG_FB_VGA16=y
> CONFIG_FB_VESA=y
> CONFIG_VIDEO_SELECT=y
> # CONFIG_FB_HGA is not set
> CONFIG_FB_RIVA=y
> # 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 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_PM3 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=y
> CONFIG_FONT_PEARL_8x8=y
> CONFIG_FONT_ACORN_8x8=y
> CONFIG_FONT_MINI_4x6=y
> CONFIG_FONT_SUN8x16=y
> CONFIG_FONT_SUN12x22=y
>
> #
> # Logo configuration
> #
> CONFIG_LOGO=y
> CONFIG_LOGO_LINUX_MONO=y
> CONFIG_LOGO_LINUX_VGA16=y
> CONFIG_LOGO_LINUX_CLUT224=y

-- 
Amit Shah
http://amitshah.nav.to/

Why do you want to read your code?
 The machine will.
                 -- Sunil Beta


  reply	other threads:[~2003-07-16  5:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-15  5:47 Amit Shah
2003-07-16  5:37 ` Amit Shah [this message]
2003-07-17 17:05   ` James Simmons
2003-07-17 17:21     ` Alan Cox
2003-07-17 17:34       ` James Simmons
2003-07-18  9:53         ` Amit Shah
2003-07-18 12:57         ` Alan Cox
2003-07-18 20:18           ` Geert Uytterhoeven
2003-07-18 21:15             ` Alan Cox
2003-07-19  6:02               ` Geert Uytterhoeven
2003-07-19 13:07                 ` Alan Cox
2003-07-21 20:14                   ` Geert Uytterhoeven

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=200307161107.40159.shahamit@gmx.net \
    --to=shahamit@gmx.net \
    --cc=jsimmons@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: 2.6.0-test1: Framebuffer problem' \
    /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

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).