how to activate X with famebuffer

how to activate X with famebuffer

[Mukund JB.]

Hello otto,

The question I am asking may the simplest of this field, but I found it no where.
Pls help.

How to activate X with framebuffer.

I am working with the following configuration:-
* Red Hat Linux 7.3 
* Kernel 2.4.18-3 
* Nvidia Riva TNT card 
* Rivafb driver 
* XFree86 4.2.0 
 
My edited the XF86Confoig file as follows( related sections only):-

Section "device"
	Identifier "linix fb"
	Driver "rivafb"	# Is rivafb the right keyword for rivafb.o module?
	BoardName "Unknown"
EndSection

Section "Screen"
	Identifier "Screen0"
	Device "linux fb"
	Monitor "COMPAQ S510"
	DefaultDepth 8
	Subsection "Display"
		Depth 8
	EndSubSection 
EndSection

Is rivafb the right keyword for rivafb.o module?
Is it the driver name(module name) that we should keep in the Driver part of Device section?

If I startx afterb modprobing the rivafb, it results in errors.
# startx 

(EE) Fialed to load module "rivafb" ( module does not exist, 0)
(EE) No devices detected.

Please help me in this regard. I have spend good enough time on this and its I high time get it done.

Is it so easy a question? Just becos I didn't find any info about in the internet and no body replies for question.

Aim Behind all this : 
To debug the rivafb driver when it being called or used by X server( XF86 ).

Regards,
Mukund jampala


-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php

Re: how to activate X with famebuffer

[Carlo E. Prelz]

	Subject: [Linux-fbdev-devel] how to activate X with famebuffer
	Date: Mon, Sep 27, 2004 at 10:45:25AM +0530

Quoting Mukund JB. (mukundjb@esntechnologies.co.in):

> How to activate X with framebuffer.

I am not much of an expert, but I see noone is answering...
First of all, you must be sure that the framebuffer level is
working. What does  /proc/fb contain? There should be one or more
line. For example, mine has

0 ATI Radeon Yd

which means that I have one framebuffer unit available. 

Then, have a look at man fbdev. Specifically, the Driver line in your
device section should be 
 
Driver "fbdev"
 
There should be another way. Set 

Driver "nv"

(for nvidia cards, including riva ones) and set 

Option "UseFBDev" "on"

I have no clear idea about what the difference is. Anyway, Have a look
at man nv and man fbdevhw. 

ALL THIS IS PURELY THEORETICAL from my point of view!! You need to
experiment a bit. 

Carlo

-- 
  *         Se la Strada e la sua Virtu' non fossero state messe da parte,
* K * Carlo E. Prelz - fluido@fluido.as             che bisogno ci sarebbe
  *               di parlare tanto di amore e di rettitudine? (Chuang-Tzu)


-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php

RE: how to activate X with famebuffer

[Mukund JB.]

Hello,
Thanks for responding.


> > How to activate X with framebuffer.
> 
> I am not much of an expert, but I see noone is answering...
> First of all, you must be sure that the framebuffer level is
> working. What does  /proc/fb contain? There should be one or more
> line. For example, mine has
> 
> 0 ATI Radeon Yd

Yes, u r right.
cat /proc/fb says
0 RIVA_VTNT2

>
> which means that I have one framebuffer unit available.
> 
> Then, have a look at man fbdev. Specifically, the Driver line in your
> device section should be
> 
> Driver "fbdev"
This statement will load the default framebuffer driver which comes with
XFree86 package. Xorg also provides a GENERIC framebuffer driver i.e.
fbdev.
This works on my system. I have no probelsm with this.
But my requirement is to activate X on rivafb (Nvidia CARD SPECIFIC
DRIVER) module.

> 
> There should be another way. Set
> 
> Driver "nv"
I think, saying so in XF86Config file will not activate X based on the
framebuffer driver. This works on my system even when I have not loaded
the rivafb (Nvidia card specific driver) module.
Even if the rivafb module is loaded, it is not invoked at startx (debug
message are not appearing ). I think, this edition of XF86Config file
will activate a normal video driver but not framebuffer driver.

> (for nvidia cards, including riva ones) and set
> 
> Option "UseFBDev" "on"
> 
I don't why to use this? If u know please provide with the info
> I have no clear idea about what the difference is. Anyway, Have a look
> at man nv and man fbdevhw.
> 
> ALL THIS IS PURELY THEORETICAL from my point of view!! You need to
> experiment a bit.
> 
> Carlo




Please suggest me how to activate X so that it uses rivafb (card
specific fb driver )module.

Thanks a lot for being the first one to help.

Regards,
Mukund jampala



-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php

RE: how to activate X with famebuffer

[Geert Uytterhoeven]

On Mon, 27 Sep 2004, Mukund JB. wrote:
> > which means that I have one framebuffer unit available.
> > 
> > Then, have a look at man fbdev. Specifically, the Driver line in your
> > device section should be
> > 
> > Driver "fbdev"
> This statement will load the default framebuffer driver which comes with
> XFree86 package. Xorg also provides a GENERIC framebuffer driver i.e.
> fbdev.
> This works on my system. I have no probelsm with this.
> But my requirement is to activate X on rivafb (Nvidia CARD SPECIFIC
> DRIVER) module.

Indeed, `Driver "fbdev"' gives you the generic (unaccelerated) fbdev driver in
X.

> > There should be another way. Set
> > 
> > Driver "nv"
> I think, saying so in XF86Config file will not activate X based on the
> framebuffer driver. This works on my system even when I have not loaded
> the rivafb (Nvidia card specific driver) module.
> Even if the rivafb module is loaded, it is not invoked at startx (debug
> message are not appearing ). I think, this edition of XF86Config file
> will activate a normal video driver but not framebuffer driver.
> 
> > (for nvidia cards, including riva ones) and set
> > 
> > Option "UseFBDev" "on"
> > 
> I don't why to use this? If u know please provide with the info

`Driver "nv"'  will give you the accelerated Nvidia driver. But by default `nv'
doesn't use the fbdev API. So in addition you have to set
`Option "UseFBDev" "on"', so `nv' knows it has to use the fbdev API for mode
switching.

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds


-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php

RE: how to activate X with famebuffer

[Mukund JB.]

Hello Geert,
Thanks for the support.
It does not work when I use UseFBdev option.

> `Driver "nv"'  will give you the accelerated Nvidia driver. But by
default
> `nv'
> doesn't use the fbdev API. 
> So in addition you have to set
> `Option "UseFBDev" "on"', so `nv' knows it has to use the fbdev API
for
> mode
> switching.

I want X to be working on rivafb(Card specific fb driver) driver rather
than fbdev(generic) driver. However,

I tried starting 'X' by adding 

Option "UseFBDev" "on"
	Or
Option "UseFBDev" "yes"

I get the error message saying :-
(EE) Screen(s) found, but none have a usable configuration.


when we startx, it ends up abruptly saying :-

"(EE) Screen(s) found, but none have a usable configuration."

Also,
when we use Driver "fbdev" in Device section, it is using the
fbdev_drv.o module from the directory "/usr/X11R6/lib/modules/drivers/"
which I could see in the Xfree86.0.log file.
What is this fbdev_drv.o module? Can u please suggest what it can be?

when u say Driver "nv", it is using the nv_drv.o module from the
directory "/usr/X11R6/lib/modules/drivers/". Can u just tell me what
nv_drv.0 file is?

The X comes up/works well when we remove/comment the UseFBDev line.

Is it any thing wrong that I am doing? Please suggest?


The following are my XF86Config-4, XFree86.0.log files.
Hope these files can be of some support to u.

				<- XF86Config-4 file ->
------------------------------------------------------------------------
----
# XFree86 4.2.0 configuration generated by Xconfigurator 4.10.7

Section "ServerLayout"
	Identifier "XFree86 Configured"
	Screen      0  "Screen0" 0 0
	InputDevice    "Mouse0" "CorePointer"
	InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

# Red Hat Linux 6.0 and later use the xfs font server for improved
# interactive performance

Section "Files"
	FontPath "unix/:7100"
EndSection

# Module loading section

Section "Module"
	Load  "dbe"		# Double-buffering
#	Load  "GLcore"		# OpenGL support
#	Load  "dri"		# Direct rendering infrastructure
	Load  "glx"		# OpenGL X protocol interface
	Load  "extmod"		# Misc. required extensions
	Load  "v4l"		# Video4Linux
	# Load  "record"	# X event recorder
	# You only need the following two modules if you do not use xfs.
	# Load  "freetype"	 # TrueType font handler
	# Load  "type1"		# Adobe Type 1 font handler
EndSection

Section "InputDevice"
	Identifier  "Keyboard0"
	Driver      "keyboard"
	Option      "XkbLayout"	"us"
EndSection

Section "InputDevice"
	Identifier	"Mouse0"
	# Modified by mouseconfig
	Driver		"mouse"
	Option		"Device"		"/dev/mouse"
	Option		"Protocol"		"PS/2"
	Option		"Emulate3Buttons"	"yes"
	Option		"ZAxisMapping"		"4 5"
EndSection

Section "Monitor"
	Identifier "COMPAQ S510"
	VendorName "Unknown"
	ModelName  "Unknown"
	HorizSync 30 - 61
	VertRefresh 50 - 120
	Option "dpms"
EndSection

Section "Device"
	Identifier "RIVA TNT2"
	Driver "nv"
	BoardName "Unknown"
EndSection

Section "Device"
	Identifier "Linux Frame Buffer"
	Driver "nv" #Driver "fbdev"-> This is generic driver provided by
XFree
	Option "UseFBDev" "yes"    # this to avoid some conflict
	BoardName "Unknown"
EndSection

Section "Screen"
	Identifier "Screen0"
	Device "Linux Frame Buffer"
	Monitor "COMPAQ S510"
	DefaultDepth 8
	Subsection "Display"
		Depth 8
	#	Modes "1024x768"
	EndSubSection
EndSection

Section "DRI"
	Mode 0666
EndSection
------------------------------------------------------------------------
----

					<- XFree86.0.log ->
------------------------------------------------------------------------
----

XFree86 Version 4.2.0 (Red Hat Linux release: 4.2.0-8) / X Window System
(protocol Version 11, revision 0, vendor release 6600)
Release Date: 23 January 2002
	If the server is older than 6-12 months, or if your card is
	newer than the above date, look for a newer version before
	reporting problems.  (See http://www.XFree86.Org/)
Build Operating System: Linux 2.4.17-0.13smp i686 [ELF] 
Build Host: daffy.perf.redhat.com
 
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
         (++) from command line, (!!) notice, (II) informational,
         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/XFree86.0.log", Time: Mon Sep 27 14:36:58 2004
(==) Using config file: "/etc/X11/XF86Config-4"
(==) ServerLayout "XFree86 Configured"
(**) |-->Screen "Screen0" (0)
(**) |   |-->Monitor "COMPAQ S510"
(**) |   |-->Device "Linux Frame Buffer"
(**) |-->Input Device "Mouse0"
(**) |-->Input Device "Keyboard0"
(**) Option "XkbLayout" "us"
(**) XKB: layout: "us"
(==) Keyboard: CustomKeycode disabled
(**) FontPath set to "unix/:7100"
(==) RgbPath set to "/usr/X11R6/lib/X11/rgb"
(==) ModulePath set to "/usr/X11R6/lib/modules"
(--) using VT number 7

(II) Open APM successful
(II) Module ABI versions:
	XFree86 ANSI C Emulation: 0.1
	XFree86 Video Driver: 0.5
	XFree86 XInput driver : 0.3
	XFree86 Server Extension : 0.1
	XFree86 Font Renderer : 0.3
(II) Loader running on linux
(II) LoadModule: "bitmap"
(II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a
(II) Module bitmap: vendor="The XFree86 Project"
	compiled for 4.2.0, module version = 1.0.0
	Module class: XFree86 Font Renderer
	ABI class: XFree86 Font Renderer, version 0.3
(II) Loading font Bitmap
(II) LoadModule: "pcidata"
(II) Loading /usr/X11R6/lib/modules/libpcidata.a
(II) Module pcidata: vendor="The XFree86 Project"
	compiled for 4.2.0, module version = 0.1.0
	ABI class: XFree86 Video Driver, version 0.5
(II) PCI: Probing config type using method 1
(II) PCI: Config type is 1
(II) PCI: stages = 0x03, oldVal1 = 0x00000000, mode1Res1 = 0x80000000
(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 8086,7190 card 0000,0000 rev 03 class 06,00,00
hdr 00
(II) PCI: 00:01:0: chip 8086,7191 card 0000,0000 rev 03 class 06,04,00
hdr 01
(II) PCI: 00:07:0: chip 8086,7110 card 0000,0000 rev 02 class 06,01,00
hdr 80
(II) PCI: 00:07:1: chip 8086,7111 card 0000,0000 rev 01 class 01,01,80
hdr 00
(II) PCI: 00:07:2: chip 8086,7112 card 0000,0000 rev 01 class 0c,03,00
hdr 00
(II) PCI: 00:07:3: chip 8086,7113 card 0000,0000 rev 02 class 06,80,00
hdr 00
(II) PCI: 00:10:0: chip 11f6,1401 card 0000,0000 rev 0a class 02,00,00
hdr 00
(II) PCI: 01:00:0: chip 10de,002d card 1043,0201 rev 15 class 03,00,00
hdr 00
(II) PCI: End of PCI scan
(II) LoadModule: "scanpci"
(II) Loading /usr/X11R6/lib/modules/libscanpci.a
(II) Module scanpci: vendor="The XFree86 Project"
	compiled for 4.2.0, module version = 0.1.0
	ABI class: XFree86 Video Driver, version 0.5
(II) UnloadModule: "scanpci"
(II) Unloading /usr/X11R6/lib/modules/libscanpci.a
(II) Host-to-PCI bridge:
(II) PCI-to-ISA bridge:
(II) PCI-to-PCI bridge:
(II) Bus 0: bridge is at (0:0:0), (-1,0,0), BCTRL: 0x08 (VGA_EN is set)
(II) Bus 0 I/O range:
	[0] -1	0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) Bus 0 non-prefetchable memory range:
	[0] -1	0x00000000 - 0xffffffff (0x0) MX[B]
(II) Bus 0 prefetchable memory range:
	[0] -1	0x00000000 - 0xffffffff (0x0) MX[B]
(II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x8c (VGA_EN is set)
(II) Bus 1 I/O range:
(II) Bus 1 non-prefetchable memory range:
	[0] -1	0xf4000000 - 0xf4ffffff (0x1000000) MX[B]
(II) Bus 1 prefetchable memory range:
	[0] -1	0xfc000000 - 0xfdffffff (0x2000000) MX[B]
(II) Bus -1: bridge is at (0:7:0), (0,-1,0), BCTRL: 0x08 (VGA_EN is set)
(II) Bus -1 I/O range:
(II) Bus -1 non-prefetchable memory range:
(II) Bus -1 prefetchable memory range:
(--) PCI:*(1:0:0) NVidia Riva TNT2 M64 rev 21, Mem @ 0xf4000000/24,
0xfc000000/25
(II) Addressable bus resource ranges are
	[0] -1	0x00000000 - 0xffffffff (0x0) MX[B]
	[1] -1	0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) OS-reported resource ranges:
	[0] -1	0xffe00000 - 0xffffffff (0x200000) MX[B](B)
	[1] -1	0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
	[2] -1	0x000f0000 - 0x000fffff (0x10000) MX[B]
	[3] -1	0x000c0000 - 0x000effff (0x30000) MX[B]
	[4] -1	0x00000000 - 0x0009ffff (0xa0000) MX[B]
	[5] -1	0x0000ffff - 0x0000ffff (0x1) IX[B]
	[6] -1	0x00000000 - 0x000000ff (0x100) IX[B]
(II) Active PCI resource ranges:
	[0] -1	0xf8000000 - 0xfbffffff (0x4000000) MX[B]
	[1] -1	0xfc000000 - 0xfdffffff (0x2000000) MX[B](B)
	[2] -1	0xf4000000 - 0xf4ffffff (0x1000000) MX[B](B)
	[3] -1	0x00001020 - 0x0000103f (0x20) IX[B]
	[4] -1	0x00001000 - 0x0000101f (0x20) IX[B]
	[5] -1	0x00001040 - 0x0000104f (0x10) IX[B]
(II) Active PCI resource ranges after removing overlaps:
	[0] -1	0xf8000000 - 0xfbffffff (0x4000000) MX[B]
	[1] -1	0xfc000000 - 0xfdffffff (0x2000000) MX[B](B)
	[2] -1	0xf4000000 - 0xf4ffffff (0x1000000) MX[B](B)
	[3] -1	0x00001020 - 0x0000103f (0x20) IX[B]
	[4] -1	0x00001000 - 0x0000101f (0x20) IX[B]
	[5] -1	0x00001040 - 0x0000104f (0x10) IX[B]
(II) OS-reported resource ranges after removing overlaps with PCI:
	[0] -1	0xffe00000 - 0xffffffff (0x200000) MX[B](B)
	[1] -1	0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
	[2] -1	0x000f0000 - 0x000fffff (0x10000) MX[B]
	[3] -1	0x000c0000 - 0x000effff (0x30000) MX[B]
	[4] -1	0x00000000 - 0x0009ffff (0xa0000) MX[B]
	[5] -1	0x0000ffff - 0x0000ffff (0x1) IX[B]
	[6] -1	0x00000000 - 0x000000ff (0x100) IX[B]
(II) All system resource ranges:
	[0] -1	0xffe00000 - 0xffffffff (0x200000) MX[B](B)
	[1] -1	0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
	[2] -1	0x000f0000 - 0x000fffff (0x10000) MX[B]
	[3] -1	0x000c0000 - 0x000effff (0x30000) MX[B]
	[4] -1	0x00000000 - 0x0009ffff (0xa0000) MX[B]
	[5] -1	0xf8000000 - 0xfbffffff (0x4000000) MX[B]
	[6] -1	0xfc000000 - 0xfdffffff (0x2000000) MX[B](B)
	[7] -1	0xf4000000 - 0xf4ffffff (0x1000000) MX[B](B)
	[8] -1	0x0000ffff - 0x0000ffff (0x1) IX[B]
	[9] -1	0x00000000 - 0x000000ff (0x100) IX[B]
	[10] -1	0x00001020 - 0x0000103f (0x20) IX[B]
	[11] -1	0x00001000 - 0x0000101f (0x20) IX[B]
	[12] -1	0x00001040 - 0x0000104f (0x10) IX[B]
(II) LoadModule: "dbe"
(II) Loading /usr/X11R6/lib/modules/extensions/libdbe.a
(II) Module dbe: vendor="The XFree86 Project"
	compiled for 4.2.0, module version = 1.0.0
	Module class: XFree86 Server Extension
	ABI class: XFree86 Server Extension, version 0.1
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "glx"
(II) Loading /usr/X11R6/lib/modules/extensions/libglx.a
(II) Module glx: vendor="The XFree86 Project"
	compiled for 4.2.0, module version = 1.0.0
	ABI class: XFree86 Server Extension, version 0.1
(II) Loading sub module "GLcore"
(II) LoadModule: "GLcore"
(II) Loading /usr/X11R6/lib/modules/extensions/libGLcore.a
(II) Module GLcore: vendor="The XFree86 Project"
	compiled for 4.2.0, module version = 1.0.0
	ABI class: XFree86 Server Extension, version 0.1
(II) Loading extension GLX
(II) LoadModule: "extmod"
(II) Loading /usr/X11R6/lib/modules/extensions/libextmod.a
(II) Module extmod: vendor="The XFree86 Project"
	compiled for 4.2.0, module version = 1.0.0
	Module class: XFree86 Server Extension
	ABI class: XFree86 Server Extension, version 0.1
(II) Loading extension SHAPE
(II) Loading extension MIT-SUNDRY-NONSTANDARD
(II) Loading extension BIG-REQUESTS
(II) Loading extension SYNC
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XC-MISC
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-Misc
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension FontCache
(II) Loading extension TOG-CUP
(II) Loading extension Extended-Visual-Information
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) LoadModule: "v4l"
(II) Loading /usr/X11R6/lib/modules/drivers/linux/v4l_drv.o
(II) Module v4l: vendor="The XFree86 Project"
	compiled for 4.2.0, module version = 0.0.1
	ABI class: XFree86 Video Driver, version 0.5
(II) LoadModule: "nv"
(II) Loading /usr/X11R6/lib/modules/drivers/nv_drv.o
(II) Module nv: vendor="The XFree86 Project"
	compiled for 4.2.0, module version = 1.0.1
	Module class: XFree86 Video Driver
	ABI class: XFree86 Video Driver, version 0.5
(II) LoadModule: "mouse"
(II) Loading /usr/X11R6/lib/modules/input/mouse_drv.o
(II) Module mouse: vendor="The XFree86 Project"
	compiled for 4.2.0, module version = 1.0.0
	Module class: XFree86 XInput Driver
	ABI class: XFree86 XInput driver, version 0.3
(II) v4l driver for Video4Linux
(II) NV: driver for NVIDIA chipsets: RIVA128, RIVA TNT, RIVA TNT2,
	RIVA TNT2 Ultra, Vanta, RIVA TNT2 M64, Aladdin TNT2, GeForce
256,
	GeForce DDR, Quadro, GeForce2 GTS/Pro, GeForce2 Ti, GeForce2
Ultra,
	Quadro2 Pro, GeForce2 MX/MX 400, GeForce2 MX 100/200, 0x0170,
0x0171,
	0x0172, 0x0173, 0x0174, 0x0175, 0x0178, 0x017A, 0x017B, 0x017C,
	GeForce2 Integrated, Quadro2 MXR, GeForce2 Go, GeForce3,
	GeForce3 Ti 200, GeForce3 Ti 500, Quadro DDC, 0x0250, 0x0258
(II) Primary Device is: PCI 01:00:0
(--) Assigning device section with no busID to primary device
(--) Chipset RIVA TNT2 M64 found
(II) resource ranges after xf86ClaimFixedResources() call:
	[0] -1	0xffe00000 - 0xffffffff (0x200000) MX[B](B)
	[1] -1	0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
	[2] -1	0x000f0000 - 0x000fffff (0x10000) MX[B]
	[3] -1	0x000c0000 - 0x000effff (0x30000) MX[B]
	[4] -1	0x00000000 - 0x0009ffff (0xa0000) MX[B]
	[5] -1	0xf8000000 - 0xfbffffff (0x4000000) MX[B]
	[6] -1	0xfc000000 - 0xfdffffff (0x2000000) MX[B](B)
	[7] -1	0xf4000000 - 0xf4ffffff (0x1000000) MX[B](B)
	[8] -1	0x0000ffff - 0x0000ffff (0x1) IX[B]
	[9] -1	0x00000000 - 0x000000ff (0x100) IX[B]
	[10] -1	0x00001020 - 0x0000103f (0x20) IX[B]
	[11] -1	0x00001000 - 0x0000101f (0x20) IX[B]
	[12] -1	0x00001040 - 0x0000104f (0x10) IX[B]
(II) resource ranges after probing:
	[0] -1	0xffe00000 - 0xffffffff (0x200000) MX[B](B)
	[1] -1	0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
	[2] -1	0x000f0000 - 0x000fffff (0x10000) MX[B]
	[3] -1	0x000c0000 - 0x000effff (0x30000) MX[B]
	[4] -1	0x00000000 - 0x0009ffff (0xa0000) MX[B]
	[5] -1	0xf8000000 - 0xfbffffff (0x4000000) MX[B]
	[6] -1	0xfc000000 - 0xfdffffff (0x2000000) MX[B](B)
	[7] -1	0xf4000000 - 0xf4ffffff (0x1000000) MX[B](B)
	[8] 0	0x000a0000 - 0x000affff (0x10000) MS[B]
	[9] 0	0x000b0000 - 0x000b7fff (0x8000) MS[B]
	[10] 0	0x000b8000 - 0x000bffff (0x8000) MS[B]
	[11] -1	0x0000ffff - 0x0000ffff (0x1) IX[B]
	[12] -1	0x00000000 - 0x000000ff (0x100) IX[B]
	[13] -1	0x00001020 - 0x0000103f (0x20) IX[B]
	[14] -1	0x00001000 - 0x0000101f (0x20) IX[B]
	[15] -1	0x00001040 - 0x0000104f (0x10) IX[B]
	[16] 0	0x000003b0 - 0x000003bb (0xc) IS[B]
	[17] 0	0x000003c0 - 0x000003df (0x20) IS[B]
(II) Setting vga for screen 0.
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Loading /usr/X11R6/lib/modules/linux/libint10.a
(II) Module int10: vendor="The XFree86 Project"
	compiled for 4.2.0, module version = 1.0.0
	ABI class: XFree86 Video Driver, version 0.5
(II) NV(0): Initializing int10
(II) NV(0): Primary V_BIOS segment is: 0xc000
(--) NV(0): Chipset: "RIVA TNT2 M64"
(**) NV(0): Depth 8, (--) framebuffer bpp 8
(==) NV(0): Default visual is PseudoColor
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"
(II) Loading /usr/X11R6/lib/modules/libvgahw.a
(II) Module vgahw: vendor="The XFree86 Project"
	compiled for 4.2.0, module version = 0.1.0
	ABI class: XFree86 Video Driver, version 0.5
(**) NV(0): Option "UseFBDev" "yes"
(==) NV(0): Using HW cursor
(**) NV(0): Using framebuffer device
(II) Loading sub module "fbdevhw"
(II) LoadModule: "fbdevhw"
(II) Loading /usr/X11R6/lib/modules/linux/libfbdevhw.a
(II) Module fbdevhw: vendor="The XFree86 Project"
	compiled for 4.2.0, module version = 0.0.2
	ABI class: XFree86 Video Driver, version 0.5
(II) UnloadModule: "nv"
(II) UnloadModule: "fbdevhw"
(II) Unloading /usr/X11R6/lib/modules/linux/libfbdevhw.a
(II) UnloadModule: "vgahw"
(II) Unloading /usr/X11R6/lib/modules/libvgahw.a
(II) UnloadModule: "int10"
(II) Unloading /usr/X11R6/lib/modules/linux/libint10.a
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found

When reporting a problem related to a server crash, please send
the full server output, not just the last messages.
This can be found in the log file "/var/log/XFree86.0.log".
Please report problems to xfree86@xfree86.org.
------------------------------------------------------------------------
----

Thanks, for so much of continuous support.

Regards,
Mukund jampala



-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php

Re: how to activate X with famebuffer

[Carlo E. Prelz]

	Subject: RE: [Linux-fbdev-devel] how to activate X with famebuffer
	Date: lun, set 27, 2004 at 07:06:59 +0530

Quoting Mukund JB. (mukundjb@esntechnologies.co.in):

> I get the error message saying :-
> (EE) Screen(s) found, but none have a usable configuration.

<cut>
 
> Section "Screen"
> 	Identifier "Screen0"
> 	Device "Linux Frame Buffer"
> 	Monitor "COMPAQ S510"
> 	DefaultDepth 8
> 	Subsection "Display"
> 		Depth 8
> 	#	Modes "1024x768"
> 	EndSubSection
> EndSection

Why did you comment out the "modes" line??

Carlo

-- 
  *         Se la Strada e la sua Virtu' non fossero state messe da parte,
* K * Carlo E. Prelz - fluido@fluido.as             che bisogno ci sarebbe
  *               di parlare tanto di amore e di rettitudine? (Chuang-Tzu)


-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php

RE: how to activate X with famebuffer

[Mukund JB.]

> > I get the error message saying :-
> > (EE) Screen(s) found, but none have a usable configuration.
> 
> <cut>
> 
> > Section "Screen"
> > 	Identifier "Screen0"
> > 	Device "Linux Frame Buffer"
> > 	Monitor "COMPAQ S510"
> > 	DefaultDepth 8
> > 	Subsection "Display"
> > 		Depth 8
> > 	#	Modes "1024x768"
> > 	EndSubSection
> > EndSection
> 
> Why did you comment out the "modes" line??
I am defining the mode in the lilo.conf file.
Can u suggest how to acticate X so that it works on rivafb framebuffer
driver.

> 
> Carlo

Regards,
Mukund jampala


-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php

Re: how to activate X with famebuffer

[Carlo E. Prelz]

	Subject: RE: [Linux-fbdev-devel] how to activate X with famebuffer
	Date: mar, set 28, 2004 at 11:11:37 +0530

Quoting Mukund JB. (mukundjb@esntechnologies.co.in):

> > > I get the error message saying :-
> > > (EE) Screen(s) found, but none have a usable configuration.
> > 
> > <cut>
> > 
> > > Section "Screen"
> > > 	Identifier "Screen0"
> > > 	Device "Linux Frame Buffer"
> > > 	Monitor "COMPAQ S510"
> > > 	DefaultDepth 8
> > > 	Subsection "Display"
> > > 		Depth 8
> > > 	#	Modes "1024x768"
> > > 	EndSubSection
> > > EndSection
> > 
> > Why did you comment out the "modes" line??
> I am defining the mode in the lilo.conf file.

Your error message tells you that the "screen" section is
unusable. So, you are supposed to experiment with modifications on
that section until the error message changes - that is, until your
screen section becomes usable. Focus on the immediate block. When your
screen section is OK. either X will work, or you will have a new error
message pointing to new tests and experiments.

X must be told at what resolution to work, and all framebuffer drivers
but the simple VESA one can change resolution on the fly, so you can
very well have X in one resolution and text mode in one (or more)
other resolutions. 

Carlo

-- 
  *         Se la Strada e la sua Virtu' non fossero state messe da parte,
* K * Carlo E. Prelz - fluido@fluido.as             che bisogno ci sarebbe
  *               di parlare tanto di amore e di rettitudine? (Chuang-Tzu)


-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php

RE: how to activate X with famebuffer

[Mukund JB.]

Hai Carlo,

I think the framebuffer problem is partially solved.
There is some thing that I to make clear clear about framebuffer.

I think the X was using loaded rivafb on my system from a long time, but problem lies some where in analyzing it.
I was testing it by opening some apps and expecting the rivafb to be invoked, which indeed is not happening?

Perception: X will invoke rivafb when ever I open a new App and when I shift between Apps. But, it is not invoked in such instances. I don’t know why rivafb is not invoked when I open a new app.

It is invoked when I run X server performance tests like "x11perf" in the GUI mode.

Why is it not invoked when a new GUI application is opened?
Is it like X server is capable of doing that( opening GUI apps) without framebuffer?

			 
ACCORDING TO FRAMEBUFFER DEFINITION :-
A framebuffer device is an abstraction for the graphic hardware. It represents the frame buffer of some video hardware, and allows application software to access the graphic hardware through a well−defined interface,
so that the software doesn't need to know anything about the low−level interface stuff 

This is taken from Geert Uytterhoeven's framebuffer.txt in the linux kernel sources.
In the above definition what is an Application? Is it the X server, Applications above it?

Suppose there is a kwrite application, obviously running over X server.
Looking at this angle the flow is as follows:-


	NORMAL Applications ( Kwrite)
	-------------------
		X Server
	-------------------
	Framebuffer Driver
	-------------------
		HARDWARE

Is it Applications like Kwrite should support Framebuffer in order the X server makes use of it. If this is the case, the flow will be as follows:-

	NORMAL Applications (Apps instructs X server - Use fb or don't use) 
   -------------------------
		X Server
   -------------------------
Framebuffer / NON-Framebuffer
		 Driver
   -------------------------
		HARDWARE


IF THIS IS THE ARCHITECTURE, THE X SERVER WILL USE FRAMEBUFFER BASED ON THE APPLICATION THAT IS CALLING IT.

what I am speaking may be a BLUNDER MISTAKE. Regrets, if so. Please correct if mistaken.

> Your error message tells you that the "screen" section is
> unusable. So, you are supposed to experiment with modifications on
> that section until the error message changes - that is, until your
> screen section becomes usable. Focus on the immediate block. When your
> screen section is OK. either X will work, or you will have a new error
> message pointing to new tests and experiments.

Now, I have no problems here.

> X must be told at what resolution to work, and all framebuffer drivers
> but the simple VESA one can change resolution on the fly, so you can
> very well have X in one resolution and text mode in one (or more)
> other resolutions.

Yes, the current screen Section has the field of modes defined as follows:-
Modes "800x600"


Regards,
Mukund jampala

Re: how to activate X with famebuffer

[Antonino A. Daplas]

On Tuesday 28 September 2004 19:27, Mukund JB. wrote:
>
> ACCORDING TO FRAMEBUFFER DEFINITION :-
> A framebuffer device is an abstraction for the graphic hardware. It
> represents the frame buffer of some video hardware, and allows application
> software to access the graphic hardware through a well−defined interface,
> so that the software doesn't need to know anything about the low−level
> interface stuff
>
> This is taken from Geert Uytterhoeven's framebuffer.txt in the linux kernel
> sources. In the above definition what is an Application? Is it the X
> server, Applications above it?

'Application' is any process, user or kernel, that directly runs on top of the 
framebuffer. It can be X, or the framebuffer console.  It can be a process 
that totally bypasses X, such as directfb or mplayer -vo fbdev. Any process 
that does not run directly on top of the framebuffer is not considered as 
part of the 'Application' layer, such as kwrite on X on fbdev, or 'mplayer 
-vo directfb' on directfb on fbdev.

But X on fbdev or direcfb on fbdev or mplayer on fbdev are all considered part 
of the 'Application' layer.

>
> Suppose there is a kwrite application, obviously running over X server.
> Looking at this angle the flow is as follows:-
>
>
> 	NORMAL Applications ( Kwrite)
> 	-------------------
> 		X Server
> 	-------------------
> 	Framebuffer Driver
> 	-------------------
> 		HARDWARE
>

Yes, above is how it works.  In this case, Kwrite doesn't know a thing about 
the framebuffer, as it runs on top of X.  Or more properly, something like 
this:

NORMAL Applications such as X, DirectFB, mplayer, etc
-------------------
Framebuffer Driver
-------------------
HARDWARE

The X server is considered as part of 'NORMAL Applications'.

> Is it Applications like Kwrite should support Framebuffer in order the X
> server makes use of it. If this is the case, the flow will be as follows:-
>
> 	NORMAL Applications (Apps instructs X server - Use fb or don't use)
>    -------------------------
> 		X Server
>    -------------------------
> Framebuffer / NON-Framebuffer
> 		 Driver
>    -------------------------
> 		HARDWARE

No, the above is not the case.

Tony




-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl