Thanks for the explanations! On Mon, Nov 24, 2014 at 4:19 AM, Martin Pieuchot <mpieuc...@nolizard.org> wrote: > On 24/11/14(Mon) 09:04, Peter Hessler wrote: >> Can you switch from the graphical console (ctrl-alt-f5) to a text >> console (ctrl-alt-f1), and back? That may help with input device >> related problems. > > That won't work in this case. His pointer isn't behind the mux and > needs to be calibrated.
It's even slightly worse: after resuming, the keyboard still works in X, but switching to a text console (either via ctrl-alt-f1 or by quitting X) results in the keyboard being unusable, i.e. typing anything results in garbled characters. I therefore cannot even try your previous suggestions of restarting X. Here is yet another experiment: after booting into text console mode, suspend and resume. The keyboard still works. However, now attempting to start X results in a black screen. Killing X and starting it a second time works (and mouse and keyboard are fine within X). The difference between the logs are: 22c22 < (==) Log file: "/var/log/Xorg.0.log", Time: Mon Nov 24 07:38:46 2014 --- > (==) Log file: "/var/log/Xorg.0.log", Time: Mon Nov 24 07:39:50 2014 45c45 < (II) Loader magic: 0xaceac707520 --- > (II) Loader magic: 0x1a2444b07520 131a132 > (--) intel(0): Output eDP1 using initial mode 1366x768 on pipe 0 160a162,163 > (II) intel(0): switch to mode 1366x768@60.0 on eDP1 using pipe 0, position > (0, 0), rotation normal, reflection none > (II) intel(0): Setting screen physical size to 361 x 203 213c216 < (II) ws: /dev/wsmouse: maximum x position: 1023 --- > (II) ws: /dev/wsmouse: maximum x position: 1365
