Still having a problem running second X server on framebuffer.

[dave g. <giv...@ya...>]

I am trying to run a regular XFree86 server on an ATI
radeon 7000, and a second X server on a framebuffer on
a SiS 630 card, using ruby, to have both on screen at
the same time.

I have recompiled XFree86 4.3.0 with the PrefBusID
patch, and in the config for the 2nd X server, I have
set it to use the "fbdev" driver and have set the
"fbdev" option to "/dev/fbX".

I am working with vanilla kernel 2.6.7 with the ruby
patch. I have catted files to both framebuffer devices
to verify that they work. I have enabled 'hackvideo'.

When I boot with support for both framebuffers
(radeonfb & sisfb), without any X server running, I
can start the frame buffer X or regular X. 

With both framebuffers, I have set the framebuffer-X
to run on /dev/fb1.

When I start the frame buffer X (onto 2nd display) on
the first display (initted @ boot) I try switching
consoles to login to another shell and run a program
on the X server, the frame buffer X stops updating the
screen. When I run the regular X server first, and
then try starting the fb-X from an xterm, I get an
error message: 
(EE) FBDEV(0): FBIOPAN_DISPLAY: Invalid argument

and the server doesn't display anything.

When I loaded support for only the SiS framebuffer and
disabled support for framebuffer console, I was able
to start the framebuffer X without getting the FBIOPan
error message. (running X on /dev/fb0)

But, when I switched consoles on the display operated
by my ATI card (the card initialized @ boot), the
framebuffer X screen turns blue (it does update).

If I Ctrl+C the fb-X, I can restart it and the screen
returns to normal.

What is going on here? Can I run these 2 servers the
way I have outlined?

Should I try a different kernel version (using 2.6.7)?


(I got the ruby-2.6 patch from this mailing list a few
days ago. the patch is dated 2004-06-16, should I try
to get a new one, if yes, from where?)

My ultimate goal is to use XDirectFB(an X server using
the DirectFB library to access the framebuffer), not
XFree86, for my framebuffer X.

XDirectFB accepts a command-line option as to which
/dev/ttyX device to use (not vt or vc). 

When I boot my kernel with dumbcon=2 I get:
Console: Colour VGA+ 80x25 vc:1-16
Console: mono dummy device 80x25 vc:17-17
Console: mono dummy device 80x25 vc:18-18
Console: switching to colour ATI Radeon QY  80x30
vc:1-16
Console: Colour SIS 730 100x37 vc:19-34

How does the range of vc's relate to /dev/ttyX
devices?
Does /dev/tty17 == vc17?

:)



		
_______________________________
Do you Yahoo!?
Win 1 of 4,000 free domain names from Yahoo! Enter now.
http://promotions.yahoo.com/goldrush