On Fri, Aug 20, 2004 at 11:26:32PM -0700, dave giffin wrote:
> I'm trying to run a second X server using the
> framebuffer.
>
> I applied the ruby-2.6 patch to vanilla kernel version
> 2.6.7. I recompiled XFree86 4.3.0 with the prefbusid
> patch.
>
> I start up my 1st X server (on an ATI card, not using
> framebuffer) without a problem. Then from an xterm on
> that server, I try starting the 2nd framebuffer X
> server on a SiS card, and get the error below.
>
You are sure you _have_ a working framebuffer?
I.e.
$ cat somefile > /dev/fbX
results in some garbage on that screen? (Replace
X with the correct number. 0 if it is the only framebuffer,
1 if the ATI card also claims a framebuffer. Or test to see
what framebuffer it really is. Surprises happens here . . . )
> The 2nd server continues to run (though the screen it
> is connected to is blank). When I ctrl+c it, the
> screen my 1st server is on goes blank and is replaced
> by a garbled image of what it used to look like (the
> image doesn't change, maybe the 2nd X server accessed
> the framebuffer on the 1st card).
Well, perhaps the second xserver accessed the wrong framebuffer?
If the Device section of the XF86Config.fb file specifies
Driver "fbdev"
then you also need to specify what framebuffer to use, i.e.
Option "fbdev" "/dev/fbX"
I believe the framebuffer driver don't use pci at all, so
prefbusid and such doesn't affect it. Make sure you're trying
to use the correct fb, and that that fb actually works.
>
> I can still press CTRL+Alt+F1 and then CTRL+ALT+F7 to
> get back to my 1st X server.
>
Such switching rep}aints the screen, and also ensures that the right
console is working.
> I am using the "prefbusid" option in the config files
> for both servers. I also activated the 'hackvideo'
> extension. (I ran echo 1 > /proc/bus/pci/hackvideo ).
>
Not necessary for the fb server, but it may be necessary for the other one
so it don't naively turn off your SiS card.
> My System:
> ATI Radeon 7000 (1st X server, no framebuffer)
> SiS 630 (2nd X server, using framebuffer)
> Redhat 9 (i686)
> gcc 3.2.2
> XFree86 4.3.0
> kernel 2.6.7 + ruby & SiS & ATI framebuffer drivers
>
Ah, you have a ATI framebuffer. Then you probably have
both /dev/fb0 and /dev/fb1. Make sure your fb-X is
using the right one!
>
>
> What can I do about this problem?
>
> The error message:
>
> XFree86 Version 4.3.0
> Release Date: 27 February 2003
> X Protocol Version 11, Revision 0, Release 6.6
> Build Operating System: Linux 2.6.7-ruby i686 [ELF]
> Build Date: 20 August 2004
> Before reporting problems, check
> http://www.XFree86.Org/
> to make sure that you have the latest version.
> 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.1.0.log", Time: Fri
> Aug 20 23:01:06 2004
> (++) Using config file: "/etc/X11/XF86Config.fb"
> (EE) FBDEV(0): FBIOPAN_DISPLAY: Invalid argument
>
Is this FBIOPAN-thing something from the XF86Config.fb file?
If so, try commenting it out. Or perhaps it is an error
indicating you tried to use a "busy" fb, if you happened to use
the wrong one?
Helge Hafting
|
