On Tue, 2006-01-17 at 22:18 -0500, BandiPat wrote:
That command will make it do a new search. You can also do sax2 -p,
Well, the mga card is there listed, as 0, with the nvidia as 1
which will give you info on what sax2 has found in the system either in PCI or AGP or both. Might be a good idea to try that first just to see if it's finding your card/s.
Since you are using a LCD monitor and I've found those can be somewhat problematic for sax2, you might also try sax2 -l, to see if using a lores screen will get into the setup gui.
Playing with variations, -m 0=mga,1=nvidia or nv at least things didn't lock up, but sax2 exited without being able to proceed. Varying the input to -m 0=mga brought up both screens and identified the cards properly and allowed me to configure, both from the command line in runlevel 3,and also from within the gui as a yast module. So we make some progress. BUT this sets up the mga screen to be the primary video screen - which I don't want, I want the AGP slot nvidia to be the primary screen. Even more oddly, when running xwindows session on the mga card, that screen is in the xwindows, and the nvidia monitor is still showing the command prompt login, which I can switch back to using ctrl-alt-fx key - I started x windows from a user login on alt-f2 in this case. Now I can see this being occassionally useful >;) setup in such a way (allowing one to have a gui display with say a help manual displayed and a nice command line on the other monitor) but it is not, generally, how I would like to have things when I run the twin monitor. I set up the two monitors to be two independent displays, then I use a kvm switch onthe second monitor to be able ti display independently the output from a second computer, when I want to. Works nicely like that. I've had a look at the yast modules and there seems to be no option for telling it which monitor to use as the default, but I'm sure I've seen this in the past! Wheres it gone?? Also now that I remember it, when I did the yast setup, it didn't show any display on the nvidia despite it being identified as an active display. Hmmm. Its all gotta be in some config files somewhere - but where? And in what form?