I would like to use the Intel vPRO AMT KVM-over-IP feature to remotely manage systems.
However I noticed that when there is no monitor attached to the system, the KVM-over-IP display remains blank as well.
- The moment I attach a VGA cable to the system the KVM-over-IP display does appear (even when the monitor itself is powered off)
- When setting the boot option "i915.modeset=0" it does work properly without cable, making me think this something that can be fixed in the DRM code.
Tested with Centos 6.2 and Debian Squeeze. Default kernel.
Mainboard: Intel DQ67
Paulo Zanoni has recently been working on KVMr stuff. Reassigning to him.
(In reply to comment #0)
> I would like to use the Intel vPRO AMT KVM-over-IP feature to remotely manage systems.
> However I noticed that when there is no monitor attached to the system, the KVM-over-IP display remains blank as well.
I can reproduce this, with the difference that about a minute after I connect, VNC gives me an error message and then disconnects me ("Connection to remote machine stopped: Reason: Error: 0x80862000: Unsupported or inactive display adapter").
Do you see this error message?
- If no: which VNC client are you using? Standard or Redirect port? Can you ssh to the machine while the monitor is still disconnected and send the output of intel_reg_dumper to me?
- If yes: ok, we have the same problem, it will be fixed.
Created attachment 57229 [details]
>Do you see this error message?
Server just disconnects after a while.
Be aware that the official VNC protocol is very simplistic and does not have any official way to pass detailed error messages to the client.
So could be that it is a message the client always shows when it hasn't received any data for a while, instead of actual information from the server.
>If no: which VNC client are you using? Standard or Redirect port? Can you ssh to
>the machine while the monitor is still disconnected and send the output of
>intel_reg_dumper to me?
Our software ( http://www.noc-ps.com/ ) acts as a proxy server handling the AMT authentication, and we use a modified version of noVNC ( http://kanaka.github.com/noVNC/ ) to display the content in the client's web browser.
Any news on this bug? I confirm it works as expected only with i915.modeset=0
You should be able to force a connector on using the video= boot option, see https://wiki.archlinux.org/index.php/Kernel_Mode_Setting#Forcing_modes for info.
sorry didn't mean to close, please let me know if the video= thing works for you.
(In reply to comment #5)
> You should be able to force a connector on using the video= boot option, see
> https://wiki.archlinux.org/index.php/Kernel_Mode_Setting#Forcing_modes for
Can also work around it with i915.modeset=0
But that is simply not an acceptable solution.
A popular use case of Intel AMT is to remotely install operating systems on computers far away, as AMT provides both KVM-over-IP as well as virtual media.
That really should work out-of-the-box, without having to edit parameters, which might be hard to do without visual.
You have to boot it somehow... and by default we shut everything off to save power if no outputs are connected. I suppose we could change that default on AMT enabled systems and at least light up a pipe & plane for AMT to pull from...
I'll wontfix this - it's kinda a feature request and we can work around it by forcing the connector state already. Doing proper kvm output detection needs a bit of code, but judging by the amount of noise in this bugzilla the demand isn't high.
I can confirm this bug on an ubuntu 14.04 LTS system with CSM-Q87M-E43 motherboard running with Intel Core i7-4770T with the latest Intel open-source graphics for this release.
Same behaviour here: as soon as you attach a VGA cable the VNC connection stops giving you a black screen and works properly. This should definitely be fixed because it might not be obvious when you first encounter this and it should work out of the box.
(In reply to Jesse Barnes from comment #6)
> sorry didn't mean to close, please let me know if the video= thing works for
'nomodeset' and 'i915.modeset=0' had a strange effect for me: even with monitor connected the last thing I had shown on the monitor was the splash screen. I suspect this is because latest systems require KMS to be enabled.
Adding 'video=VGA-1:1280x1024@60me' helped and I got no black screen. 'e' option is mandatory here since it forces the system into thinking that there is a valid VGA signal coming from the monitor even if it isn't (the kernel.org doc for the video option is here https://www.kernel.org/doc/Documentation/fb/modedb.txt).
So my boot options line in /etc/default/grub looks like this now (don't forget to run sudo update-grub if you are on ubuntu or debian and want to reproduce)
Just for debugging purpose, I tell you that on Dell Precision Tower 3620 doesn't work with 'video=VGA-1:1280x1024@60me', neither with 'nomodeset' and 'i915.modeset=0'.
It just work with a monitor attached. In my case don't think is a i915 issue, since it doesn't work even on the BIOS or boot process (with a monitor works without issues).
Marking this again as resolved+wontfix. Dmitrii - file another bug for you problem if valid with the latest kernel from drm-tip (see https://01.org/linuxgraphics/documentation/how-report-bugs).