I just recreated the problem and was able to fix it by deleting the ~/.config/monitors.xml file.
Note that by deleting this file all settings for displays will be lost.
The file is in a hidden folder, so to be able to find it you need to make hidden folders visible in the file browser. To do this press Ctrl+H.
Press CTRL+ALT+F1 to open a TTY virtual terminal.Then type your username and password and once you have logged in type rm ~/.config/monitors.xml and press ENTER to delete the file @joost said about.
Thanks to @joost for telling the file
I'm facting similar issues on HP Spectre x360. Loki worked great, but Juno is terrible.
In response to Unable to disable built-in monitor, I have found a way to turn it off:
Find out the display names:
xrandr | grep conn | grep -v dis
Disable the desired display:
xrandr --output <display> --off
On my machine, first command returned:
I finally managed to fix this issue following steps given here Install Nvidia driver instead nouveau.
The issue was that, although the nvidia drivers were correctly installed, the nouveau drivers were still being used, even if the nvidia drivers were selected in 'Software & Updates'/Additional drivers.
Steps I followed:
Blacklist the modules. Open the ...
We can use command
pactl - Control a running PulseAudio sound server on terminal
first, list our available properties in our machine using this command:
pactl list cards
based on my hardware above, i set output:hdmi-stereo as my default profile using this command:
pactl set-card-profile 0 output:hdmi-stereo
if we want to set to internal ...
This seems to be a limitation (bug?) of the current sound setting app. The current workaround is to install PulseAudio Volume Control from the AppCentre, and to select a HDMI configuration profile.
Related Stackexchange Issue
Related Github Issue
The Huawei MateBooks will sometimes not auto-extend a display. That said, you pay be able to trigger the function by pressing F8 (or Fn+F8) to trigger the BIOS toggle. Some models may also use Super+P.
The idea would be to tell lightdm to use the same settings that you use for the monitors.
So, login into elementary with the external monitor connected, set up your displays the way you want in System Settings -> Displays (mark the external display as primary by clicking its star in the upper left corner). Save you configuration.
Now, copy the ~/.config/...
Instead of closing the lid of the laptop you can use the cycle display modes shortcut Super+p. On both of the laptops I use there is such a function key also. If I do it like this after the resume of suspend it enables the same monitor as before the suspend. Also, if you want to skip logging in on wakeup, you can set this using System settings > Security &...
I see you are using the Intel Corporations display driver.
Do you have a built in graphics chip from either Nvidia or Amd
cause if you do you might want to install the latest drivers for ubuntu
from either of them to make it work properly.
I am not sure about AMD but to install nvidia drivers here is what you do
sudo add-apt-repository ppa:graphics-drivers ...
Seems to me that your xrandr --newmode syntax is incomplete (without the enclosing quotes).
Also, you should check this answer to make sure you're following the steps correctly, and you're giving xrandr the parameters it needs.
Finally, remember that in order to make xrandr modes permanent, you should create a script to add them at boot time.
I don't know If you are still around. I never done this but I just gathered info I believe might help you
You need to install Nvidia drivers
$ sudo apt install software-properties-gtk software-properties-common
Then use the command:
$ sudo ubuntu-drivers list
You should get something like this (probably different version numbers):
An eOS system update was just pushed and seems to have solved this issue. The monitor now displays with the proper resolution. Setting monitor positions and primary/secondary settings is still really jank but it is possible to work with it until everything is right.
One more power cycle (full power off and power on) did it (kept HDMI cable plugged in throughout). It would be nice, however, to have a method that didn't rely on pure luck, as I power cycled several times previously with no effect. Perhaps xrandr can manually force a state change?
So for anyone else who may be experiencing this issue: The lack of HDMI audio is documented on Ubuntu's AMDGPU and AMDGPU-Pro wiki pages. As of Ubuntu 16.04, only the open source AMDGPU/amdgpu-Pro official open-source Radeon drivers can be used on newer model GPU's and APU's(like mine), it specifically notes:
"The open source AMDGPU driver does not ...
It seems this is a problem introduced by Pulseaudio 8.
Pulseaudio 9 claims to fix the problem (See "Automatic routing improvements", Pulseaudio 9 Release notes).
Upgrading to Pulseaudio 9 doesn't seem possible in Loki or is beyond my techincal level. (EDIT: here is someone trying it in Ubuntu 16.04 and running into unmet dependencies, as I did...).
I even ...