Re: Successful ruby setup and a problem

[Wayne W. <wh...@Ma...>]

On Tue, 9 Mar 2004 Boszormenyi Zoltan <zb...@fr...> wrote:

> Yesterday I compiled 4.3.0-62 from FC2 test and that fixed the keyboard
> controller hardware access the kernel complained constantly but it also
> "destroys" the :1.0 when I logout on :0.0.
>
> Sorry, I did not described what it means in the first post. The screen
> goes black on :1.0. It looks like it goes into powersave mode. I think
> the X that drives :0.0 does some register settings in the hardware of
> :1.0 and the X that drives :1.0 looses track of what's going on. I
> pressed Ctrl-Alt-BkSpace on :1.0 after the monitor went black and the
> gdm login screen came back.

I have the exact same problem.  My setup is two Radeon RV100 QY [Radeon
7000/VE], one AGP and one PCI.  When I log out of the AGP console :0, it
"destroys" the PCI console :1.  I have found that I can restore the :1
console by getting X to reinitialize the display, e.g. with
Ctrl-Alt-KeyPadMinus (followed by Ctrl-Alt-KeyPadPlus to get back to the
previous resolution).  When the display comes back, the top few lines of
the screen have been scribbled on.  To restore the display, it is enough
to have X execute xf86Screens[0]->LeaveVT(0, 0) followed by
xf86Screens[0]->EnterVT(0, 0), so as a hack I bound Ctrl-Alt-KeyPadDivide
to this sequence in programs/Xserver/hw/xfree86/common/xf86Events.c.

Anyway, my understanding of the problem is this, which may be completely
nonsensical:  There is still some (legacy VGA?) resource each card has
which X expects to be mapped at a particular address, so that only one
card can have this resource mapped at a time.  Since :1 is started up
second, it has the resource mapped to the :1 card most of the time.  When
:0 exits, its X process expects that resource to be mapped to the :0 card
and goes ahead and writes to that address.  But the address is mapped to
the :1 card, so the :1 card is screwed up.

Cheers, Wayne