First one is how do i run the nvidia settings as root in 11.1 ive tried nvidia-config and nvidia-xconfig but they fail to load the nvidia settings, i am trying to set up a dual monitor using my HD 37" plasma tv as a second monitor
secondly how do i enable compiz to load at startup?
Thanks in advance
If you don’t care to use the terminal just log in as root, then you can use the nvidia-settings graphics front-end.
In KDE there is a menu item in utilities called Desktop effects. There’s something similar in gnome.
@brunomcl Please DO NOT recommend logging in as root! The results can be disastrous.
To run the settings as root open a console and type sudo nvidia-xconfig
or sudo nvidia-settings
/Geoff
If I may, logging in as root is not this all-inclusive disaster. For these quick maintenance tasks it’s perfectly OK, and much easier for someone not used to the command line.
Everytime we use su, sudo or yast we are running things with root privileges. The consequences can be as “disastrous” as running the same tasks logged as root.
Please note that I’m not recommending that you start browsing the internet or add unverified repositories or run closed binaries as root, just the easier way to set your xorg.conf with a GUI. Sure you can do it from the command line, if you know how to use su/sudo, the name of the executable, etc. But if you don’t, it may make a simple thing get frustrating.
Also, something just occurred me. It may be more dangerous to teach a new user to run an executable using su/sudo than as root. The user may get used to run stuff he downloads this way, something like “hey, this program I installed is not running, I’ll try as sudo like I learned in the forum.”
OTOH, logging as root makes me more conscious of the ‘unusualness’ of the situation - the non-customized desktop, the very explicit bomb wallpaper, etc. It makes me want to do what I came to do and get out fast.
What do you think?
This is not true running a console or Yast as su or with root privileges is NOT the same as logging in as root.
Have a read here.
What you do is up to you but please don’t recommend it to others.
Why do you think windows is so susceptible to attacks…might it be because most users run there machines with admin privileges
/Geoff
While being so careful do you also watch out for the hackers turning you machine into a spam bot?
/Geoff
geoffro, please don’t be upset. My intention is not to contradict anyone, and certainly not someone as experienced as you. And yes, I understand the differences of running as root vs escalated privileges (or at least I think I do).
However, I also understand that opensuse sets root account for maintenance tasks, and the case in question is one. If the root account should never be used it shouldn’t be there, as some distros do.
I have used the root account maybe three times during the last three years, and the last time was exactly for this, to allow the nvidia program to change xorg.conf after a change of monitors.
Again, I’m not advocating the indiscriminate use o root, but it has it’s uses. Just that.
While being so careful do you also watch out for the hackers turning you machine into a spam bot?
I suppose watching out for unusual network activity counts? And running clamav sporadically? If I don’t run any servers in a home machine am I heading for disaster just by logging into root?
Well, I’m not looking for a flame, nor trying to be ironic. Again, my apologies. I’ll refrain from posting this sort of thing again.
Thanks for the replies guy’s but i feel none the wiser, i am aware of what can happen if i run as root, i am still unable to find an answer to my original question.
Thanks
brunomcl wrote:
> geoffro, please don’t be upset. My intention is not to contradict
> anyone, and certainly not someone as experienced as you. And yes, I
> understand the differences of running as root vs escalated privileges
> (or at least I think I do).
>
> However, I also understand that opensuse sets root account for
> maintenance tasks, and the case in question is one. If the root account
> should never be used it shouldn’t be there, as some distros do.
>
> I have used the root account maybe three times during the last three
> years, and the last time was exactly for this, to allow the nvidia
> program to change xorg.conf after a change of monitors.
>
> Again, I’m not advocating the indiscriminate use o root, but it has
> it’s uses. Just that.
>
> Code:
> --------------------
> While being so careful do you also watch out for the hackers turning
> you machine into a spam bot?
> --------------------
>
> I suppose watching out for unusual network activity counts? And running
> clamav sporadically? If I don’t run any servers in a home machine am I
> heading for disaster just by logging into root?
>
> Well, I’m not looking for a flame, nor trying to be ironic. Again, my
> apologies. I’ll refrain from posting this sort of thing again.
Frankly, the dogma that one must never login as root strikes me as pure
paranoia. I think you made a very valid point with your observation that
the red wallpaper with all those bombs reminds you to be careful. It is a
visual reminder, making it more difficult to “forget” you are running with
root privileges. It is far from perfect, of course, since simply running
the application maximized or in full screen mode tends to hide that “scary”
wallpaper! But it is a bit more than the visual reminder you get when
running in a console.
The points on which I think we would all agree is that one must be careful
when running with root privileges. Giving root privileges to any
application that does not require them is complete folly. When root
privileges are required, one should obtain them in some way, do what needs
to be done, and then immediately relinquish those privileges.
Forgetting that last part is where one is asking for disaster, regardless of
how those privileges are obtained. IMHO, this is the root cause of the
paranoia surrounding the concept of “login as root”. One just might not
remember to log out, and continue to run other applications! OTOH, the
same problem exists when using “su” in console if you forget to exit.
Which is worse? Chevy or Ford?
There is, however, another aspect to this that concerns me more than the
question whether one should ever login as root. In order to avoid this
issue, more and more applications (such as YaST) are prompting for the root
password so they can obtain root privileges for themselves. Great idea? I
wonder. Inexperienced users (and even experienced ones for that matter)
seem happy to provide that password without hesitation. Why? Because it
is quick, easy, and socially acceptable (since they are admonished over and
over again that to login as root is “bad”). And these applications are
completely trustworthy, right?
A major security problem we see in Windows is that it is very common for the
user to be running everything with “administrative” privileges (whatever
that actually means). Some equate this to logging in as root. Perhaps
this is the true basis of the admonishion. But as more and more casual
linux users get accustomed to providing the root password to every
application that prompts for it, their systems are no more secure than any
other. How long will it be before some game program comes along prompting
for the root password? It’s a mute question, I suppose, since the same
users who would respond to that prompt would just as happily log in as root
if that was required to play the latest game.
I guess my point is that you are fooling yourself if you think your system
is safe simply because you never login as root. That is well down on the
list of concerns I have for things that might compromise my system!
There! I’ve given my opinion. Flame away! Only it probably should be in
some other forum, as I fail to see how this concerns “hardware”. 
The real problem is apathy. If only we could get people to wake up and
realize we could solve the problems in the whole world if we all simply
showed some concern about them! Oh, who cares anyway? Forget about it.
Ok so ive kinda solved 1 problem, i have dual setup on the laptop and tv, ONLY i cant change the tv resolution to 1280x800 its default 1280x768 in Suse and my HD tv reolution is 1920x1080 and i cant seem to change the HD format to 1080p its currently 720p i cant seem to change it via nvidia settings does it have to be changed by editing the xorg file?
Thanks
First check if it is not a limitation of the tv-out hardware on your video card. I’m presuming the primary display (vga-out) can run at the resolution you want.
Inability to set supported freqs/resolutions mean that the display isn’t correctly described in xorg.conf, mostly because it was not correctly detected (happens mostly with new or rare devices).
If not, you have to configure the display (option “PreferredMode” in section “Monitor”) to support this resolution in xorg.conf. It is not an obvious setting, as the resolution/frequency descriptions are a bit cryptic. This can be done by selecting the correct (or a compatible) display adapter in yast, and cloning it’s definitions to the second display sections/options in xorg.conf. for example, in my xorg.conf I have:
Section "Monitor"
Option "CalcAlgorithm" "XServerPool"
DisplaySize 408 255
HorizSync 30-83
Identifier "Monitor[0]"
ModelName "AOC 912VWA"
Option "DPMS"
Option "PreferredMode" "1440x900"
VendorName "AOC"
VertRefresh 43-75
UseModes "Modes[0]"
EndSection
Section "Modes"
Identifier "Modes[0]"
Modeline "1440x900" 106.00 1440 1520 1672 1904 900 903 909 934
EndSection
There are also issues with high frequencies on analog TV’s, but I think that with LCD panels you are safe if you stay with 60 Hz. Anyway check your TV specs.
It will take some learning, but it’s not that hard.
Thanks for the reply, i have connected the laptop via HDMI her is my my xorg.conf file output
Section “ServerLayout”
Identifier “Layout[all]”
Screen 0 “Screen0” 0 0
InputDevice “Keyboard[0]” “CoreKeyboard”
InputDevice “Mouse[1]” “CorePointer”
InputDevice “Mouse[3]” “SendCoreEvents”
Option “Clone” “off”
Option “Xinerama” “off”
EndSection
Section “Files”
InputDevices “/dev/gpmdata”
InputDevices “/dev/input/mice”
FontPath “/usr/share/fonts/misc:unscaled”
FontPath “/usr/share/fonts/local”
FontPath “/usr/share/fonts/75dpi:unscaled”
FontPath “/usr/share/fonts/100dpi:unscaled”
FontPath “/usr/share/fonts/Type1”
FontPath “/usr/share/fonts/URW”
FontPath “/usr/share/fonts/Speedo”
FontPath “/usr/share/fonts/PEX”
FontPath “/usr/share/fonts/cyrillic”
FontPath “/usr/share/fonts/latin2/misc:unscaled”
FontPath “/usr/share/fonts/latin2/75dpi:unscaled”
FontPath “/usr/share/fonts/latin2/100dpi:unscaled”
FontPath “/usr/share/fonts/latin2/Type1”
FontPath “/usr/share/fonts/latin7/75dpi:unscaled”
FontPath “/usr/share/fonts/baekmuk:unscaled”
FontPath “/usr/share/fonts/japanese:unscaled”
FontPath “/usr/share/fonts/kwintv”
FontPath “/usr/share/fonts/truetype”
FontPath “/usr/share/fonts/uni:unscaled”
FontPath “/usr/share/fonts/CID”
FontPath “/usr/share/fonts/ucs/misc:unscaled”
FontPath “/usr/share/fonts/ucs/75dpi:unscaled”
FontPath “/usr/share/fonts/ucs/100dpi:unscaled”
FontPath “/usr/share/fonts/hellas/misc:unscaled”
FontPath “/usr/share/fonts/hellas/75dpi:unscaled”
FontPath “/usr/share/fonts/hellas/100dpi:unscaled”
FontPath “/usr/share/fonts/hellas/Type1”
FontPath “/usr/share/fonts/misc/sgi:unscaled”
FontPath “/usr/share/fonts/xtest”
FontPath “/opt/kde3/share/fonts”
EndSection
Section “Module”
Load “glx”
Load “dbe”
Load “extmod”
Load “dri”
Load “freetype”
EndSection
Section “ServerFlags”
Option “AllowMouseOpenFail” “on”
Option “ZapWarning” “on”
Option “Xinerama” “0”
EndSection
Section “InputDevice”
Identifier “Keyboard[0]”
Driver “kbd”
Option “Protocol” “Standard”
Option “XkbLayout” “gb”
Option “XkbModel” “microsoftpro”
Option “XkbRules” “xfree86”
EndSection
Section “InputDevice”
Identifier “Mouse[1]”
Driver “mouse”
Option “Buttons” “14”
Option “Device” “/dev/input/mice”
Option “Name” “Logitech USB Receiver”
Option “Protocol” “explorerps/2”
Option “Vendor” “Sysp”
Option “ZAxisMapping” “4 5”
EndSection
Section “InputDevice”
Identifier “Mouse[3]”
Driver “synaptics”
Option “Buttons” “5”
Option “Device” “/dev/input/mice”
Option “Emulate3Buttons” “on”
Option “HorizScrollDelta” “0”
Option “InputFashion” “Mouse”
Option “Name” “Synaptics;Touchpad”
Option “Protocol” “explorerps/2”
Option “SHMConfig” “on”
Option “Vendor” “Sysp”
Option “ZAxisMapping” “4 5”
EndSection
Section “Modes”
Identifier “Modes[0]”
EndSection
Section “Monitor”
Identifier “Monitor[0]”
VendorName “–> LCD”
ModelName “1280X800@60HZ”
UseModes “Modes[0]”
DisplaySize 305 230
HorizSync 30.0 - 52.0
VertRefresh 50.0 - 60.0
Option “CalcAlgorithm” “XServerPool”
Option “DPMS”
Option “PreferredMode” “1280x800”
EndSection
Section “Monitor”
Identifier “Monitor0”
VendorName “Unknown”
ModelName “LPL”
HorizSync 30.0 - 75.0
VertRefresh 60.0
EndSection
Section “Device”
Identifier “Device[0]”
Driver “nvidia”
VendorName “NVIDIA”
BoardName “GeForce 8400M GS”
Option “SaXDualHead”
Option “TwinView”
Option “SaXDualMonitorVendor” “–> VESA”
Option “SecondMonitorHorizSync” “31-50”
Option “SaXDualVSync” “50-60”
Option “MetaModes” “1280x800,1280x800;1280x768,1280x768;1280x720,1280x720;1024x768,1024x768;1280x600,1280x600;1024x600,1024x600;800x600,800x600;768x576,768x576;640x480,640x480”
Option “SaXDualOrientation” “RightOf”
Option “SaXDualResolution” “1280x800”
Option “TwinViewOrientation” “RightOf”
Option “SaXDualMode” “Xinerama”
Option “SecondMonitorVertRefresh” “50-60”
Option “SaXDualHSync” “31-50”
Option “SaXDualMonitorModel” “1024X768@60HZ”
Screen 0
EndSection
Section “Device”
Identifier “Device0”
Driver “nvidia”
VendorName “NVIDIA Corporation”
BoardName “GeForce 8400M GS”
EndSection
Section “Screen”
Identifier “Screen[0]”
Device “Device[0]”
Monitor “Monitor[0]”
DefaultDepth 24
SubSection “Display”
Depth 15
Modes “1280x800” “1280x768” “1280x720” “1024x768” “1280x600” “1024x600” “800x600” “768x576” “640x480”
EndSubSection
SubSection “Display”
Depth 16
Modes “1280x800” “1280x768” “1280x720” “1024x768” “1280x600” “1024x600” “800x600” “768x576” “640x480”
EndSubSection
SubSection “Display”
Depth 24
Modes “1280x800” “1280x768” “1280x720” “1024x768” “1280x600” “1024x600” “800x600” “768x576” “640x480”
EndSubSection
SubSection “Display”
Depth 8
Modes “1280x800” “1280x768” “1280x720” “1024x768” “1280x600” “1024x600” “800x600” “768x576” “640x480”
EndSubSection
EndSection
Section “Screen”
Identifier “Screen0”
Device “Device0”
Monitor “Monitor0”
DefaultDepth 24
Option “TwinView” “1”
Option “metamodes” “DFP-0: 1280x800 +0+0, DFP-1: 1280x720 +0+0; DFP-0: NULL, DFP-1: 1280x720 +0+0; DFP-0: 1024x768 +0+0, DFP-1: NULL; DFP-0: 640x480 +0+0, DFP-1: 640x480 +640+0”
SubSection “Display”
Depth 24
EndSubSection
EndSection
Section “Extensions”
Option “Composite” “on”
EndSection
Larry, thanks. I was starting to feel a complete idiot, as opposed to the half-baked one I know I am. 
I see the root account as valid only for those graphics apps that need root privileges but can’t be integrated in yast because they are not F/OSS, such as nvidia setting. But, it may be a better idea suggest to newcomers to edit the launch icon (or create a new one) for the app that runs ‘sudo appname’, or “kdesu appname” instead of running root. At least it would keep the paranoids (just kidding ) happy.
Well, for starters resolutions above 800 lines are out. Is this a hardware limitation? Do you want 1080 lines tv-out or just 800 instead of 768?
Also the Modes section is empty. I don’t now if it’s necessary or not, you should research this.
If Xinerama is disabled, why this?
Option "SaXDualMode" "Xinerama"
You may want to research this option. Your answer is probably here:
Option "SaXDualMonitorModel" "1024X768@60HZ"
But don’t go changing it indiscriminately, you’ll only get Xserver not running.
Good luck!