ASUS UL20A: Difference between revisions
m Text replacement - "</code>" to "}}" |
m reformat |
||
| Line 1: | Line 1: | ||
The ASUS UL20A is my laptop named 'Smallbook'. | The ASUS UL20A is my laptop named 'Smallbook'. | ||
== Drivers == | == Drivers == | ||
| Line 7: | Line 6: | ||
It appears that any drivers > 16 will fail to install on the laptop, under Windows 8.1. This version contains the two finger scroll built-in. | It appears that any drivers > 16 will fail to install on the laptop, under Windows 8.1. This version contains the two finger scroll built-in. | ||
== Issues == | == Issues == | ||
| Line 16: | Line 13: | ||
You can verify this after booting into linux by running the following a few times. | You can verify this after booting into linux by running the following a few times. | ||
{{highlight|lang=bash|code= | |||
<nowiki> | |||
echo l > /proc/sysrq-trigger | echo l > /proc/sysrq-trigger | ||
dmesg | tail -n 50 | dmesg | tail -n 50 | ||
</ | </nowiki> | ||
}} | |||
The kernel worker, {{code|kworker/x:y}} (where x and y are random based on which CPU core is running the module), will use up 100% of the available CPU of one core. | The kernel worker, {{code|kworker/x:y}} (where x and y are random based on which CPU core is running the module), will use up 100% of the available CPU of one core. | ||
[[Category:Hardware]] | |||
[[Category: | |||
Revision as of 02:38, 1 September 2019
The ASUS UL20A is my laptop named 'Smallbook'.
Drivers
Synaptics Touchpad
Get the 16.2.21 drivers from their website at: http://drivers.synaptics.com/Synaptics_v16_2_21_C_XP32_Vista32_Win7-32_XP64_Vista64_Win7-64_Win8.zip
It appears that any drivers > 16 will fail to install on the laptop, under Windows 8.1. This version contains the two finger scroll built-in.
Issues
Linux
The module atl1c drives the onboard Atheros ethernet adapter but will use up all the available CPU. This happened on the Linux Kernel used by Ubuntu (3.13.0-24) while running ClonezillaAlt. Removing it is not an option since it will kill the networking.
You can verify this after booting into linux by running the following a few times.
echo l > /proc/sysrq-trigger
dmesg | tail -n 50
The kernel worker, kworker/x:y (where x and y are random based on which CPU core is running the module), will use up 100% of the available CPU of one core.