[opensuse-kde] Screen blanking when switching back to system when using hardware KVM.
I first asked about this on the factory mailing list but it was suggested I try this list. I have a hardware KVM that I use to switch between multiple computers. When I switch away from my Tumbleweed system with the KVM switch and return I have a blanked screen. The screen saver is disabled. Screen locker is disabled. DPMS is disabled. How can I disable this behaviour? I can do a CTRL-ALT-F1 and get a console when this happens. No amount of keyboard mashing restores the KDE screen. The only way to recover is to power cycle the system or issue a shutdown from a console. This system is not useful in this condition. Can this feature or bug be disabled? This is a HP Intel Core 2 Duo E8400 system Desktop with what hardware info tells me is "Intel Q33/Q35/G33 graphics. Steven -- ____________ Apply appropriate technology. Use what works without prejudice. Steven L Hess ARS KC6KGE DM05gd22 Owner Flex-1500 and Flex-3000 Flex-6300, FT-857D, FT-817ND openSUSE Linux 13.1 KDE, Tumbleweed KDE with Packman Known as FlameBait and The Sock Puppet of Doom. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
* Steven Hess <flamebait@gmail.com> [08-02-15 10:30]:
I first asked about this on the factory mailing list but it was suggested I try this list.
I have a hardware KVM that I use to switch between multiple computers. When I switch away from my Tumbleweed system with the KVM switch and return I have a blanked screen. The screen saver is disabled. Screen locker is disabled. DPMS is disabled. How can I disable this behaviour?
I can do a CTRL-ALT-F1 and get a console when this happens. No amount of keyboard mashing restores the KDE screen. The only way to recover is to power cycle the system or issue a shutdown from a console. This system is not useful in this condition. Can this feature or bug be disabled?
If you can get to a tty# and it is functional, you shouldn't need to restart the entire system. Try just restarting X: rcxdm restart Substitute your chosen displaymanager for xdm. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
If you can get to a tty# and it is functional, you shouldn't need to restart the entire system. Try just restarting X: rcxdm restart Substitute your chosen displaymanager for xdm.
Thing is I shouldn't have to resort to that. My desktop should be there when I come back. That's what I'm working for not a work around to this feature or bug. Steven -- ____________ Apply appropriate technology. Use what works without prejudice. Steven L Hess ARS KC6KGE DM05gd22 Owner Flex-1500 and Flex-3000 Flex-6300, FT-857D, FT-817ND openSUSE Linux 13.1 KDE, Tumbleweed KDE with Packman Known as FlameBait and The Sock Puppet of Doom. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Sun, 2 Aug 2015 17:34, Steven Hess wrote:
If you can get to a tty# and it is functional, you shouldn't need to restart the entire system. Try just restarting X: rcxdm restart Substitute your chosen displaymanager for xdm.
Thing is I shouldn't have to resort to that. My desktop should be there when I come back. That's what I'm working for not a work around to this feature or bug.
To clarify: This (screen blanking) happens only with KDE / Plasma as DE, not in FVWM / IceWM / XFCE / LXDE ? Just for completeness, have you tested with GNOME? (This is to exclude underlaying (X11 / Wayland) troubles, and to ensure that this behavior is limited to KDE) Another info, please: Which openSUSE, with what KDE / Plasma version does this happen on? OSS 13.1 with default updates, or are there extra repos involved? - Yamaban. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Sun, Aug 2, 2015 at 8:55 AM, Yamaban <foerster@lisas.de> wrote:
On Sun, 2 Aug 2015 17:34, Steven Hess wrote:
If you can get to a tty# and it is functional, you shouldn't need to restart the entire system. Try just restarting X: rcxdm restart Substitute your chosen displaymanager for xdm.
Thing is I shouldn't have to resort to that. My desktop should be there when I come back. That's what I'm working for not a work around to this feature or bug.
To clarify: This (screen blanking) happens only with KDE / Plasma as DE, not in FVWM / IceWM / XFCE / LXDE ? Just for completeness, have you tested with GNOME?
(This is to exclude underlaying (X11 / Wayland) troubles, and to ensure that this behavior is limited to KDE)
Another info, please: Which openSUSE, with what KDE / Plasma version does this happen on? OSS 13.1 with default updates, or are there extra repos involved?
As I stated this is current Tumbleweed. So it's whatever KDE Plasma version is current in Tumbleweed. flamebait@linux-rraz:~> kde4-config -v Qt: 4.8.7 KDE Development Platform: 4.14.10 kde4-config: 1.0 I have not tried any other desktops because I don't use them. The screen saver is disabled in desktop settings. Screen locking is disabled in desktop setting Power management is set for monitor always on. DPMS is disabled in X11 famebait@linux-rraz:~> xset q Keyboard Control: auto repeat: on key click percent: 0 LED mask: 00000000 XKB indicators: 00: Caps Lock: off 01: Num Lock: off 02: Scroll Lock: off 03: Compose: off 04: Kana: off 05: Sleep: off 06: Suspend: off 07: Mute: off 08: Misc: off 09: Mail: off 10: Charging: off 11: Shift Lock: off 12: Group 2: off 13: Mouse Keys: off auto repeat delay: 250 repeat rate: 30 auto repeating keys: 00ffffffdffffbbf fadfffefffedffff 9fffffffffffffff fff7ffffffffffff bell percent: 50 bell pitch: 400 bell duration: 100 Pointer Control: acceleration: 20/10 threshold: 4 Screen Saver: prefer blanking: yes allow exposures: yes timeout: 0 cycle: 600 Colors: default colormap: 0x22 BlackPixel: 0x0 WhitePixel: 0xffffff Font Path: /usr/share/fonts/misc:unscaled,/usr/share/fonts/Type1/,/usr/share/fonts/100dpi:unscaled,/usr/share/fonts/75dpi:unscaled,/usr/share/fonts /ghostscript/,/usr/share/fonts/cyrillic:unscaled,/usr/share/fonts/truetype/,built-ins,/home/flamebait/.fonts DPMS (Energy Star): Standby: 0 Suspend: 0 Off: 0 DPMS is Disabled Font cache: Server does not have the FontCache Extension Something is sensing the loss of a monitor to output to and shutting the KDE Plasma display off. Whatever this is I want to turn it off. I don't want the screen to ever blank ever. -- ____________ Apply appropriate technology. Use what works without prejudice. Steven L Hess ARS KC6KGE DM05gd22 Owner Flex-1500 and Flex-3000 Flex-6300, FT-857D, FT-817ND openSUSE Linux 13.1 KDE, Tumbleweed KDE with Packman Known as FlameBait and The Sock Puppet of Doom. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 2015-08-02 18:09, Steven Hess wrote:
I have not tried any other desktops because I don't use them.
Well, you should. As a troubleshooting test. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
rcxdm restart
rckdm restart produces only an error. Can't find rckdm That doesn't work. Only a reboot gets me back to a working desktop. Steven -- ____________ Apply appropriate technology. Use what works without prejudice. Steven L Hess ARS KC6KGE DM05gd22 Owner Flex-1500 and Flex-3000 Flex-6300, FT-857D, FT-817ND openSUSE Linux 13.1 KDE, Tumbleweed KDE with Packman Known as FlameBait and The Sock Puppet of Doom. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Steven Hess composed on 2015-08-02 08:55 (UTC-0700):
rcxdm restart
rckdm restart produces only an error. Can't find rckdm That doesn't work. Only a reboot gets me back to a working desktop.
Maybe you have sddm installed instead of kdm and need rcsddm restart? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 08/02/2015 10:58 AM, Patrick Shanahan wrote:
If you can get to a tty# and it is functional, you shouldn't need to restart the entire system. Try just restarting X: rcxdm restart Substitute your chosen displaymanager for xdm.
In modern systems that would be systemctl restart .... The last parameter is a YMMV thing. For me its "xdm.service". It may be "display-manager.service". It may be "gdm.service". I can't peer over your shoulder and tippy-tappy at your keyboard to find out, but if you run "systemctl --all" when the system is running you'll get a complete listing of all the units. Yes, overwhelming, I know, but you'll find the relevant one there .... somewhere. I did. No need to reboot. Just restart what is necessary. Systemctl and the way units are written takes care of things like dependencies :-) Yes I know there are people who are even more of a dinosaur than I am and refuse to admit that the systemd tools and facilities are here to stay and are the future, but that's the way it is. Eat iridium like the mammals ... "Adapt or Die". -- Together, we can make ourselves a nation that spends more on books than on bombs, more on hospitals than the terrible tools of war, more on decent houses than military aircraft. -- Robert Kennedy March 24, 1968 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Sun, Aug 2, 2015 at 9:11 AM, Anton Aylward <opensuse@antonaylward.com> wrote: Anton I know you try your best to be helpful. But you often just create noise. You often derail threads. PLEASE resist the urge to respond to this thread. Thank you Steven -- ____________ Apply appropriate technology. Use what works without prejudice. Steven L Hess ARS KC6KGE DM05gd22 Owner Flex-1500 and Flex-3000 Flex-6300, FT-857D, FT-817ND openSUSE Linux 13.1 KDE, Tumbleweed KDE with Packman Known as FlameBait and The Sock Puppet of Doom. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
* Steven Hess <flamebait@gmail.com> [08-02-15 12:15]:
On Sun, Aug 2, 2015 at 9:11 AM, Anton Aylward <opensuse@antonaylward.com> wrote:
Anton I know you try your best to be helpful. But you often just create noise. You often derail threads. PLEASE resist the urge to respond to this thread.
You may not want to hear it, but he provided you a way to determining which display manager command you need to use since rckdm does not work on your system. Sugar, not salt, helps :) -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Sun, Aug 2, 2015 at 9:35 AM, Patrick Shanahan <paka@opensuse.org> wrote:
* Steven Hess <flamebait@gmail.com> [08-02-15 12:15]:
On Sun, Aug 2, 2015 at 9:11 AM, Anton Aylward <opensuse@antonaylward.com> wrote:
Anton I know you try your best to be helpful. But you often just create noise. You often derail threads. PLEASE resist the urge to respond to this thread.
You may not want to hear it, but he provided you a way to determining which display manager command you need to use since rckdm does not work on your system. Sugar, not salt, helps :)
Thanks for the advice Patrick That's not the problem though. He tends to say way more than necessary. He is quite happy to display his knowledge in a very verbose and thread derailing way. I'm happy he offered his knowledge. I acknowledge he does know what he's saying. I just don't want this to be a 100 post thread with lots of extraneous unneeded detail. I thanked him. I'm thanking him again. I just want to solve this issue with KDE Plasma. I don't think restarting something that's already running is the correct approach. I want to stop this screen blanking. I don't want to restart KDE Plasma every time I change the computer I'm working with. That's not fixing what's happening. That's unwanted desktop behaviour. Steven -- ____________ Apply appropriate technology. Use what works without prejudice. Steven L Hess ARS KC6KGE DM05gd22 Owner Flex-1500 and Flex-3000 Flex-6300, FT-857D, FT-817ND openSUSE Linux 13.1 KDE, Tumbleweed KDE with Packman Known as FlameBait and The Sock Puppet of Doom. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Felix I tried your suggestions. I have the same behavior. I even disabled the power management service. That also failed to solve the blanking issue. Not ready to toss my hands up yet. Google has failed me here. On Sun, Aug 2, 2015 at 9:54 AM, Steven Hess <flamebait@gmail.com> wrote:
On Sun, Aug 2, 2015 at 9:35 AM, Patrick Shanahan <paka@opensuse.org> wrote:
* Steven Hess <flamebait@gmail.com> [08-02-15 12:15]:
On Sun, Aug 2, 2015 at 9:11 AM, Anton Aylward <opensuse@antonaylward.com> wrote:
Anton I know you try your best to be helpful. But you often just create noise. You often derail threads. PLEASE resist the urge to respond to this thread.
You may not want to hear it, but he provided you a way to determining which display manager command you need to use since rckdm does not work on your system. Sugar, not salt, helps :)
Thanks for the advice Patrick
That's not the problem though. He tends to say way more than necessary. He is quite happy to display his knowledge in a very verbose and thread derailing way. I'm happy he offered his knowledge. I acknowledge he does know what he's saying. I just don't want this to be a 100 post thread with lots of extraneous unneeded detail. I thanked him. I'm thanking him again.
I just want to solve this issue with KDE Plasma. I don't think restarting something that's already running is the correct approach. I want to stop this screen blanking. I don't want to restart KDE Plasma every time I change the computer I'm working with. That's not fixing what's happening. That's unwanted desktop behaviour.
Steven
-- ____________ Apply appropriate technology. Use what works without prejudice. Steven L Hess ARS KC6KGE DM05gd22 Owner Flex-1500 and Flex-3000 Flex-6300, FT-857D, FT-817ND openSUSE Linux 13.1 KDE, Tumbleweed KDE with Packman Known as FlameBait and The Sock Puppet of Doom.
-- ____________ Apply appropriate technology. Use what works without prejudice. Steven L Hess ARS KC6KGE DM05gd22 Owner Flex-1500 and Flex-3000 Flex-6300, FT-857D, FT-817ND openSUSE Linux 13.1 KDE, Tumbleweed KDE with Packman Known as FlameBait and The Sock Puppet of Doom. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
* Steven Hess <flamebait@gmail.com> [08-02-15 13:00]:
Felix
I tried your suggestions. I have the same behavior. I even disabled the power management service. That also failed to solve the blanking issue. Not ready to toss my hands up yet. Google has failed me here.
On Sun, Aug 2, 2015 at 9:54 AM, Steven Hess <flamebait@gmail.com> wrote:
On Sun, Aug 2, 2015 at 9:35 AM, Patrick Shanahan <paka@opensuse.org> wrote:
* Steven Hess <flamebait@gmail.com> [08-02-15 12:15]:
On Sun, Aug 2, 2015 at 9:11 AM, Anton Aylward <opensuse@antonaylward.com> wrote:
Anton I know you try your best to be helpful. But you often just create noise. You often derail threads. PLEASE resist the urge to respond to this thread.
You may not want to hear it, but he provided you a way to determining which display manager command you need to use since rckdm does not work on your system. Sugar, not salt, helps :)
Thanks for the advice Patrick
That's not the problem though. He tends to say way more than necessary. He is quite happy to display his knowledge in a very verbose and thread derailing way. I'm happy he offered his knowledge. I acknowledge he does know what he's saying. I just don't want this to be a 100 post thread with lots of extraneous unneeded detail. I thanked him. I'm thanking him again.
I just want to solve this issue with KDE Plasma. I don't think restarting something that's already running is the correct approach. I want to stop this screen blanking. I don't want to restart KDE Plasma every time I change the computer I'm working with. That's not fixing what's happening. That's unwanted desktop behaviour.
Steven
-- ____________ Apply appropriate technology. Use what works without prejudice. Steven L Hess ARS KC6KGE DM05gd22 Owner Flex-1500 and Flex-3000 Flex-6300, FT-857D, FT-817ND openSUSE Linux 13.1 KDE, Tumbleweed KDE with Packman Known as FlameBait and The Sock Puppet of Doom.
-- ____________ Apply appropriate technology. Use what works without prejudice. Steven L Hess ARS KC6KGE DM05gd22 Owner Flex-1500 and Flex-3000 Flex-6300, FT-857D, FT-817ND openSUSE Linux 13.1 KDE, Tumbleweed KDE with Packman Known as FlameBait and The Sock Puppet of Doom. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Maybe, just maybe, could it be the bios blanking your screen ??? Might look better trimmed, but .... -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Maybe, just maybe, could it be the bios blanking your screen ???
Might look better trimmed, but ....
I looked a BIOS configuration previously. I thought that it might be it too. I didn't see any configuration or any feature that would correspond to screen blanking. I didn't turn off power management as all it seemed to control was the Hard Drive. That and the ability to grab a console with CTRL-ALT-F1 left me to leave BIOS as it was. I solved this on another system by adding in a Nvidia GT 610 and letting nvidia-settings generate a xorg.conf then disabling display power management in xorg.conf It was running tumbleweed too. I had to put that system back under Windows 7 though. This system doesn't have a xorg.conf everything is hashed out Steven -- ____________ Apply appropriate technology. Use what works without prejudice. Steven L Hess ARS KC6KGE DM05gd22 Owner Flex-1500 and Flex-3000 Flex-6300, FT-857D, FT-817ND openSUSE Linux 13.1 KDE, Tumbleweed KDE with Packman Known as FlameBait and The Sock Puppet of Doom. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 08/02/2015 01:36 PM, Steven Hess wrote:
This system doesn't have a xorg.conf everything is hashed out
You mean everything under /etc/X11/xorg.conf.d, I presume? That's an "OUCH!" for me. I found I had to play around with the 50-device settings, in particular the acceleration to get a stable system. As far as I can tell the Intel Q _needs_ some kind of acceleration setting. I also customized the "screen' and "monitor" for my hardware rather than play games with xrandr on every boot. The latter was because sometimes the screen would come back with the wrong size settings. Not your problem, I realise, but it is related to the driver and screen blanking/return. -- In order to get better you have to do what you don't want to do. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Steven Hess composed on 2015-08-02 07:28 (UTC-0700):
I have a hardware KVM that I use to switch between multiple computers. When I switch away from my Tumbleweed system with the KVM switch and return I have a blanked screen.
Does it happen regardless of length of time switched away?
The screen saver is disabled. Screen locker is disabled. DPMS is disabled. How can I disable this behaviour?
Maybe a non-intuitive approach would work. Instead of disabling DPMS, keep it enabled, maybe adding 'Option "BlankTime" "36000"' (and/or OffTime), and set KDE's Dim screen and Screen Energy Saving to long intervals. I typically set mine to 111 or 125, depending on what happens when I click the box to change it, even if I have set 'Option "DPMS" "off"'. Maybe try setting them to the maximum. 360 seems to be the limit in 5.3.2. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 08/02/2015 10:28 AM, Steven Hess wrote:
I have a hardware KVM that I use to switch between multiple computers.
I had one back when I was using VGA type systems. I gave it up after I got a late model flat-panel and DVI. So I can no longer try to reproduce your problem,
When I switch away from my Tumbleweed system with the KVM switch and return I have a blanked screen. The screen saver is disabled. Screen locker is disabled. DPMS is disabled.
KDE systemsetting has a gazillion other settings and I do wonder how they interact. I haven't explored many of them. You say this is specific to KDE so that _must_ be some KDE-spoecific setting.
How can I disable this behaviour?
I can do a CTRL-ALT-F1 and get a console when this happens. No amount of keyboard mashing restores the KDE screen.
A few time I've had the system come back to me on a different VT. The settings I have say that it should be Ctl-Alt-F[123456] to get consoles and login (though i don't use them all) and so X should start on VT#7. But sometimes its appeared on VT#8 and once on VT#9. Have you explored that in your keyboard mashing? I have absolutely no idea why this happens and its not consistent or reproducible-to-order. At other times I've had KDE sleep and blank and not wake up at the keyboard; its taken mouse jiggling & clicking And even then its not immediate. You don't mention having tried this. I have no idea why and while its an irritant, its not an 'often enough' irritant to be reportable and and not reproducible enough to warrant a bug description. Please note that while you can reproduce this to order with the KVM, I am not using one but it happens (occasionally) none the less. There does seem to be a problem. You have it worse but its not unique.
This is a HP Intel Core 2 Duo E8400 system Desktop with what hardware info tells me is "Intel Q33/Q35/G33 graphics.
Mine is the Q35. Dell Optiplex. 13.1 KDE 4.14 Kernel is 4.1 series. Doesn't seem to happen with 'standard', does with "desktop". Perhaps that says something. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Steven Hess composed on 2015-08-02 07:28 (UTC-0700):
I have a hardware KVM that I use to switch between multiple computers.
Brand & Model? Port type: VGA? DVI? HDMI? DP? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Sun, Aug 2, 2015 at 12:36 PM, Felix Miata <mrmazda@earthlink.net> wrote:
Steven Hess composed on 2015-08-02 07:28 (UTC-0700):
I have a hardware KVM that I use to switch between multiple computers.
Brand & Model?
Port type:
VGA? DVI? HDMI? DP? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
The actual box itself is attached to the wall behind several suspended monitors I can't move. It's an IOGEAR 4 port. The port the computer in question is on is connected to a Trendnet two port that connects to the IOGEAR. (It behaves the same way when connected directly to the IOGEAR) These things are impossible to get to to get model numbers. Port is a VGA Keyboard and mouse connections are all USB Steven -- ____________ Apply appropriate technology. Use what works without prejudice. Steven L Hess ARS KC6KGE DM05gd22 Owner Flex-1500 and Flex-3000 Flex-6300, FT-857D, FT-817ND openSUSE Linux 13.1 KDE, Tumbleweed KDE with Packman Known as FlameBait and The Sock Puppet of Doom. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Steven Hess composed on 2015-08-02 13:05 (UTC-0700):
The actual box itself is attached to the wall behind several suspended monitors I can't move. It's an IOGEAR 4 port. The port the computer in question is on is connected to a Trendnet two port that connects to the IOGEAR. (It behaves the same way when connected directly to the IOGEAR) These
So you did try swapping the HP's cabling with another PC's without any effect? Only one switch, or more than one?
things are impossible to get to to get model numbers.
Port is a VGA Keyboard and mouse connections are all USB
In a fashion on Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03) with 64 bit E7600 TW 20150728 I tried to emulate a KVM, but using only the video element. On the digital side I used a DVI to HDMI cable to connect the DVI out to a Vizio TV's HDMI in #4, then after starting Plasma switching the TV to HDMI #1 to watch TV for a while. Plasma was ready and waiting on return to #4. I tried the same thing with VGA, connecting VGA cable to a Dell LCD, logging in on Plasma, then switching the Dell to its DVI port for 20+ minutes while doing other things. Plasma was again ready to go after switching through S-Video to composite and returning to VGA. The failure here with KB and pointing remaining connected has me wondering if the key to success might actually be the KVM's disconnected input devices. Can you try connecting an extra mouse and/or keyboard to the Q33/Q35/G33 HP? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 08/02/2015 08:43 PM, Felix Miata wrote:
The failure here with KB and pointing remaining connected has me wondering if the key to success might actually be the KVM's disconnected input devices.
Which makes me wonder .... Firstly, is a dummy load presented to the device while unselected? Secondly, what is the mechanics of the switch? I mean that in sense of: does it leave everything open circuit for a moment when switching? IIR there's a technical terms for that ... break-before-make ... make/break sequence ... something before something. open before close. something like that. Different types of equipment need different switch mode. I'm wondering if the way KDE utilizes the Intel Q sees an 'open circuit' as something gone wrong. In effect, the session sees the terminal as having been turned off or disconnected. There's a simple test here. Run a KDE session and disconnect or turn off the screen. Wait, then turn it back on. Hmm. I'll try that and follow up. -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Anton Aylward composed on 2015-08-02 21:04 (UTC-0400):
Felix Miata wrote:
The failure here with KB and pointing remaining connected has me wondering if the key to success might actually be the KVM's disconnected input devices.
There's a simple test here.
Run a KDE session and disconnect or turn off the screen. Wait, then turn it back on. Hmm. I'll try that and follow up.
Maybe not that simple. I tried on two: Intel Corp 82Q963/Q965 Integrated Graphics Controller (rev 02) Optiplex 745 Intel Corp 4 Series Chipset Integrated Graphics Controller (rev 03) Biostar T41 HD 745 I tried with 1440x900 LCD, T41 with CRT@1600x1200, disconnecting power from display, and unplugging USB KB & mouse. Plasma5 was ready to go on both on restoring power and replugging USB. However, both installations have kscreen set to not autostart in kdedrc. On both, resolution and DPI are preconfigured though xrandr in startup script, not xorg.conf*, while 50-monitor.conf sets DPMS off. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 08/02/2015 10:49 PM, Felix Miata wrote:
Maybe not that simple. I tried on two:
...
However, both installations have kscreen set to not autostart in kdedrc. On both, resolution and DPI are preconfigured though xrandr in startup script, not xorg.conf*, while 50-monitor.conf sets DPMS off.
I used xrandr as init at one time, no longer. Now I do everything using xorg.conf.d/* In my case, similar equipment but with LG Flatron No problems. -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Anton Aylward composed on 2015-08-03 08:03 (UTC-0400):
Felix Miata wrote:
both installations have kscreen set to not autostart in kdedrc. On both, resolution and DPI are preconfigured though xrandr in startup script, not xorg.conf*, while 50-monitor.conf sets DPMS off.
I used xrandr as init at one time, no longer. Now I do everything using xorg.conf.d/*
Xrandr traditionally has not been my first choice, but xorg.conf* hasn't/doesn't always work: https://bugs.freedesktop.org/show_bug.cgi?id=77321 https://bugzilla.opensuse.org/show_bug.cgi?id=771521 https://bugzilla.opensuse.org/show_bug.cgi?id=901506 https://bugs.freedesktop.org/show_bug.cgi?id=69903 https://bugs.freedesktop.org/show_bug.cgi?id=82193 https://bugs.freedesktop.org/show_bug.cgi?id=82205 https://bugs.freedesktop.org/show_bug.cgi?id=85016 https://bugzilla.opensuse.org/show_bug.cgi?id=841696 https://bugzilla.opensuse.org/show_bug.cgi?id=766059 https://bugzilla.opensuse.org/show_bug.cgi?id=706024 https://bugzilla.opensuse.org/show_bug.cgi?id=661536 Xrandr doesn't always produce expected results either: https://bugzilla.opensuse.org/show_bug.cgi?id=929016 -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Sun, Aug 2, 2015 at 5:43 PM, Felix Miata <mrmazda@earthlink.net> wrote:
Steven Hess composed on 2015-08-02 13:05 (UTC-0700):
The actual box itself is attached to the wall behind several suspended monitors I can't move. It's an IOGEAR 4 port. The port the computer in question is on is connected to a Trendnet two port that connects to the IOGEAR. (It behaves the same way when connected directly to the IOGEAR) These
So you did try swapping the HP's cabling with another PC's without any effect? Only one switch, or more than one?
things are impossible to get to to get model numbers.
Port is a VGA Keyboard and mouse connections are all USB
In a fashion on Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03) with 64 bit E7600 TW 20150728 I tried to emulate a KVM, but using only the video element. On the digital side I used a DVI to HDMI cable to connect the DVI out to a Vizio TV's HDMI in #4, then after starting Plasma switching the TV to HDMI #1 to watch TV for a while. Plasma was ready and waiting on return to #4. I tried the same thing with VGA, connecting VGA cable to a Dell LCD, logging in on Plasma, then switching the Dell to its DVI port for 20+ minutes while doing other things. Plasma was again ready to go after switching through S-Video to composite and returning to VGA.
The failure here with KB and pointing remaining connected has me wondering if the key to success might actually be the KVM's disconnected input devices. Can you try connecting an extra mouse and/or keyboard to the Q33/Q35/G33 HP? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
The graphics controller is a Intel 82Q33 I was able to finally determine. Plugged in a keyboard and mouse to front USB jack and booted the system. I still have the issue. I've had a good night's sleep and decided to bite the bullet and have ordered a Nvidia GT 610 card for the system. This set up solved this problem on the other system I have after I modified /etc/X11/xorg.conf.d/monitor.conf I'll avoid any meals out this week to pay for it. I am thinking it's just a querk in the nature of this old Intel video chipset in combination with my KVM hardware. This KVM hardware setup does not provide a signal that the system is looking for and KDE Plasma blanks video in response. The underlying video system is still working as evidenced by the ability to CTRL-ALT-F1 and get console. KDE Plasma is likely working as designed with the defaults. The new video card is cheaper than a new KVM. Thanks for all the good help on trying to resolve this Issue. Steven -- ____________ Apply appropriate technology. Use what works without prejudice. Steven L Hess ARS KC6KGE DM05gd22 Owner Flex-1500 and Flex-3000 Flex-6300, FT-857D, FT-817ND openSUSE Linux 13.1 KDE, Tumbleweed KDE with Packman Known as FlameBait and The Sock Puppet of Doom. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
participants (6)
-
Anton Aylward -
Carlos E. R. -
Felix Miata -
Patrick Shanahan -
Steven Hess -
Yamaban