Re: Two Nvidia cards, and black screen

[<han...@sa...>]

Hi,

Thanks for the information. It seems like mode switching doesn't help.

Right now there is one thing that really disturbs me, and that is the=20
fact that after 6 hours of playing around with the X servers today, I=20
once got both displays up and running perfectly, but just once. The next=20
time I tried it with exactly the same settings, once again it didn't=20
work.

Another thing that I have noticed is that I can change back and forth=20
between both running xservers by using either "xset -dpms -display :0.0"=20
or "xset -dpms -display :1.0". This will wake up the monitor of one X=20
server, while putting to sleep the other ones monitor and vice/versa.

I'm not giving up yet though ;) I must have missed something.. I have=20
also been trying with the opensouce "nv" driver, but get the same=20
results.

I'll have to contiunue tomorrow.

-Hans

> Your problem looks similar to the one encountered with radeon cards.
> Except you state that the first display is turned off without vga
> signal. A Radeon card keeps the VGA signal up but the display is black=20
> and can be restored by video mode switching (Ctrl-Alt- /-).
>=20
> In your case, without VGA signal, it shouldn't be possible to restore
> the display but you could check just in case.
>=20
> As explained in my previous mail, the problem occurs when the second
> card do VGA IOs at initialization. Regarding the open source driver
> those functions are provided by the vgahw module (see
> http://www.x.org/X11R6.8.2/doc/DESIGN19.html for details). The log=20
> entries are shown below:
>=20
> (II) Loading sub module "vgahw"
> (II) LoadModule: "vgahw"
> (II) Loading /usr/X11R6/lib/modules/libvgahw.a
> (II) Module vgahw: vendor=3D"X.Org Foundation"
>          compiled for 6.8.2, module version =3D 0.1.0
>          ABI class: X.Org Video Driver, version 0.7
> (II) RADEON(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is=
=20
> 0x0000
>=20
> I don't know if the close source nvidia driver uses this module or
> access the VGA registers by itself. Anyway the only solution is to
> modify the driver to disable VGA IOs.
>=20
> This has been done with the "VGAAccess" option for radeon and rage128=20
> drivers in the following patches posted in the xorg bugzilla:
> https://bugs.freedesktop.org/show_bug.cgi?id=3D2064
> https://bugs.freedesktop.org/show_bug.cgi?id=3D2089
>=20
> Regarding nvidia, you might ask them to implement this feature in their
> driver.
>=20
> Regards,
> C=E9dric
>=20
>=20
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practic=
es
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & Q=
A
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> Linuxconsole-dev mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxconsole-dev