I’ve loaded OpenSuSE 13.2, having previously run openSuSE 12.2, and now have a problem getting the correct screen size (1680x1050) displayed.
I connect to my monitor via a KVM switch. It’s possible to load the EDID from the monitor into the KVM switch, which I have done. In theory, now, if X is set to auto-detect the screen size, my screen should display correctly. This works with the driver as supplied, but when I switch to the nvidia driver it doesn’t. It displays the screen at 1024x768, and doen’t give me a larger option.
I had a similar problem with openSuSE 12.2, but there is a workaround. By connecting the monitor directly to the PC - which gives me the correct screen size - I can use nvidia-settings to save an X configuration file. This worked with openSuSE 12.2.
However, when I run it now, it asks me for the name of the X configuration file. That’s where I’ve stopped. What should the file be called and where should I place it?
Hi
If you run the nvidia-settings as root user, then save it under /etc/X11 directory as xorg.conf, or create as your user and then copy and save as root user to /etc/X11 you should be fine. I’m lazy and always let the nvidia setup run it’s xconfig program
Thanks, but I’m afraid that didn’t work. The option are different now, but it still won’t give me a possible screen size of 1680x1050, let alone display that without any interference on my part.
What is the nvidia xconfig program of which you speak?
Sometimes you just have to add the screen size to xorg.conf files For different reasons but KVM switches are one. You say your KVM stores the info but are you sure it spits it out to the OS when asked?? I have never actually hear of one doing that.
How did you store it? Use Windows? had a special driver?? Coulld be one of those Windows only features
Just make a mode line and put it in the xorg.conf stuff
On Thu 29 Jan 2015 04:06:01 PM CST, johngwalker wrote:
malcolmlewis;2691770 Wrote:
> Hi
> If you run the nvidia-settings as root user, then save it
> under /etc/X11 directory as xorg.conf, or create as your user and
> then copy and save as root user to /etc/X11 you should be fine. I’m
> lazy and always let the nvidia setup run it’s xconfig program
Thanks, but I’m afraid that didn’t work. The option are different now,
but it still won’t give me a possible screen size of 1680x1050, let
alone display that without any interference on my part.
What is the nvidia xconfig program of which you speak?
Hi
It doesn’t, if you open nvidia-settings on the X Server Display
Configuration under ‘selection’ you don’t see the screen, if you press
the advanced button you can set the ViewPortIn to 1680x150?
It’s nvidia-xconfig;
NAME
nvidia-xconfig - manipulate X configuration files for the NVIDIA
driver
SYNOPSIS
nvidia-xconfig options ]
DESCRIPTION
nvidia-xconfig is a tool intended to provide basic control over
configuration options available in the NVIDIA X driver.
From the man page or nvidia-xconfig --help.
–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.32-33-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
I came across some files I had previously stored called 50-device.conf, 50-monitor.conf and 50-screen.conf, so I dropped them into /etc/X11/xorg.conf.d, replacing the similarly-named files that were already there. I recreated xorg.conf using nvidia-xconfig.
The results were somewhat peculiar. The login screen appeared to be the correct size, as did the initial screen that comes up when you log in (whatever it’s called - it has five icons in a white rectangle). However the screen then goes blank and reappears at 1024x768. It’s as though it’s picking up the right size then hits something it can’t understand and so leaps to the default.
I hadn’t realised the size had to be set separately in KDE. But that made sense, given what I saw: the correct size then a change to the wrong one when KDE kicked in.
I changed the screen size in the KDE system settings and it worked. So thanks to all.
I’m surprised that you hevn’t heard of a KVM switch storing the EDID of its attached monitor. I don’t have much experience of KVM switches, apart from the one I have now, the ATEN CS1734B, but, since ATEN don’t mention the ability to copy the EDID as a USP I assumed this was general. You can read about what it does in the user manual at http://www.aten.com/download/download_m.php
Anyway, we managed to make things work without that facility, so I am now a happy bunny.
