> Can you try going back to init 3 and run sax2 –r –m 0=nvidia.
> Try to accept all and if your prompted by sax2 for a test just don’t
> bother but save.
This left me with a single screen. First monitor works fine, second
monitor goes inactive (“no signal” message) as soon as I switch to
RL5. (In text mode, it always mirrors the first one.)
Also, after logging in Gnome complains:
The X system keyboard settings differ from your current GNOME
Expected model “pc105”, layout “de nodeadkeys” and options
“compose compose:rwin eurosign eurosign:e”, but the following
settings were found: model “microsoftpro”, layout “de nodeadkeys”
and no options.
Which set do you want to use?
[Use X Settings] [Keep GNOME Settings]
(Translated back from German.)
> try going back to run level 5
> and login to your user, then as su run the nvidia-settings.
nvidia-settings produced a bunch of complaints:
ERROR: Invalid X Screen 1 specified on line 51 of configuration file
‘/root/.nvidia-settings-rc’ (there is only 1 X Screen on this Display).
with the line number incrementing from 51 to 80 but then came up fine.
My first screen “Philips 22SW (DFP-0 on GPU-0)” (the working one) was
set to “Configuration: Separate X screen” with no way to change it,
the alternatives “Disabled” and “TwinView” being both greyed out.
The second screen “Acer AL1721 (DFP-1 on GPU-0)” appeared with
“Configuration: Disabled”, with both alternatives “Separate X Screen”
and “TwinView” available.
> Try using the separate
> independent screen (not xinerama I guess) set your default monitor and
> all the other stuff e.g.: resolution/refresh rate then save it without
> merging with the existing xorg configuration, then restart x to see if
> there is changes.
For the first test I set my second screen to “Separate X screen” just
like the first one, clicked “Save to X Configuration File”, keeping
the filename /etc/X11/xorg.conf but removing the checkmark from
“Merge with existing file”. The checkmark for “Xinerama” was not set,
and I left it that way. After restarting X, the second screen was
black but active, and after logging back in it came up as a second
display (:0.1) with its own desktop icons and menu bar. Problem #1
was gone (ie. the opensuse-updater minimized fine into the systray)
but the keyboard warning came up again, this time telling me
“found layout: us”, and my keyboard layout was indeed set to US no
matter whether I answered “keep Gnome settings” or “use X settings”.
Problems #2 (“Computer” button on screen 1 opening the Gnome menu on
screen 0) and #4 (Firefox on screen 0 not accepting requests from
screen 1) were still present. I didn’t have the patience to test
problem #3 (screen saver) because it was just too annoying to type
with the wrong kezboard lazout. (The US layout exchanges y and z
with respect to the German one.) Oh yes, the screens were also
arranged the wrong way (moving the mouse beyond the right border of
the first screen made it reenter on the left side of the second screen
which is actually situated to the left of the first one) with no
obvious means of correcting that.
I then ran nvidia-settings again (unsurprisingly, there were no
“Invalid X Screen” warnings this time) and changed the first screen
from “Separate screen” to “TwinView” which automatically changed the
second one to “TwinView” too, and also made an option “Position”
appear, allowing me to specify that my second screen is to the left of
the first one. Again I saved without merging and restarted X. Again,
the keyboard warning and the bad kezboard lazout. But this time, I had
a single X display (:0.0) covering both screens and arranged correctly
too, hence problems #2 and #4 were gone. (I assume #3 was gone, too,
but once again I wasn’t patient enough to test it.)
At that point, in order to fix the kezboard issue, I tried starting
over with sax2 -r in RL3, but this time, against your advice, clicking
“Change Configuration” in sax2 and setting the correct keyboard
parameters. This avoided the first “keyboard settings” warning, but
after running nvidia-settings and saving without merging, my keyboard
layout was again back to US.
Next I attempted to set the correct keyboard mapping in the Gnome
control center. That did not have any effect at all except changing
the “expected” part in the “keyboard settings” warning after logon.
Then I changed the keyboard settings in YaST - Select Keyboard Layout
(which is really just SaX2 in disguise). This worked, but at the same
time broke the dual screen configuration, ie. after the next X restart
the second screen stayed black again.
So finally I resorted to running nvidia-settings and afterwards
editing /etc/X11/xorg.conf manually to change
generated from default
Option “Protocol” “Standard”
Option “XkbLayout” “de”
Option “XkbModel” “pc105”
Option “XkbOptions” “Compose,compose:rwin,eurosign:e”
Option “XkbRules” “xfree86”
Option “XkbVariant” “nodeadkeys”
That seems to have done the trick for the keyboard at least, but after
looking inside the various xorg.conf files created during the tests
above I am a bit nervous about other entries in the SaX2 generated
ones which are missing from those by nvidia-settings, such as FontPath
and Mouse Option lines.
> With your #4. question in the first post, I am experiencing it too.
> Seems that you can only open firefox in one screen and won’t allow a
> second on the second screen.
I could live with that if communication between the two screens worked,
so that for example Thunderbird from one screen could ask Firefox on
the other one to open a link.
> Before I can open two instances of firefox
> in the first screen and just drag it with mouse in the second screen
> which will not let me do it anymore.
With TwinView, that works. So it seems like TwinView is the way to go.
> On the side. I never touch sax2 with my nvidia card and rely in the
> nvidia-settings to configure it.
The trouble with nvidia-settings is that it always blindly sets the
keyboard layout to “US”, which is somewhat inconvenient for owners
of non-US keyboards like me.
> Sax2/yast2 doesn’t recognize my nvidia
> 7300 gt.
On my system, SaX2 pretends to recognize the nVidia card but
invariably breaks any dual-screen configuration I might have set up.
So in sum, the solution seems to be:
- use TwinView
- create your xorg.conf manually by merging the best parts from what
nvidia-settings and sax2 generate
Not very satisfying, but apparently the best we can do.