ASUS UL20A: Difference between revisions

From Leo's Notes
This page was last edited on 24 February 2017, at 19:13.
m Text replacement - "<code>" to "{{code|"
m Text replacement - "</code>" to "}}"
Line 12: Line 12:
== Issues ==
== Issues ==
=== Linux ===
=== Linux ===
The module {{code|atl1c</code> 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.  
The module {{code|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.
You can verify this after booting into linux by running the following a few times.
Line 21: Line 21:
</syntaxhighlight>
</syntaxhighlight>


The kernel worker, {{code|kworker/x:y</code> (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:Personal]]
[[Category:Personal]]

Revision as of 19:13, 24 February 2017

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.