darksmurf's questions

I have Ubuntu 16.04 on my Acer Aspire 7750G laptop connected to an external monitor with the built-in screen disabled. I also have an external keyboard and mouse connected to the laptop.

When I suspend the laptop with the laptop lid open I am able to wake the laptop by pressing the external keyboard.

However, if I suspend the laptop while the lid is closed, I am unable to wake it using the external keyboard. The same is true if I suspend the laptop with the lid open and then close the lid. The same is also true if I suspend the laptop with the lid open, close the lid, open the lid and try to wake it.

To summarize: I am unable to wake the laptop using the external keyboard if the lid has been close any time during hibernation. I am therefore unable to have my laptop lid constantly closed.

I've tried enabling all /sys/bus/usb/devices/usb*/power/wakeup

I've tried setting HandleLidSwitch=ignore in /etc/systemd/logind.conf

I've tried setting IgnoreLid=true in /etc/UPower/UPower.conf

How can I wake my laptop while the lid is closed?

EDIT

This might be good to know. Even though I am unable to wake the laptop with the lid closed, something is happening when I press a key on the keyboard. If I, while suspended with the lid closed, press a key on the kayboard, the LEDs on the laptop flash once and I can hear the fans winding up. After about 0.5 sec it stops. If I press a key again, nothing happens. If I then open the lid and wake the laptop by pressing ESC on the built-in keyboard, I can see that there is a stored character in the password field on the login screen. This means that there actually is a connection to the keyboard and that the key press registers while the laptop is suspended with the lid closed, but it does not wake the laptop.

I'm running Ubuntu 16.04 on my Acer Aspire 7750G laptop with switchable graphics (integrated Intel graphics and an AMD Radeon HD 6650M). I recently bought an AOC Q3279VWF 2560x1440 monitor that I connected to the laptop through HDMI.

The largest possible resolution for the monitor under Display settings was 1920x1080. To force the native 2560x1440 I messed around with cvt and xrandr. Most refresh rates did not work (displayed an error in the terminal or no signal on the monitor) but when I by accident tried 44 Hz it suddenly worked:

cvt 2560 1440 44
xrandr --newmode "2560x1440_44.00"  222.75  2560 2720 2992 3424  1440 1443 1448 1479 -hsync +vsync
xrandr --addmode HDMI-1 "2560x1440_44.00"

However, while I get the correct resolution on the monitor, there is a constant terrible lag on everything that moves on the screen; when watching a video it is very stuttery; when moving the cursor it lags behind.

What is the reason for this lag and can it be fixed? Also, is there a logical pattern for which refresh rates work and which don't?

I wanted to give my terminal prompt in Ubuntu a more personal look, and wanted to change the text prior to the '$' when writing a command.

From what I've found this is done by editing the .bashrc file in the home directory, so I went in there and changed

if [ "$color_prompt" = yes ]; then
    PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
else
    PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
fi

to

if [ "$color_prompt" = yes ]; then
    PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
else
    PS1='\e[1;32m[\W]\$ \e[m'
fi

This works and the terminal looks the way I want it to.

But after some time when entering a couple of commands when I use the arrow-up key to get to the command history, things get weird.

From a clean line and pressing the arrow-up key is works. When pressing it again the text that was on the line gets capped at about ~15 characters and the new command in the history (that is supposed to be displayed) gets capped by a few characters in the beginning, and they are sort of merged together on the command line.

E.g. my two most recent commands are

Java Test4 words-250.txt words-250-in.txt
Javac Test4.java

When pressing the arrow-up key once, the first line is displayed, as it should. When pressing it a second time, this is displayed:

Java Test4 worc Test4.java

Despite this weird output, the terminal works fine. If for instance I press enter after doing the above, Javac Test4.java will run. If I instead try to delete the entire line using backspace, I am only able to delete up until the line says

Java Test4

and if pressing enter after that I get a new empty line, just as if the line was empty when pressing enter.

All of this goes away if I reset the .bashrc file.

Why does this happen and how can I fix it?

A couple of days ago I decided to install Ubuntu on my computer that runs Windows 8.1. I downloaded LiLi USB Creator, ubuntu-14.10-desktop-amd64.iso, and used it to create a 100Gb partition and install Ubuntu there.

Everything went fine, I was able to reboot, install Java JDK, and other stuff. When I went into Windows again and back to Ubuntu I got the dreaded Low Graphics Mode error, and I couldn't reach the login screen.

I tried entering fail safe mode and install drivers for my AMD GPU using sudo apt-get install fglrx.

I tried editing the /etc/lightdm/lightdm.conf file because I read something about a bug, but this file was not present in the mentioned folder.

I tried switching from lightdm to gdm using these instructions. Nothing worked, so I reinstalled the same version of Ubuntu. The same thing happened again, without me changing/installing anything or entering Windows in between. I tried installing everything again. I tried updating my programs using some GUI in the sidebar as well as using sudo apt-get update && sudo apt-get upgrade.

I tried installing the 14.04.2 LTS version instead. When trying to install drivers using fglrx in this version, it complains about dependencies.

After some installations I'm able to reach the login GUI a couple of times, and after some I go directly to the graphics error. I have done so many re-installations and tried so many things in so many orders that my head is about to explode.

Is there something I should reconfigure in my BIOS? Does my 2x AMD 280x GPUs in crossfire have anything to do with it?

Can someone more experienced than me help me to troubleshoot this?

EDIT: I've mainly used this post when trying to troubleshoot. I've tried most of the things that I've found relevant. The post is also quite old, and some of the solutions are out-dated. I also have a problem that I haven't seen anywhere else: The error occurs randomly after a fresh installation. That is why I've created my own post about the problem.