From: <han...@sa...> - 2005-08-07 18:17:15
|
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 |
From: <han...@sa...> - 2005-08-08 10:10:56
|
Hi, I noticed the closed source nvidia driver has the following option: Option "UseInt10Module" "boolean" Enable use of the X Int10 module to soft-boot all secondary cards, rather than POSTing the cards through the NVIDIA kernel module. Default: off (POSTing is done through the NVIDIA kernel module). I tried using this option, first on one , then one the other, and=20 finally on both cards, but to no effect (other then some error message=20 about accessing the vga bios on one card). Am I still correct to assume that at least in theory it would be=20 possible to modify the int10 module (whereas you have modified the=20 radeon driver) to get the around the problem? I will try to use a modified nv driver as you suggested later today. Thanks for all your help! -Hans >=20 > After reading vgahw, radeon and nv source code, it seems to me that both > problems (blanc screen and DPMS) are related to vgahw functions call. >=20 > I'm afraid there's no solution with the stock drivers because I presume > there is a ressource conflict on VGA IOs between the two cards. >=20 > I would suggest to use a modified nv driver for the secondary card to > prevent messing the primary card settings. I guess the function=20 > NVRestore should be disabled to prevent the blank the screen at shutdown.= =20 > As for DPMS, I didn't look at it yet. >=20 > 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 |
From: <ce...@ri...> - 2005-08-10 02:29:14
|
han...@sa... a =E9crit : > Am I still correct to assume that at least in theory it would be=20 > possible to modify the int10 module (whereas you have modified the=20 > radeon driver) to get the around the problem? I don't think so but there is an interesting option to try: Screen Section Option "NoInt10" "boolean" Disables the Int10 module, a module that uses the int10 call to the BIOS of the graphics card to initialize it. Default: false. I'm still thinking that the cause of the screen blanking is the driver which try to restore the console in VGA text mode at shutdown. C=E9dric |
From: <ce...@ri...> - 2005-08-10 03:46:22
|
han...@sa... a =E9crit : > Am I still correct to assume that at least in theory it would be=20 > possible to modify the int10 module (whereas you have modified the=20 > radeon driver) to get the around the problem? I don't think so but there is an interesting option to try: Screen Section Option "NoInt10" "boolean" Disables the Int10 module, a module that uses the int10 call to the BIOS=20 of the graphics card to initialize it. Default: false. I'm still thinking that the cause of the screen blanking is due to the=20 driver which try to restore the console in VGA text mode at shutdown. C=E9dric |
From: <han...@sa...> - 2005-08-08 12:25:38
|
Hi, I disabled NVRestore from the nv driver, and now the monitor won't go to=20 sleep anymore, however the picture on the monitor freezes (all movement=20 stops), the mouse-pointer dissapears, and input from the keyboard is not=20 accepted anymore. As soon as I stop the second X server, activity on the first X server=20 resumes (mouse and keyboad become active again). So things are moving in=20 the right direction. Would you have any idea what to do about the=20 freezing of the mouse/keyboad? Thanks, Hans >=20 > After reading vgahw, radeon and nv source code, it seems to me that both > problems (blanc screen and DPMS) are related to vgahw functions call. >=20 > I'm afraid there's no solution with the stock drivers because I presume > there is a ressource conflict on VGA IOs between the two cards. >=20 > I would suggest to use a modified nv driver for the secondary card to > prevent messing the primary card settings. I guess the function=20 > NVRestore should be disabled to prevent the blank the screen at shutdown.= =20 > As for DPMS, I didn't look at it yet. >=20 > 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 |
From: <ce...@ri...> - 2005-08-10 02:29:15
|
han...@sa... a =E9crit : > I disabled NVRestore from the nv driver, and now the monitor won't go t= o=20 > sleep anymore, however the picture on the monitor freezes (all movement= =20 > stops), the mouse-pointer dissapears, and input from the keyboard is no= t=20 > accepted anymore. >=20 > As soon as I stop the second X server, activity on the first X server=20 > resumes (mouse and keyboad become active again). So things are moving i= n=20 > the right direction. Would you have any idea what to do about the=20 > freezing of the mouse/keyboad? Did you disable NVSync() and NVLockUnlock() issued at the same time ? if=20 not, try to suppress them. C=E9dric |
From: <han...@sa...> - 2005-08-10 08:07:17
|
Hi, Well. This is now getting frustrating ;) I returned both NVIDIA cards yesterday, after a long futile fight with them, but of course I never tried the -sharevts option. Can you confirm that you have both NVIDIA cards up and running with all features (TV-out, and 3D-accelleration)? And can you also confirm that without the -sharevts option, you have a similar screen blanking problem then the one described by me? If yes, I just might go get some new NVIDIA cards ;) Thanks for the reply, Hans > I am running two Nvidia cards (two FX5200, AGP and PCI) with the > closed source driver from Nvidia without problems. I'm currently > using the 7667/amd64 version, but I've been running with these two > cards for some time now. (They used to sit in a standard x86-box.) > > I'm using the stock Ubuntu X.org (or, rather, I used to do so; I've > had to recompile it to not ignore key 103 when using the evdev > keyboard driver). Are you using the -sharevts option when running the > second X server? > > > Arne. > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices > Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > _______________________________________________ > Linuxconsole-dev mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxconsole-dev |
From: Arne G. G. <ar...@li...> - 2005-08-10 16:56:58
|
* han...@sa... > Hi, > > Well. This is now getting frustrating ;) I returned both NVIDIA cards > yesterday, after a long futile fight with them, but of course I never > tried the -sharevts option. Can you confirm that you have both NVIDIA > cards up and running with all features (TV-out, and 3D-accelleration)? $ DISPLAY=:0 glxinfo | grep OpenGL OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce FX 5200/AGP/SSE2 OpenGL version string: 2.0.0 NVIDIA 76.67 OpenGL extensions: $ DISPLAY=:1 glxinfo | grep OpenGL OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce FX 5200/PCI/SSE2 OpenGL version string: 2.0.0 NVIDIA 76.67 OpenGL extensions: $ glxgears 3773 frames in 5.0 seconds = 754.600 FPS 3798 frames in 5.0 seconds = 759.600 FPS I don't personally use the acceleration very heavily, so I've no idea if the glxgears number is impressive or not. At least the acceleration seems to be enabled. (The PCI card actually shows better numbers than the AGP card. Odd.) I use S-video out only on the PCI card, but that works. I believe I have tested the AGP card and found that to work as well, without being 100% sure. My only beef with the cards has been that I'm somehow unable to get DVI out to work properly on the PCI card, but I have no reason to suspect that this is caused by the multihead configuration. (Nvidia claims to have fixed some 1600x1200 DVI issues in the latest drivers, but I haven't yet had the time to see if this makes any difference.) > And can you also confirm that without the -sharevts option, you have a > similar screen blanking problem then the one described by me? If yes, I > just might go get some new NVIDIA cards ;) Starting the second head X without the -sharevts option causes the primary head to blank/poweroff, image returns when second head is terminated. As Cédric Rivard says, the -sharevts-option is an extension found (at least) in the Ubuntu and Debian versions of X.org 6.8.2. (Without this option, I believe you need the ruby kernel patches to get around precisely the problem seen above.) Arne. |
From: Hugo V. <hvw...@ya...> - 2005-08-10 18:36:03
|
--- Arne Georg Gleditsch <ar...@li...> wrote: > * han...@sa... > > Hi, > > > > Well. This is now getting frustrating ;) I > returned both NVIDIA cards > > yesterday, after a long futile fight with them, > but of course I never > > tried the -sharevts option. Can you confirm that > you have both NVIDIA > > cards up and running with all features (TV-out, > and 3D-accelleration)? I got into this discussion late, so I apologize if this has been covered already or is not applicable, but I also have NVIDIA cards, no fancy ones, TNT2 AGP and MX-440 PCI. When I turn on acceleration with any NVIDIA driver under Ruby the driver loops. It is discussed here: http://www.nvnews.net/vbulletin/showthread.php?t=31858&page=22&pp=15&highlight=loop I gather it is mobo related. I would have to put my old K7A back in again, to find out :-( Hugo ____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs |
From: <han...@sa...> - 2005-08-10 08:26:54
|
Hi again, Where do you actually get the -sharevts option from? It doen't seem to be a standard x.org commandline option, and I can't find anything about it in NVIDIAS driver readme either..? -Hans > > I am running two Nvidia cards (two FX5200, AGP and PCI) with the > closed source driver from Nvidia without problems. I'm currently > using the 7667/amd64 version, but I've been running with these two > cards for some time now. (They used to sit in a standard x86-box.) > > I'm using the stock Ubuntu X.org (or, rather, I used to do so; I've > had to recompile it to not ignore key 103 when using the evdev > keyboard driver). Are you using the -sharevts option when running the > second X server? > > > Arne. > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices > Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > _______________________________________________ > Linuxconsole-dev mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxconsole-dev |
From: <ce...@ri...> - 2005-08-10 09:42:22
|
Le Mercredi 10 Ao=FBt 2005 10:26, han...@sa... a =E9crit=A0: > Hi again, > > Where do you actually get the -sharevts option from? It doen't seem to > be a standard x.org commandline option, and I can't find anything about > it in NVIDIAS driver readme either..? In Debian and Ubuntu Xorg source package: 013_novtswitch.diff and 018_sharevts_option.diff C=E9dric |
From: <han...@sa...> - 2005-08-11 09:19:58
|
Hi, Thanks for all the information. I have now once again ordered new NVIDIA=20 cards, but it will take about 2 days for them to arrive (if the shop=20 still wants to sell them to me, after I returned the previous cards ;)) In the meantime I have tried to get a dual-session setup working with a=20 Radeon 7500 PCI and a Radeon x300 PCI-E, but this seems to be even more=20 painfull then with the NVIDIAS: The 7500 PCI requires me to run the=20 latest CVS snapshot of x.org to get tv-out working, and for the x300 I=20 have to run x.org 6.8.2 with ATI's binary fglrx driver, which also still=20 seems to be very buggy (can't get dual-head monitors working correctly).=20 Additionally the setup has the same blanking problem then with the=20 NVIDIA cards. I'll let you know if I have any luck with the -sharevts option. These=20 two days of waiting for the NVIDIA cards are going to do me good I=20 think, during the last week I have been ripping all of the hair from my=20 head ;) -Hans >=20 > $ DISPLAY=3D:0 glxinfo | grep OpenGL > OpenGL vendor string: NVIDIA Corporation > OpenGL renderer string: GeForce FX 5200/AGP/SSE2 > OpenGL version string: 2.0.0 NVIDIA 76.67 > OpenGL extensions: > $ DISPLAY=3D:1 glxinfo | grep OpenGL > OpenGL vendor string: NVIDIA Corporation > OpenGL renderer string: GeForce FX 5200/PCI/SSE2 > OpenGL version string: 2.0.0 NVIDIA 76.67 > OpenGL extensions: > $ glxgears=20 > 3773 frames in 5.0 seconds =3D 754.600 FPS > 3798 frames in 5.0 seconds =3D 759.600 FPS >=20 > I don't personally use the acceleration very heavily, so I've no idea > if the glxgears number is impressive or not. At least the > acceleration seems to be enabled. (The PCI card actually shows better > numbers than the AGP card. Odd.) >=20 > I use S-video out only on the PCI card, but that works. I believe I > have tested the AGP card and found that to work as well, without being > 100% sure. >=20 > My only beef with the cards has been that I'm somehow unable to get > DVI out to work properly on the PCI card, but I have no reason to > suspect that this is caused by the multihead configuration. (Nvidia > claims to have fixed some 1600x1200 DVI issues in the latest drivers, > but I haven't yet had the time to see if this makes any difference.) >=20 > > And can you also confirm that without the -sharevts option, you have a= =20 > > similar screen blanking problem then the one described by me? If yes, I= =20 > > just might go get some new NVIDIA cards ;) >=20 > Starting the second head X without the -sharevts option causes the > primary head to blank/poweroff, image returns when second head is > terminated. >=20 > As C=E9dric Rivard says, the -sharevts-option is an extension found (at > least) in the Ubuntu and Debian versions of X.org 6.8.2. (Without > this option, I believe you need the ruby kernel patches to get around > precisely the problem seen above.) >=20 >=20 > =09=09=09=09=09=09=09Arne. >=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 |
From: <han...@sa...> - 2005-08-12 13:05:31
|
Hi, I'm very happy to report that the Ubuntu 013_novtswitch and=20 018_sharevts_option patches did the trick! Right now I have a dual-session setup running with an=20 Geforece 6600 PCI-E, and a Radeon 7500 PCI. Both sessions work perfectly, and the=20 screenblanking has dissapeared. The patches were fairly easy to apply against the gentoo 6.8.2-r2 x.org=20 source tree. There was only one trivial reject with the sharevts_option patch, which was=20 very easy to fix manually. Now I can't wait to get my Geforce 5200 PCI at the beginning of next=20 week, I have every reason to be optimistic about it working just as well as the radeon 7500=20 (and even if it wouldn't work, I can live with the radeon ;)). So once again, thanks to everyone who has helped me here, and specifically = to Cedric for providing me with so many tips and ideas + the needed patches! -Hans >=20 > $ DISPLAY=3D:0 glxinfo | grep OpenGL > OpenGL vendor string: NVIDIA Corporation > OpenGL renderer string: GeForce FX 5200/AGP/SSE2 > OpenGL version string: 2.0.0 NVIDIA 76.67 > OpenGL extensions: > $ DISPLAY=3D:1 glxinfo | grep OpenGL > OpenGL vendor string: NVIDIA Corporation > OpenGL renderer string: GeForce FX 5200/PCI/SSE2 > OpenGL version string: 2.0.0 NVIDIA 76.67 > OpenGL extensions: > $ glxgears=20 > 3773 frames in 5.0 seconds =3D 754.600 FPS > 3798 frames in 5.0 seconds =3D 759.600 FPS >=20 > I don't personally use the acceleration very heavily, so I've no idea > if the glxgears number is impressive or not. At least the > acceleration seems to be enabled. (The PCI card actually shows better > numbers than the AGP card. Odd.) >=20 > I use S-video out only on the PCI card, but that works. I believe I > have tested the AGP card and found that to work as well, without being > 100% sure. >=20 > My only beef with the cards has been that I'm somehow unable to get > DVI out to work properly on the PCI card, but I have no reason to > suspect that this is caused by the multihead configuration. (Nvidia > claims to have fixed some 1600x1200 DVI issues in the latest drivers, > but I haven't yet had the time to see if this makes any difference.) >=20 > > And can you also confirm that without the -sharevts option, you have a= =20 > > similar screen blanking problem then the one described by me? If yes, I= =20 > > just might go get some new NVIDIA cards ;) >=20 > Starting the second head X without the -sharevts option causes the > primary head to blank/poweroff, image returns when second head is > terminated. >=20 > As C=E9dric Rivard says, the -sharevts-option is an extension found (at > least) in the Ubuntu and Debian versions of X.org 6.8.2. (Without > this option, I believe you need the ruby kernel patches to get around > precisely the problem seen above.) >=20 >=20 > =09=09=09=09=09=09=09Arne. >=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 ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Linuxconsole-dev mailing list Lin...@li... https://lists.sourceforge.net/lists/listinfo/linuxconsole-dev |
From: <han...@sa...> - 2005-08-23 22:13:38
Attachments:
013_novtswitch.diff.gz
018_sharevts_option.diff.gz
|
Hi, You need to apply the attached patches to your x.org 6.8.2 source tree, and recompile. The options should work after that. -Hans > Hi, > > I am having the same problem with the two NVidia cards > GeForce4 MX4000 AGP 8x and GeForce FX5200 PCI on > Debian unstable with Ruby patched kernel 2.6.12. I am > using the NVidia driver version 7676. > > I read somewhere that I should use the -sharevts > option when starting the second X server. I tried, but > this option is not recognized. How should I do this? > > Thanks a bunch! > > Andrej > > --- han...@sa... wrote: > > > > > Hi! > > > > I have 1 NVIDIA Gefore FX 5200 PCI, and one NVIDIA > > Gefore 6600 PCI-E > > card. I have both X servers set up correctly so that > > they run without > > any problem seperatly (with different keyboards and > > mice). Both X > > servers use the nvidia close source 6629 driver. > > > > My problem is that whenever I try to start the > > second X server, while > > the first one is already running, the monitor > > connected to the first X > > server goes black (monitor is turned off/signal > > lost). The xserver > > itself however continues running, and all > > applications (like music from > > xmms) also continue running. There are no errors in > > any log files. There > > is no difference when trying to start the X servers > > in the opposite > > order. Starting the second X server always kills the > > display of the one > > already running. > > > > I have tried to turn the monitor back on with "xset > > dpms dorce on > > -display :0.0", but this doesn't help. > > > > I'm running x.org 6.8.2 with the IsloateDevice > > patch. I'm actually not > > running ruby anymore, but I'm using the evdev driver > > for the separate > > keyboards/mice > > (https://bugs.freedesktop.org/show_bug.cgi?id=968), > > so in > > a sence I'm posting to the "wrong" list, but I guess > > people here are the > > most experienced with these kind of setups. > > > > The PCI card is also set as the primary graphics > > card in bios, otherwise > > it didn't work at all. > > > > Thanks for any help on this! > > > > -Hans > > > > > > > > > ------------------------------------------------------- > > SF.Net email is Sponsored by the Better Software > > Conference & EXPO > > September 19-22, 2005 * San Francisco, CA * > > Development Lifecycle Practices > > Agile & Plan-Driven Development * Managing Projects > > & Teams * Testing & QA > > Security * Process Improvement & Measurement * > > http://www.sqe.com/bsce5sf > > _______________________________________________ > > Linuxconsole-dev mailing list > > Lin...@li... > > > https://lists.sourceforge.net/lists/listinfo/linuxconsole-dev > > > > > > > ___________________________________________________________ > To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices > Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > _______________________________________________ > Linuxconsole-dev mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxconsole-dev |
From: <ce...@ri...> - 2005-08-08 07:53:37
|
han...@sa... a =E9crit : > 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 work. >=20 > 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. >=20 > 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 results. After reading vgahw, radeon and nv source code, it seems to me that both problems (blanc screen and DPMS) are related to vgahw functions call. I'm afraid there's no solution with the stock drivers because I presume there is a ressource conflict on VGA IOs between the two cards. I would suggest to use a modified nv driver for the secondary card to prevent messing the primary card settings. I guess the function=20 NVRestore should be disabled to prevent the blank the screen at shutdown.=20 As for DPMS, I didn't look at it yet. C=E9dric |