I’ve just installed 11.3 and I’m having issues with the display resolution not being correct when I login, and when I switch users to create a second session the new session just freezes up very quickly. I think I’ve traced this to being an issue with using a KVM (Belkin SOHO), although this worked fine with 10.3.
I initially had EDID errors in ‘boot.msg’, so I’ve had to use ‘nomodeset’ to avoid these, and I’ve used ‘Xorg -configure’ to create a ‘xorg.conf’ which has been moved into ‘/etc/X11’. At this point if I connect my monitor directly to the machine everything is fine and I get the 1280x1024 that I expect, but when I connect via the KVM my problems return and the resolution drops to ‘1024x768’.
I’ve had a look at setting the required resolution in 'xorg.conf but I really cannot get my head around the way that file works. Any pointers would be greatly appreciated
Can you post the contents of xorg.conf you created? It could be that suitable horizontal sync and vertical refresh timings need to be explicitly defined…
I’m sorry to be a pain, but my ‘Posting Permissions’ say ‘You may not post attachments’ and I just can’t see where I can change a setting or apply for permission! I’m rather loathed to simply ‘cut & paste’ into this text, as I’m not sure that would be following etiquette. Could you advise me please?
For very large files you should use a service like pastebin but you could also simply post the interesting parts of any log ie those that apply to the problem. For small files and pasts from the command line press the Go Advanced button and use the code quote to preserve format. As you post more your attachment restriction will be eased.
It would seem my post is going to be too long, so I’ve split it across two posts!
So, here’s what I’ve done. Thinking about it when I was more awake, I realised one way was to retrieve a copy of the ‘xorg.conf’ from a backup of my old 10.3, then compare that with the ‘xorg.cong.new’ created by ‘Xorg -configure’ and do a copy and paste, not quite that simple but nearly!
Now I must stress that I do not know what I’m doing exactly, so I’ve copied the files here for anyone to have a look at if they wish, to tell me if there’s anything wrong:
and also contacted Belkin, who advise me that my ‘F1DS104J’ 4-port SOHO KVM switch does not support DCC.
Now the outcome - the system is far more stable and is at least usable (I hope). However, there are still occasions when there are raster lines flickering about after I’ve switched users (as you can imagine I’ve been flicking back and forth quite a bit), about 1 in every 7 switches, sometimes switching back and back again solves it but only about 50% of the time.
If anyone can provide any further suggestions as to how to get my machine more flicker-free I would be most appreciative, but I can possibly live with it.
The upshot would seem that with X moving away from using a ‘xorg.conf’, and some KVM’s (possibly a lot) not supporting DCC there are likely to be other occasions where this happens.
So it looks like you’ve managed to edit your xorg.conf with a usable configuration for your situation - well done! There is a lot that could be stripped out (not required), but I don’t think its worth the effort considering it won’t actually improve things further.
Some would suggest you try the proprietary driver, but with the KVM blocking DDC, the proprietary driver options concerning ignoring EDID and forcing manual modes are non-existent.
On a different note, ableit slightly related, I note that some KVM switches do work fine.
The OP noted:
I use a 4 port KVM, which is the Aten Master View CS1784 and I do not see the problems the OP noted. I typically switch back and forth between 3 different PCs, all typically at different resolutions and different openSUSE versions.
I do have a problem on occasion (once every few months) where one of my PCs will give me a ‘no keyboard detected’ message when booting, and the only way I have found to clear this is to switch OFF all PCs (including removing power from the back of the PC), switch OFF the KVM, and then plug in and switch back ON everything. Fortunately this does not happen very often.
Sorry to read of the OP’s difficult, but I did want to note that not all KVMs have this difficulty (but rather they have their own quirks).
> Some would suggest you try the proprietary driver, but with the KVM
> blocking DDC, the proprietary driver options concerning ignoring EDID
> and forcing manual modes are non-existent.
Now that part was quite useful here. I’ve been brute forcing video for
while now - first I had seen about the kvm causing issues. Pulled it out
and damned if the annoying error message during boot didn’t go away…
Never thought to try that.
