The XXXp models (like the 1005p) are based on newer Pine Trail platforms. Issues may arise as newer models are released.

The XXXp models (like the 1005p) are based on newer Pine Trail platforms. Issues may arise as newer models are released.

−

Fn Keys (included wireless switch)

+

Fn Keys (included wireless switch) o

−

* Almost working, the Fn+F2 (wireless switch) doesn't work yet; supported by eeepc_laptop kernel module. May require 'acpi_osi=Linux' to be added to kernel boot parameters for eeepc_laptop module to load.

+

* Almost working, the Fn+F2 (wireless switch) mostly works; supported by eeepc_laptop kernel module. May require 'acpi_osi=Linux' to be added to kernel boot parameters for eeepc_laptop module to load. The system doesn't always connect right away when re-enabled by HW switch (~1 minute delay).

Wireless chipset

Wireless chipset

* Eee PC 901/1000H wireless chip is Ralink RT2860, which is not supported by current kernel (work on support is in progress, see [http://rt2x00.serialmonkey.com/wiki/index.php/Main_Page rt2400] project page for more details), but there's an open source driver provided by Ralink. RPMFusion has a kmod package with this driver (kmod-rt2860). [https://fedoraproject.org/wiki/OtherRepositories Read this for more details on external repositories].

* Eee PC 901/1000H wireless chip is Ralink RT2860, which is not supported by current kernel (work on support is in progress, see [http://rt2x00.serialmonkey.com/wiki/index.php/Main_Page rt2400] project page for more details), but there's an open source driver provided by Ralink. RPMFusion has a kmod package with this driver (kmod-rt2860). [https://fedoraproject.org/wiki/OtherRepositories Read this for more details on external repositories].

With some Eee PC's, the brightness setting are either too low, or are sometimes a little inconstant or arbitrary (inconsistent on each boot, eg. high to low/completely off).

+

If you have issues with this, issue this command to fix it:

+

+

<pre># setpci -s 00:02.0 f4.b=80

+

</pre>

+

+

The <code>80</code> represents the desired range for brightness in hexadecimal, where <code>FF</code> allows to maximum brightness. <code>80</code> is about half and is generally ideal but may need to be tweaked to suit one's need.

<li>Install Jupiter and Jupiter Support/Eee from [http://sourceforge.net/projects/jupiter/ SourceForge] to add power profiles as well as extra function keys and automatic support for Super Hybrid Engine.

+

+

Download the latest jupiter and jupiter-support-eee RPM packages from SourceForge.

The XXXp models (like the 1005p) are based on newer Pine Trail platforms. Issues may arise as newer models are released.

Fn Keys (included wireless switch) o

Almost working, the Fn+F2 (wireless switch) mostly works; supported by eeepc_laptop kernel module. May require 'acpi_osi=Linux' to be added to kernel boot parameters for eeepc_laptop module to load. The system doesn't always connect right away when re-enabled by HW switch (~1 minute delay).

Wireless chipset

Eee PC 901/1000H wireless chip is Ralink RT2860, which is not supported by current kernel (work on support is in progress, see rt2400 project page for more details), but there's an open source driver provided by Ralink. RPMFusion has a kmod package with this driver (kmod-rt2860). Read this for more details on external repositories.

With some Eee PC's, the brightness setting are either too low, or are sometimes a little inconstant or arbitrary (inconsistent on each boot, eg. high to low/completely off).
If you have issues with this, issue this command to fix it:

# setpci -s 00:02.0 f4.b=80

The 80 represents the desired range for brightness in hexadecimal, where FF allows to maximum brightness. 80 is about half and is generally ideal but may need to be tweaked to suit one's need.

Install Jupiter and Jupiter Support/Eee from SourceForge to add power profiles as well as extra function keys and automatic support for Super Hybrid Engine.
Download the latest jupiter and jupiter-support-eee RPM packages from SourceForge.