* Graphics Mode Woes
@ 2004-04-23 0:39 Bobby Hitt
2004-04-23 1:48 ` Dmitry Torokhov
` (2 more replies)
0 siblings, 3 replies; 6+ messages in thread
From: Bobby Hitt @ 2004-04-23 0:39 UTC (permalink / raw)
To: linux-kernel
Hello,
I'm attempting to get linux 2.6.5 to go into 1024x768x64k mode with my
NVidia GEForce card. Under 2.4.25, it works fine with "vga=791" in my
lilo.conf file. Here's what's in the log:
Apr 22 17:19:09 gateway kernel: vesafb: framebuffer at 0xf0000000, mapped to
0xe080d000, size 3072k
Apr 22 17:19:09 gateway kernel: vesafb: mode is 1024x768x16,
linelength=2048, pages=0
Apr 22 17:19:09 gateway kernel: vesafb: protected mode interface info at
c000:c590
Apr 22 17:19:09 gateway kernel: vesafb: scrolling: redraw
Apr 22 17:19:09 gateway kernel: vesafb: directcolor: size=0:5:6:5,
shift=0:11:5:0
Apr 22 17:19:09 gateway kernel: Console: switching to colour frame buffer
device 128x48
Apr 22 17:19:09 gateway kernel: fb0: VESA VGA frame buffer device
Under 2.6.5:
Apr 22 17:57:58 gateway kernel: rivafb: nVidia device/chipset 10DE0110
Apr 22 17:57:58 gateway kernel: rivafb: Detected CRTC controller 0 being
used
Apr 22 17:57:58 gateway kernel: rivafb: RIVA MTRR set to ON
Apr 22 17:57:58 gateway kernel: rivafb: PCI nVidia NV10 framebuffer ver
0.9.5b (nVidiaGeForce2-M, 32MB @ 0xF0000000)
Apr 22 17:57:58 gateway kernel: vga16fb: initializing
Apr 22 17:57:58 gateway kernel: vga16fb: mapped to 0xc00a0000
Apr 22 17:57:58 gateway kernel: fb1: VGA16 VGA frame buffer device
Totally different output and no references to vesafb. With "vga=791" on
bootup the screen goes blank then switches to the normal graphics mode. Even
when I use "vga=ask" and I put in a valid number, the screen switches to
text mode momentarily then goes back to the normal graphics mode.
Here's the related portion of my .config file:
#
# Graphics support
#
CONFIG_FB=y
# 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_OLD 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_KYRO 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=y
CONFIG_FONT_ACORN_8x8=y
# 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
Any help or suggestions are appreciated,
Bobby
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: Graphics Mode Woes
2004-04-23 0:39 Graphics Mode Woes Bobby Hitt
@ 2004-04-23 1:48 ` Dmitry Torokhov
2004-04-23 3:32 ` Paul Misner
2004-04-23 16:56 ` James Simmons
2 siblings, 0 replies; 6+ messages in thread
From: Dmitry Torokhov @ 2004-04-23 1:48 UTC (permalink / raw)
To: linux-kernel; +Cc: Bobby Hitt
On Thursday 22 April 2004 07:39 pm, Bobby Hitt wrote:
> CONFIG_FB_VGA16=y
> CONFIG_FB_VESA=y
> CONFIG_VIDEO_SELECT=y
> # CONFIG_FB_HGA is not set
> CONFIG_FB_RIVA=y
^^^^^^^^^^^^^^^^^^^^
If you want vesa framebuffer why even select rivabf (NVidia)?
--
Dmitry
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Graphics Mode Woes
2004-04-23 0:39 Graphics Mode Woes Bobby Hitt
2004-04-23 1:48 ` Dmitry Torokhov
@ 2004-04-23 3:32 ` Paul Misner
2004-04-23 16:56 ` James Simmons
2 siblings, 0 replies; 6+ messages in thread
From: Paul Misner @ 2004-04-23 3:32 UTC (permalink / raw)
To: linux-kernel
On Thursday 22 April 2004 07:39 pm, Bobby Hitt wrote:
> Hello,
>
> Here's the related portion of my .config file:
> #
> # Graphics support
> #
> CONFIG_FB=y
> # 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
>
> #
> # 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=y
> CONFIG_FONT_ACORN_8x8=y
> # 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
>
> Any help or suggestions are appreciated,
>
> Bobby
I believe that you only want a single one of the CONFIG_FB options set. As I
recall, having more then one built in to the kernel causes problems,
especially with VGA16 and VESA. Why not just turn on CONFIG_FB_VESA=y, and
make the others modules (=m).
Why not turn off, or at least build as modules, all the things you aren't
really going to be using. Building everything into the kernel is a good way
to cause yourself problems.
As an example, part of my config is:
CONFIG_FB=y
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
CONFIG_FB_VESA=y
CONFIG_VIDEO_SELECT=y
The only things turned on in the graphics section are displayed above.
Paul
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Graphics Mode Woes
2004-04-23 0:39 Graphics Mode Woes Bobby Hitt
2004-04-23 1:48 ` Dmitry Torokhov
2004-04-23 3:32 ` Paul Misner
@ 2004-04-23 16:56 ` James Simmons
2004-04-23 20:13 ` Bobby Hitt
2 siblings, 1 reply; 6+ messages in thread
From: James Simmons @ 2004-04-23 16:56 UTC (permalink / raw)
To: Bobby Hitt; +Cc: linux-kernel
That is because the native driver takes priority over the vesafb driver.
Disable the native driver if you don't want ot use it.
On Thu, 22 Apr 2004, Bobby Hitt wrote:
> Hello,
>
> I'm attempting to get linux 2.6.5 to go into 1024x768x64k mode with my
> NVidia GEForce card. Under 2.4.25, it works fine with "vga=791" in my
> lilo.conf file. Here's what's in the log:
>
> Apr 22 17:19:09 gateway kernel: vesafb: framebuffer at 0xf0000000, mapped to
> 0xe080d000, size 3072k
> Apr 22 17:19:09 gateway kernel: vesafb: mode is 1024x768x16,
> linelength=2048, pages=0
> Apr 22 17:19:09 gateway kernel: vesafb: protected mode interface info at
> c000:c590
> Apr 22 17:19:09 gateway kernel: vesafb: scrolling: redraw
> Apr 22 17:19:09 gateway kernel: vesafb: directcolor: size=0:5:6:5,
> shift=0:11:5:0
> Apr 22 17:19:09 gateway kernel: Console: switching to colour frame buffer
> device 128x48
> Apr 22 17:19:09 gateway kernel: fb0: VESA VGA frame buffer device
>
> Under 2.6.5:
>
> Apr 22 17:57:58 gateway kernel: rivafb: nVidia device/chipset 10DE0110
> Apr 22 17:57:58 gateway kernel: rivafb: Detected CRTC controller 0 being
> used
> Apr 22 17:57:58 gateway kernel: rivafb: RIVA MTRR set to ON
> Apr 22 17:57:58 gateway kernel: rivafb: PCI nVidia NV10 framebuffer ver
> 0.9.5b (nVidiaGeForce2-M, 32MB @ 0xF0000000)
> Apr 22 17:57:58 gateway kernel: vga16fb: initializing
> Apr 22 17:57:58 gateway kernel: vga16fb: mapped to 0xc00a0000
> Apr 22 17:57:58 gateway kernel: fb1: VGA16 VGA frame buffer device
>
> Totally different output and no references to vesafb. With "vga=791" on
> bootup the screen goes blank then switches to the normal graphics mode. Even
> when I use "vga=ask" and I put in a valid number, the screen switches to
> text mode momentarily then goes back to the normal graphics mode.
>
> Here's the related portion of my .config file:
>
> #
> # Graphics support
> #
> CONFIG_FB=y
> # 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_OLD 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_KYRO 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=y
> CONFIG_FONT_ACORN_8x8=y
> # 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
>
> Any help or suggestions are appreciated,
>
> Bobby
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Graphics Mode Woes
2004-04-23 16:56 ` James Simmons
@ 2004-04-23 20:13 ` Bobby Hitt
2004-04-23 23:06 ` James Simmons
0 siblings, 1 reply; 6+ messages in thread
From: Bobby Hitt @ 2004-04-23 20:13 UTC (permalink / raw)
To: James Simmons; +Cc: linux-kernel
Hello,
I've since gotten this working, thanks to the help of Dmitry Torokhov:
-----
This is what I have for my GeForce2 Go. Actually I think what hurts you is
FB_VGA16, not RIVA.. Still, if you using vesa like I do there is no point
compiling rivafb (and If you using nVIDIA's binary driver rivafb usually
conflicts with it).
-----
I had the wrong drivers loaded.. My question now is where would I have been
able to disable the "native driver"? I don't recall seeing this in the
.config file.
TIA,
Bobby
----- Original Message -----
From: "James Simmons" <jsimmons@infradead.org>
To: "Bobby Hitt" <Bob.Hitt@bscnet.com>
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>
Sent: Friday, April 23, 2004 12:56 PM
Subject: Re: Graphics Mode Woes
>
> That is because the native driver takes priority over the vesafb driver.
> Disable the native driver if you don't want ot use it.
>
>
> On Thu, 22 Apr 2004, Bobby Hitt wrote:
>
> > Hello,
> >
> > I'm attempting to get linux 2.6.5 to go into 1024x768x64k mode with my
> > NVidia GEForce card. Under 2.4.25, it works fine with "vga=791" in my
> > lilo.conf file. Here's what's in the log:
> >
> > Apr 22 17:19:09 gateway kernel: vesafb: framebuffer at 0xf0000000,
mapped to
> > 0xe080d000, size 3072k
> > Apr 22 17:19:09 gateway kernel: vesafb: mode is 1024x768x16,
> > linelength=2048, pages=0
> > Apr 22 17:19:09 gateway kernel: vesafb: protected mode interface info at
> > c000:c590
> > Apr 22 17:19:09 gateway kernel: vesafb: scrolling: redraw
> > Apr 22 17:19:09 gateway kernel: vesafb: directcolor: size=0:5:6:5,
> > shift=0:11:5:0
> > Apr 22 17:19:09 gateway kernel: Console: switching to colour frame
buffer
> > device 128x48
> > Apr 22 17:19:09 gateway kernel: fb0: VESA VGA frame buffer device
> >
> > Under 2.6.5:
> >
> > Apr 22 17:57:58 gateway kernel: rivafb: nVidia device/chipset 10DE0110
> > Apr 22 17:57:58 gateway kernel: rivafb: Detected CRTC controller 0 being
> > used
> > Apr 22 17:57:58 gateway kernel: rivafb: RIVA MTRR set to ON
> > Apr 22 17:57:58 gateway kernel: rivafb: PCI nVidia NV10 framebuffer ver
> > 0.9.5b (nVidiaGeForce2-M, 32MB @ 0xF0000000)
> > Apr 22 17:57:58 gateway kernel: vga16fb: initializing
> > Apr 22 17:57:58 gateway kernel: vga16fb: mapped to 0xc00a0000
> > Apr 22 17:57:58 gateway kernel: fb1: VGA16 VGA frame buffer device
> >
> > Totally different output and no references to vesafb. With "vga=791" on
> > bootup the screen goes blank then switches to the normal graphics mode.
Even
> > when I use "vga=ask" and I put in a valid number, the screen switches to
> > text mode momentarily then goes back to the normal graphics mode.
> >
> > Here's the related portion of my .config file:
> >
> > #
> > # Graphics support
> > #
> > CONFIG_FB=y
> > # 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_OLD 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_KYRO 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=y
> > CONFIG_FONT_ACORN_8x8=y
> > # 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
> >
> > Any help or suggestions are appreciated,
> >
> > Bobby
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel"
in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
> >
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Graphics Mode Woes
2004-04-23 20:13 ` Bobby Hitt
@ 2004-04-23 23:06 ` James Simmons
0 siblings, 0 replies; 6+ messages in thread
From: James Simmons @ 2004-04-23 23:06 UTC (permalink / raw)
To: Bobby Hitt; +Cc: linux-kernel
> I've since gotten this working, thanks to the help of Dmitry Torokhov:
> -----
> This is what I have for my GeForce2 Go. Actually I think what hurts you is
> FB_VGA16, not RIVA.. Still, if you using vesa like I do there is no point
> compiling rivafb (and If you using nVIDIA's binary driver rivafb usually
> conflicts with it).
Makes sense since the vag16 uses a different pixel encoding method, planar
verses packed pixels.
> I had the wrong drivers loaded.. My question now is where would I have been
> able to disable the "native driver"? I don't recall seeing this in the
> .config file.
By native I meant the nVIDIA fbdev driver.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2004-04-23 23:06 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-04-23 0:39 Graphics Mode Woes Bobby Hitt
2004-04-23 1:48 ` Dmitry Torokhov
2004-04-23 3:32 ` Paul Misner
2004-04-23 16:56 ` James Simmons
2004-04-23 20:13 ` Bobby Hitt
2004-04-23 23:06 ` James Simmons
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox