![]() Registered Member ![]()
|
I've got a QNIX QX2710 monitor, which doesn't work out of the box with X Windows. I was able to get it to work with Fluxbox and Gnome using a custom xorg.conf I found online, but for some reason it doesn't work with KDE.
Under KDE, I'll get the splash screen where the icons light up as parts of KDE load, and the screen is just fine at first. But before it can get to the 2nd icon, my monitor just starts displaying some sort of test pattern. Which is what I got before I found a working xorg.conf, so I'm guessing KDE isn't honoring the settings in xorg.conf, but I don't know what I can do about it. I've pasted my current xorg.conf as a file. Note there's a lot of suggested xorg.conf's floating around for this monitor online, and it took a while for me to find one that worked. This guy's seemed promising, but it made half of the monitor dim and there were weird visual glitches all over. FWIW, I'm using Nvidia's 331.67 on a Geforce GTX 670.
|
![]() ![]()
|
kscreen2 or krandr will apply a former randr mode, but they should only pick allowed ones.
since apparently "2560x1440_96" is the only supported mode, i'd try commenting all others/remove them from "Modes" in the "Display" subsection. This is however a bit weird. The screen should inform X11 about the supported modes (and thus no other mode be selectable and you not have to write modelines in 2014 ...) |
![]() Registered Member ![]()
|
Ok, I commented-out all the modes except 2560x1440_96 in the Screen and Monitor sections, but the result is still the same. I've attached my new xorg.conf just to prove that I'm not crazy.
I thought maybe the output from xrandr would be helpful, so I ran it from a another virtual terminal when KDE was running (and not displaying properly), and again when fluxbox is running (and it DOES display properly): xrandr with KDE:
xrandr with fluxbox:
new xorg.conf:
|
![]() ![]()
|
Well, "something"™ sets the resolution to 800x600
login to KDE, move to VT1 (ctrl+alt+f1, alternatively you can maybe login via ssh?) and run
return to KDE (ctrl+alt+f7) and run "kcmshell4 kscreen", set the screen resolution (lower right icon in the monitor picture) to 2560x1440, apply, ok, pray, log out and back in again. alternatively just
latter will break with the next system update. |
![]() Registered Member ![]()
|
I tried your suggestion of launching KDE, switching to another virtual console, and running:
and got this error:
I ran just plain "xrandr" again to check the listed modes, and sure enough the 2560x1440 resolution was still in there. Don't know if this helps, but on a lark I tried running:
and:
and both of these times, there were no error messages, but also both times, xrandr was displaying the 800x600 as the active resolution -the '*' in the output for xrandr indicates the current one, right? Of course, I kept checking on what KDE was up to after each command, and still just test pattern... |
![]() ![]()
|
"Interesting" - pot. the KDE startup script stumbles on this behavior.
-> Tried "sudo chmod -x `which krandrstartup`" seeking to prevent it running? On the xrandr weirdness: Maybe the new API is more convincing?
or alternatively
|
![]() Registered Member ![]()
|
It would appear that krandrstartup wasn't installed on my system at all. KDE had been working with a pair of Asus monitors before I replaced them with the Qnix, but I tracked krandrstartup to the kde-workspace-randr package via packages.debian.org, and installed it. I'm using Debian testing, by the way. Didn't seem to make a difference, before or after I did the "chmod -x" on it.
Note that I've currently got Gnome running in the first X display and then launched KDE from another virtual console so I could compose this message and run your suggestions at the same time. Thus KDE is on DISPLAY=:1 --verified by running "DISPLAY=:1 xrandr" and checking that the low resolution was the current mode. "DISPLAY=:1 xrandr --output DVI-I-1 --mode 2560x1440" yields:
"DISPLAY=:1 xrandr --output DVI-I-1 --auto" yields:
|
![]() Registered Member ![]()
|
I don't know if this is a clue, but:
I discovered that, when running fluxbox or gnome, I can bring up the KDE control panel (actually titled System Settings, apparently) by running "systemsettings" from an xterm. To be clear, the KDE control panel appears in fluxbox or gnome; it's not miraculously appearing in a malfunctioning KDE X session running from another virtual console. When I open the "Display and Monitor" part of the KDE control panel, I noticed the following output in the xterm I launched it from:
Is that last message, about XRandR versions, noteworthy? |
![]() ![]()
|
Seems harmless, https://bugs.kde.org/show_bug.cgi?id=326776
The X11 Error seems far more like a problem to me (--auto fails!) I assume anything in XRandr does not care about one or more Options in your xorg.conf. Can you in fluxbox do eg.
Be prepared to loose the screen with this. |
![]() Registered Member ![]()
|
Hey! Sorry it took me so long to get back. Been a busy week. Please don't give up on me.
I wasn't quite sure if you were looking to try to hit the KDE session or the fluxbox session with the commands:
...so I tried both:
Each time, nothing happened except for generating this error message: xrandr: cannot find mode 800x600 I ran them both from inside an xterm inside fluxbox. The fluxbox screen didn't show any sign of change, and when I checked on the KDE session it was still doing the same thing as before. |
Registered users: Bing [Bot], Google [Bot], Sogou [Bot], Yahoo [Bot]