Blank screens in virtual terminals
Are people still getting blank screens in their TTY's?? I'm running linux-4.0.5-1 and I'm perfectly able to view the virtual terminals. I had to change the AccelMode of the Intel Driver from SNA to UXA though. -- Nighpher (talk) 18:47, 7 June 2015 (UTC)
Anecdote: Fedora 23 on a UX305CA had several problems including the trackpad problem. All went away when rawhide kernel kernel-22.214.171.124.rc6.git1.2.fc24.x86_64 was installed. My best guess is that Skylake support in 4.4 plus the Fedora i2c driver fix is what made everything work. The Fedora 23 kernel-4.2.8-300.fc23.x86_64 had all these problems: improper screen resolution detection, at least some fn + arrow keys didn't generate PgUp etc, trackpad missing. I'm not sure how to translate this to Arch but I hope that it helps. -- 22:40, 1 January 2016 Hugh
- I compiled 4.4.0-rc7 with the first 16 patches applied from http://pkgs.fedoraproject.org/cgit/kernel.git/tree/, using the .config from my stock -ARCH kernel. Trackpad worked immediately on reboot
$ xinput Virtual core pointer id=2 [master pointer (3)] Virtual core XTEST pointer id=4 [slave pointer (2)] Logitech USB-PS/2 Optical Mouse id=9 [slave pointer (2)] Elan Touchpad id=11 [slave pointer (2)]
- -- 02:26, 2 January 2016 Precurse
From the article:
- There is also a kernel patch which enables the proper brightness keys. This patch is tested with 4.4 kernels: https://bugzilla.kernel.org/attachment.cgi?id=195071
- Applied this patch to 4.5 and brightness keys are working as expected.
Further from the article:
- 04/2016: If someone else can try this patch given by Intel DRM Team : https://patchwork.freedesktop.org/series/4783/. Please respond to this thread here when done: http://thread.gmane.org/gmane.comp.freedesktop.xorg.drivers.intel/84376/focus=84538[dead link 2021-11-10 ⓘ]
I have the UX305CA with the Intel 7265D wifi module.
Wifi on the UX305CA is fairly stable in my usage, however at times it can be quite unstable (as of Linux 4.14 with -29 ucode). There are several issues I've found which may or may not be model specific.
I've found that earlier versions of the iwlwifi microcode (-22 ucode and earlier) has had issues with some networks (especially eduroam) when waking up the laptop. The latest version as of the time of writing (29.x) has no issues whatsoever. I was able to reproduce this several times while I was on Ubuntu, and I was able to work around this by switching distros with newer linux-firmware packages. You may however see in your dmesg error messages with regards to the module restarting due to issues with firmware, the kernel will usually resolve this issue itself.
Wifi module unable to work after reboot
I don't know if this is model specific or if it affect other devices with this wifi module, but after rebooting my laptop, I sometimes lose wifi capability.
One easy way to fix this is to switch off the laptop completely first, then powering it back on. This could be due to a buggy firmware (but doesn't affect Windows), however I don't know too much on this issue.