linuxconsole-dev

Dual head initialization

[Joshua R. <jam...@by...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

YEAH!  I finally got a dual head system set up and running with a Matrox
G450 card.
My only question is if the issue of framebuffer re-initalization when
exiting X was ever resolved?
When I Exit X on the primary head (a mga device) it grabs the frame
buffer for the secondary head (the fbdev device)  A switch to vt8 and
back to vt7 fixes this, but most of my roommates are not so
understanding of this quirk.
is there
A.  A quick fix or scriptwrapper that could cause the neccessary
framebuffer shifts?
B.  A way to prevent the graphics card form re-initializing?

Random note, I found that joymouse was a great alternative to getting a
new usb mouse for the second head.  It uses an existing joystick and
converts it into a mouse.  I have had a few problems of usb devices
swapping amongst themselves (joystick/keyboards) and it caused havok
until I changed the --vt5x statement to reflect the new position of the
keyboard.
~Joshua
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDVcs7yZ4qqW21pBoRApT5AJ0QGWyPmBN/V51OgUhbJz05QvfDvwCgk+jj
SiY7E7khxnB4UGSdXdN5+6o=
=B+ou
-----END PGP SIGNATURE-----

Re: Dual head initialization

[Aivils S. <ai...@un...>]

On Tre=F0diena, 19. Oktobris 2005 07:27, Joshua Reed wrote:
> YEAH! =A0I finally got a dual head system set up and running with a Matrox
> G450 card.
> My only question is if the issue of framebuffer re-initalization when
> exiting X was ever resolved?
> When I Exit X on the primary head (a mga device) it grabs the frame
> buffer for the secondary head (the fbdev device) =A0A switch to vt8 and
> back to vt7 fixes this, but most of my roommates are not so
> understanding of this quirk.
> is there
> A. =A0A quick fix or scriptwrapper that could cause the neccessary
> framebuffer shifts?
> B. =A0A way to prevent the graphics card form re-initializing?

Tell desktop manager to reinit X without restart. Under gdm gdm.conf
# If you are having trouble with using a single server for a long time and
# want gdm to kill/restart the server, turn this on
AlwaysRestartServer=3Dfalse


> Random note, I found that joymouse was a great alternative to getting a
> new usb mouse for the second head. =A0It uses an existing joystick and
> converts it into a mouse.

You can test a competitor http://www.ltn.lv/~aivils/files/xke-0.03.tar.bz2
It does not have axis converting, remaping - so incomplete.

> I have had a few problems of usb devices=20
> swapping amongst themselves (joystick/keyboards) and it caused havok
> until I changed the --vt5x statement to reflect the new position of the
> keyboard.

It is common trouble for all Linux input layer. I already include
X starting script X1wrap , which create necessary symbolic link
tty -> ftty in runtime.

Aivils

Re: Dual head initialization

[Helge H. <hel...@ai...>]

Joshua Reed wrote:

>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>YEAH!  I finally got a dual head system set up and running with a Matrox
>G450 card.
>My only question is if the issue of framebuffer re-initalization when
>exiting X was ever resolved?
>When I Exit X on the primary head (a mga device) it grabs the frame
>buffer for the secondary head (the fbdev device)  A switch to vt8 and
>back to vt7 fixes this, but most of my roommates are not so
>understanding of this quirk.
>is there
>A.  A quick fix or scriptwrapper that could cause the neccessary
>framebuffer shifts?
>  
>
I used xdm, and got a problem like this. Whenever X
restarted on the first head, it changed the framebuffer-to-
vga-connector mapping, making both screens show the same.

Fortunately, xdm lets you run a script whenever the xserver
starts and another whenever an xserver stops.  There I put
calls to a program that mapped screens the way I wanted them,
the end result being that a xserver restart caused a short blink
on the other display.

>B.  A way to prevent the graphics card form re-initializing?
>  
>
Several ways:

1. Use the framebuffer xserver.  It is unaccelerated, but more
    than fast enough for 2D graphichs.  You'll loose accelerated
    3D though.

2. Or set things up so X doesn't restart just because someone logs
    in/out.  Then, the problem will only happen once, at boot-time.

3. FIX the stupid xserver! Make it deal with its own card only, and
    never ever touch "legacy vga adresses" which may very well belong
    to another card.  Also, in the case of X running on a single head
    belonging to a dualhead card, fix X so it doesn't mess with the
    other head AT ALL.

Helge Hafting