Differences between revisions 67 and 68
Revision 67 as of 2010-01-24 15:04:46
Size: 9454
Editor: ?dsalt
Comment: Column correction & unwanted link removal
Revision 68 as of 2010-01-24 15:42:14
Size: 8874
Editor: ?dsalt
Comment: Control methods cleanup & update
Deletions are marked like this. Additions are marked like this.
Line 114: Line 114:
This table aims to compile the differences that the eeepc_laptop (or eeepc_acpi) module sees between models. When the kernel module is loaded, it sends an ACPI command that probes the capabilities ("control methods supported") of the eeepc it is running on. This can be seen by running `dmesg | grep eee`.
|| Model || BIOS version || Control methods supported ||
|| 701 || 801 ||<style="text-align: center;" |3> 0x101711 ||
||<^>701SD||<^>303||
|| 900 || 601, 704 ||
|| 901 || 1101, 1603, 1703, … ||<style="text-align: center;" |1> 0x101713 ||
|| 901GO || 2003 ||<style="text-align: center;" |1> 0x301711 ||
|| 900A || 0306, 0703 ||<style="text-align: center;" |1> 0x181711 ||
|| 1002HA || 0205 ||<style="text-align: center;" |1> 0x101713 ||
|| 1000HGO || 0602 ||<style="text-align: center;" |1> 0x301713 ||
|| 1000HE || 0605 ||<style="text-align: center;" |1> 0x301713 ||
|| 1005HA || ???? ||<style="text-align: center;" |1> 0xe101711 ||
|| 1008HA || ???? ||<style="text-align: center;" |1> ?x?????? ||
This table aims to compile the differences that the eeepc_laptop module sees between models. When the kernel module is loaded, it sends an ACPI command that probes the capabilities ("control methods supported") of the eeepc it is running on. This can be seen by running `dmesg | grep eee`.
Line 128: Line 116:
Newer kernels may cause the values to be reported as 0x6nnnnnn. For example, from a 901 running 2.6.31-rc6: || '''Model''' || '''Control methods supported''' ||
|| 701 ||<|3(> `0x`'''`?`'''`101711` ||
|| 701SD ||
|| 900 ||
|| 901 || `0x6101713` ||
|| 901GO || `0x`'''`?`'''`181711` ||
|| 1002HA || `0x`'''`?`'''`101713` ||
|| 1000HGO || `0x`'''`?`'''`301713` ||
|| 1000HE || `0x`'''`?`'''`301713` ||
|| 1005HA || `0xe101711` ||
|| 1008HA || `0x`'''`???????`''' ||

Newer kernels will add some extra options which the BIOS doesn't report to this. If any are added, the kernel log will contain at least one of the following four lines:
Line 130: Line 130:
eeepc_laptop: LID (1000000) not reported by BIOS, enabling anyway
Line 132: Line 133:
eeepc_laptop: Get control methods supported: 0x6101713 eeepc_laptop: TPD (8000000) not reported by BIOS, enabling anyway
Line 135: Line 136:
Also, it seems that the reported methods do not vary with the BIOS version but only with the model. The meaning of those control methods bitmaps can be better understood by looking at the `CM_ASL_*` constants in the source code of the eeepc_laptop kernel module. From right to left, the bits mean:
 * WLAN, Bluetooth, IRDA, IEEE1394 (Firewire);
 * webcam, TV (tuner?), GPS, DVD-ROM;
 * display switch, panel brightness, BIOS flash, ACPI flash;
 * CPU FV, CPU temperature, CPU fan, chassis fan;
 * USB port 1, USB port 2, USB port 3, modem;
 * SD/MMC card reader, 3G, WiMax, HWCF;
 * lid, type ('''what's this?'''), panel power, touchpad LED.
Line 137: Line 145:
The meaning of those control methods bitmaps can be better understood by looking at the CM_ASL_* constants in the source code of the eeepc_laptop / eeepc_acpi kernel module. From right to left, the bits mean "WLAN, Bluetooth, IRDA, 1394 (Firewire); webcam, TV (tuner?), GPS, DVD-ROM; display switch, panel brightness, BIOS flash, ACPI flash; CPU FV, CPU temp, CPU fan, chassis fan; USB 1, USB 2, USB 3, modem; card reader, lid". There are ACPI commands for toggling the 3G modem on and off, but no correspondence to any control method bit (as of yet). Disassembly of the asus_acpi module (2.6.21.4-eeepc, xandros on eeePC 901GO) suggest, that the 3G modem toggling support is indicated by bit 21 instead of lid. Wimax is probably indicated by bit 22. I'll test a kernel patch against eeepc-laptop platform driver and update the wiki afterwards.

These control methods control if the control files (some of the files in `/sys/devices/platform/eeepc`) are created or not; some are created anyway.
Some of these control methods control whether the control files (some of the files in `/sys/devices/platform/eeepc`) are created or not; some are created anyway.

Translations: Nederlands

Eee PC Models

Many pages on this wiki were written when only the earliest models were available. We will update those pages to include details for other models as needed. For example, our ../HowTo/Install should cover all models for which the installer has support. The following pages should not be used to avoid updating those pages or filing appropriate bugs with model-specific usertags (see ../Bugs/About), but instead should summarize the status of work on model-specific issues. In time, we should scrub away as many of these differences as possible by letting the software do all of the work.

If your exact model is not listed here, see http://event.asus.com/eeepc/comparison/eeepc_comparison.htm for a more complete table from Asus. In general when you see 802.11b/g/n on the Asus site it is either Ralink or Atheros AR928X, particularly in the more recent models, whereas 802.11b/g is Atheros (except 701SD uses Realtek rtl8187se instead).

Unsupported models

Asus releases so many models in short time that it is difficult to catch up with supporting them. As Asus does not care if the hardware is well supported by free drivers this task can become very difficult. So we decided not to support the Eee Box line. This model is more like a conventional PC. Coincidentally for the current generation of Eee Box, the debian-eeepc.img installer works because it includes rt2860. Just don't count on this for future models.

Similarly, we don't (presently) fully support EeePCs which use Poulsbo; see this bug for the reason why.

Differences between models

Hardware differences

This table aims to compile the different hardware drivers and issues known to the different models. Latest models may have hardware elements in common with any other model, so this table may be a start point for troubleshooting issues with new models.

Hardware differences that are totally transparent to the system (processor type or amount of RAM) won't be displayed here.

Networking

Input

Graphics

Ethernet

WLAN

Bt

3G

Silver hotkeys

Touchpad

2G Surf (700)

Atheros L2

Atheros AR2425

No

yes

None

Elantech

GMA900

701

no

Synaptics

900

6-byte Synaptics

900A

Atheros L1E

Elantech

GMA950

901GO

?Huawei EM770, ?Huawei E620

4

1000HGO

Yes

?Huawei E620

1000HD

Atheros L2

no

6-byte Synaptics

901, 1000, 1000H

Atheros L1E

Ralink RT2860

Elantech

904HD

Atheros

No

6-byte Synaptics

701SD

Realtek 8187

None

Elantech

GMA900

1000HE

Atheros AR928X or Ralink RT2860

Yes

4

GMA950

1002HA

Atheros AR928X

1

1005HA

Atheros L1C

???

1008HA

2?

1001HA

Ralink RT3090

???

???

???

1101HA

Atheros AR928X

GMA500

1201HA

1005P

Atheros AR???? (002C)

Yes

no

GMA950

1201N

Realtek 8192SE

???

???

Synaptics

GeForce 9400M

Note: Silver hotkey count does not include the power button.

Note: “6-byte Synaptics” may be Elantech.

WLAN

Module

Interface

802.11

Atheros AR2425

madwifi

ath0

ath5k

wlan0

Atheros AR928X

ath9k

Ralink RT2860

rt2860sta

ra0 (< 2.6.32)

b, g, n-draft

wlan0 (≥ 2.6.32)

rt2800pci

wlan0

Ralink RT3090

rt3090sta

wlan0

rt2800pci?

wlan0

Realtek 8187

rtl8187se

Realtek 8192SE

rtl8192se

wlan0?

Ethernet

Module

Speed

Atheros L1C

atl1c

10, 100, 1000

Atheros L1E

atl1e

10, 100, 1000

Atheros L2

atl2

10, 100

(Speed information is taken from various sources, including the kernel configuration help text.)

See here for more information about possible problems with the front microphone.

ACPI differences

This table aims to compile the differences that the eeepc_laptop module sees between models. When the kernel module is loaded, it sends an ACPI command that probes the capabilities ("control methods supported") of the eeepc it is running on. This can be seen by running dmesg | grep eee.

Model

Control methods supported

701

0x?101711

701SD

900

901

0x6101713

901GO

0x?181711

1002HA

0x?101713

1000HGO

0x?301713

1000HE

0x?301713

1005HA

0xe101711

1008HA

0x???????

Newer kernels will add some extra options which the BIOS doesn't report to this. If any are added, the kernel log will contain at least one of the following four lines:

eeepc_laptop: LID (1000000) not reported by BIOS, enabling anyway
eeepc_laptop: TYPE (2000000) not reported by BIOS, enabling anyway
eeepc_laptop: PANELPOWER (4000000) not reported by BIOS, enabling anyway
eeepc_laptop: TPD (8000000) not reported by BIOS, enabling anyway

The meaning of those control methods bitmaps can be better understood by looking at the CM_ASL_* constants in the source code of the eeepc_laptop kernel module. From right to left, the bits mean:

  • WLAN, Bluetooth, IRDA, IEEE1394 (Firewire);
  • webcam, TV (tuner?), GPS, DVD-ROM;
  • display switch, panel brightness, BIOS flash, ACPI flash;
  • CPU FV, CPU temperature, CPU fan, chassis fan;
  • USB port 1, USB port 2, USB port 3, modem;
  • SD/MMC card reader, 3G, ?WiMax, HWCF;

  • lid, type (what's this?), panel power, touchpad LED.

Some of these control methods control whether the control files (some of the files in /sys/devices/platform/eeepc) are created or not; some are created anyway.

It is currently unknown if adding hardware (i.e. bluetooth on the 900, 3G modem on the 901) affects the control methods – if so, it would mean that the BIOS is quite smart when it comes to autodetecting new specific hardware – but removing hardware appears to cause no change. (This has been tested by removing the WLAN card from a 901.)